wishlist

[mr-c]

• json/yaml input
• accept an ORCID and derive the rest

Thanks for making this!

[idoerg]

You're welcome to write JSON/YAML input, although I am not sure how it will be used. Large group papers have a major author (or, rather, some manager/admin) who collects the author details in a spreadsheet. Not sure how JSON/YAML fits in this workflow.

As for ORCID: do you mean that an author can supply their ORCID ID and from there the program will collect details from the website? That's actually pretty neat.

EDIT: the problem is that ORCID does not list current affiliations, only employment, which may or may not overlap.

[mr-c]

One could autogenerate a json/yaml input from Git or other sources; would allow for easy editing by pull request.

orcid at least for names/sanity; we should report this usecase to them for future update on their end.

[mr-c]

http://support.orcid.org/forums/175591-orcid-ideas-forum/suggestions/12854727-allow-for-affiliation-that-is-neither-an-employer