Many years ago I prepared names for the temple (several children) and did all their ordinance work except sealing to parents. I discovered before I did the SP that my research was incorrect and the parents on the name cards were not the correct parents of the children (same father's name). I reserved those names so no one would do those sealings and have been sitting on them for a very long time. What should I do to make sure those sealings are not done and others mislead about who the parents are for these children? Thx. ----- Original Message ----- From: Thomas Jay Kemp To: lds-ward-consultant@rootsweb.com Sent: Friday, April 26, 2013 5:28 AM Subject: Re: [LDS-WC] Shared Temple Ordinances Deadbeats sitting on names .... for years ...? No. It's likely that these were submitted by elderly members who have since aged out ... members who struggled with computers and weren't sure how do deal with the files; members that thought when they "submitted" their names that they would be worked on and completed and have no idea that they are still sitting there waiting for them to take further action. The every changing submission seems 'easy' for us to navigate - but for others it is a maze of buttons, rules, options that are difficult to comprehend. That's why only 1% of the Church is actively submitting names. Think back. The only way to 'submit' a name 6 years ago was to 'reserve' it for 'you' to do. The members didn't necessarily understand that. Submitted - in the general understanding is that it's in the system - it's being taken care of. So - if they submitted 200 relatives - it would take them decades to do that much Temple work. At the same time there was no easy way for them to flip those names in to the general Temple file. Difficult to follow - hard to understand computers - ever changing Temple submission rules/programs - it would be easy for handfuls of names to become millions of names stuck in the system. The default should be that all names are set as 'submitted' to the general Temple - with an opt out to reserve only the few names that you can realistically do. This new "Share" button makes it easy to flip the names to the general Temple file. But require the member to opt in to take further action. If we could have the 'default' - set to submit all names to the general Temple file - with a check box option to select out the few names/ordinances that we want to do - it would dramatically reduce the huge backlog of 'reserved' ordinances going forward. This "Share" button is really handy for accomplishing that - we should make sure the members we work with are using it. On Fri, Apr 26, 2013 at 1:41 AM, <JCBrooks@aol.com> wrote: > It just occurred to me that maybe the reason the list is definitely > shortened is because they don't want us to see how many ordinances are not > getting done :-) > > I'm finding a lot a stale ordinances in my temple list that are due to > the fact that someone else, some Legacy submitter with no contact info, > submitted the names for work pre-2008 and has never completed it. Then I > came > along and added parents and a sealing to parents request. My request will > not be done until the deadbeat (for lack of a better word) submitter > problem > is resolved. > > I sure hope they are working on that serious problem. It is a result of > names that went missing in action after the switch to NFS (cards in temples > went to limbo), people who printed cards and lost them, people who printed > cards for a "must do" baptism and never completed the other ordinances, > and > people who either died or lost interest. > > Michele > > > In a message dated 4/25/2013 10:34:14 P.M. Pacific Daylight Time, > dsam52@sampubco.com writes: > > I show at the moment > > Family Tree > 132 reserved > 75 shared > 3 printed > > in new.Familysearch > 205 total (that is the combined of 132 and 75 because I retain sealings.) > > Anyway, I had been told at least in nFS it is 400 the limit or it freezes. > > Nothing is said about the limit in Family Tree. > > The only limits I am aware is 50 records per batch to be printed. > > And in Getsatisfaction, it had been reported there are multiple issues > with Temple lists right now. > > > David Samuelsen > > On 4/25/2013 8:04 PM, Thomas Jay Kemp wrote: > > I like this new feature. > > > > Does it list all submitted names - or to a number limit? > > > > For example - in nFS - I see a count that is double/triple the count > that > > is showing in the Shared (Reserved/Shared/Printed) combined counts. > > > > It seems like the new Shared count is up to a capped limit. > > What is correct? > > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > > ------------------------------- > > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' > without the quotes in > the subject and the body of the message > > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' > without the quotes in the > subject and the body of the message > > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' > without the quotes in the subject and the body of the message > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM ------------------------------- To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

