Public documentation

h1. Creation of metadata of EEA spatial datasets using the EEA SDI editor

User Guidance

{{toc}}

h2. 1. Introduction

This document is targeting EEA staff, ETC partners and EEA contractors who need to create metadata of geospatial datasets following the EEA metadata profile with the final objective of registering those geospatial datasets in the EEA catalogue of geospatial datasets (EEA SDI), accessible through http://sdi.eea.europa.eu.

The reference, complete version of the EEA metadata profile, to which the metadata of EEA geospatial datasets need to be compliant, is available on *https://taskman.eionet.europa.eu/projects/public-docs/wiki/Cataloguemetadata_guidelines*. The EEA metadata profile is compliant with ISO 19115:2003 and ISO/TS 19139:2007 as well as with "the INSPIRE Metadata Technical Guidelines based on ISO 19115 and ISO 19119 V. 1.3":http://inspire.ec.europa.eu/documents/Metadata/MD_IR_and_ISO_20131029.pdf. 

This page describes the main practical steps to create metadata using the EEA custom view of the "*SDI editor*":https://sdi.eea.europa.eu/editor-catalogue. The SDI Editor is based on an Open Source software GeoNetwork (The GeoNetwork version used by the SDI Editor is 3.4.3.), which is freely available on https://geonetwork-opensource.org/.

While using the EEA SDI editor is highly recommended, should this not be possible these guidelines are also useful as they point out to how to fill in key metadata elements in order to comply with the EEA metadata profile. 

All the information on how to trigger the registration of geospatial datasets in the EEA SDI, for which an EEA profile-compliant metadata file is mandatory, is available in the "*EEA SDI Wiki*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/EEA_SDI. This wiki also provides basic information on the SDI components (metadata catalogue and data storage) and links to the main naming conventions. 

For further information, please contact the "SDI Team":mailto:sdi@eea.europa.eu.

h2. 2. Getting started: how to add a new or import an existing metadata file

To access the SDI metadata editor it is necessary to go to https://sdi.eea.europa.eu/editor-catalogue and login with your Eionet account. If you do not have an Eionet account or cannot access the editor please contact the "SDI Team":mailto:sdi@eea.europa.eu.

!2a.jpg!

Once you are logged in, in order to create or import a new metadata record please click on *“Contribute”* where you will find several options – the main ones are *“Add new record”* or *“Import new records”* which use cases are described below.

!2b.jpg!

h3. 2.1 Add new record

This option is recommended if you are starting from scratch, i.e. you are creating a new metadata from the beginning, or when you have a metadata file which may not be following the EEA metadata profile, ISO or INSPIRE specifications. 

The EEA SDI Team has created a partially-filled in *EEA MD template* which shall be used in this case. The template is available in the editor but is also available for "*download (xml format)*":https://taskman.eionet.europa.eu/attachments/53631/EEA_metadata_template.xml, for its use in other metadata editors.

Therefore, to add a new record, click on *“Contribute”* then select *“Add new record”* and, after checking that the option *“EEA metadata template”* is selected, click on *“Create”.* The system will then create a new record on the basis of the pre-selected template. 

!21.jpg!

