openMetadataInitiative
Revisit representation of personal names
In the openMINDS developer meeting of 2023-10-02 we discussed changing the representation of personal names, since
- some people have only a single name, no family name
- "givenName" may not be semantically correct, since some people use a name they have chosen themselves, not one that was given to them
- more generally, some people are known by different names at different times in their life
In the short term, we decided to store a single name in the "givenName" property. In the medium term, we will add an optional "fullName" property (which will be inferred from givenName and familyName if those are given"). This is backwards compatible. In the longer term, we will make "fullName" required. This requires a new openMINDS major release.
For name changes, we decided to keep using the "alternateName" array.
The alternative approach, of adding a separate Name/NameVersion schema, was felt to be too complicated.
A further topic is whether to represent middle names by (a) making givenName an array, (b) adding a middleName property, (c) as at present, put them as initials in givenName.
never ending issue (see #83,#17) :)
new schema in this space by quarto at https://quarto.org/docs/journals/authors.html: name: given: string family: string literal: string dropping-particle: string non-dropping-particle: string
I like the term "literal" which represents the jatsxml "string-name".
As you probably know, Orcid use givenNAme as the required field: https://support.orcid.org/hc/en-us/articles/360006973853-Add-and-edit-your-name-on-your-ORCID-record
