elifesciences / enhanced-preprints-import

Enhanced Preprints import system
1 stars 0 forks source link

MSID: 88375 Version: 2 DOI: 10.1101/2023.05.24.542110 #3674

Open nlisgo opened 6 months ago

nlisgo commented 6 months ago

MSID: 88375

Version: 2

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

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!

fred-atherden commented 5 months ago

Schematron:

error: <pub-id pub-id="doi"> in reference (id=c30) does not contain a valid DOI: '1007-1019.10.1016/j.neuron.2016.10.023'. error: <pub-id pub-id="doi"> in reference (id=c34) does not contain a valid DOI: '114810.10.1016/j.ejmech.2022.114810'.

JGilbert-eLife commented 5 months ago

@acollings There's no author response on this revised preprint. Is that correct?

JGilbert-eLife commented 5 months ago

Oh, never mind! Looks like there's been a snafu with this ticket - it should be a v2, but all the links etc are for the v1. https://prod--epp.elifesciences.org/reviewed-preprints/88375v2 does not work, so I assume that something has gone pretty amiss. @fred-atherden can you help here?

(The meca package is for the v1 too, so I can't correct the DOI issue yet.)

fred-atherden commented 5 months ago

Ah thanks @JGilbert-eLife. I've updated the ticket links and moved the meca package for the mv2 over. Obviously those schematron validation messages will be for the v1 so can be ignored.

There aren't any schematron messages for the v2.