Genealogical Data Standards (RootsTech Session)Edit This Page
From FamilySearch Wiki
Attendees are invited to add notes of their own. A big "thank you" is due Pat M. for being our session scribe.
|Attribution||When data is copied, credit is copied with it|| |
|Data in proprietary format||
|Ease of use||i.e. data re-entry|| |
|Persistent URL's||Average life is 100 days|| |
|Guidance||for new users|| |
|Tag & link||
|Research process||Evidence should be an independent class like persons, families, and sources.|| |
|Inconsistent search experience||
|Transfer rich data||Photos, sources, scanned documents. Embedded or linked. Metadata in jpeg.|| |
|Inability to do cross-repository search||Lack standard metadata or exposure.||2|
|Documentation||Sources, citations. Automatic, user assisted, transferring, ...||1, 3|
|Key as seen||(Representation). To surface in search results, the data must be standardized. Error rates for interpretation.||1|
|Static data interchange||GEDCOM standard not updated by FamilySearch.||1|
- Data interchange. Exchange uninterpreted data linked with standardized data.
Governance of a standard can be provided by:
- a vendor,
- a consortium of vendors,
- an existing standards body, or
- a new organization or community.
Perhaps a community led governance body started and assisted by FamilySearch would be appropriate.
Some issues might best be solved at different levels or by different groups.
Robert Gardner of Google volunteered to help any vendors who want Google to index the content that is only accessible with a subscription. His contact information is:
Robert D. Gardner, Ph.D.
Software Engineer 19540 Jamboree Road
Irvine, CA 92612
Share Your Opinion!
Give feedback on our new look! Tell us what you like, and what you would do differently.Give Feedback