The lowest level class, which is used to contain all further metadata. The MI_Metadata class is taken from ISO 19115-2:2009, and is an extension of MD_Metadata from ISO 19115:2003.
A unique identifier for the metadata record. This field is generated by the MERIDIAN submission form invisibly during the submission process.
The language and locale of the element being described. Only required for textual (character-based) content. For MERIDIAN, this takes the form of an ISO 639-2/T three letter language code. Currently, the submission form invisibly inserts Eng; Can (adding additional details on the locale, Canada) for the metadata language of online submissions.
This element describes the resource which the metadata record describes. For example, a metadata record for a dataset would have a hierarchy level of dataset. This entry is selected from a codelist. The MERIDIAN submission form landing page determines what hierarchy level a metadata submission is assigned.
The character set or encoding used in the element being described (e.g., the metadata). The submission form assigns UTF-8 for metadata, but for the related resource it may vary. Only required for textual (character-based) content.
Hierarchy level name
A free text representation of the gmd:hierarchyLevel. This is automatically generated when using MERIDIAN's web form.
Describes which person or organization was responsible for creating the metadata and can be contacted with questions. Usually this is the person who performs the metadata submission. This field is not shown on the MERIDIAN discovery portal.
The name of a person. Conditional: At least one name (gmd:individualName and gmd:organizationName) is required.
The name of an organization. Conditional: At least one name (gmd:individualName and gmd:organizationName) is required.
A class which contains contact details for the named individual or organization. Whenever gmd:CI_Citation is used, there must be at least one gmd:CI_Citation with at least one gmd:contactInfo containing an electronic address.
Contains multiple fields used to describe a physical or electronic address. Electronic address is strongly recommended. Conditional: At least one of gmd:phone and gmd:address must be provided.
Multiple fields, allowing the input of a phone number and a fax number. Phone numbers strongly preferred to fax numbers. Conditional: At least one of gmd:phone and gmd:address must be provided.
Free text description of special instructions or limitations on contacting a named individual or organization.
The role of the named party. Specific values for role may be recommended for specific contexts. E.g., the metadata contact is recommended to be "custodian".
The date of metadata creation. Usually this is the date the metadata is submitted to MERIDIAN, but for older records it may be a date in the past.
Metadata standard name
The name of the metadata standard or profile used to generate the metadata record. Reference to the MERIDIAN metadata profile should be made here.
Metadata standard version
The specific version of the metadata standard or profile used to generate the metadata record. Reference to the specific version of the MERIDIAN metadata profile used should be made here.
Class containing information on the quality of the related resource. E.g., completeness of the resource, known 'bad spots', etc. For resources involving experimental data collection, we recommend repeating this class for both the collection session and the post-processing work.
The scope of the resource covered by the quality report. E.g., if the quality information only relates to a specific file or temporal extent, this element records it.
The history of the resource in the reported scope. Should include details on processing, any modifications which were applied, calibrations, and sources used.
A class which describes how the element being described is maintained and updated. May include contact information as well.
How frequently the element being described is changed. This element is selected from a codelist. By default, it is set to "notPlanned", indicating no updates are planned.
Details on how the resource was acquired or generated. This is most relevant for experimental data, but also has implications for model data.
A class which contains details on the platform used to generate the resource. A platform usually holds multiple instruments and is not necessarily crewed. A ship and an ocean buoy may both be considered platforms.
An identifier for the platform, which can be used to distinguish it from other platforms. E.g., a serial number.
A list of instruments which are mounted on the platform. Each instrument should be named by its identifier.
A class which contains details on a specific instrument which was used to generate a measurement. An instrument is usually a specific sensor or apparatus, and generally mounted on, or attached to, a platform. Conditional: When instruments have been used in the collection of the resource (but you are not describing a platform they are mounted on), we require this class be used. Otherwise, place them in the equivalent gmi:instrument class inside the gmi:platform element.
The identifier of a specific instrument. Must be unique enough to distinguish it from other similar instruments, and ideally tie the instrument to a calibration file.
A class which contains details and identification information for a specific resource. Generally, this class is used to contain details on the dataset. gmd:MD_DataIdentification has been extended into MER:MD_DataIdentification to incorporate Darwin Core elements. Although strictly repeatable, this is not recommended.
A citation for the resource or object being described. E.g., for a dataset, this would be a class containing the dataset citation.
The title of the resource as it should appear in a citation.
Contains a specific event in the life of the resource (e.g., creation, last modification, publication) selected from a codelist and the ISO 8601 date for that event. Creation date is required to appear here, for insertion into a dataset citation.
A list of the people and parties who should be acknowledged in a citation for the resource.
An abstract for the resource in free text. Generally a brief description of what is contained in the resource and how it was acquired.
The purpose of the resource - the reason it was created and the goal it was meant to achieve.
The status of the resource as selected from a codelist. That is, is the resource still in development, or has it been deprecated in some way? Choose the most appropriate value from the associated codelist.
Point of contact
The individuals or organizations who bear responsibility for the resource and are willing to be contacted should there be questions about the resource.
The specific type of the instrument described. E.g., a voltmeter versus a hydrophone versus a satellite.
The party responsible for updating the resource. Required if updates are planned.
The physical, geographic, temporal, and optionally vertical extent of the resource described.
An optional free text description of the (physical, geographic, temporal and/or vertical) extent of the resource.
The physical, geographic extent over which the resource was collected or is valid, described using latitudes and longitudes. This container class can hold multiple different representations of extent, but only the most relevant ones are shown here.
Allows the extent to be described using GML-style series of polygons or points. Conditional: at least one class in gmd:geographicElement is required.
Geographic bounding box
The extreme limits of the geographic extent described in terms of 2 bounding latitudes and 2 bounding longitudes, within which all of the extent is contained. This results in a box on a normal cylindrical map projection (e.g., Mercator). Conditional: at least one class in gmd:geographicElement is required.
Contains the time period over which the resource was collected or is otherwise valid.
The eastern-most longitude which was measured, observed, simulated, or stored in the resource. The east bound should be strictly larger than the west bound. The longitude should be measured as if it were performed with conventional GPS using the WGS84 coordinate reference system.
The western-most longitude which was measured, observed, simulated, or stored in the resource. The east bound should be strictly larger than the west bound. The longitude should be measured as if it were performed with conventional GPS using the WGS84 coordinate reference system.
The southern-most latitude which was measured, observed, simulated, or stored in the resource. The north bound should be strictly larger than the south bound. The latitude should be measured as if it were performed with conventional GPS using the WGS84 coordinate reference system.
The northern-most latitude which was measured, observed, simulated, or stored in the resource. The north bound should be strictly larger than the south bound. The latitude should be measured as if it were performed with conventional GPS using the WGS84 coordinate reference system.
A free text class which can contain any information which does fit elsewhere, but is deemed by the metadata contact to be relevant to others in some way.
Details on how the resource is distributed or might be acquired.
Contains details on the digital format of the resource.
The name of the digital format used to contain the resource. May be a MIME type.
The version of the format used to contain the resource. A version number or unique identifier can be used to distinguish multiple versions of the same format.
Container class for keywords and their thesauri. At least 1 keyword is required. Repeat this class for each unique type of keyword.
Each instance of this element contains a single keyword.
Information about the party which distributes the resource. Conditional: Only required if a direct download link (Transfer options) is not provided.
The name and contact details for the resource distributor. As this class can only be used once within gmd:distributor, repeat gmd:distributor if there are multiple distributor contacts - or group them into a single organization.
Free text details on how to acquire the resource from the distributor. Used when a direct link cannot be provided for whatever reason.
List of possible ways to acquire the resource, typically related to physical and digital formats. Used to contain directions on online linkages. Conditional: Only required when an online linkage is available and there is no known distributor. Otherwise, fill in gmd:distributor and transfer options there.
Contains information on how to download a resource from the web.
The link to the item, not including the protocol. E.g., www.google.com - without the leading HTTP.
The transfer protocol used. E.g., HTTP or FTP. Combined with linkage to create a functioning link on the catalogue.
The size of the resource, when distributed, in megabytes. Essentially, the amount of data required for a requester to obtain the resource from the distributor. If the resource is stored in a compressed format, the size of the compressed object is expected.
The general broad category which the above keyword(s) belong(s) to. Recommended, but not required, if the gmd:descriptiveKeywords element is to be repeated.
Information on the the thesaurus or controlled vocabulary used to supply the above keywords. Conditional: Required when providing the primary 4 keywords, but otherwise optional.
Container class for the constraints and limitations on use. Can be replaced by extended classes with additional constraint details, such as security classification. Although repeatable, this is not recommended.
Free text description of the limitations on use. E.g., the name of a Creative Commons license.
Provides a general category for the resource from a list of simple categories.
A broad class which contains free text descriptions of the computing environment which was used to generate or process the resource, or those which might be necessary to successfully operate or view the resource. E.g., things like required memory or software, compatible operating systems, and other known issues.
The meaning of this class has been changed from the original Darwin Core meaning. This class is used to contain information on annotation sets. Each annotation set gets its own Occurrence.
Darwin Core: (Occurrence) recorded by
Information on who recorded the associated occurrence or annotation set. Only one element allowed, so all recorders must be in a single element. Enter names in a consistent manner - preferably Last name, First name.
Darwin Core: Organism quantity
The number of annotations recorded in a given annotation set.
Darwin Core: Organism quantity type
The units of the above measurement. Required whenever Organism Quantity is recorded. For MERIDIAN, this is 'number of annotations'.
Darwin Core: Associated references
References used or related to the given occurrence. E.g., references to sound detection algorithms.
Darwin Core: Occurrence remarks
Any other comments about the given occurrence or annotation set.
Darwin Core: Organism
The Darwin Core class which contains information about specific organisms. Each unique organism requires its own Organism class. We strongly recommend this class is tied closely to a taxon, as an organism ought to be a member of a specific taxon.
Darwin Core: Organism name
The name of the given organism. This could either be a vernacular name or an identifier. The MERIDIAN submission form uses this as the organism identifier as well.
Darwin Core: Organism remarks
Remarks about the given organism. May include field observations.
Darwin Core: Event
The Darwin Core class for specific event information. MERIDIAN has repurposed this to be used for additional information related to a specific occurrence, in particular the sampling methodology and effort. Each Event is therefore tied to an occurrence.
Darwin Core: Sampling protocol
Information about the sampling protocol or methodology used to gather a specific annotation set.
Darwin Core: Sampling effort
Information about the amount of effort expended to gather a particular annotation set.
Darwin Core: Identification
This class is used to contain information regarding the animal identification process applied to a given annotation set. As an annotation set is not necessarily paired with positively identified animals, these concepts have been separated.
Darwin Core: Identified by
Contains a list of people or algorithms which performed the associated identifications.
Darwin Core: Identification references
A list of references used in the given identification process.
Darwin Core: Identification remarks
Any other remarks related to the given identification.
Darwin Core: Taxon
Contains information related to a specific taxon. This should be used to identify the specific species in a given identified annotation. As such, this is tied to identification in our approach.
Darwin Core: Scientific name
The scientific or taxonomic name of a given taxon. This is distinct from a taxon identifier, which is usually assigned by a taxonomic organization.
Darwin Core: Vernacular name
The common name of a given taxon. In the event there are multiple, attempt to use the most well known one, or use multiple separated by a semicolon.
Darwin Core: Taxon remarks
Any other comments related to a specific taxon.
Darwin Core record level terms
Darwin Core makes use of record level terms, which can be used within any class. These are frequently used to link together various classes.
Darwin Core: Basis of record
The origin of the given Darwin Core record - whether it was human-made or machine-made. We recommend this is only used in Occurrence, but it may be used in any class.
Darwin Core: Information withheld
A generic free text element which is used to describe information which may be available, but has been withheld from the metadata record.
Darwin Core: Occurrence ID
An identifier for a specific occurrence. Used to internally tie classes together.
Darwin Core: Organism ID
An identifier for a specific organism. Used internally to tie classes together.
Darwin Core: Event ID
An identifier for a specific event. To specifically used within the MERIDIAN submission form - an event is given an Occurrence ID instead - but can be used to increase redundancy.
Darwin Core: Identification ID
An identifier for a specific identification process. Used to tie various classes together.
Darwin Core: Taxon ID
An identifier for a specific taxon. Used to tie various classes together.
Within ISO, a generic class used to contain information regarding raw data or other content within a resource, generally through reference to a sensor or coverage. For MERIDIAN, we repurposed this class to contain information on physical parameters contained with a specific model.
Contains a brief description of what has been modelled.
Classification of the content described. For models, we recommend 'thematicClassification'.
Each instance of this class contains information on a specific modelled dimension or variable.
The name of the variable modelled.
A free text description of the variable modelled.
This is a free text description of the history of the resource in the specified scope. Things like calibrations, data cleaning, and error corrections could be described here.
Contains details on sources used in the development of the resource. Most relevant for model data sets, but potentially relevant for other resource types.
A free text description of the source and its relevance to the resource. Best to describe in relationship to the current resource. This should not be a copy/paste of the source's abstract.
Contains all the elements necessary to create a complete citation to the source.
A free text description of the instrument. Can include details on calibrations, known issues, model information, or point to external manuals.
Instrument event list
Contains a list of events specific to the instrument and relevant to the resource being described.
Event list description
Contains details on the character set and language used to describe the events.
A description of a singular event in reference to a specific instrument during the data collection period of the current resource.
The general type of event described. Selected from a codelist.
Contains information about the overall project or operation which operated the instruments during the data collection process. E.g., a large research project, a funded expedition...
An identifier or other unique name for the operation.
Free text description of the current operation.
The current status of the operation, as selected from a codelist.
Platforms involved in the operation
The elements within this class are identical to those within the other gmi:platform associated with gmi:MI_AcquisitionInformation. Conditional: If there is a platform to be described, put it here - not in the other gmi:platform. Used to unambiguously tie platforms to the operation which ran them.
A free text description of the platform being described. May include links to other papers or resources which provide further detail on the platform.
Contains details on people or organizations which built, launched, or operated the platform.
Instruments mounted on platform
Contains details on each instrument mounted on a particular platform. Contains the same elements as the previous gmi:MI_Platform instance (within gmi:MI_AcquisitionInformation). Required because we expect you to have at minimum a single instrument attached to a given platform.
List of possible ways to acquire the resource, typically related to physical and digital formats. Used to contain directions on online linkages. Conditional: Only required when an online linkage is available with a known distributor. Otherwise, fill in gmd:transferOptions below.
Single instrument event
Contains details about a single event with respect to a particular instrument.