MSID: 101181 Version: 1 DOI: 10.1101/2024.06.12.598701

[fred-atherden]

MSID: 101181

Version: 1

Preprint DOI: https://doi.org/10.1101/2024.06.12.598701

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=101181
• New model tracking: https://docs.google.com/spreadsheets/d/1_fHaoOy7hjyocptKtVJRijeNpUY4hBS7Ck_aVmx6ZJk/
• Reviews on sciety: https://sciety.org/articles/activity/10.1101/2024.06.12.598701

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/101181v1
• 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.1101/2024.06.12.598701
• Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/101181/v1/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!

[elife-bot]

error: [journal-ref-article-title] This journal reference (id c17) has no article-title element.
warning: [journal-ref-text-content] This journal reference (id c17) has untagged textual content - . Available from: . Is it tagged correctly?
warning: [journal-ref-text-content] This journal reference (id c20) has untagged textual content - . , , , editors. ; Feb 17;. Is it tagged correctly?
warning: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c5) has a publication-type='other'. Is that correct?
warning: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c11) has a publication-type='other'. Is that correct?
warning: [mixed-citation-other-publication-flag] mixed-citation in reference (id=c13) has a publication-type='other'. Is that correct?
info: [article-version-flag] This is preprint version 1.2.
warning: [article-corresp] The number of corresponding authors and distinct emails is the same, but a match between them has been unable to be made. As its stands the corresp will display on EPP: *sz397@cam.ac.uk; alexandre.leitao@research.fchampalimaud.org; fmj1001@cam.ac.uk.
warning: [ed-report-kwd-group-2] evidence-strength type kwd-group has 2 keywords: Convincing; Solid. This is unusual, please check this is correct.

[naushinthomson]

@acollings Should convincing be removed as a keyword here?

[acollings]

Hi @naushinthomson yes, fixed!