elifesciences / publish-reviewed-preprints-issues

MIT License
0 stars 0 forks source link

MSID: 96691 Version: 2 DOI: 10.1101/2024.02.20.581121 #843

Closed fred-atherden closed 2 days ago

fred-atherden commented 3 weeks ago

MSID: 96691

Version: 2

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

Step 1. Awaiting reviews

Editorial to post reviews via hypothesis

Useful links:

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

Step 2. Preview reviewed preprint

Production QC content ahead of publication

Instructions:

Useful links:

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:

Step 4: Published! PDF requested

Waiting for PDF to be generated

Useful links:

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!

elife-bot commented 1 week ago
warning: [journal-ref-text-content] This journal reference (id c4) has untagged textual content - e484.. Is it tagged correctly?
warning: [journal-ref-text-content] This journal reference (id c8) has untagged textual content - 127AP05-03.. Is it tagged correctly?
warning: [journal-ref-text-content] This journal reference (id c21) has untagged textual content - : 10.1159/000503146. DOI:. Is it tagged correctly?
warning: [journal-ref-text-content] This journal reference (id c54) has untagged textual content - : 793-802. DOI:10.1038/nn.3078, PMID: . Is it tagged correctly?
warning: [journal-ref-text-content] This journal reference (id c109) has untagged textual content - : E1237-1244. DOI:10.1152/ajpendo.00058.2013, PMID: . Is it tagged correctly?
warning: [journal-ref-text-content] This journal reference (id cs10) has untagged textual content - .2016. PMID: . Is it tagged correctly?
warning: [title-lower-case] Content of <title> element is entirely in lower-case case: Is that correct? 'h current'
info: [article-version-flag] This is preprint version 1.2.