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 101 to 120.First23456789Last
Id Label Status Status Modified Notation
A1.4114 [Cystoseira] spp. in eulittoral rockpools Quick edit Valid 2014-01-31 A1.4114
A1.412 Fucoids and kelp in deep eulittoral rockpools Quick edit Valid 2014-01-31 A1.412
A1.4121 [Sargassum muticum] in eulittoral rockpools Quick edit Valid 2014-01-31 A1.4121
A1.413 Seaweeds in sediment-floored eulittoral rockpools Quick edit Valid 2014-01-31 A1.413
A1.414 Hydroids, ephemeral seaweeds and [Littorina littorea] in shallow eulittoral mixed substrata pools Quick edit Valid 2014-01-31 A1.414
A1.415 Pontic eulittoral rockpools with green seaweeds ([Cladophora], [Ulva], [Enteromorpha]), [Mytilus], [Mytilaster], [Polybius], [Pachygrapsus] and small fish Quick edit Valid 2014-01-31 A1.415
A1.42 Communities of rockpools in the supralittoral zone Quick edit Valid 2014-01-31 A1.42
A1.421 Green seaweeds ([Enteromorpha] spp. and [Cladophora] spp.) in shallow upper shore rockpools Quick edit Valid 2014-01-31 A1.421
A1.422 Pontic deep upper shore rockpools with [Mytilus] and [Pachygrapsus] juveniles Quick edit Valid 2014-01-31 A1.422
A1.43 Brackish permanent pools in the geolittoral zone Quick edit Valid 2014-01-31 A1.43
A1.431 Eutrophic brackish permanent pools in the geolittoral zone Quick edit Valid 2014-01-31 A1.431
A1.432 Mesotrophic brackish permanent pools in the geolittoral zone Quick edit Valid 2014-01-31 A1.432
A1.433 Oligotrophic brackish permanent pools in the geolittoral zone Quick edit Valid 2014-01-31 A1.433
A1.44 Communities of littoral caves and overhangs Quick edit Valid 2014-01-31 A1.44
A1.441 Chrysophyceae and Haptophyceae on vertical upper littoral fringe soft rock Quick edit Valid 2014-01-31 A1.441
A1.442 Green algal films on upper and mid-shore cave walls and ceilings Quick edit Valid 2014-01-31 A1.442
A1.443 [Audouinella purpurea] and [Pilinia maritima] crusts on upper and mid-shore cave walls and ceilings Quick edit Valid 2014-01-31 A1.443
A1.444 [Audouinella purpurea] and [Cladophora rupestris] on upper to mid-shore cave walls Quick edit Valid 2014-01-31 A1.444
A1.445 [Verrucaria mucosa] and/or [Hildenbrandia rubra] on upper to mid shore cave walls Quick edit Valid 2014-01-31 A1.445
A1.446 Sponges and shade-tolerant red seaweeds on overhanging lower eulittoral bedrock and in cave entrances Quick edit Valid 2014-01-31 A1.446
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?