Create Downstream deliverables page

naushinthomson commented 4 years ago

[x] Create page
[ ] Add description of what is being covered (merge fixing crossref failures page into this page)
[x] Add description of checks required on this content, compiled from current protocol documents
[x] Add examples covering correct and incorrect scenarios, as required to support checks
[x] Populate with schematron messages
[ ] Provide explanations for how to fix schematron errors and warnings
[x] Review house style document to ensure all requirements are covered by GitBook and schematron
[ ] Review schematron messages related to this topic to ensure they are user friendly
[ ] Becky approved page
[x] Melissa approved page
[x] Fred approved page
[x] James approved page
[x] Naushin approved page
[ ] Claudia approved page
[ ] Share page with Exeter and invite feedback
[ ] Revise with Exeter's suggestions

Definition of done

[ ] Page completed
[ ] Team reviewed and approved page?
[ ] Assign Fred to update the Schematron

fred-atherden commented 3 years ago

This is now ready for review - https://elifesciences.gitbook.io/productionhowto/-M1eY9ikxECYR-0OcnGt/article-details/relationships/downstream-deliveries.

JGilbert-eLife commented 3 years ago

Crossref delivery isn't on publication; it happens as soon as the article is uploaded to Continuum provided the pub date is not in the future, in which case it's just past midnight that day, as stated.

JGilbert-eLife commented 3 years ago

Other than that, no comments - thanks for putting this together, @FAtherden-eLife !

fred-atherden commented 3 years ago

Good point, thanks.

naushinthomson commented 3 years ago

For the Pubmed central section, should there be a similar note like one in the PubMed section:

PubMed is not to be confused with PubMed Central, which is a separate digital repository (more on that below).

Assuming that the page isn't read in order?

naushinthomson commented 3 years ago

The description of what to do for PMC failures is currently covered in managing production queries - I think it makes sense to keep it as it is here and for that page to link to here, would you agree? If so I can update that page. Alternatively I guess we could keep the info on both pages!

naushinthomson commented 3 years ago

Is it worth linking to a homepage for each of the downstream deliverables or would that not be possible/not required for some of these?

naushinthomson commented 3 years ago

That's all from me thanks!

fred-atherden commented 3 years ago

The description of what to do for PMC failures is currently covered in managing production queries - I think it makes sense to keep it as it is here and for that page to link to here, would you agree? If so I can update that page. Alternatively I guess we could keep the info on both pages!

:+1:

Removed the text from that page and added a link.

fred-atherden commented 3 years ago

Is it worth linking to a homepage for each of the downstream deliverables or would that not be possible/not required for some of these?

Some of these already had them. I added a couple more. There are some which I haven't added, for a few reasons:

If they are behind paywalls and we don't have subscriptions to these services, the link would just be a login page which we don't have credentials for.
It really doesn't make sense to add a singular link for some (Google Scholar and Crossref, for example).
The pages (that I can find) don't actually have any useful information pertaining to what we do, and they are liable to change (meaning we would have to update these general 'about' links). The name can just be searched instead.

griffithsc commented 3 years ago

This looks great to me, thanks Fred!

Just one tiny thing from me:

There are many different version of JATS (and other XML) they accept,

There's a typo here I think - should be 'versions'

On Tue, 29 Jun 2021 at 09:39, FAtherden-eLife @.***> wrote:

Is it worth linking to a homepage for each of the downstream deliverables or would that not be possible/not required for some of these?

Some of these already had them. I added a couple more. There are some which I haven't added, for a few reasons:

If they are behind paywalls and we don't have subscriptions to these services, the link would just be a login page which we don't have credentials for.

It really doesn't make sense to add a singular link for some (Google Scholar and Crossref, for example).

The pages (that I can find) don't actually have any useful information pertaining to what we do, and they are liable to change (meaning we would have to update these general 'about' links). The name can just be searched instead.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/elifesciences/schematron-gitbook/issues/109#issuecomment-870398458, or unsubscribe https://github.com/notifications/unsubscribe-auth/ATIHFBHUE4AOHQJGQ5ZSBI3TVGBD7ANCNFSM4NFXAGYQ .

-- Claudia Griffiths Production Assistant https://elifesciences.org/

--

elifesciences.org https://elifesciences.org

eLife Sciences Publications, Ltd is a limited liability non-profit non-stock corporation incorporated in the State of Delaware, USA, with company number 5030732, and is registered in the UK with company number FC030576 and branch number BR015634 at the address Westbrook Centre, Milton Road, Cambridge, CB4 1YG.

fred-atherden commented 3 years ago

Good spot, thanks @griffithsc!

elifesciences / schematron-wiki

Create Downstream deliverables page #109

Definition of done