Summary

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

Details

Page properties

Content

...	...	@@ -252,7 +252,7 @@
252	252	To add your model, click "+", fill in the form, then click "Add model".
253	253
254	254	As development of your model proceeds, you can easily register new versions of the code,
255		-and new parameterizations, by clicking "Add new version".
	255	+and new parameterizations by clicking "Add new version".
256	256
257	257	If you prefer not to use the app, you can instead fill in the [[Curation request form>>https://nettskjema.no/a/277393#/]].,
258	258	and you will be contacted by e-mail with further instructions.
...	...	@@ -284,11 +284,11 @@
284	284
285	285	1. Does the model description provide sufficient context to understand the purpose and use of the model?
286	286	1. Does the code repository contain a licence file, explaining the conditions for reusing the code?
287		-1. Does the model have a clearly defined version identifier (e.g. v1.0)? For models in a Git repository, the version identifier should match the name of a tag or release.
	287	+1. Does the model have a clearly defined version identifier (e.g. v1.0). For models in a Git repository, the version identifier should match the name of a tag or release.
288	288
289	289	The curators will also take a snapshot of your model code.
290	290
291		-* For models in public Git repositories, we archive a copy of the repository in [[Software Heritage>>https://www.softwareheritage.org/||rel=" noopener noreferrer" target="_blank"]].
	291	+* For models in public Git repositories, we archive a copy of the repository in Software Heritage.
292	292	* For models in a collab Bucket or Drive, we make a read-only copy of the code in a public container in the EBRAINS repository.
293	293
294	294	Once this is done, you will be invited to review a preview of how the model entry will appear in the KG Search,