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,461 to 96,480.First4,8204,8214,8224,8234,8244,8254,8264,827Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177519 PISKORY Quick edit Valid - stable 2022-08-11 PL177519
euProtectedAreaCode.PL177520 PODCERKWA Quick edit Valid - stable 2022-08-11 PL177520
euProtectedAreaCode.PL177521 PODOLANY Quick edit Valid - stable 2022-08-11 PL177521
euProtectedAreaCode.PL177522 POGORZELSKI MSZAR Quick edit Valid - stable 2022-08-11 PL177522
euProtectedAreaCode.PL177523 POLANA SIWCA Quick edit Valid - stable 2022-08-11 PL177523
euProtectedAreaCode.PL177524 POLANKI Quick edit Valid - stable 2022-08-11 PL177524
euProtectedAreaCode.PL177525 PONIKWA Quick edit Valid - stable 2022-08-11 PL177525
euProtectedAreaCode.PL177526 PONTY - D?BY Quick edit Valid - stable 2022-08-11 PL177526
euProtectedAreaCode.PL177527 PÓ?WYSEP I WYSPY NA JEZIORZE RYDZEWSKIM Quick edit Valid - stable 2022-08-11 PL177527
euProtectedAreaCode.PL177528 PR?DY Quick edit Valid - stable 2022-08-11 PL177528
euProtectedAreaCode.PL177529 PRZECINKA Quick edit Valid - stable 2022-08-11 PL177529
euProtectedAreaCode.PL177530 PRZECISZÓW Quick edit Valid - stable 2022-08-11 PL177530
euProtectedAreaCode.PL177531 SKA?KI PRZEGORZALSKIE Quick edit Valid - stable 2022-08-11 PL177531
euProtectedAreaCode.PL177532 PRZE?OM HO?UBLI Quick edit Valid - stable 2022-08-11 PL177532
euProtectedAreaCode.PL177533 PRZE?OM MIENI Quick edit Valid - stable 2022-08-11 PL177533
euProtectedAreaCode.PL177534 PRZE?OM OS?AWY POD DUSZATYNEM Quick edit Valid - stable 2022-08-11 PL177534
euProtectedAreaCode.PL177535 PRZE?OM WITÓWKI Quick edit Valid - stable 2022-08-11 PL177535
euProtectedAreaCode.PL177536 PRZE?OMY POD KSI??EM KO?O WA?BRZYCHA Quick edit Valid - stable 2022-08-11 PL177536
euProtectedAreaCode.PL177537 PRZ??LIN Quick edit Valid - stable 2022-08-11 PL177537
euProtectedAreaCode.PL177538 PRZEW?OKA Quick edit Valid - stable 2022-08-11 PL177538
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?