The newly created metadata record will be automatically opened in your browser. You will need now to go to [[SDI_editor_guidance#3-Edition-of-a-metadata-record|section 3]] for a step-by-step guidance on how to fill in the template.

h3. 2.2 Import new records

This option is only recommended if you want to use an existing metadata file as a template. It is important to check first if the metadata you are using is following the EEA metadata profile – and in any case, to follow always this guidance and the EEA metadata profile documentation as a reference. 

Click on *“Contribute”* then select *“Import new records”* from the drop-down menu. There are several methods to import a metadata record: uploading a file from your local computer or from a remote location (URL), or copying/pasting the XML content directly (see below):

!22.jpg!

After selecting the preferred method, make sure that the following options are selected (they should be pre-selected by default):

 -Type of record: Metadata

 -Record identifier processing: Generate UUID for inserted metadata

 -Apply XSLT conversion: none

 -Option “Validate” not selected

 -Option “Publish” not selected

 -Option “Assign to current catalog” selected

 -Assign to group: eea_users

 -Assign to category: none

After checking the configuration above, click on *“+Import”*. The import should take only a few seconds, if any. If the file has been imported correctly an *“Import report”* will appear to the right side of the interface including the UUID of the new metadata. You can open the metadata record by clicking on the pencil icon *"Edit"*.

!22b.jpg!

Otherwise, to open the recently imported file please go back to *“Contribute”* where you will find a list of metadata records. The last one you have imported should appear on top of the list and your Eionet user should appear as *“owner”* right below the title. Then please click on the *“Edit”* icon to start the edition of the metadata record. 

You will need now to go to [[SDI_editor_guidance#3-Edition-of-a-metadata-record|section 3]] for a step-by-step guidance on how to fill in the metadata record. 

!22c.jpg!

There is another similar option to create a metadata file based on an existing one, by using the option *“Duplicate”* on the metadata that we want to copy, in the list appearing after clicking on *“Contribute”*. 

!22d.jpg!

The selected metadata will appear in the screen, being the next step clicking on *“Create”*. 

!22e.jpg!

The editor window will be then open automatically for you to start editing.

h2. 3. Edition of a metadata record

Once the metadata file has been created or imported, we can already start editing and filling in the metadata elements. 

There are three editor views (interfaces) you can eventually use: *“EEA”*, *“Simple”* and *“Full”*. “EEA” view is a customised view that we will follow in this document, as it shows only the EEA metadata profile elements as well as tips and recommendations on how to fill them in (boxes in blue). The *“Simple”* and *“Full”* views exist by default in any GeoNetwork implementation. The *“Full”* view provides all possible options from the ISO 19115 standard while the *“Simple”* is a simplified version of the full view.  

!3a.jpg!

The order in which the elements appear in this document follows exactly the order of appearance (top-down) in the EEA view of the SDI editor. This may not be the order in which they may appear in the EEA metadata profile reference wiki. Please note that elements marked with a *"*"* are mandatory with respect to the EEA metadata profile. 

As a general recommendation throughout the editing process, please save regularly the metadata record to avoid losing any changes during the editing (the *“Save metadata”* button can be found in the upper right corner). Although by default it will be selected, please ensure that you on the button it appears *“Save metadata”* .

!3.jpg!

h3. 3.1 Section “Identification of resource”

h4. a) Title

<pre>

XML element: MD_Metadata/identificationInfo/*/citation/*/title

</pre>

Rename the *“Title”* field following the "*naming convention*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/Naming_conventions#2-Dataset-title-convention.

The title should be self-explanatory and should not contain acronyms unless they are widely known. In any case, should an acronym be used in the title, it shall be made explicit in the abstract.

Then click on *“Save metadata”* to save it and continue to fill in the fields as appropriate.

!31a.jpg!

h4. b) Dataset identifier

<pre>

XML element: MD_Metadata/identificationInfo/*/citation/*/identifier

</pre>

The *“Dataset identifier”* shall be unique and ideally meaningful, following this "*naming convention*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/Naming_conventions#1-Dataset-identifier-convention.

!31b.jpg!

h4. c) Edition

<pre>

XML element: MD_Metadata/identificationInfo/*/citation/*/edition

</pre>

Add *“Edition”* number, which consists of the version number and revision number separated by a “.” as they are indicated in the dataset identifier. It is recommended that this is also indicated in the [[Naming_conventions#2-Dataset-title-convention|Dataset Title]] and in the [[Naming_conventions#1-Dataset-identifier-convention|Dataset Identifier]]. 

!31c.jpg!

h4. d) Date

<pre>

XML element: MD_Metadata/identificationInfo/*/citation/*/date

</pre>

Set at least the creation date for the dataset, and publication date if the dataset is published on the "EEA website":https://www.eea.europa.eu/data-and-maps. There shall be not more than one date of creation and publication. 

Optionally, date of last edition/revision can be added when relevant.

!31d.jpg!

h4. e) Abstract

[XML element: MD_Metadata/identificationInfo/*/abstract]

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. Ideally it should also contain information about the coverage (linguistic transcriptions of the extent or location), main attributes, data sources, legal references and importance of the work. Acronyms should be written in full when first used. When the metadata refers to a revision of an already existing dataset, it is important to indicate as well the main changes on this new version.

!31e.jpg!

h3. 3.2 Section “Classification and keywords”

h4. a) “Classification - ISO 19115 Topic categories”

[MD_Metadata/identificationInfo/*/topicCategory]

Choose at least one from this code list. This is a high-level classification scheme defined in Part D 2 of the INSPIRE Metadata Regulation 1205/2008/EC and are derived directly from the topic categories defined in MD_TopicCategoryCode (B.5.27) of ISO 19115.

!32a.jpg!

h4. b) “Keywords – INSPIRE theme”

[MD_Metadata/identificationInfo/*/descriptiveKeywords (INSPIRE themes)]

Choose at least one of "the 34 INSPIRE Spatial Data Themes":http://www.eionet.europa.eu/gemet/en/inspire-themes/.

!32b.jpg!

h4. c) “Keywords – GEMET concepts”

[MD_Metadata/identificationInfo/*/descriptiveKeywords (GEMET concepts)]

Choose at least 2-3 GEMET concepts, see "thesaurus":http://www.eionet.europa.eu/gemet/en/themes/.

!32c.jpg!

h4. d) “Keywords – Spatial coverage of the dataset”

[MD_Metadata/identificationInfo/*/descriptiveKeywords (Location / coverage of the dataset)]

This metadata element is used to describe the intended spatial coverage of a dataset in text form. Where appropriate, country codes such as those described "*here*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/Country_codes (see example in the screenshot) should be used instead of listing all Member States.

!32d.jpg!

h4. e) “Keywords – EEA data categories”

[MD_Metadata/identificationInfo/*/descriptiveKeywords (EEA data categories]

By default, the EEA category is set to *“geospatial data”* as the SDI only publishes metadata of geospatial datasets for now. Should you need to add more keywords here please contact the "SDI Team":mailto:sdi@eea.europa.eu.

!32e.jpg!

h4. f) “Keywords – EEA keywords list”

[MD_Metadata/identificationInfo/*/descriptiveKeywords (EEA keywords list)]

EEA keywords shall be short, meaningful and shall not duplicate other metadata elements (such as INSPIRE Themes, GEMET or EEA categories). Whenever possible, keywords from the list of terms used in the EEA website to tag datasets shall be reused, "see list":https://taskman.eionet.europa.eu/projects/public-docs/wiki/Catalogueeea_keywords.

!32f.jpg!

h4. g) “Catalogue category”

Select additional catalogue labels for your metadata. The default label is set to datasets as the EEA metadata catalogue so far only includes dataset or a dataset series metadata. Should the dataset be free, full and open for re-use, please also select the label geodatacore so this dataset can be discovered by the GEOSS.

!32g.jpg!

h3. 3.3 Section “Spatial and Temporal Extent”

h4. a) “Geographic bounding box”

[MD_Metadata/identificationInfo/*/extent (spatial)]

This is the actual geographic extent of the resource, represented by the minimum rectangle which encompasses all features in the dataset. The bounding box shall be expressed in decimal degrees with a precision of at least 2 decimals, with positive east and north. For datasets including overseas territories, it is advised to split the overall geographic extent into several bounding boxes. The coordinates of the bounding boxes shall be expressed in any geodetic coordinate reference system with the Greenwich Prime Meridian.

!33a.jpg!

h4. b) “Temporal extent”

[MD_Metadata/identificationInfo/*/extent (temporal)]

This element describes the time period covered by the content of the dataset, normally related to the data collection period. When the dataset refers to a (specific) full year, *"Begin Date"* should be set to 1st January of that year and *"End Date*" should be set to 31st December of that year.

!33b.jpg!

h3. 3.4 Section “Spatial representation and resolution”

h4. a) “Ref. System”

[MD_Metadata/referenceSystemInfo/*/referenceSystemIdentifier]

The Coordinate Reference System shall be referred to with its EPSG code, here we provide only those more commonly used at the EEA. Should you require any CRS not present in this list please contact the "SDI Team":mailto:sdi@eea.europa.eu.

!34a.jpg!

h4. b) “Spatial representation type”

[MD_Metadata/identificationInfo/*/spatialRepresentationType]

Method used to spatially represent geographic information, based on the elements of the codelist defined in ISO 19115 MD_SpatialRepresentationTypeCode.

!34b.jpg!

h4. c) “Spatial resolution type”

[MD_Metadata/identificationInfo/*/spatialResolution]

This element refers to the level of detail of the data set. It shall be expressed either as a resolution distance (typically for gridded data and imagery-derived products) or the equivalent scale (typically for maps or map-derived products), but not both. Although it is possible to specify several spatial resolutions, we require to have only one (smallest scale or coarsest resolution).

!34c.jpg!

h4. d) “Temporal resolution”

[MD_Metadata/identificationInfo/*/descriptiveKeywords (Temporal resolution of the dataset)]

ISO 19115-1 refers to this element as the smallest resolvable temporal period in a resource. "Springer":https://link.springer.com/referenceworkentry/10.1007%2F978-0-387-35973-1_1376 defines temporal resolution as the amount of time needed to revisit and acquire data for the exact same location. When applied to remote sensing, this amount of time depends on the orbital characteristics of the sensor platform as well as sensor characteristics. This element is to be filled in in particular for time series.

!34d.jpg!

h3. 3.5 Section “Additional technical information”

h4. a) “Maintenance and update frequency”

[MD_Metadata/identificationInfo/*/resourceMaintenance]

Frequency with which modifications and deletions are made to the data after it is first produced. This dataset is required for all datasets with a revision number. This element takes a value out of the codelist of ISO19115 element MD_MaintenanceFrequencyCode. In case no frequency from the list is satisfactory, switch to the full view and use the element PeriodDuration as indicated in the "*EEA metadata guidelines*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/Cataloguemetadata_guidelines#Guidelines-for-creators-of-metadata-related-to-spatial-datasets.

!35a.jpg!

h4. b) “Language of dataset”

[MD_Metadata/identificationInfo/*/language]

English selected by default, choose another language, if needed.

!35b.jpg!

h4. c) “Distribution format”

[MD_Metadata/distributionInfo/*/distributionFormat]

This element provides the format(s) in which the resource is stored and distributed. The element should be expressed using codes from the list derived from those used by the libraries GDAL and OGR (if a format is missing, contact the "SDI Team":mailto:sdi@eea.europa.eu).

!35c.jpg!

h3. 3.6 Section “Data quality”

h4. a) “Lineage”

[MD_Metadata/dataQualityInfo/*/lineage]

This element provides a statement on process history and the overall quality of the spatial data set. The process history may be described with the information on the source data used and the main transformation steps that took place in creating the current data set (or dataset series). This element should also address version specificities where suitable. It should also 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 statement can reference an already existing document made available together with the dataset or be included in the metadata.

!36a.jpg!

h4. b) “Conformity”

"Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council":https://eur-lex.europa.eu/legal-content/EN/ALL/?uri=OJ:L:2010:323:TOC as regards interoperability of spatial data sets and services.

!36b.jpg!

h3. 3.7 Section “Resource constraints”

h4. a) “Access constraints”

[MD_Metadata/identificationInfo/*/resourceConstraints/*/useLimitation and */accessConstraints

Code list based element which refers to any constraints applied to assure the protection of privacy or intellectual property and any special restriction or limitation on obtaining the resource or the metadata. By default and for EEA datasets this element is set to *“Other Restrictions”*. For datasets which are not owned by EEA but are distributed by EEA please select the appropriate code from the list. In case of a doubt, please contact the "SDI Team":mailto:sdi@eea.europa.eu.

!37a.jpg!

h4. b) "Other constraints”

