Changes for page data-curation-copy
Last modified by eapapp on 2023/07/04 16:46
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 6 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki.e apapp1 +XWiki.ingrreit - Content
-
... ... @@ -17,9 +17,9 @@ 17 17 {{/html}} 18 18 19 19 20 -== Publishing neuroscience data, models and software via EBRAINS == 20 +(% class="wikigeneratedid" id="HPublishingneurosciencedata2CmodelsandsoftwareviaEBRAINS" %) 21 +(% style="font-size:2em" %)**Publishing neuroscience data, models and software via EBRAINS** 21 21 22 - 23 23 (% class="wikigeneratedid" %) 24 24 The aim of this collab is to provide you with detailed information about publishing data, simulations, computational models, and software via EBRAINS. If you want a quick overview of the sharing process, see [[https:~~/~~/ebrains.eu/service/share-data>>https://ebrains.eu/service/share-data]]. 25 25 ... ... @@ -83,13 +83,13 @@ 83 83 //to share data on EBRAINS: // 84 84 // // 85 85 [[[[image:image-20230324171114-2.png||height="150" width="106"]]>>https://drive.ebrains.eu/f/dfd374b9b43a458192e9/]] 86 - 87 - 88 88 ))) 89 89 90 90 91 91 ==== **1. Provide some general information about your dataset** ==== 92 92 91 + 92 + 93 93 (% style="margin-right:10px" %)[[image:https://lh3.googleusercontent.com/zh7TvO6w04YGW9jIhfhmdT6CexdGs-AWOLfJXKRq7-tdHOu6ar1rOQx8o4rZevrjXqgPZ7-Ejv4b6X9XpgXuHpdUXi-mBTHIUnv5Vz-DktHt0sP-PZ3gE8XgZid3TV3swV1uTCBhHx11ge0pjP7RVxswGQ=s2048||height="85px;" width="91px;"]](%%)** Fill in the [[Curation request form>>https://nettskjema.no/a/277393#/]]. ** 94 94 95 95 This form collects preliminary information about your data, allowing us to assess whether the dataset fits within the scope of EBRAINS. The submission generates a curation ID allowing us to track the case. ... ... @@ -104,16 +104,26 @@ 104 104 105 105 ==== **2. Upload data ** ==== 106 106 107 +(% class="box floatinginfobox" id="share-data-infographic" %) 108 +((( 109 +(% style="text-align:center" %) 110 +//Download our infographic// 111 +//with guidelines 112 +on data organization: // 107 107 114 +(% style="text-align:center" %) 115 +[[[[image:image-20230621121014-1.png||height="150" width="106"]]>>https://drive.ebrains.eu/lib/f5cf4964-f095-49bd-8c34-e4ffda05a497/file/ebrains-infographic-data-organisation.pdf/]] 116 +))) 117 + 108 108 (% style="margin-right:10px" %)[[image:https://lh5.googleusercontent.com/sieKO-kW8O18iPaUyonwyo4UfHBmtc2E9BDnjbx52j6J_uGmm-OzGAo7sloMk3sYwKa6QW3hYQsOA9N4H7uGQpca088Wrk0Nurpt_J3B0-NSbcaPNdZIh21otQcG6jnAxLGiKoEvkTyaDGTMk3fu7me8mQ=s2048||height="94px;" width="94px;"]](%%)**Ensure data is structured consistently prior to upload. ** 109 109 110 -We look for organized data, not organized according to our standard. This is to support the broadest degree of sharing possible. We do however require that the data is organized in a consistent and precise manner. Please see our// //[[ collection ofguidelines on data organization>>https://drive.ebrains.eu/smart-link/25299f04-c4e5-4028-8f5f-3b8208f9a532/]] for further guidance.120 +We look for organized data, not organized according to our standard. This is to support the broadest degree of sharing possible. We do however require that the data is organized in a consistent and precise manner. Please see our// //[[guidelines on data organization>>https://drive.ebrains.eu/smart-link/25299f04-c4e5-4028-8f5f-3b8208f9a532/]] for further guidance. 111 111 112 112 (% style="margin-right:10px" %)[[image:https://lh5.googleusercontent.com/EWtYwfVlbeC-jqPasgmzidqc50GrkKIEgwXeUeql8aaMHIukmFdWEy0nufVWWATbxDDK3XwwZEDmASrbpCsBk1u0HpAd8x4ZgAMsMPRcWyrb9etlV6FgKE_QN2e6SqKxHE0rzkR8uI1rRW_5z21TFGYVnw=s2048||height="91px;" width="91px;"]](%%)**Upload data to EBRAINS Storage, either using a drag-and-drop solution (opt. 1) or an interactive python script (opt. 2).** 113 113 114 - //**Opt. 1. **//For smaller datasets with a reasonable amount of files, we recommend using the Collab-Bucket solution (drag-and-drop). A Collab Bucket must first be assigned to a dataset, which happens when a datasets is accepted for sharing.124 +**Opt. 1. **For smaller datasets with a reasonable amount of files, we recommend using the Collab-Bucket solution (drag-and-drop). A Collab Bucket must first be assigned to a dataset, which happens when a datasets is accepted for sharing. 115 115 116 - //**Opt. 2. **//For larger datasets or datasets with a large amount of files, we recommend using a programmatic approach. The [[python script>>https://github.com/eapapp/ebrains-data-storage/tree/main/data-proxy]] is interactive and does not require any additional programming.126 +**Opt. 2. **For larger datasets or datasets with a large amount of files, we recommend using a programmatic approach. The [[python script>>https://github.com/eapapp/ebrains-data-storage/tree/main/data-proxy]] is interactive and does not require any additional programming. 117 117 118 118 119 119 EBRAINS offers secure, long-term storage at [[CSCS Swiss National Supercomputing Centre>>url:https://www.cscs.ch/]], with currently no upper limit of storage capacity. ... ... @@ -124,11 +124,11 @@ 124 124 ==== **3. Submit metadata** ==== 125 125 126 126 127 -(% style="margin-right:10px" %)[[image:https://lh5.googleusercontent.com/WS4T2LhF9znWWChn3Z550agLrrb-KTWdYVsJSv0lh4cGjKbjuN1WV68WER9xkYqi1UqN7KYZz7bImYz3_TpOuTuvma7T192QUiUZoyJVPk1fj5NSDSQh_kpIeBufAOdDtsDRpPKK_P5EDPqRCTAaOTNyCw=s2048||height="91px;" width="91px;"]](%%)**Submit metadata using the **[[EBRAINS Metadata Wizard>>https://ebrains-metadata-wizard.apps.hbp.eu/]]** (opt. 1), or throughdirect interactionwiththe Knowledge Graph (opt. 2) **137 +(% style="margin-right:10px" %)[[image:https://lh5.googleusercontent.com/WS4T2LhF9znWWChn3Z550agLrrb-KTWdYVsJSv0lh4cGjKbjuN1WV68WER9xkYqi1UqN7KYZz7bImYz3_TpOuTuvma7T192QUiUZoyJVPk1fj5NSDSQh_kpIeBufAOdDtsDRpPKK_P5EDPqRCTAaOTNyCw=s2048||height="91px;" width="91px;"]](%%)**Submit metadata using the **[[EBRAINS Metadata Wizard>>https://ebrains-metadata-wizard.apps.hbp.eu/]]** (opt. 1), or directly via the Knowledge Graph (opt. 2) ** 128 128 129 - //**Opt. 1.**//Manually submit the minimal required metadata via the [[EBRAINS Wizard>>https://ebrains-metadata-wizard.apps.hbp.eu/]]. The minimal required metadata covers extended bibliographic information necessary to publish your dataset on EBRAINS. The submitted information, including uploaded files, will be sent to the Curation team automatically139 +**Opt. 1.** Manually submit the minimal required metadata via the [[EBRAINS Metadata Wizard>>https://ebrains-metadata-wizard.apps.hbp.eu/]]. The minimal required metadata covers extended bibliographic information necessary to publish your dataset on EBRAINS. The submitted information, including uploaded files, will be sent to the Curation team automatically 130 130 131 - //**Opt. 2.**//To go beyond the minimal required metadata, you can directly interact with the Knowledge Graph (KG) in your private space. Within the private space, you can upload metadata and interact with them, moreover you can connect your metadata to existing publicly accessible entries. Access to your private space is granted upon the initiation of the curation process. You can access your private space via:141 +**Opt. 2.** To go beyond the minimal required metadata, you can directly interact with the Knowledge Graph (KG) in your private space. Within the private space, you can upload metadata and interact with them, moreover you can connect your metadata to existing publicly accessible entries. Access to your private space is granted upon the initiation of the curation process. You can access your private space via: 132 132 133 133 * Knowledge Graph Editor: This User Interface allows you to manually enter metadata into your KG space and validate metadata that are programmatically uploaded. The Editor contains a basic set of openMINDS metadata templates, but can be extended to the full openMINDS metadata model on request. Access is granted once the request is accepted. 134 134 * [[Fairgraph>>https://fairgraph.readthedocs.io/en/stable/]]: This is the recommended software tool for programmatic interaction with the KG. It allows you to programmatically upload openMINDS compliant metadata into your KG space and interact with existing metadata. ... ... @@ -137,10 +137,12 @@ 137 137 Datasets published through the EBRAINS Knowledge Graph have to be registered using **openMINDS compliant metadata** delivered as JSON-LD files. See this summary table for an overview of [[the minimally required openMINDS properties for publishing>>https://drive.ebrains.eu/lib/47995dbc-f576-4008-a76c-eefbfd818529/file/ebrains-minimum-required-metadata.xlsx]] on EBRAINS. 138 138 139 139 140 -==== **4. Write a Data Descriptor 150 +==== **4. Write a Data Descriptor** ==== 141 141 142 -(% style="margin-right:10px" %)[[image:https://lh4.googleusercontent.com/lMYEKOXzejbBydOdotWWteXQo7j363xRyntBGjcPZVEdtIU1CJYX7q1STpdr2JPZK4hpWWXk20UlkUOqDGL5kX6vnQVBSdrfUo6EGfXOwpuGq1Uygv0tTZJ0lRO6voJvg56QC2mufvjAcRXGfAKFOjtc6w=s2048||height="94px;" width="94px;"]](%%)**Write a data descriptor by filling in **[[this template>>https://drive.ebrains.eu/f/a2e07c95b1a54090bbbc/?dl=1]]** . ** 143 143 153 + 154 +(% style="margin-right:10px" %)[[image:https://lh4.googleusercontent.com/lMYEKOXzejbBydOdotWWteXQo7j363xRyntBGjcPZVEdtIU1CJYX7q1STpdr2JPZK4hpWWXk20UlkUOqDGL5kX6vnQVBSdrfUo6EGfXOwpuGq1Uygv0tTZJ0lRO6voJvg56QC2mufvjAcRXGfAKFOjtc6w=s2048||height="94px;" width="94px;"]](%%)**Write a data descriptor by filling in **[[this template>>https://drive.ebrains.eu/f/a2e07c95b1a54090bbbc/?dl=1]]**.** 155 + 144 144 The Data Descriptor is a document helping others interpret and reuse (and prevent misuse) of your data, and is critical to achieve a basic level of FAIR. The document will be uploaded in the repository of the data, shared as a PDF. 145 145 146 146 See our infographic about the data descriptor for inspiration or guidance. ... ... @@ -149,64 +149,115 @@ 149 149 150 150 Journal publications sufficiently describing the shared data, such as made available through [[Nature Scientific Data>>http://www.nature.com/sdata/about]], [[Elsevier Data in Brief>>http://www.journals.elsevier.com/data-in-brief/]], [[BMC Data note>>https://bmcresnotes.biomedcentral.com/submission-guidelines/preparing-your-manuscript/data-note]] and more, can replace the EBRAINS Data Descriptor. 151 151 164 + 152 152 (% class="box floatinginfobox" id="data-descriptor-infographic" %) 153 153 ((( 154 154 (% style="text-align:center" %) 155 -//Download our infographic : //156 - //The EBRAINS Data//157 -//Descriptor at a glance//168 +//Download our infographic 169 +about the EBRAINS Data// 170 +//Descriptor// 158 158 // // 159 159 [[[[image:image-20230324171109-1.png||height="150" width="106"]]>>https://drive.ebrains.eu/f/c1ccb78be52e4bdba7cf/]] 160 - 161 161 ))) 162 162 163 -==== **5. Preview and publish 175 +==== **5. Preview and publish** ==== 164 164 165 165 166 166 (% style="margin-right:10px" %)[[image:https://lh4.googleusercontent.com/XqT26Q4yWJK26cjtjhI4ToXoZZMxhT9LimG4Hk9mePxy0-KPKgpVIzcuiP5mOQowBgf2JjkrWUq2VbCmafWWZPJplEZALnFOlCZHLlQgzOx7fFwoBteyi_IlMLkPBS9vtOcdNIZ59HyLnQz4RsTQ0lUrSw=s2048||height="91px;" width="91px;"]](%%)**Preview and approve the release of your dataset. ** 179 + 167 167 Once a Curator has assembled the dataset in the EBRAINS Knowledge Graph, combining the data, metadata and data descriptor, the data provider will receive a private URL for previewing the dataset prior to release. We need an official approval from the data custodian{{footnote}}The Data Custodian is responsible for the content and quality of the Data and metadata, and is the person to be contacted by EBRAINS CS in case of any misconduct related to the Data. It is the obligation of a Data Custodian to keep EBRAINS informed about changes in the contact information of the authors of the Datasets provided by them ([[EBRAINS Data Provision Protocol - version 1.1>>https://strapi-prod.sos-ch-dk-2.exo.io/EBRAINS_Data_Provision_Protocol_dfe0dcb104.pdf]]).{{/footnote}} to release the dataset. Once released, a [[DataCite DOI>>https://datacite.org/]] will be generated for the dataset. If the identical data collection has received a DOI elsewhere, we recommend re-using the already issued DOI. 168 168 169 169 183 + 184 + 170 170 ---- 171 171 172 -=== =**Sharinghuman subjectdata**====187 +=== Step by Step - Models === 173 173 174 -(% class="box floatinginfobox" %) 175 -((( 176 -**Human subject data that can be shared on EBRAINS:** 177 -// // 178 -// - Post-mortem data// 179 -// - Aggregated data// 180 -// - Strongly pseudonymized or de-identified subject data// 181 -// with a legal basis for sharing (e.g. Informed Consent)// 182 -// // 183 183 184 -(% class="small" %) 185 -//If you have human data that does not qualify as any of the above,// 186 -//please [[get in touch>>https://www.ebrains.eu/contact/]] and we will clarify the available options.// 187 -))) 190 +==== 1. Start early ==== 188 188 189 - Humansubjectdatasharedon EBRAINS mustcomplywith [[GDPR>>https://gdpr-info.eu/]]and [[EU directives>>https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32010L0063]].The information weneed toassessthisiscollectedviaour[[Ethics andRegulatoryComplianceSurvey>>https://nettskjema.no/a/224765]].192 +It is not necessary to wait until you are ready to publish to register your model with EBRAINS. 190 190 191 -Post-mortem and aggregated human data can be shared openly, given direct identifiers in the metadata are removed. Strongly pseudonymized and de-identified data can be shared via the Human Data Gateway (HDG). 194 +By registering a model early in your project, you can take advantage of EBRAINS tools 195 +to keep track of simulations and to share them with your collaborators. 192 192 193 - TheHuman Data Gateway (HDG) was introduced in February2021as aresponse to the needs of multiple data providers whoare bringing human subject data toEBRAINS. HDG coversthesharingof strongly pseudonymized or de-identified data, alimited range human subjectdatawithout direct identifiersnd with very few indirect identifiers.197 +==== 2. Create/choose a Collab workspace ==== 194 194 195 - TheHDG adds an an authentication layer on top of the data. Thismeansthat **data users **must request access to the data (via theirEBRAINSaccount) and willreceiveaccess provided they actively accept the [[EBRAINS Access Policy>>https://ebrains.eu/terms#access-policy]], the [[EBRAINS General Terms of Use>>https://ebrains.eu/terms#general-terms-of-use]], and the [[EBRAINS Data Use Agreement>>https://ebrains.eu/terms#data-use-agreement]].The account holder also havetoaccept that information about their requestand accesstospecificdata under HDG is being tracked and stored. **Data owners**must beaware that sharing under the HDGaffects the legal responsibilitiesforthedata. Theymust agree tojoint control of thedata (see the [[Data Provision Protocolv1>>url:https://strapi-prod.sos-ch-dk-2.exo.io/EBRAINS_Data_Provision_Protocol_dfe0dcb104.pdf]],section 1.4 - 1.5) and the Data Protection Officersof the responsible institutions must have accepted that the data can be shared under HDG.199 +We use EBRAINS Collaboratory "collab" workspaces to help manage the model curation process. 196 196 197 - TheHDGisanextensionofthexistingservicesanddoesnoteplacethefutureEBRAINS Serviceforsensitivedata (planned for2024) which isoutsidetheomain ofthecurrentEBRAINS Data and Knowledgeservices.201 +In particular, we use collab membership (the "Team") to control who can view or edit your model metadata prior to publication. 198 198 203 +It is up to you whether you create a new collab for each model, or reuse an existing collab 204 +(it is no problem to have multiple models associated with a single collab). 199 199 200 ----- 206 +Collabs are also useful for storing simulation results, adding documentation for your model, 207 +and/or providing tutorials in Jupyter notebooks. 201 201 202 -=== Stepby Step- Models===209 +==== 3. Upload code ==== 203 203 211 +We recommend storing model code and/or configuration files in an online Git repository, for example on GitHub. 212 +This repository should be public when you publish the model, but a private repository can be used for model development. 204 204 205 - ~1. Requestcuration using the[[Curationrequest form>>https://nettskjema.no/a/277393#/]].You will becontactedbya curator withmoreinformation.214 +Alternatively, you can upload code to the Collab Drive or Bucket storage. 206 206 216 +==== 4.Submit metadata ==== 207 207 208 - //Additionalinformationwillbeaddedsoon.//218 +We recommend submitting metadata using the Model Catalog app, installed in your collab. 209 209 220 +To install it: 221 + 222 +1. click the "+ Create" button 223 +1. in the "Create Page" form, add a title, such as "Model Catalog", and select "Community App", then click "Create" 224 +1. scroll down until you find the "Model Catalog" app, click "Select", then "Save & View" 225 + 226 +You will then see a table of all the models and validation tests associated with this collab. 227 +If this is your first time using the app, the table will probably be empty. 228 +To add your model, click "+", fill in the form, then click "Add model". 229 + 230 +As development of your model proceeds, you can easily register new versions of the code, 231 +and new parameterizations, by clicking "Add new version". 232 + 233 +If you prefer not to use the app, you can instead fill in the [[Curation request form>>https://nettskjema.no/a/277393#/]]., 234 +and you will be contacted by e-mail with further instructions. 235 + 236 +==== 5. Provide a reference dataset ==== 237 + 238 +Once you're ready to publish your model entry in the EBRAINS Knowledge Graph, 239 +we encourage you to provide a dataset containing the simulation results produced by your model, 240 +following the process under "Step by step - Data" above. 241 + 242 +These reference data will be linked to the model, and will be helpful to anyone trying to 243 +reuse your model. 244 + 245 +We will soon introduce a "Reproducible" badge for all models that include a reference dataset, 246 +and whose simulation results can be reproduced by an EBRAINS curator. 247 + 248 +==== 6. Request publication, preview and publish ==== 249 + 250 +Until you request your model entry to be published in the EBRAINS Knowledge Graph, 251 +only members of the collab will be able to view the model entry, in the Model Catalog app 252 +or using the Model Validation Python client. 253 + 254 +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. 255 + 256 +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. 257 + 258 + 259 +Curators will then perform a number of checks: 260 + 261 +1. Does the model description provide sufficient context to understand the purpose and use of the model? 262 +1. Does the code repository contain a licence file, explaining the conditions for reusing the code? 263 +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. 264 + 265 +The curators will also take a snapshot of your model code. 266 + 267 +* 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"]]. 268 +* 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. 269 + 270 +Once this is done, you will be invited to review a preview of how the model entry will appear in the KG Search, 271 +and will have the opportunity to request modifications prior to approval and publication. 272 + 210 210 ---- 211 211 212 212 === Step by Step - Software === ... ... @@ -233,8 +233,43 @@ 233 233 234 234 ---- 235 235 299 +=== Sharing human subject data === 300 + 301 +(% class="box floatinginfobox" %) 302 +((( 303 +**Human subject data that can be shared on EBRAINS:** 304 +// // 305 +// - Post-mortem data// 306 +// - Aggregated data// 307 +// - Strongly pseudonymized or de-identified subject data// 308 +// with a legal basis for sharing (e.g. Informed Consent)// 309 +// // 310 + 311 +(% class="small" %) 312 +//If you have human data that does not qualify as any of the above,// 313 +//please [[get in touch>>https://www.ebrains.eu/contact/]] and we will clarify the available options.// 314 +))) 315 + 316 + 317 +Human subject data shared on EBRAINS must comply with [[GDPR >>https://gdpr-info.eu/]]and [[EU directives>>https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=celex%3A32010L0063]]. The information we need to assess this is collected via our [[Ethics and Regulatory Compliance Survey>>https://nettskjema.no/a/224765]]. 318 + 319 +Post-mortem and aggregated human data can be shared openly, given direct identifiers in the metadata are removed. Strongly pseudonymized and de-identified data can be shared via the Human Data Gateway (HDG). 320 + 321 +The Human Data Gateway (HDG) was introduced in February 2021 as a response to the needs of multiple data providers who are bringing human subject data to EBRAINS. HDG covers the sharing of strongly pseudonymized or de-identified data, a limited range human subject data without direct identifiers and with very few indirect identifiers. 322 + 323 +The HDG adds an an authentication layer on top of the data. This means that **data users **must request access to the data (via their EBRAINS account) and will receive access provided they actively accept the [[EBRAINS Access Policy>>https://ebrains.eu/terms#access-policy]], the [[EBRAINS General Terms of Use>>https://ebrains.eu/terms#general-terms-of-use]], and the [[EBRAINS Data Use Agreement>>https://ebrains.eu/terms#data-use-agreement]]. The account holder also have to accept that information about their request and access to specific data under HDG is being tracked and stored. **Data owners** must be aware that sharing under the HDG affects the legal responsibilities for the data. They must agree to joint control of the data (see the [[Data Provision Protocol v1>>url:https://strapi-prod.sos-ch-dk-2.exo.io/EBRAINS_Data_Provision_Protocol_dfe0dcb104.pdf]], section 1.4 - 1.5) and the Data Protection Officers of the responsible institutions must have accepted that the data can be shared under HDG. 324 + 325 +The HDG is an extension of the existing services and does not replace the future EBRAINS Service for sensitive data (planned for 2024) which is outside the domain of the current EBRAINS Data and Knowledge services. 326 + 327 +---- 328 + 236 236 == **The openMINDS metadata framework** == 237 237 331 +(% class="box floatinginfobox" %) 332 +((( 333 +[[[[image:https://github.com/HumanBrainProject/openMINDS/raw/main/img/light_openMINDS-logo.png||alt="openMINDS logo" height="87" width="164"]]>>https://github.com/HumanBrainProject/openMINDS]] 334 +))) 335 + 238 238 openMINDS (open Metadata Initiative for Neuroscience Data Structures) is a community-driven, open-source metadata framework for graph database systems, such as the EBRAINS Knowledge Graph. It is composed of linked metadata models, libraries of serviceable metadata instances, and supportive tooling ([[openMINDS Python>>url:https://pypi.org/project/openMINDS/]], openMINDS Matlab). For exploring the openMINDS schemas, go to the [[HTML documentation>>url:https://humanbrainproject.github.io/openMINDS/]]. For a full overview of the framework, go to [[the openMINDS collab>>url:https://wiki.ebrains.eu/bin/view/Collabs/openminds/]] or the [[GitHub repository>>https://github.com/HumanBrainProject/openMINDS]]. 239 239 240 240 For feedback, requests, or contributions, please get in touch with the openMINDS development team via ... ... @@ -252,8 +252,10 @@ 252 252 The curators in EBRAINS are located in Oslo, Jülich, Trier and Paris. 253 253 254 254 255 -**Located in Norway :**353 +**Located in Norway** 256 256 355 +//Institute of Basic Medical Sciences,** **University of Oslo, Norway// 356 + 257 257 |(% style="width:303px" %)((( 258 258 [[image:My project2.jpg||height="209" width="167"]] 259 259 ... ... @@ -302,8 +302,12 @@ 302 302 )))| | | 303 303 304 304 305 -\\**Located in Germany :**405 +\\**Located in Germany** 306 306 407 +//Human-Computer Interaction, University of Trier, Germany// 408 + 409 +//Institute of Neuroscience and Medicine (INM-1), Research Centre Jülich, Germany// 410 + 307 307 |(% style="width:303px" %)((( 308 308 [[image:My project (2).jpg||height="209" width="167"]] 309 309 ... ... @@ -313,20 +313,15 @@ 313 313 Phd Student 314 314 Sensors and Cognitive Psychology (M. Sc.)(%%) 315 315 (% class="small" style="--darkreader-inline-color:#d3cbbf; color:#4a5568" %)**Human-Computer Interaction** 316 -)))|(% style="width:3 28px" %)(((317 - 420 +)))|(% style="width:303px" %)((( 421 +[[image:Lyuba.jpg||height="209" width="167"]] 318 318 319 - 320 - 321 - 322 - 323 - 324 324 **Lyuba Zehl** 325 325 326 326 (% class="small" %)Knowledge Systems Engineer 327 327 Dr. rer. nat. (Systems Neuroscience)(%%) 328 328 (% class="small" style="--darkreader-inline-color:#d3cbbf; color:#4a5568" %)**Standard development, data & knowledge management, interdisciplinary communication, data analysis** 329 -)))|(% style="width:3 21px" %) |(% style="width:324px" %)428 +)))|(% style="width:303px" %) |(% style="width:303px" %) 330 330 331 331 ---- 332 332 ... ... @@ -337,24 +337,18 @@ 337 337 338 338 === **Showcase shared data, models or software in other services** === 339 339 340 -Below is a list of additional services that data, models or software shared via EBRAINS can benefit from. EBRAINS is continuously looking to increase the number of interoperable services. 439 +Below is a list of additional services that data, models or software shared via EBRAINS can benefit from. EBRAINS is continuously looking to increase the number of interoperable services. 341 341 342 -**Viewer for 2D images ** 343 343 344 -* Integrate image data with //the Mio viewer//: EBRAINS Multi-Image OpenSeadragon viewer provides an intuitive way of navigating high-resolution 2D image series. It has browser-based classic pan and zoom capabilities. A collection can be displayed as a filmstrip (Filmstrip Mode) or as a table (Collection Mode) with adjustable number of row and columns. See [[Mio viewer links available for this dataset>>https://search.kg.ebrains.eu/?category=Dataset&q=nr2f1#9677359c-73fa-4425-b8fa-3de794e9017a]] as an example. MioViewer user manual is found [[here>>https://multi-image-osd.readthedocs.io/en/latest/index.html]]. 442 +|(% colspan="2" %)**Viewer for 2D images** 443 +|[[image:MIO_screenshot.PNG]]|Integrate image data with //the Mio viewer//: EBRAINS Multi-Image OpenSeadragon viewer provides an intuitive way of navigating high-resolution 2D image series. It has browser-based classic pan and zoom capabilities. A collection can be displayed as a filmstrip (Filmstrip Mode) or as a table (Collection Mode) with adjustable number of row and columns. See [[Mio viewer links available for this dataset>>https://search.kg.ebrains.eu/?category=Dataset&q=nr2f1#9677359c-73fa-4425-b8fa-3de794e9017a]] as an example. MioViewer user manual is found [[here>>https://multi-image-osd.readthedocs.io/en/latest/index.html]]. 444 +|(% colspan="2" %)**Viewer for sequential atlas-registered 2D images with annotation options** 445 +|[[image:LZ_screenshot.PNG]]|Integrate atlas-registered 2D image data with //the LocaliZoom viewer//: The EBRAINS LocaliZoom serial section viewer displays series of registered 2D section images with atlas overlay, allowing the users to zoom into high-resolution images and have information about the brain regions. See the [[LocaliZoom links available for this dataset>>https://doi.org/10.25493/T686-7BX]] as an example. LocaliZoom user manual is found [[here>>https://localizoom.readthedocs.io/en/latest/index.html]]. 446 +|(% colspan="2" %)**Interactive 3D atlas viewer with options for data visualization** 447 +|[[image:3Datlas_screenshot.PNG]]|Upload your data to the //Siibra-explorer//: The siibra-explorer is used for visualizing volumetric brain data in all the brain atlases provided by EBRAINS (Human, Monkey, Rat and Mouse). The siibra-explorer viewer uses siibra-api to enable navigation of brain region hierarchies, maps in different coordinate spaces, and linked regional data features. Furthermore, it is connected with the siibra toolsuite providing several analytical workflows. To learn more about how to register your data to atlases, read about the [[Atlas services on ebrains.eu>>https://ebrains.eu/services/atlases#Integratedatatoanatlas]]. 448 +|(% colspan="2" %)**Use your research product in an interactive publication** 449 +|[[image:LivePaper_screenshot.PNG]]|Add your data, models or software to a// Live paper. //Read more about [[Live papers on ebrains.eu>>https://www.ebrains.eu/data/live-papers/live-papers]]. 345 345 346 -**Viewer for sequential atlas-registered 2D images with annotation options** 347 - 348 -* Integrate atlas-registered 2D image data with //the LocaliZoom viewer//: The EBRAINS LocaliZoom serial section viewer displays series of registered 2D section images with atlas overlay, allowing the users to zoom into high-resolution images and have information about the brain regions. See the [[LocaliZoom links available for this dataset>>https://doi.org/10.25493/T686-7BX]] as an example. LocaliZoom user manual is found [[here>>https://localizoom.readthedocs.io/en/latest/index.html]]. 349 - 350 -**Use your research product in an interactive publication ** 351 - 352 -* Add your data, models or software to a// Live paper. //Read more about [[Live papers on ebrains.eu>>https://www.ebrains.eu/data/live-papers/live-papers]]. 353 - 354 -**Interactive 3D atlas viewer with options for data visualization** 355 - 356 -* Upload your data to //the Siibra//-explorer: The siibra-explorer is used for visualizing volumetric brain data in all the brain atlases provided by EBRAINS (Human, Monkey, Rat and Mouse). The siibra-explorer viewer uses siibra-api to enable navigation of brain region hierarchies, maps in different coordinate spaces, and linked regional data features. Furthermore, it is connected with the siibra toolsuite providing several analytical workflows. To learn more about how to register your data to atlases, read about the [[Atlas services on ebrains.eu>>https://ebrains.eu/services/atlases#Integratedatatoanatlas]]. 357 - 358 358 ---- 359 359 360 360 ==== **Add a tutorial or learning resource ** ==== ... ... @@ -392,33 +392,26 @@ 392 392 ))) 393 393 ))) 394 394 395 - 396 -(% class="wikigeneratedid" id="HHowcanIshareA0models3F" %) 397 397 No, if communication is on a regular basis, we are able to finish curation within two weeks. Publishing your data naturally takes some effort but we will support you as much as possible. 398 398 399 399 >Is sharing my data also beneficial for me or only for others? 400 400 401 - 402 402 When you publish your data via EBRAINS, we provide comprehensive data management support and safe long term storage - all free of charge. Additionally, your data can be cited, just like a scientific journal article. Sharing your data may even lead to new funding opportunities. Many funders specifically support projects that are part of the “Open Science” initiative. 403 403 404 404 >Can my data be too insignificant to share? 405 405 406 - 407 407 No, there is no such thing as insignificant data. Data that is considered insignificant for a given topic, may have great significance for another. By making “insignificant” data publicly available, other researchers may find something interesting that was off-topic for your own purposes. 408 408 409 409 >Can my data be easily misused if I share it? 410 410 411 - 412 412 No, your data will be covered by a Creative Commons license of your choice. There are a variety of licenses available, enabling you to prevent use for specific purposes, e.g. commercial use. 413 413 414 414 >Can I share my data before my paper is published? 415 415 416 - 417 417 Yes, if you do not want to share your data before publishing the results in an article, you can publish your dataset with an embargo status. This will make it possible to find information about the data without making the data itself available, and give you a citeable DOI. 418 418 419 419 >Can I lose my competitive edge if I share my data before I publish the associated paper? 420 420 421 - 422 422 No, publishing your data does not mean that others can use it however they want. Use of your data will require citation, and by choosing an appropriate Creative Commons licence you decide what others are allowed to do with it. If you still feel worried, you can publish your data under embargo, and in this way delay the date of data release, but still make it possible for others to find the information about the data. 423 423 424 424 ... ... @@ -429,8 +429,6 @@ 429 429 [[curation-support@ebrains.eu>>mailto:curation-support@ebrains.eu]] 430 430 431 431 518 +== References == 519 + 432 432 {{putFootnotes/}} 433 -~)~)~)~)~)~) 434 -~)~)~) 435 -~)~)~)~)~)~)~)~)~) 436 -~)~)~)~)~)~)
- 3Datlas_screenshot.PNG
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.eapapp - Size
-
... ... @@ -1,0 +1,1 @@ 1 +410.7 KB - Content
- LZ_screenshot.PNG
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.eapapp - Size
-
... ... @@ -1,0 +1,1 @@ 1 +1.8 MB - Content
- LivePaper_screenshot.PNG
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.eapapp - Size
-
... ... @@ -1,0 +1,1 @@ 1 +120.9 KB - Content
- Lyuba.jpg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.spieschnik - Size
-
... ... @@ -1,0 +1,1 @@ 1 +568.2 KB - Content
- MIO_screenshot.PNG
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.eapapp - Size
-
... ... @@ -1,0 +1,1 @@ 1 +607.0 KB - Content
- image-20230621121014-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.ingrreit - Size
-
... ... @@ -1,0 +1,1 @@ 1 +106.5 KB - Content