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 581 to 600.First2627282930313233Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA275W TB SCHWAZ OST Quick edit Deprecated - superseded 2022-08-11 ATPA275W
euProtectedAreaCode.ATPA27W HAAGER RÜCKEN Quick edit Deprecated - superseded 2022-08-11 ATPA27W
euProtectedAreaCode.ATPA28 STADL-PAURA Quick edit Valid - stable 2022-08-11 ATPA28
euProtectedAreaCode.ATPA28W STADL-PAURA Quick edit Deprecated - superseded 2022-08-11 ATPA28W
euProtectedAreaCode.ATPA29 KÖNIGSWIESEN Quick edit Valid - stable 2022-08-11 ATPA29
euProtectedAreaCode.ATPA3 NEUFELD Quick edit Valid - stable 2022-08-11 ATPA3
euProtectedAreaCode.ATPA30 JAUNITZTAL- FREISTADT Quick edit Valid - stable 2022-08-11 ATPA30
euProtectedAreaCode.ATPA31 NÖRDLICHES EFERDINGER BECKEN Quick edit Valid - stable 2022-08-11 ATPA31
euProtectedAreaCode.ATPA31W NÖRDLICHES EFERDINGER BECKEN Quick edit Deprecated - superseded 2022-08-11 ATPA31W
euProtectedAreaCode.ATPA32 SAUWALD Quick edit Valid - stable 2022-08-11 ATPA32
euProtectedAreaCode.ATPA32W SAUWALD Quick edit Deprecated - superseded 2022-08-11 ATPA32W
euProtectedAreaCode.ATPA33 AURACHRINNE Quick edit Valid - stable 2022-08-11 ATPA33
euProtectedAreaCode.ATPA34 BAD GOISERN UND GOSAU Quick edit Valid - stable 2022-08-11 ATPA34
euProtectedAreaCode.ATPA35 SCHWANENSTADT Quick edit Valid - stable 2022-08-11 ATPA35
euProtectedAreaCode.ATPA36 RANDRINNE Quick edit Valid - stable 2022-08-11 ATPA36
euProtectedAreaCode.ATPA36W RANDRINNE Quick edit Deprecated - superseded 2022-08-11 ATPA36W
euProtectedAreaCode.ATPA37 BAD ISCHL Quick edit Valid - stable 2022-08-11 ATPA37
euProtectedAreaCode.ATPA37W BAD ISCHL Quick edit Deprecated - superseded 2022-08-11 ATPA37W
euProtectedAreaCode.ATPA38 ZIRKING Quick edit Valid - stable 2022-08-11 ATPA38
euProtectedAreaCode.ATPA38W ZIRKING Quick edit Deprecated - superseded 2022-08-11 ATPA38W
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?