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,401 to 4,420.First217218219220221222223224Last
Id Label Status Status Modified Notation
G3.1B5 Cold station spruce forests Quick edit Valid 2014-01-31 G3.1B5
G3.1B6 Carpathian spruce forests Quick edit Valid 2014-01-31 G3.1B6
G3.1B61 Western Carpathian subalpine spruce forests Quick edit Valid 2014-01-31 G3.1B61
G3.1B611 Western Carpathian acidophilous spruce forests Quick edit Valid 2014-01-31 G3.1B611
G3.1B612 Carpathian holly-fern spruce forests Quick edit Valid 2014-01-31 G3.1B612
G3.1B62 Eastern Carpathian subalpine spruce forests Quick edit Valid 2014-01-31 G3.1B62
G3.1B621 Carpathian subalpine rhododenron spruce forests Quick edit Valid 2014-01-31 G3.1B621
G3.1B622 Carpathian subalpine Bruckenthalia spruce forests Quick edit Valid 2014-01-31 G3.1B622
G3.1B623 Carpathian high montane [Hieracium] spruce forests Quick edit Valid 2014-01-31 G3.1B623
G3.1B624 Carpathian high montane [Bazzania] spruce forests Quick edit Valid 2014-01-31 G3.1B624
G3.1B625 Carpathian [Leucanthemum] high montane spruce forests Quick edit Valid 2014-01-31 G3.1B625
G3.1C Inner range montane [Picea] forests Quick edit Valid 2014-01-31 G3.1C
G3.1C1 Acidophile montane inner Alpine spruce forests Quick edit Valid 2014-01-31 G3.1C1
G3.1C2 Calciphile montane inner Alpine spruce forests Quick edit Valid 2014-01-31 G3.1C2
G3.1C3 Bedstraw montane inner Alpine spruce forests Quick edit Valid 2014-01-31 G3.1C3
G3.1C4 Tall herb montane inner Alpine spruce forests Quick edit Valid 2014-01-31 G3.1C4
G3.1C5 Peatmoss montane inner Alpine spruce forests Quick edit Valid 2014-01-31 G3.1C5
G3.1C6 Inner Carpathian spruce forests Quick edit Valid 2014-01-31 G3.1C6
G3.1D Hercynian subalpine [Picea] forests Quick edit Valid 2014-01-31 G3.1D
G3.1D1 Subalpine spruce forests of the Bayerischer Wald Quick edit Valid 2014-01-31 G3.1D1
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?