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 102,401 to 102,420.First5,1175,1185,1195,1205,1215,1225,1235,124Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SE0441280000000069 SIBBARP BARNVIKEN Quick edit Deprecated - retired 2022-08-11 SE0441280000000069
euProtectedAreaCode.SE0441280000000072 RIBERSBORG KALLBADHUSET Quick edit Valid - stable 2022-08-11 SE0441280000000072
euProtectedAreaCode.SE0441280000004366 SCANIABADPLATSEN Quick edit Valid - stable 2022-08-11 SE0441280000004366
euProtectedAreaCode.SE0441280000004499 SUNDSPROMENADEN Quick edit Valid - stable 2022-08-11 SE0441280000004499
euProtectedAreaCode.SE0441282000000408 BORSTAHUSEN PIREN Quick edit Valid - stable 2022-08-11 SE0441282000000408
euProtectedAreaCode.SE0441282000000409 BORSTAHUSEN STRANDBYN Quick edit Valid - stable 2022-08-11 SE0441282000000409
euProtectedAreaCode.SE0441282000000410 LANDSKRONA Quick edit Deprecated - retired 2022-08-11 SE0441282000000410
euProtectedAreaCode.SE0441282000000411 KYRKBACKEN Quick edit Valid - stable 2022-08-11 SE0441282000000411
euProtectedAreaCode.SE0441282000000412 LANDSKRONA Quick edit Deprecated - retired 2022-08-11 SE0441282000000412
euProtectedAreaCode.SE0441282000000413 LANDSKRONA Quick edit Deprecated - retired 2022-08-11 SE0441282000000413
euProtectedAreaCode.SE0441282000000414 ALABODARNA NORRA Quick edit Valid - stable 2022-08-11 SE0441282000000414
euProtectedAreaCode.SE0441282000000415 LILL-OLAS BRYGGA SEMESTERBYN Quick edit Valid - stable 2022-08-11 SE0441282000000415
euProtectedAreaCode.SE0441282000004370 HALVMNEN Quick edit Deprecated - retired 2022-08-11 SE0441282000004370
euProtectedAreaCode.SE0441283000000310 RYDEBACK Quick edit Valid - stable 2022-08-11 SE0441283000000310
euProtectedAreaCode.SE0441283000000311 ORBY ANGAR Quick edit Valid - stable 2022-08-11 SE0441283000000311
euProtectedAreaCode.SE0441283000000313 RAA VALLAR Quick edit Valid - stable 2022-08-11 SE0441283000000313
euProtectedAreaCode.SE0441283000000314 HELSINGBORG Quick edit Deprecated - retired 2022-08-11 SE0441283000000314
euProtectedAreaCode.SE0441283000000316 VIKINGSTRAND Quick edit Valid - stable 2022-08-11 SE0441283000000316
euProtectedAreaCode.SE0441283000000317 LARODBADEN Quick edit Valid - stable 2022-08-11 SE0441283000000317
euProtectedAreaCode.SE0441283000000318 HITTARP Quick edit Valid - stable 2022-08-11 SE0441283000000318
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?