Sources Write - Githubissues

Sources Write Certification Checklist

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.

[ ] Read Certified
[ ] Use the Sources API resource calls to read and create sources to persons.
[ ] When creating a source, give the user the option to enter the following information. Only the Title is required for the source to be saved.
Title (required)
URL
Citation
Notes
Attach Sources Certification
[ ] Create Sources Certified
[ ] Use the Sources API resource to attach sources to persons
[ ] When attaching a source to a person, allow the user the following options.
Enter search parameters or person ID to find and select the person to attach sources to.
View the person Name, person ID, birth date, birthplace, death date, death place, parents names, and spouses names if available in the results of the search.
Set event tags such as name, gender, birth, christening, death, and burial for the source.
Enter a reason that the source is valid. Reasons are not to be used to promote the partner or partner products.
[ ] User Interface Requirements are to make interfaces substantially similar to the following:
Search for Family Tree persons ID
Associate a Person or Artifact in a Third-Party Application with a Person in FamilySearch Family Tree
Read and View Sources Contributed by the Authenticated User
View Sources through FamilySearch Family Tree Person Page
Create a Source
Attach an Existing Source to a Person
Update Source Certification

Note: To update, delete, and detach sources requires Tree Write Certification

[ ] Attach Sources Certified
[ ] Edit Sources
[ ] Detach Sources
[ ] Delete Sources
[ ] Compare Sources
[ ] Mechanisms in place to prevent duplication and preserve data integrity.
Prevent duplication of a Source on the same partner-FT connected Persons - The Partner tracks the SrcID while on this Partner person. The partner app should capture the SrcID when they copy an FT Source or Create a Source
Preserve the Source data integrity - Capture Source conclusions and SrcRef Reason and tags.
Maintain connected Person/Source integrity - So before a partner user can edit a Source that came from FT on that connected Person, the user must see the current FT Source values.
When a Partner creates a new FT Person - any Sources created are attached to that FT Person. Those Sources have no dup issues on a new Person.
At the point of connecting Person between FT and Partner (not from an Add Person workflow) no Sources flow across to FT. The user can push-pull to attach specific Sources. A connected Person that has a subsequent Source attached/detached on the FT side may or may not show up as the Partner Person side.

Options

If you pre-populate the reason, make users aware of where and how to explain a reason if they decide to change it. See the results of additions and attachments in FamilySearch in order to edit, or undo.
Create, access and otherwise manage source boxes.
When Creating a Source for a previously created memory, enable the following:
- Search and view all memories that were contributed by the current user.
- Create a source using an uploaded photo or document by using the Memory module API resources. See the how to for Create Source With Memories example.
- Allow the user to enter a source title, citation, and note by using the Source Descriptions API resources. See the Create Source Description example.