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 621 to 640.First2829303132333435Last
Id Label Status Status Modified Notation
euSubUnitCode.CZOHL OHRE - LOWER ELBE AND OTHER TRIBUTARIES OF THE ELBE Quick edit Valid - stable 2021-06-17 CZOHL
euSubUnitCode.DE1000 DONAU BY Quick edit Valid - stable 2021-06-17 DE1000
euSubUnitCode.DE2100 ALPENRHEINBODENSEE Quick edit Valid - stable 2021-06-17 DE2100
euSubUnitCode.DE2200 HOCHRHEIN Quick edit Valid - stable 2021-06-17 DE2200
euSubUnitCode.DE2300 OBERRHEIN Quick edit Valid - stable 2021-06-17 DE2300
euSubUnitCode.DE2380 NECKAR Quick edit Valid - stable 2021-06-17 DE2380
euSubUnitCode.DE2400 MAIN Quick edit Valid - stable 2021-06-17 DE2400
euSubUnitCode.DE2600 MOSELSAAR Quick edit Valid - stable 2021-06-17 DE2600
euSubUnitCode.DE2700 MITTELRHEIN Quick edit Valid - stable 2021-06-17 DE2700
euSubUnitCode.DE2800 NIEDERRHEIN Quick edit Valid - stable 2021-06-17 DE2800
euSubUnitCode.DE2900 DELTARHEIN Quick edit Valid - stable 2021-06-17 DE2900
euSubUnitCode.DE3100_3500_3600 OBERE EMS EMSNORDRADDE HASE Quick edit Valid - stable 2021-06-17 DE3100_3500_3600
euSubUnitCode.DE3800_3900_3990 LEDAJUEMME UNTERE EMS EMSAESTUAR Quick edit Valid - stable 2021-06-17 DE3800_3900_3990
euSubUnitCode.DE4100 WERRA Quick edit Valid - stable 2021-06-17 DE4100
euSubUnitCode.DE4200 FULDADIEMEL Quick edit Valid - stable 2021-06-17 DE4200
euSubUnitCode.DE4500 WESER Quick edit Valid - stable 2021-06-17 DE4500
euSubUnitCode.DE4800 ALLER Quick edit Valid - stable 2021-06-17 DE4800
euSubUnitCode.DE4880 LEINE Quick edit Valid - stable 2021-06-17 DE4880
euSubUnitCode.DE4900 TIDEWESER Quick edit Valid - stable 2021-06-17 DE4900
euSubUnitCode.DE5400 MULDEELBESCHWARZE ELSTER Quick edit Valid - stable 2021-06-17 DE5400
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?