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
owl:sameAs Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013
skos:exactMatch Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
30 Sep 2013

Add new data elements

Mandatory
Mandatory
Optional
Optional (forcefully equal to identifier in this vocabulary)
 

Vocabulary concepts

4,043 concepts found, displaying 2,881 to 2,900.First141142143144145146147148Last
Id Label Status Status Modified Notation
PL22 Slaskie Quick edit Valid 2013-09-25 PL22
PL224 Czestochowski Quick edit Valid 2013-09-25 PL224
PL225 Bielski Quick edit Valid 2013-09-25 PL225
PL226 Centralny slaski (NUTS 2003) Quick edit Valid 2013-09-25 PL226
PL227 Rybnicki Quick edit Valid 2013-09-25 PL227
PL228 Bytomski Quick edit Valid 2013-09-25 PL228
PL229 Gliwicki Quick edit Valid 2013-09-25 PL229
PL22A Katowicki Quick edit Valid 2013-09-25 PL22A
PL22B Sosnowiecki Quick edit Valid 2013-09-25 PL22B
PL22C Tyski Quick edit Valid 2013-09-25 PL22C
PL3 Region Wschodni (NUTS 2013) Quick edit Valid 2013-09-25 PL3
PL31 Lubelskie (NUTS 2013) Quick edit Valid 2013-09-25 PL31
PL311 Bialski (NUTS 2013) Quick edit Valid 2013-09-25 PL311
PL312 Chelmsko-zamojski (NUTS 2013) Quick edit Valid 2013-09-25 PL312
PL313 Lubelski (NUTS 2003) Quick edit Valid 2013-09-25 PL313
PL314 Lubelski (NUTS 2013) Quick edit Valid 2013-09-25 PL314
PL315 Pulawski (NUTS 2013) Quick edit Valid 2013-09-25 PL315
PL32 Podkarpackie (NUTS 2013) Quick edit Valid 2013-09-25 PL32
PL321 Rzeszowsko-tarnobrzeski (NUTS 2003) Quick edit Valid 2013-09-25 PL321
PL322 Krosniensko-przemyski (NUTS 2003) Quick edit Valid 2013-09-25 PL322
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?