diff --git a/dmp-dataset-templates/Horizon2020_V2_added_Source.xml b/dmp-dataset-templates/Horizon2020_V2_added_Source.xml new file mode 100644 index 000000000..2090a64ff --- /dev/null +++ b/dmp-dataset-templates/Horizon2020_V2_added_Source.xml @@ -0,0 +1 @@ +
1.11.1.1What is the purpose of the data collection/generation and its relation to the objectives of the project?
1.21.2.1What types and formats of data will the project generate/collect?
1.31.3.1Will you re-use any existing data and how?
1.41.4.1What is the origin of the data?
1.51.5.1What is the expected size of the data?
1.61.6.1To whom might it be useful ('data utility')?
1Data SummaryAnswer 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.12.1.1.1truetruetruetrue2.1.1.22.1.1.3true Will you use metadata to describe the data?
2.1.22.1.2.12.1.2.2URL/Location
2.1.32.1.3.1truetrue2.1.3.22.1.3.3trueWill your metadata use standardised vocabularies?
2.1.42.1.4.12.1.4.2URL/Description
2.1.52.1.5.1 Will you make the metadata available free-of-charge?
2.1.62.1.6.1Will your metadata be harvestable?
2.1.72.1.7.1trueWill you use naming conventions for your data?
2.1.82.1.8.12.1.8.2URL/Name
2.1.92.1.9.1Will you provide clear version numbers for your data?
2.1.102.1.10.1trueWill you provide persistent identifiers for your data?
2.1.112.1.11.1Persistent identifiersSelect 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.122.1.12.1true Will you provide searchable metadata for your data?
2.1.132.1.13.12.1.13.2trueWhat services will you use to provide searchable metadata?
2.1.142.1.14.12.1.14.2URL/Name
2.1.152.1.15.1truefalseWill you use standardised formats for some or all of your data?
2.1.162.1.16.12.1.16.2trueWhich standardised data formats do you plan on using?
2.1.172.1.17.12.1.17.2Standardised formatsIs the structure of the file(s) provided in a standardised format?
2.1.182.1.18.12.1.18.22.1.18.3Please describe the formats you plan to store your data in, including any URLs to documentation.
2.1.192.1.19.1somenoneAre the file formats you will use open?
2.1.202.1.20.1Please describe which data are not in an open format and why?
2.1.212.1.21.1Please describe which data are not in an open format and why?
2.1.222.1.22.1forsomedatafornodata Do supported open-source tools exist for accessing the data?
2.1.232.1.23.1 Please describe which data require proprietary tools to access the data?
2.1.242.1.24.1 Please describe which data require proprietary tools to access the data?
2.1.252.1.25.1Will you provide metadata describing the quality of the data?
2.1Making data findable, including provisions for metadataData 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.12.2.1.1trueAre there ethical or legal issues that can impact sharing the data?
2.2.22.2.2.1somenoneWill all your data be openly accessible?
2.2.32.2.3.12.2.3.22.2.3.3Data type/ Reason/ URL
2.2.42.2.4.12.2.4.22.2.4.3Data type/ Reason/ URL
2.2.52.2.5.12.2.5.2trueHow will the data be made available?Select the repository where your data will be uploaded.
2.2.62.2.6.12.2.6.2URL/Name
2.2.72.2.7.1 Is the storage sufficiently secure for the data and does the storage provide backup and recovery procedures?
2.2.82.2.8.1truetrue Are there any methods or tools required to access the data?
2.2.92.2.9.12.2.9.2Please provide links describing the methods for accessing the data.
2.2.102.2.10.12.2.10.2Please provide links describing the tools for accessing the data.
2.2.112.2.11.1Will you also make auxiliary data that may be of interest to researchers available?
2.2Making data openly accessibleNot 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.12.3.1.1somenoneWill you use a standard vocabulary for your data types?
2.3.22.3.2.1Will you provide a mapping to more commonly used ontologies?
2.3.32.3.3.1Will you provide a mapping to more commonly used ontologies?
2.3Making data interoperableData 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.12.4.1.1laterneverWhen do you plan to make your data available for reuse?
2.4.22.4.2.1Please specify how long after the project has ended the data will be made available?
2.4.32.4.3.1Please describe the reason the data will not be made available.
2.4.42.4.4.1What internationally recognised licence will you use for your data?
2.4.52.4.5.1trueDo you have documented procedures for quality assurance of your data?
2.4.62.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"><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.82.4.8.1How long do you intend to support data reuse?
2.4.92.4.9.1Please specify why the data will be unsupported for reuse.
2.4Increase data reuseData 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.12.5.1.1How will the cost of making your data findable, accessible, interoperable and reusable be covered?
2.5.22.5.2.1falseWill you identify a data manager to manage your data, if not who will be responsible for the management of your data?
2.5.32.5.3.1Identify the people or roles that will be responsible for the management of the project data
2.5.42.5.4.1otherHow do you intend to ensure data reuse after your project finishes?
2.5Allocation of resourcesData 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.
2FAIR 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.13.1.1keptoninsecureWhat do you plan to do with research data of limited use
3.23.2.1Please describe why the data will be kept on insecure, unmanaged storage
3Data Security
4.14.1.1trueDo you make use of other procedures for data management?
4.24.2.1Please provide links to documentation on these other procedures.
4Other
 \ No newline at end of file