SDI editor guidance » History » Revision 260
Revision 259 (Jose Rubio, 2019-12-18 11:57) → Revision 260/294 (Jose Rubio, 2020-02-11 09:28)
h1. EEA SDI Editor User Guide
{{>toc}}
h2. 1. Introduction
This wiki page 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 and complete version of the EEA metadata profile*, to which the metadata of EEA geospatial datasets need to be compliant, and on which this page is based, is available [[Cataloguemetadata_guidelines|here]]. The EEA metadata profile is compliant with ISO 19115:2003 and ISO/TS 19139:2007 as well as with "Technical Guidance for the implementation of INSPIRE dataset and service metadata based on ISO/TS 19139:2007":https://inspire.ec.europa.eu/file/1705/download?token=iSTwpRWd.
*This page describes the main practical steps to create metadata using the EEA customised view of the* "*SDI editor*":https://sdi.eea.europa.eu/editor-catalogue. The SDI Editor is based on an Open Source software GeoNetwork (the current version used is 3.10), 3.8), which is freely available on https://geonetwork-opensource.org/.
While using the EEA SDI editor is highly recommended, should this not be possible this user guidance is also useful as it helps fill in key metadata elements in order to comply with the EEA metadata profile. A "metadata template":https://taskman.eionet.europa.eu/attachments/77813 is also available to facilitate the compliance with the EEA metadata profile.
A key consideration before starting the creation of an EEA metadata file is that *there is a 1:1 relation between metadata and datasets*: several MD cannot point out at the same dataset – i.e. geodatabases should contain one dataset described by a metadata set. All other important information, such as how to trigger the registration of geospatial datasets in the EEA SDI, is available in the "*EEA SDI Wiki main page*":https://taskman.eionet.europa.eu/projects/public-docs/wiki/EEA_SDI, which 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/77813, 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 (Code)
<pre>
XML element: MD_Metadata/identificationInfo/*/citation/*/identifier
</pre>
The *Dataset identifier* or *code* 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
<pre>
XML element: MD_Metadata/identificationInfo/*/abstract
</pre>
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
<pre>
XML element: MD_Metadata/identificationInfo/*/topicCategory
</pre>
Choose at least one from the code list provided, which 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. The full list is available in [[Cataloguemetadata_guidelines#MD_MetadataidentificationInfotopicCategory|the detailed metadata guidelines]].
!32a.jpg!
h4. b) Keywords – GEMET - INSPIRE themes
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
Choose at least one of the 34 INSPIRE Spatial Data Themes from the code list provided, aligned with the "INSPIRE theme registry":http://inspire.ec.europa.eu/theme.
!32b.jpg!
h4. c) Keywords – GEMET
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
Choose at least 2-3 concepts from the full and/or hierarchical list provided, which is linked to the "GEMET thesaurus":http://www.eionet.europa.eu/gemet/en/themes/.
!32c.jpg!
h4. d) Keywords – Spatial scope
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
This keyword is used to describe the administrative level that the dataset intends to cover and a value should be taken from code list Spatial Scope in the "INSPIRE registry":http://inspire.ec.europa.eu/metadata-codelist/SpatialScope. Typically this value will be "European".
!32d.jpg!
h4. e) Keywords – Continents, countries, sea regions of the world
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
This metadata element is used to describe the intended spatial coverage of a dataset in text form. A list of possible values is provided. 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.
!32e.jpg!
h4. f) Keywords – EEA (data) categories
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
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.
!32f.jpg!
h4. g) Keywords – EEA keywords list
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
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.
These keywords are intended to be used only by internal EEA users and are available through the catalogue only for authenticated users.
!32g.jpg!
h4. h) Catalogue category
Select additional catalogue labels for your metadata for categorisation purposes. Should the dataset be free, full and open for re-use, please select the label geodatacore so this dataset can be discovered by the GEOSS. Please note that this label is not reflected in the XML metadata as it is only internal to Geonetwork.
!32h.jpg!
h3. 3.3 Section “Spatial and Temporal Extent”
h4. a) Geographic bounding box
<pre>
XML: MD_Metadata/identificationInfo/*/extent
</pre>
This is the actual geographic extent of the resource. It is represented by the minimum rectangle which encompasses all features in the dataset, described by the maximum and minimum latitude and longitude. 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
<pre>
XML element: MD_Metadata/identificationInfo/*/extent
</pre>
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
<pre>
XML element: MD_Metadata/referenceSystemInfo/*/referenceSystemIdentifier
</pre>
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 the list provided please contact the "SDI Team":mailto:sdi@eea.europa.eu.
!34a.jpg!
h4. b) Spatial representation type
<pre>
XML element: MD_Metadata/identificationInfo/*/spatialRepresentationType
</pre>
Method used to spatially represent geographic information, based on the elements of the codelist defined in ISO 19115 MD_SpatialRepresentationTypeCode and listed [[Cataloguemetadata_guidelines#MD_MetadataidentificationInfospatialRepresentationType|here]].
!34b.jpg!
h4. c) Spatial resolution
<pre>
XML element: MD_Metadata/identificationInfo/*/spatialResolution
</pre>
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 - select "Spatial resolution (distance)") or the equivalent scale (typically for maps or map-derived products - select "Spatial resolution (scale denominator)"), 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) Keywords - Temporal resolution
<pre>
XML element: MD_Metadata/identificationInfo/*/descriptiveKeywords
</pre>
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. As the EEA Catalogue has not yet implemented the standard ISO 19115-1,the information is provided as a keyword to be selected from an already existing ISO Codelist (MaintenanceFrequencyCode), also used in the [[Cataloguemetadata_guidelines#MD_MetadataidentificationInforesourceMaintenance|resourceMaintenance]] element.
!34d.jpg!
h3. 3.5 Section “Additional technical information”
h4. a) Maintenance and update frequency
<pre>
XML element: MD_Metadata/identificationInfo/*/resourceMaintenance
</pre>
Frequency with which modifications and deletions are made to the data after it is first produced. This dataset is at least required for all datasets which are versioned. 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 [[Cataloguemetadata_guidelines#MD_MetadataidentificationInforesourceMaintenance|here]].
!35a.jpg!
h4. b) Language of dataset
<pre>
XML element: MD_Metadata/identificationInfo/*/language
</pre>
English selected by default, choose another language, if needed.
!35b.jpg!
h4. c) Distribution format
<pre>
XML element: MD_Metadata/distributionInfo/*/distributionFormat
</pre>
This element provides the format(s) in which the resource is stored and distributed. The element should be expressed by selecting the corresponding values from the list, which are derived from those used by the libraries GDAL and OGR and described [[Cataloguemetadata_guidelines#MD_MetadatadistributionInfodistributionFormat|here]]. 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
<pre>
XML element: MD_Metadata/dataQualityInfo/*/lineage
</pre>
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 (PDF file, for example), to avoid very lengthy descriptions. More detailed information is provided [[Cataloguemetadata_guidelines#MD_MetadatadataQualityInfolineage|here]].
!36a.jpg!
h4. b) Conformity
<pre>
XML element: MD_Metadata/dataQualityInfo/*/DQ_DomainConsistency/result/DQ_ConformanceResult
</pre>
Any dataset published in the EEA catalogue has to include at least a conformity statement with respect to the INSPIRE IR as regards interoperability of spatial datasets and services. The template provides already by default the values for the three elements to be filled in:
*Title*: "Commission Regulation (EU) No 1089/2010 of 23 November 2010 implementing Directive 2007/2/EC of the European Parliament and of the Council as regards interoperability of spatial data sets and services"
*Date*:"2010-12-08"
*[Degree of] conformity*: "Not evaluated"
For datasets which have been evaluated against the INSPIRE IR the degree of conformity value will have to be selected accordingly.
!36b.jpg!
h3. 3.7 Section “Resource constraints”
h4. a) Access constraints
<pre>
XML element: MD_Metadata/identificationInfo/*/resourceConstraints/*/accessConstraints
</pre>
This metadata section is used to describe Limitations on Public Access as described in the INSPIRE Metadata Regulation. This section shall include a combination of an instance of “access Constraints” element with the value of “Other Constraints” and at least one instance of “Other Constraints” element pointing to one value of the INSPIRE code list LimitationsOnPublicAccess (link http://inspire.ec.europa.eu/metadata-codelist/LimitationsOnPublicAccess). For datasets falling under EEA standard data policy, the value selected here shall be “no limitations to public access”. For datasets under different access limitations, select the appropriate value from the list. In case of doubt, please contact the SDI team.
!37a.jpg!
h4. b) Use Constraints
<pre>
XML element: MD_Metadata/identificationInfo/*/resourceConstraints/*/useConstraints
</pre>
This metadata section is used to describe the Conditions applying to access and use as described in the INSPIRE Metadata Regulation. This section shall include a combination of an instance of “use Constraints” element with the value of “Other Constraints” and at least one instance of “Other Constraints” element pointing to one value of the INSPIRE code list ConditionsApplyingToAccessAndUse (link http://inspire.ec.europa.eu/metadata-codelist/ConditionsApplyingToAccessAndUse) or to a free text element describing the terms and conditions, including where applicable the corresponding fees or an URL pointing to an online resource where these conditions are described. For datasets falling under the standard EEA access and use conditions, the following text shall be used: "EEA standard re-use policy: unless otherwise indicated, re-use of content on the EEA website for commercial or non-commercial purposes is permitted free of charge, provided that the source is acknowledged (http://www.eea.europa.eu/legal/copyright). Copyright holder: European Environment Agency (EEA)." In case of doubt, please contact the SDI team.
!37b.jpg!
h3. 3.8 Section “Responsible Party”
h4. a) Point of contact
<pre>
XML element: MD_Metadata/identificationInfo/*/pointOfContact
</pre>
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) Online resources
<pre>
XML element: MD_Metadata/distributionInfo/*/transferOptions
</pre>
This element provides the links to associated resources as described in the metadata file. The EEA metadata should include several links as indicated in the template:
* Link to the dataset file in the SDI storage server: This is an internal link and is to be added by the SDI team during the registration process.
* Link to website: When available, please add the link to the webpage where the dataset is accessible using the "WWW:LINK-1.0-http--link" protocol.
* Link to the web map service: When available, please add the HTTPS link to the WMS GetCapabilities using “OGC:WMS” protocol.
* Link to rest web services: When available, please add the HTTPS link to the ESRI Rest service using the “ESRI:REST” protocol.
Examples on how this looks like in the XML file can be found [[Cataloguemetadata_guidelines#MD_MetadatadistributionInfotransferOptions|here]].
!39a.jpg!
h4. b) Thumbnail
<pre>
XML element: MD_Metadata/distributionInfo/*/graphicOverview
</pre>
This element is providing the link to a snapshot of the whole dataset, usually in PNG format and not bigger than 1 MB. While the thumbnail needs to be provided by the data steward in the corresponding registration taskman ticket, the link in the metadata is to be added only by the SDI Team during the registration process, read more about this procedure [[EEA_SDI#3Registration-of-datasets-in-the-EEA-SDI|here]].
!39b.jpg!
h3. 3.10 Section “Validation”
h4. a) Validation
This tool includes an automated check against different standards under two options: "Validate" - an internal GNW tool that checks the compliance with the EEA metadata profile - and "TG version 2.0 - Data sets and series" - which triggers a validation of the file externally in the "INSPIRE reference validator":http://inspire.ec.europa.eu/validator/ using the relevant conformance classes under "Metadata (TG version 2.0)".
Editors can voluntarily run the first of the checks ("Validate") to ensure compliance against the EEA Metadata profile before it is sent for validation by SDI Team.
!310a.jpg!
Editors should check only the errors displayed under "EEA editor checks", which appear after clicking on the red hand.
!310b.jpg!
Each error refers to the lacking element. The validation can be run as many times as needed until the errors under "EEA editor checks" have been solved.
!310c.jpg!
h2. 4. Other functionalities of the EEA SDI editor
The SDI Editor has been implemented using GeoNetwork, and therefore it has many functionalities which are shared with the EEA internal and public catalogues. Please keep in mind that the *SDI Editor is a sandbox* to be used only to create or modify metadata records. *No final versions of the metadata are stored or maintained in the SDI Editor.*
h3. 4.1 Metadata views in editing mode
In editing mode, the metadata record is displayed in a slightly different way depending on the chosen *view*. The selection of the view can be made using the "eye" button on the upper right side.
The EEA catalogue provides four main views:
* *EEA view*: this is an EEA customised view which provides [only] access to all the descriptors of the EEA metadata profile and includes helpers to guide the editors when filling in the elements.
* *Simple view*: this is a GeoNetwork generic view which shows the all fields from the metadata file.
* *Full view*: this is an GeoNetwork generic view which provides access to all descriptors from the ISO metadata standard.
* *XML view*: this is an GeoNetwork generic view which displays the metadata as an XML document.
The EEA view is used by default when launching the edition of a record. In case you want to add more information than that required by the EEA metadata profile, you will need to switch to simple/full/XML view to edit the corresponding 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* functionality (free text search as well as the advanced filters) or click on the *“Contribute”* to visualize the list of records in EEA SDI editor (by default sorted by "modified", meaning that they are ordered from more to less recent).
!43.jpg!
h3. 4.4 Display mode of the metadata
There are three different display modes in GeoNetwork (button on the upper right):
* Default view: It provides key information of the resource, including download and links, keywords, some key technical details, data policy, lineage and contact points.
* Full view: It provides full details of the resource in five sections: identification, distribution, quality, ref. system and metadata.
* XML view: It shows the whole content of the metadata in XML format.
!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!
Go to top