Nationell Metadataprofil version 4.0 - för Geodata

Hjälp om enskilda metadataelement och sektioner av metadata

Denna sammanställning av den Nationella metadata är framtagen för att det skall vara enkelt att få en överblick om vilka metadata som är definierade i profilen. Ordningen är inte anpassad efter hur den underliggande standarden är strukturerad utan är istället ordnad för att informationen skall vara enklare att förstå.
Målet är att denna sammanställning skall ge tilräcklig information för att förstå vad man kan ange.  För att sedan fylla i metadata kan man läsa mer detaljerad hjälp i exempelvis GeodataExplorer.

 

Elementnanm Krav Antal Beskrivning
Identifiering
Titel obligatorisk enkel namn som resursen är känd under
Alternativ titel frivillig multipel kortnamn eller namn i annat språk som resursen är känd under
Referensdatum villkorad multipel Datum som anger när resursen skapades, revideras och/eller publicerades.
Identfierare för resursen villkorad multipel Unik identfierare för en datamängd
Information om resursen
Beskrivning av resursen obligatorisk enkel
Sammanfattning frivillig enkel En sammanfattande beskrivning av resursen
Status frivillig enkel
Exempelbild frivillig multipel
+ Resurskontakt obligatorisk multipel
Child Row 1 frivillig enkel Content for expandable row
Klassificering frivillig enkel
Initiativ frivillig enkel En klassificering som anger specifika användningsområden, Exempelvis Inspire, Öppna data
Inspire-tema villkorad enkel
Ämnesområde obligatorisk enkel
Information om dataset obligatorisk enkel
Identifierare för resursen obligatorisk enkel
Språk i resurs obligatorisk multipel
Rumslig representation obligatorisk multipel
Rumslig upplösning obligatorisk multipel
Information om tjänst
Sammankopplade resurser
Typ av tjänst
Klassificering av tjänst
Restriktioner
Användbarhetsbegränsningar
Åtkomstrestriktioner
Nyttjanderestriktioner
Begränsningar i publik åtkomst
Kvalitet
Historik
Överensstämmelse
Kvalitetsrapport
Tillhandahållande
Distributör
Format
Online-länkar
Information om metadata
Datum för metadata
Språk i metadata
Metadatastándard
Version av metadatastandard
Metadatakontakt

 

Second table content

Elementnanm Krav Antal Beskrivning
Identifiering
Titel obligatorisk enkel namn som resursen är känd under
Alternativ titel frivillig multipel kortnamn eller namn i annat språk som resursen är känd under
Referensdatum villkorad multipel Datum som anger när resursen skapades, revideras och/eller publicerades.
Identfierare för resursen villkorad multipel Unik identfierare för en datamängd
Information om resursen
Beskrivning av resursen obligatorisk enkel
Sammanfattning frivillig enkel En sammanfattande beskrivning av resursen
Status frivillig enkel
Exempelbild frivillig multipel
+ Resurskontakt obligatorisk multipel
Child Row 1 frivillig enkel Content for expandable row
Child Row 2 frivillig enkel Content for expandable row
Klassificering frivillig enkel
Initiativ frivillig enkel En klassificering som anger specifika användningsområden, Exempelvis Inspire, Öppna data
Inspire-tema villkorad enkel
Ämnesområde obligatorisk enkel
Information om dataset obligatorisk enkel
Identifierare för resursen obligatorisk enkel
Språk i resurs obligatorisk multipel
Rumslig representation obligatorisk multipel
Rumslig upplösning obligatorisk multipel
Information om tjänst
Sammankopplade resurser
Typ av tjänst
Klassificering av tjänst
Restriktioner
Användbarhetsbegränsningar
Åtkomstrestriktioner
Nyttjanderestriktioner
Begränsningar i publik åtkomst
Kvalitet
Historik
Överensstämmelse
Kvalitetsrapport
Tillhandahållande
Distributör
Format
Online-länkar
Information om metadata
Datum för metadata
Språk i metadata
Metadatastándard
Version av metadatastandard
Metadatakontakt

 

Metadata about the metadata record

