TNG Events and Event Types

From TNG_Wiki
Jump to: navigation, search

Standard Events

TNG has the following "standard" facts and events, as shown in clips from the Person and Family data entry screens:

In Person Records:
  • Name (in component fields)
  • Sex
  • Birth
  • Christening
  • Death
  • Burial
  • Baptism (LDS)
  • Confirmation (LDS)
  • Initiatory(LDS)
  • Endowment (LDS)
Standardpersonevents.png
In Family records:
  • Marriage
  • Divorce
  • Sealing (LDS)
Standardfamilyevents.png

In the Person Edit screen shot above, the LDS events were hidden by a configuration setting.

TNG treats these "standard" events quite differently from other events. The value of the primary name/gender facts, and the date and place of the primary instance of each of these events are stored directly in TNG's People and Families tables.

Custom Events

Facts and events other than the standard events - including secondary instances of the standard event types- cannot be created until "custom" event types are entered into the TNG EventTypes table. Once that is done, "custom" events can be created, and are stored in the TNG Events table.

Here is a clip from one site's EventTypes search results list:

Eventtypes.png

Note that

  • The events outlined in green are standard events (and facts), but their presence in this table allow secondary events for those event types to be recorded. Secondary facts are recorded as events and are therefore able to take on a date and a placename.
  • The Email and Phone events outlined in red are actually associated with Repositories rather than People or Families. My only guess as to the reason that Email and Phone are recorded as events rather than data fields in the TNG Repositories table is that with events, a Repository can have than one Email address or phone number. Strangely, Email and Phone events are recorded for every Repository record, even if there is no Email or Phone value for that Repository.
  • The events outlined in blue represent a Gedcom artifact. That is, Gedcom has a general purpose "EVEN" event, which needs a "TYPE" modifier on the next line. There is no standardization of "TYPE", so anything can be put there. Some genealogy applications record when a person "Arrived" in a new locale, such as a country, city, or state. In such systems, a person's immigration to a new country may be recorded with an Arrival event (or, more specifically, an EVEN event with the Arrival tag. In other circumstances, a person's immigration to a new country may be recorded with a standard Gedcom IMMI (for immigration) event.
  • All of the unmarked events are TNG "Custom" events that are recorded in Event records in the TNG database. You can see that most of them are standard Gedcom events with standard Gedcom tags, but two - _DECAUSE, and _MDCL - are nonstandard.
 

Creating Custom Events

When TNG is installed, the EventTypes table is empty. Event Types can be entered manually, or added by processing a Gedcom file.

Entering Event Types manually

At Administration >> Custom Event Types, you'll see a table similar to the one above, and you can use the Add New tab to create additional Custom event types. Each event type has the following attributes:

  • Associated With - Which type of object - Individual, Family, Source, or Repository
  • Tag - The short, capitalized code used in Gedcom files. A number of tags are already defined in a drop-down list, or you may enter any tag value.
  • Type - The Tag type associated with the EVEN (Event) Tag. This should be a single word.
  • Display - The value to be used on Person and Family Profiles, and some other reports, to identify events of this type. This should generally be a single word.
  • Other Languages - If you have defined other languages to be active on your site, you can enter display values for each of those languages.
  • Display Order - A digit that groups events on the Person and Family profiles. All events with Display Order=0 are displayed before events with Display Order=1, etc.
  • Event Data: Accept/Ignore - When this Event is seen in a Gedcom, should it be loaded into the database, or ignored.
  • Collapse Event: Yes/No - When yes is selected, on the Person or Family Profile, when there are multiple instances of an event type (such as Residence or Census), the events will not be displayed initially. Instead, just one line with the event display string will be shown, with an arrow that the user can click on to display all instances of that event type.

Gedcom Import

At Administration >> Import/Export >> Import, where you start a Gedcom import, you may check either (or neither) of two checkboxed:

  • "Import Custom Event Types Only" - The Gedcom file is read only to load the EventTypes table with event tags not already in the table. Then you can go to the Administration >> Custom Event Types screen to select new eventtypes as necessary to change their attributes, and then run the Gedcom Import again.
  • "Accept Data for all new Custom Event Types" - All new event types in the Gedcom file will be added to the EventTypes table as the Gedcom is process, AND data associated with those event types will be saved in the database.

Other Considerations

  1. In some TNG reports, when there is no Birth date, the primary Christening date will be used in its place (often prefixed with "chr." or some other abbreviation).
  2. In some TNG reports, when there is no Death data, the primary Burial date will be used in its place (often prefixed with "bur." or some other abbreviation).
  3. Because "Baptism" is a special LDS event, and LDS events are not always displayed, infant baptisms should be recorded as "Christening" events, not as "Baptisms"

See also

Events in TNG and in Gedcom