Missing Sealing Info.

Hello!
I was recently called as the ward clerk for a married student ward at BYU. Now that summer is in full swing, students are getting married, moving in, and moving out frequently. I am having an issue with students that are recently sealed in the temple (within the last month). Their sealing information does not show up on LCR even though the temple recorder should have updated that info the day of the wedding. Thus, I end up having to move in each spouse individually, add the wife to the husband's household, and then update her last name to her married name if desired by the couple. The problem is that without sealing information, the spouses show up as "other" within the household. Are the temples behind on recording sealing info? Is there a glitch on their end of the system or is the problem on my end? Any information would be appreciated.

Thanks!

I'm not sure as there's much you can do short of asking the stake president to put a bit of pressure on the temples to keep one. I'd indicate that it's creating a problem with the records.

One thought: you might record the sealing as a civil marriage before putting the two into the same household. That will cause the spouse to show up correctly. I'm not sure if it will mess up the membership record as it might appear in the history that they married then sealed. I'm not sure as it would make a difference.

critviz wrote: Sun May 29, 2022 11:37 am The problem is that without sealing information, the spouses show up as "other" within the household.

I think the "sealing information" is not the problem. If you just move two individuals together without recording a marriage, one of them will normally show up as "other." I believe if you record the marriage between them, the spouse will show correctly. However, in that case, I'm not sure what will happen to the record when the temple gets around to recording the sealing.

davesudweeks wrote: Sun May 29, 2022 2:21 pm I think the "sealing information" is not the problem. If you just move two individuals together without recording a marriage, one of them will normally show up as "other."

Correct, but it appears that he's wanting the temple to record the marriage/sealing. And there lies the problem. Like you, I'm not sure what would happen if he records it like a civil marriage in the interim.

I'll add, I believe that once an "other" always a "other" until the marriage is recorded, the household split and recombined again. However, I think it takes a pretty sharp eye to spot the spouse is an "other" in most listings the members have access to. At least until children are added to the household.

I believe there's still a "special request" feature. One could try sending the sealing information that way (I assume LCR won't let you record it). CHQ will have to check with the temple before recording it, and you may get a "miffed message", but I'd just explain you need the update sooner than later to keep the records accurate and ask for recommendations.

The server that used to transfer living temple ordinances to the membership system died a little bit ago and since that process was very old and going to a legacy system it couldn't be restored easily. We have been working on replacing and modernizing it. We have just finished the process for endowments and sealing to parents and that has been running now this week. They have been getting the data manually and trying to enter the sealing to spouse records. We have the code for that ready to start testing so we are hoping to have it done before too long (but marriages are one of the hard things in the system (and in real life ) so it may take a while to work out all the kinks. I'm sorry for any hardship this has caused. We feel that the hand of the Lord was in this because it sped up the process of getting rid of the legacy system in ways that we haven't been able to ourselves, but we also recognize that it has disrupted some things for clerks.

Recording the marriage will not cause any issues with the process once we get it back in place so feel free to do that for now.