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,721 to 3,740.First183184185186187188189190Last
Id Label Status Status Modified Notation
G1.694 South-Dinaric beech forests Quick edit Valid 2014-01-31 G1.694
G1.6A Hellenic [Fagus] forests Quick edit Valid 2014-01-31 G1.6A
G1.6A1 Pindus Hellenic beech forests Quick edit Valid 2014-01-31 G1.6A1
G1.6A2 Olympian Hellenic beech forests Quick edit Valid 2014-01-31 G1.6A2
G1.6B Mediterraneo-Moesian [Fagus] forests Quick edit Valid 2014-01-31 G1.6B
G1.6C Illyrian [Fagus] forests Quick edit Valid 2014-01-31 G1.6C
G1.6C1 Illyrian woodrush-beech forests Quick edit Valid 2014-01-31 G1.6C1
G1.6C2 Illyrian neutrophile beech forests Quick edit Valid 2014-01-31 G1.6C2
G1.6C21 Illyrian collinar neutrophile beech forests Quick edit Valid 2014-01-31 G1.6C21
G1.6C22 Illyrian montane fir-beech forests Quick edit Valid 2014-01-31 G1.6C22
G1.6C221 Illyrian low-montane acidocline fir-beech forests Quick edit Valid 2014-01-31 G1.6C221
G1.6C222 Illyrian low-montane neutrophile fir-beech forests Quick edit Valid 2014-01-31 G1.6C222
G1.6C223 Illyrian high-montane fir-beech forests Quick edit Valid 2014-01-31 G1.6C223
G1.6C3 Illyrian thermophile beech forests Quick edit Valid 2014-01-31 G1.6C3
G1.6C31 Illyrian coastal beech forests Quick edit Valid 2014-01-31 G1.6C31
G1.6C32 Illyrian inland calciphile beech forests Quick edit Valid 2014-01-31 G1.6C32
G1.6C321 Illyrian hop-hornbeam beech forests Quick edit Valid 2014-01-31 G1.6C321
G1.6C322 Illyrian [Helleborus odorus] beech forests Quick edit Valid 2014-01-31 G1.6C322
G1.6C323 Illyrian [Acer obtusatum] beech forests Quick edit Valid 2014-01-31 G1.6C323
G1.6C4 Illyrian subalpine beech forests Quick edit Valid 2014-01-31 G1.6C4
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?