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 741 to 760.First3435363738394041Last
Id Label Status Status Modified Notation
A5.273 Baltic sandy bottoms of the aphotic zone Quick edit Valid 2014-01-31 A5.273
A5.28 Mediterranean communities of superficial muddy sands in sheltered waters Quick edit Valid 2014-01-31 A5.28
A5.281 Facies with [Callianassa tyrrhena] and [Kellia corbuloides] Quick edit Valid 2014-01-31 A5.281
A5.282 Facies with fresh water resurgences with [Cerastoderma glaucum] and [Cyathura carinata] Quick edit Valid 2014-01-31 A5.282
A5.283 Facies with [Loripes lacteus], [Tapes] spp. Quick edit Valid 2014-01-31 A5.283
A5.284 Association with [Caulerpa prolifera] on superficial muddy sands in sheltered waters Quick edit Valid 2014-01-31 A5.284
A5.285 Facies of hydrothermal oozes with [Cyclope neritea] and nematodes Quick edit Valid 2014-01-31 A5.285
A5.3 Sublittoral mud Quick edit Valid 2014-01-31 A5.3
A5.31 Sublittoral mud in low or reduced salinity Quick edit Valid 2014-01-31 A5.31
A5.311 Baltic brackish water sublittoral muddy biocenoses influenced by varying salinity Quick edit Valid 2014-01-31 A5.311
A5.3111 Baltic muds of the infralittoral photic zone with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A5.3111
A5.3112 Boreal Baltic narrow inlets with soft mud substrate Quick edit Valid 2014-01-31 A5.3112
A5.32 Sublittoral mud in variable salinity (estuaries) Quick edit Valid 2014-01-31 A5.32
A5.321 [Polydora ciliata] and [Corophium volutator] in variable salinity infralittoral firm mud or clay Quick edit Valid 2014-01-31 A5.321
A5.322 [Aphelochaeta marioni] and [Tubificoides] spp. in variable salinity infralittoral mud Quick edit Valid 2014-01-31 A5.322
A5.323 [Nephtys hombergii] and [Tubificoides] spp. in variable salinity infralittoral soft mud Quick edit Valid 2014-01-31 A5.323
A5.324 Infralittoral fluid mobile mud Quick edit Valid 2014-01-31 A5.324
A5.325 [Capitella capitata] and [Tubificoides] spp. in reduced salinity infralittoral muddy sediment Quick edit Valid 2014-01-31 A5.325
A5.326 Oligochaetes in variable or reduced salinity infralittoral muddy sediment Quick edit Valid 2014-01-31 A5.326
A5.327 [Limnodrilus hoffmeisteri], [Tubifex tubifex] and [Gammarus] spp. in low salinity infralittoral muddy sediment Quick edit Valid 2014-01-31 A5.327
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?