Question Name TYPE

How can I enter a not predefined TYPE for an individuum, for example "Artist name"?

Why is the entered TYPE converted to Uppercase (entered a raw gedcom)?

How to translate the entered TYPE?

Franz Frese wrote:

How can I enter a not predefined TYPE for an individuum, for example "Artist name"?......

Franz,
They have to be entered via Edit Raw Gedcom.

See discussion here: www.webtrees.net/index.php/en/forum/9-re...ined-name-type#97573
and Github post here: github.com/fisharebest/webtrees/issues/4735
~doug

Instead of using “artist name” you should use “also known as”.

Should is too harsh: can. You can use AKA.
With a note it's an artist name.

Me thinks the gedcom specs only give examples of name types, not limit the enumeration. Have to check though

Instead of using “maiden name” you can use “birth name”.
So you can remove "maiden name" from predefined list.
"artist name" was an example!

Bert,
Yes you can use Also known As in the presented list.

GEDCOM says the following.
[ aka | birth | immigrant | maiden | married | <user defined>]

I agree that they seam to mean the same thing in Western cultures.

However,

I have two entries where the individual had a name on their birth certificate, but quickly the name was changed to something else for public consumption. In both cases the usage was to protect the true father and child from ridicule.

Some times an individual will not receive a name a birth, but receive their name at a naming ceremony later in life.

For my heritage which I am trying to record and preserve, the Chinese have many different formalized names. I have the same issue as Franz in having it translated correctly. That is why free typing the Name TYPE is not ideal, but better than editing the raw gedcom. See for example en.wikipedia.org/wiki/Names_of_Sun_Yat-sen .
Looking forward to what Greg has planned on future releases.

In my eyes free text within TYPE fields is not the problem. Only the translation has to follow the free text. I would suggest to add new free text entries in English and enter the new translation in the respective language either directly to the translation portal translate.webtrees.net or open a new thread in the translation section of the forum.

norwegian_sardines wrote:

I agree that they seam to mean the same thing in Western cultures.

However,

I have two entries where the individual had a name on their birth certificate, but quickly the name was changed to something else for public consumption. In both cases the usage was to protect the true father and child from ridicule.

Some times an individual will not receive a name a birth, but receive their name at a naming ceremony later in life.

the name tag has no date / period associated. (different date - different married name - only one TYPE)
given name is not given at birth (may be at christening)
surname exists at birth
for the rare cases I would use a note.

Franz said:

the name tag has no date / period associated. (different date - different married name - only one TYPE)
given name is not given at birth (may be at christening)
surname exists at birth
for the rare cases I would use a note.

Yes you are correct, this is an issue with GEDCOM v5.5.1 and we are working on fixing this for either v7.1 or 8.0 of GEDCOM.

One change that could be done using a Dialect of GEDCOM is to introduce a _DATE tag but this would require a module to be written to support the GEDCOM dialect just like imported GEDCOMs from other applications.