WHO: Production
WHEN: Between Export from EJP/xPub and delivery to production vendor/new specification for XML delivered to website
WHERE: In eLife bot processes
WHAT: A means to compare the exported reviewer information against that stored in eJP for the full submission to ensure that we are getting the correct details.
WHY: eJP has not been exporting the correct information for reviewers, so having validation for this seems sensible.
Proposed solution
Use the Data Pipeline project work that has been done to collate eJP data in an eLife datasource in order to validate the reviewers exported in the XML. These should match the reviewers who have agreed to reveal their identity on the full submission, not those on any of the other versions of the article.
Clarification needed and assumptions
We will need to talk to @de-code about how to do this and what information is available in the data pipeline.
Tasks
[ ] Talk to @de-code about availability of reviewers and reveal-identity status in data pipeline
Problem / Motivation
WHO: Production WHEN: Between Export from EJP/xPub and delivery to production vendor/new specification for XML delivered to website WHERE: In eLife bot processes WHAT: A means to compare the exported reviewer information against that stored in eJP for the full submission to ensure that we are getting the correct details. WHY: eJP has not been exporting the correct information for reviewers, so having validation for this seems sensible.
Proposed solution
Use the Data Pipeline project work that has been done to collate eJP data in an eLife datasource in order to validate the reviewers exported in the XML. These should match the reviewers who have agreed to reveal their identity on the full submission, not those on any of the other versions of the article.
Clarification needed and assumptions
We will need to talk to @de-code about how to do this and what information is available in the data pipeline.
Tasks
Technical notes
@gnott , @Melissa37