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
29 Oct 2015
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 (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

99,985 concepts found, displaying 98,341 to 98,360.First4,9144,9154,9164,9174,9184,9194,9204,921Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SKREK023 ZEMPLINSKA SIRAVA - BIELA HORA Quick edit Valid - stable 2019-11-05 SKREK023
euProtectedAreaCode.SKREK024 ZEMPLINSKA SIRAVA - HORKA Quick edit Valid - stable 2019-11-05 SKREK024
euProtectedAreaCode.SKREK025 VINIANSKE JAZERO Quick edit Valid - stable 2019-11-05 SKREK025
euProtectedAreaCode.SKREK026 ZEMPLINSKA SIRAVA - MEDVEDIA HORA Quick edit Valid - stable 2019-11-05 SKREK026
euProtectedAreaCode.SKREK027 ZEMPLINSKA SIRAVA - KAMENEC Quick edit Valid - stable 2019-11-05 SKREK027
euProtectedAreaCode.SKREK028 ZEMPLINSKA SIRAVA - PALKOV Quick edit Valid - stable 2019-11-05 SKREK028
euProtectedAreaCode.SKREK029 ZLATE PIESKY Quick edit Valid - stable 2019-11-05 SKREK029
euProtectedAreaCode.SKREK030 IVANKA PRI DUNAJI Quick edit Valid - stable 2019-11-05 SKREK030
euProtectedAreaCode.SKREK031 VE?KÝ DRAŽDIAK Quick edit Deprecated 2021-07-16 SKREK031
euProtectedAreaCode.SKREK032 SLNECNE JAZERA Quick edit Valid - stable 2019-11-05 SKREK032
euProtectedAreaCode.SKREK033 TONA Quick edit Deprecated 2021-07-16 SKREK033
euProtectedAreaCode.SKREK034 VOJ?IANSKE JAZERO Quick edit Deprecated 2021-07-16 SKREK034
euProtectedAreaCode.SKREK035 SULIANSKE JAZERO Quick edit Valid - stable 2019-11-05 SKREK035
euProtectedAreaCode.SKREK036 VAJNORSKE JAZERO Quick edit Valid - stable 2019-11-05 SKREK036
euProtectedAreaCode.SKREK037 PLAZ ORMET Quick edit Valid - stable 2019-11-05 SKREK037
euProtectedAreaCode.SKREK038 VELKA DOMASA - NOVA KELCA - POLOOSTROV KRYM Quick edit Valid - stable 2019-11-05 SKREK038
euProtectedAreaCode.SKS01 SLOVAK REPUBLIC Quick edit Valid - stable 2019-11-05 SKS01
euProtectedAreaCode.UK03600 SPITTAL Quick edit Valid - stable 2019-11-05 UK03600
euProtectedAreaCode.UK03700 BAMBURGH CASTLE Quick edit Valid - stable 2019-11-05 UK03700
euProtectedAreaCode.UK03800 SEAHOUSES NORTH Quick edit Valid - stable 2019-11-05 UK03800
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?