Attention: The EBRAINS drive will be unavailable for most of the weekend starting the 25th October. Although the Lab is availble while the Drive is down, files that are stored in the Drive will not be loaded and you will be unable to save documents directly on the Lab.


Last modified by adavison on 2024/11/13 10:32
From version 42.1
edited by adavison
on 2024/11/08 17:27
Change comment: There is no comment for this version
To version 42.2
edited by adavison
on 2024/11/13 10:22
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,9 +13,8 @@
13 13  
14 14  == Method 1: Providing a codemeta.json file in your software repository ==
15 15  
16 -See [[https:~~/~~/codemeta.github.io>>https://codemeta.github.io]]
16 +[[CodeMeta>>https://codemeta.github.io/||rel=" noopener noreferrer" target="_blank"]] is a project developed by a number of actors involved in sharing software, including Zenodo, GitHub, DataCite and Software Heritage, to provide a common specification for software metadata. EBRAINS has adopted the CodeMeta specification to maximise interoperability with other software repositories, and to minimise the added burden on software developers. A web form for generating codemeta.json files is available at [[https:~~/~~/codemeta.github.io/codemeta-generator/>>https://codemeta.github.io/codemeta-generator/||rel=" noopener noreferrer" target="_blank"]], provided by Software Heritage.
17 17  
18 -More information coming soon.
19 19  
20 20  == Method 2: Publishing software through Zenodo ==
21 21