Question PERSONAL_NAME_PIECES

The NPFX, GIVN, NICK, SPFX, SURN, and NSFX tags are provided optionally for systems that cannot operate effectively with less structured information.

webtrees has no problem operating effectively "with less structured information."

Those using the optional name pieces should assume that few systems will process them, and most will not provide the name pieces.

Therefore, I would prefer to not have them in my data nor in my exported GEDCOM. I understand there may be a few users exporting to programs that need them. I am not one.

I would request a settings option to not generate those. I do use NICK but rarely. If not generating SURN, GIVN, etc. also loses NICK, I can add it manually for those few cases.

(I am happy to see that the latest version uses TYPE married instead of _MARNM.)

I think you could do this very easiliy with a custom module.

See my recent post regarding the CEME tag.

The NAME tag has lots of logic associated with it, to read values from the GIVN/SURN/etc.

So, you'd need to replace NAME with a simple input field.

You should then tell webtrees that the INDI:XXXX tag should not have the following subtags (0,0 means min/max of zero).

I would prefer to not have them in my data nor in my exported GEDCOM.

Agreed. I would greatly appreciate it if the creation of the NPFX, GIVN, NICK, SPFX, SURN, and NSFX name parts became optional.

See also: How to prevent creation of GIVN, SPFX and SURN tags?

Thanks for sharing the custom tag solution, Greg!

Note: the second SPFX subtag should be NSFX.

But it doesn't work quite right.

If I add a child to a family whose name contains a Surname prefix, then by default the Surname prefix and the Surname are still shown and stored when entering. Despite the fact that these are disabled via the custom module.

In this case, how can name parts be prevented from being stored?

OK - webtrees will always display any existing tags.

When webtrees creates a new individual, it uses the "Surname Tradition" settings to create a new name.
This name can include the SPFX and SURN from the parent/spouse.

Just change the surname tradition setting to none.

OK - webtrees will always display any existing tags.

Only the NAME of the parent/spouse is stored, so the subtags SPFX and SURN don't exist but are created by webtrees when creating an new individual.

Just change the surname tradition setting to none.

Without a surname tradition the surname must be entered each time, which is not convenient and also error-prone due to possible typing errors.

Isn't there a possibility to omit the creation of the SPFX and SURN subtags in the surname tradition?

> Isn't there a possibility to omit the creation of the SPFX and SURN subtags in the surname tradition?

At present no.

But I plan to reorganise the surname-tradition code to be more like the gedcom tag code.

This will allow a module to register a new surname tradition. You can add your own. It would be simple to modify an existing one and remove the SURN tags.

fisharebest wrote:

I think you could do this very easiliy with a custom module.

See my recent post regarding the CEME tag.

The NAME tag has lots of logic associated with it, to read values from the GIVN/SURN/etc.

So, you'd need to replace NAME with a simple input field.

Code:

'INDI:NAME' => CustomElement(I18N::translate('Name')),

This changes the edit form? If I leave it out, will it still build the name from the other fields?

fisharebest wrote:

You should then tell webtrees that the INDI:XXXX tag should not have the following subtags (0,0 means min/max of zero).

Code:

'INDI:NAME' => [['NPFX', '0:0']], 'INDI:NAME' => [['GIVN', '0:0']], 'INDI:NAME' => [['SPFX', '0:0']], 'INDI:NAME' => [['SURN', '0:0']], 'INDI:NAME' => [['SPFX', '0:0']],

Or do these prevent them from appearing in the edit form? Is it allowed to have a comma after the last element in the array?

This has evolved from feature request to customization, so I have posted www.webtrees.net/index.php/en/forum/4-cu...85-limit-name-pieces

It is allowed to have a comma after the last element. This makes it easier if you like to add more entries later.

Another idea: A checkbox next to the text field for each of these items for "put in GEDCOM."
An admin setting to choose whether default is ticked or not ticked.
Can still use the entries for indexing (save them in a separate column or table?) even if not putting them in raw GEDCOM.

Or, an admin setting to hide them from raw GEDCOM (including export) while keeping them in the DB and the edit panel.

I use the SURN tag to support: 1) multiple surnames separated by comma, 2) stem surname where gender effects name suffix, 3) family group when individual has no surname by tradition

These surname traditions effect Polish, Nordic, Portuguese, Brazilian, Spanish and other surname customs.

You probably don’t have these, but I’m pointing this out if others think this concept might be a good idea for them.

norwegian_sardines wrote:

I use the SURN tag to support: 1) multiple surnames separated by comma, 2) stem surname where gender effects name suffix, 3) family group when individual has no surname by tradition

These surname traditions effect Polish, Nordic, Portuguese, Brazilian, Spanish and other surname customs.

You probably don’t have these, but I’m pointing this out if others think this concept might be a good idea for them.

I have Polish and Mexican, but so far I have not needed either (1) or (2). But I don't want to eliminate it, just make it optional. People who export to "systems that cannot operate effectively with less structured information" will still need the option.

fisharebest wrote:

I think you could do this very easiliy with a custom module.

The NAME tag has lots of logic associated with it, to read values from the GIVN/SURN/etc.

So, you'd need to replace NAME with a simple input field.

Code:

'INDI:NAME' => CustomElement(I18N::translate('Name')),

You should then tell webtrees that the INDI:XXXX tag should not have the following subtags (0,0 means min/max of zero).

Code:

'INDI:NAME' => [['NPFX', '0:0']], 'INDI:NAME' => [['GIVN', '0:0']], 'INDI:NAME' => [['SPFX', '0:0']], 'INDI:NAME' => [['SURN', '0:0']], 'INDI:NAME' => [['SPFX', '0:0']],

I have a module with the second part, the 0:0 lines, but not the CustomElement.  It still creates the name pieces.  Does the CustomElement go in the same file?  Before or after the other part?

I tried it this way, and got a "Error: Call to undefined function NamepieceNamespace\CustomElement() in /var/www/html/un/unigen.us/modules_v4/namepieces/NamepieceModuleCustomTags.php:141"