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 501 to 520.First2223242526272829Last
Id Label Status Status Modified Notation
I8 Local Id of the Source Apportionments must be unique. Quick edit Valid 2023-05-04 I8
I9 List unique namespaces and count number of elements. Quick edit Valid 2023-05-04 I9
J0 Check if delivery if this is a new delivery or updated delivery (via reporting year) Quick edit Valid 2023-05-04 J0
J1 Number of AQ Scenarios reported Quick edit Valid 2023-05-04 J1
J10 Check if namespace is registered in vocabulary (http://dd.eionet.europa.eu/vocabulary/aq/namespace/view) Quick edit Valid 2023-05-04 J10
J11 You must provide a reference to a plan document from data flow H via its namespace & localId. The plan document must have the same reporting year as the scenario document. Quick edit Valid 2023-05-04 J11
J12 You must provide a link to a Source Apportionment (I) document from data flow I via its namespace & localId (for the same reporting year). Quick edit Valid 2023-05-04 J12
J13 A code of the scenario should be provided as an alpha-numeric code starting with the country ISO code. Quick edit Valid 2023-05-04 J13
J14 Short textul description of the publication should be provided. Include the ISBN number if available. Quick edit Valid 2023-05-04 J14
J15 You should provide title as written in the publication. Quick edit Valid 2023-05-04 J15
J16 Author(s) should be provided as text (Please provide in one field separated by commas if there are multiple authors). Quick edit Valid 2023-05-04 J16
J17 The publication date should be provided in yyyy or yyyy-mm-dd format. Quick edit Valid 2023-05-04 J17
J18 Publisher should be provided as a text (Publishing institution / academic journal / etc.) Quick edit Valid 2023-05-04 J18
J19 Url to the published AQ Scenario should be valid (if provided). Quick edit Valid 2023-05-04 J19
J2 Number of new EvaluationScenarios compared to previous report. Quick edit Valid 2023-05-04 J2
J20 The year for which the projections are developed must be provided and the yyyy format must be used. Quick edit Valid 2023-05-04 J20
J21 Reference year from which the projections started and for which the scenario is available must be provided and must conform to yyyy format. Quick edit Valid 2023-05-04 J21
J23 A description of the emission scenario used for the baseline analysis should be provided as text. Quick edit Valid 2023-05-04 J23
J24 The baseline total emissions should be provided as integer with correct unit. Quick edit Valid 2023-05-04 J24
J25 The expected concentration (under baseline 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 J25
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?