Replace RevMan 5 file in Cochrane library

Owner: Rebecka hall, Rachel Craven, Gert Van Valkenhoef

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: New review format (?) & Retire RevMan 5

Hypothesis

When RevMan 5 is retired in Apr 2023, the RevMan 5 files available in the Cochrane Library (currently behind a paywall) will no longer be useful. 

Use cases relevant:

  1. Users have a RevMan 5 file stored and they want to import the data into RevMan Web
    1. From CLIB
    2. Shared by Cochrane for guidelines (replace with copy feature when Cochrane only use RevMan Web)
    3. From previous projects done in RevMan 5

Success metric

No RevMan 5 files are supplied to users of the Cochrane library by the time RevMan 5 is retired. 

Q: How problematic would it be to continue to supply RevMan 5 files for some time after RevMan 5 is retired? 

Which assumptions are made in relation to the value?

  • access to the dataset will require full text access but in the future we'd aim to make it open access

What are the dependencies for fulfilling the business value?

  • Cochrane library development: ability to download new data package
    • Small change in CLIB UI wording
  • New data format agreed as part of supplementary materials 

What are the risks related to this epic?

  • Data format not agreed in time (dependency on new review format and downloading review data for non-Cochrane users)
  • Design of data format rushed resulting in changes later on
  • Capacity from Wiley/Highwire not available in time
  • Converter introducing errors in data files

Q: How can we make sure back file convertion is not needed in future when the data format changes? 

What is included in the scope of this solution?

  • Replace RevMan 5 stats file with zip folder that contains study data and analysis data for all reviews (not just those using new review format)
  • Supply conversion tool that allows you to convert a RevMan 5 file to a package of CSV files
    • needs to be robust long-term
    • should have low operational costs and should not require updating
  1. Do we include what's in the data package in the Cochrane library or should we include what the RevMan 5 file can include?
    1. Need to include files for Study information, study characteristics and risk of bias 1 for non-study-centric reviews?
  2. Where do people access the service?
  3. How is the service hosted?
    1. Provide a service in reviewDB to see how it is being used (winner)
      1. Cochrane review
      2. File originated from CLIB
      3. Form along side user journey 
      4. Terms of use to inform which data is being logged
      5. (plus) Changes to format supported 
      6. (plus) No separate maintenance
    2. Pull out code from reviewDB and package in a separate java desktop application
      1. (minus) cumbersome for user
      2. (minus) risk of support burden
    3. Release a new version of RevMan 5 that exports the new format (with no connection to Archie)
      1. (minus) cumbersome for user
      2. (minus) risk of support burden
    4. Don't remove option to download RevMan 5, users can export 
      1. (minus) cumbersome for user
      2. (minus) risk of support burden
      3. (minus) Doesn't produce files that exactly match import formats