Other restrictions and legal prerequisites for accessing and using the resource or metadata. For EEA datasets this element is set to *“No limitations”*.

!37b.jpg!

h4. c) “Use limitation”

[MD_Metadata/identificationInfo/*/resourceConstraints/*/useLimitation and */accessConstraints]

This element provides a statement on any limitation that can affect the fitness of use of the resource or metadata. The EEA template includes by default the standard text to be included for those datasets owned by EEA which can be freely distributed. For datasets which are not owned by EEA but are distributed by EEA please insert the statement corresponding to the applicable policy. In case of a doubt, please contact the "SDI Team":mailto:sdi@eea.europa.eu.

!37c.jpg!

h3. 3.8 Section “Responsible Party”

h4. a) “Point of contact”

[MD_Metadata/identificationInfo/*/pointOfContact (point of contact]

This element provides the identification of those organisations associated with the dataset. By default, and for EEA owned datasets, the responsible party for the roles of *“Point of contact”* and *“Custodian”* of the dataset is set to the EEA. If the dataset is not owned by the EEA, select a contact from the list of predefined entries. Contact the "SDI Team":mailto:sdi@eea.europa.eu if you think a new contact should be added to the register.

!38a.jpg!

h3. 3.9 Section “Associated resources”

h4. a) “Thumbnail and Online resources”

[MD_Metadata/identificationInfo/*/graphicOverview (Dataset thumbnail)

[MD_Metadata/distributionInfo/*/transferOptions]

Links for internal access (EEA file path) and the graphic overview (thumbnail) will be added by the SDI Team during the registration process. The thumbnail (max. 1 MB) has to be uploaded in the "*Taskman ticket*":https://taskman.eionet.europa.eu/projects/datasets-for-sdi/issues, see "*the description of the related procedure*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/EEA_SDI#3Registration-of-datasets-in-the-EEA-SDI.

Link to website: When available, please add the link to the webpage where the dataset is accessible.

Link to the webmap service: When available, please add the link to the WMS GetCapabilities using “OGC:WMS” protocol or to the corresponding layer.

Link to rest web services: When available, please add the link to the ESRI Rest service using the “ESRI:REST” protocol.

!39a.jpg!

h3. 3.10 Section “Validation”

h4. a) Validation

This tool is under development and will include an automated check against different standards (e.g. EEA metadata profile, ISO 191215(19139), Inspire).

!310a.jpg!

h2. 4. Other functionalities of the EEA SDI editor

h3. 4.1 Visualisation of the metadata in editing mode

The visualisation of the metadata record depends on the selected view. By default, the EEA view is visualised. 

In case you want to add more fields then please select simple/full view to visualise the necessary fields.

!41.jpg!

h3. 4.2 “Close”/“Save and close“ 

You can save and/or close your metadata whenever is needed.

!42.jpg!

h3. 4.3 How to find a metadata record

You can use the search option (free text search/filters) or clicking on the *“Contribute”* to simply visualise the list of the recently edited records in EEA SDI editor.

!43.jpg!

h3. 4.4 Display mode of the metadata

!44.jpg!

h3. 4.5 Download options

After the completion of the metadata record you can close the editing window and will be able to download the metadata record in different formats (e.g. xml, pdf) or display it in different views (e.g. default, full and xml view).

!45.jpg!

h3. 4.6 Re-open metadata records

Click on *“Edit”* and update your metadata record.

!46.jpg!