A question about future 3rd party integrations.
Will the CET tree be able to talk to multiple platforms the way the FS tree does? Or will each CET be tied to a single software platform?
Currently, I have trees on Ancestry, Legacy and RootsMagic. All of these are able to send data back and forth to the main FamilySearch Tree. They are all out of sync with each other and used for various purposes, but I would love to have a central place to eventually collate the info from each platform. I try with the FS tree but it's a bit too changeable to rely on. Having a single CET for all my good research and then slowly synching across to the main FS tree as needed is the goal here.
Answers
-
FamilySearch has no specific business objectives to control what software can access a tree programmatically. However, the system is built to provide the software developers with control over the read&write communications to the tree created from their clients in order to meet their business needs. All authorized users in a tree (ie Owner, Co-owners and Contributors) can always access the tree on FamilySearch. Developers can choose to limit remote access to a tree to either JUST the owner/creator of the tree, or they can allow all authorized tree members to have remote access. Developers can choose to restrict remote access to the tree created from their product to JUST software clients from their company, or they can choose to allow any integrated software clients to read and write to the tree.
Currently all committed software vendors have chosen to build their future integrated versions to allow maximum tree availability to all authorized users and all integrated software clients.
Here is the story form of what that will mean for you once these software products are released: The owner of a tree that is maintained on their desktop in software product A (SP-A) launches their software and authenticates to FamilySearch from within the product. They push a button and the software reaches out over the internet and tells FamilySearch to create a new CET. The software then populates that CET with all the data from the desktop and alerts the user when the new CET is complete and ready. The Owner comes to their new CET on FamilySearch and extends invitations to the research colleagues they trust to help build the tree. Once these accept the invitation and become members of that CET, they can launch their chosen software product, which may be SP-A or SP-B or SP-C. They will authenticate with FamilySearch and ask the software to call and get a list of the CETs they have access to. They choose the new CET they just joined and the software will pull that CET into their desktop database. From that point forward, the owner can make a change to the tree in SP-A which will sync to the CET on FamilySearch. That change will then sync out to the various connected software products of all the authorized tree members. Same for the authorized users. Of course there may be some future vendors who might require that all authorized users use the same software client or that access is limited to only the tree creator.It is not a FamilySearch role to speak to the development commitments and progress of any 3rd party company. Most leading software will likely integrate and many are doing so now. For details you should inquire with the developer of your chosen software product.
1 -
@Susie O'Neil Thank you for your feedback. It is valuable in the development of CET but also in educating and helping other CET users.
0
