LDS Accounts with access to local unit resources must be tied to a specific member. Using the membership number of an less-active member should be very inappropriate because it would expose their private information to the missionary. The only option is to create an out-of-unit record for the missionary and then give them a standard calling in MLS. When a missionary transfers you would have to remove the previous missionaries' out-of-unit record and create one for the new ones. There is no way around that, at least at this time.aetaber wrote:Our very alert sister missionaries asked for access to our ward calendar, particularly once they get more computer time (per the June 2013 broadcast). How can we get a missionary account set up that a) doesn't tie up one of our local less-active member accounts, b) doesn't need to be reset every time we have a missionary transfer, and c) can have calendar viewing privileges for all ward calendars?
Best regards,
Alan Taber
Moorestown, NJ
The instructions on the sync page states "(This URL is provided for your own personal use. It should not be shared with anyone else.)"sbradshaw wrote:Another option would be to have the ward mission leader give them his sync URL for the calendar.
What caused them to be removed is that the church decided to stop recording who did the proxy work for whom. Once it got simplified to where and when, the mag stripe was no longer needed. It wasn't the technology that was the wrong direction, it was the purpose that got changed. There was a similar change on the membership record side - that as it turned out went too far. (Stopped recording who ordained whom with the resulting problems with priesthood linage.)mevans wrote:Some people might remember how temples used to be computerized with the mag-stripe recommend and that the church put a stop to that and rethought everything and came up with a different way to use computers inside the temples.
It's obvious that mission offices already associate missionaries with wards they are serving in. The Directory shows this information in the Missionary section.russellhltn wrote:Seems to me the logical way to do it is to have the mission office assign missionaries to a ward and then they'd have access like regular members. But I'm sure that's a major code change to accommodate this new function.
How would this work with missionaries who are assigned to multiple wards?russellhltn wrote:Seems to me the logical way to do it is to have the mission office assign missionaries to a ward and then they'd have access like regular members.
Probably much the same way out-of-unit leaders are handled. (They'd have a list to pick which unit to look at.) But that makes the data that much more complicated and longer to develop.Gary_Miller wrote:How would this work with missionaries who are assigned to multiple wards?
That's interesting...the whole church membership is accessible via LDAP. It makes me want to investigate LDAP more to see how it might be useful in solving some problems.Gary_Miller wrote:How would this work with missionaries who are assigned to multiple wards?russellhltn wrote:Seems to me the logical way to do it is to have the mission office assign missionaries to a ward and then they'd have access like regular members.
They could, but for the way most of the apps are written right now that would mean giving them an actual out-of-unit calling.mevans wrote: The church currently supports out-of-unit callings. I figured missionaries might be handled with the same mechanism.
CDOL and the LDAP portion can definitely support multiple out-of-unit callings and multiple units. The problem is each app has to check for the users home unit and then decide if they want to look at callings as well and then handle someway of switching/viewing all units. Some of the apps do this better than others.mevans wrote:I don't know if you can have more than one out-of-unit calling. If the directory schema is set up right, it should be able to support multiple units.