Difference between revisions of "Best practices"
| Line 6: | Line 6: | ||
==Development== | ==Development== | ||
Best practice recommendations for software development. | Best practice recommendations for software development. | ||
| + | ===ESIP software assessment guidelines=== | ||
* [https://esipfed.github.io/Software-Assessment-Guidelines/guidelines.html ESIP Software Guidelines] | * [https://esipfed.github.io/Software-Assessment-Guidelines/guidelines.html ESIP Software Guidelines] | ||
Revision as of 11:40, July 19, 2018
Return to IM Code Registry main page
Overview
Here are some best practice recommendations for software.
Development
Best practice recommendations for software development.
ESIP software assessment guidelines
Publishing software
Best practice recommendations for publishing software.
IMCR Portal
Considerations for publishing in the IMCR Portal.
Using the controlled vocabulary
The IMCR controlled vocabulary and how to use it.
Project repository
Considerations for features to include in the project repository.
README
README are essential for orienting the user to what the project addresses.
Vignette
Vignettes are useful for demonstrating the projects functionality.
DOI
Periodic releases of the project code can be accompanied by the minting of a DOI. GitHub supports archive in with generation of a DOI, thereby making the project citable.
Test data
Test data facilitates experimentation and understanding of the projects functionality.
