WHO: Production/Production Vendor
WHEN: Between Export from EJP/xPub and delivery to production vendor
WHERE: In eLife bot processes
WHAT: Reporting standards
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
Example output from EJP:
<custom-meta-group><custom-meta>
...
<meta-name>Standard used to collect data</meta-name><meta-value>The clinical trial recruiting subjects for the current paper was published in McGowan I et al. (2013) A phase 1 randomized, double blind, placebo controlled rectal safety and acceptability study of tenofovir 1% gel (MTN-007). PLoS ONE 8: e60147. As part of that review, CONSORT checklist, CONSORT flow chart and the MTN-007 IRB approval were submitted, and are attached again with this submission. </meta-value></custom-meta>
Final published XML:
<supplementary-material id="repstand1"><object-id pub-id-type="doi">10.7554/eLife.00666.034</object-id><label>Reporting standard 1</label><caption><title>CONSORT checklist</title></caption><media mimetype="application" mime-subtype="pdf" xlink:href="elife-00666-repstand1.pdf"/>
Differences:
Standard used to collect data not used in final XML
Change tagging completely
Final XML title/caption is not provided in EJP output (although it is there in their system)
Final XML label needs to add number to end (ie 1 for first and 2 and so on if multiple)
Clarification needed and assumptions
EJP does not export the legend: ```LegendConsort Flow Chart'''
eLife has two places where the id is recorded differently, need to clarify which is right:
"repstand1" OR " "reportingstandard1"
Problem / Motivation
WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Reporting standards 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
Example output from EJP:
<custom-meta-group><custom-meta>...<meta-name>Standard used to collect data</meta-name><meta-value>The clinical trial recruiting subjects for the current paper was published in McGowan I et al. (2013) A phase 1 randomized, double blind, placebo controlled rectal safety and acceptability study of tenofovir 1% gel (MTN-007). PLoS ONE 8: e60147. As part of that review, CONSORT checklist, CONSORT flow chart and the MTN-007 IRB approval were submitted, and are attached again with this submission. </meta-value></custom-meta><file file-type='graphical_abstract' id='103046'><upload_file_nm>CONSORT checklist.pdf</upload_file_nm><order>17</order><size units='bytes'>48243</size><custom-meta><meta-name>Title</meta-name><meta-value>Reporting Standards Document</meta-value></custom-meta></file><file file-type='graphical_abstract' id='103047'><upload_file_nm>CONSORT Flow Chart.pdf</upload_file_nm><order>18</order><size units='bytes'>145174</size><custom-meta><meta-name>Title</meta-name><meta-value>Reporting Standards Document</meta-value></custom-meta></file>Submission screen:
Final published XML:
<supplementary-material id="repstand1"><object-id pub-id-type="doi">10.7554/eLife.00666.034</object-id><label>Reporting standard 1</label><caption><title>CONSORT checklist</title></caption><media mimetype="application" mime-subtype="pdf" xlink:href="elife-00666-repstand1.pdf"/>Differences: Standard used to collect data not used in final XML Change tagging completely Final XML title/caption is not provided in EJP output (although it is there in their system) Final XML label needs to add number to end (ie 1 for first and 2 and so on if multiple)
Clarification needed and assumptions
https://github.com/elifesciences/XML-mapping/blob/master/elife-00666.xml https://github.com/elifesciences/XML-mapping/blob/master/elife_file_naming_2016_08_25.md
Tasks
Technical notes
@gnott
User interface / Wireframes
NA
Linked to: #11