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 201 to 220.First7891011121314Last
Id Label Status Status Modified Notation
A2.328 Pontic "camca" habitat of River Danube mouths Quick edit Valid 2014-01-31 A2.328
A2.33 Marine mud shores Quick edit Valid 2014-01-31 A2.33
A2.4 Littoral mixed sediments Quick edit Valid 2014-01-31 A2.4
A2.41 [Hediste diversicolor] dominated gravelly sandy mud shores Quick edit Valid 2014-01-31 A2.41
A2.411 [Hediste diversicolor] in littoral gravelly muddy sand and gravelly sandy mud Quick edit Valid 2014-01-31 A2.411
A2.4111 [Hediste diversicolor] and [Macoma balthica] in littoral gravelly mud Quick edit Valid 2014-01-31 A2.4111
A2.4112 [Hediste diversicolor] and [Scrobicularia plana] in littoral gravelly mud Quick edit Valid 2014-01-31 A2.4112
A2.4113 [Hediste diversicolor] and [Streblospio shrubsolii] in littoral gravelly sandy mud Quick edit Valid 2014-01-31 A2.4113
A2.4114 [Hediste diversicolor], cirratulids and [Tubificoides] spp. in littoral gravelly sandy mud Quick edit Valid 2014-01-31 A2.4114
A2.4115 [Hediste diversicolor] and [Corophium volutator] in littoral gravelly sandy mud Quick edit Valid 2014-01-31 A2.4115
A2.42 Species-rich mixed sediment shores Quick edit Valid 2014-01-31 A2.42
A2.421 Cirratulids and [Cerastoderma edule] in littoral mixed sediment Quick edit Valid 2014-01-31 A2.421
A2.43 Species-poor mixed sediment shores Quick edit Valid 2014-01-31 A2.43
A2.431 Barnacles and [Littorina] spp. on unstable eulittoral mixed substrata Quick edit Valid 2014-01-31 A2.431
A2.432 Pontic mixed sediment shores with ????? Quick edit Valid 2014-01-31 A2.432
A2.5 Coastal saltmarshes and saline reedbeds Quick edit Valid 2014-01-31 A2.5
A2.51 Saltmarsh driftlines Quick edit Valid 2014-01-31 A2.51
A2.511 Atlantic saltmarsh and drift rough grass communities Quick edit Valid 2014-01-31 A2.511
A2.512 Atlantic saltmarsh driftline annual communities Quick edit Valid 2014-01-31 A2.512
A2.513 Mediterranean saltmarsh driftlines Quick edit Valid 2014-01-31 A2.513
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?