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
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
speciesInstrument Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
13 Jul 2015

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

2,915 concepts found, displaying 2,501 to 2,520.First122123124125126127128129Last
Id Label Status Status Modified Notation
Silene mariana Silene mariana Quick edit Valid 2016-10-06 Silene mariana
Silene nocteolens Silene nocteolens Quick edit Valid 2016-10-06 Silene nocteolens
Silene orphanidis Silene orphanidis Quick edit Valid 2016-10-06 Silene orphanidis
Silene pompeiopolitana Silene pompeiopolitana (synonym) Quick edit Deprecated - superseded 2016-10-06 Silene pompeiopolitana
Silene rothmaleri Silene rothmaleri Quick edit Valid 2016-10-06 Silene rothmaleri
Silene salsuginea Silene salsuginea Quick edit Valid 2016-10-06 Silene salsuginea
Silene sangaria Silene sangaria Quick edit Valid 2016-10-06 Silene sangaria
Silene velutina Silene velutina Quick edit Valid 2016-10-06 Silene velutina
Siluris aristotelis Siluris aristotelis (synonym) Quick edit Deprecated - superseded 2016-10-06 Siluris aristotelis
Siluris glanis Siluris glanis (synonym) Quick edit Deprecated - superseded 2016-10-06 Siluris glanis
Silurus aristotelis Silurus aristotelis Quick edit Valid 2016-10-06 Silurus aristotelis
Silurus glanis Silurus glanis Quick edit Valid 2016-10-06 Silurus glanis
Sinapidendron angustifolium Sinapidendron angustifolium Quick edit Valid 2016-10-06 Sinapidendron angustifolium
Sinapidendron frutescens Sinapidendron frutescens Quick edit Valid 2016-10-06 Sinapidendron frutescens
Sinapidendron gymnocalyx Sinapidendron gymnocalyx Quick edit Valid 2016-10-06 Sinapidendron gymnocalyx
Sinapidendron rupestre Sinapidendron rupestre Quick edit Valid 2016-10-06 Sinapidendron rupestre
Sinapidendron sempervivifolium Sinapidendron sempervivifolium Quick edit Valid 2016-10-06 Sinapidendron sempervivifolium
Sisymbrium cavanillesianum Sisymbrium cavanillesianum Quick edit Valid 2016-10-06 Sisymbrium cavanillesianum
Sisymbrium confertum Sisymbrium confertum Quick edit Valid 2016-10-06 Sisymbrium confertum
Sisymbrium supinum Sisymbrium supinum Quick edit Valid 2016-10-06 Sisymbrium supinum
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?