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,381 to 96,400.First4,8164,8174,8184,8194,8204,8214,8224,823Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177432 KÓZKI Quick edit Valid - stable 2022-08-11 PL177432
euProtectedAreaCode.PL177433 KU?NIE Quick edit Valid - stable 2022-08-11 PL177433
euProtectedAreaCode.PL177434 KWA?NA BUCZYNA Quick edit Valid - stable 2022-08-11 PL177434
euProtectedAreaCode.PL177435 KWIDZY?SKIE OSTNICE Quick edit Valid - stable 2022-08-11 PL177435
euProtectedAreaCode.PL177436 LAS BUKOWY Quick edit Valid - stable 2022-08-11 PL177436
euProtectedAreaCode.PL177437 LAS GO?CIBIA Quick edit Valid - stable 2022-08-11 PL177437
euProtectedAreaCode.PL177439 LAS JAB?ONIOWY Quick edit Valid - stable 2022-08-11 PL177439
euProtectedAreaCode.PL177440 LAS KRÓLEWSKI Quick edit Valid - stable 2022-08-11 PL177440
euProtectedAreaCode.PL177441 LAS ?AGIEWNICKI Quick edit Valid - stable 2022-08-11 PL177441
euProtectedAreaCode.PL177442 LAS LI?CIASTY W PROMNIE Quick edit Valid - stable 2022-08-11 PL177442
euProtectedAreaCode.PL177443 LAS NAD JEZIOREM M?DRZECHOWSKIM Quick edit Valid - stable 2022-08-11 PL177443
euProtectedAreaCode.PL177444 LAS ZWIERZYNIECKI Quick edit Valid - stable 2022-08-11 PL177444
euProtectedAreaCode.PL177445 LASY RAD?OWSKIE Quick edit Valid - stable 2022-08-11 PL177445
euProtectedAreaCode.PL177446 ?ACHY BRZESKIE Quick edit Valid - stable 2022-08-11 PL177446
euProtectedAreaCode.PL177447 ?AWICE KIE?PI?SKIE Quick edit Valid - stable 2022-08-11 PL177447
euProtectedAreaCode.PL177448 ?AWICE TROSZY?SKIE Quick edit Valid - stable 2022-08-11 PL177448
euProtectedAreaCode.PL177449 ?AWSKI LAS I Quick edit Valid - stable 2022-08-11 PL177449
euProtectedAreaCode.PL177450 ?AWSKI LAS II Quick edit Valid - stable 2022-08-11 PL177450
euProtectedAreaCode.PL177451 ??G KOREA Quick edit Valid - stable 2022-08-11 PL177451
euProtectedAreaCode.PL177452 ??GACZ NAD JEZIORK? Quick edit Valid - stable 2022-08-11 PL177452
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?