From 32a76346ea07f23183d347d63ea4cce2321bc059 Mon Sep 17 00:00:00 2001 From: gkolokythas Date: Fri, 11 Oct 2019 16:46:57 +0300 Subject: [PATCH] Adds 5 new Dataset Templates ("Science Foundation Ireland/ Luxembourg National Research Fund" is also called "SE RDM") --- dmp-dataset-templates/AcademyOfFinland.xml | 256 +++ dmp-dataset-templates/FWF.xml | 1287 ++++++++++++++ ...rganisationForScientificResearch (NWO).xml | 885 ++++++++++ ...nIrelandLuxembourgNationalResearchFund.xml | 1540 +++++++++++++++++ .../TheResearchCouncilOfNorway.xml | 293 ++++ 5 files changed, 4261 insertions(+) create mode 100644 dmp-dataset-templates/AcademyOfFinland.xml create mode 100644 dmp-dataset-templates/FWF.xml create mode 100644 dmp-dataset-templates/NetherlandsOrganisationForScientificResearch (NWO).xml create mode 100644 dmp-dataset-templates/ScienceFoundationIrelandLuxembourgNationalResearchFund.xml create mode 100644 dmp-dataset-templates/TheResearchCouncilOfNorway.xml diff --git a/dmp-dataset-templates/AcademyOfFinland.xml b/dmp-dataset-templates/AcademyOfFinland.xml new file mode 100644 index 000000000..e9ce27510 --- /dev/null +++ b/dmp-dataset-templates/AcademyOfFinland.xml @@ -0,0 +1,256 @@ + + + + + + + + + + +
+ + +
+ 1.1 + + + + 1.1.1 + + + + + + + + + What kinds of data is your research based on? What data will be collected, produced or reused?What file formats will the data be in? + Give a rough estimate of the size of the data produced or collected. Also explain what kinds of existing data you will use, for example, the types of texts, images, photographs, measurements, statistics, physical samples or codes. + + +
+
+ 1.2 + + + + 1.2.1 + + + + + + + + + How will the consistency and quality of data be controlled? + Explain how the data collection, analysis and processing methods used may affect the quality of data and how you will minimize the risks related to data accuracy. + + +
+ + 1 + General description of data + + +
+ +
+ + +
+ 3.1 + + + + 3.1.1 + + + + + + + + + How will you document your data to make them findable, accessible, interoperable and reusable for you and others? What kinds of metadata standards, files or other documentation will you use to help others understand and use your data? + + + +
+ + 3 + Documentation and metadata + + +
+
+ + +
+ 4.1 + + + + 4.1.1 + + + + + + + + + Where will your data be stored, and how will they be backed up? + Describe where you will store and back up your data during your research project. Methods for preserving and sharing your data after your research project has ended are explained in more detail in Section 5 + Consider who will be responsible for backup and recovery. If there are several researchers involved, create a plan with your collaborators and ensure safe transfer between participants. + +
+
+ 4.2 + + + + 4.2.1 + + + + + + + + + Who will be responsible for controlling access to your data, and how will secured access be controlled? + Describe who has access to your data, what they are authorised to do with the data and how you will ensure the safe transfer of data to your collaborators. + + +
+ + 4 + Storage and backup during the research project + + +
+
+ + +
+ 5.1 + + + + 5.1.1 + + + + + + + + + What part of the data can be made openly available or published? Where and when will the data, or their metadata, be made available? + Describe whether you will publish or otherwise make all your data or only parts of them openly available. If your data or parts of them cannot be opened, please explain why. + + +
+
+ 5.2 + + + + 5.2.1 + + + + + + + + + Where will data with long-term value be archived, and for how long? + Briefly describe what data to archive and for how long – as well as what data to dispose of after the project. Describe the access policy to the archived data. + + +
+ + 5 + Opening, publishing and archiving the data after the research project + + +
+
+ + +
+ 6.1 + + + + 6.1.1 + + + + + + + + + Who will be responsible for specific tasks of data management during the research project life cycle? + Estimate also the resources (e.g. financial, time and effort) required for data management. + Estimate the need to hire expert help to manage, preserve and share the data. Consider the additional computational facilities and resources that need to be accessed, and what the associated costs will amount to. + +
+ + 6 + Data management responsibilities and resources + + +
+ + \ No newline at end of file diff --git a/dmp-dataset-templates/FWF.xml b/dmp-dataset-templates/FWF.xml new file mode 100644 index 000000000..84c5a7986 --- /dev/null +++ b/dmp-dataset-templates/FWF.xml @@ -0,0 +1,1287 @@ + + + + + + + + +
+ + +
+ 1.1 + + + + 1.1.1 + + + + + + + + + What kinds of data/source code will be generated or reused (type, format, volume)? + + + +
+
+ 1.2 + + + + 1.2.1 + + + + + + + + + How will the research data be generated and which methods will be used? + + + +
+
+ 1.3 + + + + 1.3.1 + + + + + + + + + How will you structure the data and handle versioning? + + + +
+
+ 1.4 + + + + 1.4.1 + + + + + + + + + Who is the target audience? + + + +
+ + 1 + Data Characteristics: Description of the data + + +
+
+ +
+ + +
+ 2.1.1 + + + + 2.1.1.1 + + + + + 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 standardized vocabularies? + + + +
+
+ 2.1.4 + + + + 2.1.4.1 + + + + + + + + 2.1.4.2 + + + + + + + + + URL/Description + + + +
+ + 2.1 + Metadata standards + + What metadata standards (if any) will be in use and why? +
+
+ +
+ + +
+ 2.2.1.1 + + + + 2.2.1.1.1 + + + + + some + + + none + + + + + + + + + + + Will all your data be openly accessible? + + + +
+
+ 2.2.1.2 + + + + 2.2.1.2.1 + + + + + + + + 2.2.1.2.2 + + + + + + + + 2.2.1.2.3 + + + + + + + + + Data type/ Reason/ URL + + + +
+
+ 2.2.1.3 + + + + 2.2.1.3.1 + + + + + + + + 2.2.1.3.2 + + + + + + + + 2.2.1.3.3 + + + + + + + + + Data type/ Reason/ URL + + + +
+
+ 2.2.1.4 + + + + 2.2.1.4.1 + + + + + + + + + 2.2.1.4.2 + + + + + true + + + + + + + + How will the data be made available? + + + +
+
+ 2.2.1.5 + + + + 2.2.1.5.1 + + + + + + + + 2.2.1.5.2 + + + + + + + + + URL/Name + + + +
+ + 2.2.1 + What information is needed for the data to be findable, accessible, interoperable and re-usable (FAIR) in the future? + + +
+
+ + +
+ 2.2.2.1 + + + + 2.2.2.1.1 + + + + + true + + + + + + + + Will you provide persistent identifiers for your data? + + + +
+
+ 2.2.2.2 + + + + 2.2.2.2.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.2.2.3 + + + + 2.2.2.3.1 + + + + + true + + + + + + + + Will you provide searchable metadata for your data? + + + +
+
+ 2.2.2.4 + + + + 2.2.2.4.1 + + + + + + + + + 2.2.2.4.2 + + + + + true + + + + + + + + What services will you use to provide searchable metadata? + + + +
+
+ 2.2.2.5 + + + + 2.2.2.5.1 + + + + + + + + 2.2.2.5.2 + + + + + + + + + URL/Name + + + +
+ + 2.2.2 + Is the data machine-readable? + + +
+
+ + +
+ 2.2.3.1 + + + + 2.2.3.1.1 + + + + + + + + + How are you planning to document this information? + + + +
+ + 2.2.3 + How are you planning to document this information? + + +
+ + + 2.2 + Documentation of data + + +
+
+ + +
+ 2.3.1 + + + + 2.3.1.1 + + + + + + + + + What quality assurance processes will you adopt? + + + +
+
+ 2.3.2 + + + + 2.3.2.1 + + + + + + + + + How will the consistency and quality of data collection be controlled and documented? + + + +
+ + 2.3 + Data quality control + + +
+ + + 2 + Documentation and Metadata + + +
+
+ +
+ + +
+ 3.1.1 + + + + 3.1.1.1 + + + + + + + + + What persistent identifier will be used? + + + +
+ + 3.1 + Data sharing strategy + + +
+
+ + +
+ 3.2.1 + + + + 3.2.1.1 + + + + + true + + + + + + + + Will there be data that will not be stored for long-term? + + + +
+
+ 3.2.2 + + + + 3.2.2.1 + + + + + + + + + What data will not be stored for long-term? + + + +
+
+ 3.2.3 + + + + 3.2.3.1 + + + + + true + + + true + + + + + + + + Will there be data that will be preserved for long-term? + + + +
+
+ 3.2.4 + + + + 3.2.4.1 + + + + + + + + + What data will be preserved for long-term + + + +
+
+ 3.2.5 + + + + 3.2.5.1 + + + + + true + + + false + + + + + + + + Will you use standardised formats for some or all of your data? + + + +
+
+ 3.2.6 + + + + 3.2.6.1 + + + + + + + + + 3.2.6.2 + + + + + true + + + + + + + + Which standardised data formats do you plan on using? + + + +
+
+ 3.2.7 + + + + 3.2.7.1 + + + + + + + + 3.2.7.2 + + + + + + + + + Standardized formats + Is the structure of the file(s) provided in a standardized format? + + +
+
+ 3.2.8 + + + + 3.2.8.1 + + + + + + + + 3.2.8.2 + + + + + + + + 3.2.8.3 + + + + + + + + + Please describe the formats you plan to store your data in, including any URLs to documentation. + + + +
+
+ 3.2.9 + + + + 3.2.9.1 + + + + + + + + + How will the data be stored after the project ends? + + + +
+
+ 3.2.10 + + + + 3.2.10.1 + + + + + + + + + + + + Where will the data be stored after the project ends? Is the storage sufficiently secure for the data and does the storage provide backup and recovery procedures? + + + +
+
+ 3.2.11 + + + + 3.2.11.1 + + + + + + + + + + + + For how long will the data be stored? + + + +
+
+ 3.2.12 + + + + 3.2.12.1 + + + + + + + + + Are there any costs that need to be covered for storage? + + + +
+
+ 3.2.13 + + + + 3.2.13.1 + + + + + + + + + + + + At what point during or after the project will the data be stored? + + + +
+
+ 3.2.14 + + + + 3.2.14.1 + + + + + + + + + Are there any technical barriers to making the research data fully or partially accessible? + + + +
+ + 3.2 + Data storage strategy + + +
+ + + 3 + Data Availability and Storage + + +
+ + + \ No newline at end of file diff --git a/dmp-dataset-templates/NetherlandsOrganisationForScientificResearch (NWO).xml b/dmp-dataset-templates/NetherlandsOrganisationForScientificResearch (NWO).xml new file mode 100644 index 000000000..e4fedbd0e --- /dev/null +++ b/dmp-dataset-templates/NetherlandsOrganisationForScientificResearch (NWO).xml @@ -0,0 +1,885 @@ + + + + + + + + + +
+ + +
+ 1.1 + + + + 1.1.1 + + + + + + + + 1.1.2 + + + + + + + + + Name applicant and project number + + + Fill in the name of the projectleader and the project number allocated by NWO +
+
+ 1.2 + + + + 1.2.1 + + + + + + + + + Did you ask for support of the data management support office of your institution? + + + NWO urgently advises researchers to seek support with the completion of this data management plan at an early stage. All universities and university medical centres provide professionalised support for research data management through their university library or ICT-department. A list of contact persons can be found on the website of NWO. +
+ + 1 + General Information + + +
+
+ + +
+ 2.1 + + + + 2.1.1 + + + + + + + + + Describe the data that will be collected/generated within the project + + + Describe the data and documents that will be generated during the project +
+
+ 2.2 + + + + 2.2.1 + + + + + + + + + Specify the type and format of the data + + + Which type and format data will be stored, digital/non-digital, raw/processed data, software, curricula material or combinations of these. NWO understands ‘data’ to be both collected, unprocessed data as well as analysed, generated data. This can be in all conceivable formats; digital and non-digital (for example samples, completed questionnaires, sound recordings, etc.). +
+ + 2 + Description dataset + + +
+
+ +
+ + +
+ 3.1.1 + + + + 3.1.1.1 + + + + + + + + 3.1.1.2 + + + + + + + + + What is the volume of the data and where will the data be stored? + + + Make a realistic estimation of the volume of the data that will be generated and the necessary storage capacity and state where you plan to store the data during the research. In the case of digital data, NWO data to be stored in the central storage centre of your institution, for example the ICT department and/or the university library. +
+
+ 3.1.2 + + + + 3.1.2.1 + + + + + + + + + Is there sufficient storage capacity during the project? + + + It is important that there is enough storage capacity, and in the case of digital data, also a backup of your data. An automatic backup by the ICT Department is safer than a manual backup. Storage of data on laptops, hard disks or external media is in general risky and will therefore, in principle, not be accepted by NWO. If external services are used then you must ensure that no conflicts of interest with the policy of research partners or co-financiers and with the policy of your department or institute, for example about the security of sensitive data +
+
+ 3.1.3 + + + + 3.1.3.1 + + + + + + + + 3.1.3.2 + + + + + + + + + Will the data be backed up regularly during the project? Who is responsible for this? + + + +
+
+ 3.1.4 + + + + 3.1.4.1 + + + + + + + + 3.1.4.2 + + + + + + + + + + + + What are the expected costs? How will these costs be covered? + Please specify these and state an amount that is as realistic as possible. + + Make a realistic estimation of the costs. Important factors that determine the costs are: +a. the type of data; +b. b. the capacity needed for storage and backup; +c. c. the amount of manual work for the allocating of metadata and the drawing up of other documentation such as code books and queries used in the statistical package; +d. d. the extent to which the data needs to be made secure; +e. e. the hiring in of external data management and other expertise. + +
+ + 3.1 + During the research + + +
+
+ + +
+ 3.2.1 + + + + 3.2.1.1 + + + + + true + + + false + + + + + + + 3.2.1.2 + + + + + + + + + + Will the data be stored in trusted repository after the project? + + + Specify in which trusted repository the data will be stored. There are a number of international certification schemes which determine the trustworthiness of data repositories. Of these the international Data Seal of Approval is the most basic set of criteria. Trusted Digital Repositories with a quality mark include repositories with a Data Seal of Approval, DIN-31644-, ISO-16363- or WDS/ICSU certification. An overview of existing repositories with Data Seal of Approval can be found in this list of repositories. +
+
+ 3.2.2 + + + + 3.2.2.1 + + + + + + + + + How will the data be made findable, accessible, interoperable and re-usable? + + + +
+
+ 3.2.3 + + + + 3.2.3.1 + + + + + true + + + + + + + + Will you provide persistent identifiers for your data? + + + A persistent identifier helps to make your data findable and citable by others. Most trusted repositories will provide a PID upon deposition of the data. +
+
+ 3.2.4 + + + + 3.2.4.1 + + + + + + + + + + + + Persistent identifiers + + + +
+
+ 3.2.5 + + + + 3.2.5.1 + + + + + + + + + For how long will the data be archived? + + + According to the Netherlands Code of Conduct for Scientific Practice (2018), raw and processed data must be stored for a period appropriate for the discipline and methodology at issue. NWO considers a minimal period of 10 years reasonable. +
+
+ 3.2.6 + + + + 3.2.6.1 + + + + + + + + 3.2.6.2 + + + + + + + + + + + + What are the expected costs? How will these costs be covered? + Specify this and state an amount that is as realistic as possible. + + +
+ + 3.2 + After the research + + The data should preferably be stored for the long-term in a national or international trusted repository. If this is not possible then the data should be stored by the institutional repository. Contact the intended data repository or archive well in advance about the requirements for depositing the data. +
+ + + 3 + Data Storage + + +
+
+ +
+ + +
+ 4.1.1 + + + + 4.1.1.1 + + + + + true + + + true + + + true + + + + + + + 4.1.1.2 + + + + + + + + + 4.1.1.3 + + + + + true + + + + + + + + Will you use metadata to describe the data? + + + +
+
+ 4.1.2 + + + + 4.1.2.1 + + + + + + + + 4.1.2.2 + + + + + + + + + URL/Location + + + +
+
+ 4.1.3 + + + + 4.1.3.1 + + + + + true + + + true + + + + + + + 4.1.3.2 + + + + + + + + + 4.1.3.3 + + + + + true + + + + + + + + Will your metadata use standardized vocabularies? + + + +
+
+ 4.1.4 + + + + 4.1.4.1 + + + + + + + + 4.1.4.2 + + + + + + + + + URL/Description + + + +
+
+ 4.1.5 + + + + 4.1.5.1 + + + + + true + + + + + + + + Will you use naming conventions for your data? + + + +
+
+ 4.1.6 + + + + 4.1.6.1 + + + + + + + + 4.1.6.2 + + + + + + + + + URL/Name + + + +
+
+ 4.1.7 + + + + 4.1.7.1 + + + + + + + + + Will you provide clear version numbers for your data? + + + +
+
+ 4.1.8 + + + + 4.1.8.1 + + + + + true + + + + + + + + Will you provide searchable metadata for your data? + + + +
+
+ 4.1.9 + + + + 4.1.9.1 + + + + + + + + + 4.1.9.2 + + + + + true + + + + + + + + What services will you use to provide searchable metadata? + + + +
+
+ 4.1.10 + + + + 4.1.10.1 + + + + + + + + 4.1.10.2 + + + + + + + + + URL/Name + + + +
+ + 4.1 + How will the data be documented? + + +
+ + + 4 + Standards and Metadata + + To make data findable and readable in the future and to be able to interpret it the data collection must be provided with descriptive information in the form of metadata. Without metadata – meaning without a good documentation of the data – most data can not be interpreted ore reused properly. Disciplines have developed different standards for metadata. That way datasets stemming from the same discipline can be linked or data can be combined. A widely used standards is the Dublin Core standard. The Digital Curation Centre (DCC) maintains a list of widely used disciplinary meta data standards. +
+
+ + +
+ 5.1 + + + + 5.1.1 + + + + + later + + + never + + + + + + + + + + + Are the data available for reuse after the project and when? + + + +
+
+ 5.2 + + + + 5.2.1 + + + + + + + + + Please specify how long after the project has ended the data will be made available? + + + +
+
+ 5.3 + + + + 5.3.1 + + + + + + + + + Please explain why the data are not suitable and/or available for reuse. + + + +
+
+ 5.4 + + + + 5.4.1 + + + + + true + + + + + + + 5.4.2 + + + + + + + + + Is there part of the data that cannot be made (directly) available? If yes, then please state the part concerned. + + + +
+
+ 5.5 + + + + 5.5.1 + + + + + true + + + + + + + + Are there any conditions for the reuse of the data? + + + State whether there are embargoes, licenses, commercial objectives or other conditions apply to the reuse of the data. +
+
+ 5.6 + + + + 5.6.1 + + + + + + + + + Are these conditions defined in a consortium agreement? + + + +
+ + 5 + Making data available + + NWO expects data stemming from NOW funded research projects to be made openly available for reuse after the end of the project. Following the guidelines of the European Commission the general rule for NWO is: “as open as possible, as closed as necessary”. If there are good reasons not to make data openly available immediately after the project (or only after an embargo period) please motivate here. In addition it is advised to determine which conditions apply to obtain access to your data. Examples of this are agreements that will be made concerning methodology, publications, the access period, availability of data, the costs (handling fee), copyright aspects, etc. +
+ + \ No newline at end of file diff --git a/dmp-dataset-templates/ScienceFoundationIrelandLuxembourgNationalResearchFund.xml b/dmp-dataset-templates/ScienceFoundationIrelandLuxembourgNationalResearchFund.xml new file mode 100644 index 000000000..3a7467e76 --- /dev/null +++ b/dmp-dataset-templates/ScienceFoundationIrelandLuxembourgNationalResearchFund.xml @@ -0,0 +1,1540 @@ + + + + + + + + + + +
+ +
+ + +
+ 1.1.1 + + + + 1.1.1.1 + + + + + + + + + Explain which methodologies or software will be used if new data are collected or produced. + + + +
+
+ 1.1.2 + + + + 1.1.2.1 + + + + + + + + + State any constraints on re-use of existing data if there are any. + + + +
+
+ 1.1.3 + + + + 1.1.3.1 + + + + + + + + + Explain how data provenance will be documented. + + + +
+
+ 1.1.4 + + + + 1.1.4.1 + + + + + + + + + Briefly state the reasons if the re-use of any existing data sources has been considered but discarded. + + + +
+ + 1.1 + How will new data be collected or produced and/or how will existing data be re-used? + + +
+
+ + +
+ 1.2.1 + + + + 1.2.1.1 + + + + + + + + + + + + Give details on the kind of data: + + + +
+
+ 1.2.2 + + + + 1.2.2.1 + + + + + + + + + + + + Give details on the data format: + + + +
+
+ 1.2.3 + + + + 1.2.3.1 + + + + + + + + + Justify the use of certain formats. + For example, decisions may be based on staff +expertise within the host organisation, a +preference for open formats, standards +accepted by data repositories, widespread +usage within the research community, or on +the software or equipment that will be used. + Give preference to open and standard +formats as they facilitate sharing and +long-term re-use of data (several repositories +provide lists of such ‘preferred formats’). + +
+
+ 1.2.4 + + + + 1.2.4.1 + + + + + + + + + Give details on the volumes. + they can be expressed in storage space required (bytes), +and/or in numbers of objects, files, rows, and columns. + + +
+ + 1.2 + What data (for example the kind, formats, and volumes), will be collected or produced? + + +
+ + + 1 + Data Description And Collection Or Re-use Of Existing Data + + +
+
+ +
+ + +
+ 2.1.1 + + + + 2.1.1.1 + + + + + + + + + Indicate which metadata will be provided to help others identify and discover the data. + + + +
+
+ 2.1.2 + + + + 2.1.2.1 + + + + + + + + + + + + Indicate which metadata standards will be used. + Use community metadata standards where +these are in place + + +
+
+ 2.1.3 + + + + 2.1.3.1 + + + + + + + + + Indicate how the data will be organised during the project. + Mentioning for example +conventions, version control, and folder +structures. Consistent, well-ordered research +data will be easier to find, understand, and +re-use. + + +
+
+ 2.1.4 + + + + 2.1.4.1 + + + + + + + + + Consider what other documentation is needed to enable re-use. + This may include information on the methodology used to +collect the data, analytical and procedural +information, definitions of variables, units of +measurement, and so on. + + +
+
+ 2.1.5 + + + + 2.1.5.1 + + + + + + + + + Consider how this information will be captured and where it will be recorded. + + For example in a database with links to each +item, a ‘readme’ text file, file headers, code +books, or lab notebooks. + +
+ + 2.1 + What metadata and documentation will accompany the data? + + For example the methodology of data collection and way of organizing data +
+
+ + +
+ 2.2.1 + + + + 2.2.1.1 + + + + + + + + + Explain how the consistency and quality of data collection will be controlled and documented + This may include processes +such as calibration, repeated samples or +measurements, standardised data capture, +data entry validation, peer review of data, or +representation with controlled vocabularies. + + +
+ + 2.2 + What data quality control measures will be used? + + +
+ + + 2 + Documentation And Data Quality + + +
+
+ +
+ + +
+ 3.1.1 + + + + 3.1.1.1 + + + + + + + + 3.1.1.2 + + + + + + + + + + + + Describe where the data will be stored and backed up during research activities and how often the backup will be performed. + It is recommended to store data in least at two separate locations. + Give preference to the use of robust, +managed storage with automatic backup, +such as provided by IT support services +of the home institution. Storing data on +laptops, stand-alone hard drives, or external +storage devices such as USB sticks is not +recommended. + +
+ + 3.1 + How will data and metadata be stored and backed up during the research? + + +
+
+ + +
+ 3.2.1 + + + + 3.2.1.1 + + + + + + + + + Explain how the data will be recovered in the event of an incident. + + + +
+
+ 3.2.2 + + + + 3.2.2.1 + + + + + + + + + Explain who will have access to the data during the research and how access to data is controlled, especially in collaborative partnerships. + + + +
+
+ 3.2.3 + + + + 3.2.3.1 + + + + + + + + + Describe the main risks and how these will be managed. + Consider data protection, particularly +if your data is sensitive for example +containing personal data, politically sensitive +information, or trade secrets. + + +
+
+ 3.2.4 + + + + 3.2.4.1 + + + + + + + + + Explain which institutional data protection policies are in place. + + + +
+ + 3.2 + How will data security and protection of sensitive data be taken care of during the research? + + +
+ + + 3 + Storage And Backup During The Research Process + + +
+ +
+ +
+ + +
+ 5.1.1 + + + + 5.1.1.1 + + + + + + + + + Explain how the data will be discoverable. and shared + + For example by deposit in a +trustworthy data repository, indexed in a +catalogue, use of a secure data service, +direct handling of data requests, or use of +another mechanism. + +
+
+ 5.1.2 + + + + 5.1.2.1 + + + + + + + + + Outline the plan for data preservation and give information on how long the data will be retained. + + + +
+
+ 5.1.3 + + + + 5.1.3.1 + + + + + + + + + Explain when the data will be made available. + + + +
+
+ 5.1.4 + + + + 5.1.4.1 + + + + + + + + + Indicate the expected timely release. + + + +
+
+ 5.1.5 + + + + 5.1.5.1 + + + + + true + + + + + + + + Will exclusive use of the data be claimed? + + + +
+
+ 5.1.6 + + + + 5.1.6.1 + + + + + + + + 5.1.6.2 + + + + + + + + + For what reason and how long exclusive use will be claimed? + + + +
+
+ 5.1.7 + + + + 5.1.7.1 + + + + + + + + + + + 5.1.7.2 + + + + + + + + + Indicate whether data sharing will be postponed or restricted + + For example to +publish, protect intellectual property, or seek +patents. + +
+
+ 5.1.8 + + + + 5.1.8.1 + + + + + + + + + Indicate who will be able to use the data. + + + +
+
+ 5.1.9 + + + + 5.1.9.1 + + + + + true + + + true + + + + + + + + Is it necessary to restrict access to certain communities or to apply a data sharing agreement? + + + +
+
+ 5.1.10 + + + + 5.1.10.1 + + + + + + + + + Explain how and why. + + + +
+
+ 5.1.11 + + + + 5.1.11.1 + + + + + + + + + Explain what action will be taken to overcome or to minimise restrictions. + + + +
+ + 5.1 + How and when will data be shared? Are there possible restrictions to data sharing or embargo reasons? + + +
+
+ + +
+ 5.2.1 + + + + 5.2.1.1 + + + + + + + + 5.2.1.2 + + + + + + + + + + + + Indicate what data must be retained or destroyed for contractual, legal, or regulatory purposes. + + + +
+
+ 5.2.2 + + + + 5.2.2.1 + + + + + + + + + Indicate how it will be decided what data to keep. + + + +
+
+ 5.2.3 + + + + 5.2.3.1 + + + + + + + + + Describe the data to be preserved long-term. + + + +
+
+ 5.2.4 + + + + 5.2.4.1 + + + + + + + + + Explain the foreseeable research uses (and/ or users) for the data. + + + +
+
+ 5.2.5 + + + + 5.2.5.1 + + + + + + + + + Indicate where the data will be deposited. + + + +
+
+ 5.2.6 + + + + 5.2.6.1 + + + + + false + + + + + + + + Will there be established repository proposed? + + + +
+
+ 5.2.7 + + + + 5.2.7.1 + + + + + + + + + Demonstrate that the data can be curated effectively beyond the lifetime of the grant. + It is recommended to demonstrate that the +repositories policies and procedures +(including any metadata standards, and +costs involved) have been checked. + + +
+ + 5.2 + How will data for preservation be selected, and where data will be preserved long-term? + + For example a data repository or archive +
+
+ + +
+ 5.3.1 + + + + 5.3.1.1 + + + + + Another mechanism + + + + + + + + + + 5.3.1.2 + + + + + + + + + Indicate how the data will be shared. + + + +
+
+ 5.3.2 + + + + 5.3.2.1 + + + + + + + + + Indicate whether potential users need specific tools to access and (re-)use the data. + Consider the sustainability of software +needed for accessing the data. + + +
+ + 5.3 + What methods or software tools are needed to access and use data? + + +
+
+ + +
+ 5.4.1 + + + + 5.4.1.1 + + + + + + + + + Explain how the data might be re-used in other contexts + Persistent identifiers should +be applied so that data can be reliably and +efficiently located and referred to. Persistent +identifiers also help to track citations and +re-use. + + +
+
+ 5.4.2 + + + + 5.4.2.1 + + + + + + + + + Indicate whether a persistent identifier for the data will be pursued + Typically, a +trustworthy, long-term repository will provide +a persistent identifier. + + +
+ + 5.4 + How will the application of a unique and persistent identifier to each data set be ensured? + + Such as a Digital Object Identifier (DOI) +
+ + + 5 + Data Sharing And Long-term Preservation + + +
+
+ +
+ + +
+ 6.1.1 + + + + 6.1.1.1 + + + + + + + + 6.1.1.2 + + + + + + + + + Outline the roles and responsibilities for data management/stewardship activities. + Name responsible individual(s) where possible. + For example data capture, metadata production, +data quality, storage and backup, data +archiving, and data sharing. + +
+
+ 6.1.2 + + + + 6.1.2.1 + + + + + true + + + + + + + + Is it a collaborative project + + + +
+
+ 6.1.3 + + + + 6.1.3.1 + + + + + + + + + Explain the co-ordination of data management responsibilities across partners + + + +
+
+ 6.1.4 + + + + 6.1.4.1 + + + + + + + + + Indicate who is responsible for implementing the DMP, and for ensuring it is reviewed and, if necessary, revised. + + Consider regular updates of the DMP + +
+ + 6.1 + Who will be responsible for data management? + + For example role, position, and institution. i.e. the data steward +
+
+ + +
+ 6.2.1 + + + + 6.2.1.1 + + + + + + + + + Explain how the necessary resources (for example time) to prepare the data for sharing/preservation (data curation) have been costed in. + Carefully consider and justify +any resources needed to deliver the data. +These may include storage costs, hardware, +staff time, costs of preparing data for +deposit, and repository charges. + + +
+
+ 6.2.2 + + + + 6.2.2.1 + + + + + true + + + + + + + + Indicate whether additional resources will be needed to prepare data for deposit or to meet any charges from data repositories + + + +
+
+ 6.2.3 + + + + 6.2.3.1 + + + + + + + + + Explain how much is needed and how such costs will be covered. + + + +
+ + 6.2 + What resources will be dedicated to data management and ensuring that data will be FAIR (Findable, Accessible, Interoperable, Re-usable)? + + For example financial and time +
+ + + 6 + Data Management Responsibilities And Resources + + +
+ + \ No newline at end of file diff --git a/dmp-dataset-templates/TheResearchCouncilOfNorway.xml b/dmp-dataset-templates/TheResearchCouncilOfNorway.xml new file mode 100644 index 000000000..7170ca130 --- /dev/null +++ b/dmp-dataset-templates/TheResearchCouncilOfNorway.xml @@ -0,0 +1,293 @@ + + + + + + + +
+ +
+ + +
+ 1.1.1 + + + + 1.1.1.1 + + + + + + + + + What is the purpose of the data collection/generation and its relation to the objectives of the project? + + + +
+
+ 1.1.2 + + + + 1.1.2.1 + + + + + + + + + What types and formats of data will the project generate/collect? + + + +
+
+ 1.1.3 + + + + 1.1.3.1 + + + + + + + + + What is the origin of the data? + + + +
+ + 1.1 + The kind of data that will be generated + + +
+
+ + +
+ 1.2.1 + + + + 1.2.1.1 + + + + + true + + + true + + + + + + + 1.2.1.2 + + + + + + + + + 1.2.1.3 + + + + + true + + + + + + + + Will you use metadata to describe the data? + + + +
+
+ 1.2.2 + + + + 1.2.2.1 + + + + + + + + 1.2.2.2 + + + + + + + + + URL/Location + + + +
+ + 1.2 + How the data will be described + + +
+ + + 1 + Data Origin and Description + + +
+
+ + +
+ 2.1 + + + + 2.1.1 + + + + + + + + + Where the data will be stored + + + +
+ + 2 + Storage and Backup + + +
+
+ +
+ + +
+ 3.1.1 + + + + 3.1.1.1 + + + + + + + + + Are there ethical or legal issues that can impact sharing the data? + + + +
+
+ 3.1.2 + + + + 3.1.2.1 + + + + + + + + + 3.1.2.2 + + + + + true + + + + + + + + How will the data be made available? + + + +
+
+ 3.1.3 + + + + 3.1.3.1 + + + + + + + + 3.1.3.2 + + + + + + + + + URL/Name + + + +
+ + 3.1 + Whether and how the data can be shared + + +
+ + + 3 + Data Sharing and Long-term Preservation + + +
+ + \ No newline at end of file