search

elifesciences / publish-reviewed-preprints-issues

MIT License
0 stars 0 forks source link

MSID: 92080 Version: 3 DOI: 10.48550/arXiv.2209.08066v5 #472

Open fred-atherden opened 3 months ago

fred-atherden commented 3 months ago

MSID: 92080

Version: 3

Preprint DOI: https://doi.org/10.48550/arXiv.2209.08066v5

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 2 months ago

@acollings, @KJT08 - were all the reviews posted for this one on Friday? I see it's press for tomorrow

acollings commented 2 months ago

I think so, but I think there was an invalid DOI error when posting. @FionaBryant did we hear more from Ryan?

Fred, is it possible to see if the reviews have been posted anyway?

fred-atherden commented 2 months ago

Thanks Andy. Yes it looks like we have in the DocMap:

Are there any others?

I'm going to move this over so we can start checking it in the meantime.

There's no preview in EPP for the RPv3, but it looks like that might be because of a missing preprint review date for the preprint v5, as temporal is complaining:

{
  "message": "Preprint doesn't have a published date",
  "source": "TypeScriptSDK",
  "stackTrace": "NonRetryableError: Preprint doesn't have a published date\n    at generateVersionJson (/app/src/activities/generate-version-json.ts:32:11)",
  "applicationFailureInfo": {
    "type": "NonRetryableError"
  }
}

I've added the details to the unmatched manuscripts spreadsheet, so that will hopefully be resolved soon and we can check.

acollings commented 2 months ago

Thanks Fred, I think 93115 is also affected

fred-atherden commented 2 months ago

Thanks Andy - RE 93115 I will check and comment in the ticket (#425)

FionaBryant commented 2 months ago

Thanks @fred-atherden and @acollings we managed to post the reviews for both 93115 (today) and 92080 (on Friday) - this issue was caused by an error in the way the DOI was entered into kotahi

fred-atherden commented 2 months ago

Thanks Fiona!

fred-atherden commented 2 months ago

This one is ready to be checked