Submit to Editorial Manager
Owner:
Roadmap history:
Selected for Future in Q3 update
What business value does this roadmap item create? / Which problem is this roadmap item trying to solve?
Allow reviews to be submitted directly from RevMan to the new Editorial Management System (EMS); allow the first group(s) to start using the new EMS.
How can the value delivered be measured?
At least one CRG is using the new EMS to manage their editorial process.
Which assumptions are made in relation to the value?
The new EMS provides a superior editorial, author, and peer reviewer experience.
What are the dependencies for fulfilling the business value?
The EMS vendor must have set up a test site and provided the required documentation on how RevMan can initiate a submission.
What are the risks related to this roadmap item?
What is included in the scope of this solution?
- Submit JATS:
RMW-1657
-
Getting issue details...
STATUS
- Pre-determine the DOI (CD# will be assigned in Archie when review is created in RMW; .pub# will need to be determined by RevMan based on What's New)
- Convert the review to JATS
- Package JATS, PDF, and additional data and submit via the EMS API (a specific manifest XML file, and meta-data JATS file are needed in addition to the standard files)
- Submit PDF: RMW-1658 - Getting issue details... STATUS
- Potentially: submit a copy of the validation report and document statistics (word count, study count, etc.) as a Word or PDF file
- Potentially: submit a compare versions view compared to the previous submitted version