20
edits
Genealogical Data Standards (RootsTech Session): Difference between revisions
Genealogical Data Standards (RootsTech Session) (view source)
Revision as of 13:33, 14 February 2011
, 14 February 2011Add transcriptions of the photographs
mNo edit summary |
(Add transcriptions of the photographs) |
||
| Line 1: | Line 1: | ||
''' | '''Notes from an open discussion moderated by [[User:AncestryInsider|the Ancestry Insider]], held at the [[RootsTech 2011|RootsTech 2011 Conference]].''' | ||
Attendees are invited to add notes of their own. A big "thank you" is due Pat M. for being our session scribe.<br> | |||
=== Issues<br> === | |||
{| width="100%" cellspacing="1" cellpadding="1" border="1" | |||
|- | |||
! scope="col" | Issue | |||
! scope="col" | Notes | |||
! scope="col" | Group | |||
|- | |||
| Governance | |||
| <br> | |||
| <br> | |||
|- | |||
| Attribution | |||
| When data is copied, credit is copied with it | |||
| <br> | |||
|- | |||
| Privacy | |||
| <br> | |||
| <br> | |||
|- | |||
| Data in proprietary format | |||
| <br> | |||
| 2 | |||
|- | |||
| Ease of use | |||
| i.e. data re-entry | |||
| <br> | |||
|- | |||
| Persistent URL's | |||
| Average life is 100 days | |||
| <br> | |||
|- | |||
| Guidance | |||
| for new users | |||
| <br> | |||
|- | |||
| Unstructured Text | |||
| <br> | |||
| 1 | |||
|- | |||
| Tag & link | |||
| <br> | |||
| 2 | |||
|- | |||
| Research process | |||
| Evidence should be an independent class like persons, families, and sources. | |||
| <br> | |||
|- | |||
| Inconsistent search experience | |||
| <br> | |||
| 2 | |||
|- | |||
| Data versioning | |||
| <br> | |||
| <br> | |||
|- | |||
| Transfer rich data | |||
| Photos, sources, scanned documents. Embedded or linked. Metadata in jpeg. | |||
| <br> | |||
|- | |||
| 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 | |||
|} | |||
=== Groupings === | |||
#Data interchange. Exchange uninterpreted data linked with standardized data. | |||
#Searchability | |||
#Documentation/Sources | |||
=== Governance === | |||
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. | |||
=== Contact Information === | |||
==== Google ==== | |||
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: | |||
<blockquote>Robert D. Gardner, Ph.D.<br>Software Engineer 19540 Jamboree Road<br>Suite 200<br>Irvine, CA 92612<br>rgardner@google.com</blockquote> | |||