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 701 to 720.First3031323334353637Last
Id Label Status Status Modified Notation
euSubUnitCode.SK40000RB2SB4 VÁH Quick edit Valid - stable 2019-09-10 SK40000RB2SB4
euSubUnitCode.SK40000RB2SB5 HRON Quick edit Valid - stable 2019-09-10 SK40000RB2SB5
euSubUnitCode.SK40000RB2SB6 IPEĽ Quick edit Valid - stable 2019-09-10 SK40000RB2SB6
euSubUnitCode.SK40000RB2SB7 SLANÁ Quick edit Valid - stable 2019-09-10 SK40000RB2SB7
euSubUnitCode.SK40000RB2SB8 HORNÁD Quick edit Valid - stable 2019-09-10 SK40000RB2SB8
euSubUnitCode.SK40000RB2SB9 BODVA Quick edit Valid - stable 2019-09-10 SK40000RB2SB9
euSubUnitCode.UK01SU01 NORTH EAST SCOTLAND Quick edit Valid - stable 2019-09-10 UK01SU01
euSubUnitCode.UK01SU02 TAY Quick edit Valid - stable 2019-09-10 UK01SU02
euSubUnitCode.UK01SU03 FORTH Quick edit Valid - stable 2019-09-10 UK01SU03
euSubUnitCode.UK01SU06 CLYDE Quick edit Valid - stable 2019-09-10 UK01SU06
euSubUnitCode.UK01SU07 ARGYLL Quick edit Valid - stable 2019-09-10 UK01SU07
euSubUnitCode.UK01SU08 WEST HIGHLAND Quick edit Valid - stable 2019-09-10 UK01SU08
euSubUnitCode.UK01SU09 NORTH HIGHLAND Quick edit Valid - stable 2019-09-10 UK01SU09
euSubUnitCode.UK01SU10 ORKNEY AND SHETLAND Quick edit Valid - stable 2019-09-10 UK01SU10
euSubUnitCode.UK02 SOLWAY TWEED Quick edit Valid - stable 2019-09-10 UK02
euSubUnitCode.UK03 NORTHUMBRIA Quick edit Valid - stable 2019-09-10 UK03
euSubUnitCode.UK04 HUMBER Quick edit Valid - stable 2019-09-10 UK04
euSubUnitCode.UK05 ANGLIAN Quick edit Valid - stable 2019-09-10 UK05
euSubUnitCode.UK06 THAMES Quick edit Valid - stable 2019-09-10 UK06
euSubUnitCode.UK07 SOUTH EAST Quick edit Valid - stable 2019-09-10 UK07
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?