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 4,021 to 4,040.First198199200201202203204205Last
Id Label Status Status Modified Notation
G1.8733 Illyro-Pannonic chestnut-sessile oak forests Quick edit Valid 2014-01-31 G1.8733
G1.87331 Pre-Carpathian chestnut-sessile oak forests Quick edit Valid 2014-01-31 G1.87331
G1.87332 Illyrian chestnut-sessile oak forests Quick edit Valid 2014-01-31 G1.87332
G1.8734 Illyrian birch-sessile oak acidophilous forests Quick edit Valid 2014-01-31 G1.8734
G1.88 Insubrian acidophilous [Quercus] forests Quick edit Valid 2014-01-31 G1.88
G1.89 Portuguese [Quercus robur] forests Quick edit Valid 2014-01-31 G1.89
G1.8A Continental [Quercus petraea] forests Quick edit Valid 2014-01-31 G1.8A
G1.9 Non-riverine woodland with [Betula], [Populus tremula] or [Sorbus aucuparia] Quick edit Valid 2014-01-31 G1.9
G1.91 [Betula] woodland not on marshy terrain Quick edit Valid 2014-01-31 G1.91
G1.911 Atlantic lowland and collinar [Betula] woods Quick edit Valid 2014-01-31 G1.911
G1.9111 Humid birch woods Quick edit Valid 2014-01-31 G1.9111
G1.91111 Northern humid birch woods Quick edit Valid 2014-01-31 G1.91111
G1.91112 Aquitano-Ligerian humid birch woods Quick edit Valid 2014-01-31 G1.91112
G1.9112 Medio-European dry acidophilous birch woods Quick edit Valid 2014-01-31 G1.9112
G1.9113 Iberian acidophilous birch woods Quick edit Valid 2014-01-31 G1.9113
G1.9114 Insubrian acidophilous birch woods Quick edit Valid 2014-01-31 G1.9114
G1.9115 Heavy-metal birch woods Quick edit Valid 2014-01-31 G1.9115
G1.9116 Dune birch woods Quick edit Valid 2014-01-31 G1.9116
G1.9117 Illyrian birch woods Quick edit Valid 2014-01-31 G1.9117
G1.912 British sub-boreal [Betula] woods Quick edit Valid 2014-01-31 G1.912
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?