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
We often receive records that have ROR identifiers as part of their raw affiliations (authors.raw_affiliations.value). This is not the right place for them, as we have a dedicated field for them authors.affiliations_identifiers.
The best approach would probably to modify the signature builder so it detects RORs based on the pattern defined in the schema and adds them to authors.affiliations_identifiers.value with (schema = ROR) instead.
A curation script should also be written to clean up all existing records after the builder update has been deployed.
Work involved
Acceptance criteria
RORs in raw affiliations are added automatically to affiliations_identifiers instead of raw_affiliations when harvesting a new record, e.g. from APS.
All existing records are cleaned up and have their RORs moved to the correct place
Screenshots(Optional)
The text was updated successfully, but these errors were encountered:
Description
We often receive records that have ROR identifiers as part of their raw affiliations (
authors.raw_affiliations.value
). This is not the right place for them, as we have a dedicated field for themauthors.affiliations_identifiers
.The best approach would probably to modify the signature builder so it detects RORs based on the pattern defined in the schema and adds them to
authors.affiliations_identifiers.value
with (schema = ROR
) instead.A curation script should also be written to clean up all existing records after the builder update has been deployed.
Work involved
Acceptance criteria
affiliations_identifiers
instead ofraw_affiliations
when harvesting a new record, e.g. from APS.Screenshots(Optional)
The text was updated successfully, but these errors were encountered: