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 1,221 to 1,240.First5859606162636465Last
Id Label Status Status Modified Notation
B3.1131 [Verrucaria maura] and sparse barnacles on exposed littoral fringe rock Quick edit Valid 2014-01-31 B3.1131
B3.1132 [Verrucaria maura] on very exposed to very sheltered upper littoral fringe rock Quick edit Valid 2014-01-31 B3.1132
B3.114 [Blidingia] spp. on vertical littoral fringe chalk Quick edit Valid 2014-01-31 B3.114
B3.115 [Ulothrix flacca] and [Urospora] spp. on freshwater-influenced vertical littoral fringe soft rock Quick edit Valid 2014-01-31 B3.115
B3.116 Association with [Entophysalis deusta] and [Verrucaria amphibia] Quick edit Valid 2014-01-31 B3.116
B3.12 Rock stacks and islets above high tide level in splash zone Quick edit Valid 2014-01-31 B3.12
B3.2 Unvegetated rock cliffs, ledges, shores and islets Quick edit Valid 2014-01-31 B3.2
B3.21 High Arctic sea-cliffs and rocky shores Quick edit Valid 2014-01-31 B3.21
B3.22 Atlantic low Arctic sea-cliffs and rocky shores Quick edit Valid 2014-01-31 B3.22
B3.23 Temperate Atlantic sea-cliffs and rocky shores Quick edit Valid 2014-01-31 B3.23
B3.24 Unvegetated Baltic rocky shores and cliffs Quick edit Valid 2014-01-31 B3.24
B3.241 Baltic boulder beaches Quick edit Valid 2014-01-31 B3.241
B3.242 Baltic unvegetated gently sloping limestone rocky shores Quick edit Valid 2014-01-31 B3.242
B3.243 Baltic unvegetated gently sloping sandstone rocky shores Quick edit Valid 2014-01-31 B3.243
B3.244 Baltic unvegetated gently sloping crystalline bedrock shores Quick edit Valid 2014-01-31 B3.244
B3.245 Baltic unvegetated coastal limestone cliffs and caves Quick edit Valid 2014-01-31 B3.245
B3.246 Baltic unvegetated coastal sandstone cliffs and caves Quick edit Valid 2014-01-31 B3.246
B3.247 Baltic unvegetated coastal crystalline bedrock cliffs and caves Quick edit Valid 2014-01-31 B3.247
B3.25 Subtropical Atlantic sea-cliffs and rocky shores Quick edit Valid 2014-01-31 B3.25
B3.26 Mediterraneo-Pontic sea-cliffs and rocky shores Quick edit Valid 2014-01-31 B3.26
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?