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
 

Vocabulary concepts

106,312 concepts found, displaying 96,941 to 96,960.First4,8444,8454,8464,8474,8484,8494,8504,851Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL396232 NAD JEZIOREM MYCZKOWIECKIM Quick edit Valid - stable 2022-08-11 PL396232
euProtectedAreaCode.PL396233 NAD P?OCICZN? Quick edit Valid - stable 2022-08-11 PL396233
euProtectedAreaCode.PL396234 NADMORSKI BÓR BA?YNOWY W MRZEZYNIE Quick edit Valid - stable 2022-08-11 PL396234
euProtectedAreaCode.PL396235 NADMORSKI BÓR STORCZYKOWY Quick edit Valid - stable 2022-08-11 PL396235
euProtectedAreaCode.PL396236 NIETLICKIE BAGNO Quick edit Valid - stable 2022-08-11 PL396236
euProtectedAreaCode.PL396237 NOWINKA Quick edit Valid - stable 2022-08-11 PL396237
euProtectedAreaCode.PL396238 OKR?GLAK Quick edit Valid - stable 2022-08-11 PL396238
euProtectedAreaCode.PL396239 OSETNO Quick edit Valid - stable 2022-08-11 PL396239
euProtectedAreaCode.PL396240 PANIE?SKA GÓRA Quick edit Valid - stable 2022-08-11 PL396240
euProtectedAreaCode.PL396241 PAZUREK Quick edit Valid - stable 2022-08-11 PL396241
euProtectedAreaCode.PL396242 PODJAB?O?SKIE Quick edit Valid - stable 2022-08-11 PL396242
euProtectedAreaCode.PL396243 POLDER S?TOPY-SAMULEWO Quick edit Valid - stable 2022-08-11 PL396243
euProtectedAreaCode.PL396244 PRZE?OM OS?AWY POD MOKREM Quick edit Valid - stable 2022-08-11 PL396244
euProtectedAreaCode.PL396245 PRZE?OM RZEKI D?BNICY Quick edit Valid - stable 2022-08-11 PL396245
euProtectedAreaCode.PL396246 PRZE?OM SANU POD GRODZISKIEM Quick edit Valid - stable 2022-08-11 PL396246
euProtectedAreaCode.PL396247 PRZYBIERNOWSKI BÓR BAGIENNY Quick edit Valid - stable 2022-08-11 PL396247
euProtectedAreaCode.PL396248 RABINÓWKA Quick edit Valid - stable 2022-08-11 PL396248
euProtectedAreaCode.PL396249 REZERWAT SKALNY IM. JANA CZARNOCKIEGO Quick edit Valid - stable 2022-08-11 PL396249
euProtectedAreaCode.PL396250 ROBY Quick edit Valid - stable 2022-08-11 PL396250
euProtectedAreaCode.PL396251 BAGNO KUSOWO Quick edit Valid - stable 2022-08-11 PL396251
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?