GCWG - RDA maDMP Metadata Application Profile (MAP)
for machine-actionable Data Management Plans
v2.5
Link to HIGH LEVEL BRIEF »
Elevator PitchValue Proposition
User Stories
FAQ
Definitions
Compatibility with Standards
References
PreambleShort Definition: A machine-actionable Data Management Plans (maDMP), updated during the entire data lifecycle, provides information about a project and its data in a discipline agnostic standardized manner that is readable and reusable by both humans and automated systems. maDMPs facilitate collaboration, reporting, compliance, and integration with automated systems. Long Definition: Machine-actionable Data Management Plans (maDMPs), are an enterprise solution that operationalizes FAIRER (Findable, Accessible, Interoperable, Reusable, Ethical, and Reproducible) data management principles and enables an organization to plan more easily, document costing and funding, track inputs and outputs, provide customized reports, and ensure transparency throughout the data lifecycle. They provide information about contributors, partner agreements, distributions and licensing, storage, technical resources and computing needs, processing workflows, associated code and software, security and privacy, data quality, ethical issues, Indigenous considerations, retention and disposition, approvals, and more. maDMPs are the means for rapidly building reliable, lightweight, scalable, and easily customized automated systems with appropriate access controls while maximizing interoperability. The maDMP Standard: This human readable GCWG-RDA maDMP Standard metadata application profile (MAP), or specification, and the equivalent machine-readable GCWG-RDA JSON schema are an extension of the international Research Data Alliance (RDA) common maDMP consensus standard. It has been developed to collect additional information required in the context of government or other large organizations building automated systems to support Enterprise Information Management. This will enable programs and services to plan and improve delivery of data and information about the data, and to comply with new policy requirements while increasing efficiency and reducing costs. Machine-actionable Data Management Plans (maDMP) support implementation of FAIRER principles and enable an organization’s enterprise maturity with the return on investment (ROI) being reduced administrative costs, improved data management efficiency, and mitigation of risks. An Interactive form to generate maDMPs has also been developed to help facilitate implementation. Purpose: The MAP provides basic interoperability between systems producing or consuming machine-actionable data management plans (maDMP's). The MAP and companion schema are the means for rapidly building reliable, lightweight, and easily customized automated systems with appropriate access controls while maximizing interoperability. Applicability: The maDMP MAP is intended to cover a wide range of use cases and does not set any business requirements. It represents information collected over the whole data lifecycle from conception through to disposition. The required (mandatory) information is minimized to apply across all use cases at the beginning of the data lifecycle. The remaining information in the MAP is set to optional. Some of this optional information becomes mandatory as the data move through the data lifecycle. Organizations can choose to make the remaining optional information mandatory during implementation if it is relevant to them. GC maDMP working group: If you see opportunities for improvement to this MAP, we invite you to join the GC maDMP working group. Contact: Claire.Austin@canada.ca or Dominique.Charles@canada.ca. ![]() Entity relationship diagram: The maDMP ERD is a logical model which is more detailed than the conceptual model. It provides a visual starting point for development and debugging of the maDMP specification and potential database design. ![]() Safeguarding ScienceSafeguarding Science is the protection of scientific knowledge, technologies, data, and long-term research integrity. An important risk mitigation measure for any project is development of a data management plan. The purpose of the Safeguarding Science section in the maDMP is twofold: (1) Describe or link to project-specific safeguarding science issues or measures that are not already recorded in another section of the maDMP; and/or, (2) Describe or link to more broadly applicable safeguarding science information. There may be a link, for example to a risk assessment and mitigation plan that is specific to the project or that applies to all projects and data within the broader organization. Some elements of safeguarding science are already included in other sections of the maDMP and should not be repeated or referenced in this section (e.g., checksum, data access, data security-privacy measures, ethical issues, intellectual property, partner agreement, protection level, retention/disposition planning, security classification, succession plan, versioning, etc.). maDMPThe central module provides high level information about the maDMP itself. It is the root of the metadata application profile. There are 10 mandatory questions (title, ID, date created, date modified, schema version, language, access, protection level, security classification, ethical issues). The submodules depicted in the conceptual model diagram, above, contain approximately 30 mandatory questions. There are also many additional optional questions. Organizations, when implementing the maDMP Standard, may choose to make optional questions mandatory depending on the use case or on the data lifecycle stage. To achieve machine-actionability, answers to questions are broken down into component parts, known as ‘fields’, to provide structured output. For example, the answer to the question “how big is the dataset” is recorded in two separate fields: size (numeric value) and units. In addition, wherever possible, the user is presented with a choice of answers known as a ‘controlled vocabulary’ to select from. For example, there are three allowed answers to the question about access to the maDMP: open, shared, or closed. To ensure consistency in a shared understanding, the user is provided with a definition of each of these terms. ContactSpecifies the party that can provide any information on the maDMP. This is not necessarily the maDMP creator, and can be a person or an organisation. There is one mandatory question (contact information).ApprovalSpecifies the approval status of the maDMP (e.g., approved, rejected, submitted, not applicable, unknown), the name and position of the approver, the approval date, and any other relevant information. In order for a basic minimum maDMP to be 'approved', all 'required' fields must have been completed. As the maDMP evolves over time, there may be additional required fields depending on the responses to other questions. For example, maDMP 'approval date' becomes required IF 'approval status' = 'approved', 'rejected', or 'submitted'. Another example: 'disposition action completed date' becomes required WHEN the action has been taken.ContributorFor listing all parties involved in the process of the data management described by this maDMP, and those parties involved in the creation and management of the maDMP itself. There are four mandatory questions (name, identifier, role, and affiliation).ProjectDescribes the project associated with the maDMP, if applicable. It can be used to describe any type of project, not only funded projects (e.g., internal projects, PhD theses, etc.). There is one mandatory question.Partner organizationFor identifying partner organizations, type of agreements, and links to download the agreement when available (e.g., MOA - Memorandum of Agreement; MOU - Memorandum of Understanding; Indigenous data sharing agreement; BCR-band council resolution; Treaty; collaborative agreement; cooperative agreement; contract; cost-sharing agreement; contractual material; funding collaboration agreement; grant agreement; service level agreement, etc.). All questions are optional.FundingTo indicate if a project is funded or not and to identify funding sources (e.g. NSF, EC, EPA, Tri-Agency, internally funded). When the project is funded, there are two mandatory questions (funder, type of funding)CostProvides a list of costs related to data management.DatasetThis follows the defintion of Dataset in the W3C DCAT specification. Dataset can be understood as a logical entity depicting data, e.g. raw data. It provides high level information about the data. The granularity of dataset depends on a specific setting. In edge cases it can be a file, but also a collection of files in different formats. See FAQ for more details. Questions provide information on data collection, dataset type, technical resources, subject, metadata, data completeness, data criticality, access, data documentation, intellectual property, language, distributions, version history, data size, geographic coverage, protection level, security and privacy, backups, computing environment, host, software and computer code, and disposition planning. All questions are optional.Security and PrivacyUsed to indicate any specific requirements related to security and privacy of a specific dataset (e.g., to indicate that data are not anonymized). There is one mandatory question.Technical ResourceFor specifying equipment needed/used to create or process the data, e.g. a microscope, etc. All questions are optional.Disposition PlanningPlanning for a dataset’s end-of-life, is also called disposition planning. Disposition generally means taking one of three actions with respect to a dataset: destroying/deleting it; transferring it to an archives; transferring the control over the authoritative instance of the dataset to another organization (not the same thing as sharing). After you dispose of a dataset, you or your organization no longer has control over that dataset, or it may no longer exist at all. Generally speaking, disposition is a term that applies only to records, and more specifically, to authoritative records. Mandated definitions of “records” and “disposition” may vary across jurisdictions, so use the definition required of your context. For example, Government of Canada institutions need to consider whether datasets under their control should be considered records or publications as defined the Library and Archives of Canada Act, in order to determine requirements for end-of-lifecycle management. For organizations in which there is no definition of disposition and records, consider aligning with the definitions featured in ISO 30300:2020 (en) Information and documentation – Records management – Core concepts and vocabulary (consider also definitions in ISO/TR 8344:2024(en), Information and documentation — Issues and considerations for managing records in structured data environments). Generally speaking, disposition is not a term that applies to the weeding of library matter (e.g., tossing surplus copies of a disseminated dataset). Retention specifications:Retention refers to how long a dataset needs to be maintained, according to requirements (for detailed definitions, see ISO 3030:2020). Requirements for the retention period may be based on scientific, administrative, fiscal, legal, historical, etc. Retention may be indeterminate (meaning, kept forever), determinate (kept for a specific period), or transitory. When retention is determinate, retention specifications typically include three elements: a retention period, which is the amount of time the dataset needs to be kept to meet requirements; an initiator or “trigger” which begins the retention period; a rationale for the retention period and trigger. Conversely, retention may be determined by a destruction requirement. There are two mandatory questions related to retention (destruction; perpetual use) and many optional questions that become mandatory over time as things move through the data lifecycle.Disposition ActionWhen a dataset has been disposed – meaning destroyed, transferred to a national archives, or transferred to another organization – record these end-of-lifecycle actions for documented disposition. This nest is for disposition actions that have actually been effected; for planned (future) actions, see the nest for “disposition planning”. There are four optional questions that become mandatory once the action has been completed (date, authorization, type, description).DistributionThis follows the definition of Distribution in the W3C DCAT specification. Distribution points to a specific instance of a dataset. Hence, distribution contains information such as the format and size of files. A dataset might be available in multiple serializations that may differ in various ways, including security classificaiton and protection level, natural language, media-type or format, schematic organization, temporal and spatial resolution, level of detail or profiles (which might specify any or all of the above). Examples of distributions include a CSV file, a data-cube, files made accessible according to different profiles such as XML or JSON schemas, anonymized/de-identified files, etc. There is one mandatory question (update frequency) and many optional questions that become mandatory over time as things move through the data lifecycle.LicenseUsed to indicate the license under which data (each specific Distribution) is made available. It also allows for modelling embargoes. See FAQ for more details. There are two optional questions (license and start date) that become mandatory once there is a data distribution that is open.HostProvides information on the system where data are stored. It can be used to provide details on a repository where data are deposited, e.g. a Core Trust Seal certified repository located in Europe that uses DOIs. It can also provide details on systems where data are stored and processed during research, e.g. a high performance computer that uses fast storage with two daily backups. All questions are optional.MetadataProvides a pointer to a metadata standard used to describe the data. It does not contain any actual metadata relating to the dataset. There are three mandatory questions (identifier, ID, language of the metadata).Indigenous considerationsUsed to provide specific information relevant to Indigenous considerations (not found elsewhere in the maDMP), in line with funder requirements (e.g., Canada's Tri-Agency), the United Nations Declaration on the Rights of Indigenous Peoples (UNDRIP), and CARE Priniciples for Indigenous data governance. This is applicable in Europe (e.g., Sami), in the Americas (e.g., Lakota in the USA, the Mayas in Guatemala, the Aymaras in Bolivia, the First Nations in Canada), in the circumpolar region (e.g., the Inuit and Aleutians), in Australia (e.g., the Aborigines and Torres Strait Islanders), in New Zealand (e.g., the Maori), and elsewhere. Indigenous considerations would include, for example, identification of Indigenous groups, Indigenous community approval of the project, Indigenous control over data, Indigenous traditional knowledge, Indigenous research methods, use of Indigenous languages. The existence of other Indigenous related information may be identified in this section with the details provided in other sections of the maDMP. This includes Indigenous data sharing agreements (identified under Partner Organization), Indigenous languages used (identified under maDMP language and/or Dataset language and/or Distribution language), Indigenous data governance (described under Dataset data governance), Indigenous contributor role such as Indigenous traditional knowledge keeper (identified under Contributor role), and use of Unified Canadian Aboriginal Syllabics Extended character encoding (identified under maDMP character unicode block and/or Distribution character unicode block. There is one mandatory question in this module (whether or not Indigenous consideration exist). There are 15 optional questions, five of which become mandatory if applicable (dmp discussed with Indigenous community, description of Indigenous considerations, Indigenous control over data, traditional knowledge, community approval). |
SPECIFICATION |
Properties in 'affiliation'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
business | Information about contributor's organization if organization type is business REQUIREMENT:
| Nested Data Structure | 0..1 | ||
country | Country where the organization the contributor is affiliated to, is located REQUIREMENT:
| Nested Data Structure | 0..1 | ||
educational_institution | Educational institution of the contributor REQUIREMENT:
| Nested Data Structure | 0..1 | ||
government_department_or_agency | Government department or agency affiliated with the contributor REQUIREMENT:
| Nested Data Structure | 0..1 | ||
non_profit | Non-profit organization affiliated with the contributor for the DMP REQUIREMENT:
| Nested Data Structure | 0..1 | ||
other | Description of the affiliation when affiliation type is "other" (e.g., Citizen science; for profit NGO, etc.) REQUIREMENT:
| String | 0..1 | What is the contributor's other affiliation? | |
province_state | Province or state of the organization the contributor is affiliated to. REQUIREMENT:
| Nested Data Structure | 0..1 | ||
type | Type of organization the contributor is affiliated to. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | No affiliation | What is the contributor's affiliation (type)? |
Properties in 'agreement'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
agreement_download_url | Download link to the partner organization agreement document REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | Provide a link to the partner organization agreement. |
description | To provide any free-form text information description on the agreement made with the partner organization REQUIREMENT:
| String | 0..1 | Agrees to gaze at the stars | Describe the project agreement with the partner organization. |
type | Partner organization agreement type (e.g., MOA - Memorandum of Agreement; MOU - Memorandum of Understanding; Indigenous data sharing agreement; BCR-band council resolution; Treaty; collaborative agreement; cooperative agreement; contract; cost-sharing agreement; contractual material; funding collaboration agreement; grant agreement; service level agreement) REQUIREMENT:
| String | 1 | cooperative agreement | What type of partner organization agreement exists? |
Properties in 'approval'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
by_mbox | Email of the person who approved the maDMP REQUIREMENT:
| String | 0..1 | What is the approval person's email? | |
by_name | Name of the person who approved the maDMP REQUIREMENT:
| String | 0..1 | What is the name of the approval person? | |
by_position | Job position of the person who approved the maDMP REQUIREMENT:
| String | 0..1 | Director | What is the position of the approval person? |
date | DMP Approval date. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2023-12-31 | What was the date of the approval action? |
description | To provide any free-form text information on the approval for the DMP REQUIREMENT:
| String | 0..1 | Need to respond to all required fields | Provide a description of the approval. |
status | Approval status for the DMP REQUIREMENT:
| Term from Controlled Vocabulary | 1 | approved | What is the maDMP approval status? |
Properties in 'business'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
business_id | Business ID REQUIREMENT:
| Nested Data Structure | 0..1 | ||
name | Business name REQUIREMENT:
| String | 1 | What is the contributor's business affiliation name? |
Properties in 'business_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Business identifier REQUIREMENT:
| String | 0..1 | What is the contributor's business affiliaton identifier? | |
registry_URI | Link to the identifier system used to identify the business REQUIREMENT:
| URI | 0..1 | Where can the reference be found | |
registry_name | To indicate what identifier system is used to identify the business when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | Registre des entreprises de la chambre de commerce | What is the name or title of the reference used to identify the business? |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | what version of the reference was used at the time where the identifier was entered | |
type | Business identifier type REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | What type of identification system uniquely identifies the business? |
Properties in 'collection'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
data_earliest_date | The earliest date in the case of time series data. Encoded using the ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 1973-01-01 | In the case of time-series data, what is the earliest date of the data in the series? |
data_latest_date | For time series data, date of the latest data in the series. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2022-12-31 | For time series data, what is the date of the latest data in the series? |
dataset_last_updated | Date when the dataset was last updated. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2023-07-20 | When was dataset last updated? |
dataset_size | Size of the dataset from which distributions are derived. REQUIREMENT:
| Number | 0..1 | 5 | What is the size of the dataset according to the specified units? |
dataset_size_units | Dataset size units REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | PB - petabytes | What units were used to measure the size of the dataset? |
dataset_update_frequency | The update frequency of the data in the dataset REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | 7 days | How frequently are the data updated? |
description | To describe the data collection processes REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | 7 days | How frequently are the data updated? |
growth_annual_terabytes | The dataset annual growth rate in terabytes per year. Important information needed when planning storage and associated budget REQUIREMENT:
| Number | 0..1 | What is the expected annual growth rate of the dataset (terabytes per year)? | |
growth_end_date | Date on which data collection for this dataset is expected to cease REQUIREMENT:
| Date | 0..1 | On what date is data collection anticipated to end? |
Properties in 'community_approval'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | To indicate whether the project has approval from an Indigenous community. REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | not applicable | Has an Indigenous community aproved this project? |
status | To provide any free-form text information on the project approval from the Indigenous communities. REQUIREMENT:
| String | 0..1 | Describe the Indigenous community approval. |
Properties in 'computing_environment'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
data_management_system | To describe the database management system or other computerized data system used to store or manage active data. Every other systems used to access the data should be described as distributions. REQUIREMENT:
| Nested Data Structure | 0..1 | ||
hardware_requirements | Minimum requirements for processing data for a specific purpose
REQUIREMENT:
| Nested Data Structure | 0..1 | ||
software | Repeat as many times as needed to describe all software and code used for data collection, data processing, data analysis, data dissemination. Fill in the computer code or the software section. If applicable, fill also the proprietary software section and the software management plan section. You may also want to provide information about the workflow documentation in the dedicated section. REQUIREMENT:
| Nested Data Structure | 0..n |
Properties in 'contact'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
city | City of the location of the responsible organization or individual
REQUIREMENT:
| String | 0..1 | Sherbrooke | In which city is the responsible contact located? |
contact_id | Persistent identifier associated with the contact REQUIREMENT:
| Nested Data Structure | 1 | ||
country | Country of the organization the contact is affiliated to REQUIREMENT:
| Nested Data Structure | 0..1 | ||
delivery_point | Enter the street address for the responsible organization or individual
REQUIREMENT:
| String | 0..1 | 2144; King West | What is the contact person's civic address? |
fax | Telephone number of a facsimile machine for the responsible organization or individual. REQUIREMENT:
| Number | 0..n | 1 (819) 5645698 | What is the contact person's fax number? |
hours_of_service | The time period (including time zone) when the organization or individual can be contacted
REQUIREMENT:
| String | 0..1 | 8:30/12:00; 13:00/16:30 EST | What are the hours and time zone during which the organization or individual can be contacted? |
mbox | E-mail address REQUIREMENT:
| String | 1 | xxxxxx@canada.ca | What is contact person's e-mail address? |
name | Name of the contact person REQUIREMENT:
| String | 1 | Winnie Pooh | What is contact person's name? |
organization | Organization the contact person is affiliated to. For Canadian Departments and agencies, conform with http://www.tbs-sct.gc.ca/fip-pcim/reg-eng.asp. Sub and sub-sub organization (sectors, branches, etc.) may optionally be added, separated by semicolons. REQUIREMENT:
| String | 0..1 | Government of Canada; Natural Resources Canada; Earth Sciences Sector; Canada Centre for Mapping and Earth Observation | Which organization does the contact person belong to? |
position | Position of the contact if contact is a person. REQUIREMENT:
| String | 0..1 | Senior Systems Scientist | What is the position of the contact person? |
postal_zip_code | ZIP or other postal code of the location
REQUIREMENT:
| String | 0..1 | J1J 2E8 | What is the contact person's postal code or zip code? |
province_state | Province or state of the location. For Canadian Provinces and Territories use the Data reference standard on Canadian provinces and territories
REQUIREMENT:
| Nested Data Structure | 0..1 | ||
role | Role of the reponsible party. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | Contact | What is the role or function of the contact person or organization? |
telephone | Telephone number by which individuals can speak to the responsible organization or individual
REQUIREMENT:
| Number | 0..n | 1 (819) 5645600 | What is the contact person's telephone number? |
url | On-line information that can be used to contact the responsible individual or organization. This element should be expressed as a URL that will guide the user to further information online.
REQUIREMENT:
| URI | 0..1 | www.geogratis.gc.ca | What is the URL that links to the contact details of the responsible person or organization? |
Properties in 'contact_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Contact person's unique identifier REQUIREMENT:
| String | 1 | 0000-0000-0000-0000 | What is the contact person's unique ID? |
registry_URI | Link to the identifier system used to identify the contact REQUIREMENT:
| URI | 0..1 | https://gcdirectory-gcannuaire.ssc-spc.gc.ca/en/GCD/?pgid=002 | Where can the identifier system be accessed? |
registry_name | To indicate what identifier system is used to identify the contact when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | GC Directory | What other identifier system is used? |
registry_version | To indicate the version number or date when the system was consulted REQUIREMENT:
| String | 0..1 | 2024/12/30 | What version of the identifier system was used at the time where the identifier was entered? |
type | Identifier type. It is recommended to use ORCID ID for scientists and researchers. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | orcid |
Properties in 'contributor'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
affiliation | Contributor affiliation status with an outside organization REQUIREMENT:
| Nested Data Structure | 1..n | ||
city | City of the location of the contributor or the cited responsible party REQUIREMENT:
| String | 0..1 | In which city is the contributor or cited responsible party located? | |
contributor_id | Identifier of the contributor REQUIREMENT:
| Nested Data Structure | 1 | ||
delivery_point | Enter the street address for the contributor or the cited responsible party REQUIREMENT:
| String | 0..1 | What is the contributor or cited responsible party's civic address? | |
fax | Telephone number of a facsimile machine for the contributor or cited responsible party REQUIREMENT:
| Number | 0..n | What is the contributor or cited responsible party's fax number? | |
hours_of_service | The time period (including time zone) when the contributor or the cited responsible party can be contacted
REQUIREMENT:
| String | 0..1 | What are the hours and time zone during which the contributor or cited responsible party can be contacted? | |
mbox | Mail address REQUIREMENT:
| String | 0..1 | yyyyyy@canada.ca | What is the contributor's email? |
name | Name REQUIREMENT:
| String | 1 | Christopher Robin | What is the contributor's name? |
position | Role or position of the contributor or cited responsible party REQUIREMENT:
| String | 0..1 | What is the position of the contributor or cited responsible party? | |
postal_zip_code | ZIP or other postal code of the location REQUIREMENT:
| String | 0..1 | What is the contributor or cited responsible party's postal code or zip code? | |
role | Type of contributor (e.g., cited responsability party, distribution contact, author, investigator, collaborator, field technician, researcher, data steward, Indigenous traditional knowledge keeper) REQUIREMENT:
| String | 1..n | Data steward | What is the contributor's role? |
telephone | Telephone number by which individuals can speak to the contributor or cited reponsible party REQUIREMENT:
| Number | 0..n | What is the contributor or cited responsible party's telephone number? | |
url | On-line information that can be used to contact the contributor or the cited responsible party. This element should be expressed as a URL that will guide the user to further information online.
REQUIREMENT:
| URI | 0..1 | What is the URL that links to the contact details of the contributor or cited responsible party? |
Properties in 'contributor_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Identifier for a contributor person REQUIREMENT:
| String | 1 | 1111-1111-1111-1111 | What is the contributor's unique ID? |
registry_URI | Link to the identifier system used to identify the contributor REQUIREMENT:
| URI | 0..1 | https://gcdirectory-gcannuaire.ssc-spc.gc.ca/en/GCD/?pgid=002 | Where can the identifier system be found? |
registry_name | To indicate what identifier system is used to identify the contributor when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | GC Directory | What identifier system is used to identify the contributor? |
registry_version | To indicate the version number or date when the system was consulted REQUIREMENT:
| String | 0..1 | 2024/12/30 | What version of the system was used or what date was the system consulted? |
type | Identifier type. It is recommended to use ORCID ID for scientists and researchers. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | other | Which identifier type is used for the contributor's unique ID (orcid, isni, openid, other)? |
Properties in 'cost'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
cost_documentation | Any external material documenting the costing details. REQUIREMENT:
| Nested Data Structure | 0..n | ||
currency_code | Allowed values defined by ISO 4217. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | USD | What is the currency for the cost amount? |
description | Description REQUIREMENT:
| String | 0..1 | Costs for running the project. | Describe the costs. |
title | Title REQUIREMENT:
| String | 1 | Cloud storage and software | Provide a title for the costs. |
value | Value REQUIREMENT:
| Number | 0..1 | 1,000,000 | What is the total cost amount? |
Properties in 'cost_documentation'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | A URL of that gives access to the costdocumentation. e.g., landing page, feed, SPARQL endpoint. The access URL should be used for the URL of a service or location that can provide access to cost documentation, typically through a Web form, query or API call. REQUIREMENT:
| URI | 0..1 | https://007gc.sharepoint.com/stb/wqmsd/Project.aspx | Provide a link to the cost documentation. |
download_url | Download URL to the cost documentation REQUIREMENT:
| URI | 0..1 | https://gc.sharepoint.com/dpmo/projects/project 345 business charter.docx | Provide the download URL for the cost documentation. |
name | Title of the external document documenting the cost REQUIREMENT:
| String | 1 | Project Business Charter | What is the title of the cost documentation? |
Properties in 'country'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
code | The 2-letter code of the country, as per the ISO standard 3166-1 Codes for the representation of names of countries and their subdivisions – Part 1: Country codes REQUIREMENT:
| Term from Controlled Vocabulary | 1 | US | Where is the contact located (country code)? |
name | The name of the country, as per the ISO standard ISO 3166-1 Codes for the representation of names of countries and their subdivisions – Part 1: Country codes REQUIREMENT:
| String | 1 | United States of America | Where is the contact located (country name)? |
Properties in 'data_management_system'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | Web or network-accessible URL for accessing the system REQUIREMENT:
| URI | 0..1 | https://dmssystem.org | What url provides access to the data management system? |
authentication | User access and authentication mechanisms. REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | OAuth | What mechanism is used for authentication and access control? |
availability | Defines whether the system is operational 24/7 or has downtime periods (e.g., 24/7, scheduled downtime) REQUIREMENT:
| String | 0..1 | scheduled down time | What is the availability of the distribution? |
backup_frequency | Backup frequency of the system REQUIREMENT:
| String | 0..1 | weekly | How often is the distribution backed up to the host? |
backup_type | Type of backup performed on the data (e.g., incremental, full, differential, synthetic full) REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | What type of backup system is used for the host? | |
certified_with | Certifications relevant to the system (e.g., CoreTrustSeal, ISO 16363). REQUIREMENT:
| String | 0..1 | coretrustseal | What is the host server certified with? |
compliance_standards | Standards the system follows for security, data management, and governance (e.g., GDPR, HIPAA, SOC 2 compliance) REQUIREMENT:
| String | 0..n | GDPR | What standard is the data management system compliant to regarding data security, data management or data governance? |
data_transfer_maximum_latency | Maximum data transfer latency of the data en ms, i.e. the delay of data transfer REQUIREMENT:
| Number | 0..1 | 50 | What is the data transfer maximum latency of the distribution? |
data_transfer_minimum_throughput | Maximum throughput of the dataset in Mbps REQUIREMENT:
| Number | 0..1 | 10 | What is the maximum throughput of the distribution? |
description | Brief explanation of the system’s purpose and functionality in relation to this dataset. If relevant, indicate the data types managed by the system. REQUIREMENT:
| String | 0..1 | During the active phase of the research project, active and transitory data are managed (versioned and tracked) within DBMSX. | What purpose does the system serve in relation to the dataset? |
geo_location | The geographical location of the server hosting the system expressed using ISO 3166-1 country code. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | CA | Where is the location of the host server? |
pid_system | Persistent identifier system used by the system. REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | ark | What pid system is used for the host server? |
protocol | The protocol used to interact with the system REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | OAI-PMH | What type of protocol is used to interact with the data management system? |
storage_type | Type or types of storage used by the data management system REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | tape storage | What type of storage the data management system relies on? |
support_checksum | Indicates whether checksum verification is supported REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Does the data management system support checksum? |
support_versioning | To indicate if the data management system supports versioning, meaning changes to datasets are tracked internally REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Does the data management system support versioning? |
title | Name of the active data management system used to store/process data (e.g., PostgreSQL, MySQL, Dataverse, iRODS, etc.) REQUIREMENT:
| String | 1 | NAQUA | How is the data management system called? |
type | The type of system used to store and manage active data. Note that a time-series database like TimescaleDB is actually a relational database, but because it's optimized for time-series data, it gets its own distinct category REQUIREMENT:
| Term from Controlled Vocabulary | 1 | Relational Database Management System (RDBMS) | What type is the data management system? |
version | Version of the data management system REQUIREMENT:
| String | 0..1 | 3.2.1 | If applicable, what is the version of the data management system? |
visibility | Defines whether the data management system is accessible internally within an organization or externally to broader audiences. Allowed values: Internal (accessible only within a specific organization or project), External (accessible to users outside the organization via public or controlled access) REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | Internal | Is the data management system accessible only internally or also externally? |
Properties in 'dataset'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
collection | Information on how the data is collected. REQUIREMENT:
| Nested Data Structure | 0..1 | ||
computing_environment | To describe the operational environment used for data collection, processing, analysis and dissemination. REQUIREMENT:
| Nested Data Structure | 0..1 | ||
data_completeness | Dataset percentage completeness REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | 95% or greater | Describe the data completness. |
data_criticality | To indicate how important the data are for the organization to achieve its goals. Example values: business function continuity and improvement, IM or IT modernization, intergovernmental agreement, minister/deputy minister priority, mission critical, policy compliance (departmental), policy compliance (federal), regulatory, risk mitigation, treasury board submission, vote netted revenue (VNR), other program priority (specify) REQUIREMENT:
| String | 0..1 | business function continuity and improvement | What is the data criticality? |
data_governance_description | Indicate if there is a data governance framework like, for example, a specified departmental data governance framework, and/or if data governance is aligned with published principles such as the CARE Principles for Indigenous Data Governance, the First Nations principles of ownership, control, access and possession (OCAP), the Māori data governance model, or some other specified data governance model. REQUIREMENT:
| String | 1 | Describe the data governance. | |
data_quality_assurance | Data Quality Assurance. Note: Data quality control level is provided at the distribution level. REQUIREMENT:
| String | 0..n | We use a complicated, undocumented system for data QA/QC | Describe the data quality assurance. |
dataset_documentation | Repeat as many times as needed to list all existing documentation, procedures for data processing, management, analysis and dissemination. For example: code book, contract, data dictionary, data production specification (ISO 19131 compliant), ELN (electronic lab notebook) protocol, QA/QC methods, SOP (standard operating procedure), workflows, etc. Make sure you also provide the related computing environment information in the dedicated section. REQUIREMENT:
| Nested Data Structure | 0..n | ||
dataset_id | Dataset ID REQUIREMENT:
| Nested Data Structure | 1 | ||
description | Description is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file. REQUIREMENT:
| String | 0..1 | mountains of data | Describe the dataset. |
disclaimer | limitation affecting the fitness for use of the resource or metadata REQUIREMENT:
| String | 0..1 | not to be used for navigation | Indicate any limitation affecting the fitness for use of the dataset |
disposition_action | Used to document disposition that has been effected in relation to a dataset. Note: when all data associated with a dataset has been disposed, also indicate this in “dmp/dataset/disposition_completed.” REQUIREMENT:
| Nested Data Structure | 0..n | ||
disposition_completed | Date on which disposition effected. Encoded using the ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2019-06-0 | Has ALL data associated with this dataset been disposed? (i.e., no data remains with the institution, and none is expected to accrue in the future) |
disposition_planning | Used to document information in anticipation of a future disposition review.
Note: does not document disposition actions actually effected. REQUIREMENT:
| Nested Data Structure | 0..1 | ||
distribution | To provide technical information on a specific instance of data. REQUIREMENT:
| Nested Data Structure | 0..n | ||
general_data_format | Main format of the dataset according to DDI General_DATA_Format controlled vocabulary https://rdf-vocabulary.ddialliance.org/ddi-cv/GeneralDataFormat/2.0.3/GeneralDataFormat.html. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | stillimage | What is the main format of the dataset? |
geodetic_datum | If the dataset contains geospatial data, indicate the geodetic datum (coordinate reference system) REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | ED50 (older European) | Which geodetic datum is this distribution for? |
geographic_coverage | The geographical area covered by a geospatial dataset REQUIREMENT:
| String | 0..1 | In the case of a geospatial dataset, what is the geographic area is covered? | |
intellectual_property | Intellectual property related to the dataset REQUIREMENT:
| Nested Data Structure | 1 | ||
issued | Date the dataset was issued. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2023-07-20 | When was the dataset issued? |
keyword | Keyword REQUIREMENT:
| String | 0..n | keyword 1, keyword 2 | Provide some keywords related to this dataset. |
language | Language of the dataset expressed using ISO 639-3 REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | mul | What language is used in this dataset? |
metadata | To describe metadata standards used. REQUIREMENT:
| Nested Data Structure | 0..n | ||
personal_data | To indicate if personal data exists in the dataset REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Do these data include personal information? |
preservation_statement | Preservation Statement. Details concerning retention and disposition should be provided in dmp/dataset/disposition_planning/ REQUIREMENT:
| String | 0..1 | Provide a general statement regarding preservation of the dataset. | |
security_and_privacy | To list all issues and requirements related to security and privacy. Create a new entry for each issue or requirement. REQUIREMENT:
| Nested Data Structure | 0..n | ||
sensitive_data | Sensitive data are data for which injury that could reasonably be expected as a result of a loss of confidentiality (resulting from unauthorized disclosure), loss of integrity (resulting from unauthorized modification or destruction), or loss of availability (resulting from unauthorized removal or other disruption). See, for example, Treasury Board of Canada, Policy on government security. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Does the dataset contain sensitive data? |
subject | Topic to which a dataset pertains. REQUIREMENT:
| Nested Data Structure | 0..n | ||
supported_works_url | An URL or DOI that gives access to the supported work. REQUIREMENT:
| URI | 0..n | Provide a URL to this supported work. | |
technical_resource | To list technical resources involved in the collection and processing of the dataset, and for which documentation is required. For computing environments, please record information in the dmp/dataset/computing_environment field REQUIREMENT:
| Nested Data Structure | 0..n | What technical resources are used to implement the DMP? | |
title | Title is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file. REQUIREMENT:
| String | 1 | fast sun images | What is the title of this dataset? |
type | If appropriate, type according to: DataCite and/or COAR dictionary. Otherwise use the common name for the type, e.g. raw data, software, survey, etc. https://schema.datacite.org/meta/kernel-4.1/doc/DataCite-MetadataKernel_v4.1.pdf http://vocabularies.coar-repositories.org/pubby/resource_type.html REQUIREMENT:
| String | 0..1 | image | What type of dataset is this? |
Properties in 'dataset_documentation'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | A URL of that gives access to the dataset documentation. e.g., landing page, feed, SPARQL endpoint. The access URL should be used for the URL of a service or location that can provide access to dataset documentation, typically through a Web form, query or API call. REQUIREMENT:
| URI | 0..1 | some.intranet/.../project page.aspx | Provide a link to the dataset documentation. |
description | To describe the documentation of the dataset REQUIREMENT:
| String | 0..1 | Describe the dataset documentation. | |
download_url | Download URL to the dataset documentation REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | Provide the download URL for the dataset documentation. |
name | Document name REQUIREMENT:
| String | 0..1 | code book | What is the name of the dataset documentation? |
Properties in 'dataset_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Identifier for a dataset REQUIREMENT:
| String | 1 | University of Vienna Phaidra (univie.ac.at) | Provide the dataset identifier ID. |
registry_URI | Link to the registry or system used to identify the dataset REQUIREMENT:
| URI | 0..1 | https://ecollab.ncr.int.ec.gc.ca/theme/1275886/DataInventoryProject/Data-Asset-Inventory_Master-Spreadsheet_FINAL.xlsx | Where can the registry or system be found? |
registry_name | To indicate what registry or system is used to identify the dataset when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | ECCC Data Asset Inventory | What registry or system was used to identify the dataset? |
registry_version | To indicate the version number or date when the system or registry was consulted REQUIREMENT:
| String | 0..1 | 2024-12-30 | What version of the registry/system was used or what date was the registry/system consulted? |
type | Identifier type REQUIREMENT:
| Term from Controlled Vocabulary | 1 | url | What is the dataset identifier ID type? |
Properties in 'disposition_action'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
authorization | Indicate disposition authorization number and details when available. May also be used to document internal signoff. REQUIREMENT:
| String | 1 | DA 2018/001, Application Guide for National Registration version 2.0. Signoff by CIO on 2020-03-13. | What legal instrument authorized the disposition? |
date | Date on which disposition effected. Encoded using the ISO 8601 Date compliant string REQUIREMENT:
| Date | 1 | 2020-03-1 | On what date was disposition effected? |
description | To document the scope of disposition action effected, as well as other details when required (e.g., means, issues). REQUIREMENT:
| String | 1 | All non-disseminated datasets associated with the project NameMyTree were manually deleted from drive Z by project lead. Litigation and ATIP checks had been completed 2020-01-12. Backup tapes not addressed. | What was the scope of the disposition? What details are important for documented disposition? |
type | Indicate the type of action taken to dispose of the data (scope of the data to be detailed in the description field) REQUIREMENT:
| Term from Controlled Vocabulary | 1 | alienated from government control | Was the dataset disposed by destruction, transfer to LAC, or alienation? |
Properties in 'disposition_impediment'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | Include the name of the litigation, software, etc. where applicable.
Note: if there is a known end date to the disposition impediment, consider entering it in “dmp/dataset/disposition_planning/disposition_review _next” REQUIREMENT:
| String | 0..1 | Thompson et al v. Canada | What is preventing you from effecting disposition, once the retention period has elapsed? |
type | To indicate the type of impediment to disposition. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | agreement | What type of impediment blocks you from effecting disposition? |
Properties in 'disposition_planning'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
archival_value | Archival value according to the national archives. (Applies to records only.)
For the Government of Canada, refer to definition of government records in the Library and Archives of Canada Act. Nevertheless, except in instances in which a distribution is considered a “publication” as defined in the Library and Archives of Canada Act, datasets under the control of a government institution likely meet the definition of a government record in the Act. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes all | Does the dataset have archival value? |
archival_value_description | Indicates nature and scope of the data with archival value according to national archives. REQUIREMENT:
| String | 0..1 | What is the nature and scope of the data with archival value according to Library and Archives Canada instructions? | |
disposition_impediment | For noting time-limited impediments to effecting disposition at the end of the dataset's retention period. Note: use the retention specification nest to indicate an indefinite retention period or a perpetual use requirement. REQUIREMENT:
| Nested Data Structure | 0..n | ||
disposition_planning_last_reviewed | To record the most recent date on which the values entered in disposition planning properties were reviewed. Encoded using the relevant ISO 8601 Date compliant string. Indicate the type of action taken to dispose of the data (scope of the data to be detailed in the description field) REQUIREMENT:
| Date | 0..1 | 2024-11-20 | When was the information in the disposition planning section last reviewed? |
disposition_review_next | To record the next date(s) on which the dataset should be reviewed for disposition. (This may be the end of a retention period, the date on which a disposition impediment will be lifted, or some other date). Encoded using the relevant ISO 8601 Date compliant string. REQUIREMENT:
| Date | 0..n | 2029-11-20 | When should someone review whether disposition can be effected? |
retention_schedule_url | A URL that leads to the applicable retention schedule REQUIREMENT:
| URI | 0..1 | //intranet.server/.../retention_schedule | Where can you click to see the retention schedule? |
retention_specification | REQUIREMENT:
| Nested Data Structure | 0..n |
Properties in 'distribution'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | A URL that gives access to the distribution. e.g., landing page, feed, SPARQL endpoint. The access URL should be used for the URL of a service or location that can provide access to the distribution, typically through a Web form, query or API call. REQUIREMENT:
| URI | 0..1 | some.data.catalogue/.../project_uuid | What is the access URL to the dataset? |
available_until | Indicates how long this distribution will be/should be available. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2023-07-20 | When is the dataset available until? |
byte_size | Size of the dataset distribution in measured in bytes. REQUIREMENT:
| Number | 0..1 | 5,000,000,000,000 | What is the size of the distribution bytes? |
character_encoding_standard | Character encoding standard used in the distribution REQUIREMENT:
| Term from Controlled Vocabulary | 1 | UTF-16 | What character encoding standard is used for the data? |
character_unicode_block_code | Unicode block used in the distribution. Use the "code" from the Unicode Standard 15.1. https://en.wikipedia.org/wiki/Unicode_block#List_of_blocks REQUIREMENT:
| Term from Controlled Vocabulary | 1 | U+18B0..U+18FF | What is the Unicode block code? |
character_unicode_block_name | Unicode block used in the distribution. Use the "name" from the Unicode Standard 15.1. https://en.wikipedia.org/wiki/Unicode_block#List_of_blocks REQUIREMENT:
| Term from Controlled Vocabulary | 1 | Unified Canadian Aboriginal Syllabics Extended | What is the Unicode block name? |
created | Date of creation of the distribution. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 1 | 2009-11-02 | When was the distribution created? |
data_access | OPEN ACCESS: available to anyone based on an open license (e.g., CC0, CC-BY, Open Government License). SHARED ACCESS: Public access with a license that limits use, that is available to anyone under terms and conditions that are not ‘open' (e.g., CC-BY-NC), shared only with named people or organisations, or via authentication for specific groups that meet certain criteria. CLOSED ACCESS: Internal access only. https://theodi.org/insights/tools/the-data-spectrum/ ; https://www.alerc.org.uk/uploads/7/6/3/3/7633190/an_introduction_to_open_shared_and_closed_data.pdf REQUIREMENT:
| Term from Controlled Vocabulary | 1 | open | Is access to the data open, shared, or closed? |
data_security-privacy_measures | To provide any free-form text information about security or privacy measures. REQUIREMENT:
| String | 0..n | anonymisation, de-identification, encryption, hash function, pseudonymisation, statistical disclosure control, none | What security measures are in places to ensure that security and privacy are not compromised? |
data_size | The RDA standard requires describing size in bytes. However, byte_size does not provide a meaningful number for large files (e.g., a file that would typically be expressed in petabytes). Also, other systems (e.g., national archives) may require both data_size and data_size_units. REQUIREMENT:
| Number | 0..1 | 5 | What is the size of the distribution according to the specified units? |
data_size_units | The RDA standard requires describing size in bytes. However, byte_size does not provide a meaningful number for large files (e.g., a file that would typically be expressed in petabytes). Also, other systems (e.g., national archives) may require both data_size and data_size_units. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | PB - petabytes | What units were used to measure the size of the distribution? |
description | Description is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file. REQUIREMENT:
| String | 0..1 | best quality data before resizing | Describe the distribution of the dataset. |
disposition_completed | Indicates the date on which the distribution was disposed. (That is, the data lifecycle is complete, at the institution).
In instances in which data was never created in relation to a planned distribution, indicates the date on which the creation of the distribution was abandoned.
Encoded using the relevant ISO 8601 Date compliant string
Note: consider adding information to “dmp/dataset/distribution/description” regarding the nature of the disposition. REQUIREMENT:
| Date | 0..1 | 2015-03-24 | Has ALL data associated with this distribution been disposed? If so, indicate date (i.e., no data remains with the institution, and none is expected to accrue in the future) |
distribution_id | ID for the distribution REQUIREMENT:
| Nested Data Structure | 1 | ||
download_url | The URL of the downloadable file in a given format. E.g. CSV file or RDF file. REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | What is the download URL of the dataset. |
end_date | Date of the most recent data in the distribution. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | When will the distribution end? when did the distribution end? | |
file_path | File path is for files that are available internally on shared drives but are not published on the internet. File paths using backslashes instead of forward slashes used for urls. REQUIREMENT:
| URI | 0..1 | What is the file path for this distribution? | |
format | Format according to: https://www.iana.org/assignments/media-types/media-types.xhtml if appropriate, otherwise use the common name for this format.https://www.iana.org/assignments/media-types/media-types.xhtml REQUIREMENT:
| String | 0..n | csv | What is this distribution’s file format? |
geographic_bounding_box | Rectangular spatial extent that encompasses all the geographic locations represented in the data REQUIREMENT:
| Nested Data Structure | 0..1 | ||
host | The host is the system where the data are stored and processed. Be sure to also fill in a physical data asset section to indicate in which the data are hosted especially in which country the server is located if they are hosted on a server or in the cloud. REQUIREMENT:
| Nested Data Structure | 0..1 | ||
issued | Date of the publication of the distribution. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 1 | When was the distribution issued? | |
license | To list all licenses applied to a specific distribution of data. REQUIREMENT:
| Nested Data Structure | 0..n | ||
linked_data_star_rating | To rate the level of openness of the dataset according to the Tim Berners-Lee (founder of the World Wide Web) 5-star rating system for open data. To score the maximum five stars, data must (1) be available on the Web under an open license, (2) be in the form of structured data, (3) be in a non-proprietary file format, (4) use URIs as its identifiers (see also RDF), (5) include links to other data sources (see linked data). To score 3 stars, it must satisfy all of (1)-(3), etc. For guidence see, https://opendatahandbook.org/glossary/en/terms/five-stars-of-open-data/ ; https://5stardata.info/en/ ; https://open.canada.ca/en/openness-rating REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | 1 star | How many stars does this dataset meet according to the Berners-Lee 5-star rating system for open data? |
online_service | To list online services where the distribution can be accessed REQUIREMENT:
| Nested Data Structure | 0..n | ||
openness_other_rating | To rate the level of openness of the dataset according to a system other than the Tim Berner-Lees system, described in dmp/dataset/openness_other_rating_system. REQUIREMENT: | String | 0..1 | What is the dataset openness rate according to the chosen framework? | |
openness_other_rating_system | Describe which system is used to rate the dataset openness when it's not the Tim Berners-Lee 5-star rating system. REQUIREMENT:
| String | 1 | What framework are you using to rate the dataset openness? | |
physical_data_asset | Allows for recording of physical assets (e.g., external hard drives) and/or physical location of servers, data centers, etc. REQUIREMENT:
| Nested Data Structure | 0..n | Is this about a physical copy of the data or a physical object that stores the data? | |
preservation_flag | To flag distributions for digital preservation attention purposes. REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | Does this distribution have a very long or perpetual retention period, or have archival value? | |
protection_level | Protected information is not classified. Information is "protected" when unauthorized disclosure could reasonably be expected to cause injury to a non-national interest (i.e., an individual interest such as a person or an organization). Protected information is any sensitive information that does not relate to national security and cannot be disclosed under access and privacy legislation because of the potential injury to particular public or private interests. Protection levels: Protected A (Injury to an individual, organization or government), Protected B (Serious injury to an individual, organization or government), Protected C (Extremely grave injury to an individual, organization or government). https://www.canada.ca/en/public-services-procurement/services/industrial-security/security-requirements-contracting/safeguarding-equipment-sites-assets-information/levels-security.html#s2 REQUIREMENT:
| Term from Controlled Vocabulary | 1 | protected A | What is the protection level for these data? |
protection_level_other_level | To indicate the protection level of the distribution as per nomenclature found in distribution_protection_level_other_nomenclature REQUIREMENT:
| String | 0..1 | What is the protection level of this distribution according to the nomenclature? | |
protection_level_other_nomenclature | To indicate which nomenclature is used to qualify the distribution protection level when "other" was chosen in distribution_protection_level REQUIREMENT:
| String | 0..1 | What other nomenclature is used to indicate the protection level of the distribution? | |
quality_control_level | Data quality control level. LEVEL 0 (Raw data or minimally processed data. Contains all available measurement data. May contain quality control flags indicating missing or invalid data. LEVEL 1 (A complete dataset of specified quality. The dataset has been subjected to quality assurance and quality control checks and data management procedures. Compliance with documented data quality objectives, standard operating procedures (SOPs), and protocols has been evaluated and documented. If the data have been audited, level '0' status will remain in effect until all audits have been completed and the investigator’s response recorded). LEVEL 2 (A complete, externally consistent dataset of specified quality that has undergone interpretative and diagnostic analyses. A validation level and status discussion must be included in the metadata record associated with the dataset). LEVEL 3 (Data that have received intense scrutiny through analysis or use in modeling. As analysis of the data proceeds, analysts may raise questions about portions of the level '2' dataset. Additional checks and tests will be performed on such data and the Level 3 code will be affixed to data passing these tests. If this scrutiny reveals an inconsistency that appears to be caused by a measurement error, the entire chain of evidence for the measurement will be reviewed). MIXED (A package of datasets with varying levels of data quality). UNKNOWN (Data quality is unknown). Reference: NARTSO Standard. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | level 0 - raw | What is the quality control level of this distribution? |
security_classification_level | Security classification that designates the level of protection against access the data or information requires when unauthorized disclosure could reasonably be expected to cause injury to the national interest – defence and maintenance of the social, political and economic stability of the nation. Classification levels: Unclassified, Restricted (disadvantageous to the interests of the nation), Confidential (injury to the national interest), Secret (serious injury to the national interest), Top Secret (exceptionally grave injury to the national interest). "Other" could include, for example: Clearance, Compartmented information, Critical nuclear weapon design information (CNDWI), No foreign dissemination (NOFORN), Official/For official use only, Official sensitive, Originator controlled dissemination (ORCON), Special intelligence, Sensitive but unclassified. https://www.canada.ca/en/public-services-procurement/services/industrial-security/security-requirements-contracting/safeguarding-equipment-sites-assets-information/levels-security.html#s2 REQUIREMENT:
| Term from Controlled Vocabulary | 1 | unclassified | What is the security classification of this distribution? |
security_classification_level_other_level | To indicate which nomenclature is used to qualify classified information REQUIREMENT:
| String | 0..1 | What other nomenclature is used to describe classified information? | |
security_classification_level_other_nomenclature | To indicate the level of the classified information held by the distribution according o the nomenclature found in distribution_security_classification_level_other_nomenclature REQUIREMENT:
| String | 0..1 | Indicate the level of classified information of the dmp according to the nomenclature | |
spatial_representation_type | Spatial representation type of the data REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | What is the type of digital representation of spatial information in the distribution? | |
start_date | Date of the oldest data in the distribution. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 1 | When is the distribution first started? | |
status | Completion status of the distribution REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | finished | What is the status of the data? |
status_description | Description of the distribution completion status REQUIREMENT:
| String | 0..1 | Describe the status. | |
title | Title is a property in both Dataset and Distribution, in compliance with W3C DCAT. In some cases these might be identical, but in most cases the Dataset represents a more abstract concept, while the distribution can point to a specific file. REQUIREMENT:
| String | 1 | Full resolution images | What is the title of the distribution of the dataset? |
update_frequency | The maintenance and update frequency of the distribution REQUIREMENT:
| Term from Controlled Vocabulary | 1 | daily | How frequently are the data updated and maintained? |
version_history | Version history of the data distribution REQUIREMENT:
| Nested Data Structure | 0..1 |
Properties in 'distribution_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Identifier for the dataset distribution REQUIREMENT:
| String | 1 | Provide the distribution identifier ID. | |
registry_URI | Link to the reference used to identify the distribution REQUIREMENT:
| URI | 0..1 | https://data-donnees.az.ec.gc.ca/data | Where can the registry or system be found? |
registry_name | To indicate what reference is used to identify the distribution when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | ECCC Data Catalogue | What registry or system was used to identify the distribution? |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | 2024/12/30 | What version of the registr/system or what date the registry/system was consulted? |
type | Identifier type REQUIREMENT:
| String | 1 | url | What is the distribution identifier ID type? |
Properties in 'dmp'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access | OPEN ACCESS: available to anyone based on an open license (e.g., CC0, CC-BY, Open Government License). SHARED ACCESS: Public access with a license that limits use, that is available to anyone under terms and conditions that are not ‘open' (e.g., CC-BY-NC), shared only with named people or organisations, or via authentication for specific groups that meet certain criteria. CLOSED ACCESS: Internal access only. https://theodi.org/insights/tools/the-data-spectrum/ ; https://www.alerc.org.uk/uploads/7/6/3/3/7633190/an_introduction_to_open_shared_and_closed_data.pdf REQUIREMENT:
| Term from Controlled Vocabulary | 1 | open | Is access to the maDMP open, shared, or closed? |
approval | Approval of the maDMP REQUIREMENT:
| Nested Data Structure | 1 | ||
contact | Specifies the party which can provide information about the DMP. This is not necessarily the DMP creator, and it can be a person or an organization. REQUIREMENT:
| Nested Data Structure | 1 | ||
contributor | Party involved in the process of data management described by the DMP, or party involved in the creation and management of the DMP itself. REQUIREMENT:
| Nested Data Structure | 1..n | ||
cost | To list costs related to data management. Providing multiple instances of a 'Cost' allows to break down costs into details. Providing one 'Cost' instance allows to provide one aggregated sum. REQUIREMENT:
| Nested Data Structure | 0..n | ||
created | Date and time of the first version of the maDMP. This date must not be changed in subsequent maDMPs. Each maDMP has a "Created" date and a "Modified" date. The modification date contains a timestamp of the last modification of the maDMP. Given two maDMPs with different modification dates, one can identify which is newer by comparing the timestamps. The same creation date indicates different versions of the same DMP. Encoded using the relevant ISO 8601 Date and Time compliant string REQUIREMENT:
| DateTime | 1 | 2021-04-15T10:53:49-5:00 | When was the first version of the maDMP created? |
dataset | To describe data on a non-technical level. REQUIREMENT:
| Nested Data Structure | 1..n | ||
description | To provide any free-form text information on the Data Management Plan (maDMP). It can be a formal statement describing how research data will be managed and documented throughout a research project and the terms regarding the subsequent deposit of the data with a data repository for long-term management and preservation (Library and Archives Canada). DMP's are living documents that outline a project’s plans for research data management. The content, format and length of DMPs depend on the nature of the given research project. DMPs can be developed to guide a single research project or span a multiproject research initiative or longer-term program of research. The DMP submitted at the application stage could, depending on the complexity and duration of the project, be presented as a more high-level outline and then be expanded on throughout the life of the project enabling automatic exchange, integration, and validation of information provided in DMPs. Machine-actonable DMP's (maDMP) are designed to support the exchange of information between systems, to provide basic interoperability between systems producing or consuming maDMPs, acting on behalf of stakeholders involved in the research life cycle (researchers, funders, repository managers, ICT providers, librarians, etc.) and the information represented over the whole DMP lifecycle (Research Data Alliance).
REQUIREMENT:
| String | 0..1 | We're finally get our data under control. | Describe the data management plan. |
dmp_id | Identifier for the DMP itself REQUIREMENT:
| Nested Data Structure | 1 | ||
ethical_issues_description | To describe any existing or potential ethical issues that are not captured in the following related fields: dmp/protection_level, dmp/security_classification_level, dmp/dataset/disposition_planning/legal_issues_description, dmp/dataset/distribution/data_security-privacy_measures, dmp/dataset/distribution/disposition_planning/legal_issues, dmp/dataset/distribution/protection_level, dmp/dataset/distribution/security_classification_level, dmp/dataset/distribution/license/, dmp/dataset/intellectual_property/, dmp/dataset/security_and_privacy/, dmp/indigenous_considerations/. Examples include, but are not limited to: Bias or lacking representation of certain populations; data collected without informed consent; lack of transparency due to absence of clear documentation about data processing, cleaning, or manipulation; the potential impact of the dataset on marginalized groups; potential dual use of the data that could be detrimental to society or specific groups; data that include cultural artifacts or practices that could be used in ways that disrespect cultural values or traditions; failure to recognize the contributions of all parties involved in collecting the data; failure to identify who is accountable for the data. REQUIREMENT:
| String | 0..1 | There are ethical issues because... | Describe any existing or potential ethical issues. |
ethical_issues_exist | To indicate whether there are ethical issues related to these data. It is the responsibility of the researcher or data steward to be aware of any ethical issues related to the data. Ethical issues vary widely depending on the context. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Do ethical issues exist? |
ethical_issues_report | To indicate, for example, where a protocol from a meeting with an ethical committee can be found, or an IRB (Institutional Review Board) report. REQUIREMENT:
| URI | 0..1 | http://report.location | Provide a link to an ethical issues report such as, for examplem and IRB (Institutional Review Board) report. |
indigenous_considerations | Indigenous considerations related to the maDMP or the data. REQUIREMENT:
| Nested Data Structure | 1 | ||
language | Language of the DMP expressed using ISO 639-3 REQUIREMENT:
| Term from Controlled Vocabulary | 1 | eng | What language is the maDMP written in? |
linked_dmp | to link related dmps , for example official-language-equivalent dmps REQUIREMENT:
| Nested Data Structure | 0..n | ||
modified | Indicates maDMP version, so must be set each time the maDMP is modified. Dates can be used to indicate past and planned actions. Dataset contains issue date that indicates whether the actions are planned or already performed. If the dataset issue date is set in the future (compared to the maDMP modification date), then the actions are planned. If the issue date is set in the past (compared to the maDMP modification date), the actions were performed in the past. Encoded using the relevant ISO 8601 Date and Time compliant string REQUIREMENT:
| DateTime | 1 | 2021-04-22T14:32:54-5:00 | When was the maDMP last modified? |
project | Project related to the DMP REQUIREMENT:
| Nested Data Structure | 0..n | ||
protection_level | Protected information is not classified. Information is "protected" when unauthorized disclosure could reasonably be expected to cause injury to a non-national interest (i.e., an individual interest such as a person or an organization). Protected information is any sensitive information that does not relate to national security and cannot be disclosed under access and privacy legislation because of the potential injury to particular public or private interests. Protection levels: Protected A (Injury to an individual, organization or government), Protected B (Serious injury to an individual, organization or government), Protected C (Extremely grave injury to an individual, organization or government). https://www.canada.ca/en/public-services-procurement/services/industrial-security/security-requirements-contracting/safeguarding-equipment-sites-assets-information/levels-security.html#s2 REQUIREMENT:
| Term from Controlled Vocabulary | 1 | protected A | What is the protection level for the maDMP? |
protection_level_other_level | To indicate which nomenclature is used to qualify the dmp protection level when "other" was chosen in dmp_protection_level REQUIREMENT:
| String | 0..1 | What other nomenclature is used to indicate the distribution protection level? | |
protection_level_other_nomenclature | To indicate the protection level of the dmp according to the nomenclature found in dmp_protection_level_other_nomenclature REQUIREMENT:
| String | 0..1 | What protection level applies to the distribution according to the nomenclature? | |
schema_version | DMP schema version REQUIREMENT:
| String | 1 | Which maDMP metadata schema version was used when creating this maDMP? | |
schema_version_uri | DMP schema URI REQUIREMENT:
| URI | 1 | What is the URI to the metadata schema version used when creating this maDMP? | |
security_classification_level | Security classification that designates the level of protection against access the DMP requires when unauthorized disclosure could reasonably be expected to cause injury to the national interest – defence and maintenance of the social, political and economic stability of the nation. Classification levels: Unclassified, Restricted (disadvantageous to the interests of the nation), Confidential (injury to the national interest), Secret (serious injury to the national interest), Top Secret (exceptionally grave injury to the national interest). "Other" could include, for example: Clearance, Compartmented information, Critical nuclear weapon design information (CNDWI), No foreign dissemination (NOFORN), Official/For official use only, Official sensitive, Originator controlled dissemination (ORCON), Special intelligence, Sensitive but unclassified. https://www.canada.ca/en/public-services-procurement/services/industrial-security/security-requirements-contracting/safeguarding-equipment-sites-assets-information/levels-security.html#s2 REQUIREMENT:
| Term from Controlled Vocabulary | 1 | unclassified | What is the security classification of the maDMP? |
security_classification_level_other_level | To indicate which nomenclature is used to qualify classified information REQUIREMENT:
| String | 0..1 | What other nomenclature is used to describe classified information? | |
security_classification_level_other_nomenclature | To indicate the level of the classified information held by the dmp according to the nomenclature found in dmp_security_classification_level_other_nomenclature REQUIREMENT:
| String | 0..1 | Indicate the level of classified information of the dmp according to the nomenclature | |
title | Title of the DMP REQUIREMENT:
| String | 1 | The most exciting project ever. | What is the title of this maDMP? |
Properties in 'dmp_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Identifier for a DMP (e.g., DOI url) REQUIREMENT:
| String | 1 | https://doi.org/10.1371/journal.pcbi.1006750 | What is the maDMP identifier? |
registry_URI | Link to the registry or system used to identify the linked dmp REQUIREMENT:
| URI | 0..1 | Where can the registry or system be found? | |
registry_name | To indicate what registry or system is used to identify the dmp when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | What registry or sytem was used to identify the dmp? | |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | What version of the registry or system or what date was the registry or system consulted? | |
type | Identifier type (e.g., DOI) REQUIREMENT:
| Term from Controlled Vocabulary | 1 | doi | What is the maDMP identifier type? |
Properties in 'documentation'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | Access url of the reference related to science safeguarding REQUIREMENT:
| URI | 0..1 | What is the url to access the reference related to science safeguarding? | |
description | Description of the reference related to science safeguarding REQUIREMENT:
| String | 0..1 | Describe the reference related to science safeguarding. | |
download_url | Download url of the reference related to science safeguarding REQUIREMENT:
| URI | 0..1 | What is the url to download the reference related to science safeguarding? | |
name | Name of the reference related to science safeguarding REQUIREMENT:
| String | 1 | What is the name of the reference related to science safeguarging? |
Properties in 'educational_institution'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
department | Name of department within an educational institution. REQUIREMENT:
| String | 0..1 | What is the contributor's educational institution department? | |
educational_institution_id | Educational institution identifier
For Canadian institution use ‘List of designated educational institutions’ https://www.canada.ca/en/employment-social-development/programs/designated-schools.html
REQUIREMENT:
| Nested Data Structure | 1 | ||
name | Name of educational_institution.
For Canadian institutions use ‘List of designated educational institutions’ https://www.canada.ca/en/employment-social-development/programs/designated-schools.html REQUIREMENT:
| String | 1 | What is the contributor's educational institution name? |
Properties in 'educational_institution_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Educational institute identifier REQUIREMENT:
| String | 0..1 | What is the contributor's educational institution identifier? | |
registry_URI | Link to the reference used to identify the educational institution REQUIREMENT:
| URI | 0..1 | Where can the reference be found | |
registry_name | To indicate what reference is used to identify the educational institution when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | Liste des universités du réseau européen | What is the name or title of the reference used to identify the educational institution? |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | what version of the reference was used at the time where the identifier was entered | |
type | Educational institute identifier type REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | What is the contributor's educational institution identifier type? |
Properties in 'funder_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Funder ID, recommended to use CrossRef Funder Registry. See: https://www.crossref.org/services/funder-registry/ REQUIREMENT:
| String | 1 | Provide the funder identifier ID. | |
registry_URI | Link to the registry or system used to identify the funder REQUIREMENT:
| URI | 0..1 | Where can the registry or the system be found? | |
registry_name | To indicate what registry or system is used to identify the funder when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | What registry or system was used to identify the funder? | |
registry_version | To indicate the version number or date when the registry or reference was consulted REQUIREMENT:
| String | 0..1 | What version of the registry/system was used or what date was the registry/system consulted? | |
type | Identifier type REQUIREMENT:
| Term from Controlled Vocabulary | 1 | fundref | What type of identifier ID does the funder use (fundref, url, other)? |
Properties in 'funding'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
funder_id | Funder ID of the associated project REQUIREMENT:
| Nested Data Structure | 1 | ||
funding_status | To express different phases of project lifecycle. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | planned | What is the funding status? |
grant_id | Grant ID of the associated project REQUIREMENT:
| Nested Data Structure | 0..1 | ||
source | Project funding source REQUIREMENT:
| Nested Data Structure | 1..n |
Properties in 'geographic_bounding_box'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
east | The easternmost point of the area covered by the dataset, expressed in degrees of latitude REQUIREMENT:
| String | 1 | Where is the easternmost point of the area covered by the dataset, expressed in degrees of latitude? | |
north | The northernmost point of the area covered by the dataset, expressed in degrees of latitude REQUIREMENT:
| String | 1 | Where is the northernmost point of the area covered by the dataset, expressed in degrees of latitude? | |
south | The southernmost point of the area covered by the dataset, expressed in degrees of latitude REQUIREMENT:
| String | 1 | Where is the southernmost point of the area covered by the dataset, expressed in degrees of latitude? | |
west | The westernmost point of the area covered by the dataset, expressed in degrees of latitude REQUIREMENT:
| String | 1 | Where is the westernmost point of the area covered by the dataset, expressed in degrees of latitude? |
Properties in 'government_department_or_agency'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
code | Code of the governmental organization. For the government of Canada, use the OrgID provided by the Inventory of Federal Organizations and Interests found at https://open.canada.ca/data/en/dataset/a35cf382-690c-4221-a971-cf0fd189a46f/resource/7c131a87-7784-4208-8e5c-043451240d95 REQUIREMENT:
| String | 0..1 | 7 | What is the contributor's government department code? |
name | Name of the governmental organization. For the government of Canada, use the Legal title provided by the Inventory of Federal Organizations and Interests found at https://open.canada.ca/data/en/dataset/a35cf382-690c-4221-a971-cf0fd189a46f/resource/7c131a87-7784-4208-8e5c-043451240d95 REQUIREMENT:
| String | 1 | Environment (Department of the) | What is the contributor's government department name? |
organizational_group | Organizational group of the government department affiliated with the contributor REQUIREMENT:
| String | 0..1 | What is the contributor's government affiliation ? | |
organizational_subgroup | Organizational subgroup of the government department affiliated with the contributor REQUIREMENT:
| String | 0..1 | What organizational subgroup does the contributor belong to? |
Properties in 'grant_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Grant ID REQUIREMENT:
| String | 1 | 12345-987654 | Provide the grant ID. |
registry_URI | Link to the reference used to identify the grant REQUIREMENT:
| URI | 0..1 | Where can the the registry or system be found? | |
registry_name | To indicate what reference is used to identify the grant when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | Registre des entreprises de la chambre de commerce | What is registry or system was used to identify the grant? |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | what version of the registry/system was used what date was the registry/system consulted? | |
type | Identifier type REQUIREMENT:
| Term from Controlled Vocabulary | 1 | url | What is the funder identifier ID type (url, other)? |
Properties in 'hardware_requirements'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
data_processing_minimum_RAM_Gb | Minimum RAM needed to process the data in GB REQUIREMENT:
| Number | 0..1 | 16 | What is the minimum RAM, in GB, required to process this dataset? |
description | Describe the hardware requirement REQUIREMENT:
| String | 1 | Describe the process requiring specific hardware | |
machine_type | Minimum computing type needed to process the data (e.g., desktop workstation, laptop, server, HPC, super computer) REQUIREMENT:
| String | 0..1 | HPC | What is the minimum machine type required process the dataset? (I'm not a fan of this at all, doesn't make sense) |
minimum_cpu_cores | Minimum CPU cores needed to process the data REQUIREMENT:
| Number | 0..1 | 8 | What is the minimum number of cpu cores required to process the data? |
minimum_cpu_speed | Minimum clock speed needed to process the data in GHz REQUIREMENT:
| Number | 0..1 | 2.5 GHz | What is the minimum speed, in GHz, required to process the dataset? |
network_requirements | Minimum bandwidth or network speed required in Mbps REQUIREMENT:
| Number | 0..1 | 100 | What is the minimum bandwidth or netowrk speed required (Mbps)? |
processing_unit_requirements | Need for specialized hardware like GPUs/TPUs for computation REQUIREMENT:
| String | 0..1 | NVIDIA Tesla V100 | What processing units are required? |
storage_capacity | Minimum storage space required REQUIREMENT:
| Number | 0..1 | 1 | What is the minimum storage capacity required to process this dataset? |
storage_capacity_unit | Unit in which the storage capacity requirement is expressed REQUIREMENT:
| Term from Controlled Vocabulary | 1 | TB | What unit is the minimum storage expressed in? |
title | Identify the purpose requiring specific hardware REQUIREMENT:
| String | 1 | Mapping historical data | What process requires specific hardware? |
Properties in 'host'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
availability | Defines whether the data host is operational 24/7 or has downtime periods REQUIREMENT:
| String | 0..1 | scheduled downtimes | What is the availability of the distribution? |
backup_frequency | Backup Frequency REQUIREMENT:
| String | 0..1 | weekly | How often is the distribution backed up to the host? |
backup_type | Type of backup of the host (e.g., incremental, full, differential, synthetic full) REQUIREMENT:
| String | 0..1 | What type of backup system is used for the host? | |
certified_with | Repository certified to a recognised standard (e.g., ISO 27001, CoreTrustSeal, etc.) REQUIREMENT:
| String | 0..1 | coretrustseal | What is the host server certified with? |
content_type | Content type of the online service (e.g., Web Service, Dataset, API, Application, Supporting Document) REQUIREMENT:
| String | 0..1 | Web Service | What is the content type of the online service? |
data_priority | Indicate if the data are active data, longterm storage, or transitory. For batch priority-based scheduling, declare relative priorities to determine the processing order of jobs and business processes: Low, Normal (default value), High, Critical, and Reserved capacity (highest priority). REQUIREMENT:
| String | 0..1 | Longterm storage; batch processing priority low | What is the priority of the data in the dataset? |
data_transfer_maximum_latency | Maximum data transfer latency of the distribution en ms, i.e. the delay of data transfer REQUIREMENT:
| Number | 0..1 | 50 | What is the data transfer maximum latency of the distribution? |
data_transfer_minimum_throughput | Maximum throughput of the distribution in Mbps REQUIREMENT:
| Number | 0..1 | 10 | What is the maximum throughput of the distribution? |
description | To describe the host of the distribution REQUIREMENT:
| String | 0..1 | Repository hosted by... | Describe the host. |
format | Format of the online service REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | WMS | What is the format of the online service? |
geo_location | Physical location of the data expressed using ISO 3166-1 country code. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | CA | Where is the location of the host server? |
language | Display language of the online service REQUIREMENT:
| String | 1..n | eng | What is the display language of the online service? |
pid_system | Persistent identifier system used by the host REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | ark | What pid system is used for the host server? |
protocol | The protocol used to interact with the host REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | What is the protocol to interact with the host? | |
storage_type | The type of storage REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | cloud | What storage type does the host server use? |
support_checksum | To indicate if checksums can be performed to ensure integrity of the distribution REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Is there a support checksum for the host? |
support_versioning | To indicate if changes made in a version is supported from the host REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Is there support versioning from the host? |
title | The name of the system hosting the dataset for external access REQUIREMENT:
| String | 1 | Super Repository | What is the title for the host of the distribution? |
type | The type of system hosting the distribution REQUIREMENT:
| Term from Controlled Vocabulary | 1 | data portal | What type is the host? |
url | The URL of the system hosting a distribution of a dataset REQUIREMENT:
| URI | 1 | https://zenodo.org | What is the url to the host of the distribution? |
version | Version number of the host system, if applicable. This field is relevant for software-based hosts such as repositories (e.g., Zenodo 4.0, Dataverse 5.13) or storage systems (e.g., MinIO RELEASE.2024-03-11T17-12-34Z). For hardware-based hosts like generic file servers, this field may be left blank. REQUIREMENT:
| String | 0..1 | What version of the host is used ? |
Properties in 'indigenous_considerations'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
characters | To indicate if Indigenous characters are used in the data. If the answer is "yes," then 'Unified Canadian Aboriginal Syllabics Extended' is identified under distribution/character_unicode_block REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Are Indigenous characters used in the data? |
community_approval | to describe approvals by indigenous communities REQUIREMENT:
| Nested Data Structure | 0..n | ||
description | General description of Indigenous considerations. REQUIREMENT:
| String | 0..1 | Community-based indicators of Indigenous health ... | Describe the Indigenous considerations related to this project. |
dmp_discussion | To indicate whether the DMP has been discussed with an Indigenous group REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | unknown | Has the maDMP been discussed with the Indigenous community? |
exist | To indicate if Indigenous consideration exist. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Are there Indigenous considerations related to this project? |
government_name | Indigenous government group affiliated with the contributor REQUIREMENT:
| String | 0..1 | What Indigenous government group does the contributor belong to? | |
group_identification | To indicate which Indigenous group(s) this dataset is related to. For example, in Canada (Indian Band, Inuit, Metis), in Europe (Sami), in New Zealand (Maori), or self-identification. REQUIREMENT:
| String | 0..n | First Nations | Which Indigenous group is this dataset related to? |
indian_band_name | First Nations Indian Band name corresponding to the First Nations code associated with the dataset. https://fnp-ppn.aadnc-aandc.gc.ca/fnp/Main/Search/SearchFN.aspx?lang=eng ;
https://open.canada.ca/data/en/dataset/b6567c5c-8339-4055-99fa-63f92114d9e4 REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | Campbell River | What First Nations Indian Band name is associated with these data? |
indian_band_number | First Nations Indian band number associated with the dataset. https://fnp-ppn.aadnc-aandc.gc.ca/fnp/Main/Search/SearchFN.aspx?lang=eng ;
https://open.canada.ca/data/en/dataset/b6567c5c-8339-4055-99fa-63f92114d9e4 REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | 622 | What First Nations Indian Band number is associated with these data? |
indigenous_control_over_data | To indicate if Indigenous communities control the data. Description of salient elements of data governance should be noted at the dataset level in the property “description”. Indigenous data sharing agreement would be identifed under partner organization agreement type. Indigenous traditional knowledge keeper would be identified under Contributor role. See, also: UNDRIP; Canada Tri-Agency requirements. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | no | Is there Indigenous control over data? |
language | To indicate if Indigenous language is used. If the answer is "yes," then it is identified under maDMP language and/or Dataset language and/or Distribution language. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Is an Indigenous language used in the maDMP, dataset, or distribution? |
research_method | To record research methods that have particular significance to an Indigenous community, or that are considered by the researchers to be Indigenous research methods. Examples might include dadirri (australia), pathway (australia), sharing circle, sikolohiyang pilipino, storytelling, talanoa (samoa), talking circle, two-eyed seeing, whakawhiti kōrero (māori), yarning. REQUIREMENT:
| String | 0..n | sharing circle | What was the research method used, that was specific to the indigenous context? |
traditional_knowledge | To indicate if traditional Indigenous knowledge is used in the dataset REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Is Indigenous traditional knowledge used in this project? |
traditional_knowledge_description | To describe the traditional knowledge used in this dataset REQUIREMENT:
| String | 0..1 | What Indigenous traditional knowledge applies to these data? |
Properties in 'intellectual_property'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
copyright_description | Description of the copyright associated with dataset REQUIREMENT:
| String | 0..1 | Non-transferable copyright | Describe the copyright associated with the dataset? |
copyright_extent | Limitations of the copyright associated with the dataset (e.g., all of the dataset; part of the dataset; etc.) REQUIREMENT:
| Term from Controlled Vocabulary | 1 | Part of the dataset | Does the copyright apply to the entire dataset? |
copyright_holder | Main copyright holder REQUIREMENT:
| Term from Controlled Vocabulary | 1..n | crown copyright - Canada | Who owns the copyright associated with the dataset? |
other | To allow for the recording of other rights than copyright. REQUIREMENT:
| String | 0..1 | What intellectual property rights, other than copyright, are associated with this dataset? |
Properties in 'license'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
license_ref | Link to license document. Examples: https://open.canada.ca/en/open-government-license-canada ; https://choosealicense.com/licenses/mit/ ; https://creativecommons.org/licenses/by-sa/4.0/legalcode ; https://opensource.org/licenses REQUIREMENT:
| URI | 1 | https://open.canada.ca/en/open-government-license-canada | Provide a link to the license. |
start_date | If date is set in the future, it indicates an embargo period. Embargo for data sharing means that data will be made available using a license, but not immediately after deposition of data in a repository. For each distribution, one can assign a license. If the license is assigned, then it means that a distribution at some point will become available. The start date set for the license indicates when it becomes binding - in other words, when the distribution becomes available under this license.Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 1 | 2023-07-20 | What is the start date of the license? |
Properties in 'linked_dmp'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | URL where the linked dmp can be accessed REQUIREMENT:
| URI | 0..1 | Where can the linked dmp be accessed | |
download_url | URL where the linked dmp can be downloaded REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | Where can the linked dmp be downloaded |
linked_dmp_id | identifier of the related dmp REQUIREMENT:
| Nested Data Structure | 1..n | ||
relationship | Explain the relationship of the linked dmp with respect to this dmp. Specify which version is authoritative, if applicable. Example: the linked dmp is the working French version of this authoritative dmp REQUIREMENT:
| String | 1 | The linked dmp is the French version of this dmp | What is the relationship between the linked dmp and this dmp? |
Properties in 'linked_dmp_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | identifier of the related dmp REQUIREMENT:
| String | 1 | https://doi.org/10.1371/journal.pcbi.1006750 | What is the maDMP identifier? |
registry_URI | Link to the reference used to identify the linked dmp REQUIREMENT:
| URI | 0..1 | Where can the registry or system be found? | |
registry_name | To indicate what reference is used to identify the linked dmp when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | What registry or sytem was used to identify the linked_dmp? | |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | What version of the registry or system or what date was the registry or system consulted? | |
type | type of identifier REQUIREMENT:
| Term from Controlled Vocabulary | 1 | doi | What is the maDMP identifier type? |
Properties in 'metadata'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | Description REQUIREMENT:
| String | 0..1 | Provides taxonomy for... | Describe the dataset metadata. |
language | Language of the metadata expressed using ISO 639-3 (three letter language code) REQUIREMENT:
| Term from Controlled Vocabulary | 1 | eng | What language is used for the dataset metadata? |
metadata_standard_id | Metadata Standard ID REQUIREMENT:
| Nested Data Structure | 1 |
Properties in 'metadata_standard_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Identifier for the metadata standard used. Example: http://www.dublincore.org/specifications/dublin-core/dcmi-terms/ REQUIREMENT:
| String | 1 | http://www.dublincore.org/specifications/dublin-core/dcmi-terms/ | What metadata standard is used? |
registry_URI | Link to the reference used to identify the metadata standard REQUIREMENT:
| URI | 0..1 | https://rdamsc.bath.ac.uk/ | Where can the registry or the system be found? |
registry_name | To indicate what reference is used to identify the metadata standard when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | RDA Metadata Standards Catalog | What is registry or system was used to identify the metadata standard? |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | 2024/10/10 | what version of the reference was used at the time where the identifier was entered |
type | Identifier type REQUIREMENT:
| Term from Controlled Vocabulary | 1 | url | What is the metadata standard identifier type? |
Properties in 'non_profit'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
name | Name of the non-profit organization affiliated with the contributor REQUIREMENT:
| String | 1 | What is the non-profit's name? | |
non_profit_id | Identifier for the non-profit organization itself REQUIREMENT:
| Nested Data Structure | 0..1 |
Properties in 'non_profit_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | what version of the reference was used at the time where the identifier was entered | |
reference_URI | Non-profit organization identifier REQUIREMENT:
| String | 0..1 | What is the non-profit's identifier? | |
reference_version | Link to the reference used to identify the business REQUIREMENT:
| URI | 0..1 | Where can the reference be found | |
type | Non-profit organization identifier type (name of registry) REQUIREMENT:
| String | 0..1 | What type of identifier does the non-profit use? |
Properties in 'online_service'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
content_type | Content type of the online service REQUIREMENT:
| String | 0..1 | Web Service | What is the content type of the online service? |
format | Format of the online service REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | WMS | What is the format of the online service? |
language | Display language of the online service REQUIREMENT:
| String | 1..n | eng | What is the display language of the online service? |
name | Name of the online service REQUIREMENT:
| String | 1 | Emerald Ash Borer Regulated Areas | What is the name of the online service? |
protocol | Protocol of the online service REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | OGC | What is the protocol type of online service? |
service_language | Language used for the online service REQUIREMENT:
| String | 0..1 | What is the language used in the online service? | |
service_url | A url that leads to the online service page REQUIREMENT:
| URI | 1 | What is the url that links to online service page? |
Properties in 'partner_organization'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
agreement | Partner organization agreement REQUIREMENT:
| Nested Data Structure | 0..1 | ||
name | Name of partner organization. REQUIREMENT:
| String | 0..1 | Stargazers | What is the partner organization's name? |
partner_organization_id | Unique identifier assigned to represent partner organization. REQUIREMENT:
| Nested Data Structure | 0..1 |
Properties in 'partner_organization_id'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
identifier | Partner organization identifier REQUIREMENT:
| String | 0..1 | What is the partner organization's ID? | |
registry_URI | Link to the reference used to identify the partner organization REQUIREMENT:
| URI | 0..1 | Where can the registry or system be found? | |
registry_name | To indicate what reference is used to identify the partner organization when selecting "other" as id type. REQUIREMENT:
| String | 0..1 | What registry or system was used to identify the partner organization? | |
registry_version | To indicate the version number or date of the reference REQUIREMENT:
| String | 0..1 | What version of the registry/system was used or what date was the registry/system consulted? | |
type | Partner organization identifier type REQUIREMENT:
| String | 0..1 | What type of ID does the partner organization use? |
Properties in 'physical_data_asset'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
building_city | City name where the physical asset(s) are located REQUIREMENT:
| String | 0..1 | What city is the physical data asset in? | |
building_name | Building name where the physical asset(s) are located REQUIREMENT:
| String | 0..1 | What is the name of the building where the physical data asset is located? | |
building_room_number | Room number where the physical asset(s) are located REQUIREMENT:
| String | 0..1 | What room number is the physical data asset stored in? | |
description | Description of the physical data asset's appearance, functionality, contents, notable features, etc. REQUIREMENT:
| String | 1 | Describe the physical data asset. | |
name | Full device name in System where the physical asset(s) are located REQUIREMENT:
| String | 0..1 | What is the computer name that houses the physical data asset? | |
type | Physical object type the data is stored on (e.g., blue-ray, clay tablet, compact disk, dvd, hard drive, solid state drive, paper, parchment, stone, quipu, tape, thumb drive) REQUIREMENT:
| String | 1 | clay tablet | What type of physical object is the data stored on? |
Properties in 'privacy_impact_assessment'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
approved | To indicate if the privacy impact assessment was approved. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Was the privacy impact assessment approved? |
approved_by | Name of the person who approved the privacy impact assessment. REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Who approved the privacy impact assessment? |
download_url | A URL that gives access to the privacy impact assessment. The access URL should be used for the URL of a service or location that can provide access to privacy impact assessment, typically through a Web form, query or API call. REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | Provide the URL to download the privacy impact assessment. |
registered | To indicate if the privacy impact assessment was registered (e.g., yes, no, ID#, etc.). https://www.tbs-sct.gc.ca/pol/doc-eng.aspx?id=18308 REQUIREMENT:
| String | 0..1 | ID xxxx-45576 | If a privacy impact assessment (PIA) was performed was it registered or does it have an ID number? |
required | To indicate if a privacy impact assessment is required. REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Is a privacy impact assessment required? |
Properties in 'project'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
algorithmic_impact_assessment_conducted | To indicate if an algorithmic impact assessment has been conducted related to these data. For example using this tool REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Has an algorithmic impact assessment been conducted related to these data? |
algorithmic_impact_assessment_conducted_uri | Link to the algorithmic impact assessment REQUIREMENT:
| URI | 0..1 | Provide a link to the algorithmic impact assessment, if applicable. | |
description | Project description REQUIREMENT:
| String | 0..1 | Important data for secret mission to the sun | Describe the project. |
end | Project end date. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2025-12-31 | When is the planned end date of the project, or when did the project end? |
funding | Funding related with a project REQUIREMENT:
| Nested Data Structure | 0..n | ||
partner_organization | Partner organization REQUIREMENT:
| Nested Data Structure | 0..n | ||
safeguarding_science_measures | Science is defined broadly to include the natural, health, and social sciences, mathematics, engineering, and technology. Safeguarding science includes safeguarding research partnerships, opensource due diligence, and risk mitigation. Some elements of safeguarding science are recorded elsewhere in the maDMP (e.g., checksum, data access, data security-privacy measures, ethical issues, intellectual property, partner agreement, protection level, retention/disposition planning, security classification, succession plan, versioning). This section should be used for additional information (e.g., description and link to a risk assessment and mitigation plan). For guidance, see: https://www.oecd.org/content/dam/oecd/en/publications/reports/2022/06/integrity-and-security-in-the-global-research-ecosystem_2bd8511d/1c416f43-en.pdf ; https://science.gc.ca/site/science/en/safeguarding-your-research/guidelines-and-tools-implement-research-security/guidance-conducting-open-source-due-diligence/conducting-open-source-due-diligence-safeguarding-research-partnerships ; https://science.gc.ca/site/science/en/safeguarding-your-research/guidelines-and-tools-implement-research-security/mitigating-your-research-security-risks ; https://science.gc.ca/site/science/en/safeguarding-your-research/guidelines-and-tools-implement-research-security/national-security-guidelines-research-partnerships/national-security-guidelines-research-partnerships-risk-assessment-form REQUIREMENT:
| Nested Data Structure | 1 | ||
start | Project start date. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..1 | 2023-07-20 | What is the project start date? |
succession_plan | Succession plan, or business continuity plan REQUIREMENT:
| String | 1 | No plan, project falls apart when P.I. leaves. | What is the project succession plan or business continuity plan? |
title | Project title REQUIREMENT:
| String | 1 | Mission to the sun. | What is the project title? |
Properties in 'province_state'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
code | The 3-letter code of the province or state, as per the ISO standard 3166-2 Codes for the representation of names of countries and their subdivisions – Part 2: Country subdivision code REQUIREMENT:
| Term from Controlled Vocabulary | 1 | QC | What province or state is the contributor working in? |
name | The name of the province or state, as per the ISO standard ISO 3166-2 Codes for the representation of names of countries and their subdivisions – Part 2: Country subdivision code REQUIREMENT:
| Term from Controlled Vocabulary | 1 | Quebec | What province or state does the contributor work in? |
Properties in 'province_state'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
code | The 3-letter code of the province or state, as per the ISO standard 3166-2 Codes for the representation of names of countries and their subdivisions – Part 2: Country subdivision code REQUIREMENT:
| Term from Controlled Vocabulary | 1 | QC | What province or state is the contributor working in? |
name | The name of the province or state, as per the ISO standard ISO 3166-2 Codes for the representation of names of countries and their subdivisions – Part 2: Country subdivision code REQUIREMENT:
| Term from Controlled Vocabulary | 1 | Quebec | What province or state does the contributor work in? |
Properties in 'redundant_backups'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | To describe the backup: scope, date backup was saved in a repository, version (or date) of the data at the time of the backup, etc. REQUIREMENT:
| String | 0..1 | This backup includes the table XXX of the 2023 survey | Describe scope |
download_url | To indicate the url where the backup can be retrieved REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | Where can the backup be downloaded from? |
Properties in 'retention_specification'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | Indicates how long a dataset should be retained, and why. In instances of determinate retention, a retention specification includes three elements: a retention period; a retention period initiator (trigger); a rationale that explains or justifies the retention period and trigger. REQUIREMENT:
| String | 1 | See the Directive on the Management of Microdata for all retention specifications. | What are the retention specifications for the dataset? |
required_destruction | To indicate that a dataset must be destroyed.
Note: context can be recorded in “retention_specifications/description.” REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes all | Does this dataset need to be destroyed (e.g., according to consent forms), in whole or in part? |
required_destruction_description | To record the date on which destruction was promised. Encoded using the relevant ISO 8601 Date compliant string. REQUIREMENT:
| Date | 0..1 | 2042-01-01 | On what date(s) was data destruction promised to occur? (e.g., according to consent forms) |
required_perpetual_use | Examples where this may be required include the need to maintain scientific integrity, treaties, agreements, or compliance with UN Joinet-Orentlicher principles for the protection and promotion of human rights through action to combat impunity.
Note: context can be recorded in “retention_specifications/description.” REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes all | Do you need to keep this dataset indefinitely, for active use? |
retention_period_duration | To record duration of retention period after trigger event. (At the end of its retention period, the dataset should be reviewed for disposition, and disposition effected if possible.) Encoded using the relevant ISO 8601 Duration compliant string. REQUIREMENT:
| String | 0..1 | P7Y2M0DT0H0M0S | How long is the retention period? |
retention_period_end_date | To record a fixed date marking the end of a retention period. Note the end of its retention period, the dataset should be reviewed for disposition, and disposition effected if possible. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 0..n | 48091 | On what date does the retention period end? |
retention_rationale | The reason (justification) for retaining a dataset for a particular period of time. REQUIREMENT:
| String | 0..n | Irreplicable observational data; 1962 ionosphere can no longer be replicated (space junk). | Why is the dataset to be retained for the length of time indicated? |
trigger_description | A trigger (retention period initiator) is an event in time that begins a retention period. REQUIREMENT:
| String | 0..n | Data collection end date | What is the event that triggers a retention period? |
trigger_occured | The date on which the trigger was triggered, and the retention period began. Encoded using the relevant ISO 8601 Date compliant string. REQUIREMENT:
| Date | 0..1 | 2024-11-20 | When did the retention period start? |
trigger_type | To indicate the type of trigger REQUIREMENT:
| Term from Controlled Vocabulary | 0..n | date (fixed) | What type of event triggers the retention period start? |
Properties in 'safeguarding_science_measures'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
documentation | Create one entry for each reference related to the project science safeguarding . REQUIREMENT:
| Nested Data Structure | 0..n | ||
exist | To indicate if any measure has have been taken to safeguard the project REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Has any measure been taken related to science safeguarding? |
redundant_backups | To describe how data used in the project have been saved to guarantee their security, integrity and long term access REQUIREMENT:
| Nested Data Structure | 0..n | ||
redundant_backups_exist | To indicate if any redundant backup of the source data exists REQUIREMENT:
| Term from Controlled Vocabulary | 1 | Does any back up of the source data exist? |
Properties in 'security_and_privacy'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | Description of security or privacy controls REQUIREMENT:
| String | 0..1 | Server with data must be kept in a locked room because ... ; Data cannot be shared even in de-identified or anonymised form. | Describe security and privacy controls considerations, or special measures. |
privacy_impact_assessment | Privacy impact assessment related to the dataset. Government of Canada institutions should refer to https://www.tbs-sct.canada.ca/pol/doc-eng.aspx?id=18309 REQUIREMENT:
| Nested Data Structure | 1 | ||
title | Provide a title for each requirement or issue listed in the security and privacy section. Titles need to be specific enough to differentiate issues or requirements between them. REQUIREMENT:
| String | 1 | Physical access control; Special privacy requirement | Provide a title for this specific security or privacy control or measure |
Properties in 'software'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
code_repository | Link to a version control repository if applicable REQUIREMENT:
| URI | 0..1 | https://github.com/FAIRERdata/maDMP-Standard | What version control repository the code is available at (url)? |
dependencies | Any additional libraries required for execution (e.g., NumPy, TensorFlow, Pandas, etc.) REQUIREMENT:
| String | 0..n | pandas | What libraries or modules is the code dependent on? |
description | To provide any free-form text information on the computer code used REQUIREMENT:
| String | 0..1 | Tool for spatial data analysis | Describe the computer code being used. |
download_url | the URL to download the computer code or the software REQUIREMENT:
| URI | 0..1 | What is the URL to download the computer code? | |
execution_environment | Specify where the software runs (e.g., Local Machine, Cloud, Docker, Kubernetes, etc.) REQUIREMENT:
| String | 0..1 | laptop | Where does the software or code run? |
license | The licensing terms under which the software/code is released. Use of a license is highly recommended (e.g., CC BY-SA 4.0, MIT, open government license, etc.) REQUIREMENT:
| String | 0..1 | CC BY-SA 4.0 | What license applies to this work? |
name | Name of the software or code REQUIREMENT:
| String | 0..1 | MATLAB | What is the name of the software or code in use? |
operating_system_description | If OS dependent, to provide any free-form text information on the operating system used REQUIREMENT:
| String | 0..1 | Describe the operating system in use? | |
operating_system_name | If OS dependent, operating system used REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | linux | What operating system is in use? |
programming_language | Computer programming language used (e.g., Python, R, SAS) REQUIREMENT:
| String | 0..1 | Python | What language is the computer code in? |
proprietary_software | To indicate if proprietary software was used REQUIREMENT:
| Term from Controlled Vocabulary | 1 | yes | Is there proprietary software in use? |
proprietary_software_justification | To indicate if proprietary software justification was provided REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | is the propietry software justified in use? |
proprietary_software_migration_plan | To indicate if there is a migration plan for the proprietary software REQUIREMENT:
| Term from Controlled Vocabulary | 0..1 | yes | Is there a migration plan for the proprietary software? |
proprietary_software_migration_plan_description | To provide any free-form text information on the migration plan for the proprietary software REQUIREMENT:
| String | 0..1 | Describe the migration plan for the propietary software. | |
software_management_plan | To reference an external software management plan REQUIREMENT:
| Nested Data Structure | 0..n |
Properties in 'software_management_plan'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
access_url | A URL of that gives access to the Software Management Plan (SMP), e.g., landing page, feed, SPARQL endpoint. The access URL should be used for the URL of a service or location that can provide access to the SMP, typically through a Web form, query or API call. REQUIREMENT:
| URI | 0..1 | some.intranet/.../project page.aspx | What is the access url to the SMP |
download_url | Title of the external document documenting the cost REQUIREMENT:
| URI | 0..1 | http://some.repo.../download/... | What is the dowload url of the SMP |
name | REQUIREMENT:
| String | 1 | What is the name or title of the SMP |
Properties in 'source'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | To provide any free-form text information on the funding source for the project REQUIREMENT:
| String | 0..1 | Provide details on project funding. | |
type | Funding source type for the project (e.g., OCIO A-base, OCIO B-base, program A-base, program B-base, Treasury Board submission, vote-net revenue (VNR), no funding) REQUIREMENT:
| String | 1..n | program A-base | How is the project funded? |
Properties in 'technical_resource'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
description | Description of the technical resource (e.g., aircraft, cell phones, database, datalogger, field analyzer, laboratory instrument, modeling-simulation output, satellite, text document, survey, wildlife tracking device) REQUIREMENT:
| String | 0..1 | Describe the required technical resource. | |
name | Name of the technical resource REQUIREMENT:
| String | 1 | 123/45/43/AT | Name the required technical resource. |
Properties in 'version_history'
Name | Description | Data Type | Cardinality | Example Value | User-friendly Question |
---|---|---|---|---|---|
revision_date | To indicate the date a revision of the data in the distribution was made. Encoded using the relevant ISO 8601 Date compliant string REQUIREMENT:
| Date | 1 | When was the last revision made? | |
revision_description | Description about what changes this revision made REQUIREMENT:
| String | 0..1 | Describe what the revision is and its purpose. | |
revision_documentation | Link to the revision documentation REQUIREMENT:
| URI | 0..1 | Provide the url link to the revision |