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:broader Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:editorialNote Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:narrower Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
17 Sep 2015

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

5,282 concepts found, displaying 3,761 to 3,780.First185186187188189190191192Last
Id Label Status Status Modified Notation
G1.6E Pontic [Fagus] forests Quick edit Valid 2014-01-31 G1.6E
G1.6E1 Western Pontic beech forests Quick edit Valid 2014-01-31 G1.6E1
G1.6E11 Eastern Balkan Range oriental beech forests Quick edit Valid 2014-01-31 G1.6E11
G1.6E12 Stranja oriental beech forests Quick edit Valid 2014-01-31 G1.6E12
G1.6E121 Stranja bearberry tree-oriental beech forests Quick edit Valid 2014-01-31 G1.6E121
G1.6E122 Stranja rhododendron-oriental beech forests Quick edit Valid 2014-01-31 G1.6E122
G1.6E13 Western Pontic rhododendron-oriental beech forests Quick edit Valid 2014-01-31 G1.6E13
G1.6E14 Western Pontic calciphile beech forests Quick edit Valid 2014-01-31 G1.6E14
G1.6E15 Western Pontic neutrocline fir-beech forests Quick edit Valid 2014-01-31 G1.6E15
G1.6E16 Western Pontic calciphile fir-beech forests Quick edit Valid 2014-01-31 G1.6E16
G1.6E2 Western sub-Pontic beech-oak forests Quick edit Valid 2014-01-31 G1.6E2
G1.6F Dobrogea [Fagus] forest Quick edit Valid 2014-01-31 G1.6F
G1.6G Crimean [Fagus] forests Quick edit Valid 2014-01-31 G1.6G
G1.6H Caucasian [Fagus] forests Quick edit Valid 2014-01-31 G1.6H
G1.6I Caspian [Fagus] forests Quick edit Valid 2014-01-31 G1.6I
G1.6J Eastern oro-Mediterranean [Fagus] forests Quick edit Valid 2014-01-31 G1.6J
G1.7 Thermophilous deciduous woodland Quick edit Valid 2014-01-31 G1.7
G1.71 Western [Quercus pubescens] woods and related communities Quick edit Valid 2014-01-31 G1.71
G1.711 Western [Quercus pubescens] woods Quick edit Valid 2014-01-31 G1.711
G1.7111 Southwestern [Quercus pubescens] woods Quick edit Valid 2014-01-31 G1.7111
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?