EJP XML manifest and Word file - Feature content

[Melissa37]

Problem / Motivation

WHO: Production/Production Vendor/Features team 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 is not set up well for feature content and as a result we currently ask the vendor to take some from the Word file and ignore the XML Metadata. Because this can be subject to change, is different from research content, and also there has been confusion, it would be better to send the vendor one clean XML manifest and Word file for them to work from, including figure sizing and template information in the manifest.

Proposed solution

Programmatically collect and delete the metadata from the word file and convert it to XML manifest; remove items not used from the XML manifest; add further processing information to the manifest, such as PDF template and figure sizing

Assumptions

• Editing metadata on EJP is not the preferred method of working for the Features team - preference is the Word file
• If there are multiple authors, adding all the affiliation details is cumbersome and providing in a Word file is preferred
• EJP does not allow for all the requirements of metadata for feature content: author bio, sub display channel

Clarification needed

• The current workflow needs to be reviewed as just replicating it might not be the best solution and some compromises could reduce the effort considerably Things to consider:
• Are 5 PDF templates necessary?
• Where in the xPub workflow will features content sit, and so how soon could xPub output what's needed without this extra effort?

---

Tasks

• [ ] Review the current workflow with production/features/dev/product
• [ ] Devise the new workflow and from that the steps required in this process

Technical notes

• To follow

User interface / Wireframes

Product to be included in the workflow discussions.

@gnott @eLifeProduction @Maelplaine @giorgiosironi

[lsh-0]

xpub has been dismantled, can this ticket be closed or replaced/updated?

[Melissa37]

@lsh-0 No it's still relevant, we just need to not use the term xpub :-)