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 541 to 560.First2425262728293031Last
Id Label Status Status Modified Notation
K08 Local Ids of the Measures must be unique & not empty Quick edit Valid 2023-05-04 K08
K09 Lists unique namespaces used and counts number of elements. Quick edit Valid 2023-05-04 K09
K10 Check if namespace is registered in vocabulary (http://dd.eionet.europa.eu/vocabulary/aq/namespace/view) Quick edit Valid 2023-05-04 K10
K11 You must provide a link to a source apportionment document from data flow I via its namespace & localId. Quick edit Valid 2023-05-04 K11
K12 A link may be provided to Evaluation Scenario (J). This must be valid via namespace & localId. Quick edit Valid 2023-05-04 K12
K13 Measure code should be a unique local identifier for each measure record. For convenience the same code as localId may be used. Quick edit Valid 2023-05-04 K13
K14 You should provide a short name for the measure. Quick edit Valid 2023-05-04 K14
K15 You should provide a short description of the measure. Quick edit Valid 2023-05-04 K15
K16 Measure classification should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/measureclassification/). Quick edit Valid 2023-05-04 K16
K17 Measure type should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/measuretype/). Quick edit Valid 2023-05-04 K17
K18 Administrative level should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/administrativelevel/). Quick edit Valid 2023-05-04 K18
K19 The measure's timescale should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/timescale/). Quick edit Valid 2023-05-04 K19
K20 Information on the cost of the measure should be provided. Quick edit Valid 2023-05-04 K20
K21 The estimated total costs should be provided. If NOT an explanation on the reasons for not providing it should be included. Quick edit Valid 2023-05-04 K21
K22 If the final total costs of the measure is provided, it needs to be a number. Quick edit Valid 2023-05-04 K22
K23 The currency must be provided conforming to vocabulary (http://dd.eionet.europa.eu/vocabulary/common/currencies/), if estimated costs are provided. Quick edit Valid 2023-05-04 K23
K24 Source sector should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/sourcesectors/). Quick edit Valid 2023-05-04 K24
K25 Spatial scale should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/spatialscale/). Quick edit Valid 2023-05-04 K25
K26 Measure Implementation Status should conform to vocabulary (use http://dd.eionet.europa.eu/vocabulary/aq/measureimplementationstatus/). Quick edit Valid 2023-05-04 K26
K27 The planned start date for the measure should be provided in the right format. Quick edit Valid 2023-05-04 K27
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?