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,421 to 4,440.First218219220221222223224225Last
Id Label Status Status Modified Notation
G3.1D2 Subalpine spruce forests of the Harz and Erzgebirge Quick edit Valid 2014-01-31 G3.1D2
G3.1D3 Subalpine spruce forests of the Sudeten Quick edit Valid 2014-01-31 G3.1D3
G3.1E Southern European [Picea abies] forests Quick edit Valid 2014-01-31 G3.1E
G3.1E1 Southeastern Moesian [Picea abies] forests Quick edit Valid 2014-01-31 G3.1E1
G3.1E11 Aegeo-Rhodopean spruce forests Quick edit Valid 2014-01-31 G3.1E11
G3.1E12 Central Rhodopide spruce forests Quick edit Valid 2014-01-31 G3.1E12
G3.1E13 Moeso-Macedonian spruce forests Quick edit Valid 2014-01-31 G3.1E13
G3.1E2 Apennine spruce forests Quick edit Valid 2014-01-31 G3.1E2
G3.1E3 Montenegrine [Picea abies] forests Quick edit Valid 2014-01-31 G3.1E3
G3.1E4 Pelagonide [Picea abies] forests Quick edit Valid 2014-01-31 G3.1E4
G3.1E5 Balkan Range [Picea abies] forests Quick edit Valid 2014-01-31 G3.1E5
G3.1F Enclave [Picea abies] forests Quick edit Valid 2014-01-31 G3.1F
G3.1F1 Subalpine Jura spruce forests Quick edit Valid 2014-01-31 G3.1F1
G3.1F2 Subalpine Black Forest spruce forests Quick edit Valid 2014-01-31 G3.1F2
G3.1F3 Peri-Alpine bazzania spruce forests Quick edit Valid 2014-01-31 G3.1F3
G3.1F4 Hercynio-Alpine montane spruce forests Quick edit Valid 2014-01-31 G3.1F4
G3.1F41 Medio-European montane spruce forests Quick edit Valid 2014-01-31 G3.1F41
G3.1F42 Illyrio-Alpine montane beech spruce forests Quick edit Valid 2014-01-31 G3.1F42
G3.1F43 Dacian beech-spruce forests Quick edit Valid 2014-01-31 G3.1F43
G3.1F5 Dinaric spruce forests Quick edit Valid 2014-01-31 G3.1F5
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?