Wiki source code of Guide to Software Curation in the EBRAINS Knowledge Graph
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
42.1 | 1 | == Audience == |
| |
14.2 | 2 | |
| |
42.1 | 3 | This guide is for software developers who would like to register their software in the EBRAINS Knowledge Graph. |
| |
1.1 | 4 | |
| |
42.1 | 5 | == Introduction == |
| |
15.2 | 6 | |
| |
42.1 | 7 | Most software changes over time, with new features or bug fixes, and new releases. For scientific research to be reproducible, it is important to keep track of which versions of software were used for a given study. This means it needs to be easy for the developers of software used in the EBRAINS Research Infrastructure to keep the information about their software up-to-date, and to register new versions of their software when they are released. |
| |
17.1 | 8 | |
| |
42.1 | 9 | For this reason, the process of adding information about software and software versions has been automated as much as possible. Two methods are available: |
| |
9.1 | 10 | |
| |
42.1 | 11 | 1. providing a codemeta.json file in your software repository. |
| 12 | 1. publishing software through Zenodo. | ||
| |
21.1 | 13 | |
| |
42.1 | 14 | == Method 1: Providing a codemeta.json file in your software repository == |
| |
21.1 | 15 | |
| |
42.1 | 16 | See [[https:~~/~~/codemeta.github.io>>https://codemeta.github.io]] |
| |
21.1 | 17 | |
| |
42.1 | 18 | More information coming soon. |
| |
21.1 | 19 | |
| |
42.1 | 20 | == Method 2: Publishing software through Zenodo == |
| |
21.1 | 21 | |
| |
42.1 | 22 | More information coming soon. |