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 421 to 440.First1819202122232425Last
Id Label Status Status Modified Notation
G95 An attainment for PM2.5 Exposure concentration obligationMUST be provided, it is has to be unique and the exceedance value reported via a unique element numericalExceedance. The reported AEI CANNOT be 0. Quick edit Valid 2023-05-04 G95
G96 An attainment for PM2.5 Exposure Reduction Target SHOULD be provided, it is has to be unique and the exceedance value reported via a unique element numericalExceedance. The reported AEI CANNOT be 0. Quick edit Valid 2023-05-04 G96
G97 Check PM2.5 Compliance against National Exposure Reduction Target Quick edit Valid 2023-05-04 G97
G99 Check if at least one of the following combinations is reported (O3-INT, O3-ALT, NO2-ALT & SO2-ALT) Quick edit Valid 2023-05-19 G99
GCrossCheck Cross checks with other data-flows Quick edit Valid 2023-05-04 GCrossCheck
H0 Check if delivery if this is a new delivery or updated delivery (via reporting year) Quick edit Valid 2023-05-04 H0
H01 Compile & feedback upon the total number of plans records included in the delivery Quick edit Valid 2023-05-04 H01
H02 Compile & feedback upon the total number of new plans records included in the delivery (compared to any delivery for the same reporting year) Quick edit Valid 2023-05-04 H02
H03 Compile & feedback upon the total number of updated plans records included in the delivery. BLOCKER will be returned if XML is an update and ALL localId (100%) are different to previous delivery (for the same YEAR). Quick edit Valid 2023-05-04 H03
H04 List of unique identifier information for all Plan records. Error will be returned if no Plans are reported. Quick edit Valid 2023-05-04 H04
H05 Your plan should be for an expected pollutant and correctly use one of pollutants listed at http://dd.eionet.europa.eu/vocabulary/aq/pollutant/ Quick edit Valid 2023-05-04 H05
H06 Reserved Quick edit Valid 2023-05-04 H06
H07 All gml ID attributes shall have unique code. Quick edit Valid 2023-05-04 H07
H08 Local Id of the Plans must be unique. Quick edit Valid 2023-05-04 H08
H09 List unique namespaces used and count number of elements. Quick edit Valid 2023-05-04 H09
H10 Check if namespace is registered in vocabulary (http://dd.eionet.europa.eu/vocabulary/aq/namespace/view) Quick edit Valid 2023-05-04 H10
H11 AQ Plan must link to a valid exceedance situation (G) Quick edit Valid 2023-05-04 H11
H12 aqd:comment should be provided if reporting period before than 2013 and a valid exceedande situation is not provided. Quick edit Valid 2023-05-04 H12
H13 Reserved Quick edit Valid 2023-05-04 H13
H15 aqd:code must be populated & unique within the XML Quick edit Valid 2023-05-04 H15
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?