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
skos:broadMatch 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

88 concepts found, displaying 1 to 20.FirstPrev12345Last
Id Label Status Status Modified Notation
CW-BC1 Baltic Sea, surface water salinity 0.5-6 psu, bottom water salinity 1-6 psu, Exposed, 90-150 ice days Quick edit Valid 2016-02-17 CW-BC1
CW-BC3 Baltic Sea, surface water salinity 3-6 psu, bottom water salinity 3-6 psu, Sheltered, 90-150 ice days Quick edit Valid 2016-02-17 CW-BC3
CW-BC4 Baltic Sea, surface water salinity 5-8 psu, bottom water salinity 5-8 psu, Exposed, < 90 ice days Quick edit Valid 2016-02-17 CW-BC4
CW-BC5 Baltic Sea, surface water salinity 6-8 psu, bottom water salinity 6-12 psu, Exposed, <90 ice days Quick edit Valid 2016-02-17 CW-BC5
CW-BC6 Baltic Sea, surface water salinity 8-12 psu, bottom water salinity 8-12 psu, Sheltered, <90 ice days Quick edit Valid 2016-02-17 CW-BC6
CW-BC7 Baltic Sea, surface water salinity 6-8 psu, bottom water salinity 8-11 psu, Exposed, <90 ice days Quick edit Valid 2016-02-17 CW-BC7
CW-BC8 Baltic Sea, surface water salinity 13-18 psu, bottom water salinity 18-23 psu, Sheltered,<90 ice days Quick edit Valid 2016-02-17 CW-BC8
CW-BC9 Baltic Sea, surface water salinity 3-6 psu, bottom water salinity 3-6 psu, Moderately Exposed to exposed, 90-150 ice days Quick edit Valid 2016-02-17 CW-BC9
CW-BL1 Black Sea, mesohaline, microtidal, shallow, moderately exposed, mixed substratum Quick edit Valid 2016-02-17 CW-BL1
CW-NEA10 Skagerrak Outer Arc Type, polyhaline, microtidal, exposed, deep Quick edit Valid 2016-02-17 CW-NEA10
CW-NEA1_26 North East Atlantic, open oceanic or enclosed seas, exposed or sheltered, euhaline, shallow (< 30 m), microtidal or mesotidal, fully mixed or partly stratified Quick edit Valid 2016-02-17 CW-NEA1/26
CW-NEA3_4 North East Atlantic, polyhaline, exposed or moderately exposed (Wadden Sea type) Quick edit Valid 2016-02-17 CW-NEA3/4
CW-NEA7 North East, Atlantic Sea, deep fjordic and sea loch systems Quick edit Valid 2016-02-17 CW-NEA7
CW-NEA8a North East Atlantic, Skagerrak Inner Arc Type, polyhaline (25-30), microtidal, moderately exposed, shallow, fully mixed Quick edit Valid 2016-02-17 CW-NEA8a
CW-NEA8b North East Atlantic, Skagerrak Inner Arc Type, polyhaline (10-30), microtidal, moderately sheltered, shallow, partly stratified Quick edit Valid 2016-02-17 CW-NEA8b
CW-NEA9 North East Atlantic, fjord with a shallow sill at the mouth with very deep maximum depth in the central basin with poor deepwater exchange Quick edit Valid 2016-02-17 CW-NEA9
CW-Type_I Mediterranean, highly influenced by freshwater input Quick edit Valid 2016-02-17 CW-Type_I
CW-Type_IIA Mediterranean, moderately influenced by freshwater input (continent influence) Quick edit Valid 2016-02-17 CW-Type_IIA
CW-Type_IIA_Adriatic Mediterranean, moderately influenced by freshwater input (continent influence), Adriatic coast Quick edit Valid 2016-02-17 CW-Type_IIA_Adriatic
CW-Type_IIIE Mediterranean, not influenced by freshwater input (Eastern Basin) Quick edit Valid 2016-02-17 CW-Type_IIIE
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?