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 621 to 640.First2829303132333435Last
Id Label Status Status Modified Notation
euSubUnitCode.NO5105 HORDALAND Quick edit Valid - stable 2019-09-10 NO5105
euSubUnitCode.NO5106 SOGN OG FJORDANE Quick edit Valid - stable 2019-09-10 NO5106
euSubUnitCode.NOFIVHA5 KEMIJOKI Quick edit Deprecated - superseded 2019-09-10 NOFIVHA5
euSubUnitCode.NOFIVHA6 TORNIONJOKI Quick edit Deprecated - superseded 2019-09-10 NOFIVHA6
euSubUnitCode.NOSE1 BOTHNIAN BAY Quick edit Deprecated - superseded 2019-09-10 NOSE1
euSubUnitCode.NOSE1TO BOTHNIAN BAY (INTERNATIONAL DISTRICT TORNE RIVER - NORWAY) Quick edit Deprecated - superseded 2019-09-10 NOSE1TO
euSubUnitCode.NOSE2 BOTHNIAN SEA Quick edit Deprecated - superseded 2019-09-10 NOSE2
euSubUnitCode.NOSE5 SKAGERRAK AND KATTEGAT Quick edit Deprecated - superseded 2019-09-10 NOSE5
euSubUnitCode.NOVHA5 KEMIJOKI Quick edit Valid - stable 2019-09-10 NOVHA5
euSubUnitCode.NOVHA6 TORNIONJOKI Quick edit Valid - stable 2019-09-10 NOVHA6
euSubUnitCode.PL1000 DANUBE RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL1000
euSubUnitCode.PL2000 VISTULA RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL2000
euSubUnitCode.PL3000 SWIEZA RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL3000
euSubUnitCode.PL4000 JARFT RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL4000
euSubUnitCode.PL5000 RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL5000
euSubUnitCode.PL6000 ODER RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL6000
euSubUnitCode.PL6700 ÜCKER RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL6700
euSubUnitCode.PL7000 PREGOLYA RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL7000
euSubUnitCode.PL8000 NEMUNAS RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL8000
euSubUnitCode.PL9000 DNIESTER RIVER BASIN DISTRICT Quick edit Valid - stable 2019-09-10 PL9000
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?