WHO: Production/Production Vendor
WHEN: Between Export from EJP/xPub and delivery to production vendor
WHERE: In eLife bot processes
WHAT: All metadata that needs to be converted to eLife final XML programmatically
WHY: EJP exports XML that was devised a while back and we've updated the final structure since. It is costly (time/money/poor regression) to get EJP to change it. Better to control it ourselves and ensure the production vendor receives what we want to be published and we control updates to it.
Proposed solution
Example output from EJP:
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Archiving and Interchange DTD v3.0 20080202//EN" "archivearticle3.dtd"><article article-type="research-article">
Example final XML:
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.2d1 20151215//EN" "JATS-archivearticle1.dtd"><article article-type="research-article" dtd-version="1.2d1" xmlns:ali="http://www.niso.org/schemas/ali/1.0/" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">
Clarification needed
The @article-type on article drives the template used on the html version of the article and is also used for PubMed deposits.
The @article-types currently used are:
article-commentary - Insight
correction - Correction
discussion - Feature 1/Feature 2
editorial - Editorial
research-article - all research content (ie non-feature content)
Question - Does EJP add these all correctly to the XML they output?
Assumptions
We will update to the most recent version of JATS soon.
Tasks
@gnott to complete
Technical notes
@gnott to complete
When using the Python XML libraries to export the final XML, it typically only includes the namespaces that are actually used, for example if you try to add xmlns:ali="http://www.niso.org/schemas/ali/1.0/" and there are no <ali:> tags, then this namespace tends to be dropped since it is not required
Problem / Motivation
WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: All metadata that needs to be converted to eLife final XML programmatically WHY: EJP exports XML that was devised a while back and we've updated the final structure since. It is costly (time/money/poor regression) to get EJP to change it. Better to control it ourselves and ensure the production vendor receives what we want to be published and we control updates to it.
Proposed solution
Example output from EJP:
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD Journal Archiving and Interchange DTD v3.0 20080202//EN" "archivearticle3.dtd"><article article-type="research-article">Example final XML:
<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.2d1 20151215//EN" "JATS-archivearticle1.dtd"><article article-type="research-article" dtd-version="1.2d1" xmlns:ali="http://www.niso.org/schemas/ali/1.0/" xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink">Clarification needed
The @article-type on article drives the template used on the html version of the article and is also used for PubMed deposits. The @article-types currently used are: article-commentary - Insight correction - Correction discussion - Feature 1/Feature 2 editorial - Editorial research-article - all research content (ie non-feature content)
Assumptions
Tasks
@gnott to complete
Technical notes
@gnott to complete
xmlns:ali="http://www.niso.org/schemas/ali/1.0/"and there are no<ali:>tags, then this namespace tends to be dropped since it is not requiredUser interface / Wireframes
NA
@gnott @eLifeProduction