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
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

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

729 concepts found, displaying 401 to 420.First1718192021222324Last
Id Label Status Status Modified Notation
euSubUnitCode.DE2600 MOSEL/SAAR Quick edit Valid - stable 2019-09-10 DE2600
euSubUnitCode.DE2700 MITTELRHEIN Quick edit Valid - stable 2019-09-10 DE2700
euSubUnitCode.DE2800 NIEDERRHEIN Quick edit Valid - stable 2019-09-10 DE2800
euSubUnitCode.DE2900 DELTARHEIN Quick edit Valid - stable 2019-09-10 DE2900
euSubUnitCode.DE3100_3500_3600 OBERE EMS, EMS/NORDRADDE, HASE Quick edit Valid - stable 2019-09-10 DE3100_3500_3600
euSubUnitCode.DE3800_3900_3990 LEDA-JÜMME, UNTERE EMS, EMS-ÄSTUAR Quick edit Valid - stable 2019-09-10 DE3800_3900_3990
euSubUnitCode.DE4100 WERRA Quick edit Valid - stable 2019-09-10 DE4100
euSubUnitCode.DE4200 FULDA Quick edit Valid - stable 2019-09-10 DE4200
euSubUnitCode.DE4500 WESER Quick edit Valid - stable 2019-09-10 DE4500
euSubUnitCode.DE4800 ALLER Quick edit Valid - stable 2019-09-10 DE4800
euSubUnitCode.DE4880 LEINE Quick edit Valid - stable 2019-09-10 DE4880
euSubUnitCode.DE4900 TIDE-WESER Quick edit Valid - stable 2019-09-10 DE4900
euSubUnitCode.DE5400 MULDE-ELBE-SCHWARZE ELSTER Quick edit Valid - stable 2019-09-10 DE5400
euSubUnitCode.DE5600_5210_5240_5300 SAALE, OBERE MOLDAU, BEROUNKA, EGER UND UNTERE ELBE Quick edit Valid - stable 2019-09-10 DE5600_5210_5240_5300
euSubUnitCode.DE5700 MITTLERE ELBE/ELDE Quick edit Valid - stable 2019-09-10 DE5700
euSubUnitCode.DE5800 HAVEL Quick edit Valid - stable 2019-09-10 DE5800
euSubUnitCode.DE5900 TIDEELBE Quick edit Valid - stable 2019-09-10 DE5900
euSubUnitCode.DE6000 ODER Quick edit Valid - stable 2019-09-10 DE6000
euSubUnitCode.DE7000 MAAS Quick edit Valid - stable 2019-09-10 DE7000
euSubUnitCode.DE9500 EIDER Quick edit Valid - stable 2019-09-10 DE9500
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?