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
 

Vocabulary concepts

106,312 concepts found, displaying 2,741 to 2,760.First134135136137138139140141Last
Id Label Status Status Modified Notation
euProtectedAreaCode.CH22096 LAC BRENET Quick edit Deprecated - retired 2022-08-11 CH22096
euProtectedAreaCode.CH22097 ETANG DU DUZILLET Quick edit Deprecated - retired 2022-08-11 CH22097
euProtectedAreaCode.CH24001 AARE MARZILI Quick edit Valid - stable 2022-08-11 CH24001
euProtectedAreaCode.CH24002 AARE LORRAINE Quick edit Valid - stable 2022-08-11 CH24002
euProtectedAreaCode.CH25001 HERMANCE PLAGE COTE EMBOUCHURE Quick edit Valid - stable 2022-08-11 CH25001
euProtectedAreaCode.CH25002 HERMANCE PLAGE Quick edit Valid - stable 2022-08-11 CH25002
euProtectedAreaCode.CH25003 ANIERE PLAGE Quick edit Valid - stable 2022-08-11 CH25003
euProtectedAreaCode.CH25004 ANIERE AVAL DEBARCADERE Quick edit Valid - stable 2022-08-11 CH25004
euProtectedAreaCode.CH25005 CORSIER PORT Quick edit Valid - stable 2022-08-11 CH25005
euProtectedAreaCode.CH25006 GABIULE Quick edit Deprecated - retired 2022-08-11 CH25006
euProtectedAreaCode.CH25007 SAVONNIERE AVAL Quick edit Valid - stable 2022-08-11 CH25007
euProtectedAreaCode.CH25008 PARC DE LA NYMPHE Quick edit Valid - stable 2022-08-11 CH25008
euProtectedAreaCode.CH25009 PORT-BLEU Quick edit Valid - stable 2022-08-11 CH25009
euProtectedAreaCode.CH25010 BELLERIVE DEBARCADERE Quick edit Valid - stable 2022-08-11 CH25010
euProtectedAreaCode.CH25011 POINTE A LA BISE Quick edit Valid - stable 2022-08-11 CH25011
euProtectedAreaCode.CH25012 BELOTTE Quick edit Valid - stable 2022-08-11 CH25012
euProtectedAreaCode.CH25013 RUTH Quick edit Deprecated - retired 2022-08-11 CH25013
euProtectedAreaCode.CH25014 AVAL TOUR CARREE Quick edit Valid - stable 2022-08-11 CH25014
euProtectedAreaCode.CH25015 PORT-TUNNEL Quick edit Valid - stable 2022-08-11 CH25015
euProtectedAreaCode.CH25016 GENEVE-PLAGE Quick edit Valid - stable 2022-08-11 CH25016
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?