EJP XML manifest items to convert: Reviewer details

[Melissa37]

Problem / Motivation

WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Reviewer details 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="reviewer" id="author-112058"><name><surname>Gisselbrecht</surname><given-names>Steve</given-names></name><role>Reviewer</role><aff><institution>Harvard University</institution><country>United States</country></aff></contrib></contrib-group>

Sample final XML: <sub-article article-type="decision-letter" id="SA1"> ... <contrib-group><contrib contrib-type="reviewer"><name><surname>Darian-Smith</surname><given-names>Corinna </given-names></name><role>Reviewer</role><aff><institution>Stanford University</institution><country>United States</country></aff></contrib>

Clarification needed and assumptions

• Assumption - can be 0,1 or multiple reviewers
• Question: should we add ejp id to these actors in the final xml?
• Do not exist in main article XML, only in the decision letter stub
• How we deal with this depends on the Texture UI and where it will display and whether it should be submitted with the decision letter XML or the Main article XML

---

Tasks

• [ ] To be discussed with Texture and eLife dev/product

Technical notes

@gnott

User interface / Wireframes

Not sure - Texture?

[Melissa37]

Is added to the kitchen sink example anyway