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 41 to 60.First12345678Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AL518 DURRES Quick edit Valid - stable 2022-08-11 AL518
euProtectedAreaCode.AL519 DURRES Quick edit Valid - stable 2022-08-11 AL519
euProtectedAreaCode.AL520 DURRES Quick edit Valid - stable 2022-08-11 AL520
euProtectedAreaCode.AL521 DURRES Quick edit Valid - stable 2022-08-11 AL521
euProtectedAreaCode.AL522 GJIRI I LALEZIT Quick edit Valid - stable 2022-08-11 AL522
euProtectedAreaCode.AL523 GJIRI I LALEZIT Quick edit Valid - stable 2022-08-11 AL523
euProtectedAreaCode.AL524 GJIRI I LALEZIT Quick edit Valid - stable 2022-08-11 AL524
euProtectedAreaCode.AL525 KAVAJE Quick edit Valid - stable 2022-08-11 AL525
euProtectedAreaCode.AL526 KAVAJE Quick edit Valid - stable 2022-08-11 AL526
euProtectedAreaCode.AL527 KAVAJE Quick edit Valid - stable 2022-08-11 AL527
euProtectedAreaCode.AL528 KAVAJE Quick edit Valid - stable 2022-08-11 AL528
euProtectedAreaCode.AL529 KAVAJE Quick edit Valid - stable 2022-08-11 AL529
euProtectedAreaCode.AL530 KAVAJE Quick edit Valid - stable 2022-08-11 AL530
euProtectedAreaCode.AL531 KAVAJE Quick edit Valid - stable 2022-08-11 AL531
euProtectedAreaCode.AL532 KAVAJE Quick edit Valid - stable 2022-08-11 AL532
euProtectedAreaCode.AL533 KAVAJE Quick edit Valid - stable 2022-08-11 AL533
euProtectedAreaCode.AL534 KAVAJE Quick edit Valid - stable 2022-08-11 AL534
euProtectedAreaCode.AL535 KAVAJE Quick edit Valid - stable 2022-08-11 AL535
euProtectedAreaCode.AL536 KAVAJE Quick edit Valid - stable 2022-08-11 AL536
euProtectedAreaCode.AL537 KAVAJE Quick edit Valid - stable 2022-08-11 AL537
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?