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 361 to 380.First1516171819202122Last
Id Label Status Status Modified Notation
A2.852 Hydrolittoral sandy substrata: level bottoms dominated by macrophyte vegetation Quick edit Valid 2014-01-31 A2.852
A2.853 Hydrolittoral sandy substrata: bars Quick edit Valid 2014-01-31 A2.853
A2.854 Hydrolittoral sandy substrata: banks Quick edit Valid 2014-01-31 A2.854
A2.86 Hydrolittoral muddy substrata Quick edit Valid 2014-01-31 A2.86
A2.861 Hydrolittoral muddy substrata: with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A2.861
A2.862 Hydrolittoral muddy substrata: dominated by macrophyte vegetation Quick edit Valid 2014-01-31 A2.862
A2.87 Hydrolittoral mixed sediment substrata Quick edit Valid 2014-01-31 A2.87
A2.871 Hydrolittoral mixed sediment substrata: with little or no macrophyte vegetation Quick edit Valid 2014-01-31 A2.871
A2.872 Hydrolittoral mixed sediment substrata: dominated by macrophyte vegetation Quick edit Valid 2014-01-31 A2.872
A3 Infralittoral rock and other hard substrata Quick edit Valid 2014-01-31 A3
A3.1 Atlantic and Mediterranean high energy infralittoral rock Quick edit Valid 2014-01-31 A3.1
A3.11 Kelp with cushion fauna and/or foliose red seaweeds Quick edit Valid 2014-01-31 A3.11
A3.111 [Alaria esculenta] on exposed sublittoral fringe bedrock Quick edit Valid 2014-01-31 A3.111
A3.1111 [Alaria esculenta], [Mytilus edulis] and coralline crusts on very exposed sublittoral fringe bedrock Quick edit Valid 2014-01-31 A3.1111
A3.1112 [Alaria esculenta] and [Laminaria digitata] on exposed sublittoral fringe bedrock Quick edit Valid 2014-01-31 A3.1112
A3.112 [Alaria esculenta] forest with dense anemones and crustose sponges on extremely exposed infralittoral bedrock Quick edit Valid 2014-01-31 A3.112
A3.113 [Laminaria hyperborea] forest with a faunal cushion (sponges and polyclinids) and foliose red seaweeds on very exposed infralittoral rock Quick edit Valid 2014-01-31 A3.113
A3.114 Sparse [Laminaria hyperborea] and dense [Paracentrotus lividus] on exposed infralittoral limestone Quick edit Valid 2014-01-31 A3.114
A3.115 [Laminaria hyperborea] with dense foliose red seaweeds on exposed infralittoral rock Quick edit Valid 2014-01-31 A3.115
A3.1151 [Laminaria hyperborea] forest with dense foliose red seaweeds on exposed upper infralittoral rock Quick edit Valid 2014-01-31 A3.1151
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?