The challenges below are taken from the Sprint GoogleDoc.
Challenge 1:
arXiv is a preprint repository for physics, math, computer science and related disciplines. It allows researchers to share and access their work before it is formally published.
Go to arXiv and
Does arXiv use a DOI?
Compare these two papers:
https://arxiv.org/abs/2008.09350
https://arxiv.org/abs/2008.00287
which one of them has a persistent identifier?
Challenge 2:
Look at this paper [link]. Click on the ‘pdf’ link to download it. Do a full-text search by using control + F or command + F and search for ‘http’. Did the author use DOIs for their data and software?
Challenge 3:
What is the problem with referring to your code and software only with a URL [example] without providing a DOI?
Is anyone interested in expanding on these exercises and reviewing them? You could also add them to the main lesson under Findable. Don't forget to add the solution to the lesson.
Don't forget to check out the comments in the google doc.
Any further comments on these challenges please add them to this issue!
The challenges below are taken from the Sprint GoogleDoc.
Challenge 1:
arXiv is a preprint repository for physics, math, computer science and related disciplines. It allows researchers to share and access their work before it is formally published.
Go to arXiv and
Does arXiv use a DOI?
Compare these two papers:
https://arxiv.org/abs/2008.09350
https://arxiv.org/abs/2008.00287
which one of them has a persistent identifier?
Challenge 2:
Look at this paper [link]. Click on the ‘pdf’ link to download it. Do a full-text search by using control + F or command + F and search for ‘http’. Did the author use DOIs for their data and software?
Challenge 3:
What is the problem with referring to your code and software only with a URL [example] without providing a DOI?
Is anyone interested in expanding on these exercises and reviewing them? You could also add them to the main lesson under Findable. Don't forget to add the solution to the lesson.
Don't forget to check out the comments in the google doc.
Any further comments on these challenges please add them to this issue!