Name Variants LogicName Variants Logic

What

Some person's names are inconsistent among Pure records. This has been reviewed and the inconsistencies might be given between the content types, but not within a same content type.

Why

Pure uses the logic explained below to assign names to content and this logic might change depending on how records are created or imported into Pure.

Please note:

• For any syncs/imports the client chooses what name should be written on the person associations object. They define this in the source data. If they do not define it and only pass on an ID, the code defaults to the persons current name (HR name).
• If you change your original name in Pure, only future content is affected.
• We do never use the sort name as display.

Research Output:
When manually creating new outputs through the editor, we always use the default publishing name. However, we use that to store the name of the publication, and we will use that stored name on the output regardless of what is altered on the person, which is intended, as the output should not be shown differently if the person changed name, it should reflect what was on the publication.

• If the persons changed their names or they added to their profile new name variants, you need to modify the name on the individual publication if you want this to be updated in the portal.
• We always use the name on the output both in backend and portal. In backend we show the known as in parenthesis in the editor like we do in all editors when it differs.

For other content types:
The know as name is always used when present. In the portal we always show the name stored on the content record (just like for research outputs). The only difference is that here we use the known as instead of the publishing name. 

Activities:
Here we are always using the current known as name if available. 

Prizes:
Here we are always using the current known as name if available. 

Press/Media:
Here we are always using the current known as name if available. 

Datasets:
Here we are always using the current known as name if available. The only difference with other content types is that we only render the initial rather than the full first name.

Persons:
In the portal we use the person's name from HR, unless a Known as name was added, then we do use the know as name in the Pure portal profile.