elifesciences / package-ejp-raw-output-zip

Transform article raw zip files from EJP to a more consistent output.
MIT License
0 stars 1 forks source link

EJP XML manifest items to convert: biorxiv preprint information (NEW REQUIREMENT) #22

Open Melissa37 opened 5 years ago

Melissa37 commented 5 years ago

Problem / Motivation

WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: biorxiv preprint publication information about the article WHY: We'd be giving the vendor clean metadata with fewer conversion requirements and it gets us closer to the end goal of converting author word files to JATS XML for publication

Proposed solution

Export from EJP as: <fn-group content-type="article-history"><title>Preprint</title><fn fn-type="other"/><ext-link ext-link-type="url" xlink:href="http://www.biorxiv.org/content/early/2017/08/08/173450"/></fn-group>

This is how we expect it to be presented in the final XML:

<pub-history><event><event-desc>This article was ogininally published as a <ext-link ext-link-type="uri" xlink:href="https://www.biorxiv.org/content/early/2017/03/24/118356">preprint on Biorxiv</ext-link></event-desc><date iso-8601-date="2016-03-01"><day>24</day><month>03</month><year>2017</year></date></event></pub-history>

Changes required: Completely rewrite the XML! Derive the publication date from the URL string Add boilerplate text: This article was originally published as a preprint on Biorxiv

Clarification needed and assumptions


Tasks

@gnott

Technical notes

@gnott

User interface / Wireframes

NA - except for Texture

gnott commented 5 years ago

Is biorxiv the only preprint server to support, especially regarding how the date appears in the URL, or will there be other preprint servers to account for now or in the future

Melissa37 commented 5 years ago

Is biorxiv the only preprint server to support, especially regarding how the date appears in the URL, or will there be other preprint servers to account for now or in the future

It is currently the only one we support. In the future there may be more, but I think they might have different url structures and processes