1. The GEDCOM TestBook Project FGS2000 Beau Sharbrough

2. The GEDCOM TestBook Project A clearinghouse for the exchange of family history information between programs using GEDCOM

3. Where can you go to find out what information can be exchanged between your program and another? Don’t worry. Take your time. Don’t hurry.

4. Where can you go to find out what problems other users are having similar to yours? Can you see me at all?

5. 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’.

6. Project Team n Project Leader n User Volunteers n Storytellers

7. The Participants n Project Leaders:  2/3/96-1/25/97 Larry Ledden  1/25/97-1/31/00Beau Sharbrough  1/31/00-Evan L Ivie n Story Tellers:  1/25/97-Robert C Anderson  1/25/97-6/1/99Bob Booth

8. The process includes four steps n Entering the story n Exporting the story n Importing the story n Reporting the results

9. A given volunteer might only do the last two steps, or anything else they think reasonable. The world is at your command.

10. Entering the story n 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

11. Exporting the story n creating a GEDCOM file n creating a register report n sending the GEDCOM file to testbook@gentech.org n GENTECH volunteers post the file on the GENTECH website

12. Importing the story n Bringing the information from a GEDCOM file into your program n 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.

13. Reporting the results n Creating another GEDCOM file n Creating another register report n Any comments that you might have

14. Use the GENTECH website as a clearinghouse n The story n Stored GEDCOMs n Stored Reports

15. General observations n The types of errors encountered ran in patterns depending on the product reviewed. n All products had problems. n Nearly all products could cleanly read a GEDCOM file generated by that product. n Not all products gave an import problem report.

16. Test Conditions n Test was conducted over a three-month period. n The same test specifications were used for all testing. n The test volunteers were not familiar with all products (learning curve). n The testers were supported by computer professionals to answer questions as needed. n The testers were not genealogy or computer professionals, but rather experienced amateur genealogists.

17. Disclaimer n Although the test specifications were clear and used for all testing, variations were possible. n It is very possible that mistakes were made, and that specific problems were not problems at all, but only misunderstanding product functions

18. 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

19. The Future n Formation of a clearinghouse for specific information about exchange issues. “SPR” Site n Opportunities to adopt "standard" approaches to problems n Communicate with developers about the needs of the marketplace, promote verndor certification. Opportunities for improvement are Here, There, and Everywhere.

20. Summary n The project needs volunteers n 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.