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 81 to 100.First12345678Last
Id Label Status Status Modified Notation
eionetSubUnitCode.BEOI OISE Quick edit Deprecated 2019-09-10 BEOI
eionetSubUnitCode.BEOU OURTHE Quick edit Deprecated 2019-09-10 BEOU
eionetSubUnitCode.BESA SAMBRE Quick edit Deprecated 2019-09-10 BESA
eionetSubUnitCode.BESC SEMOIS-CHIERS Quick edit Deprecated 2019-09-10 BESC
eionetSubUnitCode.BESE SENNE Quick edit Deprecated 2019-09-10 BESE
eionetSubUnitCode.BEVE VESDRE Quick edit Deprecated 2019-09-10 BEVE
eionetSubUnitCode.CH10 RHINE Quick edit Deprecated - superseded 2019-09-10 CH10
eionetSubUnitCode.CH1001 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1001
eionetSubUnitCode.CH1002 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1002
eionetSubUnitCode.CH1003 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1003
eionetSubUnitCode.CH1004 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1004
eionetSubUnitCode.CH1005 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1005
eionetSubUnitCode.CH1006 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1006
eionetSubUnitCode.CH1007 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1007
eionetSubUnitCode.CH1008 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1008
eionetSubUnitCode.CH1009 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH1009
eionetSubUnitCode.CH1010 REZGUS Quick edit Deprecated 2019-09-10 CH1010
eionetSubUnitCode.CH10_INTL UNKNOWN Quick edit Deprecated - superseded 2019-09-10 CH10_INTL
eionetSubUnitCode.CH50 RHONE Quick edit Deprecated - superseded 2019-09-10 CH50
eionetSubUnitCode.CH5001 UNKNOWN Quick edit Deprecated - retired 2019-09-10 CH5001
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?