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 401 to 420.First1718192021222324Last
Id Label Status Status Modified Notation
A3.135 Association with [Corallina elongata] and [Herposiphonia secunda] Quick edit Valid 2014-01-31 A3.135
A3.136 Mediterranean and Pontic association with [Corallina officinalis] Quick edit Valid 2014-01-31 A3.136
A3.137 Association with [Schottera nicaeensis] Quick edit Valid 2014-01-31 A3.137
A3.138 Pontic facies with [Petricola lithophaga] in very exposed vertical rock Quick edit Valid 2014-01-31 A3.138
A3.139 Pontic [Vermiliopsis infundibulum] biogenic rocks Quick edit Valid 2014-01-31 A3.139
A3.14 Encrusting algal communities Quick edit Valid 2014-01-31 A3.14
A3.15 Frondose algal communities (other than kelp) Quick edit Valid 2014-01-31 A3.15
A3.151 [Cystoseira] spp. on exposed infralittoral bedrock and boulders Quick edit Valid 2014-01-31 A3.151
A3.152 Pontic [Ulva rigida] communities on exposed infralittoral bedrock and boulders Quick edit Valid 2014-01-31 A3.152
A3.153 Pontic [Gelidium latifolium] communities on exposed infralittoral bedrock and boulders Quick edit Valid 2014-01-31 A3.153
A3.2 Atlantic and Mediterranean moderate energy infralittoral rock Quick edit Valid 2014-01-31 A3.2
A3.21 Kelp and red seaweeds (moderate energy infralittoral rock) Quick edit Valid 2014-01-31 A3.21
A3.211 [Laminaria digitata] on moderately exposed sublittoral fringe rock Quick edit Valid 2014-01-31 A3.211
A3.2111 [Laminaria digitata] on moderately exposed sublittoral fringe bedrock Quick edit Valid 2014-01-31 A3.2111
A3.2112 [Laminaria digitata] and under-boulder fauna on sublittoral fringe boulders Quick edit Valid 2014-01-31 A3.2112
A3.2113 [Laminaria digitata] and piddocks on sublittoral fringe soft rock Quick edit Valid 2014-01-31 A3.2113
A3.212 [Laminaria hyperborea] on tide-swept, infralittoral rock Quick edit Valid 2014-01-31 A3.212
A3.2121 [Laminaria hyperborea] forest, foliose red seaweeds and a diverse fauna on tide-swept upper infralittoral rock Quick edit Valid 2014-01-31 A3.2121
A3.2122 [Laminaria hyperborea] park with hydroids, bryozoans and sponges on tide-swept lower infralittoral rock Quick edit Valid 2014-01-31 A3.2122
A3.213 [Laminaria hyperborea] on tide-swept infralittoral mixed substrata Quick edit Valid 2014-01-31 A3.213
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?