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,741 to 3,760.First184185186187188189190191Last
Id Label Status Status Modified Notation
G1.6D Dacian [Fagus] forests Quick edit Valid 2014-01-31 G1.6D
G1.6D1 East Carpathian acidophile beech forests Quick edit Valid 2014-01-31 G1.6D1
G1.6D11 Dacian woodrush-beech forests Quick edit Valid 2014-01-31 G1.6D11
G1.6D12 Dacian [Galium kitaibelianum] beech forests Quick edit Valid 2014-01-31 G1.6D12
G1.6D13 Dacian [Galium rotundifolium] beech forests Quick edit Valid 2014-01-31 G1.6D13
G1.6D2 East Carpathian neutrophile beech forests Quick edit Valid 2014-01-31 G1.6D2
G1.6D21 Dacian [Symphytum] beech forests Quick edit Valid 2014-01-31 G1.6D21
G1.6D211 Dacian [Dentaria glandulosa] beech forests Quick edit Valid 2014-01-31 G1.6D211
G1.6D212 Dacian [Pulmonaria rubra] fir-beech forests Quick edit Valid 2014-01-31 G1.6D212
G1.6D213 Dacian [Leucanthemum] beech forests Quick edit Valid 2014-01-31 G1.6D213
G1.6D22 Dacian hairy sedge beech-hornbeam forests Quick edit Valid 2014-01-31 G1.6D22
G1.6D3 East Carpathian subalpine beech forests Quick edit Valid 2014-01-31 G1.6D3
G1.6D31 Dacian subalpine beech-spruce forest Quick edit Valid 2014-01-31 G1.6D31
G1.6D32 Dacian subalpine gooseberry beech forests Quick edit Valid 2014-01-31 G1.6D32
G1.6D4 East Carpathian calciphile beech forests Quick edit Valid 2014-01-31 G1.6D4
G1.6D5 South Carpathian thermophilous beech forests Quick edit Valid 2014-01-31 G1.6D5
G1.6D51 South Carpathian [Aremonia] beech forests Quick edit Valid 2014-01-31 G1.6D51
G1.6D52 South Carpathian [Corylus colurna] beech forests Quick edit Valid 2014-01-31 G1.6D52
G1.6D53 South Carpathian [Helleborus odorus] beech forests Quick edit Valid 2014-01-31 G1.6D53
G1.6D54 South Carpathian [Festuca drymeja] beech forests Quick edit Valid 2014-01-31 G1.6D54
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?