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 761 to 780.First3536373839404142Last
Id Label Status Status Modified Notation
A5.328 Pontic mud with [Spisula subtruncata], [Syndesmia fragilis], and [Cardium paucicostatum] in low and variable salinity Quick edit Valid 2014-01-31 A5.328
A5.33 Infralittoral sandy mud Quick edit Valid 2014-01-31 A5.33
A5.331 [Nephtys hombergii] and [Macoma balthica] in infralittoral sandy mud Quick edit Valid 2014-01-31 A5.331
A5.332 [Sagartiogeton undatus] and [Ascidiella aspersa] on infralittoral sandy mud Quick edit Valid 2014-01-31 A5.332
A5.333 [Mysella bidentata] and [Abra] spp. in infralittoral sandy mud Quick edit Valid 2014-01-31 A5.333
A5.334 [Melinna palmata] with [Magelona] spp. and [Thyasira] spp. in infralittoral sandy mud Quick edit Valid 2014-01-31 A5.334
A5.335 [Ampelisca] spp., [Photis longicaudata] and other tube-building amphipods and polychaetes in infralittoral sandy mud Quick edit Valid 2014-01-31 A5.335
A5.336 [Capitella capitata] in enriched sublittoral muddy sediments Quick edit Valid 2014-01-31 A5.336
A5.337 Pontic sandy mud with [Melinna palmata] Quick edit Valid 2014-01-31 A5.337
A5.338 Pontic sandy mud with [Abra alba], Cardiidae and [Mytilus] Quick edit Valid 2014-01-31 A5.338
A5.34 Infralittoral fine mud Quick edit Valid 2014-01-31 A5.34
A5.341 [Cerastoderma edule] with [Abra nitida] in infralittoral mud Quick edit Valid 2014-01-31 A5.341
A5.342 [Arenicola marina] in infralittoral mud Quick edit Valid 2014-01-31 A5.342
A5.343 [Philine aperta] and [Virgularia mirabilis] in soft stable infralittoral mud Quick edit Valid 2014-01-31 A5.343
A5.344 [Ocnus planci] aggregations on sheltered sublittoral muddy sediment Quick edit Valid 2014-01-31 A5.344
A5.345 [Astarte crenata] beneath high salinity cold polar water Quick edit Valid 2014-01-31 A5.345
A5.346 Oligochaetes in mobile mud Quick edit Valid 2014-01-31 A5.346
A5.347 Pontic mobile muds of the River Danube mouths Quick edit Valid 2014-01-31 A5.347
A5.35 Circalittoral sandy mud Quick edit Valid 2014-01-31 A5.35
A5.351 [Amphiura filiformis], [Mysella bidentata] and [Abra nitida] in circalittoral sandy mud Quick edit Valid 2014-01-31 A5.351
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?