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,541 to 4,560.First224225226227228229230231Last
Id Label Status Status Modified Notation
G3.4C41 Moeso-Macedonian Scots pine forests Quick edit Valid 2014-01-31 G3.4C41
G3.4C42 Pelagonian Scots pine forests Quick edit Valid 2014-01-31 G3.4C42
G3.4C5 Dinaric spring heath Scots pine forests Quick edit Valid 2014-01-31 G3.4C5
G3.4C51 Dinaric serpentine Scots pine forests Quick edit Valid 2014-01-31 G3.4C51
G3.4C52 Dinaric dolomite Scots pine forests Quick edit Valid 2014-01-31 G3.4C52
G3.4C6 Dinaric calcicole Scots pine forests Quick edit Valid 2014-01-31 G3.4C6
G3.4C7 Dinaric acidophile Scots pine forests Quick edit Valid 2014-01-31 G3.4C7
G3.4C8 East Carpathian [Sesleria] Scots pine forests Quick edit Valid 2014-01-31 G3.4C8
G3.4C9 East Carpathian bilberry Scots pine forests Quick edit Valid 2014-01-31 G3.4C9
G3.4CA East Carpathian [Daphne blagayana] Scots pine forests Quick edit Valid 2014-01-31 G3.4CA
G3.4D Po terrace [Pinus sylvestris] forests Quick edit Valid 2014-01-31 G3.4D
G3.4E Ponto-Caucasian [Pinus sylvestris] forests Quick edit Valid 2014-01-31 G3.4E
G3.4F European [Pinus sylvestris] reforestation Quick edit Valid 2014-01-31 G3.4F
G3.5 [Pinus nigra] woodland Quick edit Valid 2014-01-31 G3.5
G3.51 Alpino-Apennine [Pinus nigra] forests Quick edit Valid 2014-01-31 G3.51
G3.511 Southern Alpine [Pinus nigra] forests Quick edit Valid 2014-01-31 G3.511
G3.512 Apennine [Pinus nigra] forests Quick edit Valid 2014-01-31 G3.512
G3.513 Lower Austrian [Pinus nigra] forests Quick edit Valid 2014-01-31 G3.513
G3.514 Northwestern Adriatic [Pinus nigra] forests Quick edit Valid 2014-01-31 G3.514
G3.52 Western Balkanic [Pinus nigra] forests Quick edit Valid 2014-01-31 G3.52
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?