Nobility title Prof. Joseph Tag Torture, Jr.

Other Events:

• Cremation: Y
• First Communion: INT 31 Dec 1997 (a test), The place
• Name: William John Smith
• Will: INT 2 TVT 5758 (interpreted Hebrew date), The place
• Retired: 11 NIVO 0006, The place
• Emigration: 1997, The place
• Immigration: Dec 1997, The place
• Christening: Est 30 Dec 1997, The place
• Baptism: Abt 31 Dec 1997, The place; Y; : 3 months; : The Church; : Birth; Address:
  Church Name
  Street Address, City Name, zip Country
• Confirmation: From 31 Dec 1997 to 2 Jan 1998, The place
• Education: 31 Dec 1997, The place; Education
• Graduation: 31 Dec 1997, The place
• Nationality: 31 Dec 1997, The place; National or tribe origin
• Occupation: 31 Dec 1997, The place; Occupation; : 40; : Employer; : Need for money; Address:
  Work address line 1
  Work address line 2, Work address line 3
• Possessions: 31 Dec 1997, The place; Possessions
• Religion: 31 Dec 1997, The place; Religion
• Occupation: 31 Dec 1998, The place; Another occupation
• Probate: From 25 SVN 5757 to 26 IYR 5757, The place
• Census: 2 TVT 5758, The place

Notes:

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.

Name:
These are notes about the first NAME structure in this record. These notes are embedded in the INDIVIDUAL record itself.

The second name structure in this record uses all possible tags for a personal name structure.

NOTE: many applications are confused by two NAME structures.

Birth:
Some specific note about the birth event.

These notes are in a separate NOTE record. These notes also have their own source citation structure.

Christened:
Christening event note (the religious event (not LDS) of baptizing and/or naming a child).

Baptized (LDS):
Notes on this LDS event. All possible LDS ordinance detail tags are used in this event.

First Communion:
First communion event note (a religious rite, the first act of sharing in the Lord's supper as part of church worship).

Name:
This is a second personal NAME structure in a single INDIVIDUAL record which is allowed in GEDCOM. This second NAME structure has all possible fields for a NAME structure.

These notes are embedded in the INDIVIDUAL record.

Will:
Will event note (a legal document treated as an event, by which a person disposes of his or her estate, to take effect after death. The event date is the date the will was signed while the person was alive. See also Probate).

Retired:
Retirement event note (an event of exiting an occupational relationship with an employer after a qualifying time period).

Emigration:
Emigration event note (an event of leaving one's homeland with the intent of residing elsewhere).

Immigration:
Immigration event note (an event of entering into a new locality with the intent of residing there).

Christening:
Alternative christening event note. GEDOM allows more than one of the same type of event.

Baptism:
A baptism event note (the event of baptism (not LDS), performed in infancy or later. See also BAPL and CHR).

Confirmation:
CONFIRMATION event note (the religious event (not LDS) of conferring the gift of the Holy Ghost and, among protestants, full church membership).

Education:
Education attribute note (indicator of a level of education attained).

Graduation:
Graduation event note (an event of awarding educational diplomas or degrees to individuals).

Nationality:
Nationality attribute note (the national heritage of an individual).

Occupation:
Occupation attribute note (the type of work or profession of an individual).

Possessions:
Possessions or property attribute note (pertaining to possessions such as real estate or other property of interest).

Religion:
Religion attribute note (a religious denomination to which a person is affiliated or for which a record applies).

Occupation:
Occupation attribute note. This is the second occupation attribute in the record.

Probate:
Probate event note (an event of judicial determination of the validity of a will. May indicate several related court activities over several dates).

Census:
Census event note (the event of the periodic count of the population for a designated locality, such as a national or state Census).

Died:
A death event note.

Buried:
Burial event note (the event of the proper disposing of the mortal remains of a deceased person).

Joseph married Mary First Jones on 31 Dec 1997 (Man and Wife) in The place, and was divorced on 31 Dec 1997 in The place. Mary was born before 1970; died after 2000. [Group Sheet] [Family Chart]

Family/Spouse: Elizabeth Second Smith. Elizabeth was born between May 1979 and Aug 1979; died in From Apr 2000 to 5 Mar 2001. [Group Sheet] [Family Chart]

Notes:

Comments on "Extra URL Filelinks" INDIVIDUAL Record.

File links in GEDCOM are created by having an OBJE structure with the path name to the file in a subordinate FILE tag and the format of the file in a subordinate FORM tag. It does not make sense to limit file links to the small set of multimedia file types mentioned in the GEDCOM standard (see INDIVIDUAL record "Standard GEDCOM Filelinks" for those file types) or even to limit them to local files. This INDIVIDUAL record has a series of links with universal resource locators (URL) in the FILE tag and the file "URL" in the FORM tag.

The sample URL links include links to a web sites, a link to an FTP site, and a link to send email.

This extension of file links to URL links is non-standard GEDCOM. What will a genealogy program do when in encounters URL file links? Cleaver programs will find the file on the Internet using your default browser, FTP program, or email program. Weaker programs will simply delete them from your file (it is bad manners to delete someone's data).