Jump to content


Photo

Update on FT API Issue with Matching/UnMatching Records

FT Family Tree API Issues match unmatch

  • Please log in to reply
7 replies to this topic

#1 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8446 posts

Posted 16 July 2013 - 04:59 PM

We have confirmation that FamilySearch has identified the issue with their last FT API update causing the Matching/UnMatching issues inside of RootsMagic.

FamilySearch has (for now) turned off their caching on the Family Tree API (which is where the bug is). With the caching turned off, it will stop "unmatching" people in RootsMagic.

People that were unmatched in RootsMagic due to this issue with the FT API will still not be able to be re-matched right now.

RootsMagic will be releasing an update later this week to resolve this problem. Under Database Tools the Phantom Records option will include the ability to clean the affected records. Once the affected records are cleaned you will be able to re-match them to a person on FT again.
Renee
RootsMagic

#2 Jerry Bryan

Jerry Bryan

    Advanced Member

  • Members
  • PipPipPip
  • 3566 posts

Posted 16 July 2013 - 05:39 PM

This is a speculative question rather than being based on anything I've experienced. But I have wondered what would happen if I have matched somebody in RM with somebody in FSFT, and if subsequently another FSFT user merges or deletes the matched individual out of existence on the FSFT side of the match. Presumably, in this situation there would now be a different individual on the FSFT side of the house with whom RM should now be matching. How is the resynchronization between RM and FSFT designed to work in this situation? Is this the same situation as the problem that is being described by many users at the present time with matching/unmatching records?

Just curious,
Jerry

#3 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8446 posts

Posted 17 July 2013 - 01:25 PM

No, what you are describing is a different scenario. If your RM person is matched to someone on FT and then that person is merged into another person, changing the ID, then the next time you open the FS Person Tools it should update it with the new ID.

On the other hand is someone came along and deleted the person on FT that you were matched to then when you open up FS Person Tools it will bring back a 404 error. That error message from FS is not very informative so people don't always know it means the person it's trying to sync to on FT has been deleted. You have to UnMatch your RM person and re-match them to someone else on FT.
Renee
RootsMagic

#4 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8446 posts

Posted 17 July 2013 - 05:12 PM

Update 6.3.0.0 - 17 July 2013
  • New: Added Problem Alerts
  • Enhanced: Added code to Database Tools > Clean phantom records to clean up issues with FamilySearch Family Tree links
  • Fixed: A number of small bugs
If you experienced having anyone in your database UnMatched from a recent FT API bug and you can not re-match them, then go to File>Database Tools and run the "Clean Phantom Records" option after you install the new update.

If you had previously tried to rematch them after the FT API UnMatched them, you will discover that those matches are now re-established. If you hadn't attempted to re-match them earlier you will need to go back now and match them again.
Renee
RootsMagic

#5 Ludlow Bay

Ludlow Bay

    Advanced Member

  • Members
  • PipPipPip
  • 868 posts

Posted 17 July 2013 - 07:54 PM

Update 6.3.0.0 - 17 July 2013

  • New: Added Problem Alerts
  • Enhanced: Added code to Database Tools > Clean phantom records to clean up issues with FamilySearch Family Tree links
  • Fixed: A number of small bugs
If you experienced having anyone in your database UnMatched from a recent FT API bug and you can not re-match them, then go to File>Database Tools and run the "Clean Phantom Records" option after you install the new update.

If you had previously tried to rematch them after the FT API UnMatched them, you will discover that those matches are now re-established. If you hadn't attempted to re-match them earlier you will need to go back now and match them again.


Say a person has 5,000 matched records, and the FT API has unmatched a few. How would one identify them?

#6 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8446 posts

Posted 17 July 2013 - 08:13 PM

Under File>FamilySearch Central near the bottom is a link for "Not Matched". It will bring up the FamilySearch Person Tools with a sidebar index to work through the people that are not Matched to anyone in FT.
Renee
RootsMagic

#7 Ludlow Bay

Ludlow Bay

    Advanced Member

  • Members
  • PipPipPip
  • 868 posts

Posted 18 July 2013 - 08:46 AM

Under File>FamilySearch Central near the bottom is a link for "Not Matched". It will bring up the FamilySearch Person Tools with a sidebar index to work through the people that are not Matched to anyone in FT.


I'm not asking for a "Not Matched Because I Haven't Gotten To Them Yet" list, but for an "UnMatched Because Somebody Screwed Up" list.

#8 Renee Zamora

Renee Zamora

    Advanced Member

  • Support
  • PipPipPip
  • 8446 posts

Posted 18 July 2013 - 09:38 AM

There isn't anyway for RootsMagic to generate an "UnMatched Because FamilySearch Screwed Up" list.
Renee
RootsMagic