Handle multiple affiliations in Zenodo for CFF 1.3.0+ #386
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* incorporate PR from upstream citation-file-format with scheme updates for multiple affiliations * add new derived author class that supports both multiple affiliations * translates `ror` into `id` for .zenodo.json
Author
|
I'm thinking that this support should perhaps actually be in the base class |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is an incomplete draft pull request to partially implement multiple affiliations once the upstream schema change is merged in to CFF v1.3.0 in citation-file-format/citation-file-format#523
This PR:
cff_1_x_x/authors/zenodoto create anaffiliations:key in.zenodo.jsonif a list is present, otherwise defaults back to theaffiliationkey.rorif present, but outputs it asidfor Zenodo backend.