Name : Metadata date
UK GEMINI id 30
Definition Date on which the metadata was last updated, or was confirmed as being up-to-date, or if not updated, then the date it was created
Purpose and meaning This is the date at which the metadata can be considered current (rather than the dataset itself). It may be the date at which the metadata was reviewed and confirmed as being ‘current’. It is used to distinguish which of two records with the same fileIdentifier the system will keep.
Obligation Mandatory
Occurrence Single
Data type Date
Domain Single date as specified by BS ISO 8601 in the extended date format (YYYY-MM-DD), where YYYY is the year, MM is the month and DD is the day. Time (HH:MM:SS, where HH is the hour, MM the minutes and SS the seconds) may be added if required, separated from the day by ‘T’.
Guidance
  1. This should be updated whenever the metadata is updated due to a change in the dataset, or when it is reviewed and confirmed as wholly correct.
  2. The date should be at an appropriate level of resolution (e.g. the day, or the day and month).
  3. The date should not be in the future.
Comment If the metadata has not been updated, then this should be the date when it was created.
Examples 2001-09-02
Revision date May 2018
Corresponding element in other standards...
Standard Name Comparison
INSPIRE Metadata Metadata date Equivalent
ISO 19115:2003 MD_Metadata.dateStamp Equivalent
ISO 19139:2007 /gmd:MD_Metadata/gmd:dateStamp/gco:Date Equivalent
Change history...

GEMINI 1 to 2.0: Change of name from Date of last update of metadata

Encoding guidelines...
Guidelines The encoding example for metadata date is shown in Example One. Note that it is
possible to record the date and time of the metadata instance using the encoding shown in
Example Two.
Example

Example One

<gmd:MD_Metadata>
  ...
  <gmd:dateStamp>
    <gco:Date>2009-10-15</gco:Date>
  </gmd:dateStamp>
  ...
</gmd:MD_Metadata>

Example Two (date and time)

<gmd:MD_Metadata>
  ...
  <gmd:dateStamp>
    <gco:DateTime>2009-10-15T12:01:30</gco:DateTime>
  </gmd:dateStamp>
  ...
</gmd:MD_Metadata>

 
Metadata errors observed...
Errors observed This is used to distinguish which of two records with
the same fileIdentifier the system will keep. Even if the records are moved to a different
server, if the fileIdentifier and metadata date are the same, the harvester will not collect
the new files.

Name : Metadata language

UK GEMINI id 33
Definition Language used for documenting the metadata
Purpose and meaning The purpose of this is to identify the language used in a multi-lingual metadata
service, for example in the INSPIRE geo-portal.
Obligation Mandatory
Occurrence Single
Data type CharacterString
Domain Free text
Guidance

  1. It is recommended to select a value from a controlled vocabulary, for example that
    provided by ISO 639-2 which uses three-letter primary tags with optional subtags.
  2. The values for the UK are:
    English eng
    Welsh cym*
    Irish gle
    Gaelic (Scottish) gla
    Cornish cor
    Ulster Scots sco

    *ISO 639/2 has two codes for Welsh: textual (‘cym’) and
    bibliographic (‘wel’). For GEMINI we recommend using cym, which abbreviates
    that language’s own name for itself.

  3. Other official European languages are listed at Official languages of the EU.
  4. In general, a default value of ‘eng’ can be applied.
  5. If there is only a small amount of metadata in a second language, e.g. Alternative title, then Metadata language should still indicate the main language.
Comment For INSPIRE, the metadata itself must be in one of the official European
languages, such as English or Irish.
Examples eng
Revision date September 2018
Corresponding element in other standards...
Standard Name Comparison
INSPIRE Metadata Metadata language Equivalent
ISO 19115:2003 MD_Metadata.language Equivalent
ISO 19139:2007 /gmd:MD_Metadata/gmd:language/gmd:LanguageCode Equivalent
Change history...

GEMINI 1 to 2.0: New element

Encoding guidelines...
Guidelines INSPIRE recommends providing the name of the language as content of the
gmd:LanguageCode element
Example

 

<gmd:MD_Metadata>
  ...
  <gmd:language>
    <gmd:LanguageCode 
      codeList='http://www.loc.gov/standards/iso639-2/php/code_list.php' 
      codeListValue='eng'>English</gmd:LanguageCode>
  </gmd:language>
  ...
