Information about whether an article has been selected for PoA'd

[Melissa37]

Problem / Motivation

WHO: Editorial/Production/eLife bot/Production vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Decide whether to include this information in output to production vendor WHY: In EJP the author decides whether they want to PoA or not, and this info is transmitted to the Production vendor by a piece of metadata in the XML manifest

Proposed solution

EJP export: <custom-meta><meta-name>PoA</meta-name><meta-value>No</meta-value></custom-meta>

Information given to Exeter at set up: This indicates whether it was PoA'd before being exported to production. It is pretty reliable, but it not the definitive source of truth. The eLife RSS feed is the source of truth for this step. It is possible for an article to change status to PoA yes (from no) after export to production.

Clarification needed and assumptions

• Require detail about how this works in the editorial process @JGilbert-eLife
• If this was not required by the production vendor would it simplify procedures for edge-cases for editorial and production staff?
• Is this necessary for the production vendor or can they add the PoA date to any article in the production process once it's appeared on the eLife site?

---

Tasks

• [ ] Review process
• [ ] Potentially drop from the export XML

Technical notes

NA

User interface / Wireframes

NA

[gnott]

Is there ever a chance the raw package is exported before the PoA article is published?

Something for discussion maybe you could clarify for me @Melissa37 is how much different is a PoA export package from a raw article package? When an article is "accepted" does that mean it can be published as a PoA, and all the assets for the raw zip are finalised?

[Melissa37]

Is there ever a chance the raw package is exported before the PoA article is published?

Yes. That is why the vendor cannot rely on this. I ahve updated the spec: It is possible for an article to change status to PoA yes (from no) after export to production.

Something for discussion maybe you could clarify for me @Melissa37 is how much different is a PoA export package from a raw article package? When an article is "accepted" does that mean it can be published as a PoA, and all the assets for the raw zip are finalised?

Yes. It's interesting because articles that are PoA'd go through QC/clean up on EJP as the submission screens are used to generate the PoA XML. However, at VoR, the vendor trusts the Word file more than the EJP output because someone has not manually crosschecked the values and updated EJP. This has the consequence that for non-PoA'd content the vendor gets less clean metadata, but it's not worth the effort and cost of cleaning up EJP for this process as they'd rather take from the Word file anyway.

At the point of PoA all the assets are finalised, although they are still subject to change during production. There is, again, a level fo QC on the content for PoA because once it's published it's out there. For the export to the production vendor, this can be done during the production process so there is less imperative to get it right at export.

I ahve attached our PoA checks document for reference - this contains the QC completed for PoA content. This is not done for articles that are not PoA'd. @JGilbert-eLife do you have anything to add to this?

Publish on Accept Protocols.docx

[JGilbert-eLife]

I don't think I have much to add here. It doesn't sound like there would be any issue with PoA version 2s, which is the one case that might involve updates in eJP after the initial PoA and export for typesetting. However, do we need to consider re-exporting articles in general somewhere? Sorry, that's probably a bit of a tangent from this!

Thanks,

James