Jump to content


Photo

Automatching using Web Hints


  • Please log in to reply
4 replies to this topic

#1 pbooth99

pbooth99

    Advanced Member

  • Members
  • PipPipPip
  • 43 posts

Posted 31 May 2019 - 05:50 AM

The FamilySearch functionality is more stable on the Windows version of Rootsmagic and that's what I am referring to here. One of the interesting Rootsmagic settings is the one to automatically add FamilySearch webhints for people. I can take an old ancestry tree with, say, 10000 people and the FamilySearch -> Automatch function might match say 2000 people. But with this other setting set as I navigate my tree, or step through the list of people, it checks FamilySearch with what is a more forgiving/less conservative criteria and slowly increases the number of matches.

At first I tried to click the down arrow repeatedly to step through and automate this process, but it became tedious.

 

Eventually  I downloaded a windows app that records macros to press certain keystrokes, that have a hot key attached to them. So I can open my partially matched Rootsmagic tree, select the first persion in the person list, then, when I press the <cntrl><Windows>j keystroke, the app simulates me rpessing downarrow, waiting two seconds, then pressing again, in a loop with 10,000 iterations. Six hours later this navigation is complete and I have another 2500 matches (say). It's convenient, but would be great to have this functionality be . a part of the product.

 

Step 2 - if I am lucky, matching someone with FamilySearch.org means that I want to add the familysearch record for that person, their spouse, heir children, their parents, etc. Typically this means a lot of clicking, I'd love to be able to accept a match with a single click an dget the person, spouse, and kids.

 

Alternate workflow. It is possible, though it wasn't immediately obvious, to add a person and their ancestors from familysearch.orb by specifying their familysearch ID. This isn't always stable or consistent. In some  cases boldly saying "50 generations of ancestors" will get me in a loop where someone has connected my family member to an FDP (FamousDeadPerson) and instead of adding 200 or 600 people I will see 30,000 people or more added over a day or longer, that goes well before 1000AD into the woods of the familysearch.org dataset. This is fascinating from the perspective of statistics, large datasets, pedigree collapse, data quality, graph traversal but I suspect it's also fantasy.

 

If computing power becomes ultimately free, how will we be doing this in 20 years?



#2 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8414 posts

Posted 31 May 2019 - 09:09 AM

You mention you're doing this with Automatching using WebHints. There is an AutoMatch on the FamilySearch Central dashboard. It will run through everyone in the database and if a high enough match it will connect them to someone on FamilySearch. This is a lot faster then trying to do it through WebHints, where it only looks at the people displayed on the screen. 

 

Go to File>FamilySearch Central to open the dashboard and login. Then click on AutoMatch. It can be stopped and restarted as needed. 


Renee
RootsMagic

#3 Kamolga

Kamolga

    Advanced Member

  • Members
  • PipPipPip
  • 69 posts

Posted 12 June 2019 - 07:10 AM

There is an AutoMatch on the FamilySearch Central dashboard.

 

I think this is what pbooth99 meant by 

 

 

I can take an old ancestry tree with, say, 10000 people and the FamilySearch -> Automatch function might match say 2000 people.


Rootsmagic 7.5.9.0 with a lot of SQL queries (SQLiteSpy) and a bit of Family Historian 6.2 (tree view and map)


#4 pbooth99

pbooth99

    Advanced Member

  • Members
  • PipPipPip
  • 43 posts

Posted 29 June 2019 - 09:36 AM

I think this is what pbooth99 meant by 

 

 

Yes, you're right. For some reason the matching criteria used used in this FamilySearch Central dashboard is stricter than the criteria used with WebHints. So in the example given the dashboard will match about 2000 people (very approximate) whilst webhints will match another 2000.



#5 Jerry Bryan

Jerry Bryan

    Advanced Member

  • Members
  • PipPipPip
  • 3535 posts

Posted 29 June 2019 - 10:47 AM

Remember that no matter how you do your FamilySearch hints, what's really going on behind the scenes is pretty convoluted. A person in your RM database is being conditionally matched against a person in FamilySearch Family Tree. A record in FamilySearch has already been conditionally matched against a person in FamilySearch Family Tree. So there are two conditional matches to be considered, not one. Either conditional match can be correct and either conditional match can be incorrect.

Ultimately what you are being asked to approve or reject is the conditional match that already exists between a record in FamilySearch and a person in FamilySearch Family Tree. This second conditional match actually has nothing to do with RM. So for example, you rationally could choose to approve the second conditional match that's totally within FamilySearch even if the first conditional match between your person in RM and the person in FamilySearch Family Tree is not correct. And you could equally rationally chose to reject the second conditional match that's between a record in FamilySearch and a person that's in FamilySearch Family tree even if your person in RM is a match with the person in FamilySearch Family Tree.

 

A specific example of an interesting problem with this kind of situation was recently discussed at http://forums.rootsm...ts-really-work/

 

The trickiest situation is when the conditional match between RM and Family Tree is incorrect and the conditional match between the FamilySearch record and FamilyTree is correct. There is no way to approve or reject the first conditional match. You can only approve or reject the second conditional match. In this case, you really need to approve the second conditional match but then RM is going to show you hint as if it is correct for your person in RM when in fact it is not.

 

Jerry