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 521 to 540.First2324252627282930Last
Id Label Status Status Modified Notation
J26 The number of exceecedance expected (under baseline scenario) should be provided as an integer Quick edit Valid 2023-05-04 J26
J27 Measures identified in the AQ Plan that are included in this baseline scenario should be provided (link to dataflow K). Quick edit Valid 2023-05-04 J27
J28 A description of the emission scenario used for the projection analysis should be provided as text. Quick edit Valid 2023-05-04 J28
J29 The projection total emissions should be provided as integer with correct unit. Quick edit Valid 2023-05-04 J29
J3 Number of existing EvaluationScenarios compared to previous report. ERROR 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 J3
J30 The expected concentration (under projection scenario) should be provided as an integer and its unit should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/uom/concentration/). Quick edit Valid 2023-05-04 J30
J31 The number of exceecedance expected (under projection scenario) should be provided as an integer a Quick edit Valid 2023-05-04 J31
J32 Measures identified in the AQ Plan that are included in this projection should be provided (link to dataflow K). Quick edit Valid 2023-05-04 J32
J4 List of unique identifier information for all EvaluationScenarios records. It returns BLOCKER if no EvaluationScenarios are provided Quick edit Valid 2023-05-04 J4
J7 All gml ID attributes shall have unique code. Quick edit Valid 2023-05-04 J7
J8 Local Ids of the EvaluationScenarios must be unique & not empty Quick edit Valid 2023-05-04 J8
J9 Lists unique namespaces and counts number of elements. Quick edit Valid 2023-05-04 J9
K0 Check if delivery if this is a new delivery or updated delivery (via reporting year) Quick edit Valid 2023-05-04 K0
K01 Compile & feedback upon the total number of Measures included in the delivery Quick edit Valid 2023-05-04 K01
K02 Number of new Measures compared to previous report. ERROR will be returned if XML is a new delivery and localId are not new compared to previous deliveries. Quick edit Valid 2023-05-04 K02
K03 Number of existing Measures compared to previous report. ERROR 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 K03
K04 List of unique identifier information for all Measures records. It returns ERROR if no Measures are reported. Quick edit Valid 2023-05-04 K04
K05 reserved Quick edit Valid 2023-05-04 K05
K06 reserved Quick edit Valid 2023-05-04 K06
K07 All gml ID attributes shall have unique code. Quick edit Valid 2023-05-04 K07
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?