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 581 to 600.First2627282930313233Last
Id Label Status Status Modified Notation
euRBDCode.UKGI17 GIBRALTAR Quick edit Valid - stable 2021-06-17 UKGI17
euSubUnitCode.AT1001 DANUBE Quick edit Valid - stable 2021-06-17 AT1001
euSubUnitCode.AT1100 DANUBE Quick edit Deprecated - superseded 2021-06-17 AT1100
euSubUnitCode.AT1200 DANUBE Quick edit Deprecated - superseded 2021-06-17 AT1200
euSubUnitCode.AT1300 DANUBE Quick edit Deprecated - superseded 2021-06-17 AT1300
euSubUnitCode.AT1400 DANUBE Quick edit Deprecated - superseded 2021-06-17 AT1400
euSubUnitCode.AT1500 DANUBE Quick edit Deprecated - superseded 2021-06-17 AT1500
euSubUnitCode.AT1600 DANUBE Quick edit Deprecated - superseded 2021-06-17 AT1600
euSubUnitCode.AT2100 RHINE Quick edit Valid - stable 2021-06-17 AT2100
euSubUnitCode.AT5100 ELBE Quick edit Valid - stable 2021-06-17 AT5100
euSubUnitCode.BEESCAUT_RW INTERNATIONAL RIVER BASIN DISTRICT OF THE SCHELDT Quick edit Valid - stable 2021-06-17 BEESCAUT_RW
euSubUnitCode.BEESCAUT_SCHELDE_BR INTERNATIONAL SUB UNIT OF THE SCHELDT Quick edit Valid - stable 2021-06-17 BEESCAUT_SCHELDE_BR
euSubUnitCode.BEMAAS_VL INTERNATIONAL RIVER BASIN DISTRICT OF THE MEUSE Quick edit Valid - stable 2021-06-17 BEMAAS_VL
euSubUnitCode.BEMEUSE_RW INTERNATIONAL RIVER BASIN DISTRICT OF THE MEUSE Quick edit Valid - stable 2021-06-17 BEMEUSE_RW
euSubUnitCode.BENOORDZEE_FED BELGIUM COAST Quick edit Valid - stable 2021-06-17 BENOORDZEE_FED
euSubUnitCode.BERHIN_RW INTERNATIONAL RIVER BASIN DISTRICT OF THE RHINE Quick edit Valid - stable 2021-06-17 BERHIN_RW
euSubUnitCode.BESCHELDE_VL INTERNATIONAL RIVER BASIN DISTRICT OF THE SCHELDT Quick edit Valid - stable 2021-06-17 BESCHELDE_VL
euSubUnitCode.BESEINE_RW INTERNATIONAL RIVER BASIN DISTRICT OF THE SEINE Quick edit Valid - stable 2021-06-17 BESEINE_RW
euSubUnitCode.BG1000 DANUBE Quick edit Valid - stable 2021-06-17 BG1000
euSubUnitCode.BG2000 BLACK SEA Quick edit Valid - stable 2021-06-17 BG2000
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?