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
22 Nov 2024
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

977 concepts found, displaying 361 to 380.First1516171819202122Last
Id Label Status Status Modified Notation
euRBDCode.BESCHELDE_VL INTERNATIONAL RIVER BASIN DISTRICT OF THE SCHELDT Quick edit Valid - stable 2021-06-17 BESCHELDE_VL
euRBDCode.BESEINE_RW INTERNATIONAL RIVER BASIN DISTRICT OF THE SEINE Quick edit Valid - stable 2021-06-17 BESEINE_RW
euRBDCode.BG1000 DANUBE Quick edit Valid - stable 2021-06-17 BG1000
euRBDCode.BG2000 BLACK SEA Quick edit Valid - stable 2021-06-17 BG2000
euRBDCode.BG3000 EAST AEGEAN Quick edit Valid - stable 2021-06-17 BG3000
euRBDCode.BG4000 WEST AEGEAN Quick edit Valid - stable 2021-06-17 BG4000
euRBDCode.CY001 CYPRUS Quick edit Valid - stable 2021-06-17 CY001
euRBDCode.CZ1000 DANUBE Quick edit Valid - stable 2021-06-17 CZ1000
euRBDCode.CZ5000 ELBE Quick edit Valid - stable 2021-06-17 CZ5000
euRBDCode.CZ6000 ODRA Quick edit Valid - stable 2021-06-17 CZ6000
euRBDCode.DE1000 DONAU BY Quick edit Valid - stable 2021-06-17 DE1000
euRBDCode.DE2000 HOCHRHEIN Quick edit Valid - stable 2021-06-17 DE2000
euRBDCode.DE3000 OBERE EMS EMSNORDRADDE HASE Quick edit Valid - stable 2021-06-17 DE3000
euRBDCode.DE4000 TIDEWESER Quick edit Valid - stable 2021-06-17 DE4000
euRBDCode.DE5000 SAALE OBERE MOLDAU BEROUNKA EGER UND UNTERE ELBE Quick edit Valid - stable 2021-06-17 DE5000
euRBDCode.DE6000 ODER Quick edit Valid - stable 2021-06-17 DE6000
euRBDCode.DE7000 MAAS Quick edit Valid - stable 2021-06-17 DE7000
euRBDCode.DE9500 EIDER Quick edit Valid - stable 2021-06-17 DE9500
euRBDCode.DE9610 SCHLEITRAVE Quick edit Valid - stable 2021-06-17 DE9610
euRBDCode.DE9650 WARNOWPEENE Quick edit Valid - stable 2021-06-17 DE9650
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?