Replace features in Archie

What business value does this epic create? / Which problem is this epic trying to solve?

Strategic fit

Link to strategy: GOAL 1 Streamlining production of reviews and simplifying editorial systems and processes

Future of review production project: Cochrane use of Porto

Hypothesis

  • (Replace with link to PID for Cochrane use of Porto) Retiring Archie will remove a substantial maintenance cost 
  • (Replace with link to PID for Cochrane use of Porto) Porto and RevMan together with EM and PM can create a better user experience for authors, editors and copy editors (question)
  • (Replace with link to PID for Cochrane use of Porto) Porto and RevMan together with EM and PM can create visibility over Cochrane's review portfolios and enable us to make more informed decisions related to:
    • which review projects to schedule
    • which authors teams to assign to projects
    • how to help authors complete review projects efficiently   

Success measure

Which assumptions are made in relation to the value?

  • The features in this epic block us from moving all groups to Porto (groups may start to use Porto earlier)
  • After Porto Phase 4 is complete, all groups can move to use Porto

What are the dependencies for full-filling the business value?

What are the risks related to this epic item?

What is included in the scope of this solution?

See Porto systems design: Phase 4 for more detailed requirements:

  • (MUST HAVE) Handle removal of users
  • (MUST HAVE) EM integration
    • The existing ReviewDB fields to track invitation status for Ingest will be used to track EM status of reviews (Out of date ticket: RMW-2958 - Getting issue details... STATUS )
    • Consider adding a field for the submission number. Consider setting the journal code (for linking).
  • (MUST HAVE) Handle de-duplication of users
  • (MUST HAVE) Management of the author byline
  • (MUST HAVE) Risk of bias 2 available to enable for Porto reviews
  • (MUST HAVE?) Changes to lifecycle management fields (unclear if must have)
  • (SHOULD HAVE) Support for group authors (Out of date ticket: RMW-2313 - Getting issue details... STATUS )
  • (SHOULD HAVE) Remove MECIR in RMW: RMW-2806 - Getting issue details... STATUS
  • (COULD HAVE) Retire editorial phase or replace it (If we retire it, remove some information on Dashboard, code to handle phase change and DB fields)
  • (COULD HAVE) Option to revert users when reverting to previous versions
  • Not sure if this story will be relevant/is already covered? RMW-2734 - Getting issue details... STATUS
  • (DON'T) Retire RevMan 5 instead of RMW-2951 - Getting issue details... STATUS

How much time do we estimate to implement this epic?