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 1,241 to 1,260.First5960616263646566Last
Id Label Status Status Modified Notation
B3.27 Rock stacks and islets above splash zone Quick edit Valid 2014-01-31 B3.27
B3.3 Rock cliffs, ledges and shores, with angiosperms Quick edit Valid 2014-01-31 B3.3
B3.31 Atlantic sea-cliff communities Quick edit Valid 2014-01-31 B3.31
B3.32 Vegetated Baltic gently sloping rocky shores and cliffs Quick edit Valid 2014-01-31 B3.32
B3.321 Baltic gently sloping limestone rocky shores with low vegetation Quick edit Valid 2014-01-31 B3.321
B3.322 Baltic gently sloping limestone rocky shores dominated by shrubs or trees Quick edit Valid 2014-01-31 B3.322
B3.323 Baltic gently sloping sandstone rocky shores with low vegetation Quick edit Valid 2014-01-31 B3.323
B3.324 Baltic gently sloping sandstone rocky shores dominated by shrubs or trees Quick edit Valid 2014-01-31 B3.324
B3.325 Baltic gently sloping crystalline bedrock shores with low vegetation Quick edit Valid 2014-01-31 B3.325
B3.326 Baltic gently sloping crystalline bedrock shores dominated by shrubs or trees Quick edit Valid 2014-01-31 B3.326
B3.327 Baltic coastal limestone cliffs and caves with low vegetation Quick edit Valid 2014-01-31 B3.327
B3.328 Baltic coastal limestone cliffs and caves dominated by shrubs or trees Quick edit Valid 2014-01-31 B3.328
B3.329 Baltic coastal sandstone cliffs and caves with low vegetation Quick edit Valid 2014-01-31 B3.329
B3.32A Baltic coastal sandstone cliffs and caves dominated by shrubs or trees Quick edit Valid 2014-01-31 B3.32A
B3.32B Baltic coastal crystalline bedrock cliffs and caves with low vegetation Quick edit Valid 2014-01-31 B3.32B
B3.32C Baltic coastal crystalline bedrock cliffs and caves dominated by shrubs or trees Quick edit Valid 2014-01-31 B3.32C
B3.33 Tethyan sea-cliff communities Quick edit Valid 2014-01-31 B3.33
B3.331 Western Tethyan sea-cliff communities Quick edit Valid 2014-01-31 B3.331
B3.332 Pontic sea-cliff communities Quick edit Valid 2014-01-31 B3.332
B3.3321 Western Pontic herbaceous sea-cliff communities Quick edit Valid 2014-01-31 B3.3321
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?