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 21 to 40.First12345678Last
Id Label Status Status Modified Notation
ara Arabic Quick edit Valid 2016-02-03 ara
arc Official Aramaic (700-300 BCE) | Imperial Aramaic (700-300 BCE) Quick edit Valid 2016-02-03 arc
arg Aragonese Quick edit Valid 2016-02-03 arg
arm Armenian Quick edit Valid 2016-02-03 arm
arn Mapudungun | Mapuche Quick edit Valid 2016-02-03 arn
arp Arapaho Quick edit Valid 2016-02-03 arp
art Artificial languages Quick edit Valid 2016-02-03 art
arw Arawak Quick edit Valid 2016-02-03 arw
asm Assamese Quick edit Valid 2016-02-03 asm
ast Asturian | Bable | Leonese | Asturleonese Quick edit Valid 2016-02-03 ast
ath Athapascan languages Quick edit Valid 2016-02-03 ath
aus Australian languages Quick edit Valid 2016-02-03 aus
ava Avaric Quick edit Valid 2016-02-03 ava
ave Avestan Quick edit Valid 2016-02-03 ave
awa Awadhi Quick edit Valid 2016-02-03 awa
aym Aymara Quick edit Valid 2016-02-03 aym
aze Azerbaijani Quick edit Valid 2016-02-03 aze
bad Banda languages Quick edit Valid 2016-02-03 bad
bai Bamileke languages Quick edit Valid 2016-02-03 bai
bak Bashkir Quick edit Valid 2016-02-03 bak
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?