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

506 concepts found, displaying 181 to 200.First678910111213Last
Id Label Status Status Modified Notation
heb Hebrew Quick edit Valid 2016-02-03 heb
her Herero Quick edit Valid 2016-02-03 her
hil Hiligaynon Quick edit Valid 2016-02-03 hil
him Himachali languages | Western Pahari languages Quick edit Valid 2016-02-03 him
hin Hindi Quick edit Valid 2016-02-03 hin
hit Hittite Quick edit Valid 2016-02-03 hit
hmn Hmong | Mong Quick edit Valid 2016-02-03 hmn
hmo Hiri Motu Quick edit Valid 2016-02-03 hmo
hrv Croatian Quick edit Valid 2016-02-03 hrv
hsb Upper Sorbian Quick edit Valid 2016-02-03 hsb
hun Hungarian Quick edit Valid 2016-02-03 hun
hup Hupa Quick edit Valid 2016-02-03 hup
hye Armenian Quick edit Valid 2016-02-03 hye
iba Iban Quick edit Valid 2016-02-03 iba
ibo Igbo Quick edit Valid 2016-02-03 ibo
ice Icelandic Quick edit Valid 2016-02-03 ice
ido Ido Quick edit Valid 2016-02-03 ido
iii Sichuan Yi | Nuosu Quick edit Valid 2016-02-03 iii
ijo Ijo languages Quick edit Valid 2016-02-03 ijo
iku Inuktitut Quick edit Valid 2016-02-03 iku
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?