> For the complete documentation index, see [llms.txt](https://fdilab.gitbook.io/open-data-commons/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://fdilab.gitbook.io/open-data-commons/readme/readme/principles-of-the-odc.md). # Principles of the ODC The spirit of the ODC is to promote the open exchange of data, tools, and ideas to accelerate treatments and cures for spinal cord and traumatic brain injuries. As far as possible, we adhere to Open Science and FAIR Data Principles. ## [Open Science](#open-science) Open Science is a movement to make scientific research, including its processes, methodology, and outputs, more transparent. [Open Science Principles](http://sciencecommons.org/resources/readingroom/principles-for-open-science/)\* * Research data, datasets, databases, and protocols should be in the public domain * This status ensures the ability to freely distribute, copy, re-format, and integrate data from research into new research, ensuring that as new technologies are developed that researchers can apply those technologies without legal barriers * Scientific citation, attribution, and acknowledgment traditions should be cultivated in norms {% hint style="info" %} \*These principles were drafted by Science Commons and presented at [Policy and Technology for e-Science](http://sciencecommons.org/events/esof-satellite-event/), a satellite workshop in conjunction with the [Euroscience Open Forum](http://www.esof2008.org/) (ESOF) 2008 {% endhint %} Open Science is ***not*** simply making the final product of research available (i.e., Open Access publishing of scientific articles), it involves integrating various practices throughout different stages of the research lifecycle. Open Science practices include (but are not limited to): * Pre-registering studies * Sharing methodology and research protocols * Creating and using open-source software * Sharing code for analysis pipelines and algorithms * Publishing pre-prints * Sharing raw (or minimally transformed) data * Publishing scientific articles open access ## [FAIR Data](#fair-data) FAIR stands for Findable, Accessible, Interoperable, and Reusable ([Wilkinson et al., 2016](https://www.nature.com/articles/sdata201618)). FAIR establishes a framework for data sharing and defines a set of recommendations developed by FORCE11 (The Future of Research Communications and e-Scholarship) for successful data dissemination. More details can be found at the[ GO-FAIR initiative](https://www.go-fair.org/fair-principles/). FAIR data encompasses four principles: * **Findable**: data should be able to be found with enough explicit metadata to be searchable; * **Accessible**: data should be accessible to others in some form; * **Interoperable**: data should be able to integrate with other datasets of the same nature using structured formats and standard definitions such as common data elements; * **Reusable**: data should include sufficient documentation and meet community standards in order to enable subsequent reuse of the data by others. The ODC has been developed to follow the FAIR principles. To ensure the success of data sharing with the ODC-SCI and ODC-TBI, tools and functionalities have been designed to meet the needs of the SCI and TBI research communities. {% hint style="info" %} Learn more about FAIR [here](https://www.fdilab.org/about-fair) and [here](https://www.go-fair.org/fair-principles/) {% endhint %} ## [Incorporating Open Science & FAIR Data into the ODC](#incorporating-open-science-and-fair-data-into-the-odc) The ODC uses a few key strategies to ensure published datasets follow Open Science and FAIR Data principles: ### **Tidy Data Format** Datasets uploaded to the ODC need to be organized in Tidy Data Format (a set of principles for organizing and structuring data) — this helps make data machine readable\ \&#xNAN;*FAIR: interoperable, reusable* ### Descriptive Metadata Datasets uploaded to the ODC are accompanied by two types of descriptive metadata: * **Narrative Metadata (project-level metadata):** information that helps to make the dataset searchable\ \&#xNAN;*FAIR: findable, accessible* * **Data Dictionary (dataset-level metadata):** information that provides granular details about the data itself\ \&#xNAN;*FAIR: interoperable, reusable* ### Editorial Review To publish data to the Public Space, a DOI must be requested — this triggers the editorial review process. The editorial board and data team review submitted datasets to ensure submissions: * Are within the scope of the ODC-SCI or ODC-TBI * Are organized in tidy format * Have complete metadata (narrative and dataset-associated documents) * Meet the minimum data requirements (i.e., include all required variables in the dataset file) * SCI: 17 variables (ODC-SCI Community Data Elements, CoDEs) * TBI: 9 variables (from the PRECISE-TBI Common Data Elements) The editorial review process generally takes a few days, however it results in higher quality shared data ***and*** ensures that shared data is FAIR. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://fdilab.gitbook.io/open-data-commons/readme/readme/principles-of-the-odc.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.