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
adms:status Vocabulary
Released
  • Step 1
  • Step 2
  • Step 3
  • Step 4
  • Step 5
01 Oct 2015
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

Add new data elements

Mandatory
Mandatory
Optional
Optional
 

Vocabulary concepts

729 concepts found, displaying 441 to 460.First1920212223242526Last
Id Label Status Status Modified Notation
euSubUnitCode.DK2-2 ISEFJORD OG ROSKILDE FJORD Quick edit Deprecated - superseded 2019-09-10 DK2-2
euSubUnitCode.DK2-3 ØRESUND Quick edit Deprecated - superseded 2019-09-10 DK2-3
euSubUnitCode.DK2-4 KØGE BUGT Quick edit Deprecated - superseded 2019-09-10 DK2-4
euSubUnitCode.DK2-5 SMÅLANDSFARVANDET Quick edit Deprecated - superseded 2019-09-10 DK2-5
euSubUnitCode.DK2-6 ØSTERSØEN Quick edit Deprecated - superseded 2019-09-10 DK2-6
euSubUnitCode.DK3 BORNHOLM Quick edit Valid - stable 2019-09-10 DK3
euSubUnitCode.DK3-1 BORNHOLM Quick edit Deprecated - superseded 2019-09-10 DK3-1
euSubUnitCode.DK4 VIDAA-KRUSAA Quick edit Valid - stable 2019-09-10 DK4
euSubUnitCode.DK4-1 VIDAA-KRUSAA Quick edit Deprecated - superseded 2019-09-10 DK4-1
euSubUnitCode.EE1 LÄÄNE-EESTI VESIKOND Quick edit Valid - stable 2019-09-10 EE1
euSubUnitCode.EE2 IDA-EESTI VESIKOND Quick edit Valid - stable 2019-09-10 EE2
euSubUnitCode.EE3 KOIVA VESIKOND Quick edit Valid - stable 2019-09-10 EE3
euSubUnitCode.EL01 WESTERN PELOPONNESE Quick edit Valid - stable 2019-09-10 EL01
euSubUnitCode.EL02 NORTHERN PELOPONNESE Quick edit Valid - stable 2019-09-10 EL02
euSubUnitCode.EL03 EASTERN PELOPONNESE Quick edit Valid - stable 2019-09-10 EL03
euSubUnitCode.EL04 WESTERN STEREA ELLADA Quick edit Valid - stable 2019-09-10 EL04
euSubUnitCode.EL05 EPIRUS Quick edit Valid - stable 2019-09-10 EL05
euSubUnitCode.EL06 ATTICA Quick edit Valid - stable 2019-09-10 EL06
euSubUnitCode.EL07 EASTERN STEREA ELLADA Quick edit Valid - stable 2019-09-10 EL07
euSubUnitCode.EL08 THESSALIA Quick edit Valid - stable 2019-09-10 EL08
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?