Update Data availability page

[eLifeProduction]

• [x] Add clarification on what to do about Github repos entered as generated datasets:

(If the repo includes source data, this can stay in the generated datasets section. No need to add a software ref but code still needs to be forked if it is mentioned in the DAS?)

• [x] Becky approved page
• [x] Melissa approved page
• [x] Fred approved page
• [x] James approved page
• [x] Naushin approved page
• [x] Share page with Exeter if relevant

Definition of done

• [x] Team reviewed and approved page?
• [ ] Add changelog to page
• [ ] Assign Fred to update the Schematron if relevant

[JGilbert-eLife]

@naushinthomson @bcollins14 @FAtherden-eLife @Melissa37 - I've added this section. Is what I have sufficient? I was a little unsure how much information was required for this.

https://app.gitbook.com/@elifesciences/s/productionhowto/article-details/content/data-availability#github-repositories-entered-as-datasets

[fred-atherden]

Looks good to me. Do we need to check with Editorial in case the data could be more appropriately placed elsewhere (and this was missed during Editorial QA)? Or do we just proceed?

[JGilbert-eLife]

I'm not sure about that. I don't think we've ever recommended the authors move their data, but then most of the examples I can recall had both code and data.

[naushinthomson]

If it is clear from the entered details or the repository page that data is present, it is acceptable to retain the dataset entry.

Would we then also fork the repository? I think that was my main reason behind adding this update because I wasn't sure.

[naushinthomson]

Otherwise, all good from me!

[bcollins14]

All good from me too, thanks!

[JGilbert-eLife]

I think this was actually completed but I didn't sign off on it. I will update the text once everything is OKed for code archiving with Exeter, then share it with them explicitly.

[JGilbert-eLife]

I've just shared this with Exeter.