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:broadMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:narrowMatch 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

174 concepts found, displaying 161 to 174.First23456789NextLast
Id Label Status Status Modified Notation
4905 4905 Quick edit Valid 2013-06-05 4905
4906 4906 Quick edit Valid 2013-06-05 4906
4907 4907 Quick edit Valid 2013-06-05 4907
4908 4908 Quick edit Valid 2013-06-05 4908
4909 4909 Quick edit Valid 2013-06-05 4909
5001 5001 Quick edit Valid 2013-06-05 5001
5002 5002 Quick edit Valid 2013-06-05 5002
5003 5003 Quick edit Valid 2013-06-05 5003
5004 5004 Quick edit Valid 2013-06-05 5004
5005 5005 Quick edit Valid 2013-06-05 5005
5006 5006 Quick edit Valid 2013-06-05 5006
5007 5007 Quick edit Valid 2013-06-05 5007
5008 5008 Quick edit Valid 2013-06-05 5008
5009 5009 Quick edit Valid 2013-06-05 5009
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?