| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | ||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | Element Display Name - English | Element Display Name - French | Element Name | Submission Form Section | Generation Method | Required or Optional | Repeatable or Non-Repeatable | Public or Internal | Default Language | Tooltip for Users | Curator Guide - Submission Interface See also: Curation - metadata considerations | Example - Submission Interface | Curator Guide - Admin Interface | Example - Admin Interface | Controlled Vocabulary | Metadata Review Procedures | Last Review Date | All Review Dates | |
2 | Title | Titre | dc.title | Required Metadata | Manual | Required | Non-Repeatable | Public | en_US | The full title by which the dataset is known. | Capitalize the first word of the title. Do not use ending punctuation. | Unmanned aerial vehicle structure from motion and lidar data for sub-canopy snow depth mapping Atmospheric Chemistry Experiment SciSat Level 2 Processed Data, v4.0 | [Same as submission interface.] | [Same as submission interface.] | Verify this field is populated. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
3 | Description | Description | dc.description | Required Metadata | Manual | Required | Non-Repeatable | Public | en_US | A summary describing the purpose, nature, and scope of the dataset. | Free text. | This mice brain data is used in the training and testing of a fully automated software pipeline for the characterization of Immunopositive Microglia in Whole Slide Imaging for Traumatic Brain Injury. The pipeline consists of two major components: White Matter Segmentation and Microglial Analysis in Count and Morphology, both of which use supervised machine learning algorithms that were trained using the respective folders. The pipeline was also tested as a whole for its performance using the brain sections included. This data was acquired by Dr. Wellington's group at the Centre for Brain Health, University of British Columbia. | [Same as submission interface.] | [Same as submission interface.] | Verify this field is populated. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
4 | Keywords | Mots-clés | dc.subject | Required Metadata | Manual | Required | Repeatable | Public | en_US | Subject, keyword, classification code, or key phrase describing the dataset. | Capitalize the first word of each term (where possible). Separate terms with either a semicolon or the enter key. | Natural graphite sheet; Uniaxial compression | Each subject term is entered in its own dc.subject field. Due to the submission interface delimiter, do not include semicolons within subjects. | Natural graphite Uniaxial compression | Verify this field is populated (at least one keyword). New 2021-11: Move place names to datacite.geolocation.geolocationPlace. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
5 | Field of Research | Domaine de recherche | frdr.crdc.code | Required Metadata | Manual | Required | Repeatable | Public | en_US | Select the field(s) of research by using the Canadian Research and Development Classification field name(s) applicable to this dataset. You may select as many fields as appropriate. | Select Group, then Class, then Field from the dropdown menus. The correct code will be populated based on the field choice. | (Group) Education (Class) Education systems (Field) Open education | Select the group, class, and field from the dropdown menu; same as submission interface. To add a new field, select "frdr.crdc.code". Although these fields are shown on the landing page/full record display, only frdr.crdc.code is stored in the metadata: - frdr.crdc.group_en - frdr.crdc.class_en - frdr.crdc.field_en - frdr.crdc.group_fr - frdr.crdc.class_fr - frdr.crdc.field_fr | [Same as submission interface.] | https://www.statcan.gc.ca/eng/subjects/standard/crdc/2020v1/index | New 2021-11: - Recent deposits review: Verify that each record has at least one CRDC Code. - Full review only: See FRDR Metadata Review Procedures - CRDC. | 2026-02-06 | 2026-02-06 | |
6 | Author | linked group | Required Metadata | Manual | Required | Repeatable | Public | n/a | n/a | Each instance of the linked group must include all linked fields. Use a single dash ("-") in placeholder fields. | Verify that each record has the same number of entries for name/affiliation/identifier and add missing placeholders; see Identify missing linked fields. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||||||
7 | > Author | > Auteur | dc.contributor.author | Required Metadata | Manual | > Required in linked group | > Non-Repeatable in linked group | Public | none | The author or researcher who produced the dataset. | Enter the author name using the Last Name and First Name fields. Apply a period after any initials. Do not include a space between initials. If the author does not have a first name, this change must be made in the Admin interface. An organization or consortium as an author should be entered in Last Name field. If you need to check for consistency with previous authors, you can use this page: https://www.frdr-dfdr.ca/repo/handle/frdr-dfdr/browse?type=author&submit_browse=Author | Archer, Reese D. | The author name is stored with a comma inserted between Last Name and First Name. | Archer, Reese D. | Search previous authors' names and aim for consistency: https://www.frdr-dfdr.ca/repo/handle/frdr-dfdr/browse?type=author&submit_browse=Author | Review dc.contributor.author for consistency: - Recent deposits review: Look for the inconsistencies listed below. To compare with other authors, search for the author’s name in the FRDR DSpace community. - Full review only: see Personal names in dc.contributor.author and datacite.contributor.*. Common inconsistencies include: - Addition or omission of middle initial - Direct order instead of indirect order - Missing period after middle initial - Extra space between initials When deciding which version of a name to use in FRDR, consider these criteria (which may conflict; use your best judgment): - Which name does the author usually publish under? - If there is an ORCID, what name do they have on their ORCID profile? - Which name is more complete? Prefer the more complete name. - Which name is used for the majority of records in FRDR? Try to minimize the number of changes made. - Which name is used for the more recent submission(s)? Prefer the name used more recently. | 2026-02-06 | 2026-02-06 2021-11-26 2021-06-08 2021-02-11 2020-11-03 | |
8 | > Author Affiliations | > Affiliations des auteurs | datacite.creator.affiliation | Required Metadata | Manual | > Required in linked group | > Non-Repeatable in linked group > Repeatable in field with semicolon delimiter | Public | en_US | The organizational or institutional affiliation(s) of the author. | Prefer the term used by ROR (https://ror.org/). Enter multiple affiliations as required. Values such as Department and addresses should be removed. Labs, research groups, institutions, hospitals etc. without RORs should remain. See FRDR - Affiliations Tracking for current values. | University of Saskatchewan | Multiple affiliations are delimited by semicolons. | University of Saskatchewan; Compute Canada | List of institutions stored in tags, with names based on the Research Organization Registry (ROR). Free text permitted. | Review affiliation for consistency: - Recent deposits review: Compare affiliations with the list in FRDR - Affiliations Tracking. Note inconsistencies for affiliations that should match existing entries. - Full review only: See FRDR Metadata Review Procedures - Affiliations. | 2026-02-06 | 2026-02-06 2022-01-04 2021-08-11 2021-04-21 2021-01-11 | |
9 | > datacite.creator.affiliationIdentifier | datacite.creator.affiliationIdentifier | Required Metadata | Automatic | > Required in linked group | > Non-Repeatable in linked group > Repeatable in field with semicolon delimiter | Public | en_US | n/a | n/a | n/a | ROR IDs may be automatically added based on affiliation selection(s). Like affiliations, ROR IDs are delimited by semicolons. The order of ROR IDs corresponds with the order of that author's affiliations. If an affiliation does not have a corresponding ROR ID, there should be a placehodler "-". | https://ror.org/010x8gc63; - | ROR IDs formatted as URLs and placeholders ("-"). | tbd | 2026-02-06 | 2026-02-06 2022-01-04 | ||
10 | > ORCID iD | > ORCID iD | datacite.creator.nameIdentifier | Required Metadata | Manual | > Optional in linked group | > Non-Repeatable in linked group | Public | en_US | A unique identifier for the author. Find out more about ORCID here: https://support.orcid.org/hc/en-usr. | You may copy and paste the full ORCID with the URI, or enter the 16-digit ORCID iD without the URI. The interface will always autocomplete to add the URI (https://orcid.org/) and insert dashes if needed. Confirm the author's ORCID iD where possible. | 0000-1234-0000-5678 0000123400005678 https://orcid.org/0000123400005678 https://orcid.org/0000-1234-0000-5678 | The ORCID iD is stored with the full URI and dashes. | https://orcid.org/0000-1234-0000-5678 | Confirm that ORCID IDs match the corresponding author. - Recent deposits review: n/a - Full review only: See FRDR Metadata Review Procedures - ORCID IDs. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 | ||
11 | Contact Name | Nom du contact | frdr.contact.name | Required Metadata | Manual | Required | Non-Repeatable | Internal | none | The name of the person to contact with questions about the dataset. | Enter the contact name using the Last Name (required) and First Name (optional) fields. Apply a period after any initials. Although a person's name is preferred, an organizational name is accepted and can be entered in the Last Name field. | Archer, Reese D. | The contact name is stored with a comma inserted between Last Name and First Name. If no First Name is provided, only the Last Name is stored (no comma is inserted). | Archer, Reese D. | Verify this field is populated. Verify that contact name is in Family Name, Given Name format. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
12 | Contact Email | Courriel du contact | frdr.contact.email | Required Metadata | Manual | Required | Non-Repeatable | Internal | en_US | The email address of the person to contact with questions about the dataset. | Enter one email address, formatted plainly (no <>). | reese.archer@example.ca | [Same as submission interface.] | [Same as submission interface.] | Verify this field is populated. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
13 | Rights | Droits | dc.rights | Required Metadata | Manual | Required | Non-Repeatable | Public | en_US | Select a license for the dataset. | Automatically populated by radio button selection. For custom licenses, use the Admin interface. | Creative Commons Public Domain Dedication (CC0 1.0) https://creativecommons.org/publicdomain/zero/1.0/ | The human readable license name. Unless using a custom license, this will be created based on the radio button selection in the submission form. When adding a custom license, include both dc.rights and dc.rights.uri where applicable. | Creative Commons Attribution-NonCommercial 4.0 (CC BY-NC 4.0) | Creative Commons Public Domain Dedication (CC0 1.0) Creative Commons Attribution 4.0 International (CC BY 4.0) Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) Creative Commons Attribution-NonCommercial 4.0 (CC BY-NC 4.0) Creative Commons Attribution-NonCommercial-ShareAlike 4.0 (CC BY-NC-SA 4.0) Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 (CC BY-NC-ND 4.0) | Verify this field is populated. Verify that dc.rights and dc.rights.uri correspond. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | |
14 | dc.rights.uri | dc.rights.uri | Required Metadata | Automatic | Required | Non-Repeatable | Public | none | n/a | Automatically populated by radio button selection. | n/a | The licence URI. Unless using a custom license, this will be created based on the radio button selection in the submission form. When adding a custom license, include both dc.rights and dc.rights.uri where applicable. | https://creativecommons.org/licenses/by-nc/4.0/ | https://creativecommons.org/publicdomain/zero/1.0/ https://creativecommons.org/licenses/by/4.0/ https://creativecommons.org/licenses/by-sa/4.0/ https://creativecommons.org/licenses/by-nc/4.0/ https://creativecommons.org/licenses/by-nc-sa/4.0/ https://creativecommons.org/licenses/by-nc-nd/4.0/ | Verify this field is populated (except for custom licenses, where dc.rights.uri may be blank). Verify that dc.rights and dc.rights.uri correspond. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
15 | Time Period Covered | Période couverte | dc.coverage.temporal | Recommended Metadata | Manual | Optional | Repeatble | Public | none | The date or date range to which the data refers. This field reflects the time period covered by the data, not the dates of coding, analysis period, or the dates the data was collected. Enter start and/or end dates in YYYY-MM-DD, YYYY-MM, or YYYY format. | Enter Start and/or End dates in YYYY-MM-DD, YYYY-MM, or YYYY format. Selections from the calendar will be in YYYY-MM-DD format. | Start: 2016-04-01 End: 2017-01-01 Start: 1985 End: 2008-12-31 Start: 2001-05 End: 2011-04 | Start and end dates are separated by a /. A start date without an end date is followed by a slash, and an end date without a start date is preceded by a slash. | 2016-04-01/2017-01-01 1985/ /2008-12-31 2001-05/2011-04 | Verify that date ranges are generally plausible. | 2026-02-06 | 2026-02-06 | ||
16 | Collection Period | Période de collecte | datacite.date.Collected | Recommended Metadata | Manual | Optional | Repeatable | Public | none | The date or date range in which the data was collected. Enter start and/or end dates in YYYY-MM-DD, YYYY-MM, or YYYY format. | Enter Start and/or End dates in YYYY-MM-DD, YYYY-MM, or YYYY format. Selections from the calendar will be in YYYY-MM-DD format. | Start: 2016-04-01 End: 2017-01-01 Start: 1985 End: 2008-12-31 Start: 2001-05 End: 2011-04 | Start and end dates are separated by a /. A start date without an end date is followed by a slash, and an end date without a start date is preceded by a slash. | 2016-04-01/2017-01-01 1985/ /2008-12-31 2001-05/2011-04 | Recent deposits review: Verify each date collected is plausible for the specific dataset. Verify that date ranges are generally plausible (e.g. end date isn’t in the future). | 2026-02-06 | 2026-02-06 | ||
17 | Funder | Organisation de financement | linked group | Recommended Metadata | Manual | Optional | Repeatable | Public | n/a | n/a | Each instance of the linked group must include all linked fields. Use a single dash ("-") in placeholder fields. | Verify that each record has the same number of entries for funder name/award number/award title and add missing placeholders; see Identify missing linked fields. | 2026-02-06 | 2026-02-06 2022-01-04 2021-06-09 2021-04-21 2021-01-12 | |||||
18 | > Funder | > Organisation de financement | datacite.fundingReference.funderName | Recommended Metadata | Manual | > Required in linked group | > Non-Repeatable in linked group | Public | en_US | Name of the funding provider. | Prefer the term used in the Crossref Funder Registry. Although multiple funders can currently be entered in one field with semicolon delimiters, separate them into separate fields. See FRDR - Funders Tracking for current values. See Crossref Funder Registry - Canadian Funders, Bilingual (v1.31) for the full list of Canadian funders. For non-Canadian funders, you can search the API, for example: https://api.crossref.org/funders?query=nserc https://api.crossref.org/funders?query=Canada%20Foundation%20for%20Innovation - you can type this with spaces, e.g. https://api.crossref.org/funders?query=Canada Foundation for Innovation | Natural Sciences and Engineering Research Council (NSERC) | When entered in the same field, multiple funders are delimited by semicolons. This should be split into separate fields, with the corresponding placeholders for Award Number and Award Title. | [Same as submission interface.] | List of funding agencies stored in tags. Free text permitted. | Review funder name for consistency: - Recent deposits review: Compare affiliations with the list in FRDR - Funders Tracking. Note inconsistencies for funder names that should match existing entries. - Full review only: See FRDR Metadata Review Procedures - Funders. | 2026-02-06 | 2026-02-06 2021-12-07 2021-08-13 2021-06-09 2021-04-21 2021-01-11 | |
19 | >Funder Identifier | datacite.fundingReference.funderIdentifier | Recommended Metadata | Automatic | > Optional in linked group | > Non-Repeatable in linked group | Public | none | The ROR of the funding provider. | ttps://ror.org/000az4664 | Automatically generated when depositor enters a funding provider if that funding provider has a ROR. | [Same as submission interface.] | ROR list. | Do not need to review. | |||||
20 | > Award Number | > Numéro de subvention | datacite.fundingReference.awardNumber | Recommended Metadata | Manual | > Optional in linked group | > Non-Repeatable in linked group | Public | en_US | The number or code assigned by the funder to a sponsored award or grant. | Free text. | 895-2016-1017 | Include placeholder "-" if there is no award number for a given funder. | [Same as submission interface.] | Review together with Award Title. Verify that the award number and title are reasonable, and that the award title should not be a funder name. | 2026-02-06 | 2026-02-06 2021-06-09 2021-02-22 | ||
21 | > Award Title | > Titre de la subvention | datacite.fundingReference.awardTitle | Recommended Metadata | Manual | > Optional in linked group | > Non-Repeatable in linked group | Public | en_US | The title or name of the award or grant. | Free text. For consistency with common award titles, see: Funders Cheat Sheet | Partnership Grant Program | Include placeholder "-" if there is no award title for a given funder. | [Same as submission interface.] | Review together with Award Number. Verify that the award number and title are reasonable, and that the award title should not be a funder name. | 2026-02-06 | 2026-02-06 2021-06-09 2021-02-22 | ||
22 | Contributor | Contributeur | datacite.contributor.DataCollector datacite.contributor.DataManager datacite.contributor.ProjectManger datacite.contributor.ResearchGroup datacite.contributor.Sponsor datacite.contributor.Supervisor datacite.contributor.Other Do not use: - datacite.contributor.DataCurator - datacite.contributor.Distributor - datacite.contributor.Editor - datacite.contributor.Producer - datacite.contributor.RelatedPerson - datacite.contributor.Researcher - datacite.contributor.HostingInstitution | Recommended Metadata | Manual | Optional | Repeatable | Public | none | A person or institution responsible for contributing to the dataset. Choose the type of contributor from the dropdown menu. | For a person's name, enter in indirect order (Last Name, First Name) and apply a period after any initials. Do not include a space between initials. Contributor type definitions are in the Depositor Guide. Contributors may be redundant with authors (dc.contributor.author) in cases where adding an author as a contributors clarifies the role of each author. Consut with the submitter if clarification is needed. | Archer, Reese D. Alberta Agriculture and Forestry | [Same as submission interface.] | [Same as submission interface.] | Verify that only valid contributor types are used; flag any former contributor types. Review all datacite.contributor.* fields for consistency: - Recent deposits review: Look for the inconsistencies listed below. - Full review only: see Personal names in dc.contributor.author and datacite.contributor.*. Common inconsistencies include: - Direct order instead of indirect order - Missing period after middle initial - Extra space between initials - Inclusion of titles, e.g. “Dr.” | 2026-02-06 | 2026-02-06 2021-11-26 2021-06-08 2021-02-11 2020-11-03 | ||
23 | Related Identifier | Identifiant associé | datacite.relatedidentifier.IsCitedBy datacite.relatedidentifier.Cites datacite.relatedidentifier.IsSupplementTo datacite.relatedidentifier.IsSupplementedBy datacite.relatedidentifier.IsPartOf datacite.relatedidentifier.HasPart datacite.relatedidentifier.IsDerivedFrom datacite.relatedidentifier.IsSourceOf datacite.relatedidentifier.Compiles datacite.relatedidentifier.IsCompiledBy datacite.relatedidentifier.Continues datacite.relatedidentifier.IsContinuedBy datacite.relatedIdentifier.IsNewVersionOf datacite.relatedIdentifier.IsPreviousVersionOf datacite.relatedIdentifier.IsReferencedBy datacite.relatedIdentifier.References | Recommended Metadata | Manual | Optional | Repeatable | Public | none | A link to a related resource. If available, provide the DOI (e.g. https://doi.org/10.1000/182). Choose the relationship between the dataset and the related resource from the dropdown menu. | This field must contain a URL. Ensure that DOIs are formatted as a URL (e.g. https://doi.org/10.1000/182; use this format and not http://dx.doi.org or another variant) If a URL is not available, use the Admin interface to move the value to datacite.descriptionType.Other (Notes). Relation type definitions are in the Depositor Guide. | https://doi.org/10.1000/182 | This field must contain a URL. If a URL is not available, use the admin interface to move the value to datacite.descriptionType.Other (Notes). Additional types may be used in the Admin interface if required: - datacite.relationtype.Continues - datacite.relationtype.IsContinuedBy - datacite.relationtype.IsDerivedFrom - datacite.relationtype.IsSourceOf | [Same as submission interface.] | Verify that only valid relation types are used; flag any other relation types. Verify that only URIs are used. Verify that DOIs are formatted using https://doi.org (not http or dx.doi.org). | 2026-02-06 | 2026-02-06 2022-01-03 2021-06-08 2021-02-11 | ||
24 | Notes | datacite.description.Other | Recommended Metadata | Manual / Automatic | Optional | Repeatable | Public | en_US / fr_CA | Additional important information about the dataset. | Free text. Use for metadata that does not fit into other fields, including version information, additional contact information, usage instructions, or related identifiers without URLs. | Anyone making use of these data has been requested by the author to provide information about intended use. | In addition to manually entered notes, some notes may be automatically generated when an item comes out of embargo: [en_US] Item exited embargo and became publicly available on YYYY-MM-DD [fr_CA] L’élément est sorti de sa période d’embargo et est devenu public le YYYY-MM-DD | [Same as submission interface.] | review not required | n/a | n/a | |||
25 | Geographic Coverage | Couverture géographique | datacite.geolocation.geolocationPlace | Geographical Metadata | Manual | Optional | Repeatable | Public | none | The geographic coverage of the dataset — i.e., the location(s) that the dataset is about. For each place name, enter as many fields as applicable to describe the location. The Country field is required in order to use the Province / Territory / State and City fields. Use GeoNames for correct spelling of place names and avoid abbreviations. | Enter a place name, country, province/territory/state, and/or city. All subfields are optional. | Place Name: Country: Canada Province / Territory / State: Alberta City: Edmonton Place Name: Country: Canada Province / Territory / State: Saskatchewan City: Place Name: Stanley Park Country: Canada Province / Territory / State: British Columbia City: Vancouver Place Name: Country: Canada Province / Territory / State: City: Place Name: Atlantic Ocean Country: Province / Territory / State: City: | Enter the Place Name, City, Province/Territory/State, and Country, separated by semicolons. Do not put a space after each semicolon. Use a placeholder "-" if a subfield is not applicable. | -;Edmonton;Alberta;Canada -;-;Saskatchewan;Canada Stanley Park;Vancouver;British Columbia;Canada -;-;-;Canada Atlantic Ocean;-;-;- | Recent deposits review: Verify the location name matches the location the dataset is about. Verify that the metadata is entered in the following format: "Additional Information;City;Province/State;Country" | 2026-02-06 | 2026-02-06 | ||
26 | Place Name | Nom de lieu | > datacite.geolocation.geolocationPlace, position 4 | Geographical Metadata | Manual | > Optional within field | > Non-repeatable within field | Public | n/a | General information on the geographic coverage of the data. Use for geographical names that are not a country, province/territory/state, or city; e.g. regions, water bodies, astronomy names, and alternate names. | Free text. | Staney Park Atlantic Ocean (blank) | The Place Name value is the 1st position of datacite.geolocation.geolocationPlace. | -;Edmonton;Alberta;Canada -;-;Saskatchewan;Canada Stanley Park;Vancouver;British Columbia;Canada -;-;-;Canada Atlantic Ocean;-;-;- | |||||
27 | Country | Pays | > datacite.geolocation.geolocationPlace, position 1 | Geographical Metadata | Manual | > Optional within field | > Non-repeatable within field | Public | n/a | The country or nation that the dataset is about. If the dataset covers multiple countries, list all of them separately. | Drop-down list of countries. | Canada (blank) | The Country value is the 4th position of datacite.geolocation.geolocationPlace. | -;Edmonton;Alberta;Canada -;-;Saskatchewan;Canada Stanley Park;Vancouver;British Columbia;Canada -;-;-;Canada Atlantic Ocean;-;-;- | List of countries. | ||||
28 | Province / Territory / State | Province / Territoire / État | > datacite.geolocation.geolocationPlace, position 2 | Geographical Metadata | Manual | > Optional within field | > Non-repeatable within field | Public | n/a | The province, territory, or state that the dataset is about. To use this field, the Country field is required. | If Canada or United States is selected for country: Drop-down list of provices/territories/states All other countries or no country selected: Free text. | Alberta Saskatchewan British Columbia (blank) | The Province / Territory / State value is the 3rd position of datacite.geolocation.geolocationPlace. | -;Edmonton;Alberta;Canada -;-;Saskatchewan;Canada Stanley Park;Vancouver;British Columbia;Canada -;-;-;Canada Atlantic Ocean;-;-;- | List of Canadian provinces/territories if Canada is selected for Country. List of U.S. states if United States is selected for Country. | ||||
29 | City | Ville | > datacite.geolocation.geolocationPlace, position 3 | Geographical Metadata | Manual | > Optional within field | > Non-repeatable within field | Public | n/a | The name of the city that the dataset is about. To use this field, the Country field is required. | Free text. | Edmonton Vancouver (blank) | The City value is the 2nd position of datacite.geolocation.geolocationPlace. | -;Edmonton;Alberta;Canada -;-;Saskatchewan;Canada Stanley Park;Vancouver;British Columbia;Canada -;-;-;Canada Atlantic Ocean;-;-;- | |||||
30 | Geographic Point | Point géographique | datacite.geolocation.geolocationPoint | Geographical Metadata | Manual | Optional | Repeatable | Public | none | Point where the data was gathered or about which the data is focused. Provide latitude and longitude. | Latitude ranges from -90 to +90; longitude ranges -180 to +180. You can use Google Maps to verify that the point is plausible. If you need to convert values in degrees, minutes, seconds to decimal degrees, you can use a tool such as the NGS Coordinate Conversion and Transformation Tool (NCAT) at https://geodesy.noaa.gov/NCAT/ | Latitude: 49.2827 Longitude: -123.1207 | Enter latitude and then longitude in decimal degrees, without comma separation. | 49.2827 -123.1207 | Verify that the format is correct (latitude-space-longitude). Recent deposits review only: Verify point matches the location the dataset is about. Full review only: See FRDR Metadata Review Procedures - Geolocation Point. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
31 | Latitude | Latitude | > datacite.geolocation.geolocationPoint, position 1 | Geographical Metadata | Manual | > Required within field | > Non-repeatable within field | Public | n/a | Latitude: Decimal degrees between -90 and +90. | 49.2827 | The latitude value is in the 1st postion of datacite.geolocation.geolocationPoint. | 49.2827 -123.1207 | ||||||
32 | Longitude | Longitude | > datacite.geolocation.geolocationPoint, position 2 | Geographical Metadata | Manual | > Required within field | > Non-repeatable within field | Public | n/a | Longitude: Decimal degrees between -180 and +180. | -123.1207 | The latitude value is in the 2nd postion of datacite.geolocation.geolocationPoint. | 49.2827 -123.1207 | ||||||
33 | Geographic Bounding Box | Cadre englobant géographique | datacite.geolocation.geolocationBox | Geographical Metadata | Manual | Optional | Repeatable | Public | none | Spatial region where the data was gathered or about which the data is focused. Provide a bounding box with decimal degree coordinates. | If possible, verify this is a valid bounding box using http://bboxfinder.com/ or another resource. With bboxfinder, coordinates must be placed in the order (xMin (W), yMin (S), xMax (E), yMax (N)). For example: datacite.geolocation.geolocationBox: 50.94256 -115.23563 50.97719 -115.13638 S = yMin: 50.94256 W = xMin:-115.23563 N = yMax: 50.97719 E = xMax: -115.13638 (xMin, yMin, xMax, yMax) = (-115.23563,50.94256,-115.13638,50.97719) | South Latitude: 49.203 West Longitude: -123.121 North Latitude: 49.297 East Longitude: -123.000 | Enter the southbound latitude, westbound longiitude, northbound latitude, and eastbound longitude in that order, without comma separation. | 49.203 -123.121 49.297 -123.000 | Verify that the format is correct (S W N E). Verify that latitudes (S and N) are between -90 and +90 and that longitudes (W and E) are between -180 and +180. Verify that S < N (always) and W < E (usually, unless crossing the prime meridian). Recent deposits review only: Verify bounding box matches the location the dataset is about. See "Curator Guide - Submission Interface" column for steps to visualize bounding box. Full review only: See FRDR Metadata Review Procedures - Geolocation Box. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||
34 | West Longitude | Longitude ouest | > datacite.geolocation.geolocationBox, position 2 | Geographical Metadata | Manual | > Required within field | > Non-repeatable within field | Public | n/a | Westbound coordinate of the bounding box. Decimal degrees between -180 and +180. | -123.121 | The west longitude value is in the 2nd position of datacite.geolocation.geolocationBox. | 49.203 -123.121 49.297 -123.000 | ||||||
35 | East Longitude | Longitude est | > datacite.geolocation.geolocationBox, position 4 | Geographical Metadata | Manual | > Required within field | > Non-repeatable within field | Public | n/a | Eastbound coordinate of the bounding box. Decimal degrees between -180 and +180. | -123.000 | The east longitude value is in the 4th position of datacite.geolocation.geolocationBox. | 49.203 -123.121 49.297 -123.000 | ||||||
36 | North Latitude | Latitude nord | > datacite.geolocation.geolocationBox, position 3 | Geographical Metadata | Manual | > Required within field | > Non-repeatable within field | Public | n/a | Northbound coordinate of the bounding box. Decimal degrees between -90 and +90. | 49.297 | The north latitude value is in the 3rd position of datacite.geolocation.geolocationBox. | 49.203 -123.121 49.297 -123.000 | ||||||
37 | South Latitude | Latitude sud | > datacite.geolocation.geolocationBox, position 1 | Geographical Metadata | Manual | > Required within field | > Non-repeatable within field | Public | n/a | Southbound coordinate of the bounding box. Decimal degrees between -90 and +90. | 49.203 | The south latitude value is in the 1st position of datacite.geolocation.geolocationBox. | 49.203 -123.121 49.297 -123.000 | ||||||
38 | Embargo Date | Date d'embargo | frdr.embargo.current | Access | Manual | Optional | Non-Repeatable | Internal | none | The first day access to your data is allowed by others. Until this date, only you will have access to the data. Your dataset may appear in search results based upon the settings under Metadata Access below. | Select the embargo date from calendar. Must be an exact date in YYYY-MM-DD format. | 2021-01-01 | Use the "Change Embargo" button in the Admin interface to update the embargo date under "Embargo Settings". | 2022-03-01 | review not required | n/a | n/a | ||
39 | Reason | Raison | n/a | Access | Manual | Optional | Non-Repeatable | Internal | n/a | The reason for the embargo. Used by the Curator to determine validity of the embargo for internal use only. See Terms of Use for details. | Free text. | Dataset is restricted while the resulting paper is undergoing review. | Use the "Change Embargo" button in the Admin interface to update the embargo reason under "Embargo Settings". | [Same as submission interface.] | review not required | n/a | n/a | ||
40 | frdr.embargo.previous | dc.rights.uri | frdr.embargo.previous | Automatic | Optional | Repeatable | Internal | none | n/a | n/a | n/a | A previous embargo date. Automatically generated when embargo date changes via "Change Embargo" function. Each embargo changes adds a new instance of this field. | 2021-03-01 | review not required | n/a | n/a | |||
41 | datacite.publicationyear | datacite.publicationyear | Automatic | Required | Non-Repeatable | Public | none | n/a | n/a | n/a | Automatically generated upon submission with the current year. If necessary, this may be manually changed to reflect a previous date of publication in another repository, matching dc.date.issued. Versioned datasets may have a mismatch due to an earlier version having an earlier publication year. | 2020 | Verify this date is present. Verify that publicationyear matches dc.date.issued. Versioned datasets may have a mismatch: their publicationYear may be the year of a previous version (e.g. version 1 published in 2024, version 2 published in 2025, and version 2's publicationYear is listed as 2024). This is incorrect, and the publicationYear of a version should always be the most recent year and match the date issued. | 2026-02-06 | 2026-02-06 2022-01-03 2021-04-21 2021-01-12 | ||||
42 | datacite.resourcetype | datacite.resourcetype | Automatic | Required | Repeatable | Public | en_US | n/a | n/a | n/a | Automatically generated upon submission with "Dataset". | Dataset | Dataset | Verify value is “Dataset”. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | |||
43 | dc.description.provenance | dc.description.provenance | Automatic/Manual | Required | Repeatable | Internal | en except embargo provenance: en_US / fr_CA | n/a | n/a | n/a | Automaticallly generated upon submission, rejection, approval, and availability in Globus. Manually add dc.description.provenance to accompany changes to data files and/or metadata after publication. Include your name and email address, the date, and a brief description of the change. | Submitted by Kelly Stathis (kelly.stathis@carl-abrc.ca) on 2019-11-27T21:40:03Z Rejected by Lee Wilson (lee.wilson@ace-net.ca) on 2019-11-27T22:00:05Z (GMT) Approved for entry into archive by Erin Clary (erin.clary@carl-abrc.ca) on 2020-01-14T00:57:09Z (GMT) Made available in Globus Data Publication on 2020-01-14T00:57:17Z (GMT). Updated to change datacite.contributor.HostingInstitution[en_US] to datacite.contributor.HostingInstitution by Kelly Stathis (kelly.stathis@carl-abrc.ca) on 2020-03-30. | review not required | n/a | n/a | ||||
44 | dc.date.accessioned | dc.date.accessioned | Automatic | Required | Repeatable | Public | none | n/a | n/a | n/a | Automatically generated with approval date/time. | 2020-01-14T00:57:17Z | Verify this date is present. | 2026-02-06 | 2026-02-06 2022-01-03 2021-04-21 2021-01-12 | ||||
45 | dc.date.available | dc.date.available | Automatic | Required | Repeatable | Public | none | n/a | n/a | n/a | Automatically generated with approval date/time or embargo date, whichever is later. Updated when embargo date is changed, or if missing when the item comes out of embargo. Previously, dc.date.available was automatically generated with the submission date/time. | 2020-01-14T00:57:17Z | Verify this date is present. | 2026-02-06 | 2026-02-06 2022-01-03 2021-04-21 2021-01-12 | ||||
46 | dc.date.issued | dc.date.issued | Automatic | Required | Non-Repeatable | Public | none | n/a | n/a | n/a | Automatically generated with approval date or embargo date, whichever is later, in YYYY-MM-DD format. Updated when embargo date is changed, or if missing when the item comes out of embargo. If necessary, dc.date.issued may be manually changed to reflect a previous date of publication in another repository. In all other cases, dc.date.issued will match dc.date.available. Versioned datasets may have a mismatch due to an earlier version having an earlier publication year. | 2020-01-13 2021-07-20T20:14:47Z | Verify this date is present. Verify that publicationyear matches dc.date.issued. Versioned datasets may have a mismatch: their publicationYear may be the year of a previous version (e.g. version 1 published in 2024, version 2 published in 2025, and version 2's publicationYear is listed as 2024). This is incorrect, and the publicationYear of a version should always be the most recent year and match the date issued. | 2026-02-06 | 2026-02-06 2022-01-03 2021-04-21 2021-01-12 | ||||
47 | dc.identifier.uri | dc.identifier.uri | Automatic | Required | Repeatable | Public | none | n/a | n/a | n/a | Automatically generated upon submission: one instance of dc.identifier.uri contains the handle, and a second instance contains the DOI formatted as a URL. | https://www.frdr.ca/repo/handle/doi:10.20383/101.0193 https://doi.org/10.20383/103.0594 | Verify that FRDR URI is present. Verify that DOI is present and correctly formatted (e.g. https://doi.org/10.20383/101.0114). | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||||
48 | dc.publisher | dc.publisher | Automatic | Required | Non-Repeatable | Public | none | n/a | n/a | n/a | Automatically generated upon submission with "Federated Research Data Repository / dépôt fédéré de données de recherche". | Federated Research Data Repository / dépôt fédéré de données de recherche | Verify value is “Federated Research Data Repository / dépôt fédéré de données de recherche”. | 2026-02-06 | 2026-02-06 2021-11-26 2021-08-11 2021-04-21 2021-01-12 | ||||
49 | globus.shared_endpoint.name | globus.shared_endpoint.name | Automatic | Required | Non-Repeatable | Internal | none | n/a | n/a | n/a | Automatically generated upon submission. Globus endpoint name. | 8bf1acc6-dc7a-11e8-8c8c-0a1d4c5c824a | review not required | n/a | n/a | ||||
50 | globus.shared_endpoint.path | globus.shared_endpoint.path | Automatic | Required | Non-Repeatable | Internal | none | n/a | n/a | n/a | Automatically generated upon submission. Globus endpoint path. | /1/published/publication_126/ | review not required | n/a | n/a | ||||
51 | frdr.datasetreview.external | Functions the same as if the depositor checked off the option for external review during the submission process. | |||||||||||||||||
52 | Contact Instructions | frdr.contact.directions | Deprecated | Optional | Non-Repeatable | Internal | en_US | Instructions to public users on when to use the contact form. | Free text. All remaining contact instructions have been moved to datacite.descriptionType.Other (Notes). | Please provide information about intended use to the author. | [Same as submission interface.] | [Same as submission interface.] | review not required | n/a | n/a |