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,921 to 2,940.First143144145146147148149150Last
Id Label Status Status Modified Notation
PL415 Miasto Poznan Quick edit Valid 2013-09-25 PL415
PL416 Kaliski Quick edit Valid 2013-09-25 PL416
PL417 Leszczynski Quick edit Valid 2013-09-25 PL417
PL418 Poznanski Quick edit Valid 2013-09-25 PL418
PL42 Zachodniopomorskie Quick edit Valid 2013-09-25 PL42
PL421 Szczecinski (NUTS 2003) Quick edit Valid 2013-09-25 PL421
PL422 Koszalinski (NUTS 2010) Quick edit Valid 2013-09-25 PL422
PL423 Stargardzki (NUTS 2010) Quick edit Valid 2013-09-25 PL423
PL424 Miasto Szczecin Quick edit Valid 2013-09-25 PL424
PL425 Szczecinski (NUTS 2010) Quick edit Valid 2013-09-25 PL425
PL426 Koszalinski Quick edit Valid 2015-01-08 PL426
PL427 Szczecinecko-pyrzycki Quick edit Valid 2015-01-08 PL427
PL428 Szczecinski Quick edit Valid 2015-01-08 PL428
PL43 Lubuskie Quick edit Valid 2013-09-25 PL43
PL431 Gorzowski Quick edit Valid 2013-09-25 PL431
PL432 Zielonogórski Quick edit Valid 2013-09-25 PL432
PL5 Makroregion Poludniowo-Zachodni Quick edit Valid 2013-09-25 PL5
PL51 Dolnoslaskie Quick edit Valid 2013-09-25 PL51
PL511 Jeleniogórsko-walbrzyski (NUTS 2003) Quick edit Valid 2013-09-25 PL511
PL512 Legnicki (NUTS 2003) Quick edit Valid 2013-09-25 PL512
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?