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 141 to 160.First4567891011Last
Id Label Status Status Modified Notation
399 Laihia / Laihela Quick edit Valid 2013-05-30 399
400 Laitila Quick edit Valid 2013-05-30 400
402 Lapinlahti Quick edit Valid 2013-05-30 402
403 Lappajärvi Quick edit Valid 2013-05-30 403
405 Lappeenranta / Villmanstrand Quick edit Valid 2010-01-01 405
407 Lapinjärvi / Lappträsk Quick edit Valid 2013-05-30 407
408 Lapua / Lappo Quick edit Valid 2013-05-30 408
410 Laukaa Quick edit Valid 2013-05-30 410
413 Lavia Quick edit Valid 2013-05-30 413
416 Lemi Quick edit Valid 2013-05-30 416
417 Lemland Quick edit Valid 2013-05-30 417
418 Lempäälä Quick edit Valid 2013-05-30 418
420 Leppävirta Quick edit Valid 2013-05-30 420
421 Lestijärvi Quick edit Valid 2013-05-30 421
422 Lieksa Quick edit Valid 2013-05-30 422
423 Lieto / Lundo Quick edit Valid 2013-05-30 423
425 Liminka / Limingo Quick edit Valid 2013-05-30 425
426 Liperi Quick edit Valid 2013-05-30 426
430 Loimaa Quick edit Valid 2013-05-30 430
433 Loppi Quick edit Valid 2013-05-30 433
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?