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

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

15 concepts found, displaying all concepts.
Id Label Status Status Modified Notation
countryCode countryCode Quick edit Valid 2015-10-30 countryCode
eionetGroundWaterBodyCode eionetGroundWaterBodyCode Quick edit Valid 2015-10-30 eionetGroundWaterBodyCode
eionetMonitoringSiteCode eionetMonitoringSiteCode Quick edit Valid 2015-10-30 eionetMonitoringSiteCode
eionetProtectedAreaCode eionetProtectedAreaCode Quick edit Valid 2015-10-30 eionetProtectedAreaCode
eionetRBDCode eionetRBDCode Quick edit Valid 2015-10-30 eionetRBDCode
eionetSubUnitCode eionetSubUnitCode Quick edit Valid 2015-10-30 eionetSubUnitCode
eionetSurfaceWaterBodyCode eionetSurfaceWaterBodyCode Quick edit Valid 2015-10-30 eionetSurfaceWaterBodyCode
euGroundWaterBodyCode euGroundWaterBodyCode Quick edit Valid 2015-10-30 euGroundWaterBodyCode
euMarineRegionCode Marine Region Code Quick edit Valid 2017-05-15 euMarineRegionCode
euMarineReportingUnitCode Marine Reporting Unit code Quick edit Valid 2019-10-02 euMarineReportingUnitCode
euMonitoringSiteCode euMonitoringSiteCode Quick edit Valid 2015-10-30 euMonitoringSiteCode
euProtectedAreaCode euProtectedAreaCode Quick edit Valid 2015-10-30 euProtectedAreaCode
euRBDCode euRBDCode Quick edit Valid 2015-10-30 euRBDCode
euSubUnitCode euSubUnitCode Quick edit Valid 2015-10-30 euSubUnitCode
euSurfaceWaterBodyCode euSurfaceWaterBodyCode Quick edit Valid 2015-10-30 euSurfaceWaterBodyCode
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?