Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -271,15 +271,15 @@
271	271
272	272	=== Step by Step - Software ===
273	273
274		-We ask software developers to provide their metadata in the "CodeMeta" format. [[CodeMeta>>https://codemeta.github.io/]] is a common format for software metadata, supported by GitHub, Zenodo, FigShare, DataCite, and the US National Science Foundation.
	274	+1. Fill in the [[EBRAINS Curation Request Form>>https://www.ebrains.eu/tools/ebrains-curation-request-form]]. You'll be contacted by a curator with further instructions. In these instructions, you will find the links to your software and software version entries in the Knowledge Graph.
	275	+1. Enter the metadata of your software in your private space of the [[Knowledge Graph Editor>>url:https://editor.kg.ebrains.eu/]] by using the links provided by the curator. Please provide the metadata for your software as complete as possible. This makes it easier for users to find and use your software. If you have questions feel free to contact the curation support. After you have finished editing your entries, please let the curators know by replying to your ticket. We curate your metadata and get back to you, if necessary.
	276	+1. After a quality check, we integrate and publish the information to the Knowledge Graph. Your software is then searchable and usable for the neuroscience community.
275	275
276		-1. Create a codemeta.json file for your software. There are several [[tools>>https://codemeta.github.io/tools/]] to help you do this, for example the [[CodeMeta generator>>https://codemeta.github.io/codemeta-generator]] app. Please fill in as many of the fields as possible.
277		-1. Place this file in the root folder of your code repository.
278		-1. Contact [[EBRAINS support>>https://www.ebrains.eu/contact/]] to request curation of your software, letting us know the URL of your code repository. If you need help hosting your code online, please also let us know.
279		-1. After a quality check, we integrate and publish the information contained in your codemeta.json file to the Knowledge Graph. Your software is then searchable and usable for the neuroscience community.
	278	+If you want to add a new version to an already curated software, please request this via the [[EBRAINS Curation Request Form>>https://www.ebrains.eu/tools/ebrains-curation-request-form]].
280	280
281		-When you release a new version of your software, just update the codemeta.json file in your repository. We will check the repository on a regular basis, and if the version identifier has changed the Knowledge Graph will be updated accordingly.
	280	+For more information, visit our [[Guide to Software Curation in the EBRAINS Knowledge Graph>>url:https://wiki.ebrains.eu/bin/view/Collabs/swc-guide]] or see our infographic on the right.
282	282
	282	+
283	283	----
284	284
285	285	=== Sharing human subject data ===
...	...	@@ -510,8 +510,6 @@
510	510
511	511	//Institute of Neuroscience and Medicine (INM-1), Research Centre Jülich, Germany (PI: Timo Dicksheid)//
512	512
513		-//Paris-Saclay Institute of Neuroscience, CNRS, Université Paris-Saclay, France (PI: Andrew P. Davison)//
514		-
515	515	----
516	516
517	517	== References ==