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 501 to 520.First2223242526272829Last
Id Label Status Status Modified Notation
A3.343 [Polyides rotundus] and/or [Furcellaria lumbricalis] on reduced salinity infralittoral rock Quick edit Valid 2014-01-31 A3.343
A3.344 [Fucus ceranoides] and [Enteromorpha] spp. on low salinity infralittoral rock Quick edit Valid 2014-01-31 A3.344
A3.345 [Codium elisabethae], [Halopteris filicina] and coralline crusts on sheltered infralittoral bedrock Quick edit Valid 2014-01-31 A3.345
A3.346 Pontic association of green and red seaweeds [Enteromorpha], [Ulva] spp., [Porphyra] spp. on moderately exposed or sheltered infralittoral rock Quick edit Valid 2014-01-31 A3.346
A3.35 Faunal communities on low energy infralittoral rock Quick edit Valid 2014-01-31 A3.35
A3.36 Faunal communities on variable or reduced salinity infralittoral rock Quick edit Valid 2014-01-31 A3.36
A3.361 [Mytilus edulis] beds on reduced salinity infralittoral rock Quick edit Valid 2014-01-31 A3.361
A3.362 [Cordylophora caspia] and [Electra crustulenta] on reduced salinity infralittoral rock Quick edit Valid 2014-01-31 A3.362
A3.363 [Hartlaubella gelatinosa] and [Conopeum reticulum] on low salinity infralittoral mixed substrata Quick edit Valid 2014-01-31 A3.363
A3.4 Baltic exposed infralittoral rock Quick edit Valid 2014-01-31 A3.4
A3.5 Baltic moderately exposed infralittoral rock Quick edit Valid 2014-01-31 A3.5
A3.6 Baltic sheltered infralittoral rock Quick edit Valid 2014-01-31 A3.6
A3.7 Features of infralittoral rock Quick edit Valid 2014-01-31 A3.7
A3.71 Robust faunal cushions and crusts in surge gullies and caves Quick edit Valid 2014-01-31 A3.71
A3.711 Foliose seaweeds and coralline crusts in surge gully entrances Quick edit Valid 2014-01-31 A3.711
A3.712 Anemones, including [Corynactis viridis,] crustose sponges and colonial ascidians on very exposed or wave surged vertical infralittoral rock Quick edit Valid 2014-01-31 A3.712
A3.713 Crustose sponges and colonial ascidians with [Dendrodoa grossularia] or barnacles on wave-surged infralittoral rock Quick edit Valid 2014-01-31 A3.713
A3.714 [Dendrodoa grossularia] and [Clathrina coriacea] on wave-surged vertical infralittoral rock Quick edit Valid 2014-01-31 A3.714
A3.715 Crustose sponges on extremely wave-surged infralittoral cave or gully walls Quick edit Valid 2014-01-31 A3.715
A3.716 Coralline crusts in surge gullies and scoured infralittoral rock Quick edit Valid 2014-01-31 A3.716
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?