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,641 to 3,660.First179180181182183184185186Last
Id Label Status Status Modified Notation
G1.632 Atlantic neutrophile beech forests Quick edit Valid 2014-01-31 G1.632
G1.6321 Calcicline bluebell beech forests Quick edit Valid 2014-01-31 G1.6321
G1.6322 Neutrocline bluebell beech forests Quick edit Valid 2014-01-31 G1.6322
G1.633 Medio-European montane neutrophile beech forests Quick edit Valid 2014-01-31 G1.633
G1.6331 Jura bittercress beech forests Quick edit Valid 2014-01-31 G1.6331
G1.6332 Western Alps bittercress beech forests Quick edit Valid 2014-01-31 G1.6332
G1.6333 Austro-Bavarian Alps bittercress beech forests Quick edit Valid 2014-01-31 G1.6333
G1.6334 Southeastern Alpine bittercress beech forests Quick edit Valid 2014-01-31 G1.6334
G1.6335 Vosges bittercress beech forests Quick edit Valid 2014-01-31 G1.6335
G1.6336 Black Forest bittercress beech forests Quick edit Valid 2014-01-31 G1.6336
G1.6337 Northern Hercynian bittercress beech forests Quick edit Valid 2014-01-31 G1.6337
G1.6338 Bohemian Quadrangle bittercress beech forests Quick edit Valid 2014-01-31 G1.6338
G1.6339 Western Carpathian bittercress beech forests Quick edit Valid 2014-01-31 G1.6339
G1.634 Bohemian lime-beech forests Quick edit Valid 2014-01-31 G1.634
G1.635 Pannonic neutrophile beech forests Quick edit Valid 2014-01-31 G1.635
G1.6351 Sub-Pannonic beech forests Quick edit Valid 2014-01-31 G1.6351
G1.6352 Pannonic neutrophile collinar beech forests Quick edit Valid 2014-01-31 G1.6352
G1.6353 Pannonic neutrophile montane beech forests Quick edit Valid 2014-01-31 G1.6353
G1.64 Pyreneo-Cantabrian neutrophile [Fagus] forests Quick edit Valid 2014-01-31 G1.64
G1.641 Hygrophile Pyrenean beech forests Quick edit Valid 2014-01-31 G1.641
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?