Delete the relationship to incorrect parents on the person page in the family listing by clicking on edit relationship and then delete relationship. You can the create new parents and add children back to them. Keep track of children's PID numbers Is that how the rest of you would do it? Michele Sent from my iPhone On Apr 26, 2013, at 1:36 PM, "Gay Davis" <grdavis@centurytel.net> wrote: > Many years ago I prepared names for the temple (several children) and did all their ordinance work except sealing to parents. I discovered before I did the SP that my research was incorrect and the parents on the name cards were not the correct parents of the children (same father's name). I reserved those names so no one would do those sealings and have been sitting on them for a very long time. What should I do to make sure those sealings are not done and others mislead about who the parents are for these children? Thx. > ----- Original Message ----- > From: Thomas Jay Kemp > To: lds-ward-consultant@rootsweb.com > Sent: Friday, April 26, 2013 5:28 AM > Subject: Re: [LDS-WC] Shared Temple Ordinances > > > Deadbeats sitting on names .... for years ...? > No. > > It's likely that these were submitted by elderly members who have since > aged out ... members who struggled with computers and weren't sure how do > deal with the files; members that thought when they "submitted" their names > that they would be worked on and completed and have no idea that they are > still sitting there waiting for them to take further action. > > The every changing submission seems 'easy' for us to navigate - but for > others it is a maze of buttons, rules, options that are difficult to > comprehend. That's why only 1% of the Church is actively submitting names. > > Think back. The only way to 'submit' a name 6 years ago was to 'reserve' it > for 'you' to do. > The members didn't necessarily understand that. > Submitted - in the general understanding is that it's in the system - it's > being taken care of. > > So - if they submitted 200 relatives - it would take them decades to do > that much Temple work. > At the same time there was no easy way for them to flip those names in to > the general Temple file. > Difficult to follow - hard to understand computers - ever changing Temple > submission rules/programs - it would be easy for handfuls of names to > become millions of names stuck in the system. > > The default should be that all names are set as 'submitted' to the general > Temple - with an opt out to reserve only the few names that you can > realistically do. > > This new "Share" button makes it easy to flip the names to the general > Temple file. > But require the member to opt in to take further action. > If we could have the 'default' - set to submit all names to the general > Temple file - with a check box option to select out the few > names/ordinances that we want to do - it would dramatically reduce the huge > backlog of 'reserved' ordinances going forward. > > This "Share" button is really handy for accomplishing that - we should make > sure the members we work with are using it. > > > On Fri, Apr 26, 2013 at 1:41 AM, <JCBrooks@aol.com> wrote: > >> It just occurred to me that maybe the reason the list is definitely >> shortened is because they don't want us to see how many ordinances are not >> getting done :-) >> >> I'm finding a lot a stale ordinances in my temple list that are due to >> the fact that someone else, some Legacy submitter with no contact info, >> submitted the names for work pre-2008 and has never completed it. Then I >> came >> along and added parents and a sealing to parents request. My request will >> not be done until the deadbeat (for lack of a better word) submitter >> problem >> is resolved. >> >> I sure hope they are working on that serious problem. It is a result of >> names that went missing in action after the switch to NFS (cards in temples >> went to limbo), people who printed cards and lost them, people who printed >> cards for a "must do" baptism and never completed the other ordinances, >> and >> people who either died or lost interest. >> >> Michele >> >> >> In a message dated 4/25/2013 10:34:14 P.M. Pacific Daylight Time, >> dsam52@sampubco.com writes: >> >> I show at the moment >> >> Family Tree >> 132 reserved >> 75 shared >> 3 printed >> >> in new.Familysearch >> 205 total (that is the combined of 132 and 75 because I retain sealings.) >> >> Anyway, I had been told at least in nFS it is 400 the limit or it freezes. >> >> Nothing is said about the limit in Family Tree. >> >> The only limits I am aware is 50 records per batch to be printed. >> >> And in Getsatisfaction, it had been reported there are multiple issues >> with Temple lists right now. >> >> >> David Samuelsen >> >> On 4/25/2013 8:04 PM, Thomas Jay Kemp wrote: >>> I like this new feature. >>> >>> Does it list all submitted names - or to a number limit? >>> >>> For example - in nFS - I see a count that is double/triple the count >> that >>> is showing in the Shared (Reserved/Shared/Printed) combined counts. >>> >>> It seems like the new Shared count is up to a capped limit. >>> What is correct? >>> >>> Please send the one word message SUBSCRIBE or UNSUBSCRIBE to >> LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM >>> ------------------------------- >>> To unsubscribe from the list, please send an email to >> LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' >> without the quotes in >> the subject and the body of the message >> >> Please send the one word message SUBSCRIBE or UNSUBSCRIBE to >> LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM >> ------------------------------- >> To unsubscribe from the list, please send an email to >> LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' >> without the quotes in the >> subject and the body of the message >> >> >> Please send the one word message SUBSCRIBE or UNSUBSCRIBE to >> LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM >> ------------------------------- >> To unsubscribe from the list, please send an email to >> LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' >> without the quotes in the subject and the body of the message > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message