1.1 1.1.1 What is the purpose of the data collection/generation and its relation to the objectives of the project?
1.2 1.2.1 What types and formats of data will the project generate/collect?
1.3 1.3.1 Will you re-use any existing data and how?
1.4 1.4.1 What is the origin of the data?
1.5 1.5.1 What is the expected size of the data?
1.6 1.6.1 To whom might it be useful ('data utility')?
1 Data Summary Answer the following questions to provide a summary of the types and characteristics of data collected, generated, shared and re-used during your research activities. Highlight why it is of relevance to the project and useful to other researchers.
2.1.1 2.1.1.1 true true true true true 2.1.1.2 2.1.1.3 true Will you use metadata to describe the data?
2.1.2 2.1.2.1 2.1.2.2 URL/Location
2.1.3 2.1.3.1 true true 2.1.3.2 2.1.3.3 true Will your metadata use standardised vocabularies?
2.1.4 2.1.4.1 2.1.4.2 URL/Description
2.1.5 2.1.5.1 Will you make the metadata available free-of-charge?
2.1.6 2.1.6.1 Will your metadata be harvestable?
2.1.7 2.1.7.1 true Will you use naming conventions for your data?
2.1.8 2.1.8.1 2.1.8.2 URL/Name
2.1.9 2.1.9.1 Will you provide clear version numbers for your data?
2.1.10 2.1.10.1 true Will you provide persistent identifiers for your data?
2.1.11 2.1.11.1 Persistent identifiers Select a persistent identifier (PID) from the list. You may select multiple PIDs according to the types of research outputs, needs and the area of your research.
2.1.12 2.1.12.1 true Will you provide searchable metadata for your data?
2.1.13 2.1.13.1 2.1.13.2 true What services will you use to provide searchable metadata?
2.1.14 2.1.14.1 2.1.14.2 URL/Name
2.1.15 2.1.15.1 true false Will you use standardised formats for some or all of your data?
2.1.16 2.1.16.1 2.1.16.2 true Which standardised data formats do you plan on using?
2.1.17 2.1.17.1 2.1.17.2 Standardised formats Is the structure of the file(s) provided in a standardised format?
2.1.18 2.1.18.1 2.1.18.2 2.1.18.3 Please describe the formats you plan to store your data in, including any URLs to documentation.
2.1.19 2.1.19.1 some none Are the file formats you will use open?
2.1.20 2.1.20.1 Please describe which data are not in an open format and why?
2.1.21 2.1.21.1 Please describe which data are not in an open format and why?
2.1.22 2.1.22.1 forsomedata fornodata Do supported open-source tools exist for accessing the data?
2.1.23 2.1.23.1 Please describe which data require proprietary tools to access the data?
2.1.24 2.1.24.1 Please describe which data require proprietary tools to access the data?
2.1.25 2.1.25.1 Will you provide metadata describing the quality of the data?
2.1 Making data findable, including provisions for metadata Data are findable when described with metadata and vocabularies in a standardized way, assigned a Persistent Identifiers (PIDs) and are registered or indexed in a searchable resource
2.2.1 2.2.1.1 true Are there ethical or legal issues that can impact sharing the data?
2.2.2 2.2.2.1 some none Will all your data be openly accessible?
2.2.3 2.2.3.1 2.2.3.2 2.2.3.3 Data type/ Reason/ URL
2.2.4 2.2.4.1 2.2.4.2 2.2.4.3 Data type/ Reason/ URL
2.2.5 2.2.5.1 2.2.5.2 true How will the data be made available? Select the repository where your data will be uploaded.
2.2.6 2.2.6.1 2.2.6.2 URL/Name
2.2.7 2.2.7.1 Is the storage sufficiently secure for the data and does the storage provide backup and recovery procedures?
2.2.8 2.2.8.1 true true Are there any methods or tools required to access the data?
2.2.9 2.2.9.1 2.2.9.2 Please provide links describing the methods for accessing the data.
2.2.10 2.2.10.1 2.2.10.2 Please provide links describing the tools for accessing the data.
2.2.11 2.2.11.1 Will you also make auxiliary data that may be of interest to researchers available?
2.2 Making data openly accessible Not all data can be made publicly open, hence data can be FAIR but not open, or open but not FAIR or both FAIR and open. Data are accessible when uploaded in a data repository and retrieved by their PIDs. When data can not be shared openly, metadata should be provided (even when the data are no longer available). In the case of sensitive or personal data, anonymization or pseudonymization and specific access rights can be applied. Where accessing data requires the use of complementary methods or tools, such procedures should be documented.
2.3.1 2.3.1.1 some none Will you use a standard vocabulary for your data types?
2.3.2 2.3.2.1 Will you provide a mapping to more commonly used ontologies?
2.3.3 2.3.3.1 Will you provide a mapping to more commonly used ontologies?
2.3 Making data interoperable Data are interoperable, meaning they can be easily understood and shared with other platforms and systems, when they are created using standard vocabularies and include references to other data and metadata.
2.4.1 2.4.1.1 later never When do you plan to make your data available for reuse?
2.4.2 2.4.2.1 Please specify how long after the project has ended the data will be made available?
2.4.3 2.4.3.1 Please describe the reason the data will not be made available.
2.4.4 2.4.4.1 What internationally recognised licence will you use for your data?
2.4.5 2.4.5.1 true Do you have documented procedures for quality assurance of your data?
2.4.6 2.4.6.1 <description/> <extendedDescription/> <additionalInformation/> </fieldSet> <fieldSet id="fieldSet-83SiE" ordinal="6"> <numbering>2.4.7</numbering> <commentField commentFieldValue="" hasCommentField="false"/> <fields> <field id="supportForDataReuse" ordinal="0"> <rdaCommonStandard/> <numbering>2.4.7.1</numbering> <validations> <validation type="0"/> </validations> <defaultValue type="" value=""/> <visible style=""> <rule ruleStyle="" target="supportForDataReuseTimeSpan" type=""> <value type="">true</value> </rule> <rule ruleStyle="" target="unsupportedforreusewhy" type=""> <value type="">false</value> </rule> </visible> <viewStyle cssClass="" renderstyle="booleanDecision"/> <data label=""/> </field> </fields> <multiplicity max="0" min="0"/> <title>Will you provide any support for data reuse?
2.4.8 2.4.8.1 How long do you intend to support data reuse?
2.4.9 2.4.9.1 Please specify why the data will be unsupported for reuse.
2.4 Increase data reuse Data can be reused when the conditions about how others can make use of the data are well-described following community-standards and are communicated as specified by the owners. Such information can be found in licenses attributed to data and in references about the data provenance.
2.5.1 2.5.1.1 How will the cost of making your data findable, accessible, interoperable and reusable be covered?
2.5.2 2.5.2.1 false Will you identify a data manager to manage your data, if not who will be responsible for the management of your data?
2.5.3 2.5.3.1 Identify the people or roles that will be responsible for the management of the project data
2.5.4 2.5.4.1 other How do you intend to ensure data reuse after your project finishes?
2.5 Allocation of resources Data management can be costly, especially when its planning hasn't been sufficient from the very beginning of the research process. Costing of data management includes for example potential use of proprietary services and tools or extra effort needed to perform specific tasks or even to develop tools from scratch.
2 FAIR Data In general terms, your research data should be 'FAIR', that is findable, accessible, interoperable and re-usable. These principles precede implementation choices and do not necessarily suggest any specific technology, standard, or implementation-solution. This template is not intended as a strict technical implementation of the FAIR principles, it is rather inspired by FAIR as a general concept.
3.1 3.1.1 keptoninsecure What do you plan to do with research data of limited use
3.2 3.2.1 Please describe why the data will be kept on insecure, unmanaged storage
3 Data Security
4.1 4.1.1 true Do you make use of other procedures for data management?
4.2 4.2.1 Please provide links to documentation on these other procedures.
4 Other