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 161 to 180.First56789101112Last
Id Label Status Status Modified Notation
A2.222 Oligochaetes in littoral mobile sand Quick edit Valid 2014-01-31 A2.222
A2.2221 Oligochaetes in full salinity littoral mobile sand Quick edit Valid 2014-01-31 A2.2221
A2.2222 Oligochaetes in variable salinity littoral mobile sand Quick edit Valid 2014-01-31 A2.2222
A2.223 Amphipods and [Scolelepis] spp. in littoral medium-fine sand Quick edit Valid 2014-01-31 A2.223
A2.2231 [Scolelepis] spp. in littoral mobile sand Quick edit Valid 2014-01-31 A2.2231
A2.2232 [Eurydice pulchra] in littoral mobile sand Quick edit Valid 2014-01-31 A2.2232
A2.2233 [Pontocrates arenarius] in littoral mobile sand Quick edit Valid 2014-01-31 A2.2233
A2.23 Polychaete/amphipod-dominated fine sand shores Quick edit Valid 2014-01-31 A2.23
A2.231 Polychaetes in littoral fine sand Quick edit Valid 2014-01-31 A2.231
A2.2311 Polychaetes, including [Paraonis fulgens], in littoral fine sand Quick edit Valid 2014-01-31 A2.2311
A2.2312 Polychaetes and [Angulus tenuis] in littoral fine sand Quick edit Valid 2014-01-31 A2.2312
A2.2313 [Nephtys cirrosa]-dominated littoral fine sand Quick edit Valid 2014-01-31 A2.2313
A2.24 Polychaete/bivalve-dominated muddy sand shores Quick edit Valid 2014-01-31 A2.24
A2.241 [Macoma balthica] and [Arenicola marina] in muddy sand shores Quick edit Valid 2014-01-31 A2.241
A2.242 [Cerastoderma edule] and polychaetes in littoral muddy sand Quick edit Valid 2014-01-31 A2.242
A2.243 [Hediste diversicolor], [Macoma balthica] and [Eteone longa] in littoral muddy sand Quick edit Valid 2014-01-31 A2.243
A2.244 [Bathyporeia pilosa] and [Corophium arenarium] in littoral muddy sand Quick edit Valid 2014-01-31 A2.244
A2.245 [Lanice conchilega] in littoral sand Quick edit Valid 2014-01-31 A2.245
A2.25 Mediterranean and Pontic communities of mediolittoral sands Quick edit Valid 2014-01-31 A2.25
A2.251 Facies with [Ophelia bicornis] Quick edit Valid 2014-01-31 A2.251
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?