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 81 to 100.First12345678Last
Id Label Status Status Modified Notation
A1.3151 [Fucus serratus] on full salinity sheltered lower eulittoral rock Quick edit Valid 2014-01-31 A1.3151
A1.3152 [Fucus serratus] on full salinity lower eulittoral mixed substrata Quick edit Valid 2014-01-31 A1.3152
A1.316 Association with [Fucus virsoides] Quick edit Valid 2014-01-31 A1.316
A1.32 Fucoids in variable salinity Quick edit Valid 2014-01-31 A1.32
A1.321 [Pelvetia canaliculata] on sheltered variable salinity littoral fringe rock Quick edit Valid 2014-01-31 A1.321
A1.322 [Fucus spiralis] on sheltered variable salinity upper eulittoral rock Quick edit Valid 2014-01-31 A1.322
A1.323 [Fucus vesiculosus] on variable salinity mid eulittoral boulders and stable mixed substrata Quick edit Valid 2014-01-31 A1.323
A1.324 [Ascophyllum nodosum] and [Fucus vesiculosus] on variable salinity mid eulittoral rock Quick edit Valid 2014-01-31 A1.324
A1.325 [Ascophyllum nodosum] ecad. [mackaii] beds on extremely sheltered mid eulittoral mixed substrata Quick edit Valid 2014-01-31 A1.325
A1.326 [Fucus serratus] and large [Mytilus edulis] on variable salinity lower eulittoral rock Quick edit Valid 2014-01-31 A1.326
A1.327 [Fucus ceranoides] on reduced salinity eulittoral rock Quick edit Valid 2014-01-31 A1.327
A1.33 Red algal turf in lower eulittoral, sheltered from wave action Quick edit Valid 2014-01-31 A1.33
A1.34 Mediterranean communities of lower mediolittoral rock sheltered from wave action Quick edit Valid 2014-01-31 A1.34
A1.341 Association with [Enteromorpha compressa] Quick edit Valid 2014-01-31 A1.341
A1.4 Features of littoral rock Quick edit Valid 2014-01-31 A1.4
A1.41 Communities of littoral rockpools Quick edit Valid 2014-01-31 A1.41
A1.411 Coralline crust-dominated shallow eulittoral rockpools Quick edit Valid 2014-01-31 A1.411
A1.4111 Coralline crusts and [Corallina officinalis] in shallow eulittoral rockpools Quick edit Valid 2014-01-31 A1.4111
A1.4112 Coralline crusts and [Paracentrotus lividus] in shallow eulittoral rockpools Quick edit Valid 2014-01-31 A1.4112
A1.4113 [Bifurcaria bifurcata] in shallow eulittoral rockpools Quick edit Valid 2014-01-31 A1.4113
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?