Wouldn't you want to use maiden names all the way though? makes it that much easier to trace ancestors if using their original names! Also what about one person having several husbands etc
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mac
Although PGV will let you add a 2 NAME Joan /Smith/ and display it properly, my interpretation of the standard does not show a 2 NAME tag as being valid. You can handle it with a NOTE in the NAME fields or add an additional 1 NAME tag, which is allowed and use the NOTE field there to explain. Doing the latter will cause the INDI to be double-listed in search results, so I have preferred to use the NOTE field. You can also add a NOTE to the DIV tag which further explains, in a contemporaneous fashion, that the INDI returned to using her maiden name.
We also use the NOTE field in the NAME structure to explain why someone previously married takes a hyphenated name as her next married name (in most cases, she has children by the first marriage who retain the previous husband's surname). i.e.:
Joan /Smith/ married (1) John Jones and became Joan /Jones/. They had a child, David Jones and divorced when the child was 14yo. She remarried Sam Brown and became Joan /Jones-Brown/.
Don't underestimate the importance of the NOTE field is explaining the who, what and whys.
-Stephen
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
archprime:
ALL my females are listed by maiden names however on marriage, the _MARNM is added to show their married name. (Can have more than one for multiple marriages.) Once the _MARNM is used, it's not always known that the female has reverted back to her maiden name on divorce. (In case you're wondering, _MARNM can also be same as her maiden name when she doesn't take her husband's name).
I use 2 NOTE to explain differences in name from the parent, will use for this situation too, as it's not that often that I know of this occurrence.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've set a standard to use the birth name as the "main name" through-out, Since I started to use PGV I've begun using _MARNM for added search capabilities. Someone could also use (but I don't) a second or third 1 NAME tag just as I would do when a person has a legal name change (which is really what is happening for a marriage name change). I use this sparingly because many other products don't support more than one 1 NAME tags.
I don't let family politics get in the way of my accurate representation of the facts. Obviously I would also add facts/events and NOTEs to support various things so you could also have:
1 EVEN
2 TYPE Name Change
2 DATE 07 NOV 1952
2 NOTE After divorce took maiden name.
This way the name is associated with a date and any other tags that are part of a normal event (PLAC, SOUR, OBJE …) This event structure would not replace a _MARNM or NAME tag but enhance the tag as documentation.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
What Gedcom tag is good to use for women who revert back to their maiden name after divorce?
Wouldn't you want to use maiden names all the way though? makes it that much easier to trace ancestors if using their original names! Also what about one person having several husbands etc
Mac
Although PGV will let you add a 2 NAME Joan /Smith/ and display it properly, my interpretation of the standard does not show a 2 NAME tag as being valid. You can handle it with a NOTE in the NAME fields or add an additional 1 NAME tag, which is allowed and use the NOTE field there to explain. Doing the latter will cause the INDI to be double-listed in search results, so I have preferred to use the NOTE field. You can also add a NOTE to the DIV tag which further explains, in a contemporaneous fashion, that the INDI returned to using her maiden name.
We also use the NOTE field in the NAME structure to explain why someone previously married takes a hyphenated name as her next married name (in most cases, she has children by the first marriage who retain the previous husband's surname). i.e.:
Joan /Smith/ married (1) John Jones and became Joan /Jones/. They had a child, David Jones and divorced when the child was 14yo. She remarried Sam Brown and became Joan /Jones-Brown/.
Don't underestimate the importance of the NOTE field is explaining the who, what and whys.
-Stephen
archprime:
ALL my females are listed by maiden names however on marriage, the _MARNM is added to show their married name. (Can have more than one for multiple marriages.) Once the _MARNM is used, it's not always known that the female has reverted back to her maiden name on divorce. (In case you're wondering, _MARNM can also be same as her maiden name when she doesn't take her husband's name).
I use 2 NOTE to explain differences in name from the parent, will use for this situation too, as it's not that often that I know of this occurrence.
I've set a standard to use the birth name as the "main name" through-out, Since I started to use PGV I've begun using _MARNM for added search capabilities. Someone could also use (but I don't) a second or third 1 NAME tag just as I would do when a person has a legal name change (which is really what is happening for a marriage name change). I use this sparingly because many other products don't support more than one 1 NAME tags.
I don't let family politics get in the way of my accurate representation of the facts. Obviously I would also add facts/events and NOTEs to support various things so you could also have:
This way the name is associated with a date and any other tags that are part of a normal event (PLAC, SOUR, OBJE …) This event structure would not replace a _MARNM or NAME tag but enhance the tag as documentation.