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 601 to 620.First2728293031323334Last
Id Label Status Status Modified Notation
euSubUnitCode.LVVUBA VENTAS UPJU BASEINU APGABALS Quick edit Valid - stable 2019-09-10 LVVUBA
euSubUnitCode.MTMALTA MALTA Quick edit Valid - stable 2019-09-10 MTMALTA
euSubUnitCode.NLEM EMS Quick edit Valid - stable 2019-09-10 NLEM
euSubUnitCode.NLMS MEUSE Quick edit Valid - stable 2019-09-10 NLMS
euSubUnitCode.NLRN RHINE Quick edit Valid - stable 2019-09-10 NLRN
euSubUnitCode.NLSC SCHELDT Quick edit Valid - stable 2019-09-10 NLSC
euSubUnitCode.NO1 BOTHNIAN BAY Quick edit Valid - stable 2019-09-10 NO1
euSubUnitCode.NO1101 MOERE AND ROMSDAL Quick edit Valid - stable 2019-09-10 NO1101
euSubUnitCode.NO1102 TROENDELAG Quick edit Valid - stable 2019-09-10 NO1102
euSubUnitCode.NO1103 NORDLAND Quick edit Valid - stable 2019-09-10 NO1103
euSubUnitCode.NO1104 TROMS Quick edit Valid - stable 2019-09-10 NO1104
euSubUnitCode.NO1105 FINNMARK Quick edit Valid - stable 2019-09-10 NO1105
euSubUnitCode.NO1106 NORWEGIAN - FINNISH Quick edit Valid - stable 2019-09-10 NO1106
euSubUnitCode.NO1TO BOTHNIAN BAY (INTERNATIONAL DISTRICT TORNE RIVER - NORWAY) Quick edit Valid - stable 2019-09-10 NO1TO
euSubUnitCode.NO2 BOTHNIAN SEA Quick edit Valid - stable 2019-09-10 NO2
euSubUnitCode.NO5 SKAGERRAK AND KATTEGAT Quick edit Valid - stable 2019-09-10 NO5
euSubUnitCode.NO5101 GLOMMA Quick edit Valid - stable 2019-09-10 NO5101
euSubUnitCode.NO5102 WEST-BAY Quick edit Valid - stable 2019-09-10 NO5102
euSubUnitCode.NO5103 AGDER Quick edit Valid - stable 2019-09-10 NO5103
euSubUnitCode.NO5104 ROGALAND Quick edit Valid - stable 2019-09-10 NO5104
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?