@Nick-Hall, I would be very much interested in being involved in this project as well as I think it would be very useful for Gramps Web.
3 Likes
(Fun fact, I applied for several in-person lectures at RootsTech next year and they were all rejected - I took it as a hint that FS folks see Gramps as competition. Good to see this doesnāt seem to be the case.)
1 Like
I am currently investigating our options.
Yes. I will continue my discussion with Gordon. There seems to be enough interest.
2 Likes
I would welcome any integration!
1 Like
I would appreciate some kind of ability to (a) capture information from the FamilySearch catalog when Iām looking at an image, and (b) create a source with that information.
Hereās an example. Suppose Iām looking at this image. The Information tab at the bottom of the screen gives me a link to the Catalog Record, an Item Number (not present in this case, though I think it ought to be ā1ā), and Film/Digital Note. Following the link to the catalog record, I can get further details such as author and publication information.
Currently I copy and paste details from the catalog record into a new source in Gramps, like this:
Of course, every user of Gramps will have different preferences for which information to store in which fields. So ideally there could be some kind of dialog in which I could say what I want to go where, and perhaps some of those decisions could be saved as defaults.
But if it doesnāt improve my accuracy or productivity as compared to the manual copying and pasting, then it wouldnāt be worth it.
1 Like
Nick, Thanks for kicking off this thread. The response is great. I will study and summarize the responses. In looking at an integration, itās important to learn what Gramps has the FamilySearch.org doesnāt and vice-a-versa. Iāve been the Strategic Opportunities Manager at FamilySearch for many years. I started the API, the developers conferences and was the first co-chair for Rootstech. I need to learn more about Gramps and itās users. Gramps users need to learn more about FamilySearch offerings:
FamilySearch API - https://developers.familysearch.org
FamilySearch GEDCOM 7 - https://gedcom.info
FamilySearch CET - [CET] API Guide
I will continue on this thread to learn more about the Gramps community and to share more about integration opportunities with the Gramps community.
6 Likes
The tool could be designed to push and/or pull after finding a matching person if the user agrees to the activity.
3 Likes
The CET options make it possible to manage and sync with a separate tree while useing hints from FamilySearch Family Tree only as you want.
4 Likes
FamilySearch Controlled Edit Tree [CET]
1 Like
We have many individuals signing up to use FamilySearch API. Each organization that uses the GRAMPS code would sign up separately and get a separate AppKey.
The reason the Gramps developer would have to sign an agreement is to assure FS that the tool would not abuse their serviceā¦ to not suck vast amounts of bandwidth, becoming a costly burden. There are other requirements about perpetuating the transparency of data copyrights and credits.
The Gramps organization would need to have an agreement to distribute such plugins through the Addon Manager. Weād have to agree to be good stewards and protect their rights the same way we push certains coding standards. If any FS API features were to be rolled into the core, that also would require abiding by such an agreement.
emyoulation is correct. Sending out e-agreements for access to FamilySearch API is a very common practice.
2 Likes
If this is going to proceed, may I suggest that a review of the enhancers currently pending be done that would enhance this feature, like adding a separate and dedicated URL field in the Citation screen. This would give a specific location for the citation URL to be copied to.
4 Likes
Yes. Iāll review any existing feature requests that may make the integration better.
1 Like