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,921 to 3,940.First193194195196197198199200Last
Id Label Status Status Modified Notation
G1.7B3 Maestrazgan [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B3
G1.7B4 Baetic [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B4
G1.7B5 French [Quercus pyrenaica] forests Quick edit Valid 2014-01-31 G1.7B5
G1.7C Mixed thermophilous woodland Quick edit Valid 2014-01-31 G1.7C
G1.7C1 [Ostrya carpinifolia] woods Quick edit Valid 2014-01-31 G1.7C1
G1.7C11 Mesomediterranean Gallo-Italic hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C11
G1.7C12 Supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C12
G1.7C121 Southwestern Alpine supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C121
G1.7C122 Southeastern Alpine supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C122
G1.7C123 Eastern Adriatic supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C123
G1.7C124 Apennine supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C124
G1.7C125 Corsican supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C125
G1.7C126 Southern Tyrrhenian supra-Mediterranean hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C126
G1.7C13 Montane hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C13
G1.7C14 Illyrian hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C14
G1.7C141 Illyrian white oak hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C141
G1.7C142 Illyrian spring heath hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C142
G1.7C15 Anatolian hop-hornbeam woods Quick edit Valid 2014-01-31 G1.7C15
G1.7C2 [Carpinus orientalis] woods Quick edit Valid 2014-01-31 G1.7C2
G1.7C21 Inner Illyrian oriental hornbeam woods Quick edit Valid 2014-01-31 G1.7C21
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?