Exchange data between systems

LegacyUser

Arm Meladius said: Hello,
Years ago there was the possibility to use an API to query famillysearch, does it vanished?

When we put data on famillysearch, it is like putting it in another dimension.
First, it is a huge effort to add each person manually after the GED file import.
I had to click about 3800 times on "add"...

Second, you can't browse you data:
- I couldn't find a way to have a list of person in my tree
- I couldn't find a way to export the data in GED or CSV or XLSX

Third, after merging my data with existing persons, I couldn't find a way to identify if persons "unknown" to me (i.e. which were not in my GED file) were linked to a person I have in my tree...
I would be interested by such information, so I could identify these persons and then manually copy/paste the data to my genealogy software (to have it in my GED file)

Regards
Arm

LegacyUser

Tom Huber said: The API has changed over the years as new features were added to FamilySearch.

There are not separate trees, only an open-edit tree for all mankind where the goal is to have just one profile for each person that has ever lived. Living people are not included because of privacy laws throughout the world. If you enter a living person in FamilySearch FamilyTree, only you will be able to see it. Most of us suggest that you only use Living persons as placeholders to connect to your deceased ancestors in the massive tree.

Most of us have found that the GEDCOM import feature has been the source of many duplicate records. Testing revealed some major flaws in the system and so changes were introduced that took care of many of those flaws. Today, the difficulty in adding entries from an uploaded GEDCOM file are approaching something close to acceptable, except that the code (which was described as old and clunky by Ron Tanner) still has areas that need attention.

Most of us do not want to see GEDCOM files used as a source for adding new or changing existing profile information, since GEDCOM files seldom are sourced. Changes and entries need to be backed by reason statements and sources where available.

GEDCOM files are no longer being used as widely as they once were. There are options to integrate sites with each other under limited circumstances as well as using a fully certified family tree management program with FamilySearch FamilyTree. There are three and even the free versions offer a level of compatibility that didn't exist just a decade or so ago. The three programs are Ancestral Quest (which is most like the old PAF program - same author), Legacy, and Roots Magic (which also can interface with an Ancestry Tree). Only Legacy lacks a Mac-compatible version, but each has their fans and since all three have free versions, it is easy to download and install each so a person comparison can be made. But be aware that their user interfaces are not similar so switching between them can be a real challenge (not to switch, but to find similar features and then use them effectively).

A GEDCOM file is generated by a genealogical program (or in some instances, a site) and really needs to be imported into a local database under the control of a family tree management program.

To find the three programs and their various versions, use the Solutions Gallery (a link is at the bottom of this and most FamilySearch.org pages) and go from there.

LegacyUser

Arm Meladius said: Thank you Tom for your message.

I understand the goal on familysearch, have a person only once.

But, how do I know that a person was added or updated by somebody, who also is my ascendant and I would like to copy that information back in my genealogy program?

Can a generate a list of my ascendants? How?

Concerning the API, few years ago when I wanted to program a tool and requested a token ID, the response was that the site was changing and the API inscriptions were disabled until the new release.
There was also the API documentation on internet but I can't find it anymore.

LegacyUser

Lynne VanWagenen said: The partnering program and APIs have changed over the years. This is the developer site:

https://www.familysearch.org/developers/