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 461 to 480.First2021222324252627Last
Id Label Status Status Modified Notation
euSubUnitCode.EL09 WESTERN MACEDONIA Quick edit Valid - stable 2019-09-10 EL09
euSubUnitCode.EL10 CENTRAL MACEDONIA Quick edit Valid - stable 2019-09-10 EL10
euSubUnitCode.EL11 EASTERN MACEDONIA Quick edit Valid - stable 2019-09-10 EL11
euSubUnitCode.EL12 THRACE Quick edit Valid - stable 2019-09-10 EL12
euSubUnitCode.EL13 CRETE Quick edit Valid - stable 2019-09-10 EL13
euSubUnitCode.EL14 AEGEAN ISLANDS Quick edit Valid - stable 2019-09-10 EL14
euSubUnitCode.ES010 MINHO Quick edit Valid - stable 2019-09-10 ES010
euSubUnitCode.ES014 GALICIAN COAST Quick edit Valid - stable 2019-09-10 ES014
euSubUnitCode.ES017 EASTERN CANTABRIAN Quick edit Valid - stable 2019-09-10 ES017
euSubUnitCode.ES018 WESTERN CANTABRIAN Quick edit Valid - stable 2019-09-10 ES018
euSubUnitCode.ES020 DUERO Quick edit Valid - stable 2019-09-10 ES020
euSubUnitCode.ES030 TAGUS Quick edit Valid - stable 2019-09-10 ES030
euSubUnitCode.ES040 GUADIANA Quick edit Valid - stable 2019-09-10 ES040
euSubUnitCode.ES050 GUADALQUIVIR Quick edit Valid - stable 2019-09-10 ES050
euSubUnitCode.ES060 ANDALUSIA MEDITERRANEAN BASINS Quick edit Valid - stable 2019-09-10 ES060
euSubUnitCode.ES063 GUADALETE AND BARBATE Quick edit Valid - stable 2019-09-10 ES063
euSubUnitCode.ES064 TINTO, ODIEL AND PIEDRAS Quick edit Valid - stable 2019-09-10 ES064
euSubUnitCode.ES070 SEGURA Quick edit Valid - stable 2019-09-10 ES070
euSubUnitCode.ES080 JUCAR Quick edit Valid - stable 2019-09-10 ES080
euSubUnitCode.ES091 EBRO Quick edit Valid - stable 2019-09-10 ES091
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?