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 436,761 to 436,780.First21,83521,83621,83721,83821,83921,84021,84121,842Last
Id Label Status Status Modified Notation
euMonitoringSiteCode.UKSC000457 R ALMOND SEAFIELD Quick edit Valid - stable 2021-06-17 UKSC000457
euMonitoringSiteCode.UKSC000462 R ALMOND BIRDS MILL Quick edit Valid - stable 2021-06-17 UKSC000462
euMonitoringSiteCode.UKSC000467 RIVER ALMOND CRAIGIEHALL Quick edit Valid - stable 2021-06-17 UKSC000467
euMonitoringSiteCode.UKSC000471 HOW BURN AT CONFLUENCE WITH R ALMOND Quick edit Valid - stable 2021-06-17 UKSC000471
euMonitoringSiteCode.UKSC000474 FOULSHIELS BURN AT CONFLUENCE WITH ALMOND PREVIOUSLY BICKERTON CONFL Quick edit Valid - stable 2021-06-17 UKSC000474
euMonitoringSiteCode.UKSC000476 KILLANDEAN BURN AT CONFLUENCE WITH R ALMOND Quick edit Valid - stable 2021-06-17 UKSC000476
euMonitoringSiteCode.UKSC000502 DARMEAD LINN Quick edit Valid - stable 2021-06-17 UKSC000502
euMonitoringSiteCode.UKSC000529 TOWER BURN PITTENCRIEFF PARK R4223 Quick edit Valid - stable 2021-06-17 UKSC000529
euMonitoringSiteCode.UKSC000532 WATER OF LEITH AT JUNIPER GREEN Quick edit Valid - stable 2021-06-17 UKSC000532
euMonitoringSiteCode.UKSC000535 WATER OF LEITH AT COMELYBANK Quick edit Deprecated 2021-06-17 UKSC000535
euMonitoringSiteCode.UKSC000536 WATER OF LEITH ANDERSON PLACE Quick edit Valid - stable 2021-06-17 UKSC000536
euMonitoringSiteCode.UKSC000545 MURRAY BURN AT CONFLUENCE WITH WATER OF LEITH Quick edit Valid - stable 2021-06-17 UKSC000545
euMonitoringSiteCode.UKSC000582 S ESK D S REDSIDE BURN Quick edit Valid - stable 2021-06-17 UKSC000582
euMonitoringSiteCode.UKSC000583 S ESK D S GORE WATER Quick edit Deprecated 2021-06-17 UKSC000583
euMonitoringSiteCode.UKSC000586 S ESK AT DALKEITH COWBRIDGE GS Quick edit Valid - stable 2021-06-17 UKSC000586
euMonitoringSiteCode.UKSC000635 R ESK AT MUSSELBURGH GAUGING STATION Quick edit Valid - stable 2021-06-17 UKSC000635
euMonitoringSiteCode.UKSC000647 EAST PEFFER BURN PEFFERSIDE Quick edit Valid - stable 2021-06-17 UKSC000647
euMonitoringSiteCode.UKSC000666 GIFFORD WATER SLATEFORD Quick edit Valid - stable 2021-06-17 UKSC000666
euMonitoringSiteCode.UKSC000676 R TYNE EAST LINTON Quick edit Valid - stable 2021-06-17 UKSC000676
euMonitoringSiteCode.UKSC000699 BIEL WATER A1 RD BRIDGE CBS DUNBAR Quick edit Valid - stable 2021-06-17 UKSC000699
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?