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 341 to 360.First1415161718192021Last
Id Label Status Status Modified Notation
nzi Nzima Quick edit Valid 2016-02-03 nzi
oci Occitan (post 1500) Quick edit Valid 2016-02-03 oci
oji Ojibwa Quick edit Valid 2016-02-03 oji
ori Oriya Quick edit Valid 2016-02-03 ori
orm Oromo Quick edit Valid 2016-02-03 orm
osa Osage Quick edit Valid 2016-02-03 osa
oss Ossetian | Ossetic Quick edit Valid 2016-02-03 oss
ota Turkish, Ottoman (1500-1928) Quick edit Valid 2016-02-03 ota
oto Otomian languages Quick edit Valid 2016-02-03 oto
paa Papuan languages Quick edit Valid 2016-02-03 paa
pag Pangasinan Quick edit Valid 2016-02-03 pag
pal Pahlavi Quick edit Valid 2016-02-03 pal
pam Pampanga | Kapampangan Quick edit Valid 2016-02-03 pam
pan Panjabi | Punjabi Quick edit Valid 2016-02-03 pan
pap Papiamento Quick edit Valid 2016-02-03 pap
pau Palauan Quick edit Valid 2016-02-03 pau
peo Persian, Old (ca.600-400 B.C.) Quick edit Valid 2016-02-03 peo
per Persian Quick edit Valid 2016-02-03 per
phi Philippine languages Quick edit Valid 2016-02-03 phi
phn Phoenician Quick edit Valid 2016-02-03 phn
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?