Reading the report card.
Import:
The control file is scored against the complete GEDCOM 5.5 grammar. Three points are awarded for the first use of a tag. Subsequent uses are not scored. After the control file is imported to a program, the exception list, if one is created, and the newly created database are evaluated to determine the accuracy of the transfer process. Three points are awarded for complete import, two points if editing is required, and one point if the tag is not recognized but if the data is imported regardless. One point is deducted if the data is not transferred but identified and recorded in the exception list. Two points are deducted if the data must be recovered from the GEDCOM file.
Export:
The program's GEDCOM file is scored against the complete grammar. Three points are allotted if the data transfers properly. One point is awarded if it transfers but requires editing. In the instance where a conflicting event or other name requires a tag be used again only a single point is awarded if the program transfers the data improperly. Two points are deducted for tag exceptions, syntax errors, cross reference errors or if a required descriptor is missing. Two points are deducted if an extended tag is used in place of a legitimate tag. All other extended tags are ignored for scoring purposes. Items known to be entered but that are not exported are assigned a negative two points but do not enter into the scoring.
The summary card has five columns each for import and export. They contain the following values:
Import:
Test file score.
Score achieved by the control file.
Gross score.
Sum of all positive values achieved by the program being tested.
Imp Gross %.
Ratio of Gross score to Test file score.
Net score.
Gross score less point deductions.
Imp Net %.
Ratio of Net score to Test file score.
Export:
Maximum total.
Score achieved by the GEDCOM file being tested.
Gross score.
Sum of all positive values achieved by the file being evaluated.
Exp Gross %.
Ratio of Gross score to Maximum total for the file being tested .
Net score.
Gross score less any deductions.
Exp Net %.
Ratio of Net score to Maximum total for the file being tested.
Evaluation.
Import:
A higher gross score indicates a more complete importation of the data. More tags have been recognized and the data will be less likely to require editing. A factor affecting the score other than tag recognition are the available fields for imported data in the receiving program. Fields may not be available or, if they are, the size is inadequate for the amount of data being transferred.
The net score indicates, to some degree, the effort required to recover the missing data from the exception list or Gedcom file. Many programs will place the exception information in a note field. This can simplify the editing process. On the other hand, data recorded to an exception list is very often out of context making it neccesary to go to the Gedcom file. Information that is not recorded to an exception list or notes is effectively lost although it can be recovered if the user is aware the information was transmitted. In a large Gedcom file this can be time consuming and require some skill using a text editor.
Export:
The maximum score is obtained by scoring the program's Gedcom file against the Gedcom grammar. The higher the score the better the program utilizes the full grammar. All programs are trying to record the same data. The simpler programs, having fewer options, will not record all the information, e.g. roles. It can also indicate the program fails to use all the available Gedcom tags. Most notable is the common usage of the miscellaneous tag, EVEN, for a variety of events that have legitimate tags available. All such information imported will require editing. Another possibilty is that the program does not export all the data recorded. This is the case with Ultimate Family Tree and, to a lesser extent, in several other programs.
The gross score indicates how well the program adheres to the Gedcom 5.5 specification. The higher the score the more likely the Gedcom will import properly into a program that scores well on import. A low gross score indicates a simplistic GEDCOM that probably doesn't take full advantage of the GEDCOM specification and whose data will probably require editing.
A low Exp Net score indicates a number of problems with the coding of the data in the GEDCOM file and that the user can expect problems when importing a file from that program.
Very often users view the exception lists produced by the various programs and mistakenly assume the fault lies with the Gedcom file being imported. This may or may not be the case. Some programs will actually read a file that has been miscoded and restore the data to the correct location. Others provide options for exporting files to specific programs to accommodate known problems. To complicate the situation the more modern programs provide so many options it is possible for two users with identical software, recording identical data , to do so in such a manner that they can create slightly different Gedcom files. Adding to the difficulties is the use by several developers of some portions of previous Gedcom specifications and, in one case, possible future specofications.
Given these conditions it is impossible to provide a precise evaluation of all the possible Gedcom transfer combinations. It is hoped however that this scorecard will provide a general overview of what might be expected.