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,661 to 95,680.First4,7804,7814,7824,7834,7844,7854,7864,787Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL115916 JEZIORO ?WI?TE Quick edit Valid - stable 2022-08-11 PL115916
euProtectedAreaCode.PL115917 JEZIORO ZDR?CZNO Quick edit Valid - stable 2022-08-11 PL115917
euProtectedAreaCode.PL115918 JOD?OWICE Quick edit Valid - stable 2022-08-11 PL115918
euProtectedAreaCode.PL115919 JOD?Y KARNIESZEWICKIE Quick edit Valid - stable 2022-08-11 PL115919
euProtectedAreaCode.PL115920 JOD?Y ?ASKIE IM. STANIS?AWA KOSTKI WISI?SKIEGO Quick edit Valid - stable 2022-08-11 PL115920
euProtectedAreaCode.PL115921 JOD?Y OLE?NICKIE Quick edit Valid - stable 2022-08-11 PL115921
euProtectedAreaCode.PL115922 JOD?Y OSTRZESZOWSKIE Quick edit Valid - stable 2022-08-11 PL115922
euProtectedAreaCode.PL115923 KACZE B?OTA Quick edit Valid - stable 2022-08-11 PL115923
euProtectedAreaCode.PL115924 KACZE ??GI Quick edit Valid - stable 2022-08-11 PL115924
euProtectedAreaCode.PL115925 KADY?SKI LAS Quick edit Valid - stable 2022-08-11 PL115925
euProtectedAreaCode.PL115926 KAJASÓWKA Quick edit Valid - stable 2022-08-11 PL115926
euProtectedAreaCode.PL115927 KALINIAK Quick edit Valid - stable 2022-08-11 PL115927
euProtectedAreaCode.PL115928 KALINOWA ??KA Quick edit Valid - stable 2022-08-11 PL115928
euProtectedAreaCode.PL115929 KALINOWO Quick edit Valid - stable 2022-08-11 PL115929
euProtectedAreaCode.PL115930 KALISZAK Quick edit Valid - stable 2022-08-11 PL115930
euProtectedAreaCode.PL115931 KA?ECKIE B?OTA Quick edit Valid - stable 2022-08-11 PL115931
euProtectedAreaCode.PL115932 KAMIENNA BUCZYNA Quick edit Valid - stable 2022-08-11 PL115932
euProtectedAreaCode.PL115933 KAMIE? MICHNIOWSKI Quick edit Valid - stable 2022-08-11 PL115933
euProtectedAreaCode.PL115934 KAMIE? ?L?SKI Quick edit Valid - stable 2022-08-11 PL115934
euProtectedAreaCode.PL115935 KANIGÓRA Quick edit Valid - stable 2022-08-11 PL115935
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?