Beta Directory Issues

[jdcr256]

In the current LUWS, when you use the Search for Member function, it brings up all the info on the member, including their ward. The beta member search feature does not indicate the ward. I see this as a major problem, as this is often vital information in a search. Any chance it can/will be fixed?

I just logged this as a bug. It should be fixed for our June release.

[zaneclark]

In the current LUWS, as a Stake Administrator, I have admin status in all wards. I can't seem to find a way to get this in the beta directory. I may be missing a link (please no jokes about the "missing link.")

[jdlessley]

In the current LUWS, as a Stake Administrator, I have admin status in all wards. I can't seem to find a way to get this in the beta directory.

By Stake Administrator I am assuming you mean you are a LUWS administrator at the stake level. The beta directory uses edit rights based on stake and unit standard positions. For the stake the positions with edit rights are the stake presidency, clerks, and STS. A position of stake website administrator is not given edit rights as of now for the directory. Anyone can be given administrator rights in the current LUWS by another admin. That is not true for the beta directory.

If you are a stake clerk, assistant stake clerk, or STS and do not have edit rights you should check in MLS to see whether your position is a standard position or a custom position. Only those using the standard positions will be granted edit rights.

I may be missing a link.

There is no additional link. When you sign in using your LDSAccount you will be recognized as having edit rights if you hold a standard position from the list of those who have been granted those rights. When a person with edit rights selects an individual's name they will see "You have rights to edit the family profile" and an Edit Profile button above the individual's information.

[russellhltn]

It's possible that the role of administrator may be changing. So far, all we've seen is directory and calender in the beta. The beta does allow greater changes to membership and as such, should probably only be handled by a clerk.

The role of web admin may not be obsolete. There's still other function we haven't seen rolled out yet. But the days of one person being admin over all the functions may be coming to a close.

[zaneclark]

By Stake Administrator I am assuming you mean you are a LUWS administrator at the stake level. The beta directory uses edit rights based on stake and unit standard positions. For the stake the positions with edit rights are the stake presidency, clerks, and STS. A position of stake website administrator is not given edit rights as of now for the directory. Anyone can be given administrator rights in the current LUWS by another admin. That is not true for the beta directory.

As I understand you, the stake clerks have edit rights for the web site but the web site administrator does not... Sounds a little backwards.... I hope this changes...

[russellhltn]

As I understand you, the stake clerks have edit rights for the web site but the web site administrator does not... Sounds a little backwards.... I hope this changes...

No, it makes perfect sense to me. The part of the website we're talking about is the membership records. That's the dominion of the ward clerks. The stake clerk(s) have the responsibility to teach the ward clerks.

What we're seeing is a redefining of "web site administrator". Where it used to be just one person had ability to change all aspects, the responsibility in different areas are being divided up according to calling.

If your Bishop or Stake President wants you to continue to administer the new site, then they should probably make you an assistant clerk and enter that as a standardized calling in MLS.

[Kyrandita]

I have discovered some new oddities about the directory...

When I was leaving for College I decided to run some tests on how the photos would transfer from stake to stake... so I uploaded a photo for myself (both individual and Family, though they were just a copy of the same photo since I'm single...) to see how it worked... I'd done this for my entire singles branch as well, but only the Family photo for them since that's the one most people seemed to care about because of the member photos area...

When I moved I was fortunate to move in with one of the people from my branch... (otherwise I wouldn't have noticed anything weird...)

When I log in I see both my family and individual photos exactly as they'd been before... no changes, but when I select my roommate his picture just shows up as a broken link... and it's the same when he logs in, he can see his picture just fine, but mine appear as broken links...

in my new ward I have no way to access the Admin tools to see whether there is some process of authorization that needs to happen before Old photos transfer into the new ward, and to some degree I guess that would make sense, what is acceptable as a member photo to one clerk may be seen as inappropriate by another... but I don't think that's the case...

I'm sorry if this is just a repeat of the "photos don't transfer between stakes" issue but from all I've read this doesn't seem to match the criteria... let me know if you need any more details... (or less, I tend to over-explain )

[russellhltn]

Under the current beta, photos have to be approved before anyone else can see them. Do you know if yours were approved before you moved?

[Kyrandita]

They had been, I approved them myself... I could try uploading them again, but without an Admin aware of the Beta to approve that wouldn't fix the photos, plus it would kind of defeat the purpose of doing this experiment in the first place...

[russellhltn]

They had been, I approved them myself.

I suggest you send a note in feedback. I don't know how it was intended to work, but having to reapprove photos of all move-in seems like extra work to me.