elifesciences / publish-reviewed-preprints-issues

MIT License
0 stars 0 forks source link

MSID: 102676 Version: 1 DOI: 10.1101/2024.08.21.608981 #1370

Open fred-atherden opened 1 month ago

fred-atherden commented 1 month ago

MSID: 102676

Version: 1

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

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 1 week ago

@gnott, any idea what might have gone wrong with the workflow here? I can see the reviews in the DocMap, but the package isn't present at s3://prod-elife-epp-meca/reviewed-preprints/102676-v1-meca.zip.

gnott commented 1 week ago

Hi @fred-atherden, the workflow reached a timed out status. The last completed step was MecaPeerReviews, next up was the MecaXslt which was attempted three times until the workflow timed out.

I don't see evidence of anything else in the worker.log, and it's hard to say exactly what was at fault. It's possible the step didn't actually start and was still trying to be scheduled, so it's not necessarily an issue with the XSLT endpoint.

I recommend we try and ingest it again to see if we get the same result.

elife-bot commented 1 week ago
! warning: [journal-ref-text-content] This journal reference (id c65) has untagged textual content - :eabe1707. doi:. Is it tagged correctly?
! warning: [journal-ref-text-content] This journal reference (id c67) has untagged textual content - :10.1128/mbio.02457-19. doi:. Is it tagged correctly?
! warning: [ref-year-value-2] Ref with id c57 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)
+ info: [article-version-flag] This is preprint version 1.1.
+ info: [permissions-info] This article is licensed under a CC BY 4.0 license. http://creativecommons.org/licenses/by/4.0/ https://elifeproduction.slab.com/posts/licensing-and-copyright-rqdavyty#permissions-info
gnott commented 1 week ago

Results! Probably an AWS / bot issue. There was a CNPIEC workflow timeout around the same time, and another (AdminEmail) during the same 15 minute gap or so, it's hard to pin down the exact reason.

fred-atherden commented 1 week ago

Makes sense - thanks for your help Graham!

fred-atherden commented 1 week ago

WOS query sent

fred-atherden commented 1 week ago

OK to proceed