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
22 Nov 2024
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

138,317 concepts found, displaying 134,801 to 134,820.First6,7376,7386,7396,7406,7416,7426,7436,744Last
Id Label Status Status Modified Notation
euProtectedAreaCode.SESH14 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH14
euProtectedAreaCode.SESH15 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH15
euProtectedAreaCode.SESH16 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH16
euProtectedAreaCode.SESH18 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH18
euProtectedAreaCode.SESH23 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH23
euProtectedAreaCode.SESH24 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH24
euProtectedAreaCode.SESH28 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH28
euProtectedAreaCode.SESH35 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH35
euProtectedAreaCode.SESH36 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH36
euProtectedAreaCode.SESH43 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH43
euProtectedAreaCode.SESH44 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH44
euProtectedAreaCode.SESH45 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH45
euProtectedAreaCode.SESH47 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH47
euProtectedAreaCode.SESH48 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH48
euProtectedAreaCode.SESH52 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH52
euProtectedAreaCode.SESH53 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH53
euProtectedAreaCode.SESH56 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH56
euProtectedAreaCode.SESH57 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH57
euProtectedAreaCode.SESH58 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH58
euProtectedAreaCode.SESH59 NOTAPPLICABLE Quick edit Valid - stable 2025-01-29 SESH59
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?