EJP XML manifest items to convert: Clinical trial information (NEW REQUIREMENT)

[Melissa37]

Problem / Motivation

WHO: Production/Production Vendor/Libero hosting WHEN: Between Export from EJP/xPub and delivery to production vendor; and hosting on eLife site WHERE: In eLife bot processes and on publication WHAT: Clinical trial information 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

Output from EJP: <back> ... <fn-group content-type="ethics-information"> ... <fn fn-type="other"><p>Clinical trial registration CB7778886452342</p></fn> ... </fn-group> ... </back>

NEW JATS4R requirements Add as a sec to the end of the abstract:

<abstract> ... <sec id="abs3-9"><title>Clinical trial registration</title><related-object id="RO1" source-type="clinical-trials-registry" source-id="ClinicalTrials.gov" source-id-type="registry-name" document-id="NCT02968459" document-id-type="clinical-trial-number" xlink:href="https://clinicaltrials.gov/show/NCT02968459">This study is registered with ClinicalTrials.gov as NCT02968459.</related-object></sec></abstract>

Note: @id added as PMC style checker requirement.

And adding to the main text: <article-meta> ... <related-object source-type="clinical-trials-registry" source-id="10.18810/isrctn" source-id-type="crossref-doi" document-id="10.1186/ISRCTN98371961" document-id-type="doi" xlink:href="https://www.isrctn.com/ISRCTN98371961">Clinical Trial Registration: This study is registered with ISRCTN as ISRCTN98371961.</related-object> ... </article-meta>

Clarification needed and assumptions

• There are a lot of requirements for the final XML that are not available in the source XML from EJP
• This change will require changes on the hosting end
• This change will require UX on the Texture interface and in xPub
• To start with we might have to push what we receive straight through to the production vendor to sort out

Reference https://github.com/substance/texture/issues/945

Tasks

• [ ] Meeting required to discuss this - to involve Editorial/xPub team/Production/Dev team
• [ ] More to follow

Technical notes

User interface / Wireframes

Will require wire frames

@gnott @Maelplaine @thewilkybarkid @eLifeProduction

Editorial need to be added to this repo

[gnott]

If we can confirm the trial number is part of the approved registries, and it appears in Crossref's list of registries (http://api.crossref.org/works/10.18810/registries/transform/application/vnd.crossref.unixsd+xml), we may be able to fill in the URI for the trial just based on the trial number alone.

Is it possible the trial numbers specified could be any value? It would be difficult to know where the trial is registered in that case unless the UI allows authors to add the registry name or a DOI or URI for the particular trial.

[Melissa37]

I am sure we could change the language on EJP and ask for more info in the free text field. A url would be best?

However, I think we've only published about 3 articles so far that have clinical trials, so it might be a lot of effort for little gain and perhaps deal with better in xPub?

We are trying to get more clinical papers but it's predicted we'll get a handful or two over the next year.

I do wonder whether this could pass straight through, but I have an idea about a validation email being sent to production when you pass onto the vendor and unusual things that we don't normally get could be highlighted on that email so production know to check the vendor processes for them? I'll open a new ticket and reference this one.