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,341 to 4,360.First214215216217218219220221Last
Id Label Status Status Modified Notation
G3.11 Neutrophile medio-European [Abies] forests Quick edit Valid 2014-01-31 G3.11
G3.111 Inner Alpine neutrophile fir forests Quick edit Valid 2014-01-31 G3.111
G3.1111 Sorrel fir forests Quick edit Valid 2014-01-31 G3.1111
G3.1112 Tall herb fir forests Quick edit Valid 2014-01-31 G3.1112
G3.1113 Trochischantes fir forests Quick edit Valid 2014-01-31 G3.1113
G3.112 Neutrophile Hercynio-Alpine fir forests Quick edit Valid 2014-01-31 G3.112
G3.1121 Peri-Alpine neutrophile fir forests Quick edit Valid 2014-01-31 G3.1121
G3.11211 Peri-Alpine neutrophile spruce fir forests Quick edit Valid 2014-01-31 G3.11211
G3.11212 Peri-Alpine neutrophile beech fir forests Quick edit Valid 2014-01-31 G3.11212
G3.1122 Illyrian neutrophile fir forests Quick edit Valid 2014-01-31 G3.1122
G3.11221 Illyrian neutrophile spruce fir forests Quick edit Valid 2014-01-31 G3.11221
G3.11222 Illyrian neutrophile beech fir forests Quick edit Valid 2014-01-31 G3.11222
G3.1123 Dacian neutrophile montane fir forests Quick edit Valid 2014-01-31 G3.1123
G3.113 Pyrenean fir forests Quick edit Valid 2014-01-31 G3.113
G3.114 East Carpathian high montane fir forests Quick edit Valid 2014-01-31 G3.114
G3.12 Calciphilous [Abies alba] forests Quick edit Valid 2014-01-31 G3.12
G3.121 Inner Alpine calcicolous fir forests Quick edit Valid 2014-01-31 G3.121
G3.122 Outer Alpine calcicolous fir forests Quick edit Valid 2014-01-31 G3.122
G3.123 Jurasso-Hercynian calcicolous fir forests Quick edit Valid 2014-01-31 G3.123
G3.124 Dinaric calcareous block fir forests Quick edit Valid 2014-01-31 G3.124
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?