substance / texture

A visual editor for research.
MIT License
1k stars 83 forks source link

[Feature] Authors and Contributors (WIP) #1269

Open michael opened 5 years ago

michael commented 5 years ago

Description

A complete feature proposal for editing authors and contributors (reviewer, editor, translator, ...) including affiliations.

User stories

User stories provided in separate tickets:

Proposal

Authors

image

Email

Corresponding author

Author affiliations

Deceased status

Author footnotes

Present addresses

See author footnotes.

Equally contributed

See author footnotes.

Author IDs

Contributor roles

Non-author contributors

Like authors but with less details, and different roles (reviewer, editor, translator, ...)

image

Non-author contributor roles

Non-author contributor affiliations

Roles

We want to define one or more dictionaries to be used to populate the contributor roles field. They will look like this:

Roles according to CRediT Taxonomy:

Name Vocab Vocab-ID Vocab-Term Vocab-Term-ID
Data Collection credit http://dictionary.casrai.org/Contributor_Roles Investigation Investigation

Roles for non-author contributors:

Name Vocab Vocab-ID Vocab-Term Vocab-Term-ID
Translator
Reviewing Editor
Senior Editor
Reviewer

Names

These are the fields available for describing a person (either author or non-author contributor)

Melissa37 commented 5 years ago

@michael Thanks for doing this, but we need to wait for @NickDuf to think about this and think about designs.

Some of the interpretations are wrong, eg:

When email provided author is automatically marked as a corresponding author in stored XML

This does not meet the need of non-eLife users.

Deceased - realised as an optional checkbox per author

We need to work out how to add it if not present and it should not be part of the main area as it is so rare.

ORCID: if authenticated flag is set field is greyed out and not editable (only reset possible loosing the authenticated flag and letting production staff enter another orcid, which would need another verification round (to be done in integration platform)

Needs more thought on this to realize all possibilities.

Also, in Milestone 2 we will be delivering you some more Author-related metadata so we should wait for them before putting together the complete spec. Sorry!

michael commented 5 years ago

Hey @Melissa37 ! This is a work in progress of course. I'm just trying to keep a full proposal addressing the requirements as they come in. The idea is to tailor this until we are all happy. I'm calling this a "Feature" which addresses a set of feature requests.

When email provided author is automatically marked as a corresponding author in stored XML

This does not meet the need of non-eLife users.

Understand. I updated the proposal to have separate fields for email and corresponding author.

We need to work out how to add it if not present and it should not be part of the main area as it is so rare.

It's only shown inside "more fields" so should not be in the way.