</gmd:MD_Metadata>

Metadata errors observed...
Errors observed
Metadata language missing
Metadata language is optional in ISO 19115 and GEMINI
2.2, but mandatory for INSPIRE and therefore in GEMINI 2.3. This is now checked by the UK
Location GEMINI schematron.

Name : Metadata point of contact

UK GEMINI id 35
Definition Party responsible for the creation and maintenance of the metadata
Purpose and meaning This is the organisation or role in an organisation responsible for this
metadata.
Obligation Mandatory
Occurrence Multiple
Data type CharacterString
Domain Free text
Guidance Should include organisation name and contact email address, as described under
Responsible party.
Comment
Examples Large-scale Topographic Data Manager, Ordnance Survey.
Revision date July 2009
Corresponding element in other standards...
Standard Name Comparison
INSPIRE Metadata Metadata point of contact Equivalent
ISO 19115:2003 MD_Metadata.contact > CI_ResponsibleParty ISO 19115 has a general class
ISO 19139:2007 /gmd:MD_Metadata/gmd:contact/gmd:CI_ResponsibleParty
Change history...

GEMINI 1 to 2.0: New element

Encoding guidelines...
Guidelines

 

  • The encoding example for metadata point of contact is shown below. Note that the
    example shows the minimum required information.
  • The format of address and contact information is described at Responsible party, with a more
    fully populated example.
  • More than one metadata point of contact may be expressed in metadata. The role of at
    least one metadata point of contact shall be ‘pointOfContact’.

 
Example

Example showing minimum required information

<gmd:MD_Metadata>
  ...
  <gmd:contact>
    <gmd:CI_ResponsibleParty>
      <gmd:organisationName>
        <gco:CharacterString>SeaZone Solutions</gco:CharacterString>
      </gmd:organisationName>
      <gmd:contactInfo>
        <gmd:CI_Contact>
          <gmd:address>
            <gmd:CI_Address>
              <gmd:electronicMailAddress>
                <gco:CharacterString>info@seazone.com</gco:CharacterString>
              </gmd:electronicMailAddress>
            </gmd:CI_Address>
          </gmd:address>
        </gmd:CI_Contact>
      </gmd:contactInfo>
      <gmd:role>
        <gmd:CI_RoleCode 
          codeList='https://schemas.isotc211.org/schemas/19139/resources/codelist/gmxCodelists.xml#CI_RoleCode' 
          codeListValue='pointOfContact'>pointOfContact</gmd:CI_RoleCode>
      </gmd:role>
    </gmd:CI_ResponsibleParty>
  </gmd:contact>
  ...
</gmd:MD_Metadata>

 
Metadata errors observed...

No error information available

 

Name : Resource type

UK GEMINI id 39
Definition Scope to which metadata applies
Purpose and meaning To distinguish between datasets, series, and services
Obligation Mandatory
Occurrence Single
Data type CodeList
Domain

MD_ScopeCode from ISO 19115. Codes to be used for datasets and dataset series are:

  • dataset
  • series

 
Guidance Identify whether resource is a dataset or a series (collection of datasets with a
common specification).
Comment  
Examples dataset
Revision date July 2009
Corresponding element in other standards...
Standard Name Comparison
INSPIRE Metadata Resource type Identical
ISO 19115:2003 MD_Metadata.hierarchyLevel Equivalent
ISO 19139:2007 /gmd:MD_Metadata/gmd:hierarchyLevel Equivalent
Change history...

GEMINI 1 to 2.0: New element, required for INSPIRE

Encoding guidelines...
Guidelines No specific rules for this metadata element
Example 

<gmd:MD_Metadata>
  ...
  <gmd:hierarchyLevel>
            <gmd:MD_ScopeCode codeListValue='dataset' 
              codeList='https://schemas.isotc211.org/schemas/19139/resources/codelist/gmxCodelists.xml#MD_ScopeCode'>dataset</gmd:MD_ScopeCode>
  </gmd:hierarchyLevel>
  ...
</gmd:MD_Metadata>
Metadata errors observed...
No error information available

Name : File Identifier

