MSID: 100527 Version: 2 DOI: 10.1101/2024.07.15.603208

[fred-atherden]

MSID: 100527

Version: 2

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

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

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/100527v2
• 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.07.15.603208
• Confirm reviews returned by EPP: https://prod--epp.elifesciences.org/api/reviewed-preprints/100527/v2/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!

[rkcook312]

production please correct author name from Ferraci to Ferracci, please also correct in v1

[elife-bot]

elife-bot workflow message:

ValidateJatsDtd, validation error for version DOI 10.7554/eLife.100527.2 file tmp/2024-09-20.13.30.36.Publish.IngestMeca_100527.ValidateJatsDtd/input_dir/content/603208.xml: [{'line': '3940', 'column': '201', 'message': "Element type 'i' must be declared."}, {'line': '3940', 'column': '406', 'message': "The content of element type 'p' must match '(email|ext-link|uri|inline-supplementary-material|related-article|related-object|hr|bold|fixed-case|italic|monospace|overline|overline-start|overline-end|roman|sans-serif|sc|strike|underline|underline-start|underline-end|ruby|alternatives|inline-graphic|inline-media|private-char|chem-struct|inline-formula|tex-math|mml:math|abbrev|index-term|index-term-range-end|milestone-end|milestone-start|named-content|styled-content|fn|target|xref|sub|sup|x|address|answer|answer-set|array|block-alternatives|boxed-text|chem-struct-wrap|code|explanation|fig|fig-group|graphic|media|preformat|question|question-wrap|question-wrap-group|supplementary-material|table-wrap|table-wrap-group|disp-formula|disp-formula-group|citation-alternatives|element-citation|mixed-citation|nlm-citation|award-id|funding-source|open-access|def-list|list|ack|disp-quote|speech|statement|verse-group)'."}, {'line': '3944', 'column': '212', 'message': "Element type 'i' must be declared."}, {'line': '3944', 'column': '232', 'message': "Element type 'i' must be declared."}, {'line': '3944', 'column': '392', 'message': "The content of element type 'p' must match '(email|ext-link|uri|inline-supplementary-material|related-article|related-object|hr|bold|fixed-case|italic|monospace|overline|overline-start|overline-end|roman|sans-serif|sc|strike|underline|underline-start|underline-end|ruby|alternatives|inline-graphic|inline-media|private-char|chem-struct|inline-formula|tex-math|mml:math|abbrev|index-term|index-term-range-end|milestone-end|milestone-start|named-content|styled-content|fn|target|xref|sub|sup|x|address|answer|answer-set|array|block-alternatives|boxed-text|chem-struct-wrap|code|explanation|fig|fig-group|graphic|media|preformat|question|question-wrap|question-wrap-group|supplementary-material|table-wrap|table-wrap-group|disp-formula|disp-formula-group|citation-alternatives|element-citation|mixed-citation|nlm-citation|award-id|funding-source|open-access|def-list|list|ack|disp-quote|speech|statement|verse-group)'."}]

[elife-bot]

warning: [journal-ref-text-content] This journal reference (id c109) has untagged textual content - , 51. doi:. Is it tagged correctly?
warning: [title-upper-case] Content of <title> element is entirely in upper case: Is that correct? 'LEGENDS SUPPLEMENTAL FIGURES'
warning: [title-upper-case] Content of <title> element is entirely in upper case: Is that correct? 'LEGENDS SUPPLEMENTAL TABLES'
info: [article-version-flag] This is preprint version 1.2.

[JGilbert-eLife]

Need to fix emails