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 101 to 120.First23456789Last
Id Label Status Status Modified Notation
csb Kashubian Quick edit Valid 2016-02-03 csb
cus Cushitic languages Quick edit Valid 2016-02-03 cus
cym Welsh Quick edit Valid 2016-02-03 cym
cze Czech Quick edit Valid 2016-02-03 cze
dak Dakota Quick edit Valid 2016-02-03 dak
dan Danish Quick edit Valid 2016-02-03 dan
dar Dargwa Quick edit Valid 2016-02-03 dar
day Land Dayak languages Quick edit Valid 2016-02-03 day
del Delaware Quick edit Valid 2016-02-03 del
den Slave (Athapascan) Quick edit Valid 2016-02-03 den
deu German Quick edit Valid 2016-02-03 deu
dgr Dogrib Quick edit Valid 2016-02-03 dgr
din Dinka Quick edit Valid 2016-02-03 din
div Divehi | Dhivehi | Maldivian Quick edit Valid 2016-02-03 div
doi Dogri Quick edit Valid 2016-02-03 doi
dra Dravidian languages Quick edit Valid 2016-02-03 dra
dsb Lower Sorbian Quick edit Valid 2016-02-03 dsb
dua Duala Quick edit Valid 2016-02-03 dua
dum Dutch, Middle (ca.1050-1350) Quick edit Valid 2016-02-03 dum
dut Dutch | Flemish Quick edit Valid 2016-02-03 dut
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?