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
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
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

276,424 concepts found, displaying 41 to 60.First12345678Last
Id Label Status Status Modified Notation
eionetGroundWaterBodyCode.ALGW_300 ELBASAN-LUSHNJE Quick edit Valid 2021-06-17 ALGW_300
eionetGroundWaterBodyCode.ALGW_400 TIRANE-FUSHE KRUJE Quick edit Valid 2021-06-17 ALGW_400
eionetGroundWaterBodyCode.ALGW_500 KORCA Quick edit Valid 2021-06-17 ALGW_500
eionetGroundWaterBodyCode.ALGW_600 VLORE -GJIROKASTER Quick edit Valid 2021-06-17 ALGW_600
eionetGroundWaterBodyCode.ALGW_800 SARANDE Quick edit Valid 2021-06-17 ALGW_800
eionetGroundWaterBodyCode.ALGW_KARAHAXH KARAHAXH Quick edit Deprecated - retired 2021-06-17 ALGW_KARAHAXH
eionetGroundWaterBodyCode.ALGW_MURSI MURSI Quick edit Deprecated - retired 2021-06-17 ALGW_MURSI
eionetGroundWaterBodyCode.ALGW_ORIKUM ORIKUM Quick edit Deprecated - retired 2021-06-17 ALGW_ORIKUM
eionetGroundWaterBodyCode.ALGW_VRION VRION Quick edit Deprecated - retired 2021-06-17 ALGW_VRION
eionetGroundWaterBodyCode.AT001 MARCHFELD-1 Quick edit Deprecated - superseded 2021-06-17 AT001
eionetGroundWaterBodyCode.AT002 MATTIGTAL Quick edit Deprecated - retired 2021-06-17 AT002
eionetGroundWaterBodyCode.AT003 SUEDLICHES WIENER BECKEN Quick edit Deprecated - retired 2021-06-17 AT003
eionetGroundWaterBodyCode.AT004 TULLNER FELD Quick edit Deprecated - superseded 2021-06-17 AT004
eionetGroundWaterBodyCode.AT005 SEEWINKEL Quick edit Deprecated - superseded 2021-06-17 AT005
eionetGroundWaterBodyCode.AT006 UNTERES SALZACHTAL Quick edit Deprecated - superseded 2021-06-17 AT006
eionetGroundWaterBodyCode.AT007 RHEINTAL UND BREGENZERACH Quick edit Deprecated - superseded 2021-06-17 AT007
eionetGroundWaterBodyCode.AT008 JAUNFELD Quick edit Deprecated - superseded 2021-06-17 AT008
eionetGroundWaterBodyCode.AT009 INNTAL Quick edit Deprecated - superseded 2021-06-17 AT009
eionetGroundWaterBodyCode.AT010 GRAZER FELD Quick edit Deprecated - superseded 2021-06-17 AT010
eionetGroundWaterBodyCode.AT011 LEIBNITZER FELD Quick edit Deprecated - superseded 2021-06-17 AT011
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?