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 301 to 320.First1213141516171819Last
Id Label Status Status Modified Notation
A2.5428 [Plantago]-saltmarsh grass meadows Quick edit Valid 2014-01-31 A2.5428
A2.5429 [Limonium]-saltmarsh grass meadows Quick edit Valid 2014-01-31 A2.5429
A2.543 Mediterranean coastal-saltmarsh grass swards Quick edit Valid 2014-01-31 A2.543
A2.544 Lower shore arctic salt meadows Quick edit Valid 2014-01-31 A2.544
A2.545 [Halimione portulacoides] low-mid saltmarshes Quick edit Valid 2014-01-31 A2.545
A2.546 [Puccinellia maritima] low-mid saltmarshes Quick edit Valid 2014-01-31 A2.546
A2.547 Sub-communities of [Puccinellia maritima] saltmarsh with [Limonium vulgare] and [Armeria maritima]; [P. maritima] with [Glaux maritima] co-dominant in species-poor vegetation; [Puccinellia maritima] with [Plantago maritima] and/or [Armeria maritima] Quick edit Valid 2014-01-31 A2.547
A2.548 Annual [Salicornia], [Suaeda] and [Puccinellia maritima] low-mid saltmarshes Quick edit Valid 2014-01-31 A2.548
A2.55 Pioneer saltmarshes Quick edit Valid 2014-01-31 A2.55
A2.551 [Salicornia], [Suaeda] and [Salsola] pioneer saltmarshes Quick edit Valid 2014-01-31 A2.551
A2.5511 Biocenosis of beaches with slowly-drying wracks under glassworts Quick edit Valid 2014-01-31 A2.5511
A2.5512 [Suaeda maritima] pioneer saltmarshes Quick edit Valid 2014-01-31 A2.5512
A2.5513 [Salicornia] spp. pioneer saltmarshes Quick edit Valid 2014-01-31 A2.5513
A2.5514 [Salicornia veneta] swards Quick edit Valid 2014-01-31 A2.5514
A2.5515 Black Sea annual [Salicornia], [Suaeda] and [Salsola] saltmarshes Quick edit Valid 2014-01-31 A2.5515
A2.5516 Low-shore Mediterranean glasswort swards Quick edit Valid 2014-01-31 A2.5516
A2.552 Mediterranean coastal halo-nitrophilous pioneer communities Quick edit Valid 2014-01-31 A2.552
A2.553 Atlantic [Sagina maritima] communities Quick edit Valid 2014-01-31 A2.553
A2.554 Flat-leaved [Spartina] swards Quick edit Valid 2014-01-31 A2.554
A2.5541 [Spartina anglica] pioneer saltmarshes Quick edit Valid 2014-01-31 A2.5541
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?