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
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
dct:isReplacedBy Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
dct:replaces Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Oct 2013
hasFeatureOfInterest Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
22 Nov 2024
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

440,076 concepts found, displaying 435,761 to 435,780.First21,78521,78621,78721,78821,78921,79021,79121,792Last
Id Label Status Status Modified Notation
euMonitoringSiteCode.UKGBNIGWNE112-Q LADY DIXON PARK Quick edit Valid - stable 2021-06-17 UKGBNIGWNE112-Q
euMonitoringSiteCode.UKGBNIGWNE113-Q NEWFORGE Quick edit Valid - stable 2021-06-17 UKGBNIGWNE113-Q
euMonitoringSiteCode.UKGBNIGWNE114-Q ORCHARDVILLE Quick edit Valid - stable 2021-06-17 UKGBNIGWNE114-Q
euMonitoringSiteCode.UKGBNIGWNE115-Q KNOCKMORE Quick edit Valid - stable 2021-06-17 UKGBNIGWNE115-Q
euMonitoringSiteCode.UKGBNIGWNE116-Q LISSUE Quick edit Valid - stable 2021-06-17 UKGBNIGWNE116-Q
euMonitoringSiteCode.UKGBNIGWNE12-C GLANBIA MAGHERALIN Quick edit Valid - stable 2021-06-17 UKGBNIGWNE12-C
euMonitoringSiteCode.UKGBNIGWNE13-C GLENBURN Quick edit Valid - stable 2021-06-17 UKGBNIGWNE13-C
euMonitoringSiteCode.UKGBNIGWNE14-C BELSIZE Quick edit Valid - stable 2021-06-17 UKGBNIGWNE14-C
euMonitoringSiteCode.UKGBNIGWNE15-C BALMORAL Quick edit Valid - stable 2021-06-17 UKGBNIGWNE15-C
euMonitoringSiteCode.UKGBNIGWNE17-C COMBER DEEP Quick edit Valid - stable 2021-06-17 UKGBNIGWNE17-C
euMonitoringSiteCode.UKGBNIGWNE19-C MCALPINES Quick edit Valid - stable 2021-06-17 UKGBNIGWNE19-C
euMonitoringSiteCode.UKGBNIGWNE20-C IDB Quick edit Valid - stable 2021-06-17 UKGBNIGWNE20-C
euMonitoringSiteCode.UKGBNIGWNE21-C PRITCHITTS BH1 Quick edit Valid - stable 2021-06-17 UKGBNIGWNE21-C
euMonitoringSiteCode.UKGBNIGWNE22-C KILKEEL Quick edit Valid - stable 2021-06-17 UKGBNIGWNE22-C
euMonitoringSiteCode.UKGBNIGWNE23-C RATHLIN Quick edit Valid - stable 2021-06-17 UKGBNIGWNE23-C
euMonitoringSiteCode.UKGBNIGWNE24-C CITY HOSPITAL Quick edit Valid - stable 2021-06-17 UKGBNIGWNE24-C
euMonitoringSiteCode.UKGBNIGWNE25-C DAVID KERR QUB Quick edit Valid - stable 2021-06-17 UKGBNIGWNE25-C
euMonitoringSiteCode.UKGBNIGWNE26-C MOUNT STEWART Quick edit Valid - stable 2021-06-17 UKGBNIGWNE26-C
euMonitoringSiteCode.UKGBNIGWNE27-C SCRABO Quick edit Valid - stable 2021-06-17 UKGBNIGWNE27-C
euMonitoringSiteCode.UKGBNIGWNE54-C BALLYHENRY Quick edit Valid - stable 2021-06-17 UKGBNIGWNE54-C
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?