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 (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

7,878 concepts found, displaying 6,101 to 6,120.First302303304305306307308309Last
Id Label Status Status Modified Notation
sty Siberian Tatar Quick edit Valid 2014-03-20 sty
sua Sulka Quick edit Valid 2014-03-20 sua
sub Suku Quick edit Valid 2014-03-20 sub
suc Western Subanon Quick edit Valid 2014-03-20 suc
sue Suena Quick edit Valid 2014-03-20 sue
sug Suganga Quick edit Valid 2014-03-20 sug
sui Suki Quick edit Valid 2014-03-20 sui
suj Shubi Quick edit Valid 2014-03-20 suj
suk Sukuma Quick edit Valid 2014-03-20 suk
sun Sundanese Quick edit Valid 2014-03-20 sun
suq Suri Quick edit Valid 2014-03-20 suq
sur Mwaghavul Quick edit Valid 2014-03-20 sur
sus Susu Quick edit Valid 2014-03-20 sus
sut Subtiaba Quick edit Valid 2014-03-20 sut
suv Puroik Quick edit Valid 2014-03-20 suv
suw Sumbwa Quick edit Valid 2014-03-20 suw
sux Sumerian Quick edit Valid 2014-03-20 sux
suy Suyá Quick edit Valid 2014-03-20 suy
suz Sunwar Quick edit Valid 2014-03-20 suz
sva Svan Quick edit Valid 2014-03-20 sva
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?