FamilySearch Developer Webinar presented on March 14, 2017. For more information, go to http://familysearch.org/developers

1. 1© 2013 by Intellectual Reserve, Inc. All rights reserved.
March 14
Developer Webinar

2. 2
Agenda
• Delay in March Pending Modifications
• consolidate-redundant-resources (Q1 2018)
• full-descendancy (June 6, 2017)
• Deprecated OSS API to be retired June 6, 2017
• New Platform Ordinances API
• Sandbox environment to be retired
• New Features
• Persons resource update
• Families of a Person
• Geocoordinates for Places on Person

3. 3
Pending Modifications
• Release of incompatible changes
• Preview of API changes
- Available on Sandbox, Beta, and Production
environments
• Activated through X-FS-Feature-Tag header

4. 4
Pending Modifications
GET /platform/tree/persons/KWQS-BBQ
{headers}
X-FS-Feature-Tag: full-descendancy

5. 5
consolidate-redundant-resources

6. 6
consolidate-redundant-resources
• Release Date: Q1 2018
• Data embedded on the Person resource makes
other API resources redundant
• Consolidate with a 303 redirect
• Must be used with the
“include-non-subject…”

7. 7
consolidate-redundant-resources
• Affects:
- Persons with Relationships
- Spouse Relationships
- Child Relationships
- Parent Relationships
- Source References
- Discussion References
- Memory References

8. 8
consolidate-redundant-resources
• Link rels from Person removed:
- child-relationships
- parent-relationships
- person-with-relationships
- spouse-relationships

9. 9
consolidate-redundant-resources
• POSTs to create consolidated resources should
go to Person resource

10. 10
full-descendancy

11. 11
full-descendancy
• Release Date: June 6, 2017
• It will return all spouses for an individual and
children
• The descendancyNumber scheme is modified

12. 12
full-descendancy
• Release Date: June 6, 2017
• It will return all spouses for an individual and
children
• The descendancyNumber scheme is modified
June
6

13. 13
full-descendancy
descendancy number description
1 The root person.
1-S The (primary) spouse of the root person.
1-S2 The second spouse of the root person.
1.3 The third child (via the primary spouse) of the root person.
1-S2.2
The second child (via the second spouse)of the root
person.
1.2-S3.4
The fourth child (via the 3rd spouse) of the second child
(via the primary spouse) of the root person.
1.2.5-S
The primary spouse of the fifth child (via the primary
spouse) of the second child (via the primary spouse) of the
root person.

14. 14
full-descendancy
…
"names" : [ {
"nameForms" : [ {
"fullText" : "Roscoe Phillips”
} ]
} ],
"display" : {
"name" : "Roscoe Phillips",
"gender" : "Male",
"lifespan" : "1909-2000",
"descendancyNumber" : "1.1-S”
}
}, …

15. 15
Ordinances API – June 6
• Migrate to the Platform Ordinances API before
June 6 2017
• Access to /reservation/v1 or /oss/ will be shut
off

16. 16
Ordinances API – June 6
• Migrate to the Platform Ordinances API before
June 6 2017
• Access to /reservation/v1 or /oss/ will be shut
off
June
6

17. 17
Sandbox environment retirement
• Traffic still coming to sandbox environment
• Sandbox still available but resources are being
reallocated. New errors will appear.
• Verify that old code doesn’t still go to
sandbox.familysearch.org

18. 18
Persons resource update
• The Persons resource now supports the GET
method. This allows you to read a list of up to
500 persons.
GET /platform/tree/persons?pids=PPPJ-
MYZ,KWQB-H46

19. 19
Families of a Person
• New resource at
/platform/tree/persons/{pid}/families
• Returns the spouses, children, parents, siblings,
and the respective relationships of the
requested PID.

20. 20
Geocoordinates for Places on Person
• GIS data is now included with all places when
reading Persons and Relationships from the
Family Tree

21. 21
Geocoordinates – birth fact (description)
{
"id": "248eaba5-34ae-4182-9874-bfcc07166241", ...
"type": "http://gedcomx.org/Birth",
"date": {...},
"place": {
"original": "Aschhausen,Jagstkreis,Wuerttemberg",
"description": "#pd_49.371388x9.540555",
"normalized": [
{
"lang": "en-US",
"value": "Aschhausen, Jagstkreis, Württemberg, Germany”
}
]
}
}

22. 22
Geocoordinates – birth fact (lat / long)
"places": [
{
"id": "pd_49.371388x9.540555",
"latitude": 49.371388,
"longitude": 9.540555,
"names": [
{
"lang": "en-US",
"value": "Aschhausen, Künzelsau, Jagstkreis,
Württemberg, Germany”
}
]
}]

23. 23
Other new features…
• Genealogies API support for adding media
• Genealogies API support for querying by
external ID
• Support for Genealogies sources create,
update, delete
• Support for reading multiple persons’
ordinances with the Ordinances resource

24. 24
Questions?