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 341 to 360.First1415161718192021Last
Id Label Status Status Modified Notation
A2.72 Littoral mussel beds on sediment Quick edit Valid 2014-01-31 A2.72
A2.721 [Mytilus edulis] beds on littoral sediments Quick edit Valid 2014-01-31 A2.721
A2.7211 [Mytilus edulis] beds on littoral mixed substrata Quick edit Valid 2014-01-31 A2.7211
A2.7212 [Mytilus edulis] beds on littoral sand Quick edit Valid 2014-01-31 A2.7212
A2.7213 [Mytilus edulis] beds on littoral mud Quick edit Valid 2014-01-31 A2.7213
A2.73 Pontic [Ficopomatus enigmaticus] reefs Quick edit Valid 2014-01-31 A2.73
A2.8 Features of littoral sediment Quick edit Valid 2014-01-31 A2.8
A2.81 Methane seeps in littoral sediments Quick edit Valid 2014-01-31 A2.81
A2.82 Ephemeral green or red seaweeds (freshwater or sand-influenced) on mobile substrata Quick edit Valid 2014-01-31 A2.82
A2.821 Ephemeral green and red seaweeds on variable salinity and/or disturbed eulittoral mixed substrata Quick edit Valid 2014-01-31 A2.821
A2.83 Hydrolittoral stony substrata Quick edit Valid 2014-01-31 A2.83
A2.831 Hydrolittoral stony substrata: level bottoms with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A2.831
A2.832 Hydrolittoral stony substrata: level bottoms dominated by macrophyte vegetation Quick edit Valid 2014-01-31 A2.832
A2.833 Hydrolittoral stony substrata: reefs Quick edit Valid 2014-01-31 A2.833
A2.84 Hydrolittoral gravel substrata Quick edit Valid 2014-01-31 A2.84
A2.841 Hydrolittoral gravel substrata: level bottoms with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A2.841
A2.842 Hydrolittoral gravel substrata: level bottoms dominated by macrophyte vegetation Quick edit Valid 2014-01-31 A2.842
A2.843 Hydrolittoral gravel substrata: banks Quick edit Valid 2014-01-31 A2.843
A2.85 Hydrolittoral sandy substrata Quick edit Valid 2014-01-31 A2.85
A2.851 Hydrolittoral sandy substrata: level bottoms with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A2.851
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?