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:broadMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:prefLabel Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
24 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

342 concepts found, displaying 121 to 140.First345678910Last
Id Label Status Status Modified Notation
288 Kruunupyy / Kronoby Quick edit Valid 2013-05-30 288
289 Kuhmalahti Quick edit Valid 2013-05-30 289
290 Kuhmo Quick edit Valid 2013-05-30 290
291 Kuhmoinen Quick edit Valid 2013-05-30 291
295 Kumlinge Quick edit Valid 2013-05-30 295
297 Kuopio Quick edit Valid 2013-05-30 297
300 Kuortane Quick edit Valid 2013-05-30 300
301 Kurikka Quick edit Valid 2013-05-30 301
304 Kustavi / Gustavs Quick edit Valid 2013-05-30 304
305 Kuusamo Quick edit Valid 2013-05-30 305
309 Outokumpu Quick edit Valid 2013-05-30 309
310 Kylmäkoski Quick edit Valid 2013-05-30 310
312 Kyyjärvi Quick edit Valid 2013-05-30 312
316 Kärkölä Quick edit Valid 2013-05-30 316
317 Kärsämäki Quick edit Valid 2013-05-30 317
318 Kökar Quick edit Valid 2013-05-30 318
319 Köyliö / Kjulo Quick edit Valid 2013-05-30 319
320 Kemijärvi Quick edit Valid 2013-05-30 320
322 Kemiönsaari / Kimitoön Quick edit Valid 2013-05-30 322
398 Lahti / Lahtis Quick edit Valid 2013-05-30 398
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?