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 5,061 to 5,080.First250251252253254255256257Last
Id Label Status Status Modified Notation
H3.29 Central Hellenic [Potentilla] cliffs Quick edit Valid 2014-01-31 H3.29
H3.2A Illyrio-Helleno-Balkanic [Potentilla] cliffs Quick edit Valid 2014-01-31 H3.2A
H3.2A1 Helleno-Balkanic calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A1
H3.2A11 Pelagonide calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A11
H3.2A12 Rhodopide calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A12
H3.2A121 Pirin calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A121
H3.2A122 Rila calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A122
H3.2A123 Rhodope calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A123
H3.2A13 Balkan Range calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A13
H3.2A131 Balkan range ramonda cliffs Quick edit Valid 2014-01-31 H3.2A131
H3.2A132 Vrachansky karst chasmophyte communities Quick edit Valid 2014-01-31 H3.2A132
H3.2A2 Dinaro-Carpathian calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A2
H3.2A3 Moist Dinaric calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A3
H3.2A4 Balkano-Illyrian shaded calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2A4
H3.2B Lowland middle European calcareous cliff communities Quick edit Valid 2014-01-31 H3.2B
H3.2C Boreal calcareous cliff communities Quick edit Valid 2014-01-31 H3.2C
H3.2D Mediterraneo-Anatolian calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.2D
H3.2E Bare limestone inland cliffs Quick edit Valid 2014-01-31 H3.2E
H3.2E1 High altitude and arctic limestone cliffs Quick edit Valid 2014-01-31 H3.2E1
H3.2E2 Mountain limestone cliffs Quick edit Valid 2014-01-31 H3.2E2
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?