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,821 to 3,840.First188189190191192193194195Last
Id Label Status Status Modified Notation
UKI43 Haringey & Islington Quick edit Valid 2015-01-08 UKI43
UKI44 Lewisham & Southwark Quick edit Valid 2015-01-08 UKI44
UKI45 Lambeth Quick edit Valid 2015-01-08 UKI45
UKI5 Outer London - East and North East Quick edit Valid 2015-01-08 UKI5
UKI51 Bexley & Greenwich Quick edit Valid 2015-01-08 UKI51
UKI52 Barking & Dagenham and Havering Quick edit Valid 2015-01-08 UKI52
UKI53 Redbridge & Waltham Forest Quick edit Valid 2015-01-08 UKI53
UKI54 Enfield Quick edit Valid 2015-01-08 UKI54
UKI6 Outer London - South Quick edit Valid 2015-01-08 UKI6
UKI61 Bromley Quick edit Valid 2015-01-08 UKI61
UKI62 Croydon Quick edit Valid 2015-01-08 UKI62
UKI63 Merton, Kingston upon Thames & Sutton Quick edit Valid 2015-01-08 UKI63
UKI7 Outer London - West and North West Quick edit Valid 2015-01-08 UKI7
UKI71 Barnet Quick edit Valid 2015-01-08 UKI71
UKI72 Brent Quick edit Valid 2015-01-08 UKI72
UKI73 Ealing Quick edit Valid 2015-01-08 UKI73
UKI74 Harrow & Hillingdon Quick edit Valid 2015-01-08 UKI74
UKI75 Hounslow & Richmond upon Thames Quick edit Valid 2015-01-08 UKI75
UKI_J London, South East Quick edit Valid 2013-09-25 UKI_J
UKI_J1 London, Berkshire, Buckinghamshire and Oxfordshire Quick edit Valid 2013-09-25 UKI_J1
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?