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 3,061 to 3,080.First150151152153154155156157Last
Id Label Status Status Modified Notation
PT166 Pinhal Interior Sul (NUTS 2010) Quick edit Valid 2013-09-25 PT166
PT167 Serra da Estrela (NUTS 2010) Quick edit Valid 2013-09-25 PT167
PT168 Beira Interior Norte (NUTS 2010) Quick edit Valid 2013-09-25 PT168
PT169 Beira Interior Sul (NUTS 2010) Quick edit Valid 2013-09-25 PT169
PT16A Cova da Beira (NUTS 2010) Quick edit Valid 2013-09-25 PT16A
PT16B Oeste Quick edit Valid 2013-09-25 PT16B
PT16C Médio Tejo (NUTS 2010) Quick edit Valid 2013-09-25 PT16C
PT16D Região de Aveiro Quick edit Valid 2015-01-08 PT16D
PT16E Região de Coimbra Quick edit Valid 2015-01-08 PT16E
PT16F Região de Leiria Quick edit Valid 2015-01-08 PT16F
PT16G Viseu Dão Lafões Quick edit Valid 2015-01-08 PT16G
PT16H Beira Baixa Quick edit Valid 2015-01-08 PT16H
PT16I Médio Tejo Quick edit Valid 2015-01-08 PT16I
PT16J Beiras e Serra da Estrela Quick edit Valid 2015-01-08 PT16J
PT17 Área Metropolitana de Lisboa Quick edit Valid 2013-09-25 PT17
PT170 Área Metropolitana de Lisboa Quick edit Valid 2015-01-08 PT170
PT171 Grande Lisboa (NUTS 2010) Quick edit Valid 2013-09-25 PT171
PT172 Península de Setúbal (NUTS 2010) Quick edit Valid 2013-09-25 PT172
PT18 Alentejo Quick edit Valid 2013-09-25 PT18
PT181 Alentejo Litoral Quick edit Valid 2013-09-25 PT181
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?