MSID: 92683 Version: 3 DOI: 10.31219/osf.io/s6thq/v3

[fred-atherden]

MSID: 92683

Version: 3

Preprint DOI: https://doi.org/10.31219/osf.io/s6thq/v3

Step 1. Awaiting reviews

Editorial to post reviews via hypothesis

Useful links:

• DocMap: https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=92683
• New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
• Reviews on sciety: https://sciety.org/articles/activity/10.31219/osf.io/s6thq/v3

For trouble shooting (e.g. no Docmaps available):

• DocMap issue addressing: https://miro.com/app/board/uXjVNCwK6EI=/
• Explore DataHub DocMaps API: https://lookerstudio.google.com/reporting/4c2f0368-babb-4beb-b5b3-497e7e7b0f08/page/ejphD
• Unmatched submissions and preprints: https://lookerstudio.google.com/u/0/reporting/9f86204f-3bf7-477c-9b18-5c5ef141bf69/page/p_gxi57ha93c
• Unmatched manuscripts spreadsheet: https://docs.google.com/spreadsheets/d/15QcK8w-ssB7109RQEDtFpJPZ0J5HTGxoHa_2TtpMBbg/edit#gid=1336081641

Step 2. Preview reviewed preprint

Production QC content ahead of publication

Instructions:

• QC preview: https://prod--epp.elifesciences.org/previews/92683v3
• Update ticket with any problems (add blocked label)
• When QC OK, add QC OK label to ticket and add publication date and time to https://docs.google.com/spreadsheets/d/1amAlKvdLcaDp5W8Z8g77NmkwbMF5n_u89ArSqPMO8jg
• Move card to next column
• (At end of the day post link in #enhanced-preprint and ask for PDF to be generated)

Useful links:

• Preprint DOI : https://doi.org/10.31219/osf.io/s6thq/v3
• Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/92683/v3/reviews
• To update the MECA path in the docmap: https://docs.google.com/spreadsheets/d/1mctCQuNFBjSn97Lihy7_vBO6z7-N-oqyLv4clyi6zHg

Step 3: Awaiting search reindex

This step adds the reviewed preprint to the homepage: https://elifesciences.org

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Useful links:

• Jenkins pipeline to reindex search can be triggered sooner or monitored here: https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 4: Published! PDF requested

Waiting for PDF to be generated

Useful links:

• PDF tracking: https://docs.google.com/spreadsheets/d/106_XeDjmuBae7gexOTNzg60lapeqjl2aRn9DzupGyS8/

Step 5: Introduce PDF to data folder and git repo

Upload PDF to relevent folder in git repo https://github.com/elifesciences/enhanced-preprints-data/

Step 6: Done!

• [ ] Kettle is on!

[fred-atherden]

Reviews haven't yet made their way to the docmap

[fred-atherden]

warn: [ref-year-value-2] Ref with id c90 has a year element which does not contain a digit. Is it correct? (it's acceptable for this element to contain 'no date' or equivalent non-numerical information relating to year of publication)
warn: [ref-year-value-2] Ref with id c100 has a year element which does not contain a digit. Is it correct? (it's acceptable for this element to contain 'no date' or equivalent non-numerical information relating to year of publication)
warn: [ref-year-value-2] Ref with id c105 has a year element which does not contain a digit. Is it correct? (it's acceptable for this element to contain 'no date' or equivalent non-numerical information relating to year of publication)
error: [pub-id-check-5] Web reference (with id c140) has a pub-idwith a pub-id-type doi (10.1006/jtbi.2000.2150). This must be incorrect. Either the publication-type for the reference needs changing, or the pub-id should be changed to another element.
warn: [ref-person-group-type-other] This person-group inside a web reference has the person-group-type 'editor'. Is that correct?
warn: [ref-person-group-type-other] This person-group inside a confproc reference has the person-group-type 'editor'. Is that correct?
warn: [ref-person-group-type-other] This person-group inside a confproc reference has the person-group-type 'editor'. Is that correct?

[fred-atherden]

Above issues fixed