You are here:
Eionet
Data Dictionary
Edit vocabulary

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
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

138,256 concepts found, displaying 461 to 480.First2021222324252627Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA185 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA185
euProtectedAreaCode.ATPA188 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA188
euProtectedAreaCode.ATPA19 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA19
euProtectedAreaCode.ATPA191 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA191
euProtectedAreaCode.ATPA195 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA195
euProtectedAreaCode.ATPA199 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA199
euProtectedAreaCode.ATPA2 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA2
euProtectedAreaCode.ATPA20 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA20
euProtectedAreaCode.ATPA201 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA201
euProtectedAreaCode.ATPA205 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA205
euProtectedAreaCode.ATPA207 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA207
euProtectedAreaCode.ATPA208 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA208
euProtectedAreaCode.ATPA21 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA21
euProtectedAreaCode.ATPA212 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA212
euProtectedAreaCode.ATPA213 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA213
euProtectedAreaCode.ATPA215 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA215
euProtectedAreaCode.ATPA216 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA216
euProtectedAreaCode.ATPA217 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA217
euProtectedAreaCode.ATPA218 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA218
euProtectedAreaCode.ATPA219 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA219
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?