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 137,561 to 137,580.First6,8756,8766,8776,8786,8796,8806,8816,882Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKGBNIPA1_30020 DOWNPATRICK Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30020
euProtectedAreaCode.UKGBNIPA1_30021 RATHLIN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30021
euProtectedAreaCode.UKGBNIPA1_30022 MAGILLIGAN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30022
euProtectedAreaCode.UKGBNIPA1_30023 ARTIKELLY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30023
euProtectedAreaCode.UKGBNIPA1_30024 CLAUDY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30024
euProtectedAreaCode.UKGBNIPA1_30025 GORTIN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30025
euProtectedAreaCode.UKGBNIPA1_30026 CASTLEDERG Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30026
euProtectedAreaCode.UKGBNIPA1_30027 OMAGH Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30027
euProtectedAreaCode.UKGBNIPA1_30028 IRVINESTOWN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30028
euProtectedAreaCode.UKGBNIPA1_30029 EDERNEY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30029
euProtectedAreaCode.UKGBNIPA1_30030 PETTIGO Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30030
euProtectedAreaCode.UKGBNIPA1_30031 CRILLY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30031
euProtectedAreaCode.UKGBNIPA1_30032 BALLYSHANNON EAST Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30032
euProtectedAreaCode.UKGBNIPA1_30033 BALLYSHANNON SOUTH Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30033
euProtectedAreaCode.UKGBNIPA1_30034 BUNDORAN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30034
euProtectedAreaCode.UKGBNIPA1_30035 TULLAGHAN-LOUGH MELVIN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30035
euProtectedAreaCode.UKGBNIPA1_30036 CASTLECALDWELL FOREST Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30036
euProtectedAreaCode.UKGBNIPA1_30038 GLEN BRIDGE Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30038
euProtectedAreaCode.UKGBNIPA1_30039 BELCOO BOHO Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30039
euProtectedAreaCode.UKGBNIPA1_30042 CONAGHER FOREST Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30042
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?