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
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
hasIdentifierScheme Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Oct 2015
hasRelatedZone Quantitative
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
08 Feb 2016
hasSpecialisedZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
03 Nov 2015
hasZoneType Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
18 Oct 2016
inCountry Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
29 Aug 2014
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

99,985 concepts found, displaying 98,541 to 98,560.First4,9244,9254,9264,9274,9284,9294,9304,931Last
Id Label Status Status Modified Notation
euProtectedAreaCode.UK17800 COWES Quick edit Valid - stable 2019-11-05 UK17800
euProtectedAreaCode.UK17900 RYDE Quick edit Valid - stable 2019-11-05 UK17900
euProtectedAreaCode.UK18000 SEAGROVE Quick edit Valid - stable 2019-11-05 UK18000
euProtectedAreaCode.UK18100 ST HELENS Quick edit Valid - stable 2019-11-05 UK18100
euProtectedAreaCode.UK18200 BEMBRIDGE Quick edit Valid - stable 2019-11-05 UK18200
euProtectedAreaCode.UK18300 WHITECLIFF BAY Quick edit Valid - stable 2019-11-05 UK18300
euProtectedAreaCode.UK18350 YAVERLAND Quick edit Valid - stable 2019-11-05 UK18350
euProtectedAreaCode.UK18400 SANDOWN Quick edit Valid - stable 2019-11-05 UK18400
euProtectedAreaCode.UK18500 SHANKLIN Quick edit Valid - stable 2019-11-05 UK18500
euProtectedAreaCode.UK18600 VENTNOR Quick edit Valid - stable 2019-11-05 UK18600
euProtectedAreaCode.UK18700 CHRISTCHURCH HIGHCLIFFE CASTLE Quick edit Valid - stable 2019-11-05 UK18700
euProtectedAreaCode.UK18750 CHRISTCHURCH FRIAR S CLIFF Quick edit Valid - stable 2019-11-05 UK18750
euProtectedAreaCode.UK18800 CHRISTCHURCH AVON BEACH Quick edit Valid - stable 2019-11-05 UK18800
euProtectedAreaCode.UK18900 CHRISTCHURCH MUDEFORD SANDBANK EAST Quick edit Valid - stable 2019-11-05 UK18900
euProtectedAreaCode.UK19000 BOURNEMOUTH HENGISTBURY WEST Quick edit Valid - stable 2019-11-05 UK19000
euProtectedAreaCode.UK19020 BOURNEMOUTH SOUTHBOURNE Quick edit Valid - stable 2019-11-05 UK19020
euProtectedAreaCode.UK19030 BOURNEMOUTH FISHERMAN S WALK Quick edit Valid - stable 2019-11-05 UK19030
euProtectedAreaCode.UK19050 BOURNEMOUTH MANOR STEPS Quick edit Valid - stable 2019-11-05 UK19050
euProtectedAreaCode.UK19060 BOURNEMOUTH BOSCOMBE PIER Quick edit Valid - stable 2019-11-05 UK19060
euProtectedAreaCode.UK19100 BOURNEMOUTH PIER Quick edit Valid - stable 2019-11-05 UK19100
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?