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 221 to 240.First89101112131415Last
Id Label Status Status Modified Notation
A2.514 [Elymus pycnanthus] with [Suaeda vera] or [Inula crithmoides] saltmarsh driftlines Quick edit Valid 2014-01-31 A2.514
A2.515 [Elymus repens] saltmarsh driftlines Quick edit Valid 2014-01-31 A2.515
A2.516 [Suaeda vera] saltmarsh driftlines Quick edit Valid 2014-01-31 A2.516
A2.517 [Suaeda vera] - [Limonium binervosum] saltmarsh driftlines Quick edit Valid 2014-01-31 A2.517
A2.518 [Spergularia marina] - [Puccinellia distans] saltmarsh driftlines Quick edit Valid 2014-01-31 A2.518
A2.519 [Frankenia laevis] - [Halimione portulacoides] saltmarsh driftlines Quick edit Valid 2014-01-31 A2.519
A2.51A [Inula crithmoides] on saltmarshes Quick edit Valid 2014-01-31 A2.51A
A2.51B [Sagina maritima] ephemeral salt marsh in sand Quick edit Valid 2014-01-31 A2.51B
A2.52 Upper saltmarshes Quick edit Valid 2014-01-31 A2.52
A2.521 Atlantic and Baltic brackish saltmarsh communities Quick edit Valid 2014-01-31 A2.521
A2.5211 Pearlwort-saltmarsh grass swards Quick edit Valid 2014-01-31 A2.5211
A2.5212 Baltic [Carex paleacea] swards Quick edit Valid 2014-01-31 A2.5212
A2.5213 Baltic [Carex mackenziei] swards Quick edit Valid 2014-01-31 A2.5213
A2.5214 Baltic salt basin [Agrostis]-[Triglochin] swards Quick edit Valid 2014-01-31 A2.5214
A2.5215 Baltic [Deschampsia bottnica] swards Quick edit Valid 2014-01-31 A2.5215
A2.522 Mediterranean [Juncus maritimus] and [Juncus acutus] saltmarshes Quick edit Valid 2014-01-31 A2.522
A2.523 Mediterranean short [Juncus], [Carex], [Hordeum] and [Trifolium] saltmeadows Quick edit Valid 2014-01-31 A2.523
A2.524 Mediterranean [Elymus] or [Artemisia] stands Quick edit Valid 2014-01-31 A2.524
A2.525 Mediterranean [Juncus subulatus] beds Quick edit Valid 2014-01-31 A2.525
A2.526 Mediterranean saltmarsh scrubs Quick edit Valid 2014-01-31 A2.526
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?