They’re often summarized using the acronym FAN for “Friends, Associates, Neighbors.” While the FAN club principle of cluster genealogy is often advocated, few apps that I’ve reviewed have a field for associates, and even fewer use the standard GEDCOM structure for them. Associates could be godparents, sponsors, witnesses, friends, neighbors, co-workers, etc. + Associations: An association in genealogy is a relationship between two people, usually but not necessarily non-familial. Few applications have these additional fields, but GEDitCOM does. + Additional Genealogical Data: The GEDCOM standard allows additional data to be included, such as events recorded and agency recorded by in a source or responsible agency for an event.
+ Family Events: Organized the event Separation along with other family events, even though it used the generic event structure. + A doptive parents’ relationships: Properly recognized the GEDCOM tag PEDI indicating whether a family relationship was birth, adopted, foster, or sealing. Not all apps can do this. There are also separate fields for Name Prefix, Suffix, Nickname, and Nobility Title, which are standard GEDCOM fields-all good. GEDitCOM imported secondary names as additional names, as expected. + Secondary Names: These are name structures that occur after the first name structure in an individual’s record in a GEDCOM file. It also imported the EMAIL and structures (see Cons). For example, it pointed out that FACT is an invalid GEDCOM tag (it’s really a valid GEDCOM 5.5.1 tag) but imported it to the Other tab. + Unrecognized data: For GEDCOM tags GEDitCOM didn’t recognize, it generally imported them anyway with a warning. + Imported all valid GEDCOM 5.5 and 5.5.1 tags: GEDitCOM is one of the few apps that imported all valid GEDCOM tags, even those it didn’t recognize from GEDCOM 5.5.1. But be aware that GEDitCOM will also export any invalid descriptions back to GEDCOM, so I recommend you move them to the corresponding note. In the individual events window, there was the statement, “Line 1 of next BIRT should not have this statement” (Fig 1). GEDitCOM pointed out the invalid event description in my file but imported it anyway. Many genealogy apps violate this rule, including FTM, which enabled me to include it in my test GEDCOM file. + Invalid event description: The only entry that a birth, death, or marriage event description (called a “descriptor” in the standard) may have is the letter “Y” to assert that the event occurred if and only if both the date and place are blank. GEDitCOM is one of the few apps I’ve tested that even has correct alias records. That way you can see the data and correct it. GEDitCOM imported the ALIA tag the way it should be, as an Associated Record on the person window, which is good to preserve the data. The closest the GEDCOM standard has to “Also Known As” is the Nickname field, whose tag is NICK, or the Name Type tag, which is rarely used. The ALIA tag should be used to provide a cross-reference to another person who may be the same. + FTM’s invalid use of the ALIA tag: Older versions of Family Tree Maker (FTM) and a few other apps incorrectly use the ALIA tag in GEDCOMs for the “Also Known As” field. It would also be nice if the report listed problems by GEDCOM line number to make it easier to find them. It’s clear from the report that GEDitCOM expects GEDCOMs to be in version 5.5 format, but more about this under Cons. + GEDCOM import log: All good genealogy apps should produce a GEDOM import error log, and GEDitCOM produces one called a GEDCOM Validation Report. I suggest you highlight, copy, and paste the text into a text editor and save it for reference, although you can access it again from the main screen if needed. One tip I have to offer is to save your file periodically because it does not save automatically. Importing a GEDCOM file into GEDitCOM is straightforward, since it is a GEDCOM editor, but instructions are on their website and in the Help menu if you need help. References to the GEDCOM standard are to version 5.5.1 unless stated otherwise. Portions of text in all capital letters that are not acronyms are GEDCOM tags, with the rest of the plain text field name in lowercase. The trial has a time limit of 15 days but is otherwise fully funtional.
GEDITCOM 2 REVIEW TRIAL
Version tested: GEDitCOM II 2.1 trial version. GenSoftReviews: 5 stars out of 5 (4 ratings)
0 kommentar(er)
