Very interesting. I am concerned this might happen to baby brothers who die as infants and receive the same name one after the other. What would have happened if you had found the "possible match" before the records were combined and marked them as "not the same person"? Would FT still have allowed them to be combined? > From: milesmeyer@gmail.com > Date: Fri, 31 May 2013 09:25:10 -0400 > To: lds-ward-consultant@rootsweb.com > Subject: Re: [LDS-WC] Delete button > > Thanks for the link to the document. I experienced a problem the other day > where two brothers, Bernard Henry Stueve and Henry Bernard Stueve were > combined by FamilySearch. The only thing I could do was make sure that > Bernard Henry's information was correct and then re-add Henry Bernard to > the family. This meant that Henry Bernard no longer had his temple > ordinance info associated with him. I was able to sync with nFS and upload > the "unofficial" ordinance records from my file. Now his record says > "Complete" but no information is listed as to when and where the ordinances > were done. > > Miles Meyer > Jacksonville, FL > > "Unless someone like you cares a whole awful lot, nothing is going to get > better. It's not." - Dr. Seuss, The Lorax > > > On Fri, May 31, 2013 at 9:08 AM, Scott and Tammy Stevenson < > sstevenson@safelink.net> wrote: > > > The delete button caution says: "It is recommended that you delete people > > only if you added a person by mistake or if the person never existed." > > I think that is a good option because I have seen where people have added > > names and information in by mistake before really searching and verifying > > the person (and listing the wrong person/information)- only then to figure > > out they made a mistake and can't figure out how to get rid of that wrong > > person once they figure out the right person. Additionally it should be > > helpful in deleting out the people listed with the incorrect gender- as one > > cannot merge individuals of different genders. > > > > As for the uncombine option- don't wait for that appear. With the new > > merging, that option is not possible. In new.familysearch.org all > > information merged was kept in separate "little files" and so it was easy > > to > > uncombine or separate those files out. With the merge in Family Search- > > there are no "little files" to easily separate out, only the selected > > information is saved and put in one record/file. The unmerge button will > > only appear until changes have been made in that newly created record. > > Once > > changes have been made, the computer doesn't know to which of the records > > the changes apply.... so it cannot uncombine. The option is to make > > separations manually. Here's a link to the white paper about how to > > separate people who have been incorrectly combined in new.familysearch. > > > > http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ > > pdf/familyTreeNotMyAncestorWhitepaper.pdf > > The issue there still remains, that in creating a new person, the > > ordinances > > will show as available- and probably have already been done (multiple times > > in some cases.) There is supposed to be a "Fix" in the works for an > > ordinance assignment option, but it hasn't been released yet. > > > > If changes are well sourced and documented, it is hoped that others will > > not > > come back in and change those records. > > > > Dive into Family Tree- it really does have a lot of great options! Not > > perfect, but I think superior to new.familysearch in the ability to really > > correct errors! And sourcing, stories and photos are amazing! > > Tammy Stevenson > > ______________________________________________________ > > Message: 3 > > Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) > > From: JCBrooks@aol.com > > Subject: [LDS-WC] Delete button > > To: lds-ward-consultant@rootsweb.com > > Message-ID: <71b04.50d1a8db.3ed93902@aol.com> > > Content-Type: text/plain; charset="US-ASCII" > > > > Is anyone as concerned as I am about the delete button? We should be > > merging first before deleting as I believe ordinances could well be lost. > > Plus > > there is so much disagreement in some families, particularly non-LDS lines, > > about research. Frankly Family Tree is embarrassing to me when I look at > > what a mess they and others have made of simple pure, well documented > > families. > > > > Like others, I am waiting until they straighten out more before I spend any > > great amount of time fixing things. It is so frustrating and we only have > > half the tools. Uncombining is sure more important than delete!! > > > > Michele > > ______________________________________________________________ > > > > > > > > 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
I was working on NFS yesterday and will start working from now on with Family Tree to straighten out the line I worked with yesterday. I was aghast to find on a Richards line, which I thought was in good order, that a person had gone in and entered death and burial dates of 2012 for people born in the 1700's. In addition, new lines have been brought in by adding people that don't really belong in a particular family. Some of the entries now have couples as their own parents, e.g., John and Sally are the couple and John and Sally are the parents also (same people). It is discouraging to put in so many hours with well researched data and then have it all convoluted It will take many hours to try and straighten this out if it is even possible. I am afraid this will be a perpetual problem. Gay Davis ----- Original Message ----- From: Mary S. Scott (Michigan) To: lds-ward-consultant@rootsweb.com Sent: Friday, May 31, 2013 9:13 AM Subject: [LDS-WC] Cleaning up on Family Tree David's point about cleaning up our family lines on Family Tree is right on target. The other day I was working on Family Tree and looking at some of my husband's families, particularly the Tanner families from Payson, Utah. Earlier that day I had read an LDS biographical sketch about a sister in a newly published book. The sister's husband had married several women before the Manifesto. They lived in some of the areas where my husband's family had lived. One of his daughters married a man with the surname of Tanner. I went on Family Tree and wanted to see how this daughter was related to my husband. As I looked at the records for the various Tanner branches, I was amazed at the inconsistencies and inaccuracies which are there. For instance, the information about John Tanner (the early convert to the Church who gave a substantial amount of money for the Kirkland Temple to Joseph Smith) needed immediate attention. (John Tanner never lived in Payson but his third wife and many of his children did.) John Tanner's mother was Thankful Tefft but Family Tree had Thankful also as the wife of John. (Terrible error and not one to let carry down to people who might not know the difference. It needed to be corrected immediately and appropriate explanations added.) The family relationships were certainly in need of careful examination and correction. With my husband's approval, I started the process of correcting these relationships. As I told my husband, we will need to look at every one of his family lines because there are probably changes which need to be made for many family members. My husband isn't that keen on family history but if we don't do these changes who will? If not now, when? Are we going to wait for our children and unborn grandchildren to be interested? It might not happen. I think now is the time and it is a task which we can do while we are able to do so. As I used to tell my family history classes, we can work on one family at a time. Straighten it out, add sources and notes, check ordinances, merge if necessary, etc. We don't have to attack the entire tree but only these smaller twigs in a methodical way. When we feel one family is in order, than we can move to another family. Besides, as we work on Family Tree, we can address issues and offer insights or feedback. Thanks for listening. I learn a lot from each of you. Mary Scott Aurora, Illinois 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
I think the important thing is to make sure you have a good amount of the source info so they don't get combined. In my case, the Ohio birth and death records are pretty complete so I can attach those records to indicate they are different people. I have also been attaching the Find A Grave records to show they are different. I think the "Not a match" makes it a little more difficult by adding additional steps but I don't think it makes it impossible to merge if you want to put the work in (not completely sure since I haven't encountered that yet). I have marked a few possible matches as "Not a match" but haven't gone back to see what happens to those records. The other thing I have been doing is I send all the contributors listed an e-mail letting them know that I am "messing around" in their names making edits and adding information. So far that has worked and we have been able to discuss the possible problems. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Fri, May 31, 2013 at 9:31 AM, Jorge Todeschini < jorgetodeschini@hotmail.com> wrote: > Very interesting. > > I am concerned this might happen to baby brothers who die as infants and > receive the same name one after the other. > > What would have happened if you had found the "possible match" before the > records were combined and marked them as "not the same person"? Would FT > still have allowed them to be combined? > > > From: milesmeyer@gmail.com > > Date: Fri, 31 May 2013 09:25:10 -0400 > > To: lds-ward-consultant@rootsweb.com > > Subject: Re: [LDS-WC] Delete button > > > > Thanks for the link to the document. I experienced a problem the other > day > > where two brothers, Bernard Henry Stueve and Henry Bernard Stueve were > > combined by FamilySearch. The only thing I could do was make sure that > > Bernard Henry's information was correct and then re-add Henry Bernard to > > the family. This meant that Henry Bernard no longer had his temple > > ordinance info associated with him. I was able to sync with nFS and > upload > > the "unofficial" ordinance records from my file. Now his record says > > "Complete" but no information is listed as to when and where the > ordinances > > were done. > > > > Miles Meyer > > Jacksonville, FL > > > > "Unless someone like you cares a whole awful lot, nothing is going to get > > better. It's not." - Dr. Seuss, The Lorax > > > > > > On Fri, May 31, 2013 at 9:08 AM, Scott and Tammy Stevenson < > > sstevenson@safelink.net> wrote: > > > > > The delete button caution says: "It is recommended that you delete > people > > > only if you added a person by mistake or if the person never existed." > > > I think that is a good option because I have seen where people have > added > > > names and information in by mistake before really searching and > verifying > > > the person (and listing the wrong person/information)- only then to > figure > > > out they made a mistake and can't figure out how to get rid of that > wrong > > > person once they figure out the right person. Additionally it should be > > > helpful in deleting out the people listed with the incorrect gender- > as one > > > cannot merge individuals of different genders. > > > > > > As for the uncombine option- don't wait for that appear. With the new > > > merging, that option is not possible. In new.familysearch.org all > > > information merged was kept in separate "little files" and so it was > easy > > > to > > > uncombine or separate those files out. With the merge in Family > Search- > > > there are no "little files" to easily separate out, only the selected > > > information is saved and put in one record/file. The unmerge button > will > > > only appear until changes have been made in that newly created record. > > > Once > > > changes have been made, the computer doesn't know to which of the > records > > > the changes apply.... so it cannot uncombine. The option is to make > > > separations manually. Here's a link to the white paper about how to > > > separate people who have been incorrectly combined in new.familysearch. > > > > > > > http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ > > > pdf/familyTreeNotMyAncestorWhitepaper.pdf > > > The issue there still remains, that in creating a new person, the > > > ordinances > > > will show as available- and probably have already been done (multiple > times > > > in some cases.) There is supposed to be a "Fix" in the works for an > > > ordinance assignment option, but it hasn't been released yet. > > > > > > If changes are well sourced and documented, it is hoped that others > will > > > not > > > come back in and change those records. > > > > > > Dive into Family Tree- it really does have a lot of great options! Not > > > perfect, but I think superior to new.familysearch in the ability to > really > > > correct errors! And sourcing, stories and photos are amazing! > > > Tammy Stevenson > > > ______________________________________________________ > > > Message: 3 > > > Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) > > > From: JCBrooks@aol.com > > > Subject: [LDS-WC] Delete button > > > To: lds-ward-consultant@rootsweb.com > > > Message-ID: <71b04.50d1a8db.3ed93902@aol.com> > > > Content-Type: text/plain; charset="US-ASCII" > > > > > > Is anyone as concerned as I am about the delete button? We should be > > > merging first before deleting as I believe ordinances could well be > lost. > > > Plus > > > there is so much disagreement in some families, particularly non-LDS > lines, > > > about research. Frankly Family Tree is embarrassing to me when I look > at > > > what a mess they and others have made of simple pure, well documented > > > families. > > > > > > Like others, I am waiting until they straighten out more before I > spend any > > > great amount of time fixing things. It is so frustrating and we only > have > > > half the tools. Uncombining is sure more important than delete!! > > > > > > Michele > > > ______________________________________________________________ > > > > > > > > > > > > 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 >
Thanks for the link to the document. I experienced a problem the other day where two brothers, Bernard Henry Stueve and Henry Bernard Stueve were combined by FamilySearch. The only thing I could do was make sure that Bernard Henry's information was correct and then re-add Henry Bernard to the family. This meant that Henry Bernard no longer had his temple ordinance info associated with him. I was able to sync with nFS and upload the "unofficial" ordinance records from my file. Now his record says "Complete" but no information is listed as to when and where the ordinances were done. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Fri, May 31, 2013 at 9:08 AM, Scott and Tammy Stevenson < sstevenson@safelink.net> wrote: > The delete button caution says: "It is recommended that you delete people > only if you added a person by mistake or if the person never existed." > I think that is a good option because I have seen where people have added > names and information in by mistake before really searching and verifying > the person (and listing the wrong person/information)- only then to figure > out they made a mistake and can't figure out how to get rid of that wrong > person once they figure out the right person. Additionally it should be > helpful in deleting out the people listed with the incorrect gender- as one > cannot merge individuals of different genders. > > As for the uncombine option- don't wait for that appear. With the new > merging, that option is not possible. In new.familysearch.org all > information merged was kept in separate "little files" and so it was easy > to > uncombine or separate those files out. With the merge in Family Search- > there are no "little files" to easily separate out, only the selected > information is saved and put in one record/file. The unmerge button will > only appear until changes have been made in that newly created record. > Once > changes have been made, the computer doesn't know to which of the records > the changes apply.... so it cannot uncombine. The option is to make > separations manually. Here's a link to the white paper about how to > separate people who have been incorrectly combined in new.familysearch. > > http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ > pdf/familyTreeNotMyAncestorWhitepaper.pdf > The issue there still remains, that in creating a new person, the > ordinances > will show as available- and probably have already been done (multiple times > in some cases.) There is supposed to be a "Fix" in the works for an > ordinance assignment option, but it hasn't been released yet. > > If changes are well sourced and documented, it is hoped that others will > not > come back in and change those records. > > Dive into Family Tree- it really does have a lot of great options! Not > perfect, but I think superior to new.familysearch in the ability to really > correct errors! And sourcing, stories and photos are amazing! > Tammy Stevenson > ______________________________________________________ > Message: 3 > Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) > From: JCBrooks@aol.com > Subject: [LDS-WC] Delete button > To: lds-ward-consultant@rootsweb.com > Message-ID: <71b04.50d1a8db.3ed93902@aol.com> > Content-Type: text/plain; charset="US-ASCII" > > Is anyone as concerned as I am about the delete button? We should be > merging first before deleting as I believe ordinances could well be lost. > Plus > there is so much disagreement in some families, particularly non-LDS lines, > about research. Frankly Family Tree is embarrassing to me when I look at > what a mess they and others have made of simple pure, well documented > families. > > Like others, I am waiting until they straighten out more before I spend any > great amount of time fixing things. It is so frustrating and we only have > half the tools. Uncombining is sure more important than delete!! > > Michele > ______________________________________________________________ > > > > 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 >
David's point about cleaning up our family lines on Family Tree is right on target. The other day I was working on Family Tree and looking at some of my husband's families, particularly the Tanner families from Payson, Utah. Earlier that day I had read an LDS biographical sketch about a sister in a newly published book. The sister's husband had married several women before the Manifesto. They lived in some of the areas where my husband's family had lived. One of his daughters married a man with the surname of Tanner. I went on Family Tree and wanted to see how this daughter was related to my husband. As I looked at the records for the various Tanner branches, I was amazed at the inconsistencies and inaccuracies which are there. For instance, the information about John Tanner (the early convert to the Church who gave a substantial amount of money for the Kirkland Temple to Joseph Smith) needed immediate attention. (John Tanner never lived in Payson but his third wife and many of his children did.) John Tanner's mother was Thankful Tefft but Family Tree had Thankful also as the wife of John. (Terrible error and not one to let carry down to people who might not know the difference. It needed to be corrected immediately and appropriate explanations added.) The family relationships were certainly in need of careful examination and correction. With my husband's approval, I started the process of correcting these relationships. As I told my husband, we will need to look at every one of his family lines because there are probably changes which need to be made for many family members. My husband isn't that keen on family history but if we don't do these changes who will? If not now, when? Are we going to wait for our children and unborn grandchildren to be interested? It might not happen. I think now is the time and it is a task which we can do while we are able to do so. As I used to tell my family history classes, we can work on one family at a time. Straighten it out, add sources and notes, check ordinances, merge if necessary, etc. We don't have to attack the entire tree but only these smaller twigs in a methodical way. When we feel one family is in order, than we can move to another family. Besides, as we work on Family Tree, we can address issues and offer insights or feedback. Thanks for listening. I learn a lot from each of you. Mary Scott Aurora, Illinois
The delete button caution says: "It is recommended that you delete people only if you added a person by mistake or if the person never existed." I think that is a good option because I have seen where people have added names and information in by mistake before really searching and verifying the person (and listing the wrong person/information)- only then to figure out they made a mistake and can't figure out how to get rid of that wrong person once they figure out the right person. Additionally it should be helpful in deleting out the people listed with the incorrect gender- as one cannot merge individuals of different genders. As for the uncombine option- don't wait for that appear. With the new merging, that option is not possible. In new.familysearch.org all information merged was kept in separate "little files" and so it was easy to uncombine or separate those files out. With the merge in Family Search- there are no "little files" to easily separate out, only the selected information is saved and put in one record/file. The unmerge button will only appear until changes have been made in that newly created record. Once changes have been made, the computer doesn't know to which of the records the changes apply.... so it cannot uncombine. The option is to make separations manually. Here's a link to the white paper about how to separate people who have been incorrectly combined in new.familysearch. http://broadcast.lds.org/eLearning/fhd/Community/en/FamilySearch/FamilyTree/ pdf/familyTreeNotMyAncestorWhitepaper.pdf The issue there still remains, that in creating a new person, the ordinances will show as available- and probably have already been done (multiple times in some cases.) There is supposed to be a "Fix" in the works for an ordinance assignment option, but it hasn't been released yet. If changes are well sourced and documented, it is hoped that others will not come back in and change those records. Dive into Family Tree- it really does have a lot of great options! Not perfect, but I think superior to new.familysearch in the ability to really correct errors! And sourcing, stories and photos are amazing! Tammy Stevenson ______________________________________________________ Message: 3 Date: Thu, 30 May 2013 19:21:38 -0400 (EDT) From: JCBrooks@aol.com Subject: [LDS-WC] Delete button To: lds-ward-consultant@rootsweb.com Message-ID: <71b04.50d1a8db.3ed93902@aol.com> Content-Type: text/plain; charset="US-ASCII" Is anyone as concerned as I am about the delete button? We should be merging first before deleting as I believe ordinances could well be lost. Plus there is so much disagreement in some families, particularly non-LDS lines, about research. Frankly Family Tree is embarrassing to me when I look at what a mess they and others have made of simple pure, well documented families. Like others, I am waiting until they straighten out more before I spend any great amount of time fixing things. It is so frustrating and we only have half the tools. Uncombining is sure more important than delete!! Michele ______________________________________________________________
Is anyone as concerned as I am about the delete button? We should be merging first before deleting as I believe ordinances could well be lost. Plus there is so much disagreement in some families, particularly non-LDS lines, about research. Frankly Family Tree is embarrassing to me when I look at what a mess they and others have made of simple pure, well documented families. Like others, I am waiting until they straighten out more before I spend any great amount of time fixing things. It is so frustrating and we only have half the tools. Uncombining is sure more important than delete!! Michele In a message dated 5/30/2013 2:49:04 P.M. Pacific Daylight Time, dsam52@sampubco.com writes: do not hold off from Family Tree. Do it there now. Family History Centers already shut off instant access to nFS for at least 2 months. Many features are not working in nFS now. You can not separate any record in nFS. This feature was shut off. There are many reasons to do in Family Tree now rather than in nFS. Non-LDS has access now to Family Tree, while can not have access to nFS And in Family Tree, there are far more duplicate records you can NOT find in nFS but are there. Family Tree, you can make quick fixes. Watch List is now linked to Family Tree, no longer linked to nFS. There are many more reasons to do it in Family Tree. David Samuelsen On 5/30/2013 2:33 PM, Gay Davis wrote: > Thanks, Miles. I will enter the basic data in NFS today and then redo the sources, etc. in Family Tree as I get a chance. I am holding off working with Family Tree very much because it is so problematic and I am hoping more of the bugs will be worked out soon. Also, I guess I have just resisted learning a whole new software when I feel competent in NFS. I am getting old (78) and don't have time for this (but I guess I will have to make time). > > Gay Davis 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
read the fine print about use of delete button. It won't delete right away. It will pop up the caution first. You need to get in! I am NOT keen on cleaning up the mess on your lines because you won't. Even the General authorities are getting in to do their cleaning up in FT rather than waiting for others. I should know because I have been in contact with one of them who share lines with me. David Samuelsen On 5/30/2013 5:21 PM, JCBrooks@aol.com wrote: > Is anyone as concerned as I am about the delete button? We should be > merging first before deleting as I believe ordinances could well be lost. Plus > there is so much disagreement in some families, particularly non-LDS lines, > about research. Frankly Family Tree is embarrassing to me when I look at > what a mess they and others have made of simple pure, well documented > families. > > Like others, I am waiting until they straighten out more before I spend any > great amount of time fixing things. It is so frustrating and we only have > half the tools. Uncombining is sure more important than delete!! > > Michele > > > In a message dated 5/30/2013 2:49:04 P.M. Pacific Daylight Time, > dsam52@sampubco.com writes: > > do not hold off from Family Tree. Do it there now. > > Family History Centers already shut off instant access to nFS for at > least 2 months. > > Many features are not working in nFS now. > > You can not separate any record in nFS. This feature was shut off. > > There are many reasons to do in Family Tree now rather than in nFS. > > Non-LDS has access now to Family Tree, while can not have access to nFS > > And in Family Tree, there are far more duplicate records you can NOT > find in nFS but are there. > > Family Tree, you can make quick fixes. > > Watch List is now linked to Family Tree, no longer linked to nFS. > > There are many more reasons to do it in Family Tree. > > David Samuelsen > > > On 5/30/2013 2:33 PM, Gay Davis wrote: >> Thanks, Miles. I will enter the basic data in NFS today and then redo > the sources, etc. in Family Tree as I get a chance. I am holding off > working with Family Tree very much because it is so problematic and I am hoping > more of the bugs will be worked out soon. Also, I guess I have just > resisted learning a whole new software when I feel competent in NFS. I am getting > old (78) and don't have time for this (but I guess I will have to make > time). >> >> Gay Davis > > 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 >
Correct - they are working on a way to get the notes transferred over from nFS but that hasn't happened yet. The Sources for FamilySearch are a separate part which allows you to link documents from the Record Search and other websites directly to your person, similar to the way Ancestry links records to people with the shaky leaves. The Reasons are attached to individual data that you change. For example, if you change someone's birth date it will ask for the reason that you made that change and why you believe it is correct. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Thu, May 30, 2013 at 3:16 PM, Gay Davis <grdavis@centurytel.net> wrote: > Miles, Let me see if I am understanding you. When I make entries or > changes in NFS, it will be carried over into Family Tree; however, Family > Tree may not pick up the sources or reasons. > > I have some reasons for working in NFS but rather than do the additions > twice--once in NFS and then again in Family Tree--I will switch to Family > Tree if that is necessary. Thx. > > Gay Davis > ----- Original Message ----- > From: Miles Meyer > To: lds-ward-consultant@rootsweb.com > Sent: Thursday, May 30, 2013 11:53 AM > Subject: Re: [LDS-WC] NFS > > > Yes, the affiliate programs still merge with nFS, except one which is now > merging with FamilyTree. If you are manually making changes you should > probably be working in FamilyTree to make sure the reasons and sources > are > added for each change. > > Miles Meyer > Jacksonville, FL > > "Unless someone like you cares a whole awful lot, nothing is going to get > better. It's not." - Dr. Seuss, The Lorax > > > On Thu, May 30, 2013 at 1:28 PM, Gay Davis <grdavis@centurytel.net> > wrote: > > > If we add new data to NFS, will it appear in Family Tree also? > > > > 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 >
do not hold off from Family Tree. Do it there now. Family History Centers already shut off instant access to nFS for at least 2 months. Many features are not working in nFS now. You can not separate any record in nFS. This feature was shut off. There are many reasons to do in Family Tree now rather than in nFS. Non-LDS has access now to Family Tree, while can not have access to nFS And in Family Tree, there are far more duplicate records you can NOT find in nFS but are there. Family Tree, you can make quick fixes. Watch List is now linked to Family Tree, no longer linked to nFS. There are many more reasons to do it in Family Tree. David Samuelsen On 5/30/2013 2:33 PM, Gay Davis wrote: > Thanks, Miles. I will enter the basic data in NFS today and then redo the sources, etc. in Family Tree as I get a chance. I am holding off working with Family Tree very much because it is so problematic and I am hoping more of the bugs will be worked out soon. Also, I guess I have just resisted learning a whole new software when I feel competent in NFS. I am getting old (78) and don't have time for this (but I guess I will have to make time). > > Gay Davis
I meant, Family Insight, not PAF insight. sorry. -----Original Message----- From: Cathe Taylor Sent: Thursday, May 30, 2013 12:04 PM To: lds-ward-consultant@rootsweb.com Subject: Re: [LDS-WC] Outages Remember that FamilySearch/Family Tree may be down and new.familysearch may be up. Paf insight is updating from new.familysearch, not Family Tree. -----Original Message----- From: JCBrooks@aol.com Sent: Thursday, May 30, 2013 11:26 AM To: lds-ward-consultant@rootsweb.com Subject: Re: [LDS-WC] Outages It's working for me and I've also been using Family Insight for several hours to update a database without issue. Michele In a message dated 5/30/2013 10:20:47 A.M. Pacific Daylight Time, thomas.j.kemp@gmail.com writes: FamilySearch has been up/down for over an hour now - now its down and not coming back. Are there issues? Planned down time? Anyone know when the site will be back to normal? 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
Yes, the affiliate programs still merge with nFS, except one which is now merging with FamilyTree. If you are manually making changes you should probably be working in FamilyTree to make sure the reasons and sources are added for each change. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Thu, May 30, 2013 at 1:28 PM, Gay Davis <grdavis@centurytel.net> wrote: > If we add new data to NFS, will it appear in Family Tree also? > > 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 >
Thanks, Miles. I will enter the basic data in NFS today and then redo the sources, etc. in Family Tree as I get a chance. I am holding off working with Family Tree very much because it is so problematic and I am hoping more of the bugs will be worked out soon. Also, I guess I have just resisted learning a whole new software when I feel competent in NFS. I am getting old (78) and don't have time for this (but I guess I will have to make time). Gay Davis Hansville, Washington ----- Original Message ----- From: Miles Meyer To: lds-ward-consultant@rootsweb.com Sent: Thursday, May 30, 2013 1:17 PM Subject: Re: [LDS-WC] NFS Correct - they are working on a way to get the notes transferred over from nFS but that hasn't happened yet. The Sources for FamilySearch are a separate part which allows you to link documents from the Record Search and other websites directly to your person, similar to the way Ancestry links records to people with the shaky leaves. The Reasons are attached to individual data that you change. For example, if you change someone's birth date it will ask for the reason that you made that change and why you believe it is correct. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Thu, May 30, 2013 at 3:16 PM, Gay Davis <grdavis@centurytel.net> wrote: > Miles, Let me see if I am understanding you. When I make entries or > changes in NFS, it will be carried over into Family Tree; however, Family > Tree may not pick up the sources or reasons. > > I have some reasons for working in NFS but rather than do the additions > twice--once in NFS and then again in Family Tree--I will switch to Family > Tree if that is necessary. Thx. > > Gay Davis > ----- Original Message ----- > From: Miles Meyer > To: lds-ward-consultant@rootsweb.com > Sent: Thursday, May 30, 2013 11:53 AM > Subject: Re: [LDS-WC] NFS > > > Yes, the affiliate programs still merge with nFS, except one which is now > merging with FamilyTree. If you are manually making changes you should > probably be working in FamilyTree to make sure the reasons and sources > are > added for each change. > > Miles Meyer > Jacksonville, FL > > "Unless someone like you cares a whole awful lot, nothing is going to get > better. It's not." - Dr. Seuss, The Lorax > > > On Thu, May 30, 2013 at 1:28 PM, Gay Davis <grdavis@centurytel.net> > wrote: > > > If we add new data to NFS, will it appear in Family Tree also? > > > > 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
It's working for me and I've also been using Family Insight for several hours to update a database without issue. Michele In a message dated 5/30/2013 10:20:47 A.M. Pacific Daylight Time, thomas.j.kemp@gmail.com writes: FamilySearch has been up/down for over an hour now - now its down and not coming back. Are there issues? Planned down time? Anyone know when the site will be back to normal? 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
FamilySearch has been up/down for over an hour now - now its down and not coming back. Are there issues? Planned down time? Anyone know when the site will be back to normal?
Miles, Let me see if I am understanding you. When I make entries or changes in NFS, it will be carried over into Family Tree; however, Family Tree may not pick up the sources or reasons. I have some reasons for working in NFS but rather than do the additions twice--once in NFS and then again in Family Tree--I will switch to Family Tree if that is necessary. Thx. Gay Davis ----- Original Message ----- From: Miles Meyer To: lds-ward-consultant@rootsweb.com Sent: Thursday, May 30, 2013 11:53 AM Subject: Re: [LDS-WC] NFS Yes, the affiliate programs still merge with nFS, except one which is now merging with FamilyTree. If you are manually making changes you should probably be working in FamilyTree to make sure the reasons and sources are added for each change. Miles Meyer Jacksonville, FL "Unless someone like you cares a whole awful lot, nothing is going to get better. It's not." - Dr. Seuss, The Lorax On Thu, May 30, 2013 at 1:28 PM, Gay Davis <grdavis@centurytel.net> wrote: > If we add new data to NFS, will it appear in Family Tree also? > > 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
Remember that FamilySearch/Family Tree may be down and new.familysearch may be up. Paf insight is updating from new.familysearch, not Family Tree. -----Original Message----- From: JCBrooks@aol.com Sent: Thursday, May 30, 2013 11:26 AM To: lds-ward-consultant@rootsweb.com Subject: Re: [LDS-WC] Outages It's working for me and I've also been using Family Insight for several hours to update a database without issue. Michele In a message dated 5/30/2013 10:20:47 A.M. Pacific Daylight Time, thomas.j.kemp@gmail.com writes: FamilySearch has been up/down for over an hour now - now its down and not coming back. Are there issues? Planned down time? Anyone know when the site will be back to normal? 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
up and down and up up at 11:55 am MDT David Samuelsen On 5/30/2013 11:12 AM, Thomas Jay Kemp wrote: > FamilySearch has been up/down for over an hour now - now its down and not > coming back. > > Are there issues? Planned down time? > > Anyone know when the site will be back to normal? > > 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 >
We did that last year with our ward Relief Society and it was a huge success. Everyone got excited about indexing. Several laptops were loaned for the evening, and we used the FHC for the evening also. Joan in NC On Sun, May 26, 2013 at 6:32 PM, Terri Jaskolka <tjaskolka@gmail.com> wrote: > Do you have wifi available? Can people bring laptops? Do you have access to > enough computers? > > I would try to make it a hands-on workshop. Show the videos, then get > everyone registered and give them a chance to try out a batch. You might > want some experienced helpers for when people have questions, as well. > > If you are not able to have the hands-on session, then I would make a > presentation about what indexing is, and what it is doing. Give the big > picture about how all these records can be made available online for all > through the help of those participating. Emphasize that it is an aspect of > family history that anyone can do, especially those who think their work is > all done, or "Aunt Matilda is doing it, there's nothing I need to do". Give > some examples of how much more complete (and accurate) a family record can > become by tying an image to someone on Family Tree (1940 Census would be a > good choice, that record could be attached to a whole family, for example). > > There is a nice Quick Start Guide here: > > http://broadcast.lds.org/eLearning/fhd/Product/en/handouts/FamilySearch_Indexing_Getting_Started.pdf > > but it's 30 pages and might be too much for a handout for all. > > -Terri J. > > > On Sun, May 19, 2013 at 3:09 PM, Nancy Gibert <nlgibert1@ameritech.net > >wrote: > > > Has anyone done a class on Indexing? My relief society wants to do an > > evening class teaching about indexing. I haven't done it in a while. I > > have seen a couple of short videos on family search. > > Any suggestions for a class? > > Thanks > > Nancy in MI > > > > > > > > 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 >
I was using FamilySearch without any issues; went to reserve names for ordinance work and the site stopped working. --- On Thu, 5/30/13, JCBrooks@aol.com <JCBrooks@aol.com> wrote: From: JCBrooks@aol.com <JCBrooks@aol.com> Subject: Re: [LDS-WC] Outages To: lds-ward-consultant@rootsweb.com Date: Thursday, May 30, 2013, 10:26 AM It's working for me and I've also been using Family Insight for several hours to update a database without issue. Michele In a message dated 5/30/2013 10:20:47 A.M. Pacific Daylight Time, thomas.j.kemp@gmail.com writes: FamilySearch has been up/down for over an hour now - now its down and not coming back. Are there issues? Planned down time? Anyone know when the site will be back to normal? 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