Re: [LegacyUG] Hinting for FamilySearch Individuals/content
Hi Cathy, Are you stilly officially involved with or are giving help freely. If that is so thank you for the wonderful help you gave to all of us, really appreciated. Regards Douglas TIGHE in sunny Queenskand Sent from my iPhone > On 9 Feb 2022, at 05:33, B Akin wrote: > > Thank you very much Cathy for your time and effort in replying. It is very > helpful! > >I've also spent some time in the Help section for L-FS Integration tool. > Between help and your reply, I have a better understanding. Maybe even of the > numbers...104 "new matches/links" since last matching, 299 "old > matches/links", 1741 "old" not matched now less the 104 "new matches-new > links" yields the 1637 "not matched" and 403 (299+104) linked now shown in > L-FS when I play with the current filter pull down menu. >Agreed, I will have to go through the auto-matched (double yellow arrows) > and convince myself that the matching makes sense. >Also, I found I can "see" the Legacy FS ID in the bottom left corner of > the L-FS main screen under the details tab. > Again, Thanks Cathy for you help. > B. Akin > > > > On 2/7/2022 8:56 PM, Cathy Pinner wrote: >> B Akin, >> >> The FamilySearch hints have always only been available for people with a FS >> ID. FamilySearch hints record hints to the FamilySearch tree and those hints >> are sent on via the Hinting API. Whether or not they are accepted or >> rejected or whatever terms FS uses is not whether you've accepted them - >> maybe the term is confirmed - but whether someone using the FS tree has. >> >> When you use the Legacy FamilySearch Integration module, any time you >> confirm that the FS tree person found is your person, the FS ID is added to >> your person in Legacy. That's the only thing transferred. You have total >> control over other data both ways. >> >> If you have used Auto Match in LFS you'll have yellow arrows. You need to >> check each one and unlink if it's found the wrong person. Some people find >> it highly accurate and others, like me, highly inaccurate. It depends on >> your family and perhaps where you live in the world. If you go person by >> person you may have a better success rate - and you may as well as you >> should check the auto matched people. >> Or you may want to search on the website if it doesn't auto find the match >> and then enter the found FS ID in Legacy. There have been some recent issues >> with the matching via LFS. >> I only attempt to link a group at a time and use the filters to get just the >> ancestors or descendants of someone using the Edit button in the Left pane. >> When you match someone you can use the chain links to link their surrounding >> relatives to their equivalent in the FS tree. They show blue when already >> linked or just a grey shadow when not. >> >> No one should be duplicated in the FamilySearch tree but in reality there >> are heaps of duplicates - many created by FS themselves as they added things >> like Parish Register transcriptions into the tree. This means that if >> someone had 12 children baptised and were themselves baptised and married, >> they are in the tree 14 times. Those 14 need to be merged by someone - and >> the spouse also probably has at least 14 duplicates that need to be merged >> and each child is duplicated multiple times ... It's a big job that I've >> only tackled for some of my direct ancestors. You can merge in LFS though I >> find it easier to merge on the website - but it still takes hours. I >> screenshot or write down the FS ID of each child at least as I have too >> often found I've orphaned children and they need to be reconnected. The >> FamilySearch help has guidance on how to do all this. Merging duplicates is >> far easier than undoing incorrectly merged and linked people. I did have a >> win this week. I messaged someone around Christmas as I found they had my >> Matilda Harris born in London, marrying in Ohio in 1850, having a child in >> Canada in 1851 whereas I knew she was single in London in the 1851 census >> and still single in London in 1871. They've sorted it out. >> >> So no you don't enter more than one person or more than one FS ID in Legacy. >> You do the work to merge the duplicate instances in the FS tree. If you are >> not sure they are duplicates, then obviously you don't merge. In that case >> you may want to enter the possible duplicate as a separate person in Legacy >> in order to record your research to find out. >> >> You can see in Legacy who has a FS ID entered by going to Search > Find > >> Detailed Search and doing this search. >> Individual > FamilySearch ID > not equal to > >> OR by going to Legacy FamilySearch and using the filters in the left pane to >> choose just those linked to FS. >> >> I think your different numbers suggest that some people were already linked >> and the auto-matching added another group. >> >> Note only you can see yourself on FamilySearch. Li
Re: [LegacyUG] Hinting for FamilySearch Individuals/content
Douglas – are you part of the TIGHE family connected to BINION’s ? Cheers from Valerie Garton nee Vaughan in sunny Sydney From: LegacyUserGroup On Behalf Of Douglas James Tighe Sent: Wednesday, 9 February 2022 8:23 PM To: Legacy User Group Subject: Re: [LegacyUG] Hinting for FamilySearch Individuals/content Hi Cathy, Are you stilly officially involved with or are giving help freely. If that is so thank you for the wonderful help you gave to all of us, really appreciated. Regards Douglas TIGHE in sunny Queenskand Sent from my iPhone On 9 Feb 2022, at 05:33, B Akin mailto:ba...@rochester.rr.com> > wrote: Thank you very much Cathy for your time and effort in replying. It is very helpful! I've also spent some time in the Help section for L-FS Integration tool. Between help and your reply, I have a better understanding. Maybe even of the numbers...104 "new matches/links" since last matching, 299 "old matches/links", 1741 "old" not matched now less the 104 "new matches-new links" yields the 1637 "not matched" and 403 (299+104) linked now shown in L-FS when I play with the current filter pull down menu. Agreed, I will have to go through the auto-matched (double yellow arrows) and convince myself that the matching makes sense. Also, I found I can "see" the Legacy FS ID in the bottom left corner of the L-FS main screen under the details tab. Again, Thanks Cathy for you help. B. Akin On 2/7/2022 8:56 PM, Cathy Pinner wrote: B Akin, The FamilySearch hints have always only been available for people with a FS ID. FamilySearch hints record hints to the FamilySearch tree and those hints are sent on via the Hinting API. Whether or not they are accepted or rejected or whatever terms FS uses is not whether you've accepted them - maybe the term is confirmed - but whether someone using the FS tree has. When you use the Legacy FamilySearch Integration module, any time you confirm that the FS tree person found is your person, the FS ID is added to your person in Legacy. That's the only thing transferred. You have total control over other data both ways. If you have used Auto Match in LFS you'll have yellow arrows. You need to check each one and unlink if it's found the wrong person. Some people find it highly accurate and others, like me, highly inaccurate. It depends on your family and perhaps where you live in the world. If you go person by person you may have a better success rate - and you may as well as you should check the auto matched people. Or you may want to search on the website if it doesn't auto find the match and then enter the found FS ID in Legacy. There have been some recent issues with the matching via LFS. I only attempt to link a group at a time and use the filters to get just the ancestors or descendants of someone using the Edit button in the Left pane. When you match someone you can use the chain links to link their surrounding relatives to their equivalent in the FS tree. They show blue when already linked or just a grey shadow when not. No one should be duplicated in the FamilySearch tree but in reality there are heaps of duplicates - many created by FS themselves as they added things like Parish Register transcriptions into the tree. This means that if someone had 12 children baptised and were themselves baptised and married, they are in the tree 14 times. Those 14 need to be merged by someone - and the spouse also probably has at least 14 duplicates that need to be merged and each child is duplicated multiple times ... It's a big job that I've only tackled for some of my direct ancestors. You can merge in LFS though I find it easier to merge on the website - but it still takes hours. I screenshot or write down the FS ID of each child at least as I have too often found I've orphaned children and they need to be reconnected. The FamilySearch help has guidance on how to do all this. Merging duplicates is far easier than undoing incorrectly merged and linked people. I did have a win this week. I messaged someone around Christmas as I found they had my Matilda Harris born in London, marrying in Ohio in 1850, having a child in Canada in 1851 whereas I knew she was single in London in the 1851 census and still single in London in 1871. They've sorted it out. So no you don't enter more than one person or more than one FS ID in Legacy. You do the work to merge the duplicate instances in the FS tree. If you are not sure they are duplicates, then obviously you don't merge. In that case you may want to enter the possible duplicate as a separate person in Legacy in order to record your research to find out. You can see in Legacy who has a FS ID entered by going to Search > Find > Detailed Search and doing this search. Individual > FamilySearch ID > not equal to > OR by going to Legacy FamilySearch and using the filters in the left pane to choose just those linked to FS. I think your different num
Re: [LegacyUG] Hinting for FamilySearch Individuals/content
Valerie. A friend of mine has Tighe ancestors from Ireland and/or Scotland if that's any help. On Wed, 9 Feb 2022 at 10:23, wrote: > Douglas – are you part of the TIGHE family connected to BINION’s ? > > > > Cheers from Valerie Garton nee Vaughan in sunny Sydney > > > > *From:* LegacyUserGroup *On > Behalf Of *Douglas James Tighe > *Sent:* Wednesday, 9 February 2022 8:23 PM > *To:* Legacy User Group > *Subject:* Re: [LegacyUG] Hinting for FamilySearch Individuals/content > > > > Hi Cathy, > > > > Are you stilly officially involved with or are giving help freely. > > If that is so thank you for the wonderful help you gave to all of us, > really appreciated. > > > > Regards > > > > Douglas TIGHE in sunny Queenskand > > > > Sent from my iPhone > > > > On 9 Feb 2022, at 05:33, B Akin wrote: > > Thank you very much Cathy for your time and effort in replying. It is > very helpful! > >I've also spent some time in the Help section for L-FS Integration > tool. Between help and your reply, I have a better understanding. Maybe > even of the numbers...104 "new matches/links" since last matching, 299 "old > matches/links", 1741 "old" not matched now less the 104 "new matches-new > links" yields the 1637 "not matched" and 403 (299+104) linked now shown in > L-FS when I play with the current filter pull down menu. >Agreed, I will have to go through the auto-matched (double yellow > arrows) and convince myself that the matching makes sense. >Also, I found I can "see" the Legacy FS ID in the bottom left corner of > the L-FS main screen under the details tab. > Again, Thanks Cathy for you help. > B. Akin > > > On 2/7/2022 8:56 PM, Cathy Pinner wrote: > > B Akin, > > The FamilySearch hints have always only been available for people with a > FS ID. FamilySearch hints record hints to the FamilySearch tree and those > hints are sent on via the Hinting API. Whether or not they are accepted or > rejected or whatever terms FS uses is not whether you've accepted them - > maybe the term is confirmed - but whether someone using the FS tree has. > > When you use the Legacy FamilySearch Integration module, any time you > confirm that the FS tree person found is your person, the FS ID is added to > your person in Legacy. That's the only thing transferred. You have total > control over other data both ways. > > If you have used Auto Match in LFS you'll have yellow arrows. You need to > check each one and unlink if it's found the wrong person. Some people find > it highly accurate and others, like me, highly inaccurate. It depends on > your family and perhaps where you live in the world. If you go person by > person you may have a better success rate - and you may as well as you > should check the auto matched people. > Or you may want to search on the website if it doesn't auto find the match > and then enter the found FS ID in Legacy. There have been some recent > issues with the matching via LFS. > I only attempt to link a group at a time and use the filters to get just > the ancestors or descendants of someone using the Edit button in the Left > pane. When you match someone you can use the chain links to link their > surrounding relatives to their equivalent in the FS tree. They show blue > when already linked or just a grey shadow when not. > > No one should be duplicated in the FamilySearch tree but in reality there > are heaps of duplicates - many created by FS themselves as they added > things like Parish Register transcriptions into the tree. This means that > if someone had 12 children baptised and were themselves baptised and > married, they are in the tree 14 times. Those 14 need to be merged by > someone - and the spouse also probably has at least 14 duplicates that need > to be merged and each child is duplicated multiple times ... It's a big job > that I've only tackled for some of my direct ancestors. You can merge in > LFS though I find it easier to merge on the website - but it still takes > hours. I screenshot or write down the FS ID of each child at least as I > have too often found I've orphaned children and they need to be > reconnected. The FamilySearch help has guidance on how to do all this. > Merging duplicates is far easier than undoing incorrectly merged and linked > people. I did have a win this week. I messaged someone around Christmas as > I found they had my Matilda Harris born in London, marrying in Ohio in > 1850, having a child in Canada in 1851 whereas I knew she was single in > London in the 1851 census and still single in London in 1871. They've > sorted it out. > > So no you don't enter more than one person or more than one FS ID in > Legacy. You do the work to merge the duplicate instances in the FS tree. If > you are not sure they are duplicates, then obviously you don't merge. In > that case you may want to enter the possible duplicate as a separate person > in Legacy in order to record your research to find out. > > You can see in Legacy who has a FS ID entered by going to S
