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
When generating the .cff file through the web app, the fields (at least the author sub-fields) are sorted by the order of addition. That means if I first add institution, and then the family name, I will get the author fields ordered in that way on my generated .cff file as well.
authors:
- given-names: Someone
affiliation: Awesome University
family-names: Smith
email: [email protected]
orcid: 'https://orcid.org/0000-0000-0000-0000'
- given-names: Jaro
family-names: Camphuijsen
email: [email protected]
affiliation: Netherlands eScience Center
orcid: 'https://orcid.org/0000-0002-8928-7831'
Instead it would be more desirable to have a standard order of these fields, because having various authors with different sub-field ordering makes the file unnecessarily chaotic.
authors:
- given-names: Someone
family-names: Smith
email: [email protected]
affiliation: Awesome University
orcid: 'https://orcid.org/0000-0000-0000-0000'
- given-names: Jaro
family-names: Camphuijsen
email: [email protected]
affiliation: Netherlands eScience Center
orcid: 'https://orcid.org/0000-0002-8928-7831'
The text was updated successfully, but these errors were encountered:
I tried again, and the issue is hard to reproduce, right now, they are actually ordered in appearance in the form, but something made my first entry shuffle them around.
When generating the .cff file through the web app, the fields (at least the author sub-fields) are sorted by the order of addition. That means if I first add institution, and then the family name, I will get the author fields ordered in that way on my generated .cff file as well.
Instead it would be more desirable to have a standard order of these fields, because having various authors with different sub-field ordering makes the file unnecessarily chaotic.
The text was updated successfully, but these errors were encountered: