You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2021. It is now read-only.
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: #25
Clinical trial info: #20
Preprint: #22
Production notes: #12
List of asset files: #11
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: #25
Clinical trial info: #20
Preprint: #22
Production notes: #12
List of asset files: #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
The text was updated successfully, but these errors were encountered: