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,621 to 3,640.First178179180181182183184185Last
Id Label Status Status Modified Notation
G1.6113 Peri-Alpine collinar woodrush beech forests Quick edit Valid 2014-01-31 G1.6113
G1.6114 Western sub-Pannonic collinar woodrush beech forests Quick edit Valid 2014-01-31 G1.6114
G1.6115 Pannonic collinar woodrush beech forests Quick edit Valid 2014-01-31 G1.6115
G1.612 Medio-European montane woodrush beech forests Quick edit Valid 2014-01-31 G1.612
G1.6121 Hercyno-Alpine montane woodrush beech forests Quick edit Valid 2014-01-31 G1.6121
G1.6122 Western medio-European montane woodrush beech forests Quick edit Valid 2014-01-31 G1.6122
G1.62 Atlantic acidophilous [Fagus] forests Quick edit Valid 2014-01-31 G1.62
G1.621 Germano-Baltic acidophilous beech forests Quick edit Valid 2014-01-31 G1.621
G1.622 Sub-Atlantic acidophilous beech forests Quick edit Valid 2014-01-31 G1.622
G1.623 Armorican acidophilous beech forests Quick edit Valid 2014-01-31 G1.623
G1.624 Pyreneo-Cantabrian acidophilous beech forests Quick edit Valid 2014-01-31 G1.624
G1.625 Western Cantabrian acidophilous beech forests Quick edit Valid 2014-01-31 G1.625
G1.626 Galician acidophilous beech forests Quick edit Valid 2014-01-31 G1.626
G1.627 Humid Iberian acidophilous beech forests Quick edit Valid 2014-01-31 G1.627
G1.628 Hyper-humid Iberian acidophilous beech forests Quick edit Valid 2014-01-31 G1.628
G1.629 Ayllon acidophilous beech forests Quick edit Valid 2014-01-31 G1.629
G1.63 Medio-European neutrophile [Fagus] forests Quick edit Valid 2014-01-31 G1.63
G1.631 Medio-European collinar neutrophile beech forests Quick edit Valid 2014-01-31 G1.631
G1.6311 Medio-European wood barley beech forests Quick edit Valid 2014-01-31 G1.6311
G1.6312 Medio-European woodruff and hairy sedge beech forests Quick edit Valid 2014-01-31 G1.6312
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?