WHO: Production/Production Vendor
WHEN: Between Export from EJP/xPub and delivery to production vendor
WHERE: In eLife bot processes
WHAT: Ethics and animal experimentation
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 export:
<back><fn-group content-type="ethics-information"><title>Ethics</title><fn fn-type="other"><p>Clinical trial registration CB7778886452342</p></fn><fn fn-type="other"><p>Human subjects: All participants gave written informed consent, and the study was approved by the Institutional Review Board of the Department of Psychology at the University of Basel. All experiments were performed in accordance with the relevant guidelines and regulations.</p></fn><fn fn-type="other"><p>Animal experimentation: If there were animal subjects involved in the study the approval number for the research along with protocol approval would be listed here.</p></fn></fn-group>
...
</back>
Final XML:
<back>
...
<fn-group content-type="ethics-information"><title>Ethics</title><fn fn-type="other"><p>Human subjects: All participants gave written informed consent, and the study was approved by the Institutional Review Board of the Department of Psychology at the University of Basel. All experiments were performed in accordance with the relevant guidelines and regulations.</p></fn><fn fn-type="other"><p>Animal subjects: If there were animal subjects involved in the study the approval number for the research along with protocol approval would be listed here.</p></fn><fn fn-type="other"><p>If this article was part of a clinical trial the Clinical trial registry and ID would be listed here, for example:</p></fn-group>
Problem / Motivation
WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Ethics and animal experimentation 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 export:
<back><fn-group content-type="ethics-information"><title>Ethics</title><fn fn-type="other"><p>Clinical trial registration CB7778886452342</p></fn><fn fn-type="other"><p>Human subjects: All participants gave written informed consent, and the study was approved by the Institutional Review Board of the Department of Psychology at the University of Basel. All experiments were performed in accordance with the relevant guidelines and regulations.</p></fn><fn fn-type="other"><p>Animal experimentation: If there were animal subjects involved in the study the approval number for the research along with protocol approval would be listed here.</p></fn></fn-group>...</back>Final XML:
<back>...<fn-group content-type="ethics-information"><title>Ethics</title><fn fn-type="other"><p>Human subjects: All participants gave written informed consent, and the study was approved by the Institutional Review Board of the Department of Psychology at the University of Basel. All experiments were performed in accordance with the relevant guidelines and regulations.</p></fn><fn fn-type="other"><p>Animal subjects: If there were animal subjects involved in the study the approval number for the research along with protocol approval would be listed here.</p></fn><fn fn-type="other"><p>If this article was part of a clinical trial the Clinical trial registry and ID would be listed here, for example:</p></fn-group>...
</back>Clarification needed and assumptions
Tasks
Technical notes
@gnott
User interface / Wireframes
NA