WHO: Production/Production Vendor
WHEN: Between Export from EJP/xPub and delivery to production vendor
WHERE: In eLife bot processes
WHAT: Validation email for production and Unusual elements to highlight to production
WHY: When changing vendors and also for very rare things, vendors often don't automate the process and things slip through the cracks. This would mean the production team are alerted in advance and know to look out for things. We do not reference EJP usually.
Problem / Motivation
WHO: Production/Production Vendor WHEN: Between Export from EJP/xPub and delivery to production vendor WHERE: In eLife bot processes WHAT: Validation email for production and Unusual elements to highlight to production WHY: When changing vendors and also for very rare things, vendors often don't automate the process and things slip through the cracks. This would mean the production team are alerted in advance and know to look out for things. We do not reference EJP usually.
Proposed solution
If the following is present in the EJP export, add it to the validation email to production so they know to look out for it during the production process: Reporting standards: https://github.com/elifesciences/package-ejp-raw-output-zip/issues/25 Clinical trial info: https://github.com/elifesciences/package-ejp-raw-output-zip/issues/20 Preprint: https://github.com/elifesciences/package-ejp-raw-output-zip/issues/22 Production notes: https://github.com/elifesciences/package-ejp-raw-output-zip/issues/12 List of asset files: https://github.com/elifesciences/package-ejp-raw-output-zip/issues/11
Will need a pass/fail status too.
Clarification needed and assumptions
For discussion with the @eLifeProduction team
Tasks
Technical notes
@gnott
User interface / Wireframes
Will require UX input to ensure the email is not ignored, or any unusual content in it is highlighted to the staff