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,061 to 4,080.First200201202203204205206207Last
Id Label Status Status Modified Notation
G1.91711 Boreo-Atlantic crowberry-bog bilberry birch woods Quick edit Valid 2014-01-31 G1.91711
G1.91712 Boreo-Atlantic small fern birch woods Quick edit Valid 2014-01-31 G1.91712
G1.91713 Icelandic bog bilberry-hairgrass birch woods Quick edit Valid 2014-01-31 G1.91713
G1.91714 Boreo-Atlantic cranesbill birch woods Quick edit Valid 2014-01-31 G1.91714
G1.9172 Oro-Scandian birch woods Quick edit Valid 2014-01-31 G1.9172
G1.91721 Oro-Scandian crowberry-lichen birch woods Quick edit Valid 2014-01-31 G1.91721
G1.91722 Oro-Scandian bilberry-hairgrass birch woods Quick edit Valid 2014-01-31 G1.91722
G1.91723 Oro-Scandian bilberry-dwarf cornel birch woods Quick edit Valid 2014-01-31 G1.91723
G1.91724 Oro-Scandian small-fern birch woods Quick edit Valid 2014-01-31 G1.91724
G1.91725 Oro-Scandian cranesbill-stone bramble birch woods Quick edit Valid 2014-01-31 G1.91725
G1.91726 Oro-Scandian tall-herb birch woods Quick edit Valid 2014-01-31 G1.91726
G1.91727 Oro-Scandian tall-fern birch woods Quick edit Valid 2014-01-31 G1.91727
G1.918 Eurasian boreal [Betula] woods Quick edit Valid 2014-01-31 G1.918
G1.919 Siberian steppe [Betula] woods Quick edit Valid 2014-01-31 G1.919
G1.91A Ponto-Caspian [Betula] woods Quick edit Valid 2014-01-31 G1.91A
G1.92 [Populus tremula] woodland Quick edit Valid 2014-01-31 G1.92
G1.921 Inner Alpine [Populus tremula] woods Quick edit Valid 2014-01-31 G1.921
G1.922 Lowland nemoral [Populus tremula] woods Quick edit Valid 2014-01-31 G1.922
G1.923 Montane [Populus tremula] stands Quick edit Valid 2014-01-31 G1.923
G1.924 Sub-Mediterranean [Populus tremula] stands Quick edit Valid 2014-01-31 G1.924
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?