You are here:
Eionet
Data Dictionary
Edit vocabulary

Edit vocabulary

Folder Mandatory
Identifier Mandatory
Label Mandatory
Base URI Optional
Registration status Mandatory
Type Mandatory Common
Numeric concept identifiers Mandatory
Optional
Definition Optional
Version Optional
Source Optional
License Optional
 

Bound elements for concepts

Element Type Status
errorType Fixed values
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 May 2023
skos:editorialNote Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:hiddenLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

612 concepts found, displaying 1 to 20.FirstPrev12345678Last
Id Label Status Status Modified Notation
1 XML must include Reporting Header  Quick edit Valid 2023-05-04 1
2 Reporting period must be reported and the envelop starting year must match the specific year within Reporing Header in the XML Quick edit Valid 2023-05-04 2
3 The following elements must be included within Reporting Header (inspire Id, reporting authority and change element) Quick edit Valid 2023-05-04 3
4 For aqd:AQD_ReportingHeader, if aqd:change='true', the following information must also be provided: aqd:AQD_ReportingHeader/aqd:changeDescription and aqd:AQD_ReportingHeader/aqd:content Quick edit Valid 2023-05-04 4
5 For aqd:AQD_ReportingHeader, if aqd:change='false', element aqd:content IS NOT expected. Quick edit Valid 2023-05-04 5
6 At least one file in the folder must be an XML with correct extension (*.xml) Quick edit Valid 2023-05-04 6
B0 Checks if this delivery is new or an update (on same reporting year) Quick edit Valid 2023-05-04 B0
B01 Number of zones reported Quick edit Valid 2023-05-04 B01
B02 Number of new zones compared to previous report.  Blocker will be returned if XML is a new delivery and localId are all new compared to previous deliveries Quick edit Valid 2023-05-04 B02
B03 Number of existing zones compared to previous report. Blocker will be returned if XML is an update delivery and localId are all new compared to previous deliveries Quick edit Valid 2023-05-04 B03
B04 List reported zones Quick edit Valid 2023-05-04 B04
B05a New zones/agglomerations for the protection of Health must link to predecessor. Quick edit Valid 2023-05-04 B05a
B05b New zones/agglomerations for the protection of vegetation should link to predecessor. Quick edit Valid 2023-05-04 B05b
B06a Number of zones that provides coordinates inside the xml via geometry element Quick edit Valid 2023-05-04 B06a
B06b Number of zones that provides coordinates via Local Administrative Units (LAU) element and external shapefile link Quick edit Valid 2023-05-04 B06b
B07 Number of unique combinations of zone types, pollutants and protection target Quick edit Valid 2023-05-04 B07
B08 Check and count expected combinations of Pollutant and ProtectionTarget Quick edit Valid 2023-05-04 B08
B09 Internal XML and INSPIRE identifiers must be unique (gml:id, base:localId) Quick edit Valid 2023-05-04 B09
B10 List unique namespaces used and count number of elements Quick edit Valid 2023-05-04 B10
B10.1 Check namespace is registered  Quick edit Valid 2023-05-04 B10.1
CSV Import

The CSV file should contain a header row for element names and data rows for concepts.
It is strongly recommended to use an exported CSV file as a template for bulk editing. Columns and rows can be added to or deleted from the template file.
A concept can be ignored by prepending a double-slash '//' to the concept row in the CSV
    Notes:
  • If the header row contains unknown elements the import will aborted and data will be rolled back
  • Erroneous concept rows are ignored, valid data rows are still imported
  • Successful import cannot be undone (unless "undo checkout" is performed)
  • If a concept with the same identifier already exists in the vocabulary it will be overwritten
  • "Purge Vocabulary" option deletes all the vocabulary concepts before import
Note
  • With this operation, contents of RDF file will be imported into vocabulary folder.
  • Only a working copy can be updated with a RDF file upload.
  • If user select "Purge Per Predicate" option. All seen predicates will be removed from vocabulary.
  • If user select "Purge All Vocabulary Data" option. All data will be removed from vocabulary.
  • Once import is successful, operation cannot be undone. If an error occurs during import, then all data will be rolled back.
In this case, existing vocabulary information will be updated with information from imported concepts.
In this case, predicates of existing concepts will be replaced with the imported predicates.
In this case, all existing concepts will be removed and the imported concepts will be added.
In this case, all imported concepts will be removed from the vocabulary.
How to handle missing concepts?