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 4,981 to 5,000.First246247248249250251252253Last
Id Label Status Status Modified Notation
H2.6F Anatolian calcareous screes Quick edit Valid 2014-01-31 H2.6F
H2.6G Eastern Carpathian calcareous thermophilous screes Quick edit Valid 2014-01-31 H2.6G
H3 Inland cliffs, rock pavements and outcrops Quick edit Valid 2014-01-31 H3
H3.1 Acid siliceous inland cliffs Quick edit Valid 2014-01-31 H3.1
H3.11 Middle European montane siliceous cliffs Quick edit Valid 2014-01-31 H3.11
H3.111 Middle European high-altitude siliceous cliffs Quick edit Valid 2014-01-31 H3.111
H3.112 Hercynio-Alpine montane and collinar siliceous cliffs Quick edit Valid 2014-01-31 H3.112
H3.113 Hercynio-Alpine serpentine cliffs Quick edit Valid 2014-01-31 H3.113
H3.114 Carpathian montane siliceous cliffs Quick edit Valid 2014-01-31 H3.114
H3.12 Oro-Iberian siliceous cliffs Quick edit Valid 2014-01-31 H3.12
H3.121 Ibero-Carpetanian siliceous cliffs Quick edit Valid 2014-01-31 H3.121
H3.122 Nevadan siliceous cliffs Quick edit Valid 2014-01-31 H3.122
H3.13 Southwestern Alpine siliceous cliffs Quick edit Valid 2014-01-31 H3.13
H3.14 Cyrno-Sardinian montane and alpine cliffs Quick edit Valid 2014-01-31 H3.14
H3.15 Helleno-Carpatho-Balkanic [Silene] siliceous cliffs Quick edit Valid 2014-01-31 H3.15
H3.151 Southern Carpathian campion siliceous cliffs Quick edit Valid 2014-01-31 H3.151
H3.152 Carpatho-Balkano-Rhodopide campion siliceous cliffs Quick edit Valid 2014-01-31 H3.152
H3.153 Pelagonide campion siliceous cliffs Quick edit Valid 2014-01-31 H3.153
H3.16 Peri-Pyrenean montane siliceous cliffs Quick edit Valid 2014-01-31 H3.16
H3.17 Western Iberian siliceous cliffs Quick edit Valid 2014-01-31 H3.17
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?