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,121 to 4,140.First203204205206207208209210Last
Id Label Status Status Modified Notation
G1.A1A11 Illyrian calcicline sessile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1A11
G1.A1A12 Illyrian neutrocline sessile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1A12
G1.A1A13 Illyrian acidocline sessile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1A13
G1.A1A2 Illyrian pedunculate oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1A2
G1.A1A3 Illyrian sub-Mediterranean oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1A3
G1.A1B Pannonic [Quercus] - [Carpinus betulus] forests Quick edit Valid 2014-01-31 G1.A1B
G1.A1B1 Pannonic hygrophile ash-oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1B1
G1.A1B2 Peri-Pannonic acidophile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1B2
G1.A1C Southeastern European [Quercus] - [Carpinus betulus] forests Quick edit Valid 2014-01-31 G1.A1C
G1.A1C1 Dacian oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C1
G1.A1C11 Dacian [Melampyrum biharense] oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C11
G1.A1C12 Dacian [Lathyrus hallersteinii] oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C12
G1.A1C13 Dacian tatar maple oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C13
G1.A1C2 Moldo-Muntenian oak-lime-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C2
G1.A1C3 Moesian oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C3
G1.A1C31 Moesian mesophile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C31
G1.A1C32 Moesian thermophile oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C32
G1.A1C321 Pre-Moesian [Galium kitaibelianum] oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C321
G1.A1C322 Moesian [Quercus cerris] oak-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C322
G1.A1C4 Southern Sarmatic oak-lime-hornbeam forests Quick edit Valid 2014-01-31 G1.A1C4
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?