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,901 to 3,920.First192193194195196197198199Last
Id Label Status Status Modified Notation
G1.7A1221 Pontic [Acer tataricum]-[Q. pedunculiflora] steppe woods Quick edit Valid 2014-01-31 G1.7A1221
G1.7A1222 Pontic [Acer tataricum]-[Quercus pubescens] steppe woods Quick edit Valid 2014-01-31 G1.7A1222
G1.7A1223 Pontic [Acer tataricum]-[Q. cerris]-[Q. pedunculiflora] steppe woods Quick edit Valid 2014-01-31 G1.7A1223
G1.7A1224 Sarmatic [Acer tataricum]-[Quercus robur] steppe woods Quick edit Valid 2014-01-31 G1.7A1224
G1.7A1225 Sarmatic [Acer tataricum]-[Q. robur]-[Q. petraea] steppe woods Quick edit Valid 2014-01-31 G1.7A1225
G1.7A123 Getic tartar maple steppe oak woods Quick edit Valid 2014-01-31 G1.7A123
G1.7A13 Sub-Euxinian steppe woods Quick edit Valid 2014-01-31 G1.7A13
G1.7A2 Irano-Anatolian steppe [Quercus] woods Quick edit Valid 2014-01-31 G1.7A2
G1.7B [Quercus pyrenaica] woodland Quick edit Valid 2014-01-31 G1.7B
G1.7B1 Central Iberian [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B1
G1.7B11 Sub-Atlantic Iberian [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B11
G1.7B111 Sub-Atlantic sub-humid [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B111
G1.7B112 Sub-Atlantic humid [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B112
G1.7B12 Iberian sub-continental [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B12
G1.7B121 Sub-continental sub-humid [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B121
G1.7B122 Sub-continental humid [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B122
G1.7B13 Mariano-Oretanian [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B13
G1.7B131 Lower Mariano-Oretanian [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B131
G1.7B132 Upper Mariano-Oretanian [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B132
G1.7B2 Cantabrian [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B2
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?