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,541 to 137,560.First6,8746,8756,8766,8776,8786,8796,8806,881Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UKGBNIPA1_10036 RATHLIN ISLAND Quick edit Valid - stable 2025-01-29 UKGBNIPA1_10036
euProtectedAreaCode.UKGBNIPA1_10037 SEAGHAN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_10037
euProtectedAreaCode.UKGBNIPA1_30001 COLERAINE KILREA Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30001
euProtectedAreaCode.UKGBNIPA1_30002 BALLYMENA Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30002
euProtectedAreaCode.UKGBNIPA1_30003 COOKSTOWN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30003
euProtectedAreaCode.UKGBNIPA1_30004 MONEYMORE Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30004
euProtectedAreaCode.UKGBNIPA1_30005 ANTRIM Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30005
euProtectedAreaCode.UKGBNIPA1_30006 MOYGASHEL Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30006
euProtectedAreaCode.UKGBNIPA1_30007 AUGHNACLOY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30007
euProtectedAreaCode.UKGBNIPA1_30008 TANDRAGEE Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30008
euProtectedAreaCode.UKGBNIPA1_30009 NEWRY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30009
euProtectedAreaCode.UKGBNIPA1_30010 KEADY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30010
euProtectedAreaCode.UKGBNIPA1_30011 MONAGHAN TOWN Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30011
euProtectedAreaCode.UKGBNIPA1_30012 KNOCKATALLON Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30012
euProtectedAreaCode.UKGBNIPA1_30013 LOUTH Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30013
euProtectedAreaCode.UKGBNIPA1_30014 BALLYCASTLE ARMOY Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30014
euProtectedAreaCode.UKGBNIPA1_30015 FAIRHEAD Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30015
euProtectedAreaCode.UKGBNIPA1_30016 GLENARIFF Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30016
euProtectedAreaCode.UKGBNIPA1_30017 BELFAST HILLS ISLAND MAGEE Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30017
euProtectedAreaCode.UKGBNIPA1_30019 ARDS PENINSULA Quick edit Valid - stable 2025-01-29 UKGBNIPA1_30019
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?