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 61 to 80.First12345678Last
Id Label Status Status Modified Notation
euProtectedAreaCode.AL538 KAVAJE Quick edit Valid - stable 2022-08-11 AL538
euProtectedAreaCode.AL539 KAVAJE Quick edit Valid - stable 2022-08-11 AL539
euProtectedAreaCode.AL540 DIVJAKE Quick edit Valid - stable 2022-08-11 AL540
euProtectedAreaCode.AL541 DIVJAKE Quick edit Valid - stable 2022-08-11 AL541
euProtectedAreaCode.AL542 DIVJAKE Quick edit Valid - stable 2022-08-11 AL542
euProtectedAreaCode.AL543 SEMAN Quick edit Valid - stable 2022-08-11 AL543
euProtectedAreaCode.AL544 SEMAN Quick edit Valid - stable 2022-08-11 AL544
euProtectedAreaCode.AL545 SEMAN Quick edit Valid - stable 2022-08-11 AL545
euProtectedAreaCode.AL546 GJIRI I LALZIT Quick edit Valid - stable 2022-08-11 AL546
euProtectedAreaCode.AL547 GJIRI I LALZIT Quick edit Valid - stable 2022-08-11 AL547
euProtectedAreaCode.AL701 VLORE Quick edit Valid - stable 2022-08-11 AL701
euProtectedAreaCode.AL702 VLORE Quick edit Valid - stable 2022-08-11 AL702
euProtectedAreaCode.AL703 VLORE Quick edit Valid - stable 2022-08-11 AL703
euProtectedAreaCode.AL704 VLORE Quick edit Valid - stable 2022-08-11 AL704
euProtectedAreaCode.AL705 VLORE Quick edit Valid - stable 2022-08-11 AL705
euProtectedAreaCode.AL706 VLORE Quick edit Valid - stable 2022-08-11 AL706
euProtectedAreaCode.AL707 VLORE Quick edit Valid - stable 2022-08-11 AL707
euProtectedAreaCode.AL708 VLORE Quick edit Valid - stable 2022-08-11 AL708
euProtectedAreaCode.AL709 VLORE Quick edit Valid - stable 2022-08-11 AL709
euProtectedAreaCode.AL710 VLORE Quick edit Valid - stable 2022-08-11 AL710
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?