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 581 to 600.First2627282930313233Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA743 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA743
euProtectedAreaCode.ATPA744 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA744
euProtectedAreaCode.ATPA745 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA745
euProtectedAreaCode.ATPA746 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA746
euProtectedAreaCode.ATPA747 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA747
euProtectedAreaCode.ATPA748 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA748
euProtectedAreaCode.ATPA749 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA749
euProtectedAreaCode.ATPA75 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA75
euProtectedAreaCode.ATPA750 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA750
euProtectedAreaCode.ATPA751 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA751
euProtectedAreaCode.ATPA755 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA755
euProtectedAreaCode.ATPA76 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA76
euProtectedAreaCode.ATPA77 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA77
euProtectedAreaCode.ATPA78 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA78
euProtectedAreaCode.ATPA79 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA79
euProtectedAreaCode.ATPA8 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA8
euProtectedAreaCode.ATPA81 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA81
euProtectedAreaCode.ATPA89 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA89
euProtectedAreaCode.ATPA9 NO INTERNATIONAL NAME Quick edit Valid - stable 2025-01-29 ATPA9
euProtectedAreaCode.ATPA91 NO INTERNATIONAL NAME Quick edit Deprecated 2025-01-29 ATPA91
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?