Remonter

Brother's Keeper, Évaluation du NGS par rapport à Gedcom

Évaluation de Brother's Keeper version 6 par rapport à la norme Gedcom par la National Genealogical Society en 2001.

19 décembre 2004 la page est à https://www.ngsgenealogy.org/ngsgentech/projects/TestBook2001/frame.htm

En février 2007 à https://www.ngsgenealogy.org/ngsgentech/projects/TestBook2001/bk6sum.cfm

Voici une reproduction intégrale.

Brother's Keeper 6.0.53 Summary

Export

Data export problems:

The GEDCOM GEDCHK report found 2 syntax error, 6 tag exceptions, and 5 extension tags.

The syntax errors were:

1: GEDC tag and its subordinate tags VERS (version) and FORM (lineage linked) did not appear in the header as required.

2: The SUBM (submitter) tag did not appear in the header as required.

The tag exceptions included the following:

1: A NOTE under FAM/SLGS/ SOUR appeared at the third level instead of second.

2: The CAUS (cause of death) was not subordinated to an event and as a result was at the wrong level.

3: SOUR (source) and QUAY (quality) tags were subordinated to a CAUS tag. This is not allowed .

4: The ADDR (address) tag was not subordinated to an event and as a result was at the wrong level.

The five extensions are:

Conclusion:

Brother's Keeper does not support all the possible Gedcom tags and in at least two cases is using extended tags when regular tags might be used. It provides users with a fixed list of tags that forces users to use a miscellaneous event tag for unsupported events. Selecting the individual event option codes the data using the miscellaneous Gedcom tag, EVEN. It does not make provision for the user to specify the type of event so unless the user makes an entry in the notes the event type will be unknown and confused with other miscellaneous events. The above mentioned extended tags are probably not a complete listing as the Testbook data set does not require an entry for over 20 of the items in the preloaded event list.

It does not export the media type or call numbers although it has fields for them. Witness information is similarly ignored.

Another potential problem occurs when the six tags below that placed the description in the location fields try to export the place information in those fields. The information will be misplaced by most programs. This is a user error and not a program fault.

Export rating: 92.32 %

GEDCOM imports:

Control GEDCOM

Problems in the control file import of facts were as follows:

Brother's Keeper did not recognize the following tags but did place the information in the exception list.

The following tags were recognized but failed to record all the information due to lack of fields.

Failed to pickup 2nd level note. Data in exception list.

Brother's Keeper did not recognize the following tags and did not record the data in the exception list. (data lost)

Failed to pickup zero level note, recorded reference number only.

Problems with source input:

When the PROP tag was not recognized and the data sent to the exception list the sources linked to that data were also not imported.

Media information was lost.

Call numbers were lost.

Notes linked by a reference code, e.g. zero level notes were lost.

Repository addresses using the CITY, STAE and POST tags placed information in the exception list.

Summary:

Failure to recognize the TYPE tag when used as a subordinate tag to EVEN for miscellaneous events could lead to the requirement of extensive editing of an imported file. The exception list, while indicating the individual to which the exception applies, fails to identify the event in many cases leaving the user to figure it out as best they can. The lost information, including those notes falling in this category, will have to be recovered from the imported Gedcom file.

Import rating: 69.30 %

 
The Gedcom Testbook Project
© Gentech 2001
Last Updated 22 August 2001

mwl

Au besoin Cliques ici pour m'envoyer un courriel.

Dernière modification : 24 décembre 2018.