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 901 to 920.First4243444546474849Last
Id Label Status Status Modified Notation
A5.5331 [Zostera marina]/[angustifolia] beds on lower shore or infralittoral clean or muddy sand Quick edit Valid 2014-01-31 A5.5331
A5.5332 Mediterranean and Pontic [Zostera noltii] beds Quick edit Valid 2014-01-31 A5.5332
A5.53321 Association with [Zostera noltii] in euryhaline and eurythermal environment Quick edit Valid 2014-01-31 A5.53321
A5.53322 Association with [Zostera noltii] on superficial muddy sands in sheltered waters Quick edit Valid 2014-01-31 A5.53322
A5.5333 Association with [Zostera marina] in euryhaline and eurythermal environment Quick edit Valid 2014-01-31 A5.5333
A5.5334 Mediterranean [Zostera hornemanniana] beds Quick edit Valid 2014-01-31 A5.5334
A5.534 [Ruppia] and [Zannichellia] communities Quick edit Valid 2014-01-31 A5.534
A5.5341 Middle European [Ruppia] and [Zannichellia] communities Quick edit Valid 2014-01-31 A5.5341
A5.5342 Tethyan marine [Ruppia] communities Quick edit Valid 2014-01-31 A5.5342
A5.5343 [Ruppia maritima] in reduced salinity infralittoral muddy sand Quick edit Valid 2014-01-31 A5.5343
A5.535 [Posidonia] beds Quick edit Valid 2014-01-31 A5.535
A5.5351 Ecomorphosis of striped [Posidonia oceanica] meadows Quick edit Valid 2014-01-31 A5.5351
A5.5352 Ecomorphosis of "barrier-reef" [Posidonia oceanica] meadows Quick edit Valid 2014-01-31 A5.5352
A5.5353 Facies of dead "mattes" of [Posidonia oceanica] without much epiflora Quick edit Valid 2014-01-31 A5.5353
A5.5354 Association with [Caulerpa prolifera] on [Posidonia] beds Quick edit Valid 2014-01-31 A5.5354
A5.54 Angiosperm communities in reduced salinity Quick edit Valid 2014-01-31 A5.54
A5.541 Vegetation of brackish waters dominated by [Phragmites australis] Quick edit Valid 2014-01-31 A5.541
A5.542 Association with [Potamogeton pectinatus] Quick edit Valid 2014-01-31 A5.542
A5.543 Vegetation of brackish waters dominated by [Ranunculus baudotii] Quick edit Valid 2014-01-31 A5.543
A5.544 Vegetation of brackish waters dominated by [Scirpus lacustris] or [Scirpus tabernaemontani] Quick edit Valid 2014-01-31 A5.544
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?