| PERSON1 | JOSEPH TAG TORTURE
Comments on "Joseph Tag Torture" INDIVIDUAL Record. This record contains all possible types of data that can be stored in an INDIVIDUAL (INDI) GEDCOM record. Here are some comments on the data tested here and things to look for when this file is imported into any GEDCOM application: 1. This record has two NAME structures. How will a program handle this type of data which is allowed in GEDCOM? (Because some GEDCOM files get very bothered by a second name, the files TGC551.ged and TGC551LF files are identical to the TGC55.ged and TGC55LF.ged files except only one name structure is used for this individual - hence the "1" in their names). 2. The first NAME structure has all possible subordinate tags for a NAME structure including source and notes a source citation and some notes. The second NAME structure (when used) has a source citation and some notes. Are these all imported? 3. The Birth and Death events use all possible fields including subordinate tags, sources, multimedia links (in Birth), and notes. The birth data has an attached family link which is sometimes needed in case of ambiguous parentage. 4. This individual has two spouses. The links to the spouses have attached notes. 5. This individual has two sets of parents - natural parents and adoptive parents. Each parent link has attached notes. The adoptive parents has a subordinate pedigree (PEDI) tag. 6. This individual has all possible events (including a generic event or EVEN structure). The GEDCOM tags for the events are given in the TYPE tag of each event. Some comments are: a. The baptism record has all possible tags for event detail. b. There are 2 christening records to see how programs react to duplicate events (which are allowed). c. The adoption event has a family link to give more information about adoptive parentage. d. The cremation event (CREM) has no data except a "Y" in the first line to indicate that the event has occurred. The importing software should keep this event in this record even though it contains no data (The GEDCOM tag is not in this TYPE tag). e. The LDS Baptism event tests all possible detail tags for an LDS ordinance. f. The LDS confirmation has no data except a "Y" in the first line to indicate that the event has occurred. The importing software should keep this event in this record even though it contains no data. g. The date fields in the various events test the possible GEDCOM methods for expressing dates, approximate dates, date ranges, and interpreted dates. There are also a few Hebrew dates, French Republic dates. and "B.C" dates. 7. The residence structure use all possible subordinate tags in the address part of the residence. 8. This individual has all possible attributes. The GEDCOM tags for the attributes are given in the TYPE tag of each attribute. Some notes are: a. There are 2 occupation attributes to test how programs handle multiple tags of the same type (which is allowed). b. The first OCCU attribute uses all possible subordinate tags for an attribute. 9. This record has three note structures. The first is this set of notes which is in a separate NOTE record. The other two are NOTE structures embedded in the record. Are all imported and kept separate? Furthermore, the two embedded note structures have subordinate source citations. The second set of notes has a source citation to a SOURCE record and the third set of notes has an embedded source citation. 10. This record has three source citations. Two are citations to a SOURCE record; one is an embedded source citation (used in older GEDCOM files). 11. This record has one link to a multimedia file. For more testing of multimedia links, see the "Standard GEDCOM Filelinks," "Nonstandard Multimedia Filelinks," "General Custom Filelinks," and "Extra URL Filelinks" INDIVIDUAL records. 12. This individual has one alias and two associations. All possible tags in the first association link are used. 13. This record is linked to a submitter and to two submitters with interest in the ancestors and descendants of this individual. 14. This record has all remaining tags allowed in individual records for user reference number, record ID, record file number, ancestral file number, and the changed date. This is a second set of notes for this single individual record. It is embedded in the INDIVIDUAL record instead of being in a separate NOTE record. These notes also have a source citation to a SOURCE record. In GEDCOM this source can only be a single line and links to a SOURCE record.       |
Comments on "Mary First Jones" INDIVIDUAL Record. This record is used to provide the first wife to "Joseph Tag Torture." Not many other tags are used.  |
PERSON2 FAMILY1 
| ||||||||||||||||||||||||||||||||||||
Comments on "Elizabeth Second Smith" INDIVIDUAL Record. This record is used to provide a second wife to "Joseph Tag Torture." Not many other tags are used. |
PERSON8 FAMILY2
|
