We need ability to display prominently biorXiv (and other pre-prints archive) links

[rija]

User story

As website user
I want to see links to both peer reviewed and pre-publication manuscript
So that I am fullly aware of the peer review status of the linked manuscript

Acceptance criteria

Given I am on a dataset page
When I navigate to the associated manuscripts section
Then if appropriate I see a link to a pre-print archive such as bioXriv for the associated pre-publication manuscript
and this link is clearly labelled as a preprint link.

Given I am on a dataset page
And the dataset has links to a manuscript that is peer reviewed
Then I see a link to the peer reviewed manuscript

Additional Info

The issue that requires addressing:
Linking a dataset to a peer reviewed manuscript is fine, but bioXriv manuscripts are not peer reviewed so we should not add those links via the same dataset_manuscript table. or if we do we have to have a flag to show "not peer reviewed" and change the wording of the display for those.
Scenario 1:
Manuscript is submitted to BioXriv and the dataset is released in GigaDB before the manuscript has been reviewed, or even submitted (example case was dataset 100622, where BGI wanted to publish and release the genome fast, within 20days from sample collection).
Scenario 2:
Even though the manuscript has been reviewed and accepted we may wish to include the link to the bioXriv version as well as the final manuscript.
Expected action:
either - addition of an external link type "Pre-Print" to enable the inclusion of the manuscript preprint link with an appropriate text box in the dataset page
or - the addition of another column in the dataset_manuscript table to flag manuscript link as not-peer-reviewed, and changes to the website to display those links with different wording.

Dependent on this ticket to be completed first:

• we need ability to store and display bioXriv links E597 #331

Product Backlog Item Ready Checklist

• Business value is clearly articulated
• Item is understood enough by the IT team so it can make an informed decision as to whether it can complete this item
• Dependencies are identified and no external dependencies would block this item from being completed
• At the time of the scheduled sprint, the IT team has the appropriate composition to complete this item
• This item is estimated and small enough to comfortably be completed in one sprint
• Acceptance criteria are clear and testable
• Performance criteria, if any, are defined and testable
• The Scrum team understands how to demonstrate this item at the sprint review

Product Backlog Item Done Checklist

• Item(s) in increment pass all Acceptance Criteria
• Code is refactored to best practices and coding standards
• Documentation is updated as needed
• Data security has not been compromised (with particular reference to the personal information we hold in GigaDB)
• No deviation from the team technology stack and software architecture has been introduced
• The product is in a releasable state (i.e. the increment has not broken anything)