WHO: Production/Production Vendor
WHEN: Between Export from EJP/xPub and delivery to production vendor
WHERE: In eLife bot processes
WHAT: LaTex files
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
EJP exports, for example the following LaTex files:
<file file-type='art_file' id='868721'><upload_file_nm>resultsresults.tex</upload_file_nm><order>2</order><size units='bytes'>31941</size></file>
@JGilbert-eLife to review this ticket and add detail as necessary
Would these need to all be present in the JATS XML file or could they be part of another manifest file?
Problem / Motivation
WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: LaTex files 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
EJP exports, for example the following LaTex files:
<file file-type='art_file' id='868721'><upload_file_nm>resultsresults.tex</upload_file_nm><order>2</order><size units='bytes'>31941</size></file>
<file file-type='supp_latex' id='868722'><upload_file_nm>resultsresults.bib</upload_file_nm><order>3</order><size units='bytes'>7504</size></file>
<file file-type='supp_latex' id='868747'><upload_file_nm>elife.cls</upload_file_nm><order>9</order><size units='bytes'>12072</size></file>
Clarification needed and assumptions
@JGilbert-eLife to review this ticket and add detail as necessary Would these need to all be present in the JATS XML file or could they be part of another manifest file?
Tasks
Technical notes
@gnott
User interface / Wireframes
NA