Genealogical Data Standards (RootsTech Session): Difference between revisions

From FamilySearch Wiki
mNo edit summary
(Add transcriptions of the photographs)
Line 1: Line 1:
'''Session notes for an open discussion moderated by the Ancestry Insider, held at the [[RootsTech_2011|RootsTech 2011 Conference]].'''
'''Notes from an open discussion moderated by [[User:AncestryInsider|the Ancestry Insider]], held at the [[RootsTech 2011|RootsTech 2011 Conference]].'''  


The promised information is coming soon.
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 &amp; 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>

Revision as of 12:33, 14 February 2011

Notes from an open discussion moderated by the Ancestry Insider, held at the 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.

Issues
[edit | edit source]

Issue Notes Group
Governance

Attribution When data is copied, credit is copied with it
Privacy

Data in proprietary format
2
Ease of use i.e. data re-entry
Persistent URL's Average life is 100 days
Guidance for new users
Unstructured Text
1
Tag & link
2
Research process Evidence should be an independent class like persons, families, and sources.
Inconsistent search experience
2
Data versioning

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

Groupings[edit | edit source]

  1. Data interchange. Exchange uninterpreted data linked with standardized data.
  2. Searchability
  3. Documentation/Sources

Governance[edit | edit source]

Governance of a standard can be provided by:

  1. a vendor,
  2. a consortium of vendors,
  3. an existing standards body, or
  4. 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[edit | edit source]

Google[edit | edit source]

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
Suite 200
Irvine, CA 92612
rgardner@google.com