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 601 to 620.First2728293031323334Last
Id Label Status Status Modified Notation
euProtectedAreaCode.ATPA39 PETTENBACHRINNE Quick edit Valid - stable 2022-08-11 ATPA39
euProtectedAreaCode.ATPA39W PETTENBACHRINNE Quick edit Deprecated - superseded 2022-08-11 ATPA39W
euProtectedAreaCode.ATPA3W NEUFELD Quick edit Deprecated - superseded 2022-08-11 ATPA3W
euProtectedAreaCode.ATPA4 WINDENER QUELLE Quick edit Valid - stable 2022-08-11 ATPA4
euProtectedAreaCode.ATPA40 GRAFENBUCH Quick edit Valid - stable 2022-08-11 ATPA40
euProtectedAreaCode.ATPA42W SCHAUNBURGLEITEN Quick edit Deprecated - superseded 2022-08-11 ATPA42W
euProtectedAreaCode.ATPA44 STEYR Quick edit Valid - stable 2022-08-11 ATPA44
euProtectedAreaCode.ATPA44W STEYR Quick edit Deprecated - superseded 2022-08-11 ATPA44W
euProtectedAreaCode.ATPA45 LEPPERSDORF (HEILQUELLE) Quick edit Valid - stable 2022-08-11 ATPA45
euProtectedAreaCode.ATPA45W LEPPERSDORF (HEILQUELLE) Quick edit Deprecated - superseded 2022-08-11 ATPA45W
euProtectedAreaCode.ATPA46 VÖCKLABRUCK Quick edit Valid - stable 2022-08-11 ATPA46
euProtectedAreaCode.ATPA46W VÖCKLABRUCK Quick edit Deprecated - superseded 2022-08-11 ATPA46W
euProtectedAreaCode.ATPA47 EISKARQUELLEN Quick edit Valid - stable 2022-08-11 ATPA47
euProtectedAreaCode.ATPA47W EISKARQUELLEN Quick edit Deprecated - superseded 2022-08-11 ATPA47W
euProtectedAreaCode.ATPA48 PERFUCHSBERGERAU Quick edit Valid - stable 2022-08-11 ATPA48
euProtectedAreaCode.ATPA48W PERFUCHSBERGERAU Quick edit Deprecated - superseded 2022-08-11 ATPA48W
euProtectedAreaCode.ATPA4W WINDENER QUELLE Quick edit Deprecated - superseded 2022-08-11 ATPA4W
euProtectedAreaCode.ATPA5 RAUM KLEYLEHOF Quick edit Valid - stable 2022-08-11 ATPA5
euProtectedAreaCode.ATPA51 REGALL OBERE JÖCHLEQUELLEN Quick edit Valid - stable 2022-08-11 ATPA51
euProtectedAreaCode.ATPA51W REGALL OBERE JÖCHLEQUELLEN Quick edit Deprecated - superseded 2022-08-11 ATPA51W
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?