elderamevans / familysearch-gramps Goto Github PK
View Code? Open in Web Editor NEWPoiggles - WIP plugin for GRAMPS-FamilySearch integration
License: BSD 2-Clause "Simplified" License
Poiggles - WIP plugin for GRAMPS-FamilySearch integration
License: BSD 2-Clause "Simplified" License
Discussion Write compliant applications can list, create, update, and delete discussions and related comments.
The following items are required as specified in order for your application to obtain Discussion Write Certification.
https://familysearch.org/developers/docs/certification/read
Read certification applies to applications that access FamilySearch resources in order to analyze, visualize, share, and publish the information. This includes reading information about persons, relationships, memories, photos, stories, documents, sources, discussions, and change history.
The following checkbox items are required as specified in order for your application to obtain Read Certification.
Important! Each type of read operation listed below must be certified independently. Read certification for one type of read operation does not certify your app for any other type of read operation.
(Me interjecting here: I'm hoping for all to be eventually checked off.)
I'm now undecided:
Should we use folders, or branches, to separate each GRAMPS version?
I know I've set up branches, but I'm feeling that it may complicate things in the long run....
It seems like the next step for integrating Gramps with FS is to write functions to go back and forth between Gramps and FS. Gramps has two serialized forms:
person.serialize()
. This is the internal format stored in the database.person.to_struct()
. This is used for queries and diffs, etc.The second form may be easier to deal with, especially as time goes on, because it can be immune to some variance in the data format.
Likewise, you can create an object from either form. In the serialized case, you need to construct the all parts exactly (Person.create(data)
where data is a tuple-based form). I believe that the JSON-like format will fill in default values (Person.create(Person.from_struct(data))
where data is a JSON-like struct).
So, I suggest methods that can take a FS result and convert it to a Gramps struct, and a Gramps struct and convert to FS JSON.
https://familysearch.org/developers/docs/certification/sources
Sources Write applications give users the following capabilities.
The following features are required for your application to obtain each of the three Source Write certifications.
Note: To update, delete, and detach sources requires Tree Write Certification
Options
See the results of additions and attachments in FamilySearch in order to edit, or undo.
OK, I realize this may not be the best channel for all, but it's currently the best one for me...
I've got the repo. I've got a good number of GRAMPS devs I can talk to. I've (somewhat) got the coding skills. I've got a bit of time. I've got a fully-functional FamilySearch-Python SDK. It sounds like we're going to get the get-go approval, even if it's only read-only access at first.
What I lack are a solid gameplan and a grasp of PyGObject (or whatever GRAMPS uses for its GUI).
I can throw some ideas as edited screenshots in here.
I've currently slapped the BSD license on the repo, but I'm more than willing to change it to GPL.
(As a side note: The reason I chose BSD for the SDK is to allow it to be compatible with the GPL, yet allow other developers to, if there's some agreement between FamilySearch/boss/school/whatever that requires the app that integrates with FamilySearch.org to be closed-source, it's available. A bit of a compromise, I know, but I felt it necessary.)
I don't know if I'll be able to contribute code any time soon, but expect some screenshots soon!
Sorry if this is not the right place to post this question, but can this be used to import FamilySearch Trees to Gramps, now? Is it ready to be used? If so, how do I use it? Didn't see anything on the wiki..
Thanks.
https://familysearch.org/developers/docs/certification/authentication
The following checkbox items are required as specified in order for your application to obtain Authentication Certification.
https://familysearch.org/developers/docs/certification/memories
Memories Write applications give users the following capabilities:
The following features are required for your application to obtain each of the three Memories Write certifications.
[ ] Read certified using at least one Memories read API.
[ ] Upload Memories certified.
[ ] Edit the titles and descriptions of memories they created.
[ ] Create personas of people in the tree on memories that they created.
[ ] Create comments to memories.
[ ] Edit Memories certified.
[ ] Delete memories that they created.
[ ] Delete personas that they created (detach from a person in the tree).
[ ] Delete memory comments.
The following capabilities are not requirements, but you can include them:
FamilySearch.org accepts the following file formats or types (note that the maximum file size is 15 MB):
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.