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 181 to 200.First678910111213Last
Id Label Status Status Modified Notation
A2.26 Strictly Pontic communities of mediolittoral sands Quick edit Valid 2014-01-31 A2.26
A2.261 [Donacilla cornea] in medium-coarse mediolittoral sands Quick edit Valid 2014-01-31 A2.261
A2.262 [Pontogammarus maeoticus] in fine mediolittoral sands Quick edit Valid 2014-01-31 A2.262
A2.3 Littoral mud Quick edit Valid 2014-01-31 A2.3
A2.31 Polychaete/bivalve-dominated mid estuarine mud shores Quick edit Valid 2014-01-31 A2.31
A2.311 [Nephtys hombergii], [Macoma balthica] and [Streblospio shrubsolii] in littoral sandy mud Quick edit Valid 2014-01-31 A2.311
A2.312 [Hediste diversicolor] and [Macoma balthica] in littoral sandy mud Quick edit Valid 2014-01-31 A2.312
A2.313 [Hediste diversicolor], [Macoma balthica] and [Scrobicularia plana] in littoral sandy mud Quick edit Valid 2014-01-31 A2.313
A2.32 Polychaete/oligochaete-dominated upper estuarine mud shores Quick edit Valid 2014-01-31 A2.32
A2.321 [Nephtys hombergii] and [Streblospio shrubsolii] in littoral mud Quick edit Valid 2014-01-31 A2.321
A2.322 [Hediste diversicolor] in littoral mud Quick edit Valid 2014-01-31 A2.322
A2.3221 [Hediste diversicolor] and [Streblospio shrubsolii] in littoral sandy mud Quick edit Valid 2014-01-31 A2.3221
A2.3222 [Hediste diversicolor] and [Corophium volutator] in littoral mud Quick edit Valid 2014-01-31 A2.3222
A2.3223 [Hediste diversicolor] and oligochaetes in littoral mud Quick edit Valid 2014-01-31 A2.3223
A2.323 [Tubificoides benedii] and other oligochaetes in littoral mud Quick edit Valid 2014-01-31 A2.323
A2.324 Saltmarsh pools Quick edit Valid 2014-01-31 A2.324
A2.325 Saltmarsh creeks Quick edit Valid 2014-01-31 A2.325
A2.3251 Erosion faces with [Carcinus maenas] Quick edit Valid 2014-01-31 A2.3251
A2.326 Pontic polychaete dominated littoral muds Quick edit Valid 2014-01-31 A2.326
A2.327 Pontic oligochaete and chironomid dominated littoral muds Quick edit Valid 2014-01-31 A2.327
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?