Posts

0 @A2302@ INDI
1 NAME Gertrude /WEBBER/
2 GIVN Gertrude
2 SURN WEBBER
2 _MARNM Gertrude /BLUE/
2 TYPE change of first & married name << this is just for posting, not what I am using
1 NAME Goitel /WEBBER/
2 _MARNM Goitel, Gitla /BLUSTEINOWITZ/
2 TYPE birth name and original married name <<< this is just for posting, not what I am using

I am showing the two scenarios for Gertrude, above. Not sure how I should be properly recording when she changes her first name and MARRIED name (this would not have been with legal docs as it wasn’t required back then). The twist being it’s married name, not her maiden name so the usuall 2 TYPE change of name is harder to use, or is it?

----- [updated: 31Aug2023]

 Alter-Drukarsh connections |The Garelicks|Journal 3.3.12 -  PHP Version 8.1.17 - mySQL 8.1
The Royals |The Kennedys|The Gerrer Rabbis  3.3.12 -  PHP Version 8.1.17 - mySQL 8.1

Like many things there is no “proper” way, only every bodies different preferences.

Technically it can be argued that “_MARNM” is not proper, because it’s not in the GEDCOM spec. It’s just a commonly used unofficial tag. So a “proper” entry (for a normal single marriage / person) would be:
@A2302@ INDI
1 NAME Gertrude /WEBBER/
2 GIVN Gertrude
2 SURN WEBBER
2 TYPE birth
1 NAME Gertrude /BLUE/
2 GIVN Gertrude
2 SURN BLUE
2 TYPE married

It is not common to use, as you seem to, both “2 _MARNM” and “2 TYPE married” though, as they both tell the same fact. I aslo don’t feel that the use of “2 TYPE birth” is necessary (and bad for many parts of the display). The first listed name will always be the “primary name” and should therefore always be the birth name. Therefore no further identification is normally required.

But in your case I don’t think I fully understand the problem. Gertrude has three names, so are they birth, marriage 1, and marriage 2 ? If not what is each name? If my supposition is corect then either of these two are what I might use:

OPTION 1:
@A2302@ INDI
1 NAME Gertrude /WEBBER/
2 GIVN Gertrude
2 SURN WEBBER
2 TYPE birth [this one is IMHO optional / not required ]
1 NAME Gertrude /BLUE/
2 GIVN Gertrude
2 SURN BLUE
2 TYPE married
1 NAME Gertrude /BLUSTEINOWITZ/
2 GIVN Gertrude
2 SURN BLUSTEINOWITZ
2 TYPE married

or

OPTION 2:
@A2302@ INDI
1 NAME Gertrude /WEBBER/
2 GIVN Gertrude
2 SURN WEBBER
2 _MARNM Gertrude /BLUE/
2 _MARNM Gertrude /BLUSTEINOWITZ/

Nigel
My personal kiwitrees site is www.our-families.info

I don’t use a 2 TYPE married, I use _MARNM because it’s critical info to know this to find info after the woman is married. Why it never made it into the GEDCOM is crazy but that’s another story.

She wasn’t married twice as your option 2 would imply. Her maiden name changed & first name (at unknown point); then she married and her and husband changed their name. Two name changes.

BORN: Gitla /WEBBER/ changed to Gertrude /WEBBER/
MARRIED: Gertrude /BLUSTEINOWITZ/ changed to Gertrude /BLUE/

While I could use Gertrude /WEBBER/ for maiden (I often do), how do I show her change of married name without implying 2 marriages?

----- [updated: 31Aug2023]

 Alter-Drukarsh connections |The Garelicks|Journal 3.3.12 -  PHP Version 8.1.17 - mySQL 8.1
The Royals |The Kennedys|The Gerrer Rabbis  3.3.12 -  PHP Version 8.1.17 - mySQL 8.1

Ah, now I see. Interesting case.

I would use OPTION 2 and add a NOTE to explain the two married names.

Or you could use OPTION 1 and similarly add the same note to the third name group (BLUSTEINOWITZ).

Either are valid. Opt 1 is the more technically correct. Opt 2 is (IMHO) the more visually pleasing and certainly a lot less effort!

Nigel
My personal kiwitrees site is www.our-families.info