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,041 to 5,060.First249250251252253254255256Last
Id Label Status Status Modified Notation
H3.25 Alpine and sub-mediterranean chasmophyte communities Quick edit Valid 2014-01-31 H3.25
H3.251 Alpine calcareous cliff heliophile communities Quick edit Valid 2014-01-31 H3.251
H3.252 Middle-European calcareous fern cliffs Quick edit Valid 2014-01-31 H3.252
H3.253 Carpathian calcareous cliff heliophile communities Quick edit Valid 2014-01-31 H3.253
H3.26 Hellenic eumediterranean calcicolous chasmophyte communities Quick edit Valid 2014-01-31 H3.26
H3.27 Aegeo-east-Mediterranean basiphile chasmophyte communities Quick edit Valid 2014-01-31 H3.27
H3.271 Cretan chasmophyte communities Quick edit Valid 2014-01-31 H3.271
H3.2711 Western Cretan chasmophyte communities Quick edit Valid 2014-01-31 H3.2711
H3.2712 Eastern Cretan chasmophyte communities Quick edit Valid 2014-01-31 H3.2712
H3.2713 High-altitude Cretan chasmophyte communities Quick edit Valid 2014-01-31 H3.2713
H3.272 Karpathos chasmophyte communities Quick edit Valid 2014-01-31 H3.272
H3.273 Eastern Aegean chasmophyte communities Quick edit Valid 2014-01-31 H3.273
H3.274 Cyclades chasmophyte communities Quick edit Valid 2014-01-31 H3.274
H3.275 Northern Sporades chasmophyte communities Quick edit Valid 2014-01-31 H3.275
H3.276 Cyprian chasmophyte communities Quick edit Valid 2014-01-31 H3.276
H3.2761 Kyrenia chasmophyte communities Quick edit Valid 2014-01-31 H3.2761
H3.2762 Troodos limestone chasmophyte communities Quick edit Valid 2014-01-31 H3.2762
H3.2763 Troodos serpentine chasmophyte communities Quick edit Valid 2014-01-31 H3.2763
H3.2764 Kythrean chasmophyte communities Quick edit Valid 2014-01-31 H3.2764
H3.28 Southern Hellenic [Potentilla] cliffs Quick edit Valid 2014-01-31 H3.28
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?