Changes for page data-curation-copy

Last modified by eapapp on 2023/07/04 16:46
From version 195.1
edited by adavison
on 2023/06/14 15:35
Change comment: There is no comment for this version
To version 196.1
edited by adavison
on 2023/06/14 15:40
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -211,8 +211,6 @@
211 211  === Step by Step - Models ===
212 212  
213 213  
214 -
215 -
216 216  ==== 1. Start early ====
217 217  
218 218  It is not necessary to wait until you are ready to publish to register your model with EBRAINS.
... ... @@ -254,13 +254,12 @@
254 254  To add your model, click "+", fill in the form, then click "Add model".
255 255  
256 256  As development of your model proceeds, you can easily register new versions of the code,
257 -and new parameterizations by clicking "Add new version".
255 +and new parameterizations, by clicking "Add new version".
258 258  
259 259  If you prefer not to use the app, you can instead fill in the [[Curation request form>>https://nettskjema.no/a/277393#/]].,
260 260  and you will be contacted by e-mail with further instructions.
261 261  
262 -====
263 -5. Provide a reference dataset ====
260 +==== 5. Provide a reference dataset ====
264 264  
265 265  Once you're ready to publish your model entry in the EBRAINS Knowledge Graph,
266 266  we encourage you to provide a dataset containing the simulation results produced by your model,
... ... @@ -278,9 +278,9 @@
278 278  only members of the collab will be able to view the model entry, in the Model Catalog app
279 279  or using the Model Validation Python client.
280 280  
281 -After publication, the model will appear in the [[EBRAINS public search results>>https://search.kg.ebrains.eu/?category=Model||rel=" noopener noreferrer" target="_blank"]], and will receive a DOI.
278 +After publication, the model will appear in the [[EBRAINS public search results>>https://search.kg.ebrains.eu/?category=Model||rel="noopener noreferrer" target="_blank"]], and will receive a DOI.
282 282  
283 -To request publication, [[contact EBRAINS support>>https://ebrains.eu/support||rel=" noopener noreferrer" target="_blank"]], providing the collab name and the model name or ID.
280 +To request publication, [[contact EBRAINS support>>https://ebrains.eu/support||rel="noopener noreferrer" target="_blank"]], providing the collab name and the model name or ID.
284 284  
285 285  
286 286  Curators will then perform a number of checks:
... ... @@ -287,11 +287,11 @@
287 287  
288 288  1. Does the model description provide sufficient context to understand the purpose and use of the model?
289 289  1. Does the code repository contain a licence file, explaining the conditions for reusing the code?
290 -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.
291 291  
292 292  The curators will also take a snapshot of your model code.
293 293  
294 -* For models in public Git repositories, we archive a copy of the repository in Software Heritage.
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"]].
295 295  * 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.
296 296  
297 297  Once this is done, you will be invited to review a preview of how the model entry will appear in the KG Search,