Repository navigation
feat(research): migrate CERN-only 901__u - #672
zubeydecivelek wants to merge 1 commit into
Conversation
eecc435 to
9b1c3b2
Compare
9b1c3b2 to
31fdae4
Compare
| for person in group | ||
| if (person.get("person_or_org") or {}).get("type") == "personal" | ||
| ] | ||
| if not personal_authors or any( |
There was a problem hiding this comment.
For extra affiliations listed under 901__u (that are not in any 100/700 affiliations tag), this condition would just ignore them.
Okay if that takes precedence, because if we try to one on one match, that will be kind of impossible because even if the affiliation is the same, it is stored in a different format.
For eg. http://cds.cern.ch/record/365441
100__ $$aAgosteo, S$$uMilan Polytechnic vs 901__ $$uPolytecnico Milano, CESNEF
To me it is fine, but just wanted to mention this and see how we move forward?
There was a problem hiding this comment.
This is what I got from Sara
RULE: If there is only one author/contributor assign the affiliation in 901__u to the only one.
I assume this means if the existing author doesn't have an affiliation already
There was a problem hiding this comment.
Thanks, if all the contributors already have their affiliations we can ignore all the 901 fields
31fdae4 to
f3c7979
Compare
f3c7979 to
2a1bd1d
Compare
Improve
901__uaffiliation handling during migration:UnexpectedValuefor unhandled affiliations requiring manual curation.