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 541 to 560.First2425262728293031Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA7 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA7
euProtectedAreaCode.ATPA70 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA70
euProtectedAreaCode.ATPA701 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA701
euProtectedAreaCode.ATPA702 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA702
euProtectedAreaCode.ATPA703 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA703
euProtectedAreaCode.ATPA704 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA704
euProtectedAreaCode.ATPA705 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA705
euProtectedAreaCode.ATPA706 NO INTERNATIONAL NAME Quick edit Deprecated 2025-01-29 ATPA706
euProtectedAreaCode.ATPA707 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA707
euProtectedAreaCode.ATPA708 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA708
euProtectedAreaCode.ATPA709 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA709
euProtectedAreaCode.ATPA71 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA71
euProtectedAreaCode.ATPA710 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA710
euProtectedAreaCode.ATPA711 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA711
euProtectedAreaCode.ATPA712 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA712
euProtectedAreaCode.ATPA713 NO INTERNATIONAL NAME Quick edit Deprecated 2025-01-29 ATPA713
euProtectedAreaCode.ATPA715 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA715
euProtectedAreaCode.ATPA716 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA716
euProtectedAreaCode.ATPA717 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA717
euProtectedAreaCode.ATPA722 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA722
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?