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 441 to 460.First1920212223242526Last
Id Label Status Status Modified Notation
H16 You must provide the name of the organisation responsible for the Plan. Quick edit Valid 2023-05-04 H16
H17 You should provide a contact point within the organisation responsible for the plan. This should be a generic contact point. Quick edit Valid 2023-05-04 H17
H18 You should provide an email address for the contact point within the organisation responsible for the plan (This should be a generic email address). Quick edit Valid 2023-05-04 H18
H19 Your reference year must be in yyyy format. Quick edit Valid 2023-05-04 H19
H20 Your plan status should use one of those listed at http://dd.eionet.europa.eu/vocabulary/aq/statusaqplan/ Quick edit Valid 2023-05-04 H20
H21 Your plan should use one of pollutants listed at http://dd.eionet.europa.eu/vocabulary/aq/pollutant/ Quick edit Valid 2023-05-04 H21
H22 Your plan should use one of protection targets listed at http://dd.eionet.europa.eu/vocabulary/aq/protectiontarget/ Quick edit Valid 2023-05-04 H22
H23 Check and count expected combinations of Pollutant and ProtectionTarget. Quick edit Valid 2023-05-04 H23
H24 AQ plan pollutant's should match those in the exceedance situation (G). Quick edit Valid 2023-05-04 H24
H25 Your reference year must be in yyyy-mm-dd format. Quick edit Valid 2023-05-04 H25
H26 Plan adoption date should not be populated if plan is in preparation, under revision or in adoption process. Quick edit Valid 2023-05-04 H26
H27 You should report a short textual description of timetable for the implementation of the air quality plan. Quick edit Valid 2023-05-04 H27
H28 You should report a URL to document or web resource describing the last version of full air quality plan. Quick edit Valid 2023-05-04 H28
H29 You should report a URL to a document or web resource where information about the implementation of the air quality plan can be found. Quick edit Valid 2023-05-04 H29
H30 Brief textual description of the published AQ Plan should be provided. Include the ISBN number (If available) Quick edit Valid 2023-05-04 H30
H31 You should provide title as written in the published AQ Plan. Quick edit Valid 2023-05-04 H31
H32 Author information for the AQ Plan report - multiple entries can be provided as a comma separate list. Quick edit Valid 2023-05-04 H32
H33 The publication date of the AQ Plan should be provided in yyyy or yyyy-mm-dd format Quick edit Valid 2023-05-04 H33
H34 Publisher should be provided as a text (Publishing institution - academic jourmal – etc.) Quick edit Valid 2023-05-04 H34
H35 Provided url to the published AQ Plan should be valid. Quick edit Valid 2023-05-04 H35
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?