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
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 61 to 80.First12345678Last
Id Label Status Status Modified Notation
169 Jokioinen / Jockis Quick edit Valid 2013-05-30 169
170 Jomala Quick edit Valid 2013-05-30 170
171 Joroinen / Jorois Quick edit Valid 2013-05-30 171
172 Joutsa Quick edit Valid 2013-05-30 172
174 Juankoski Quick edit Valid 2013-05-30 174
176 Juuka Quick edit Valid 2013-05-30 176
177 Juupajoki Quick edit Valid 2013-05-30 177
178 Juva Quick edit Valid 2013-05-30 178
179 Jyväskylä Quick edit Valid 2013-05-30 179
181 Jämijärvi Quick edit Valid 2013-05-30 181
182 Jämsä Quick edit Valid 2013-05-30 182
186 Järvenpää / Träskända Quick edit Valid 2013-05-30 186
202 Kaarina / S:t Karins Quick edit Valid 2013-05-30 202
204 Kaavi Quick edit Valid 2013-05-30 204
205 Kajaani / Kajana Quick edit Valid 2013-05-30 205
208 Kalajoki Quick edit Valid 2010-01-01 208
211 Kangasala Quick edit Valid 2013-05-30 211
213 Kangasniemi Quick edit Valid 2013-05-30 213
214 Kankaanpää Quick edit Valid 2013-05-30 214
216 Kannonkoski Quick edit Valid 2013-05-30 216
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?