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 641 to 660.First2930313233343536Last
Id Label Status Status Modified Notation
A4.735 Pontic methane seeps in infralittoral and circalittoral rock Quick edit Valid 2014-01-31 A4.735
A5 Sublittoral sediment Quick edit Valid 2014-01-31 A5
A5.1 Sublittoral coarse sediment Quick edit Valid 2014-01-31 A5.1
A5.11 Infralittoral coarse sediment in low or reduced salinity Quick edit Valid 2014-01-31 A5.11
A5.111 Baltic level gravel bottoms of the infralittoral photic zone with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A5.111
A5.112 Baltic gravel banks of the infralittoral photic zone Quick edit Valid 2014-01-31 A5.112
A5.113 Baltic shell gravel bottoms in the infralittoral photic zone Quick edit Valid 2014-01-31 A5.113
A5.114 Baltic gravel bottoms of the aphotic zone Quick edit Valid 2014-01-31 A5.114
A5.115 Baltic shell gravel bottoms of the aphotic zone Quick edit Valid 2014-01-31 A5.115
A5.12 Sublittoral coarse sediment in variable salinity (estuaries) Quick edit Valid 2014-01-31 A5.12
A5.13 Infralittoral coarse sediment Quick edit Valid 2014-01-31 A5.13
A5.131 Sparse fauna on highly mobile sublittoral shingle (cobbles and pebbles) Quick edit Valid 2014-01-31 A5.131
A5.132 [Halcampa chrysanthellum] and [Edwardsia timida] on sublittoral clean stone gravel Quick edit Valid 2014-01-31 A5.132
A5.133 [Moerella] spp. with venerid bivalves in infralittoral gravelly sand Quick edit Valid 2014-01-31 A5.133
A5.134 [Hesionura elongata] and [Microphthalmus similis] with other interstitial polychaetes in infralittoral mobile coarse sand Quick edit Valid 2014-01-31 A5.134
A5.135 [Glycera lapidum] in impoverished infralittoral mobile gravel and sand Quick edit Valid 2014-01-31 A5.135
A5.136 Cumaceans and [Chaetozone setosa] in infralittoral gravelly sand Quick edit Valid 2014-01-31 A5.136
A5.137 Dense [Lanice conchilega] and other polychaetes in tide-swept infralittoral sand and mixed gravelly sand Quick edit Valid 2014-01-31 A5.137
A5.138 Association with rhodolithes in coarse sands and fine gravels mixed by waves Quick edit Valid 2014-01-31 A5.138
A5.139 Facies with [Gouania wildenowi] Quick edit Valid 2014-01-31 A5.139
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?