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 96,341 to 96,360.First4,8144,8154,8164,8174,8184,8194,8204,821Last
Id Label Status Status Modified Notation
euProtectedAreaCode.PL177391 JEZIORO FLETNOWSKIE Quick edit Valid - stable 2022-08-11 PL177391
euProtectedAreaCode.PL177392 JEZIORO MARTWE Quick edit Valid - stable 2022-08-11 PL177392
euProtectedAreaCode.PL177393 JEZIORO ORCHOWE Quick edit Valid - stable 2022-08-11 PL177393
euProtectedAreaCode.PL177394 JEZIORO ORLE Quick edit Valid - stable 2022-08-11 PL177394
euProtectedAreaCode.PL177395 JEZIORO UDZIERZ Quick edit Valid - stable 2022-08-11 PL177395
euProtectedAreaCode.PL177396 JEZIORO TRZEBIDZKIE Quick edit Valid - stable 2022-08-11 PL177396
euProtectedAreaCode.PL177397 JEZIORO WIELKIE Quick edit Valid - stable 2022-08-11 PL177397
euProtectedAreaCode.PL177398 JEZIORSKO Quick edit Valid - stable 2022-08-11 PL177398
euProtectedAreaCode.PL177399 JOD?Y SIELECKIE Quick edit Valid - stable 2022-08-11 PL177399
euProtectedAreaCode.PL177400 KADZIELNIA Quick edit Valid - stable 2022-08-11 PL177400
euProtectedAreaCode.PL177402 KALWARIA PAC?AWSKA Quick edit Valid - stable 2022-08-11 PL177402
euProtectedAreaCode.PL177403 KAMERA Quick edit Valid - stable 2022-08-11 PL177403
euProtectedAreaCode.PL177404 KAMIE?-GRZYB Quick edit Valid - stable 2022-08-11 PL177404
euProtectedAreaCode.PL177405 KAMIE? NAD JA?LISKAMI Quick edit Valid - stable 2022-08-11 PL177405
euProtectedAreaCode.PL177406 KAMIENNA GÓRA Quick edit Valid - stable 2022-08-11 PL177406
euProtectedAreaCode.PL177407 KAMIONNA Quick edit Valid - stable 2022-08-11 PL177407
euProtectedAreaCode.PL177408 KANIA Quick edit Valid - stable 2022-08-11 PL177408
euProtectedAreaCode.PL177409 KANTOR STARY Quick edit Valid - stable 2022-08-11 PL177409
euProtectedAreaCode.PL177410 KANISTON Quick edit Valid - stable 2022-08-11 PL177410
euProtectedAreaCode.PL177411 KAMIENIEC Quick edit Valid - stable 2022-08-11 PL177411
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?