The GEDCOM TestBook Project

FGS2000

Beau Sharbrough

The GEDCOM TestBook Project

A clearinghouse for the exchange of family history information between programs using GEDCOM

Where can you go to find out Where can you go to find out what information can be what information can be exchanged between your exchanged between your program and another?program and another?

Don’t worry. Take your time. Don’t hurry.

Where can you go to find out what problems other users are having similar to yours?

Can you see me at all?

What space contains the combined knowledge of the community of genealogical computer users that I can explore?

Please listen. You don’t know what you’re missin’.

Project Team Project LeaderProject Leader

User VolunteersUser Volunteers StorytellersStorytellers

The Participants Project Leaders:

2/3/96-1/25/97 Larry Ledden 1/25/97-1/31/00 Beau Sharbrough 1/31/00- Evan L Ivie

Story Tellers: 1/25/97- Robert C Anderson 1/25/97-6/1/99 Bob Booth

The process includes four steps

Entering the story Exporting the story Importing the story Reporting the results

A given volunteer might only do the last two steps, or anything else they think reasonable.

The world is at your command.

Entering the story

Entering the sources and the information from the story into your program

Equal parts content and method in this recipe

Maybe I’m Amazed that any communication takes place at all

Exporting the story

creating a GEDCOM file creating a register report sending the GEDCOM file to

testbook@gentech.org GENTECH volunteers post the file

on the GENTECH website

Importing the story

Bringing the information from a GEDCOM file into your program

NOTE: Be sure you don’t do this in your real data set.

Files can be downloaded from the website – They’re sitting perfectly still.

Reporting the results

Creating another GEDCOM file

Creating another register report

Any comments that you might have

Use the GENTECH website as a clearinghouse

The story Stored GEDCOMs Stored Reports

General observations

The types of errors encountered ran in patterns depending on the product reviewed.

All products had problems. Nearly all products could cleanly read a

GEDCOM file generated by that product.

Not all products gave an import problem report.

Test Conditions

Test was conducted over a three-month period. The same test specifications were used for all

testing. The test volunteers were not familiar with all

products (learning curve). The testers were supported by computer

professionals to answer questions as needed. The testers were not genealogy or computer

professionals, but rather experienced amateur genealogists.

Disclaimer

Although the test specifications were clear and used for all testing, variations were possible.

It is very possible that mistakes were made, and that specific problems were not problems at all, but only misunderstanding product functions

Types of problems encountered

Input error log page count from 0 to 8 pages

GEDCOM statements not recognized

Named individuals became individuals with no names

Married individuals became married to "Unknown Person"

Marriage information added for unmarried

person Death information added where not present

before

Event types were changed to a different but related type

Event type changed to miscellaneous

Second marriage event added for nearly all individuals

Lost certain common event types (baptism,

birth, death)

Lost everything except the names and relationships

Pieces of a locality string lost

LDS temple names changed

Order of children changed

Lost source references

Lost sources

Lost source text (full transcription of test problem)

Lost note references

Lost marriage connection

Lost parent connection

lost dates and/or places of some or all events

Lost special events only

Lost endnotes

Administrative action date added to genealogical reports

The Future Formation of a clearinghouse for specific

information about exchange issues. “SPR” Site

Opportunities to adopt "standard" approaches to problems

Communicate with developers about the needs of the marketplace, promote verndor certification.

Opportunities for improvement are Here, There, and Everywhere.

Summary

The project needs volunteers The information gathered will be

freely available for anyone If you’re worried that you won’t be

able to find the results, relax – you

have a Ticket to Ride.