You are here:
Eionet
Data Dictionary
Edit vocabulary

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

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

290 concepts found, displaying 201 to 220.First7891011121314Last
Id Label Status Status Modified Notation
1860 Laxå Quick edit Valid 2013-05-30 1860
1861 Hallsberg Quick edit Valid 2013-05-30 1861
1862 Degerfors Quick edit Valid 2013-05-30 1862
1863 Hällefors Quick edit Valid 2013-05-30 1863
1864 Ljusnarsberg Quick edit Valid 2013-05-30 1864
1880 Örebro Quick edit Valid 2013-05-30 1880
1881 Kumla Quick edit Valid 2013-05-30 1881
1882 Askersund Quick edit Valid 2013-05-30 1882
1883 Karlskoga Quick edit Valid 2013-05-30 1883
1884 Nora Quick edit Valid 2013-05-30 1884
1885 Lindesberg Quick edit Valid 2013-05-30 1885
1904 Skinnskatteberg Quick edit Valid 2013-05-30 1904
1907 Surahammar Quick edit Valid 2013-05-30 1907
1960 Kungsör Quick edit Valid 2013-05-30 1960
1961 Hallstahammar Quick edit Valid 2013-05-30 1961
1962 Norberg Quick edit Valid 2013-05-30 1962
1980 Västerås Quick edit Valid 2013-05-30 1980
1981 Sala Quick edit Valid 2013-05-30 1981
1982 Fagersta Quick edit Valid 2013-05-30 1982
1983 Köping Quick edit Valid 2013-05-30 1983
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?