9
edits
No edit summary |
No edit summary |
||
Line 15: | Line 15: | ||
==== FamilySearch Person Centric System introduces a Modern Linking Model. ==== | ==== FamilySearch Person Centric System introduces a Modern Linking Model. ==== | ||
FamilySearch is a person centric system. Each person listed in the indexed historical records collections has their own unique persistant archial link (URL) or person source and hense thier own | FamilySearch is a person centric system. Each person listed in the indexed historical records collections has their own unique persistant archial link (URL) or person source and hense thier own unique web page. Linking a person source, or page, from the historical records to a conclusion person in the Family Tree is the manner by which a research tells the system that the two people are the same. This system allows FamilySearch to account for each individual recorded in the records more accurately than does the ambiguous linking of images, which may contain many unspecified indivuals. | ||
<br> | |||
Each historical records person source is stored in the GedcomX data model which gives it deep internal awareness of it's person's data and relationships. It knows what vital data is present on the record and what that data means. It knows what relationships to other persons it's person has on the record and what those relationships mean. It knows what record (ex a census household record) it's person is found on, what image(s) that record is found on, and what collection the image is part of. In other words, if you link the person source in historical records to the Family Tree person you are simultaneously linking the record, the image, if available, and the collection since these are all associated with each other. | |||
<br> | |||
Historically computing systems and data models could not support such internal knowledge and many genealogists are used to creating one source for a record or image and then attaching it to multiple individuals. Since one page might contain from five to one hundred people, many might have the same source. If that old process is still followed in today's advanced system the resaercher would be telling the system that the single person source in historical records is the same person as all the persons in Family Tree to which it is attached. That would represent the addition of incorrect information to the Family Tree and should not be done. Please attach each person in the records to the proper corresponding person in the Family Tree.<br> | |||
<br> | |||
For example, with proper linking of persons in the records to persons in the Family Tree FamilySearch will be able to provide tools that: | This data model will enable the delivery of very helpful genealogical tools in the Family Search system. For example, with proper linking of persons in the records to persons in the Family Tree FamilySearch will be able to provide tools that: | ||
• Suggest that you link other individuals in the same record to corresponding relatives of the ancestor. So you extract all the info from a record. | • Suggest that you link other individuals in the same record to corresponding relatives of the ancestor. So you extract all the info from a record. | ||
Line 35: | Line 35: | ||
• Indicate who in a record or submitted tree still needs to be linked into FamilyTree. | • Indicate who in a record or submitted tree still needs to be linked into FamilyTree. | ||
• Optionally filter out linked-in individuals from search results for records | • Optionally filter out linked-in individuals from search results for records (i.e., in order for users to be able to focus on new information that hasn't already been assimilated into the tree yet). | ||
• Automatically know which conclusion types the source satisfies for a given ancestor (as well as what values it has for each conclusion type!) | • Automatically know which conclusion types the source satisfies for a given ancestor (as well as what values it has for each conclusion type!) | ||
Line 45: | Line 45: | ||
Most of these helpful features aren't possible if the people in the records are incorrectly linked to the people in the tree that aren't them. | Most of these helpful features aren't possible if the people in the records are incorrectly linked to the people in the tree that aren't them. | ||
<br> | |||
The above explanation is true only for FamilySearch, or 3rd party records, that are encoded in the new GedcomX data standard. At present (Oct 17 2013) only FamilySearch uses this model, but there is significant interest from other record keeping organizations. Source links created to external images, documents, etc that are NOT encoded in GedcomX will not have any of the rich internal knowledge. They consist of largely a URL, whatever titles and citation infor the user provides and little more. These external sources may need to be linked to multiple persons in the old manner. | |||
The above explanation is true only for FamilySearch, or 3rd party records, that are encoded in the new GedcomX data standard. At present (Oct 17 2013) only FamilySearch uses this model, but there is significant interest from other record keeping organizations. Source links created to external images, documents, etc that are NOT encoded in GedcomX will not have any of the rich internal knowledge. They consist of largely a URL, whatever titles and citation infor the user provides and little more. These external sources may need to be linked to multiple persons in the old manner. | |||
===== The following explains how to properly link a family in the FamnilySearch records. ===== | ===== The following explains how to properly link a family in the FamnilySearch records. ===== | ||
Line 55: | Line 55: | ||
<br> | <br> | ||
See Using the Source Box Master Copies for a suggestion as to how to create one record for each person in a source record that is not indexed. | See Using the Source Box Master Copies for a suggestion as to how to create one record for each person in a source record that is not indexed. | ||
=== Tips for organizing temple work === | === Tips for organizing temple work === |
edits