FSDN conversations

1© 2014 by Intellectual Reserve, Inc. All rights reserved.

Recent FSDN ConversationsVaughn Hepworth

2

Server Issues and Down Time

. Sandbox has been up and down in the past, but with the move to a new environment, there seems to be a lot less downtime than before.

Additional testing support for modules such as Reservations

3

Changes to FSDN Announcements

. New, exciting features will be announced through a Marketing Campaign as well as FSDN

Business oriented announcements will be communicated the same way

We are looking for new ways to communicate technical vs non technical correspondence

4

Indexing Questions

. The new indexing program (to be released later this year) is being developed with a formal API layer separating the front-end applications from the back-end services.

We are using the API internally and it is being developed in such a way that it could be made available to third-party developers in the future, but we don’t currently have any immediate plans (or even a timeframe) for making it available publicly.

5

Bowtie API

. Part of the Ancestry endpoint

Allows you to bring back the children of the specified person as well as x number of ancestors

Person

Father

Mother

Grand Father

Grand Mother

Grand Father

Grand Mother

Child

Child

Child

6

110 Year Rule Changes

.

Anyone wanting to reserve ordinances for persons that were born within 110 years can no longer give an assertion that they have permission. They must now submit a ticket to our Support group to approve. Once approval is given, the reservation will be added to your list

Exceptions to this would be close relatives.

7

Living/Death Assertion

.

110 year rule for marking persons deceased.

If a death type event is sent, the person will get marked deceased. IE Burial, Cremation

Partner Application FS API

If there is no death type event, Family Search is no longer making assumptions about the status of a person. In the near future, applications must specify whether a person is living or dead.

Buried: Jan 9, 1832

Partner Application FS API

Success!

Failed!

8

Alternative Vital Events?

. FamilySearch FamilyTree is conclusionary. The goal is to have the community arrive at the best possible conclusion, of name, birth, relationships of our ancestors. While there is a desire to support Research and multiple opinions that is in the future.

One of the motivations for only having one birth, christening, death, burial is to drive conversations. If each person can enter their own opinion, then there will be no conversations to arrive at the most accurate information.

9

Hinting API

. The PID can be passed to the FamilySearch Hinting API to receive a list of historical records matching the vital and relationship data of that person.

FamilySearch provides a page where the user can review historical records and optionally attach them to the FamilySearch person.

10

ARKs & Redirects

.

ARKS are long lived Identifiers

FamilySearch maintains ARKs for:

Persons in the Family Tree Personas in the FamilySearch Historical Records Archive Records in the FS Historical Records Archive Artifacts (images or documents)

They can be read using the <Identifier> node

Supports some additional “decorations” or URI paramenters such as:

Details or the resource Change history of the resource Memories attached to the resource Ordinances associated with the resource Record hints for the resource Source Links of the resource

<identifier type="http://gedcomx.org/Persistent">https://familysearch.org/ark:/61903/4:1:KW8W-RF8</identifier>

11

Tagging and Sources

. FS Architects talk about 2 different types of sources. A persona source, like names in historical records, vs everything else, like images, web pages, etc. When dealing with persona sources, the recommended process is to attach each persona from the record to the person in the tree

Birth CertificateName: John Smith

Mother: Jane SmithFather: James Smith

John Smith

James Smith

Jane Smith

12

Tagging and Sources

. It knows which personas in a record are already attached to someone in the Family Tree (and are thus

"accounted for"), as indicated by "green" rows in the side-by-side record-to-tree record attach tool; and as indicated by showing "Review Attachments" vs. "Attach to Family Tree" on the record details page.

It can suggest "hints" and remember which ones have been attached (or, eventually, excluded, i.e., deemed "not a match").

It can help users create conclusions based directly on what the sources say. It can help users add new relatives into the tree based on what the sources say (which is one of the primary

ways many users now add new people to the tree).

Jane Smith

Marriage CertificateWife: Jane Smith

Husband: John Smith

John SmithInferred Marriage Relationship

13

Places 2.0

. New Functionality Allow users to search for all Cemeteries within A specified region(state) Find all Temples within 5 miles of a specific location Supports unauthenticated access tokens

14

User Change History

. New Endpoint that allows you to see the list of persons that the Current user has accessed

15

Questions?

.