Open nlisgo opened 1 year ago
The preprint was posted 5 days ago, full text is available but bioRxiv's API returns nothing:
curl 'https://api.biorxiv.org/meca_index/elife/all/2023.06.01.543271' | jq
{
"status": [
{
"count": 0,
"messages": "none found"
}
]
}
@QueenKraken, please can you check with Ted about this one? Thanks
I've messaged Ted.
Looks like the meca package is there now. Unblocked
Affected by https://github.com/elifesciences/enhanced-preprints-issues/issues/640 but OK to proceed in the meantime
"msas": "Cell Biology, Neuroscience" "msid": "88459" "preprintDoi": "10.1101/2023.06.01.543271"
"Reviewed Preprint posted": "2023-06-21" "Sent for peer review": "2023-05-01" "Posted to bioRxiv": "2023-05-01" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2023.06.01.543271v1")
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey
Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey
Pull request: https://github.com/elifesciences/enhanced-preprints-data/pull/107
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews
Who can help: Editorial team
Example
``` "msas": "Genetics and Genomics", "Neuroscience" "msid": "84628" "version": "1" "preprintDoi": "10.1101/2022.10.28.514241" "articleType": "Reviewed Preprint" "status": "Published from the original preprint after peer review and assessment by eLife." "Reviewed Preprint posted": "2023-01-02" "Sent for peer review": "2022-10-28" "Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2022.10.28.514241v1") Editors: Reviewing Editor Michael B Eisen University of California, Berkeley, United States Senior Editor Michael B Eisen University of California, Berkeley, United States ```Step 4: Modify manuscripts.json (no PDF)
Pull request: [PLACE LINK TO PULL REQUEST HERE] #enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Instructions to modify manuscripts.json
- Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml - Click: Run workflow - Complete the form and click "Run workflow" - A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls - Open the pull request and click the "Ready for review" button to trigger tests - Once the tests pass and you are happy with the changes the PR can be merged Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files Once the pull request is merged in it should be available a few minutes later.Request that a doi
Post the following in #enhanced-preprint:
Step 5: Awaiting search reindex
The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.
Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner. https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/Step 6: Published! Request PDF generation
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
Step 7: Introduce PDF to data folder and git repo
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json
[PLACE LINK TO PULL REQUEST HERE]
Instructions to add PDF url to manuscripts.json
- Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml - Click: Run workflow - Complete the form and click "Run workflow" - A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls - Open the pull request and click the "Ready for review" button to trigger tests - Once the tests pass and you are happy with the changes the PR can be merged Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files Once the pull request is merged in it should be available a few minutes later.Step 9: Done!