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 136,201 to 136,220.First6,8076,8086,8096,8106,8116,8126,8136,814Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SIOBC8308 JEPIHOVEC-KONJICE Quick edit Valid - stable 2025-01-29 SIOBC8308
euProtectedAreaCode.SIOBC8310 PODMEVSKOV GRABEN Quick edit Valid - stable 2025-01-29 SIOBC8310
euProtectedAreaCode.SIOBC8314 MARINKOV GRABEN 2 Quick edit Valid - stable 2025-01-29 SIOBC8314
euProtectedAreaCode.SIOBC8319 GOVCE Quick edit Valid - stable 2025-01-29 SIOBC8319
euProtectedAreaCode.SIOBC8321 BREZNO Quick edit Valid - stable 2025-01-29 SIOBC8321
euProtectedAreaCode.SIOBC8322 BELOVO Quick edit Valid - stable 2025-01-29 SIOBC8322
euProtectedAreaCode.SIOBC8323 TEVCE Quick edit Valid - stable 2025-01-29 SIOBC8323
euProtectedAreaCode.SIOBC8324 MALE GRAHOVSE Quick edit Valid - stable 2025-01-29 SIOBC8324
euProtectedAreaCode.SIOBC8325 LESKOVCA Quick edit Valid - stable 2025-01-29 SIOBC8325
euProtectedAreaCode.SIOBC8327 TRATE Quick edit Valid - stable 2025-01-29 SIOBC8327
euProtectedAreaCode.SIOBC8328 POLANA Quick edit Valid - stable 2025-01-29 SIOBC8328
euProtectedAreaCode.SIOBC8329 VOLUSKI VRH Quick edit Valid - stable 2025-01-29 SIOBC8329
euProtectedAreaCode.SIOBC8331 JURKLOSTER-SOLA Quick edit Valid - stable 2025-01-29 SIOBC8331
euProtectedAreaCode.SIOBC8332 JURKLOSTER-LOVSKI DOM Quick edit Valid - stable 2025-01-29 SIOBC8332
euProtectedAreaCode.SIOBC8333 LAHOV GRABEN Quick edit Valid - stable 2025-01-29 SIOBC8333
euProtectedAreaCode.SIOBC8334 TRIJE STUDENCI Quick edit Valid - stable 2025-01-29 SIOBC8334
euProtectedAreaCode.SIOBC8335 GLOBOCAJ Quick edit Valid - stable 2025-01-29 SIOBC8335
euProtectedAreaCode.SIOBC8336 JEPIHOVEC 3 Quick edit Valid - stable 2025-01-29 SIOBC8336
euProtectedAreaCode.SIOBC8342 JEPIHOVEC 9-10-11 Quick edit Valid - stable 2025-01-29 SIOBC8342
euProtectedAreaCode.SIOBC8352 BOROVKE 3 Quick edit Valid - stable 2025-01-29 SIOBC8352
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?