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 95,921 to 95,940.First4,7934,7944,7954,7964,7974,7984,7994,800Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL124031 PILAWSKI GR?D Quick edit Valid - stable 2022-08-11 PL124031
euProtectedAreaCode.PL1240312214000001 KAP OW TECZA Quick edit Deprecated - retired 2022-08-11 PL1240312214000001
euProtectedAreaCode.PL124032 PILSKO Quick edit Valid - stable 2022-08-11 PL124032
euProtectedAreaCode.PL124033 PI?ACKIE WZGÓRZA Quick edit Valid - stable 2022-08-11 PL124033
euProtectedAreaCode.PL124034 PI?AKI Quick edit Valid - stable 2022-08-11 PL124034
euProtectedAreaCode.PL124035 PIONKI Quick edit Valid - stable 2022-08-11 PL124035
euProtectedAreaCode.PL124036 PIÓROPUSZNIKOWY JAR Quick edit Valid - stable 2022-08-11 PL124036
euProtectedAreaCode.PL124037 P?UTOWO Quick edit Valid - stable 2022-08-11 PL124037
euProtectedAreaCode.PL124038 P?U?NICA Quick edit Valid - stable 2022-08-11 PL124038
euProtectedAreaCode.PL124041 PNIEWSKI ?UG Quick edit Valid - stable 2022-08-11 PL124041
euProtectedAreaCode.PL124045 POD RYSIANK? Quick edit Valid - stable 2022-08-11 PL124045
euProtectedAreaCode.PL124046 PODGÓRZE Quick edit Valid - stable 2022-08-11 PL124046
euProtectedAreaCode.PL124047 PODLESIE Quick edit Valid - stable 2022-08-11 PL124047
euProtectedAreaCode.PL124048 PODZAMCZE Quick edit Valid - stable 2022-08-11 PL124048
euProtectedAreaCode.PL124049 POGORZELCE Quick edit Valid - stable 2022-08-11 PL124049
euProtectedAreaCode.PL124050 POLANA POLICHNO Quick edit Valid - stable 2022-08-11 PL124050
euProtectedAreaCode.PL124051 POLESIE KONSTANTYNOWSKIE Quick edit Valid - stable 2022-08-11 PL124051
euProtectedAreaCode.PL124052 POMIECHÓWEK Quick edit Valid - stable 2022-08-11 PL124052
euProtectedAreaCode.PL124053 POMORZE Quick edit Valid - stable 2022-08-11 PL124053
euProtectedAreaCode.PL124054 PONTY IM. TEODORA ZIELI?SKIEGO Quick edit Valid - stable 2022-08-11 PL124054
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?