Family Historian User Group

From the GEDCOM v5.5.1 document the surname prefix is defined as: Surname prefix or article used in a family name. Different surname articles are separated by a comma, for example in the name "de la Cruz", this value would be "de, la" One of the biggest issues with surname and surname prefix in a “s...

The GEDCOM Standard semantics of NICK vs AKA is unclear in 5.5.1, which means they are used in multiple ways in extant GEDCOM files. Currently the GEDCOM steering committee feels that “nick” is the familiar form of a single name (as in Dick for Richard, Jenny for Jennifer). While AKA is the complete...

When it come to source and source_citation and images associated with them I see these in a very specific way. The source is the book, census, bound collection of pages, microfilm, etc. the only images I associate with this record is the cover, title page, and other similar pages that describe the s...

For me it depends heavily on how sure I am of the actual age of the individual at the time of the dated event. If I know the age at the event with a high degree of accuracy then the age given in the source and the text source goes in the TEXT field and my accurate age goes in the AGE field. If I don...

I find the concept of “Standardized name” funny in the land of Norway! Most of my relatives never had a inherited surname to begin with.

The GEDCOM structure does allow for a NAME.NOTE and NAME.SOUR subtags, but not a NAME.DATE subtag. Since a Source_Citation is allowed, GEDCOM does allow in “linked sources” a subtag of DATA.DATE where the date is the date of recorded entry.

n SOUR @…@
+1 DATA
+2 DATE

My comment is probably not welcome (sorry) but I consider all licenses obtained by a individual as a source for an event for obtaining said license. I realize that it sound like I’m splitting hairs, but in the case of a Family event MARL (marriage license) this event for me sets the standard for all...

If you look at the GEDCOM-L design and proposal for “location” it is currently an add-on to GEDCOM, but can also be a replacement for the GEDCOM Place_Structure. It supports many of the things the current GEDCOM structure misses. The _LOC tag is added at the same level as a PLAC tag: 2 PLAC Naustdal...

Tatewise is correct, that PLAC has not been normalized to use XREF links, this is one of the drawbacks of being GEDCOM compliant! If you follow GEDCOM-L proposals they extend GEDCOM by normalizing to _LOC records and XREF pointers for each location. My hope was that GEDCOM 7.0 would have normalized ...

Yes I’ve seen and reviewed a few of the tests from John’s site, but some time ago! I don’t recall my findings in specifics, but I do remember him not testing things like PLAC.FORM or some other PLAC subtags. FACT.TYPE was a concern with all programs, which for me is a deal breaker! My point was with...

I just start to investigate FH7 to use in conjunction with my very GEDCOM 5.5.1 compliant database. I probably use every (or nearly every) tag in the GEDCOM specification except those specific to LDS. Based on your statement I’m probably going to find some lost data or broken concepts at some point ...

Tatewise,

GEDCOM is only meant to be a GEnealogy Data COMmunications format and does not restrict internal program data structures.

Yes this is true, but my understand was that FH7 used GEDCOM internally as well! Is this not true?

In 20441|Places and Addresses wildbill said: . My disappointment with the FH Address is that it is not relational to the Place In GEDCOM the ADDR (address tag) is very separate from the PLAC tag and are not related in any way except that they are subtags of an event or attribute (facts). The ADDR ta...

I’ve never heard of a Fax as it relates to a postal code in the USA. In the USA it is either a ZIP (5 digits) or ZIP+4 (9 digits). Predecessor systems were called “postal zones” (2 digits) and SCF (the first 3 digits of a ZIP).

My first question is “what are you struggling with regarding source/citation”. My comment about using notes vs the source/citation structure is that most reporting features use the given structure in reports to list out the places that information was found, while notes are less likely or harder to ...

Since the beginning of my foray into genealogy in the early 1980’s I’ve use “interview by {interviewer} of {interviewee}” as my source. I learned this from a Norwegian Researcher who did a lot of interviews of locals for books he wrote about each of the kommune he chronicled. Some of the information...

I realize what I’m about to say has been said in other entries in this thread, but it should be repeated: Because a lot of the work we do in genealogy (as in other scientific research) is based on / rides on the work of others in our field we must acknowledge their work when citing information. If d...

PAF had a lot of trouble with following GEDCOM. The most recent versions of PAF (version 4.0 and above) were not authored by LDS but by Ancestral Quest. Many software programs had data entry fields for specific levels of “place” rather than one free-form field. PAF never supported multiple NAME tags...

@tatewise, I would suspect that a conversion is required when reading a file path from the index as well!

Windows (as opposed to *nix operation systems) operates natively in UTF-16, so converting a UTF-16 encoding to the Unicode character set (and Vice-Vera) is always part of the Windows API, while converting a UTF-8 encoding to the Unicode (and vice-versa) may not be available in a specific Windows API...

In GEDCOM, this is we’re I use the MARR.TYPE tag to indicate “common-law”, or “separated” and other types/dispositions of relationships that become like a marriage in various societies and customs!

As for adding parents to the baptismal Thomas, who may or may not be “your” Thomas. GEDCOM v5.5.1 has a construct that in theory solves your problem. It is most likely not supported in FH (most applications don’t or use it incorrectly). The INDI.ALIA tag could be used to point to an additional Thoma...

After review I don’t think the use of the FAMC tag on Thomas would work as this tag (and it’s subtags) could be used to question Thomas’ connection to his parents but not the fact that the Baptism used in Thomas’ Individual_Record may be incorrectly assigned to the Thomas “father of this family.” Th...

An important reason for not automatically sorting children by birth order (by date) is when you don’t have an exact date or any date for some or all of the children. For example: A couple could have two children in a year but you don’t know the day or month, but you could know the order! Ordering by...

If you have a little website knowledge, I use webtrees at webtrees.net to display my GEDCOM. It is free to use but requires your own website. Easy to install however! I think their is even a docker script as well. Then it can be viewed on any browser. webtrees is a branch of the older phpgedview, fr...