UK GEMINI id 45
Definition Unique identifier for this metadata file
Purpose and meaning To support the operation of UK Location and INSPIRE, discovery metadata records must
include a File Identifier for the resource.
Obligation Mandatory
Occurrence Single
Data type CharacterString
Domain Free text
Guidance

  1. File Identifier must be populated with a unique identifier. This may be a UUID
    generated by a metadata creation tool.
    Once created and published to UK
    Location, the File Identifier must not be changed.

    A change to the File Identifier would represent the creation of a new resource.

    If the UK Catalogue receives two records with the same File Identifier, the one
    with the more recent metadata date will be retained.
  2. Persistence and uniqueness across the metadata infrastructure are key
  3. Only use characters that are allowed in URIs (RFC3986), in particular, do not use
    curly brackets
  4. ISO AP 1.0 recommends that
    it is a UUID
Comment File Identifier should not be confused with the UK GEMINI2 metadata item
Resource identifier, which identifies the data resource being described.
Examples
Revision date March 2019
Corresponding element in other standards...
Standard Name Comparison
INSPIRE Metadata metadata/2.0/rec/common/fileIdentifier Equivalent
ISO 19115:2003 MD_Metadata.fileIdentifier Equivalent
ISO 19139:2007 /gmd:MD_Metadata/gmd:fileIdentifier Equivalent
Change history...
  • introduced in the UK Location application profile and XML encoding
  • New element in GEMINI 2.3
Encoding guidelines...
Guidelines

 

  1. The first XML child element of any GEMINI2 metadata instance shall be
    gmd:fileIdentifier. The content of this XML element is the identifier of the metadata
    instance. File identifier is not a metadata item of GEMINI2. It is not to be confused
    with the metadata item Resource identifier.
  2. The content of the XML element shall be a unique managed identifier, such as a
    system generated UUID. Once the identifier has been set for a metadata instance it
    shall not change.

 
Example 

<gmd:MD_Metadata>
  <gmd:fileIdentifier>
    <gco:CharacterString>98e25be5-388d-4be3-bc5f-ba07ef6009b2</gco:CharacterString>
  </gmd:fileIdentifier>
  ...
</gmd:MD_Metadata>

 
Metadata errors observed...
Errors observed

  1. Two records with the same identifier, resulting in only one being harvested
  2. New identifier for an existing record, leading to duplicate records
  3. Identifiers wrapped in curly brackets

Name : Hierarchy level name

UK GEMINI id 47
Definition Name of the hierarchy level for which the metadata is provided
Purpose and meaning Required in the ISO 19115 encoding of GEMINI 2.3 metadata records, where it allows
for multiple scoped sections in the metadata.
Obligation Conditional, required when Resource type (ISO hierarchyLevel) is not “dataset”.
Occurrence Single
Data type CharacterString
Domain Free text
Guidance Set to “service”, “series” as appropriate. Can be set “dataset”, but in that case it is optional
Comment
Examples

  • series
Revision date April 2020
Corresponding element in other standards...
Standard Name Comparison
INSPIRE Metadata see metadata/2.0/req/sds/resource-type, even for series Equivalent
ISO 19115:2003 MD_Metadata.hierarchyLevelName Equivalent
ISO 19139:2007 /gmd:MD_Metadata/gmd:hierarchyLevelName Equivalent
Change history...
New element in GEMINI 2.3
Encoding guidelines...
Guidelines No specific rules for this metadata element
Example

Example 1 - dataset, where hierarchyLevelName could just be omitted

<gmd:MD_Metadata>
  ...
  <gmd:hierarchyLevelName gco:nilReason="inapplicable"/>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification id="BGS-13607137">
      ...
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

Example 2 – series, where hierarchyLevelName is required

<gmd:MD_Metadata>
  ...
  <gmd:hierarchyLevelName>
    <gco:CharacterString>series</gco:CharacterString>
  </gmd:hierarchyLevelName>
  ...
  <gmd:identificationInfo>
    <gmd:MD_DataIdentification id="OSTerrain50">
      ...
    </gmd:MD_DataIdentification>
  </gmd:identificationInfo>
  ...
</gmd:MD_Metadata>

 
Metadata errors observed...

No error information available

 

html goes here