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,661 to 3,680.First180181182183184185186187Last
Id Label Status Status Modified Notation
G1.642 Mesophile Pyrenean beech forests Quick edit Valid 2014-01-31 G1.642
G1.643 Sub-humid oro-Cantabrian beech forests Quick edit Valid 2014-01-31 G1.643
G1.644 Humid Central Massif fir-beech forests Quick edit Valid 2014-01-31 G1.644
G1.65 Medio-European subalpine [Fagus] woods Quick edit Valid 2014-01-31 G1.65
G1.66 Medio-European limestone [Fagus] forests Quick edit Valid 2014-01-31 G1.66
G1.661 Middle European dry-slope limestone beech forests Quick edit Valid 2014-01-31 G1.661
G1.6611 Medio-European dry slope sedge beech forests Quick edit Valid 2014-01-31 G1.6611
G1.6612 Medio-European steep slope yew beech forests Quick edit Valid 2014-01-31 G1.6612
G1.6613 Medio-European blue moorgrass beech forests Quick edit Valid 2014-01-31 G1.6613
G1.6614 Medio-European naked basiphile beech forests Quick edit Valid 2014-01-31 G1.6614
G1.6615 Pannonic limestone beech forests Quick edit Valid 2014-01-31 G1.6615
G1.662 Northwestern Iberian xerophile beech woods Quick edit Valid 2014-01-31 G1.662
G1.67 Southern medio-European [Fagus] forests Quick edit Valid 2014-01-31 G1.67
G1.671 Alpino-Apennine acidophilous beech forests Quick edit Valid 2014-01-31 G1.671
G1.672 Pyreneo-C‚vennian acidophilous beech forest Quick edit Valid 2014-01-31 G1.672
G1.673 Corsican beech forests Quick edit Valid 2014-01-31 G1.673
G1.674 Alpino-Apennine neutrophile beech forests Quick edit Valid 2014-01-31 G1.674
G1.675 Sub-Mediterranean calcicolous beech forests Quick edit Valid 2014-01-31 G1.675
G1.6751 Box beech forests Quick edit Valid 2014-01-31 G1.6751
G1.6752 Androsace beech forests Quick edit Valid 2014-01-31 G1.6752
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?