Evise FAQs for Editors
Why is Elsevier building EVISE®?
Because EVISE® is Elsevier owned, we will be in full control of its development, ensuring it will meet evolving requirements of editorial systems and processes into the future, and allowing us to innovate and drive progress in submission and peer review. Development of EVISE® uses “Agile” principles which enable us to respond to feedback from end users and our own monitoring. Finally, EVISE® will be fully integrated with other key Elsevier products, including Scopus, ScienceDirect and Mendeley, offering a much enhanced user experience, and enabling us to support researchers from research though to collaboration.
What are the benefits for my journal?
Does EVISE® offer all functionality offered in EES?
Yes and no. Yes, in that your journal will not be scheduled for migration until all the functionality (which may be equivalent functionality) required for it to operate is available. No, in that you may find that a particular feature is not in EVISE®, or that EVISE® handles the need differently. We have not copied over all functionality from EES to EVISE® as many EES features were not used by most journals, or with time have become out of date / non-optimal. EVISE® is a new system that has been designed from scratch and it is structured and organized differently from EES; where EES was role-based, EVISE® is task-based.
How will users be supported, and how can users learn the new system?
Firstly considering Editors:
- The main Editor, or the most appropriate Editor spokesperson will be asked to register a journal “set-up session” where they will have the opportunity to discuss and decide upon detailed configurations and settings, together with the Publisher and Journal Manager, and receive training from an experienced trainer. The session is recorded for future reference and sharing with the other Editors for the journal.
- All handling Editors will be invited to attend a training webinar before go-live, at a timing of their choice.
- A test site will be available for all Editors to become familiar with the system before go-live.
For all users, the EVISE® self-guided e-learning tool is available. The support organization has been up and running from the moment the first journals migrated, and is available both during and after migration via our support website. With each release, a demo on the newly introduced functionality is made available. This is available from the right hand side of the e-learning welcome page, under Tools > Watch Editor Demo Video.
When will the migration take place for my journal?
Journals will be migrated from EES to EVISE® on a journal-by-journal basis during 2015/2016. The migration schedule will be determined by journal Publishers in consultation with Editors and communicated well in advance of starting migration. The migration is managed by a Deployment Lead (DL) working in close collaboration with your regular Journal Manager, Publisher, and a dedicated EVISE® Trainer, who will ensure - together with you - that your journal is configured optimally, that you are comfortable in the new system, and that the transition proceeds smoothly.
Once the EVISE® site opens, what will happen to new submissions?
New regular submissions will be directed to EVISE®. New Special Issues will be configured in EVISE® wherever possible, but new submissions to existing Special Issues in EES should continue to be submitted to EES and handled there.
Once the EVISE® site opens, what will happen to manuscripts remaining in EES?
Both EES and EVISE® will need to be used for a time after a journal’s EVISE® site goes live, while submissions in EES are completed. However, understanding the challenge working in two editorial systems creates for Editors, we will try to minimize the overlap as much as possible. We will shortly launch TrIESTE (Transfer Inflight EES Submissions To EVISE®), whereby new submissions and revised article submissions, that have not entered the review process, will be transferred to EVISE®. TrIESTE will not apply to papers already under review, or Special Issue papers. You will receive more information about this project in due course.
When will the EES site be closed?
Once the last active submission in EES for a journal is complete, the EES site will be closed.
What will happen to the data from EES?
Historical records will be maintained in accordance with our archiving policy and will be available upon request.
Will my journal's reviewer database be migrated to EVISE®?
An initial transfer of a journal's reviewer records will take place when the migration to EVISE® begins. This includes reviewers' statistics, and personal keywords and personal classifications that can be searched during reviewer search. Note that the review history (the manuscripts reviewed and recommendations given by a reviewer) will not be transferred to EVISE®. Editors will be able to invite reviewers as normal, though reviewers will need to register in EVISE® before they can proceed. When the EES site is discontinued, a final transfer will take place to ensure any newly added reviewers in EES are moved to EVISE®.
Will all journals move to EVISE®?
Yes, all journals will be moved to EVISE®. EES will be decommissioned once all journals have migrated.
When will I be contacted regarding migration for my journal?
Elsevier will contact individual Editors of all journals prior to migration and provide all migration related details well in advance. If you have any questions in the meantime you should contact your Publisher.