INSPIRE Metadata for DIAS (IN PROGRESS)
Summary
-
Resource title -
Resource abstract -
Resource type -
Resource locator -
Unique resource identifier -
Coupled resource -
Resource language -
Topic category -
Spatial data service type -
Keyword value -
Geographic bounding box -
Temporal extent -
Date of publication -
Date of last revision -
Date of creation -
Lineage -
Degree -
Specification -
Limitations on public access (other constraints) -
Limitations on public access (classification) -
Conditions applying to access and use -
Responsible party -
Responsible party role -
Metadata point of contact -
Metadata date -
Metadata language
Identification
Resource title
– dataset, dataset series, services –
This is a characteristic, and often unique, name by which the resource is known. The title is the most informative element of a metadata record and usually the highest priority as search engines go to this element.
RECOMMENDATIONS:
The Resource Title has to be concise and to the point. It should not contain unexplained acronyms or abbreviations. It is recommended a maximum length of 250 characters and keeping the similarity with the original title of the resource, in the sense of the ‘official naming’.
If the data or service is part of a larger project, it is recommended to indicate the Project at the end of the title, in brackets. In case of Project names, abbreviations are allowed, as long as the rest of the title follows the guidelines above and the abbreviation is spelled out immediately in the abstract.
Resource abstract
– dataset, dataset series, services –
This is a brief narrative summary of the content of the resource. The abstract provides a clear and concise statement that enables the reader to understand the content of the data or service.
RECOMMENDATIONS:
The resource abstract is a succinct description that can include:
– A brief summary with the most important details that summarise the data or service
– Coverage: linguistic transcriptions of the extent or location in addition to the bounding box
– Main attributes
– Data sources
– Legal references
– Importance of the work.
Do not use unexplained acronyms.
Summarise the most important details in the first sentence or first 100 characters.
Resource type
– dataset, dataset series, services –
This is the type of resource being described by the metadata and it is filled in with a value from a classification of the resource based on its scope. The choice of Resource Type will be probably the first decision made by the user and it will define the metadata elements that should be filled.
Resource locator
– dataset, dataset series, services –
Dataset and dataset series:
The Resource Locator is the ‘navigation section’ of a metadata record which point users to the location (URL) where the data can be downloaded, or to where additional information about the resource may be provided.
Setting up the correct resource locators is important for the connection between the data and the services that provide access to them or for providing additional information concerning the resource.
RECOMMENDATIONS:
If no direct link to a resource is available, provide link to a contact point where more information about the resource is available.
Services:
The Resource Locator for Services, if available, provides the access point of the service, that is an Internet address containing a detailed description of a spatial data service, including a list of endpoints to allow an automatic execution.
RECOMMENDATIONS:
If no direct link to a resource is available, provide link to a contact point where more information about the resource is available.
Unique resource identifier
– dataset, dataset series –
This element is a value uniquely identifying the resource.
RECOMMENDATION:
Never delete an existing identifier for a resource. If a change in resource identification is needed, add a new identifier but also keep the old one.
Coupled resource
– services –
If the resource is a spatial data service, this metadata element refers to, where relevant, the target spatial data set(s) of the service. It is implemented by reference, i.e. through a URL that points to the metadata record of the data on which the service operates. It helps therefore linking services to the relevant datasets.
Resource language
– dataset, dataset series –
It refers to the language(s) used within the resource (dataset, series, or service if relevant).
RECOMMENDATION:
If the resource does not contain any textual information (e.g. only codes and digits), the language should be defaulted to the value of the metadata language.
Classification of spatial data and services
Topic category
– dataset, dataset series –
The topic category is a high-level classification scheme to assist in the grouping and topicbased search of available spatial data resources.
A correct categorization is very important to help users to search and find the resources they are looking for.
Spatial data service type
– services –
This is a classification to assist in the search of available spatial data services. The list of language-neutral values as in Part D3 of the INSPIRE Metadata Regulation 1205/2008/EC includes: discovery, view, download, transformation, invoke and other.
If the service is also an INSPIRE Network Services, then it is necessary to include in the Metadata element 2.8.2 Specifications, reference to the relevant INSPIRE Network Service Implementing Rule or amendment.
Keyword
Keyword value
– dataset, dataset series, services –
The keyword value is a commonly used word, formalised word or phrase used to describe the subject. While the topic category is too coarse for detailed queries, keywords help narrowing a full text search and they allow for structured keyword search
RECOMMENDATION:
It is better to select keyword values from a collection of terms linked and predefined (controlled vocabularies).
It is suggested to choose a minimum of two keywords in addition to the required keyword from the GEMET – INSPIRE themes (for dataset and dataset series) or the categories from part D 4 of the INSPIRE Metadata Regulation 1205/2008/EC (for services).
Ideally, both a code (neutral language value) and a human-readable label (in any language) should be included in the metadata.
Geographic location
Geographic bounding box
– dataset, dataset series –
This is the extent of the resource in the geographic space, given as a bounding box. Defining the coordinates of a rectangle representing the resource area on a map allows the discovery by geographical area.
– Western-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east);
– Eastern-most coordinate of the limit of the dataset extent, expressed in longitude in decimal degrees (positive east);
– Northern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north);
– Southern-most coordinate of the limit of the dataset extent, expressed in latitude in decimal degrees (positive north).
Temporal reference
Temporal extent
– dataset, dataset series, services –
The temporal extent defines the time period covered by the content of the resource.This time period may be expressed as:
– an individual date
– an interval of dates (starting date and ending date)
– a mix of individual dates and intervals of dates
Date of publication
– dataset, dataset series, services –
This is the date of publication of the resource when available, or the date of entry into force.
There may be more than one date of publication.
Date of publication differs from the temporal extent. For example, a dataset might have been published in March 2009 (2009-03-15) but the covered information was collected over the year 2008 (temporal extent from 2008-01-01 to 2008-12-31).
Date of last revision
– dataset, dataset series, services –
This date describes when the resource was last revised, if the resource has been revised.
Date of revision differs from the temporal extent. For example, a dataset might have been revised in April 2009 (2009-04-15) but the covered information was collected over the year 2008 (temporal extent from 2008-01-01 to 2008-12-31).
Date of creation
– dataset, dataset series, services –
This date describes when the resource was created.
Date of creation differs from the temporal extent. For example, a dataset might have been created in February 2009 (2009-02-15) but the covered information was collected over the year 2008 (temporal extent from 2008-01-01 to 2008-12-31).
Quality and validity
Lineage
– dataset, dataset series, services –
According to the Implementing Rules for Metadata, Lineage is ‘a statement on process history and/or overall quality of the spatial data set. Where appropriate it may include a statement whether the data set has been validated or quality assured, whether it is the official version (if multiple versions exist), and whether it has legal validity. The value domain of this element is free text.’
The process history may be described by information on the source data used and the main transformation steps that took place in creating the current data set (series).
RECOMMENDATIONS:
If a data provider has a procedure for the quality management of their spatial data set (series) then the appropriate ISO data quality elements and measures should be used to evaluate and report (in the metadata) the results. If not, the Lineage metadata element (defined in the Implementing Rules for Metadata) should be used to describe the overall quality of a spatial data set (series).
The use of acronyms should be avoided. If used, their meaning should be explained.
Conformity
Degree
– dataset, dataset series, services –
This is the degree of conformity of the resource to the implementing rules adopted under Article 7(1) of INSPIRE Directive 2007/2/EC or other specification.
Specification
– dataset, dataset series, services –
This is a citation of the implementing rules adopted under Article 7(1) of INSPIRE Directive 2007/2/EC or other specificationto which a particular resource conforms.
If a spatial data service is an INSPIRE Network service, use this element to report the relevant INSPIRE Network Implementing Rule to which it conforms.
A resource may conform to more than one implementing rules adopted under Article 7(1) of INSPIRE Directive 2007/2/EC or other specification.
Constraints related to access and use
Limitations on public access (other constraints)
– dataset, dataset series, services –
Limitations on public access shall be represented by at least one of these metadata elements:
– MD_LegalConstraints. accessConstraints
– MD_LegalConstraints. otherConstraints
– MD_SecurityConstraints. classification
This metadata element shall provide information on the limitations and the reasons for them.
If there are no limitations on public access, use the free text available in MD_LegalConstraints. otherConstraints to enter “No Limitations” in the language used for the metadata.
Limitations on public access (classification)
– dataset, dataset series, services –
See Limitations on public access (other constraints)
Conditions applying to access and use
– dataset, dataset series, services –
See Limitations on public access (other constraints)
Responsible organisation
Responsible party
– dataset, dataset series, services –
This is the description of the organisation responsible for the establishment, management, maintenance or distribution of the resource.
RECOMMENDATION:
The name of the organization should be given in full, without abbreviations. It is recommended to use institutional email instead of personal emails.
Responsible party role
– dataset, dataset series, services –
This is the role of the responsible organisation.
RECOMMENDATION:
Select all roles that best represent the function performed by the responsible party.
Metadata on metadata
Metadata point of contact
– dataset, dataset series, services –
This is the description of the organisation responsible for the creation and maintenance of the metadata. This refers to the metadata record and not to the resource responsible party; they will not necessarily be the same.
RECOMMENDATION:
The name of the organization should be given in full, without abbreviations. It is recommended to use institutional email instead of personal emails.
Metadata date
– dataset, dataset series, services –
The date which specifies when the metadata record was created or updated.
Metadata language
– dataset, dataset series, services –
This is the language in which the metadata elements are expressed.