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 701 to 720.First3233343536373839Last
Id Label Status Status Modified Notation
A5.232 [Sertularia cupressina] and [Hydrallmania falcata] on tide-swept sublittoral sand with cobbles or pebbles Quick edit Valid 2014-01-31 A5.232
A5.233 [Nephtys cirrosa] and [Bathyporeia] spp. in infralittoral sand Quick edit Valid 2014-01-31 A5.233
A5.234 Semi-permanent tube-building amphipods and polychaetes in sublittoral sand Quick edit Valid 2014-01-31 A5.234
A5.235 Mediterranean communities of fine sands in very shallow waters Quick edit Valid 2014-01-31 A5.235
A5.2351 Facies with [Lentidium mediterraneum] Quick edit Valid 2014-01-31 A5.2351
A5.236 Mediterranean communities of well sorted fine sands Quick edit Valid 2014-01-31 A5.236
A5.237 Pontic communities of well sorted fine sands Quick edit Valid 2014-01-31 A5.237
A5.2371 Pontic shallow fine sands with [Lentidium mediterraneum], [Cerastoderma glaucum], [Cyclope neritea] and amphipod tubes Quick edit Valid 2014-01-31 A5.2371
A5.2372 Pontic well sorted fine sands with [Lentidium mediterraneum], [Mya arenaria], [Anadara inaequivalvis] and [Crangon crangon] Quick edit Valid 2014-01-31 A5.2372
A5.2373 Pontic fine sands with [Donax venustus], [Lentidium mediterraneum] and [Lucinella divaricata] Quick edit Valid 2014-01-31 A5.2373
A5.2374 Pontic shallow clean fine sands with [Chamelea gallina], [Lentidium mediterraneum] and [Divaricella divaricata] Quick edit Valid 2014-01-31 A5.2374
A5.2375 Pontic fine sands with [Loripes lacteus], [Pestarella candida] and [Tellina tenuis ] Quick edit Valid 2014-01-31 A5.2375
A5.2376 Pontic fine sands with [Lucinella divaricata], [Abra alba] and [Upogebia pusilla] Quick edit Valid 2014-01-31 A5.2376
A5.2377 Pontic fine sands with [Arenicola marina] Quick edit Valid 2014-01-31 A5.2377
A5.2378 Pontic fine sands with [Chamelea gallina], [Cyclope neritea] and [Nassarius nitidus] Quick edit Valid 2014-01-31 A5.2378
A5.2379 Pontic fine sands with [Solen marginatus] Quick edit Valid 2014-01-31 A5.2379
A5.237A Pontic fine sand with [Anadara inequivalvis] Quick edit Valid 2014-01-31 A5.237A
A5.237B Pontic fine and muddy sands with [Mya arenaria] Quick edit Valid 2014-01-31 A5.237B
A5.24 Infralittoral muddy sand Quick edit Valid 2014-01-31 A5.24
A5.241 [Echinocardium cordatum] and [Ensis] spp. in lower shore and shallow sublittoral slightly muddy fine sand Quick edit Valid 2014-01-31 A5.241
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?