article type description & default selection

elifesciences / UX-features-roadmaps

A test attempt at moving some of the Product team feature definition and prioritisation into GitHub. The aim is to create more detailed feature definitions, provide more transparent prioritisation and more effective "linking" of product design to development tickets (currently in the xPub project board).

0 stars 0 forks source link

article type description & default selection #63

Open chris-huggins opened 5 years ago

chris-huggins commented 5 years ago

Should we add a brief description to each article type to help authors make a selection? If article types aren't self explanatory best practice would suggest some help is needed. We already have the information in the author guide and could link to more detailed description for further advice.

Should we also default to "Research articles" to help authors with the choice and save time where research article is most common type? Where there is a common preference for a selector it is usually best practice to default to it.

chris-huggins commented 5 years ago

Default:

Example for features:

Should we include for types we do not yet accept to help direct users to eJP?

chris-huggins commented 5 years ago

Decision made - Add a line "Find out more about eLife's article types in the author guide" or similar, with link to the article types page. If users are clicking it we could explore adding the suggestions above. https://github.com/elifesciences/elife-xpub/issues/2343

Task:

[ ] Review the number of users pressing the button

This won't help us establish if users attempting to upload a Research Advance are wasting time by submitting in LRev when they should be in eJP. The suggestion above would help with that.