Sync FS Ordinances and Sources with new or current RM10 Tree
After creating a new RM10 Tree using Ancestry.com, Using Family Search Central (Automatch feature), All new records are matched with FS, and then the records are analysed for LDS Ordinance actions but the individual records are not updated, you can then individually update the LDS Ordinance section one record at a time.
Need to be able to automatically update all the LDS Ordinances and sources in the same way as we do to automatch the people records to FS records…
Currently you must update the LDS Ordinaces section one ancestor at a time.
Currently you must update Sources section one FS source record pre ancestor at a time.
With over 100 trees and several hundred ancestors to keep current, keeping these trees current requires more time than is available.
Using the current RM10 Publishing option, the reports require to have all the ordinance and sources to reflect the FS information,
There limitation that FamilySearch has on the FT API given us. Most is in order to prevent duplication and to limit server demand. The LDS ordinances will import if you use the import option on FamilySearch Central. That would need to be done in a new blank database. Then it would require a drag n drop and merging afterwards. With an existing database ordinances can only be added one person at a time. All that can be updated when you leave the FS Central screen open is the ordinance status. Source are just limited to adding one person and source at a time.
A challenge of synching ordinances implied by @drwkolob is that there isn’t a clean sync option like there is with other events. You can copy the ordinances, or copy all of the ordinances, but you can’t replace an existing ordinance with a more complete ordinance or an updated ordinance. When an ordinance is copied, it creates a second event. If you only one want to record one ordinance, you then have to edit the individual and delete the extraneous ordinances. (Unless I’m missing something…is there a better way to do this?)
No, that’s correct. We can only add ordinances. That is partly why I discourage people from adding blank ordinances with those old temple ready statuses. From the FT API it will only add and not overwrite. The more duplicates are merged on FamilySearch the more the official dates will change. It would be a personal preference if you want to keep different ordinance dates in your database or not. At some point I just leave what I have over what FS is saying today, especially when my date is earlier.
It would be fairly simple to add a feature to address this. Even though the FT API only allows add, RM could then check to see if an ordinance already exists in the RM record on the backend and give the user a chance to replace an existing ordinance or merge similar ordinances (to capture things like notes and sources). It would also be useful to have a tool which would do a wholesale check for duplicate ordinances and give the user a chance to replace or merge them. There could be configuration choices to select things like your favorite (and mine) to keep the oldest ordinance.
Confirming request has been reported to development.