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,181 to 4,200.First206207208209210211212213Last
Id Label Status Status Modified Notation
G1.A462 Moesian ravine and slope forests Quick edit Valid 2014-01-31 G1.A462
G1.A4621 Moesian beech-ash-sycamore ravine forests Quick edit Valid 2014-01-31 G1.A4621
G1.A46211 Moesian [Geranium macrorrhizum] ravine forests Quick edit Valid 2014-01-31 G1.A46211
G1.A46212 Moesian beech-hornbeam-ostrya ravine forests Quick edit Valid 2014-01-31 G1.A46212
G1.A46213 Moesian ash-sycamore ravine forests Quick edit Valid 2014-01-31 G1.A46213
G1.A4622 Moesian horse-chestnut ravine forests Quick edit Valid 2014-01-31 G1.A4622
G1.A46221 Balkan Range horse-chestnut ravine forests Quick edit Valid 2014-01-31 G1.A46221
G1.A46222 Pelagonid horse-chestnut ravine forests Quick edit Valid 2014-01-31 G1.A46222
G1.A4623 Moesian ash-oak slope forests Quick edit Valid 2014-01-31 G1.A4623
G1.A46231 Balkan ash-oak slope forests Quick edit Valid 2014-01-31 G1.A46231
G1.A46232 Rhodopid ash-oak-ostrya slope forests Quick edit Valid 2014-01-31 G1.A46232
G1.A463 Illyrian ravine forests Quick edit Valid 2014-01-31 G1.A463
G1.A464 Eastern Carpathian ravine forests Quick edit Valid 2014-01-31 G1.A464
G1.A4641 Dacian [Phyllitis] beech ravine forests Quick edit Valid 2014-01-31 G1.A4641
G1.A4642 Dacian ash-sycamore ravine forests Quick edit Valid 2014-01-31 G1.A4642
G1.A4643 Dacian [Geranium macrorrhizum] beech ravine forests Quick edit Valid 2014-01-31 G1.A4643
G1.A47 Euxinian ravine forests Quick edit Valid 2014-01-31 G1.A47
G1.A5 [Tilia] woodland Quick edit Valid 2014-01-31 G1.A5
G1.A51 Western [Tilia] forests Quick edit Valid 2014-01-31 G1.A51
G1.A52 Sub-boreal [Tilia] forests Quick edit Valid 2014-01-31 G1.A52
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?