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

210 concepts found, displaying 161 to 180.First4567891011Last
Id Label Status Status Modified Notation
162 Horjul Quick edit Valid 2013-05-30 162
163 Jezersko Quick edit Valid 2013-05-30 163
164 Komenda Quick edit Valid 2013-05-30 164
165 Kostel Quick edit Valid 2013-05-30 165
166 Križevci Quick edit Valid 2013-05-30 166
167 Lovrenc na Pohorju Quick edit Valid 2013-05-30 167
168 Markovci Quick edit Valid 2013-05-30 168
169 Miklavž na Dravskem polju Quick edit Valid 2013-05-30 169
170 Mirna Peč Quick edit Valid 2013-05-30 170
171 Oplotnica Quick edit Valid 2013-05-30 171
172 Podlehnik Quick edit Valid 2013-05-30 172
173 Polzela Quick edit Valid 2013-05-30 173
174 Prebold Quick edit Valid 2009-12-10 174
175 Prevalje Quick edit Valid 2013-05-30 175
176 Razkrižje Quick edit Valid 2013-05-30 176
177 Ribnica na Pohorju Quick edit Valid 2013-05-30 177
178 Selnica ob Dravi Quick edit Valid 2013-05-30 178
179 Sodražica Quick edit Valid 2013-05-30 179
180 Solčava Quick edit Valid 2013-05-30 180
181 Sveta Ana Quick edit Valid 2013-05-30 181
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?