EJP XML manifest items to convert: <contrib-group> @content-type="author"

[Melissa37]

Problem / Motivation

WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Author related metadata 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

Sample EJP output: <contrib-group><contrib contrib-type="author" corresp="yes" id="author-24343"><name><surname>Cembrowski</surname><given-names>Mark S</given-names></name><ext-link ext-link-type="orcid">http://orcid.org/0000-0001-8275-7362</ext-link><aff><addr-line><named-content content-type="department"></named-content></addr-line><institution>Janelia Research Campus, Howard Hughes Medical Institute</institution><addr-line><named-content content-type="city">Ashburn</named-content></addr-line><country>United States</country><email>cembrowskim@janelia.hhmi.org</email></aff></contrib> ... <funding-group><award-group><principal-award-recipient>author-24343</principal-award-recipient><funding-source id="http://dx.doi.org/10.13039/100000011">Howard Hughes Medical Institute (HHMI)</funding-source><award-id></award-id> ... <fn-group><fn fn-type="con" id="author-24343">Conceptualization, Data curation, Software, Formal analysis, Validation, Investigation, Visualization, Methodology, Writing&#8212;original draft, Writing&#8212;review and editing, </fn> ... <fn-group><fn fn-type="conflict" id="author-24343">none</fn>

Author word file screenshot:

Final XML example: <contrib-group><contrib contrib-type="author" corresp="yes" id="author-24343"><name><surname>Cembrowski</surname><given-names>Mark S</given-names></name><contrib-id contrib-id-type="orcid" authenticated="true">http://orcid.org/0000-0001-8275-7362</contrib-id> <email>m.harrison@elifesciences.org</email><xref ref-type="aff" rid="aff1">1</xref><xref ref-type="other" rid="fund1"/><xref ref-type="fn" rid="conf1"/><xref ref-type="fn" rid="con1"/> ... <aff id="aff1"><label>1</label><institution>Janelia Research Campus, Howard Hughes Medical Institute</institution><addr-line><named-content content-type="city">Ashburn</named-content></addr-line><country>United States</country></aff> ... <funding-group><award-group id="fund1"><funding-source><institution-wrap><institution-id institution-id-type="FundRef">https://dx.doi.org/10.13039/100000011</institution-id><institution>Howard Hughes Medical Institute</institution></institution-wrap></funding-source><principal-award-recipient><name><surname>Cembrowski</surname><given-names>Mark S</given-names></name></principal-award-recipient></award-group> ... <fn-group content-type="competing-interest"><title>Competing interests</title><fn fn-type="COI-statement" id="conf1"><p>No competing interests declared</p></fn> ... <fn-group content-type="author-contribution"><title>Author contributions</title><fn fn-type="con" id="con1"><p>Conceptualization, Data curation, Software, Formal analysis, Validation, Investigation, Visualization, Methodology, Writing original draft, Writing review and editing</p></fn>

Other items: Equal contributions: <xref ref-type="fn" rid="equal-contrib1">&#x2020;</xref> Present addresses <xref ref-type="fn" rid="pa1">&#167;</xref> Datasets: <xref ref-type="other" rid="dataset1"/>

Assumptions

• This will be a useful exercise for xPub and ScienceBeam projects and resultant code could be incorporated into those projects
• This will meet a short term need until xPub is released, when the expected output from xPub could match this?
• eLife will be required to change aspects of their affiliation tagging based on JATS4R recommendations (ie change <addr-line><named-content content-type="city"> to <city>; conflict tagging and CreDiT taxonomy (contributions) will change)
• Conflict of interest/Funding/Contributions data is available in XML metadata only and not in the Word file

Clarification needed

• A process will still need to use the Word file to get additional affiliations from there as not all affiliations can be added to EJP
• Present addresses will also need to be got from the Word file
• Authors update their Word file but not their EJP metadata and so where there are conflicts the Word file is the preferred source of truth, but conflicts should be indicated

---

Tasks

Where to start @gnott ?! This issue needs to be broken down

Technical notes

@gnott

User interface / Wireframes

NA

@eLifeProduction @de-code @gnott

[Melissa37]

Competing interests moved to a new issue as we are not JATS4R compliant

[lsh-0]

xpub has been dismantled, can this issue be closed or replaced/updated?