You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps does it take to reproduce the issue? The algorithm discussed in #9089 fails for some Organization Names. PR #9089 adds two parameters to change the outcome and to suppress spurious given/family names for Orgs. That PR uses the new code for the schema.org export and in-page metadata, but does not back-port it to the OpenAire oai_datacite export so mischaracterizations can still occur there. Examples include 'The Project' from QDR and 'Portable Antiquities of the Netherlands' from DANS.
When does this issue occur? In the OpenAire metadata export for Creator/Contact entries
What happens? An org gets the nameType 'Personal' and has odd give/family names, e.g. givenName 'The' and familyName 'able Antiquities of the Netherlands' for the example above.
Which version of Dataverse are you using?
5.12 and earlier
The text was updated successfully, but these errors were encountered:
What steps does it take to reproduce the issue? The algorithm discussed in #9089 fails for some Organization Names. PR #9089 adds two parameters to change the outcome and to suppress spurious given/family names for Orgs. That PR uses the new code for the schema.org export and in-page metadata, but does not back-port it to the OpenAire oai_datacite export so mischaracterizations can still occur there. Examples include 'The Project' from QDR and 'Portable Antiquities of the Netherlands' from DANS.
When does this issue occur? In the OpenAire metadata export for Creator/Contact entries
What happens? An org gets the nameType 'Personal' and has odd give/family names, e.g. givenName 'The' and familyName 'able Antiquities of the Netherlands' for the example above.
Which version of Dataverse are you using?
5.12 and earlier
The text was updated successfully, but these errors were encountered: