Alignment between flat and complex headers to reduce user confusion

Royal-Society-of-New-Zealand / NZ-ORCID-Hub

The home of development for the New Zealand ORCID Hub

MIT License

13 stars 8 forks source link

Alignment between flat and complex headers to reduce user confusion #760

Closed rpaw053 closed 5 years ago

rpaw053 commented 5 years ago

Example of two headers which are causing confusion are the works:

"Identifier" from invitees; and,

"Work Id" aka "external-id-value" from the message body.

Please relabel "Identifier" to "Local Identifier"

and the flat file "Work Id" to "External Id(entifier Value)"

Order of flat file export could be improve a little to to keep the external id items together

[ORCIDHUB-489] created by jgus614

rpaw053 commented 5 years ago

Now in invitee section, the "Identifier" is relabeled to "Local Identifier"
So henceforth in work, funding, peer review and resource record the CSV file upload can have header either 'local identifier' or 'identifier'
and in JSON it can be either 'local-identifier' or 'identifier'.

(Github: https://github.com/Royal-Society-of-New-Zealand/NZ-ORCID-Hub/pull/749/files )

by rpaw053

rpaw053 commented 5 years ago

We have flexibility in the headers i.e admin can upload with the heading

"Work Id" or "External Id(entifier Value)" in case of Work record.
"Funding id" or "External Id(entifier Value)" in case of Funding record.
"Peer Review Id" or "External Id(entifier Value)" in case of Peer Review record.

So as discussed we will keep this.

The only change is in invitee section where we have to relabel "Identifier" to "Local Identifier".

by rpaw053