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,101 to 4,120.First202203204205206207208209Last
Id Label Status Status Modified Notation
G1.A161 Wood bedstraw oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A161
G1.A162 Mixed lime-oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A162
G1.A163 Boreonemoral spruce-lime-oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A163
G1.A164 Peri-Carpathian lime-oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A164
G1.A165 Bohemian oak-hornbeam and oak-lime forests Quick edit Valid 2014-01-31 G1.A165
G1.A166 Carpathian hairy sedge oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A166
G1.A167 Sub-Pannonic primrose oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A167
G1.A168 Central sub-Carpathian oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A168
G1.A1681 Waldsteinia oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1681
G1.A1682 Scorpion-vetch oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1682
G1.A169 Western boreal mixed deciduous forests Quick edit Valid 2014-01-31 G1.A169
G1.A16A Northern middle Russian oak-lime forests Quick edit Valid 2014-01-31 G1.A16A
G1.A17 Sub-Atlantic calciphile [Quercus] - [Carpinus betulus] forests Quick edit Valid 2014-01-31 G1.A17
G1.A171 Sub-Atlantic calciphile privet oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A171
G1.A172 Sub-Atlantic xerophile [Anthericum] oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A172
G1.A173 Sub-Atlantic calciphile squill ash-oak forests Quick edit Valid 2014-01-31 G1.A173
G1.A18 Southern Alpine [Quercus] - [Carpinus betulus] forests Quick edit Valid 2014-01-31 G1.A18
G1.A19 Pyreneo-Cantabrian [Quercus] - [Fraxinus] forests Quick edit Valid 2014-01-31 G1.A19
G1.A1A Illyrian [Quercus] - [Carpinus betulus] forests Quick edit Valid 2014-01-31 G1.A1A
G1.A1A1 Illyrian sessile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1A1
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?