Repositories
danielskatz opened this issue · comments
Based on discussion in Section 1 of A&P google doc
- Should we provide any guidance on which repositories should be used for software?
I think an up to date list of repositories or deposit archives can be helpful for users/researchers, at least to know what the options are. Maybe as an annexe to the document?
Possible things checklist?
- version control API (with ability to provide specific, persistent, unique identifier to a particular version)
- persistence of project information (if the author deletes a project, the information about the project remains)
- persistence of the artefact? (is this required)
- enable versions/revisions to be linked
- to enable understanding of whether the information has been validated / reviewed?
- to enable understanding of whether the artefact has been validated / reviewed?
For geosciences, they've published preferred repositories.
Ask Lorraine Hwang whether the list of criteria used to choose these have been published?
Also ask Shelley Stall and @daslerr about this as well.
I think this is the project I was thinking about: http://www.copdess.org/, https://repositoryfinder.datacite.org/