Aquadiva - Data Dissemination Manual
This guide will walk you through the basics of using data dissemination.



1. Overview


The Data Dissemination Module, available via Setup (Cog button) and Export Metadata, provides a tool to export metadata to a standard compliant XML file. For every metadata structure in the system there is one tab in the tab strip.

The data grid in one tab shows all datasets belonging to the selected metadata structure.

2. Metadata Export

Select a checkbox to mark datasets you would like to export.

Please click the Export button and wait until the metadata XML file has been created successfully and a download link is available in-line.



3. Mapping tool

In the mapping tool in BEXIS it is possible to set each metadata structure to predefined keys and party types (for more information about party types see the manual about parties).

  • Keys are attributes such as title or description.
  • Party types are defined objects such as persons, institutes, organization or workshops.

Advantages after mapping a metadata structure:

  1. When publishing a dataset, BEXIS must retrieve information from the metadata and convert it to the requested formats. The more keys and party types are defined, the better the information can be prepared for publication.
  2. In the BEXIS there are party types like people, project, etc.

    In the metadata form, according to the mapping, appropriate results are suggested. If a user encapsulates a person in the metadata form, all matching persons are made available for selection. This simplifies the input of metadata.


This image shows an overview of the existing Parties. In this case only one person and one exists.


Auto complete for projects.


Auto complete for persons.

3.1. Mapping Overview


The page is divided into 3 sections. The source is displayed on the left. The target is displayed on the right side. In the middle all created mappings are displayed.

3.1.1 Source and Target

Each side as a simple and complex block as also a free text search. Simple elements are example first name, last name or full name from a person. A Complex type can be a person.

img1   img1

3.1.2 Mapping

Mappings are connections between the source and the target. There are different connection possibilities between the simple attributes. Generally only the connection between two simple attributes is considered.

With the aid of a transformation rule, it is possible to cover a wide range of different cases. A transformation rule consists of a RegEx and a mask. With an example you can check the values and the expected result.

RegEx Documenation (mdsn)

3.2 Mapping Examples

Following is some examples of one to one, one to many and many to one mapping.

3.2.1 EXAMPLE one to one

This example creates a connection between 2 titles. All words are separated by a RegEx and then arranged differently via the mask.


3.2.2 EXAMPLE one to many

This example creates a connection between 1 name and a FirstName and LastName. In the transformation rule, the first and last names are separated from one another by a RegEx and then positioned in the mask via the variable.


3.2.3 EXAMPLE many to one

This example creates a connection between the FirstName and LastName by name. Here is no RegEx needed but the mask ordered from both variables.


3.3. Create a mapping

  1. Search a select for a simple or complex element from the source.
  2. Add Element to the mapping in the middle by clicking the orange arrow next to the element.
  3. Search a select for a simple or complex element from the target.
  4. Search a select for a simple or complex element from the target.
  5. Create the mapping by clicking the create button
  6. In the mapping container there are all available simple elements for this mapping. Draw a line by clicking on one simple element from the source side and drag it to a simple element on the target side.
  7. If needed, add RegEx and mask to the transformation rule. After entering values in the blocks
  8. Press save

4. Publishing a Dataset Version

It is possible to prepare the data for 2 brokers and a total of 3 data repositories.

  • Broker
    • GFBIO
    • Pensoft
  • Data Repositories
    • GFBIO – Collections
    • Pangaea
    • Pensoft

There is a limitation for Pensoft. All data prepared for Pensoft must be generated with the GBIF metadata structure.

It is only possible to prepare datasets if the metadata is valid.

4.1. Publish

The user can publish a dataset version if you go to the dataset and find the publish tab.

The dropdown is showing all available data center. Select on and the system try to convert the data and the metadata as defined in the submissionConfig.xml. If something fails a message will displayed.


There are two types of fails:

  1. The system is not able to convert the data.
  2. Metadata is not valid. This is a warning. You can go on but the metadata.xml in the zip ist not valid against the exported xsd schema



4.2. GBFIO

Via the GFBIO portal you can start a submission and publish your dataset. Depending on the subject of the data set, a suitable Data Repository is defined. There are different main Types.

  • Pangaea
  • Collections
  • ENA

Each data repository has different data requirements. BEXIS 2 offers an export for Pangea and Collections.

4.2.1 Collections

The data for the collections is stored in a zip file.

The following files can be found in the zip file.


  1. Schema - XSD Schema for the metadata
  2. Data.*** - Primary Data
  3. Data structure - Structure of the primary data
  4. Manifest File - General information’s about the Dataset
  5. Metadata - Metadata information’s about the dataset

4.2.2 Pangaea

For Pangea, the metadata and primary data are stored in a text file.