ljhwang
commented
8 years ago I added some slight modifications to the google doc:
A repository that archives and/or maintains a collection of software. The repository would like to address usage and impact of software in its holding. Usage would aid potential users whether the software is being actively maintained or developed or has been superseded. Both would help repository know how to direct resources e.g. maintenance, training etc.
Requirements:
- Code name ideally, a unique identifier
- Relationships to previous versions
- Connect to repository
- Connect to research
A repository that archives and/or maintains a collection of software. The repository would like to address usage and impact of software in its holding. Usage would aid potential users whether the software is being actively maintained or developed or has been superceded. Impact would help repository know how to direct resources e.g. maintainence, training etc.
In all such cases, as a repository the easiest way to find this would be a UID. Desired would be repository name and/url - this creates exposure/name recognition
_similar _to Funder case