DiversityWorkbench

Modules

The Diversity Workbench is a set of components for building and managing biodiversity information, each focusing on a specific domain. Each component can provide services to the other components. For example, DiversityAgents supplies information for other modules such as DiversityCollection and DiversityTaxonNames.

Module of the Diversity Workbench Description
Agents Administration of agents, i.e. persons and institutions, which should be documented, e.g. with their addresses
Collection Administration of the scientific collections and specimens within these collections
Descriptions Administration of the knowledge about descriptions of organisms and descriptions of any other item/element/entity
Exsiccatae Administration of bibliographical information and standardised abbreviations of botanical and mycological exsiccatae in a global index
Gazetteers A data collection to enable the linking of geographical records with the Getty Thesaurus of Geographical Names (TGN), the German GN250 database and other sources of geographical names
Projects Administration of (research) projects as well as data collections, data packages/datasets processed by other DWB modules
References Administration of bibliographic data for any kind of scientific publication
Sampling Plots Administration of individual sampling plots and assigned toponyms with their hierarchy
Scientific Terms Data collections of scientific terms from external sources (e.g. vegetation, stratigraphy, soil science), including terms used to describe specimen parts (e.g. bones) 
Taxon Names Administration of taxonomic names, their synonyms and hierarchical position

Main form

The main forms of all modules have a design as shown below

Main form

Status

In the status area, you will find

  • The name of the module
  • The name of the database if different from the module
  • The version of the software

The menu contains the options provided by the module

Commands

The commands area contains buttons for handling the data:

  • - To connect to a database, click the button.
  • - To save the changes in a dataset, click the button.
  • - To propagate the changes in a dataset to linked modules, click the button.
  • - To undo the changes in a dataset click the button. This will restore the original data unless the changes have been saved, or changes were done in certain tables or hierarchies where the data must be stored to display the hierarchy.
  • - To create a new entry in the database, click the  button below the search result listbox. This will create an entry with the specimen and display it in the list.
  • - To copy a specimen, select it from the list and click the button .
  • - To set options for a dataset click the button .
  • - To change the arrangement of the query click the button.

Podcast

Jan 14, 2025

Subsections of Modules

Diversity Agents

Scope of DiversityAgents within the Diversity Workbench

DiversityAgents is the module for the administration of agents within the Diversity Workbench. DiversityAgents provides information for other modules like DiversityCollection and DiversityTaxonNames. DiversityAgents keeps only data connected with the handling of agents. Data of other realms like e.g. projects or references are handled in separate modules. For an overview of the available modules see the image below. DiversityAgents might also be used as a stand-alone application.

Data managment sectors of the application

Sector Description
Agent A person, institution etc.
Contacts Contacts of an agent including address, phone number, e-mail etc.
Keyword Keywords characterizing the agent
Project The projects that a agent is a part of
Images Images related to the agent, e.g. a portrait
References The references related to the agent
Hierarchy Additional hierarchies of the agent, e.g. when an agent has contracts in several companies
Relations Relations of the agent, e.g. child of …
Descriptor Descriptors of the agent
Identifier IDs of the agents, e.g. ORCID
External sources Source where the data have been taken or relation to external soucres

Usage example

An agent with several contact addresses (office, private, mobile) is working for two institutions. This agent has been included in several projects and there are images of the agent. The agent has children working in one of the institution. The agent among other identifiers has an ORCID. The instituions where the agent is working for are described with predefined values.

Relations and connections between the various sectors

Main form of DiversityAgents

To start the application double click on DiversityAgents.exe.

The first time you start the application you have to configure the connection to the database (Connection, Server ... ) you want to work with. The header of your form allways shows you, with which database you are working, the version of the client, the database server and your login.

To see the descriptions for the fields of the database, simply move your mouse over it. A tooltip will appear with an explanation of the field.

Where you have to choose items from lists, type the beginning of the item name in the field and then click on the drop down button . This will start a query in the database and list the result in the combobox. If contents can be linked to an other module, click on the  button to start a query in this module.

Jan 24, 2025

Subsections of Agents

Diversity Agents

Download

Upcoming version

4.2.5

SQL Server 2016

For this version you need SQL Server 2016 or higher

  • New table JsonCache containing the data related to an agent as JSON. In the menu accessible via Administration → Json cache … or in the header click on the Show JsonCache button to see the json cache for the current agent.

Database updates

DiversityAgentsUpdate_020125_to_020126
  • JsonCache
    • New table JsonCache
    • New views JsonCache_FullAccess and JsonCache_Public
    • New procedure procFillJsonCache
    • trgUpdAgent - including update for JsonCache

Current version

4.2.4 (2024-07-30)

Download

  • Deleting selected agents
  • Removing selected agents from project

Updates in DWB Libraries

  • Import wizard with optional translation of \r\n in data into line break

Database updates

DiversityAgentsUpdate_020124_to_020125
  • New titles in AgentTitle_Enum
  • New gender diverse in AgentGender_Enum

Previous versions

4.2.3 (2024-06-25)

Download

  • Query: Inclusion of datawithholding and agent gender in query
  • Export wizard included
  • In data menu option to delete selected agents
  • In data menu option to remove selected agents from selected project

4.2.2 (2023-01-08)

Download

  • Editing of enumerations included
  • Bugfix saving data
  • Update of linked data in DiversityCollection and DiversityProjects Video starten
  • Showing first image in header
  • Bugfix client format
  • Images for descriptor types Video starten

 

4.2.1 (2023-07-12)

  • Button to show resp. get URL for Identifier

  • Help provided by online manual

  • Bugfix removing links to external data

  • Visibility of button for removal of synonymy depending on presence of synonymy

  • Showing synonym in interface for linked modules

  • Bugfix missing WebView-Runtimes

  • Database updates

    • 02.01.24: ProjectUser: Adding ReadOnly for locking a project;

4.2

Download (2023-05-08)

  • Bugfixes in Workbench.dll

 

4.1.41 (2023-05-03)

  • Adding query columns ValidFrom and ValidUntil

Datebase updates

  • 02.01.23: AgentContactInformation_Public - avoiding loops; Missing relation between [SynonymToAgentID] and [AgentID] in [dbo].[Agent]; Agent_Core: Adding column ValidFrom and ValidUntil; Missing descriptions;

 

4.1.40 (2023-04-05)

  • Bugfix query for partial available dates

 

4.1.39 (2023-04-03)

  • Hierarchy: ensure visibilty of selected agent
  • Additional query display column Identifier
  • Additional query restrictions for Identifier
  • Setting default for optimizing and remembering of query with context menu
  • New form for setting defaults and loading of linked server connections with start
  • Documentation of database improved
  • Several bugfixes for many order columns

4.1.34

  • Hierarchy: ensure visibilty of selected agent

4.1.35

  • Login administration: Enable setting read only for projects

4.1.36

  • Hierarchy: Ensure result despite loop, prevent building of new loops
  • Enable locking of projects
  • Ensure read only for locked and read only datasets
  • Images display reorganized and bugfix access
  • Login administration: Filter for names
  • Projects
    • Read only
    • Locked
  • Menu:
    • Reconnect to database
    • Client update

4.1.37

  • Contacts: Hiding display order for cumulative address
  • Hierarchies: Explizit message for loops and removal of loops
  • Table editors: Other hierarchies, References, Identifier, Descriptor and Relation added
  • Startup window added
  • Restriction of agent refill when needed
  • Button for removal of synonymy relation in case of loops
  • Button for setting of content language including images for main languages
  • Display of loop in hierarchy
  • Display of loop in synonymy
  • Bugfix adding contact information
  • Bugfix enabling controls according to ReadOnly status

4.1.38

  • Bugfix query for missing dates
  • Query:
    • Multicolumns in result list enabled
    • Query for dates for birth and death included
    • Remember query settings enabled
    • Optimizing enabled
    • Display columns added (Type, City, Country)

 

Datebase updates

  • 02.01.20: ProjectUser: new column [ReadOnly]; New view PublicIdentifier showing public content of AgentIdentifier; Table AgentDescriptor - FK for DescriptorType if missing;
  • 02.01.21: ProjectList: Add ReadOnly; Ensure result despite of loops for functions AgentChildNodes, AgentTopID, AgentHierarchyAllSuperior, AgentAddress and AgentHierarchy; ProjectProxy: new columns [RowGUID], [LastChanges], [IsLocked]; New views AgentID_FullAccess, AgentID_Locked, AgentID_ReadOnly and AgentID_AvailableReadOnly;
  • 02.01.22: new table LanguageCode_Enum; Table Agent - new column Language including Agent_log, trgDelAgent and trgUpdAgent; procInsertAgentCopy - new column ContentLanguage; AgentChildNodes - new column ContentLanguage; AgentHierarchy - new column ContentLanguage; AgentSynonymTopID - ensure result despite of loops; AgentSynonymyChildNodes - Optimized, ensure result despite of loops and new column ContentLanguage; AgentSynonymy - ensure result despite of loops and new column ContentLanguage; AgentSuperiorList - new column ContentLanguage; AgentTopID: ensure result despite of loops; AgentSuperiorList: ensure result despite of loops and not IgnoreButKeepForReference; AgentHierarchyAllSuperior: ensure result despite of loops;
  • 02.01.23 Missing descriptions for tables, trigger, views;

 

Libraries - DiversityWorkbench

The chapters below describe features that are available in several modules of the Diversity Workbench resp. provided via a shared library like DiversityWorkbench.dll

DiversityWorkbench

Upcoming version

4.2.13

  • Export wizard
    • Bugfix searching for parent of start table
  • Query
    • Bugfix when QueryMainTableLocal is null

Current version

4.2.12

  • Import wizard
    • Bugfixes for duplicate check if no data are available
  • Export wizard
    • Bugfixes if no data are available in parent table
    • Showing generated SQL commands

Previous versions

4.2.11

  • Import wizard
    • Bugfixes for duplicate check for data containing ’ in values of checked column
    • Bugfixes for column pre- and postfix containing ’ in values
    • Option to prevent insert into column
    • Description for columns expanded and redesigned
  • Bugfixes setting linked servers
  • JsonCache: New interface for the modules containing a json summary for datasets

4.2.10

  • Webservice Catalogue of Life available
  • Several bugfixes

4.2.9

  • UserControlQueryList: Dropdownwidth for column selection set to 200 to ensure readablility

4.2.8 (2023-08-30)

  • UserControlQueryList - bugfix if for readonly no valid boolean expression is returned
  • Documentation
    • Bugfix - Listing objects
    • Bugfix - Setting title
    • Bugfix - Selecting schema
    • Bugfix init HUGO replacements

4.2.7 (2023-08-17)

  • Formfunctions
    • Bugfix missing command in function public bool initSqlAdapter(ref System.Data.SqlClient.SqlDataAdapter Adapter, string SQL, System.Data.DataTable Table)
    • Bugfix WorkbenchUnit in function public static string getDatabaseNameFromURI(string URI)
    • Bugfix Project.cs - using ViewBaseURL instead of function or linked server
  • Archive
    • Optional inclusion of log tables
    • Bugfixes resetting database
    • Several bugfixes getting data
    • Several bugfixes restoring archive
    • Progress bars included
    • Extension for setting specific query to get IDs for temp table

4.2.6 (2023-08-01)

  • Documentation
    • Bugfix listing objects
    • HUGO
      • Export of enumeration table content
  • Updating depending datasets Video starten.
    • Context menu:
      • Adding current dataset.
      • Adding all datasets from the list.
      • Showing content of the list.
      • Clearing the list.
  • Bugfix setting backlinks for DiversityCollection linked to DiversityAgents
  • Bugfix setting SQL for backlink updates
  • Bugfix setting backlinks for DiversityProjects linked to DiversityAgents
  • Bugfix setting images in tree of FormEnumAdministration
  • FormFunctions: public static string IsoDate(string Text, bool SpaceAsSeparator = true, bool RestrictToDate = false) expanded with optional restriction to date

4.2.5 (2023-07-25)

  • TableEditor:
    • Bugfix in initForm
  • Enumeration administration:
    • Table editor included
  • Agent - Bugfix getting synonyms in unit values
  • Formfunctions - Autocompletion - Bugfix missing Alias for table
  • Documentation
    • HUGO
      • Export as markdown for HUGO included
      • Replacements and adaptions for HUGO included
  • Spreadsheet:
    • Optional inclusion of RowGUID for tables where PK should be edited Video starten
    • Hiding RowGUID by default

4.2.4 (2023-07-12)

  • FormFunctions:
    • public static string IsoDate(string Text, bool SpaceAsSeparator = true)
  • Documentation:
    • Default output set to HUGO
    • HUGO output
      • Index removed
      • Application objects removed
      • ER-diagram located underneath table header
      • Bugfix ER-diagram path
      • Bugfix Enum output
      • Include menu icon

WpfControls

Current version

1.0.1

  • Bugfix rescanning image if values for height and width are missing
  • Showing message for button ShowDetail if no detail is defined

Diversity Agents

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Jul 30, 2024

Diversity Agents

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.
Jul 30, 2024

Diversity Agents

Menu

  • Connection
    • Database Create database Create a new module database on the current server
    • Database Database Choose one of the databases available on the server. Only those databases will be listed to which the user has access permission
    •  Reconnect to database Reconnect to the current database
    • Module connections Edit the connections to the other modules within the current module.
    •  Transfer settings Transfer previous settings IP-Address and port of the server, name of the database, login etc. of a previous version of the client to the current version.
    •  Timeout Setting the timeouts.
      •  Timeout for database Setting the timeout for queries in the database.
      •  Timeout web requests Setting the timeout for web requests.
    •  Current server activity
    •  Quit Quit the application and stop all processes started by the application
  • Query
    • Show query Show or hide the query list
  • Data
    •  Archive
      •  Administrate archive Administrate the current archives
      •  Create archive Create a new archive
      •  Reset archive Reset the database resp. clear user tables
      •  Restore archive Restore an existing archive
      •  Create schema Create a schema of the database
    • Backup database Backup of the whole database
    • Export
      • CSV (bcp) Export data of the whole database as csv files
      • Export wizard
    •  Import
      •  Wizard
        •  Agent Import data from a tab separated text file
    • Table Editors Edit the data in single tables
      •  Agent
      •  Contact
      • Reference
      • Other hierarchy
      •  Identifier
      •  Descriptor
      •  Relation
    • Scan modules Scan modules for links to the current dataset
      • DiveristyCollection
      • DiveristyProject
      • DiveristyReferences
      • DiveristySamplingPlots
      • DiveristyScientificTerms
    • Remove agents Deleting the agents selected in the query results
    • Remove from project Removing the agents selected in the query results from the project selected in the query list
  • View
    • Show images Display the images of the agent
    • Show projects Display the projects related to the agent
  • Administration
    • Agent display types Administration of the agent Agent display types
    • Descriptor types Administration of the descriptor types
    •  Identifier Administration of the identifier types
    •  Database Administration of the database
      • Documentation Documentation of the structure of the database.
      • Logins Administration of the logins of the server their permissions in the databases
    •  Rename the current database
    • Setting the address published for links by other modules
    • SQL Tools: tools for managing the Tools database (SQL)
    • Setting the default projects for Default Projects the users
    • Setting the default projects for Default Project the current user
    • Download of the projects from DiversityProjects
    • Administration of external datasources
    • Setting the directory for the resources directory
  • Help
    • Manual Opens the online manual
    • Info Show the version of the program and corresponding information
    •  Errorlog
    •  Websites Websites related to DiversityAgents
      •  Download applications Download DiversityAgents from the website of the Diveristy Workbench project
      •  Information model Inspect the information model on the website of the Diveristy Workbench project
  • Update
    • Update database Update the database to the current version
    • Client Download the current version of the client

 

 

 

 

Jan 21, 2025

Diversity Agents

Tutorial

Training database

For the first steps we provide a training installation on:

training.diversityworkbench.de,5432

Please turn to the development team for a login.

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.

Editing

The main forms of all modules have a design as shown below

Main form

Status

In the status area you find

  • The name of the module,
  • The name of the database if different fron the module
  • The version of the software

The menu contains the options provided by the module

Commands

The commands area contains buttons for e.g. handling the data:

  • - To connect to a database click on the button.
  • - To save the changes in a dataset click on the button.
  • - To propagate the changes in a dataset to linked modules click on the button.
  • - To undo the changes a dataset click the button. This will recover the original data unless the changes had been saved or changes were done in certain tables or hierarchies were the data must be stored to display the hierarchy.
  • - To create a new entry in the database, click on the  button below the search result listbox. This will create a entry with the specimen and show it in the list.
  • - To copy a specimen, choose it from the list and click on the button .
  • - To options a dataset click on the button .
  • - To change the arrangement of the query click on the button.
Jul 30, 2024

Diversity Agents

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many colunns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Jul 30, 2024

Editing in Diversity Agents

The main forms of all modules have a design as shown below

Main form

Status

In the status area you find

  • The name of the module,
  • The name of the database if different fron the module
  • The version of the software

The menu contains the options provided by the module

Commands

The commands area contains buttons for e.g. handling the data:

  • - To connect to a database click on the button.
  • - To save the changes in a dataset click on the button.
  • - To propagate the changes in a dataset to linked modules click on the button.
  • - To undo the changes a dataset click the button. This will recover the original data unless the changes had been saved or changes were done in certain tables or hierarchies were the data must be stored to display the hierarchy.
  • - To create a new entry in the database, click on the  button below the search result listbox. This will create a entry with the specimen and show it in the list.
  • - To copy a specimen, choose it from the list and click on the button .
  • - To options a dataset click on the button .
  • - To change the arrangement of the query click on the button.

Agent Panel

The basic data for agents are entered in the upper part of the form (see image below).

The header of the form shows automatically the combined name of the agent created by the database according to the data, the ID in the database, the version of the dataset and the revision level. The version is set by the database and will be increased with every change in the data.

The JSON button will open a window showing the cached JSON data and the link will open a window showing the data available via the module interface.

History

To see the history of the changes within a dataset, click on the history button (see the history part for further details).

Withholding data

By default an agent is not available for publication. This is indicated by the red stop sign . If an agent should be published, click on the stop sign and remove all text in the withholding reason field. Any text, even white spaces, in the withholding reason field will prevent the publication of thie agent. The sign will change to a gray stop sign indicating the agent is now available for publication.  

Language

To set the language of the content, click on the language button . The ISO-639-1-Code for the selected language will be shown and the icon will change to a flag sign of the selected language.  

Synonymy

DiversityAgents can manage several representations of the same name resp. person. To link these entries you can declare one name a synonym of the other. An overview of the synonymy is shown in the Synonymy part (see below). The accepted name resp. the entry not declared to be a synonym is shown as the top of the hierachy. To change to a name within the synonymy, just double-click on it. 

 

To set the synonymy, click on the synonym button to open a window where you can search for the entry, the current entry should become a synonym of. In the field [Syn.type] set the type of the synonymy. The service of DiversityAgents is used by other modules. Therefore it must be avoided to delete datasets. Instead of deleting an entry, set it a synonym of a valid entry and set the type of the synonymy to replaced with. If an agent was replaced or declared a synonym, the synonym button will change to a search button . Click on this button to get to the dataset that replaced the current dataset resp. its synonym. If a dataset was replaced by another entry, the form will change as shown below.

 

Data

In the area below the header, you can enter resp. edit the data related to an agent. The available fields depend on the type of the agent that differ between persons and other types. If you enter inconsistent values for the dates, you will get a message reminding you to enter valid values.

Storage

The data of the agent are stored in the table Agent.

Jan 14, 2025

Subsections of Editing

Creating Diversity Agents

Create new agent

To create a new agent, click on the new-button above the search result listbox. You will be asked, if you are sure.

Click OK and a form will be show where the basic entries “agent type”, “First name” and “Last name” need to be given. By pressing the OK button the new agent will be created.

Forwarding changes to linked data

After changes to a dataset, the button will get a pink background if any part related to linked datasets is concerned. This relates to all dataset in the databases select for an update as described in chapter connections. To add the current dataset independed of changes to changes, choose Insert current ID in backlink list from the context menu. To insert all items from the query in the backlink list, click on the button. To check the content of the current backlink list select in the context menu. To clear the backlink list, select in the context menu. Provided the permission to update the respective tables you can forward the changes to datasets in linked modules with a click on the button as described in the tutorial Video starten

For further information see the chapter Editing

Delete agents

Warning

The service of DiversityAgents is used by other modules. Therefore it must be avoided to delete referenced datasets. Instead of deleting an agend, consider to set it to a synonym of a valid entry and set the type of the synonymy to replaced with.

To remove an agent you have 2 options:

  • Select the agent in the result list of the query and click on the delete button
  • Choose all agents in the result list of the query with a click on the
    select all
    button and choose Data - Remove agents from the menu
Tip

If the agents should only be removed from a project choose in the menu Data - Remove from project. This option will fail for agents with only one project. Agents will not be removed from the last project.

Dec 24, 2024

Diversity Agents

Data in tables

Besides of the main form, the Diversity Workbench provides 2 editors of the data in tabular form:

  • Table editors : Provide single table based access to the data of the query results in the main form
  • Spreadsheets : Provide predefined tabular access including the possibility to query and filter data and can be used as starting form

See a short tutorial for an introduction Video starten with DiversityCollection as an example (Grids are only available in DiversityCollection).

Comparison of tabular forms

Property Table editors Spreadsheets
Range One table Predefined selection of tables
Query Depending on main form Own query
Filter Restricted Direct query in database
Column sequence Fixed Fixed
Start form No Yes
Different versions No Yes
Read only projects No access Read only mode
Data in map No In TK25 sheet

 

Jul 30, 2024

Subsections of Tables

Diversity Agents

Spreadsheets

The spreadsheets similar to the grids provide a tabular access to the data. In addition you can search and filter data independent from the main form. For an introduction see two short tutorials Video starten (overview), Video starten (tables and columns). To open a spreadsheet, choose Grid - Spreadsheets - and then one of the provided versions, e.g. Organisms from the menu. A window as shown below will open where the data are marked and organized according to the database tables. If values in one of the tables are missing, this will be indicated with a grey background. The colors correspond to the overview for the database.

Start

To use any of the spreadsheets as a starting window, click on the  button. Now the application will directly open the spreadsheet with the same parameters when you close it. Video starten

 

Database

To change to another database, click on the button and choose the database as described here. Please keep in mind that the main form will connect to the new selected database. 

 

Project

If a user has read only projects available, a button will appear in front of the project. Click on this button to change to the list of projects with read only access. The window will change into the Read only mode (see below). To return to the list of projects with write access, just click no the button again. After changing the source for the project list, the project label will blink with red to remind you, to select a project from the list. Video starten

 

Getting the data

The data are always restricted to one project, selected in the corresponding field (see image above) and restricted to the first top lines as specified in the Max. res. field. To change to the next or previous block of data, use the resp. button. 

The program will organize the data in blocks indicated by the colors as shown above. In the example above the first block contains 2  Organisms all belonging to the block starting with  Hildesheim... for the Event and M-0014196 for the Specimen. The next block then starts with  Hildesheim... indicated by a change in the color containing 2 Organisms. For most of the spreadsheets, the presence of the Event in the data is a prerequisit. As long as you do not sort or filter the data (see below), these blocks will be consistent with the data. As soon as you filter or sort the data, these blocks may be split and may not correspond to the data blocks in the database any more. In the example below you see the effect of sorting by the column Taxon on breaking up the blocks. E.g. the block for the specimen M-0036950 is split into 2.

 

SQL

The query used for the retrieval of the data can be accessed with a click on the SQL button.

 

Filtering

To filter the content of a table you can apply a filter either on the whole table or on each of the columns of the table.

Table filter

This filter will apply on the whole table. Click in the black box next to the filter area and select one of the filter options as shown below.

  • : Filled (all visible columns)
  • : Empty (all visible columns)
  • : Data in table do exist
  • Ø: Data in table do not exist

Tutorial:

Column filter

Tutorial: Video starten

This filter will apply on a single column of a table. To set a filter click in the field underneath the column name. A window as shown below will open. With a click on the button you can enter a value from the current content of the column as filter.

Here you set the sorting (see below), enter the search string and choose among several ways of comparison with the contents in the database:

  • =: The content must be exactly like the given value
  • : The content must be different to the given value
  • ~: The content must be similar to the given value, use wildcards % for any string or _ for a single character
  • ¬: The content must NOT be similar to the given value, use wildcards % for any string or _ for a single character
  • <: The content must be smaller than the given value
  • >: The content must be bigger than the given value
  • |: The content must be in a given list of values
  • : The content must NOT be in a given list of values

For columns linked to modules of the DiversityWorkbench there may be additional options. E.g. for a column linked to DiversityTaxonNames you get 3 additional options:

  • +H: Include lower Hierarchy
  • +S: Include Synonyms
  • +H+S: Include lower Hierarchy and Synonyms

After selecting one of these options, you will be asked for the database and the project where the data should be taken from. In the next step the corresponding names as retrieved from the selected source will be listed (see below). To change the filter click on the button and on the button to remove it.

Sorting

↓↑ Tutorial: Video starten

The data can be sorted by each visible column. If you click into the field underneath the column name a window will open as described above. To change between the modes of sorting, just click on the current sorting. The modes are:

  • -: Not sorted
  • : Sorted in ascending sequence
  • : Sorted in descending sequence

After all parameters are set, the sort mode and filter settings will be shown in the field underneath the column name (see image below). The number indicates the sequence within the sorting columns.

 

Timeout

After all parameters are set, click on the button. If for any reason you get a timeout, meaning the query for the data takes too long, either simplify your query or adapt the time for the query after a click on the button. If you do not want to restrict the time for the queries, set the value to 0. The default value is 30 seconds. 

 

Read only mode

<> Tutorial: Video starten

The formatting of the sheet including the color indication of tables and data blocks is rather time consuming. If these are not needed, e.g. for exporting the data, you can switch to the Read only mode for higher performance. For projects with read only access (see above), the mode is automatically set to Read only

 

Editing

Video starten

To edit the data, just change them. If data are missing, type or select a value in the corresponding field. To remove data, click on the x field. This will remove all entries dependent on this entry that means all data right from the entry in the same line resp. block and any depending data. If there are any depending data, a window will open as shown below listing these data. Click OK if you want to remove the selected data including all depending data as shown in the window.

 

To change the content of several values in a column, either select the whole column with a click on the  button or select the fields manually. To avoid the pop-up of data-entry windows e.g. for columns with a lookup list, click no the button. Once you have selected the contents to change, select the mode of change:

  • Prepend: Insert the given value at the beginning of the content
  • Append: Append the given value at the end of the content
  • Overwrite: Remove current content and insert given value
  • Replace: Replace a string in the content with the given value
  • Clear: Remove the content

After selecting the change mode, enter the text in the field where necessary and click on the corresponding button to perform the changes.

With the context menu (mark area and right click) you can Remove data (for single data fields with a list behind), Tranfer or Copy the content into the clipboard and Insert the content of the clipboard into the selected cells. Tutorial: Video starten

Locked columns

Columns that can not be edited are indicated with a lighter background color of the header and a gray text of title and content. These columns contain e.g. database generated content or data from lookup tables.

Inclusion of RowGUID

By default the primary key can not be changed in the spreadsheet. In some cases you may want to change parts of the primary key. To do this, you must include the column RowGUID in the list of selected columns. The program will ensure that the changed data do not collide with existing data, that is having the same primary key. See an example in a short tutorial:

 

Fixed sources

Tutorial: Video starten

For columns that are linked to a remote module, you can fix the source for the query. If the source is fixed, the query will directly contact the source as shown in the image below. To set resp. change the source, click on the button. A window will open where you can select either a webservice or a source database together with a project within the database. To remove the source, click on the button (only visible if a source is present).

To see an overview for the fixed sources, click on the button. A window will open where all sources are listed with the source for the current column marked with a yellow background. 

 

A "right-click" on the button in the main form will show the settings as well and with a click on the button you can set the connection for the selected column. If a column depends on values from the data as for example the relations to the module DiversityTaxonNames with a dependence on the taxonomic group, the relation will change with the selected row, depending on the data retrieved from the selected row. If there is no connection to the related module defined, the button will appear gray and if the column has no relation to a module, the button will appear like

If the source is not fixed the query will start as described here.

Settings

- To change the data shown in the query results, either click on the header of the tables, e.g. Event for that table. A window as shown below will open where you can select or deselect columns, change their headers etc. Red columns need to be filled (either by the database, the program or the user). In the Alias field you can rename the columns to your preferences. The button will show a description of the columns. For columns linked to a module, the current settings for the link will be shown in addition to the description. To display a column in the sheet use the checkbox . If a column is needed, but should be hidden, select the checkbox. Displayed columns are indicated by a yellow background while hidden columns get a light yellow background. Certain columns are required (indicated by a purple color) and can not be removed e.g. if they are involved in a link to a remote module like in the example below the columns FamilyCache and OrderCache. Columns linked to a module are indicated by a blue color.

The button allows you to include one of the tables missing in the sheet (see image below). After selection of the table, select the column(s) you want to include in the sheet as shown in the image above.

To store resp. load settings, use the resp. button. If a setting file has been corrupted click on the button to remove it and restart with factory settings. The spreadsheet will always start with the previous settings. The location where the settings are stored are set under Administration - Resources directory ... . For an introduction see a short tutorial Video starten.

 

Column width

Tutorial: Video starten

The width of the columns can be set manually (in the filter area) or automatically with a click on the button. A window will open where you can choose and set the parameters for setting the column width.

 

Adding

Tutorial: Video starten

To add new data, use the area underneath the data table. You can enter preset values that will be used for the new data. If the new data should be added to existing entries, select the corresponding row. Then click on the + field of the datarange that should be inserted. If preset values are given, all corresponding tables will be filled together with the new inserted data. Defaults for the responsibles can be set under Administration - Customize Display. If a column is linked to a remote module, the corresponding columns will be filled together with the selection of the link, so e.g. if you select a link for a taxonomic name to a DiversityTaxonNames the columns for the taxon and if available the familiy etc. will be filled as well. To remove a linked value, select it a choose Remove from the context menu (right click).

Export

Tutorial: Video starten

To export the data as a tab separated text file (UTF8), click on the button. You will be asked if you want to include the hidden columns. These are the primary keys you may need for statistic evaluations etc.

Feedback

To send a feedback to the developer of the software, create a screenshot and click on the  button. 

Details

Tutorial: Video starten

To see all details of a dataset, select the dataset in the sheet and click on the button. A window, corresponding to the main form will open, showing all data related to the selected specimen. 

 

Image

Tutorial: Video starten

If an image is present a preview will be shown in the right upper area of the window. Click on it to see the image in a separate form. The images are restricted to the first image of one source, so e.g. in the organisms sheet only the first image of the specimen linked with this organism will be shown while images of e.g. linked to none or another organism or the collection event will not be addressed. 

Jul 30, 2024

Diversity Agents

Table Editors

For the data selected in the main window the table editors offer a direct access to the tables of the database. The menu Data - Table editors provide an editor for selected tables within the database.

A window with the content of the table will open. Columns with a gray background can not be edited here. Columns with a light gray background are linked to the contents of lookup tables where you can change according to the contents of these tables.

Select Set timeout ... from the menu to increase the default timeout from 5 seconds to a higher value, e.g. for greater amounts of data.  

Editing

You can either edit the contents of the table directly or perform changes to any number of marked fields. To mark a whole column use the  button. Once you have selected the contents to change, select one of the modes of change that appear in the upper left corner. The modes of change are:

  • Insert: Insert the given value at the beginning of the content
  • Append: Append the given value at the end of the content
  • Replace: Replace a string in the content with the given value
  • Clear: Remove the content

After selecting the change mode, enter the text in the field where necessary and click on the corresponding button to perform the changes

Filtering

To filter the content of the table, click in the column that should be used for filtering. Then choose the mode of comparision:

  • = : The content must be exactly like the given value
  • ~ : The content must contain the given value
  • ≠ : The content must be different to the given value

If you want the filtering to be case sensitive, choose the a<>A option. After all parameters are set, click on the button. To undo the filtering, click on the button. This will reset the data to the last saved version. If you want your changes to be saved, click the button before you reset the filtering. If you close the window all changes so far will be saved automatically. So if you do not want to save your changes, click on the button before closing the window.

Export

To export the data as a tab separated text file, click on the button. The file will be automatically saved in the client-folder.  

To export the data in a SQLite database click on the button. The data will be exported into the SQLite database DiversityAgentTables.sqlite in the folder Export in your application directory. If you want to save previous exports, please rename the SQLite database or copy it to a different directory.  

Log data

To see the log data of the table, you can click on the button. The content of the log table can not be changed, but is read only.  

Jul 30, 2024

Diversity Agents

Contact

Every agent can have several contacts resp. addresses. These are listed in the contact section (see image below).

The address that is used by other modules is a cumulation of the addess data of the agent and all its superior agents (see below).

By default the contacts are not available for publication, indicated by the sign and a pink background (see below). To enable the publication of a contact, click on the button and remove the data withholding reason. The sign will change to and the contact will be available for publication.

To see the public available contact information, click on the button. The window that will open shows the public available contact information including those of parent data (see image below). The cumulative address will collect data of every first contact information of the superior agents in the main hierarchy provided these are public and valid. Video starten

The data of the agent contacts are stored in the table AgentContactInformation.

Jan 14, 2025

Diversity Agents

Descriptors

To add a new descriptor click on the button. To delete a selected descriptor click on the  button. To administrate the descriptor types, click on the button or select Administration - Descriptor types... from the menu. A window as shown below will open.

 

To add a new descriptor type click on the button. To delete a selected descriptor type click on the  button. Deleting is only possible as long as the type has not been used. Otherwise this option is blocked as shown below. You may link a type to a module of the DiversityWorkbench. If the data contain either a link to a module or a link to a resource, the setting of the module will be blocked as shown below.

The data of the agent descriptors are stored in the table AgentDescriptor.

Jan 14, 2025

Diversity Agents

External data

The list at the button of the form showns the original datasources of the dataset (see image above).

To edit the sources where data are linked to choose Administration - External sources... from the menu. A window as shown below will open where you can add, edit and remove external sources for datasets.

The data concerning external information are stored in the tables AgentExternalDatabase.

Jan 21, 2025

Diversity Agents

Hierarchy

Main hierarchy

The relation to other agents is shown in the hierarchy. For an introduction see a short video Video starten.

Every agent can have one main superior agent. To set this superior agent click on the button. To remove the superior agent click on the button. To change to another agent in the hierarchy, select it and click on the button.

The address of an agent e.g. used by other modules will be replenished with the addresses of all superior agents (for further details see topic Contact). If an entry in the main hierarchy is changed or removed you will be asked of this information should be transferred into to other hierarchies, so the information about e.g. previous employments is not lost.

If the hierarchy contains a loop, a corresponding message will be shown and the tree will contain the current dataset twice (see below). To remove the loop, click on the button in the dataset where the relation to the upper dataset should be removed.

 

Other hierarchies

For other hierarchies, e.g. previous employments, you can add entries in the Other hierarchy part as shown below.

Use the and buttons to add resp. delete other hierarchies. The  button will open a window where you can search within the database for the parent agent you want to select. After you selected the agent where the current agent should be included into the depending data, click OK to close the window. Select the new parent in the list to see the current agent within the main hierarchy of the parent agent. The items shown in the tree are restricted to the main hierarchy of the parent agent and the current agent and do not include other items of other hierarchies. A parent for the other hierarchies may be included several times, e.g. to document several employments but in will be shown in the tree only once for every parent (see image above).

The other hierarchies are NOT visible outside the current agent. So in the example above, the parent defined in the other hierarchy will NOT show this entry in the hierarchy of the parent (see image below).

Use the button to set a selected entry in the other hierarchies as the main hierarchical entry. If a parent for main hierarchy is defined, it will be transferred into the other hierarchies. The selected entry from the other hierarchies will be removed unless there are entries in the details, e.g. Notes.

Use the button to change to an agent selected in the tree. The hierachies will display entries from projects where you have no access as well. If you want to change to a dataset using the button where you have no access you will get the message You have not the proper rights to access this dataset.  

All hierarchies

A summary of all hierarchies is shown in the "All" section where the items shown in the tree are restricted to the current agent and superior data as shown below. Other hierarchies defined outside the current agent will NOT be shown here.

After changes in the main hierarchy or the other hierachies click on the button for an update of the tree. Use the button to change to an agent selected in the tree. If you want to change to a dataset using the button where you have no access you will get the message You have not the proper rights to access this dataset.

The data of the agent hierarchy are stored in the tables Agent

Jan 14, 2025

Diversity Agents

Identifier

The agent may be linked to several identifiers as shown below. Use the and buttons to add resp. remove identifiers for an agent.

To administrate the types of the identifier, choose Administration - Identifier types … from the menu. A window as shown below will open, where you can add, edit and remove types for the identifier.

The data of the agent identifier are stored in the table AgentIdentifier.

Jan 14, 2025

Diversity Agents

Images

Each agent may be documented with several images.

To enter a new image, click on the  button. A window will open where you can enter the path and file name of the image. The selected image will be shown in the preview.

To delete an image, select it from the list and click on the  button. To see the image in a separate form, click on the button. The path of the image is shown under the image list. Click on it to open a browser with the image. you may as well click on the link below the image. By default a new image gets the entry "Withhold by default" as data withholding reason and is therefore blocked from publication. To change this, click on the button and either enter your own reason or remove the entry to enable the publication of the image. If an image should be published (with an empty datawithholding reason) the button will change to . To return to the unpublished state just click on the button and enter any text in the window that will open. The button will change to to indicate that the image will not be published. You may select a Type and specify a sequence e.g. to enable a selective publication of images. In the interface the images will be sorted accoring to their sequence.

Data are stored in the table AgentImage.

Jan 14, 2025

Diversity Agents

Keywords

To add a new keyword to the list click on the  Button. To delete an selected keyword from the list click on the  Button.

The data of the agent keywords are stored in the table AgentKeyword.

Jan 14, 2025

Diversity Agents

Module connections

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. DiversityAgents is referred by several modules. To scan for references from these modules on data in DiversityAgents choose Data - Scan modules - from the menu (see image below).

With these options the program will scan all sources of the selected module as listed in the connections for references to the current agent. After selecting an agent in the tree, the sources of the selected modules together with the linked data will be listed as shown below.

Select a link to see a summary of the linked data (see below).

To get further information about an item click on the button. If so far the path to the respective application has not been set, you will get a corresponding message (see below).

Click on the button to set the path to the application (see below).

By default the path to the application is C:\Program Files (x86)\DiversityWorkbench\Diversity...\Diversity.…exe as shown.

Jan 14, 2025

Subsections of Modules

Diversity Agents

Module Related Entry

The DiversityWorkbench is a set of components for building and managing biodiversity information. Each of which focuses on a particular domain and provides services for the other modules. For an introduction see a short tutorial Video starten.

To use the service of an external module you need access to the database of this module and optionally the module application placed in your application directory. Entries related to an external module have a standard interface in the main form.

Linking to a datasource or module

There are 4 options to link the content to a datasource (or module).

  • Local database
  • Remote database
  • Cache database
  • Webservice

There are two differnt approaches for providing content for the textbox. Either as a autocomplete list (, , ) or by searching values on base of the entered text in combination with a combobox ().

For the autocomplete lists just start to type and the corresponding entries will be listed where you can choose the entry you are looking for. To set the link including additional information provided by the original source (, ), you just have to leave the textbox. The program will then contact the database to which the entry corresponds and insert the additional information including the link to the source database.

The next paragaphs show how to uses this linking. The colours of the pins are automatically set when a datasource is set. The colour indicates if the current set datasource ist set to the local, remote or cache databse or to a webservice. To select one of the datasources, click on the  button and choose among the sources.

Local database

The values shown in the autocomplete list are taken from the entries in the local database.

This is the default. To refresh the content or slect the local databse as source, click on the pin button, choose the first empty entry of the list and click OK.

Remote database

To set the datasource on a remote database, choose a database from the list.

Either a database available via a linked server (e.g. [TNT.DIVERSITYWORKBENCH.DE,5432].DiversityTaxonNames_TaxaVaria see below) or a database on your local server, starting with e.g. DiversityTaxonNames for taxa in the identification

Next you will be asked to choose a project within the selected source. In case there are additional options you may be asked e.g. for taxa to restrict the content to a checklist provided by the datasource. The pin button and the textbox will change their color to orange to indicate the current source type. The autocomplete list is then generated based on the content in the remote database. When you leave the textbox the software will automatically add additional information from the selected source and set the link as shown below.

 

Cache database

To provide data via the cache database these data must be first imported as source as described in the link to cacheDB chapter.

This option provides faster access to remote data e.g. on linked servers . To choose a source from the cache database, click on the pin button and select the entry CacheDB from the list (see below) and click OK.

Next you will be asked to choose among the sources provided by the cache database. Choose your preferred source and click OK. The button and the textbox will change their color to to indicate the current source type. Now the values for the autocomplete list will be based on this datasource. Just start to type and the corresponding entries will be listed where you can choose the entry you are looking for. To set the link including additional information provided by the original source, you have to leave the textbox. The program will contact the database to which the entries in the cache database correspond and insert the additional information.

Webservice 

To set the datasource on a webservice, choose a webservice from the list as shown below. The pin button and the textbox will change their color to blue to indicate the current source type.

To get data from the webservice, you have to enter a search text in the textbox and click on the combobox button to search the webservice for matching entries. Choose among the provided results to fill the textfield and the set the link to the webservice.   

States and functions of the interface

There are several states and functions of this interface:

  • 1: the value is only set in the local database with no connection to the remote module. In this state you may either type the value or select it from the values which are already available in the database (see above).

  • 2: the value is related to the remote module.

If you wish to set a relation to the remote module you have 2 options:

Option 1

Click on the pin button to select a source as described above.

An overview for all settings can be found under Administration - Customize display - Settings.

Charts

After the source is set to a database of the DiversityWorkbench certain datasources provide also charts for the selection of taxa or terms. Click on the chart button to open a table where you can select one of the provided taxa resp. terms. Video starten

 

Option 2 Detailed linking with query option

Click on the amonite button. A window will open where you may select an entry from the foreign database. If the option for loading the connections is not set the connection to a database may not be established indicated by a button. Either requery all connections as described in chapter Connections or click on the button to open the database connections for the linked module. With this option you have the full range of query options as shown in the image below as well as access to additional webservices.

For DiversityScientificTerms you can use a hierarchy for the selection of the lists as shown below.

 

If the value has a relation to the remote module, the interface will appear as shown below with the content of textbox set to read only and a yellow background.

To release the connection to the remote module click on the button. If you require further information on the value, click on the button. This will open a form showing an overview of the related value.

If the client application of the module is available, you may inspect the details of the entry. To start the client application of the remote module click on the button. 

If the provided link does not correspond to a dataset in the source, you will get a message as shown below. Click Yes to remove the wrong link and replace it with a valid link. Video starten

 

Relation to a webservice

Some modules provide the possibility to link your data to an external webservice. For example, DiversityTaxonNames gives you access to the taxonomic names of IndexFungorum. To establish a connection to an external webservice click on the button. As with the link to modules within the DiversityWorkbench, a window will open where you are able to choose from either DiversityWorkbench modules or external Webservices. See chapter Webservice for further details

Jul 30, 2024

Diversity Agents

Projects

Every agent can be assigned to any number of projects. To assign a agents to a project click on the  button. To remove it from a project, select the project from the list and click on the  button.

There are 4 states of accessibility for projects Video starten

  •     Full access: The user can edit the data
  •      Read only access: The user can only read the data
  •      Locked: The project is locked. Nobody can change the data
  •     No access: The user has no access via a project

If there are projects, to which you have no full access to, these will be listed in a separate lists at the top as shown below.

Below is an example where the user has access via a project with access and a project with read only access. In addition the data are contained in a project where the user has no access.

 

Below is an example where the user has access via one read only project.

 

Below is an example where the dataset is contained in a project that is locked.

 

Data are stored in the table AgentProject.

Details upon the projects within the Diversity Workbench are stored in the database DiversityProjects. To open a project to see further information upon a project click on the   button. 

 

 

 

Jan 14, 2025

Subsections of Projects

Diversity Agents

Display types

The type in which an agents name will be displayed can be set within a project.

To edit the display types, choose Administration - Agent display types ... from the menu. A window as shown below will open, where you can set the type for every project.

 

Every user has a default project within DiversityAgents. As an administrator, you can set the default projects for every user. The display type for a user is set according to these projects. To edit the default projects, choose Administration - Default projects ... from the menu. A window as shown below will open, where you can set the default project for every user. If the projects are not specified here, the first project the user has access to will be used.

 

Every user can set his default project by choosing Administration - Default project ... from the menu. A window as shown below will open, where the user can set the default project.

 

The tables used for the storage of these parameters are shown below.

Description of the tables

Table ProjectProxy

The projects - refers to database DiversityProjects

Column Data type Description Nullable Relation
ProjectID int The ID of the project, Primary key NO -
Project nvarchar (50) The name of the project as stored in the module DiversityProjects NO -
ProjectURI varchar (255) The URI of the project, e.g. as provided by the module DiversityProjects. YES -
AgentNameDisplayType nvarchar (50) The display type of the name of the agent YES Refers to table AgentNameDisplayType_Enum
CreateArchive bit If an archive e.g. by a task schedule should be created YES -
ArchiveProtocol nvarchar (MAX) The protocol created during the last archive YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -
LastChanges datetime The recent date when data within the project had been changed YES -
IsLocked bit If the data within the project should not be changeed and the access for all users is restricted to read only YES -

Depending on:

  • AgentNameDisplayType_Enum

Table ProjectUser

The projects to which users have access to

Column Data type Description Nullable Relation
LoginName nvarchar (50) The login name of the user NO Refers to table UserProxy
ProjectID int The ID of the default project of the user as stored in table ProjectProxy NO Refers to table ProjectProxy
ReadOnly bit If the user has only read access to data of this projectDefault value: (0) YES -

Depending on:

  • ProjectProxy
  • UserProxy

Table UserProxy

The user logins - refers to database DiversityUsers

Column Data type Description Nullable Relation
LoginName nvarchar (50) The login name of the user, Primary key NO -
CombinedNameCache nvarchar (50) A combined name of the user, created on the base of an entry in the module DiversityUsers YES -
UserURI varchar (255) Refers to UserInfo.UserID in database DiversityUsers YES -
ProjectID int The ID of the default project of the user as stored in table ProjectProxy YES Refers to table ProjectProxy
Queries xml (MAX) Queries created by the user YES -
AgentURI varchar (255) A link to a DiversityAgents module where further informations about the user is available. YES -
ID int ID of the user NO -
PrivacyConsent bit If the user consents the storage of his user name in the database YES -
PrivacyConsentDate datetime The time and date when the user consented or refused the storage of his user name in the database YES -

Depending on:

  • ProjectProxy
Jul 30, 2024

Diversity Agents

References

References containing informations about the agent are listed in the References tab. The enter a new reference click on the button, To remove a reference use the button. A link to the module DiversityReferences can be established with the button.

The data of the agent references are stored in the table AgentReference.

Jan 14, 2025

Diversity Agents

Relations

The relations to other agents are shown in the Relations tab. To enter a new relation, click on the button, to remove a relation use the button. If the relations of an agent should not be published e.g. on the web, enter a reason in the Withholding section. Any text will prevent a publication. To change to an related agent, select it and click on the button.

The data of the agent relations are stored in the table AgentRelation.

Jan 14, 2025

Diversity Agents

Resources

The resources directory is set via the menu (Administration - Resources).

There are 3 possibilities for the resources directory:

  • Select any directory you have read/write access (User defined)
  • Select the "Home" directory of the user
  • Select the "My Documents" directory of the user

The default is set to Home. This directory will contain all files the user need access to (see image below).

Certain directories are hidden (Query) and are handled by the software i.e. the content should not be changed by the user. The other folders are generated by the software if missing, e.g. Export for any exports (see below).

 

Jul 30, 2024

Diversity Agents

Synonymy

The synonymy to other agents is shown in the Synonymy tab. Every agent can be a synonym to another agent. To make an agent to a synonym click on the button. For agents that are declared a synonym, you can specify the type of the synonymisation. If the type is "replaced by" than this agent will no longer be visible for external modules but will be replaced by the agent it is a synonym of. To change to a synonym of the agent just click on the button.

If the hierarchy for the synomyms contains a loop, a corresponding message will be shown and the tree will contain the current dataset twice (see below). To remove the loop, click on the button in the header for the dataset where the relation to the upper dataset should be removed.

 

Jul 30, 2024

Diversity Agents

Data withholding

If an agent should not be published e.g. on the web, enter a data withholding reason. Click on the   button to open a window where you can enter the reason why the data should not be published. Any entry will prevent the data from being published. For datasets with a data withholding reason the image will change to . To remove the restriction just click on the button and delete the reason. Besides whole datasets, the relations, adresses and images can be blocked from publication. See e.g. Relations for more details.

Jan 14, 2025

Diversity Agents

Import Export

The chapter below refers to DiversityCollection but is valid for DiversityAgents as well. The CacheDatabase is accessed via DiversityCollection

An overview of some options for the im- and export in the module DiversityCollection is shown in the image below. The options Importwizard, Exportwizard, Archive and Replication are available in most of the modules.

Example for a data flow

The image below shows an expample for a data flow from the original source to the final GBIF-portal. As a first step the data are imported via the Import wizard are imported into the database. After the data are given free for publication, they are transferred into the cache database .  From there they are transferred into a Postgres database containing a package for conversion into ABCD. Finally the BioCASE tool for mapping the data is used to provide the data for GBIF.

Jan 14, 2025

Subsections of Im- & Export

Diversity Agents

Archive

Creating an archive

The data related to a project can be exported into an archive. Choose Data - Archive - Create archive... from the menu. A window as shown below will open.

Select the project you want to create an archive of and click on the Find the data =\\\ button. The data related with the project will be imported into temporary tables to allow you to inspect them in advance of the creation of the archive (use the buttons to see the data). To create the archive, click on the Create the archive button. A directory will be created containing a XML file for every table. For a common introduction see the tutorial: Video starten.

You can include the log data by selecting the option as described in the tutorial: Video starten.

 

Resetting the database

Before you restore an archive, please make sure that the data from the archive do not interfere with the data in the database. In order to avoid problems you should clean the database from any user data. To clear the database from any user data, choose  Data - Archive - Reset database... from the menu. A window as shown below will open listing all tables and the number of data within these tables. Click on the Reset database  button to remove any of these data including any data in the log tables.

 

Restoring an archive

To restore an archive choose Data - - Archive - Restore archive... from the menu. A window as shown below will open listing the tables in the database. To restore an archive click on the Choose archive directory button and select the directory containing the archive files. Next click on the Read data =\\\ button to import the data from the XML files into temporary tables.

With a click on the buttons you can inspect the content of the temporary tables. Finally click on the Restore from archiv button. If you select the option, the import will ask you for a stop in case of an error.

You can include the log data by selecting the option as described in the tutorial: Video starten.  

Planing

Plan schedule based archive creation

To administrate the schedule based creation of archives choose Data - Archive - Administrate archives... from the menu. A window as shown below will open listing the projects in the database. Select the project that should be included in the schedule based creation of archives. To create an archive for all selected projects, click on the Create archives button. The protocol of a previous archiving is shown as in the image below. Successful runs are indicated with a green color while failures have a red background (see below).

 

Creation of xsd schemata

Next to the data, the archive files contain a xsd description of the tables. To create xsd schemata independent of the content, select Data - Archive - Create schema from the menu. A windows as shown below will open with the list of all tables where the main tables of the database are preselected.

To change this selection you may use the  all and  none buttons resp. the Add to selection  and Remove from selection  options using * as a wildcard. Click on the Create schemata  button to create the schemata for the selected tables in the predefined directory. The  button will open this directory containing the created files. The schemata contain the name of the DiversityWorkbench module and its version, the definition of the table, the primary key and the colums together with their datatype and description (see the example below).

Creation of archives as a backgroud process

To archive the data in a scheduler based background process, you can start the application with the following arguments:

  • Archive
  • Server of the SQL-server database
  • Port of SQL-server
  • Database with the source data
  • Optional: Directory where the archive directories should be created

C:\DiversityWorkbench\DiversityAgents> DiversityAgents.exe Archive snsb.diversityworkbench.de 5432 DiversityAgents C:\DiversityWorkbench\DiversityAgents\Archive

The application will create the archives, generate the protocols as described above and quit automatically after the job is done. The user starting the process needs a Windows authentication with access to the SQL-Server database and proper rights to archive the data. If the last argument is not given the default directory …\Application directory\Archive\ will be used.

 

 

 

May 16, 2024

Diversity Agents

Replication

The chapter below refers to DiversityCollection but is valid for DiversityAgents as well.

Replication

If you wish to work with your data on a local database (called subscriber), e.g. on your laptop, not linked to a database on a central server (called publisher) and these data should be synchronized with the data in the database on the server, you may use the replication function of DiversityCollection. To install the database on your local computer see the installation section.

To use the replication function you require the roles Replicator or Administrator.

Add Publisher

To define a publishing database choose Data → Replication → Add Publisher from the menu. A window will open where you choose the publisher. After the publisher is set, you may transfer data between your local database (subscriber) and the publisher. This function is only available for administrators.

Remove Publisher

To remove a publisher from the list choose Data → Replication → [Publisher] → Remove from the menu (where [Publisher] is the name of the publishing database on the publishing server). This function is only available for administrators.

Clean database

Initially you may wish to remove all previous data from your local database (subscriber). Choose Data → Replication → Clean database … from the menu. A window will open as shown below where you may choose the ranges which should be cleared:

  • Definitions = the basic definitions within the database, e.g. the available taxonomic groups.
  • Descriptions = the descriptions and their translations of the tables and columns of the database.
  • Project, User = the available projects and users.
  • Basic data = basic data like the collection.
  • Data = the specimen, organisms etc.

Choose the data ranges you wish to clear and click on the button. All tables which contain data will be listed as shown below.

 

Choose the tables which should be cleared and click on the Clean database button. Please keep in mind that you can not delete data from a table as long as there is data in a related table depending on the data you wish to delete. The sequence of the tables is organized to avoid these problems.

Download

To download data from the publisher choose Data → Replication → [Publisher] → Download from the menu (where [Publisher] is the name of the publishing database on the publishing server). A form will open as shown below. Choose the project of the data and the data ranges (see above) which you wish to download. Click on the button to list the tables containing data. To start the download click on the Start download button. With the Force download, ignore conflicts option you can decide whether or not the data in your local database (= Subscriber) should be checked for changes before you download the data from the publisher.

If not all data should be included in the replication, you have the option to set a filter. Click on the button for the table where the data should be filtered to set this filter. A window as shown below will open.

All columns of the table will be listed and allow you to set the filter. To inspect the filtered data, click on the button. Click on the button to see the current filter. If a filter is set this will be indicated with a blue background .  

Merge

To merge data from your local subscriber database with the publisher you must first choose a project. Choose Data → Replication → [Publisher] → Merge** from the menu ([Publisher] is the name of the publishing database on the publishing server). As described for the download, choose the data ranges and click on the button. To start the upload click on the Start merge button.

 

Upload

To transfer data from your local subscriber database to the publisher you must first choose a project. Choose Data → Replication → [Publisher] → Upload from the menu ([Publisher] is the name of the publishing database on the publishing server). As described for the download, choose the data ranges and click on the

button. To start the upload click on the Start upload button. With the Force upload, ignore conflicts option you can decide whether or not the data in server (= Publisher) should be checked for changes before you upload the data from your local database (= Subscriber).

As described for the download, data may be filtered with a click on the button (see above).

 

Tools

To fix problems that may interfere with the replication you find some tools under the menu Data → Replication → [Publisher] → Tools… from the menu ([Publisher] is the name of the publishing database on the publishing server). A window will open as shown below.

You may synchronize the RowGUIDs between basic subscriber and publisher tables if for any reason these are differing, e.g. due to manual insert. Choose the table that should be synchronized. The tables will be compared for both publisher and subscriber. The datasets with identical key but different RowGUID will be listed (see above). Click on the Start update button to synchronize the RowGUIDs.  

Conflict

If the transfer of data was successful, the numbers of the transferred data will be shown as below.

During the download or upload a conflict may occur, if the data has been edited in both databases. This will be indicated as shown below.

Click on the button to open a window as shown below where you can choose between the two versions of the data as found in the publisher and the subscriber database.

The conflicting columns are marked red. For text values the program will create a combination of both values (see above) in a merged version of the data. Choose the preferred version of the data and click Solve conflict button. If you can not solve a conflict, use the Ignore conflict or Stop conflict resolution buttons respectively.

 

Report

At the end of each transfer a report will be created with a summary for every table which has been included.

 

May 16, 2024

Diversity Agents

Export

  • Archive
  • Export via Table editors as tab separated text file or SQLite database
  • Export as CSV file via bcp
  • Export via CacheDatabase in DiversityCollection and DiversityDescriptions
  • Create a backup Backup
May 16, 2024

Subsections of Export

Diversity Agents

Backup

The chapter below refers to the module DiversityCollection but is valid for DiversityAgents as well

If you want to create a backup of your database, there are 2 options. You may either export the data as csv files to your local computer or you may create a backup on the server.

Export data as csv

To export your data as csv files to your local computer, choose Data → Export → CSV(bcp) ... from the menu. A window will open as shown below, where you can select the tables that should be exported. Click on the Start Export button to export your data. If you choose the option as shown below 2 files will be created for every table. The first file (*.csv) contains the data while the second file (*.xml) contains the structure of the table.

Create backup on the server

To create a backup of your database on the server, choose Data → Backup database from the menu. This will create a SQL-Server backup on the server where the database is located. Ensure that there is enough space on the server.

Another option is to create a direct copy of the database files on the server. For this you have to use the functions provided by SQL-Server. However, you need administration rights for the database you want to create a backup of. Open the Enterprise Manager for SQL-Server, choose the database and detach it from the server as shown in the image below.

After detaching the database, you can save a copy of the ..._Data.MDF file to keep it as a backup.

After storing the backup you have to reattach the database.

A dialog will appear where you have to select the original database file in your directory.

May 16, 2024

Diversity Agents

Export CSV

The chapter below refers to the module DiversityCollection but is valid for DiversityAgents as well

To export the tables of the database in a tabulator, comma or semicolon separated format, choose Data → Export → Export CSV... from the menu. A window as shown below will open where you can select the tables to be exported in sections Selection criteria and in the Tables for export.

A prerequisite for this export is that the bcp program is installed on your computer. This has either been installed together with the installation of SQL-Server or you have to install the Microsoft Command Line Utilities for SQL Server.

To start the export click on the Start export button. By default the data will be exported into a directory ...\Export\<database_name> below your application directory. Click on the button to select a different target directory before starting export.

 

After export the tables are marked with green background, if table schema and data were exported successfully. If only the data were exported, this is marked with yellow background, if nothing was exported, the background is red. A detailed export report can be viewed by a click on the export result file name.  

May 16, 2024

Diversity Agents

Export Wizard

The export wizard provides a possibility to export the data selected in the main form. The data are exported as tab separated text file. The export may include transformations of the data as well as information provided by linked modules and webservices. Choose Data - Export - Export wizard from the menu and then select one of the export targets (Event, Specimen, ...). For a short introduction see the tutorial.  

Adding tables

There are the following ways to add tables:

  • One parallel table
  • Several parallel tables according to selected data
  • Dependent table

All options will include the depending tables as defined for the default table. The option for several tables will add as many tables as there are found in the data.

If you added parallel tables, you should set the sequence of the datasets within these tables: For the columns that should be used for sorting the data, set the ordering sequence to a value > 0 and choose if the ordering sequence should be ascending or descending .

Certain columns in the database may provide information linked to another table or a module resp. webservice . Click on the button to add a linked value.

Adding and editing file columns

To add columns to the exported file, use the buttons. In the textbox at the top of the file column, you can change the header for the column. To change the position of a file column use the resp. button. To fuse a column with the previous column, click in the gray bar on the left side of the column that will change to for fused columns. To remove a file column, use the button. Pre- and postfixes for the columns can directly be entered in the corresponding fields. To apply transformations on the data click on the button.  

Filter

To filter the exported data, use the filter function. Click on the button and enter the text for the filter. Only data matching the filter string will be exported. If a filter is set, the button will have a red background to remind you of the filter. The filter may be set for any number of columns you need for the restriction of the exported data.  

Rowfilter

This filter in contrast to the filter above strictly applies to the row according to the sequence of the data. For an explanation see a short tutorial Video starten.

 

Test

To test the export choose the Test tab, set the number of lines that should be included in the test and click on the Test export button. To inspect the result in a separate window, click on the button.

SQL

If you want to inspect the SQL commands created during the test check this option. To see the generated SQL click on the SQL button after the Test export. A window containing all commands including their corresponding tables will be shown.

 

Export

To export your data to a file, choose the Export tab. If you want to store the file in different place use the button to choose the directory and edit the name of the file if necessary. Check the include a schema option if you want to save a schema together with your export. To start the export, click on the Export data   button. To open the exported file, use the button.

 

Export to SQLite

To export your data into a SQLite database, choose the Export to SQLite tab. You may change the preset name of the database in order to keep previous exports. Otherwise you overwrite previous exports with the same filename. To start the export, click on the Export data   button. To view the exported data, use the button.

 

Schema

To handle the settings of your export, choose the Schema tab. To load a predefined schema, click on the button. To reset the settings to the default, click on the button. To save the current schema click on the button. With the button you can inspect the schema in a separate window.

May 16, 2024

Subsections of Export Wizard

Diversity Agents

Export Wizard Transformation

The exported data may be transformed e.g. to adapt them to a format demanded by the user. Click on the button to open a window as shown below. For an introduction see a short tutorial Video starten.

Here you can enter 6 types of transformation that should be applied to your data. Cut out parts,  Translate contents from the file, RegEx apply regular expressions or Replace text and apply Calculations Σ or Filters on the data from the file. All transformations will be applied in the sequence they had been entered. Finally, if a prefix and/or a postfix are defined, these will be added after the transformation. To remove a transformation, select it and click on the button.

 

Cut

With the cut transformation you can restrict the data taken from the file to a part of the text in the file. This is done by splitters and the position after splitting. In the example below, the month of a date should be extracted from the information. To achieve this, the splitter '.' is added and then the position set to 2. You can change the direction of the sequence with the button Seq starting at the first position and starting at the last position. Click on the button Test the transformation to see the result of your transformation.

With the Start at Pos. option the given splitters will be converted into space (' ') and the whole string starting with the given position will be used (see below).

 

Translate

The translate transformation translates values from the file into values entered by the user. In the example above, the values of the month should be translated from roman into numeric notation. To do this click on the button to add a translation transformation (see below). To list all different values present in the data, click on the button. A list as shown below will be created. You may as well use the and buttons to add or remove values from the list or the button to clear the list. Then enter the translations as shown below. Use the save button to save entries and the Test the transformation button to see the result. 

To load a predefined list for the transformation use the   button. A window as shown below will open. Choose the Encoding of the data in your translation source and indicate if the First line contains column definition. Click OK to use the values from the file for the translation.

 

Regular expression

The transformation using regular expressions will transform the values according to the entered Regular expression and Replace by values. For more details please see documentations about regular expressions.

 

Replacement

The replacement transformation replaces any text in the data by a text specified by the user. In the example shown below, the text "." is replaced by "-". 

 

Calculation 

The calculation transformation Σ performs a calculation on numeric value, dependent on an optional condition. In the example below, 2 calculations were applied to convert 2-digit values into 4 digit years.

 

Filter 

The filter transformation compares the values from the data with a value entered by the user. As a result you can either Export content into file or Export fixed value. To select another column that should be compared, click on the button and choose a column from the file in the window that will open. If the column that should be compared is not the column of the transformation, the number of the column will be shown instead of the symbol. To add further filter conditions use the button. For the combination of the conditions you can choose among AND and OR. 

 

 

 

 

 

 

May 16, 2024

Diversity Agents

Export Wizard Tutorial

This tutorial demonstrates the export of a small sample from the database. For an introduction see a short tutorial Video starten.

Choosing the data

In the main form, select the data that should be exported (only the data displayed in the query results are exported).

Exporting the data

Choose Data → Export → Wizard → Organism ... from the menu. A window as shown below will open where the available tables for export are listed in the upper left area. To show the data columns of a table, select this table in the list.

 

Adding additional tables

In this example, we want to add as many parallel identification tables as present in the data. To do this, click on the button of the Identification table. At the end of the list (depending on your data) the additional tables are added (see below).

 

Setting the sequence for the tables

To set the sequence of the Identifications, select the first table and for the column IdentificationSequence set sorting sequence to 1 and the direction for sorting to descending

 

Choosing data from linked modules

Some columns provide the possibility to add data from linked tables or modules. In this example we choose the column NameURI linking to the module DiversityTaxonNames (see below).

To provide linked values, click on the button. A window as shown below will open, where you can choose among the provided services.

After the service is selected, you will be asked for the value provided by the service (see below).

Now the selected link is added underneath the column as shown below. You can add as many links as you need for your export.

For some modules there are values that refer to other modules with a name like [Link to ...] as shown in the example below.

If you select one of theses values, you will be asked to select the service or database linked to this modul (see below)

... and then to select one of the provided columns (see below)

Within the form this linked values will be marked as shown below. If several results are retrieved these will be separated with by " | ".

 

Adding columns to the file

To add columns to the exported file, click on the buttons for the columns resp. linked values. In this example select all Family values and the TaxonomicName (see below).

 

Fusing columns

The families should appear as one column and as the sources can exist only once for each identification we can fuse these columns. To do so, click on the delimiters between these columns (see below).

 

Setting the headers

By default the headers for the exported data are set according to the names of the columns in the database. To change this, edit them as shown below where TaxonomicName has been changed to Taxon (see below). For fused columns only the header in the first column will be used.

 

Testing

To test the export, click on the Test export button. The result depends on the content in your data but should look similar as shown below.

 

Export

To finally export the data, choose the Export tab. By default the data will be exported into tab separated file in a directory in the application directory (see below). You can change the directory (click on the button). You can choose the Include schema option to create a schema that you may reuse in a later export.

May 16, 2024

Diversity Agents

Import

There are several import mechanisms available for most modules. Some modules like DiversityDescriptions have special import mechanisms.

Import wizard

for tab separated lists: Import data from foreign sources and attach further data to existing data sets in the database.

Replication

Replication with a local database.

Archive

Restoring an archiv.

May 16, 2024

Subsections of Import

Diversity Agents

Import wizard

The examples below are from the module DiversityAgents, but are valid for any other module as well.

With the current solution please ensure that there are no concurrent imports in the same database.

For some imports like e.g. for Collections in DiversityCollection you will be reminded to update the cache tables for the hierarchies.

With this import routine, you can import data from text files (as tab-separated lists) into the database. A short introduction is provided in a video Video starten. Choose Data Import Wizard Agent from the menu. A window as shown below will open that will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choose for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

Choosing the File and Settings

  • File: As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Choosing a file will automatically set the default directory for the import files. To avoid setting this directory, deselect the option Adapt default directory in the context menu of the button to open the file.
  • Encoding: Choose the Encoding of the file, e.g. Unicode. The preferred encoding is UTF8.
  • Lines: The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the
  • First line: The option First line contains the column definition decides if this line will not be imported.
  • Duplicates: To avoid duplicate imports you can Use the default duplicate check - see a video Video starten for an explanation.
  • Language: If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data.
  • Line break: With the option Translate \r\n to line break the character sequence \r\n in the data will be translated in a line break in the database.
  • SQL statements: To save all SQL statements that are generated during a test or import, you can check the option Record all SQL statements. Video starten
  • Schema: Finally you can select a prepared Schema (see chapter Schema below) for the import.

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

The import of certain tables can be paralleled. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import information of logging columns like who created and changed the data, click on the include logging columns button in the header line. This will include additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue background (see below and chapter Table data).

Merging data

You can either import your data as new data or Merge them with data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported. Otherwise the data will be updated.

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

Empty content will be ignored e.g. for the Merge or Update option. To remove content you have to enter the value NULL. As long as the column will allow emty values, the content will be removed using the NULL value.

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you which actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive columns, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparison   = For all merge types other than insert columns for comparison with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

Testing

- To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and then click on the Test data in line:  button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display any errors that occurred as shown below. All datasets marked with a red background, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets:

  • INSERT
  • MERGE
  • UPDATE,
  • No difference
  • Attach
  • No data

The colors of the table columns indicate whether a column is decisive , a key column or an attachment column .  

If you suspect, that the import file contains data already present in the database, you may test this and extract only the missing lines in a new file. Choose the attachment column (see chapter Attaching data) and click on the button Check for already present data. The data already present in the database will be marked red (see below). Click on the button Save missing data as text file to store the data not present in the database in a new file for the import. The import of agents contains the option Use default duplicate check for AgentName that is selected by default. To ensure the employment of this option the column AgentName must be filled according to the generation of the name by the insert trigger of the table Agent (InheritedNamePrefix + ' ' + Inheritedname + ', ' + GivenName  + ' ' + GivenNamePostfix + ', ' + InheritedNamePostfix + ', ' + AgentTitle - for details, see the documentation of the database).

If you happen to get a file with a content as shown below, you may have seleted the wrong encoding or the encoding is incompatible. Please try to save the original file as UTF8 and select this encoding for the import. 

Import

- With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below). You optionally can include a description of your schema and with the button you can generate a file containing only the description.


Schedule for import of tab-separated text files into DiversityAgents

  • Target within DiversityAgents: Agent
  • Database version: 02.01.13
  • Schedule version: 1
  • Use default duplicate check:
  • Lines: 2 - 7
  • First line contains column definition:
  • Encoding: UTF8
  • Language: US

Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings according to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

Description

- A description of the schema may be included in the schema itself or with a click on the Import button generated as a separate file. This file will be located in a separate directory Description to avoid confusion with import schemas. An example for a description file is shown below, containing common settings, the treatment of the file columns and interface settings as defined in the schema.

  • and the video: Anpassungen für HUGO Video starten: Umzug von chm nach html. Anleitung für Umstellung auf html. Übersetzung von html nach markdown. Auswahl der Dateien im Programm. Pandoc als Voraussetzung für Konvertierung. Ansicht der markdown Dateien. Ersetzen des headers (Frontmatter). Anpassungen für Bilder, Ersatz der Icons durch Vektorgrafiken. Beispiel für Vektorgrafik. Bearbeitung der Liste für Ersetzungen über Tabelle. Laden einer Datei mit Ersetungen. Ansicht der Datei und Laden der Datei. Durchfürung der Ersetzungen.
  • How to export the content of enum tables for inclusion in the manual for HUGO
  • and the video Ausgabe des Inhalts von Aufzählungstabellen Video starten: Auswahl der Aufzählungstabellen, Anwählen der Ausgabeoption, Auswahl der Spalten, Export und Ansicht im Formular und im Browser.
  • How to fix broken links for Hugo
  • and the video: Video starten

  • How to related reference links for Hugo

  • and the video: Video starten

Administration

  • How to set the access to projects
    • see chapter Zugriff auf Projekte
    • and the video Video starten: Einstellungen des Zugriffs auf Projekte, Zugriff auf Daten innerhalb von Projekten

Editing

  • How to set the language of a dataset
    • see chapter Sprache
    • and the video Video starten: Festlegen der Sprache des Inhalts eines Datensatzes.
    • How are addresses retrieved from the hierarchy
      • see chapter Hierarchien
      • and the video Video starten: Haupthierarchie mit Ermittlung der Adresse und zusätzliche Hierarchien.
        • How to remove loops from a hierarchy
          • see chapter Schleifen entfernen
          • and the video Video starten: Entfernen von Schleifen in der Hierarchie anhand von Beispieldaten.
    • How to remove loops in the synonymy
    • How to see the public contanct infos
      • see chapter Öffentliche Kontaktdaten
      • and the video Video starten: Ermittlung der öffentlichen Kontaktdaten anhand zugänglichen Kontaktdaten des aktuellen Eintrags sowie der in der Haupthierarchie verfügbaren Kontaktdaten.
    • How to set the icons of descriptors
      • see chapter Descriptoren - Icons einstellen
      • and the video Video starten: 2 prinzipielle Typen von Deskriptor: Modul zugeordnet oder ohne Modul. 4 Möglichkeiten für die Einstellung der Icons - OHNE ICON: Modul zugeordnet: Default Icon des Moduls. ohne Modul: Default Icon für Deskriptor. MIT ICON: ohne Modul: Ausgabe des gesetzten Icons. Modul zugeordnet: Ausgabe des gesetzten Icons. Default Icon des Moduls wird ersetzt.
    • How to propagate changes to linked data
      • see chapter Änderungen verlinkter Datensätze weiterleiten
      • and the video Video starten: DiversityAgents als Modul in der DWB. Darstellung der Beispieldaten in DiversityCollection und DiversityAgents. Änderung in DiversityAgents, Eintrag des geänderten Datensatzes in Update Liste. Auswahl der zu aktualsierenden Datenbanken. Display types in DiversityAgents. Eintrag von aktuellem Datensatz, Eintrag aller Datensätze, Ansicht der Liste, Löschen der Liste. Aktualisieren des Datensatzes. Kontrolle der Änderungen in DiversityCollection.
    • Spreadsheet

  • How to include column RowGUID to enable changes in the PK of a table
  • see chapter …
  • and the video RowGUID einschliessen Video starten: Erläuterung der RowGUID. Beispieldaten im TableEditor. Laden der Daten im Spreadsheet. Versuch der Änderung einer Spalte die Teil des Primärschlüssels ist. Einschliessen der RowGUID. Versuch der Änderung mit eingeschlossener RowGUID. Ablehnung der Änderung bei Kollision mit Primärschlüssel. Änderung der Daten ohne Kollision. Ergebnis der Bearbeitung.

Import

  • How to import data
    • see chapter Überblick
    • and the video Video starten: Import von Daten anhand des Beispiels im Tutorial.
    • How to check for duplicates
      • see chapter Duplikate
      • and the video Video starten: Prüfung auf in der Datenbank bereits vorhandene Duplikate während des Imports.
    • How to transform data during the import
      • see chapter Transformation
      • and the video Video starten. Transformation von Daten für den Import am Beispiel eines Datums.

Archive

  • How to create an achive including the log tables
  • see chapter Archiv inclusive des Logs
  • and the video Video starten.
    (Aufbau von Logtabellen, Vorstellung der Beispieldaten, Erstellung eines Archivs: Einschliessen der Logtabellen, Suche nach Daten, Anlegen des Archivs. Wechsel in leere Datenbank. Einlesen der Archivdaten: Auswahl des Archivs, Log einschliessen, Einlesen der Daten, Archivdaten einspielen, Meldung zu vorhandenem Projekt. Anmeldebestätigung. Ansicht der Daten einschliesslich der Daten in den Logtabellen)
  • How to create an archive
  • see chapter Archiv erstellen
  • and the video Video starten.
    (Automatisierte Erstellung durch Server, Manuelle Erstellung, Suche nach Daten, Erstellung, Inhalt einer xml-Datei, Protokoll).

Diversity Agents

Customize

The main window can be customised in several parts. To change the visible parts in the main window select Administration - Customize... from the menu.

Query

The set the option for optimized queries and the option to remember the query settings as default, select the Optimized resp. Remeber option. The corresponding buttons in the query will be hidden providing more space. 

Start

Load linked datasources at start: If the datasources on linked servers should be loaded together with the start of the programm.

Jan 21, 2025

Diversity Agents

Internals

For users that need more detailed information about the software including database design etc.

Jul 30, 2024

Subsections of Internals

Diversity Agents

Version

For information about the version of the client application choose Help, Info…

The current version in the example above is 4.0.0 for the client and 2.1.13 for the database

 

 

Jul 30, 2024

Diversity Agents

License

This manual is copyrighted work licensed under a Creative Commons License.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

 

For information about the license of the client software choose Help, Info…

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License (GPL) for more details.

Jul 30, 2024

Diversity Agents

Data Access

Access to the data

To get access to the data, you have to fulfill several requirements. In DiversityCollection, you must be a member of one of the user groups. You can only access data, which is listed in the projects you have access to. For external users data may be blocked by entries in the data withholding reasons or due to a data embargo.

   

May 16, 2024

Subsections of Access

Diversity Agents

Login Administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

To set the website where information about details concerning the General Data Protection Regulation are shown, click on the button.   

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

To administrate the  linked servers, click on the button.   

To send a feedback click on the button.   

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the time span (From - To) and the number of data sets where any activity of the current login has been found.

 

Creation of login

To create a new login click on the button. A window will open as shown below. A login that should be able to create new logins must to be a System administrator.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has [no access] will be listed in [gray] while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

The state and date of the privacy consent according to the General Data Protection Regulation is shown in dependence of the selected database.

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

As a database owner you can edit the permissions and role memberships with the and buttons. Please keep in mind that any change of the permissions may cause serious troubles and should only be used for testing and bug fixing. The final setting of the permissions should be performed by a proper update script of the database. For every action you will get the code that is to be included in an update script (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below). Projects are related to the module DiversityProjects. To get additional information about a project select it in the list and click on the button. 

Starting with database version 02.05.35 next to the projects with full access, a second list provides projects with [Read Only] access (see image below). Use the and buttons to move projects between Accessible and Read Only. If a project is set on [Read Only] a user can still add annotations. Starting with version 4.3.219 a project as a whole can be locked with the restriction of access to read only. For more details see chapter Project administration.

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

To see an overview of the users within a project select one of the project in either list and click on the corresponding button . A window as shown below will open listing all users and their roles with access to the selected project.

To add or remove a role for a login, select the corresponding field and choose or from the context menu (see below).

 

Settings of a login in a database

Depending on the database you can edit the settings of a login as shown below.

If you wish to use settings already defined for another login, click on the Search template button. A window (see below) will open where you can choose among the settings defined for logins in the database.

 

Overview for a login

If you want to see an overview of all permissions and project for a login, click on the button. A window as shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user, roles and projects in the database. 

To remove a user, select it in the list and click on the button. 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

To find users within the database that have no valid login, click on the button. A window as shown below will open, listing the users without a login. Select those that should be removed and click OK. This will include a removal from the collection managers.

 

May 16, 2024

Diversity Agents

Security

A user may be in several groups with diverse rights in the database. Here certain higher groups have all rights of lower groups in addition to special rights for the higher group, e.g. the group User may only read data of certain tables while Typist has the rights of User and additionally may edit the data in certain tables - see overview below.

Summarized overview of some of the groups and their permissions as an example for the module DiversityCollection

Role Permissions in addition to lower role and user group respectively Included rights
Administrator Delete data, edit user permissions DataManager
CollectionManager Administration of collections, handling loans etc. StorageManager
DataManager Delete data, edit image descripton templates Editor
Editor Create new entries and delete details (not entire data sets) Typist
Requester Has the right to place requests for specimen
StorageManager Administration of stored parts, handling loans etc. User
Typist Edit data User
User See the data of the data tables, add annotations

To place a user in one of the groups, select Administration - Database - Logins... from the menu. In the window that will open select a login and a database. The roles available in the selected database will be listed as shown below. Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

 

If you are an Administrator you may add a user to one of these groups.

Any user may have access to several projects.

May 16, 2024

Diversity Agents

Project access for user

The accessibility of projects for users can have 4 different states:

  • No access: The current user has no access to the project
  • Accessible: The current user has access to the project
  • [Read only]: The current user has read only access to the project
  • [Locked]: The project is locked. Any user can either none or read only access to the project

To allow the current user access projects use the [ > ] button for the selected project resp. the [ >> ] button for all projects. To revoke access for the current user use the [ < ]  button for the selected project resp. the [ << ] button for all projects. To change the access for a project to read only use the button and the button to remove a project from the read only list.

 

 

Locking of a project

To lock a selected project use the button. For all users the project will be removed from the accessible or read only list and transferred to the locked list. This is only allowed for a database owner (dbo). Please make sure that you really want to lock a project. Any dataset related to this project will be set to read only for all users. For an introduction, please see the a short tutorial Video starten.

To remove the locked state of a project, select the project in the No access list and click on the  button. The selected project will be moved from the locked list into the read only list for those users that had access to the project.

 

Retrieval of projects from DiversityProjects

Details of the projects within the DiversityWorkbench are stored in the database DiversityProjects. To access further information on a project click on the  button. To edit details in projects you require the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you may use the synchronize function in the user administration window as shown below. If DiversityProjects is not available, you may create a new project by clicking the button. If DiversityProjects is available, use the synchronize function .

     

May 16, 2024

Diversity Agents

Database

  The database for DiversityAgents based on Microsoft SQL-Server 2014 or above.

Organisation of the data

The main data are kept in the table Agent. Contacts are listed in the table AgentContactInformation (see below). For further tables and details see the table descriptions.

Jan 14, 2025

Subsections of Database

Installation

Diversity Workbench modules use Microsoft SQL-Server 2014 or above as database engine. If you do not have a database server with DiversityAgents already available, you have to install the database engine first. Download the free version of Microsoft SQL Server Express 2016 or above from http://www.microsoft.com/downloads/.. Start the program and follow the instructions for the installation.

 

Server configuration

To configure your server for remote access, launch the SQL Server Configuration Manager (see image below).

If the tool is not available via the app menu but you have SqlServerManagmentStudio and SqlServer installed type [Win] + r to open the Run dialog, type the command SQLServerManager16.msc and press [Enter] to start the tool.

Then click on the "Protocols for SQLEXPRESS" node. Right click on "TCP/IP" in the list of Protocols and choose "enable" for TCP/IP.

Right click on the TCP/IP node and select, "Properties" to open a window as shown below.

In the part IPALL clear out the value for "TCP Dynamic Ports". Give a TCP-Port number to use when making remote connections, e.g. "4321" as shown above. You have to restart the SQL Server Express service before you can connect to your database. 

If you use a database on a server, make sure that the firewall of the server allows access via the port you set for the connections (see below). 

Start the Microsoft SQL Server Managment Studio and attach the database as shown below. Choose the node "databases" and right-click on it to open the context menu (see below). Then choose "attach" from the context menu. A window will open where you can choose the file DiversityAgents_Data.MDF from your database directory and attach it to the database engine.

 

After the installation make shure to get the latest updates from http://windowsupdate.microsoft.com/.

 

Database configuration

To configure your Database, use the Client as described in

Database configuration.

Mar 26, 2024

Diversity Agents

Creation

To configure your Database, choose Administration → Database → Rename database to change the name of the database according to your requirements. During this renaming all processes in the database will be terminated (you will get a warning if processes from other host are active).

Afterwards you should adapt the address that is published by the database for access by other modules. Choose Administration → Database → Set published address from the menu. This will change the published address to the name of the server where your database is located and an identifier for you database, e.g. http://xy.diversityworkbench.de/Collection/

 

May 16, 2024

Diversity Agents

Configuration

To configure your Database, choose Administration → Database → Rename database to change the name of the database according to your requirements. During this renaming all processes in the database will be terminated (you will get a warning if processes from other host are active).

Afterwards you should adapt the address that is published by the database for access by other modules. Choose Administration → Database → Set published address from the menu. This will change the published address to the name of the server where your database is located and an identifier for you database, e.g. http://xy.diversityworkbench.de/Collection/

 

May 16, 2024

DiversityAgents Model 2.1.24

Content

DiversityAgents Information Model (version 2.1.24, 12 October, 2024)

Authors M. Weiss, A. Grunz, G. Hagedorn, D. Triebel, S. Seifert
License CC BY-ND 3.0
Suggested citation M. Weiss, A. Grunz, G. Hagedorn, D. Triebel & S. Seifert (2024). DiversityAgents information model (version 2.1.24). http://www.diversityworkbench.net/Portal/DiversityAgentsModel_2.1.24
Notes The model is implemented on MS SQL Server and so the data types are also MS SQL Server specific

A short introduction:

DiversityAgents is the module for the administration of agents within the Diversity Workbench. DiversityAgents provides information for other modules like DiversityCollection and DiversityTaxonNames. DiversityAgents keeps only data directly connected with the handling of agents. Data of other realms like e.g. projects or references are handled in separate modules. DiversityAgents can also be used as a stand-alone application.

  • Agent is the central entity, containing the information directly related to the agent.
  • AgentProject keeps the relation to the projects. Each agent may be included in several projects.
  • AgentImage keeps the images for a agent.
  • AgentContactInformation is the central entity, containing the contact informations for the Agent.
  • AgentRelation keeps the relations between the agents.
  • AgentReference keeps the references containing informations about the agent.

ER-Diagram

Overview over all entities and relations used in the database model

ER-Diagram

TABLES


Table Agent

The main table with the data of the agent

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (= Primary key) NO -
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES Refers to table Agent
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitleDefault value: '' NO -
Version smallint The version of a agent record (revision number, internally filled by system)Default value: (1) NO -
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES Refers to table AgentTitle_Enum
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES -
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES -
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES -
InheritedName nvarchar (255) The last names of the agent (if a person) YES -
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES -
Abbreviation nvarchar (50) Abbreviation of the agent YES -
AgentType nvarchar (50) The type of the agent, e.g. person, companyDefault value: N’person' YES Refers to table AgentType_Enum
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES -
AgentGender nvarchar (50) The gender of the agent YES Refers to table AgentGender_Enum
Description nvarchar (1000) A description of the agent YES -
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES -
Notes nvarchar (MAX) Notes about the agent YES -
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES -
ValidFromDay tinyint The day of the begin of the exsistence of the agent YES -
ValidFromMonth tinyint The month of the begin of the exsistence of the agent YES -
ValidFromYear smallint The year of the begin of the exsistence of the agent YES -
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES -
ValidUntilDay tinyint The day of the end of the exsistence of the agent YES -
ValidUntilMonth tinyint The month of the end of the exsistence of the agent YES -
ValidUntilYear smallint The year of the end of the exsistence of the agent YES -
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary. YES -
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded YES -
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died YES -
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES Refers to table Agent
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to” YES Refers to table AgentSynonymisationType_Enum
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’Default value: N’unchecked’ YES Refers to table RevisionLevel_Enum
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES -
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.Default value: (0) YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
ContentLanguage nvarchar (50) The language of the content YES Refers to table LanguageCode_Enum

Depending on:

  • AgentGender_Enum
  • AgentSynonymisationType_Enum
  • AgentTitle_Enum
  • AgentType_Enum
  • LanguageCode_Enum
  • RevisionLevel_Enum

trgInsAgent

Setting the value of column AgentName according to standard derived from content of given values in columns InheritedNamePrefix, Inheritedname, GivenName, GivenNamePostfix, InheritedNamePostfix and AgentTitle


Table AgentContactInformation

The contact information resp. addresses of the agents

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) NO -
AddressType nvarchar (50) Type of the adress, e.g. private YES Refers to table AddressType_Enum
Country nvarchar (255) Country of the address YES -
City nvarchar (255) City of the address YES -
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES -
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES -
Address nvarchar (255) Free text postal address of the agent YES -
Telephone nvarchar (50) Phone number, including area code YES -
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES -
Telefax nvarchar (50) Fax number, including area code YES -
Email nvarchar (255) E-mail address of the agent YES -
URI nvarchar (255) URI pointing to a homepage containing further information YES -
Notes nvarchar (MAX) Notes about this address YES -
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES -
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise nullDefault value: N’Withhold by default’ YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • AddressType_Enum
  • Agent

trgInsAgentContactInformation


Table AgentDescriptor

The Descriptors for the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
DescriptorID int Unique ID for the descriptor, Part of PK NO -
Descriptor nvarchar (200) The DescriptorDefault value: '’ NO -
URL varchar (500) URL of the Descriptor. In case of a module related Descriptor, the link to the module entry resp. the related webserviceDefault value: '' YES -
DescriptorType nvarchar (50) Type of the Descriptor as described in table AgentDescriptorType_EnumDefault value: N’Descriptor' YES Refers to table AgentDescriptorType_Enum
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Agent
  • AgentDescriptorType_Enum

Table AgentExternalDatabase

The external databases from which data in the database may have been imported from

Column Data type Description Nullable Relation
ExternalDatabaseID int An ID to identify an external data collection of plant names (primary key, the ID has no meaning outside of the DiversityWorkbench system) NO -
ExternalDatabaseName nvarchar (100) The name of the data collection that has been integrated or can be linked to for further analysis YES -
ExternalDatabaseVersion nvarchar (255) The version of this data collection (either official version number, or dates when the collection was integrated) YES -
Rights nvarchar (500) A description of copyright agreements or permission to use data from the external database YES -
ExternalDatabaseAuthors nvarchar (200) The persons or institutions responsible for the external database YES -
ExternalDatabaseURI nvarchar (300) The link to the database provider resp. the external database YES -
ExternalDatabaseInstitution nvarchar (300) The institution responsible for the external database YES -
InternalNotes nvarchar (1500) Additional notes concerning this data collection YES -
ExternalAttribute_AgentID nvarchar (255) The table and field name in the external data collection to which PlantNameAnalysis.ExternalNameID refers YES -
PreferredSequence tinyint For selection in e.g. picklists: of several equal names only the name from the source with the lowest preferred sequence will be provided. YES -
Disabled bit If this source should be disabled for selection of names e.g. in picklists YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database. YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Table AgentExternalID

The ID’s of data that were imported from foreign souces

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
ExternalDatabaseID int The ID of an external taxonomic data collection as defined in AgentExternalDatabase (foreign key + part of primary key)Default value: '' NO Refers to table AgentExternalDatabase
ExternalAgentURI varchar (255) The URI (e.g. LSID) of the external agent YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Agent
  • AgentExternalDatabase

Table AgentHierarchyOther

Other hierarchies of the agent

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
HierarchyID int Identifier of the hierarchy, part of PK NO -
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy NO Refers to table Agent
ValidFrom datetime The start time of the hierarchy, e.g. when a person was employed in an institution YES -
ValidUntil datetime The end of a hierarchy, e.g. when an employment ended YES -
Notes nvarchar (MAX) Notes about the other hierarchy YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Agent

Table AgentIdentifier

Identifier for the agent

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
Identifier nvarchar (400) Identifier for the agent, part of PK NO -
IdentifierURI varchar (500) URI of Identifier YES -
Type nvarchar (50) Type of the identifier as defined in table AgentIdentifierType_Enum YES Refers to table AgentIdentifierType_Enum
Notes nvarchar (MAX) Notes about the identifier YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Agent
  • AgentIdentifierType_Enum

Table AgentImage

The images of the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
URI varchar (255) The complete URI address of the image. This is only a cached value if ResourceID is available referring to the module DiversityResources NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
Description nvarchar (MAX) Description of the resource YES -
Type nvarchar (50) The type of the image YES Refers to table AgentImageType_Enum
Sequence int The sequence of the imageDefault value: (1) YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise nullDefault value: N’Withhold by default' YES -

Depending on:

  • Agent
  • AgentImageType_Enum

trgInsAgentImage


Table AgentKeyword

The keywords for the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
Keyword nvarchar (200) The keyword NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Agent

trgInsAgentKeyword


Table AgentProject

The projects of the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (= Foreign key) NO Refers to table Agent
ProjectID int The ID of the projectDefault value: (0) NO Refers to table ProjectProxy
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Agent
  • ProjectProxy

Table AgentReference

References containing informations about the agent

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
ReferenceTitle nvarchar (255) The title of the publication where information about the agent was published. Note this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (255) URI of reference where information about the agent, e.g. referring to the module DiversityReferences YES -
ReferenceDetails nvarchar (50) Details within the reference, e.g. pages YES -
ContainsImage tinyint If the reference contains an image of the agent YES -
ContainsReferencelist tinyint If the reference contains a publication list of the agent YES -
Notes nvarchar (255) Notes about the reference YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Depending on:

  • Agent

trgInsAgentReference


Table AgentRelation

Relations of the agent to other agents

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
RelatedAgentID int The AgentID of the related agent NO -
RelationType nvarchar (50) The type of the relation between the agents, e.g. “parent of”, “child of”, “married to” YES Refers to table AgentRelationType_Enum
Notes nvarchar (255) Notes about the relation YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Depending on:

  • Agent
  • AgentRelationType_Enum

trgInsAgentRelation


Enumeration tables

Tabledesign

Column Data type Description
Code nvarchar (50) A text code that uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
ParentCode nvarchar (50) The code of the superior entry, if a hierarchy within the entries is necessary
ParentRelation nvarchar (50) Relation to parent entry, e.g. part of
Description nvarchar (500) Description of enumerated object, displayed in the user interface
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayEnable bit Enumerated objects can be hidden from the user interface if this attribute is set to false (= unchecked check box)
URL varchar (500) A link to further information about the enumerated object
InternalNotes nvarchar (500) Internal development notes about usage, definition, etc. of an enumerated object
Icon image A symbol representing this entry in the user interface
ModuleName varchar (50) If the enumerated entry is related to a DiversityWorkbench module or a related webservice, the name of the DiversityWorkbench module, e.g. DiversityAgents
RowGUID uniqueidentifier -Default value: newsequentialid()

Table AddressType_Enum

Lookup table for the types of the addresses

Dependent tables:

  • AgentContactInformation

Content

Code Description
office office address
private private address

Table AgentDescriptorType_Enum

The type of the Descriptors

Dependent tables:

  • AgentDescriptor

Table AgentGender_Enum

Gender of the agent: female or male

Dependent tables:

  • Agent

Content

Code Description
female
male

Table AgentIdentifierType_Enum

Types of the agent identifier, e.g. ISNI

Dependent tables:

  • AgentIdentifier

Content

Code Description
ISNI International Standard Name Identifier (ISO 27729)
ORCID Open Researcher Contributor Identification
ROR Research Organization Registry

Table AgentImageType_Enum

Types of images in table AgentImage, e.g. Logo

Dependent tables:

  • AgentImage

Content

Code Description
Logo Logo
Portrait Portrait

Table AgentNameDisplayType_Enum

Display types of the names of the agents, defining e.g. the position of title, given and inherited part of the name and their abbreviation

Dependent tables:

  • ProjectProxy

Content

Code Description
Abbr The international defined standard arbbreviation; e.g. L. for Linne
G. Ii Given name. Inherited name; e.g. H. Hertel
Gg Ii Given name InheritedName; e.g. Hannes Hertel
Ii, G. Inherited name, GivenName; e.g. Hertel, H.
Ii, Gg Inherited name, GivenName; e.g. Hertel, Hannes
Tt. G. Ii Titel Given name. Inherited name; e.g. Prof. H. Hertel
Tt. Gg Ii Titel Given name Inherited name; e.g. Prof. Hannes Hertel

Table AgentRelationType_Enum

Relation types of agents, e.g. Child of

Dependent tables:

  • AgentRelation

Content

Code Description
Child of
Married to
Parent of

Table AgentSynonymisationType_Enum

Synonymisation types of agents, e.g. synonym to

Dependent tables:

  • Agent

Content

Code Description
replaced with if the agent was replaced by another entry
synonym to if the agent is synonym to another agent

Table AgentTitle_Enum

Lookup table for the titles of the agents

Dependent tables:

  • Agent

Content

Code Description
Dr.
Frater
Pater
Prof.
Prof. Dr.

Table AgentType_Enum

Lookup table for the types of the agents

Dependent tables:

  • Agent

Content

Code Description
Collection
Company
Department
Group
Institution
Person
University

Table LanguageCode_Enum

The codes for the languages

Dependent tables:

  • Agent

Content

Code Description
af Afrikaans
ar Arabisch
az Aserbaidschanisch
be Belarussisch
bg Bulgarisch
ca Katalanisch
cs Tschechisch
da Dänisch
de Deutsch
el Griechisch
en Englisch
es Spanisch
et Estnisch
eu Baskisch
fa Farsi
fi Finnisch
fo Färingisch
fr Französisch
gl Galizisch
gu Gujarati
he Hebräisch
hi Hindi
hr Kroatisch
hu Ungarisch
hy Armenisch
id Indonesisch
is Isländisch
it Italienisch
ja Japanisch
ka Georgisch
kk Kasachisch
kn Kannada
ko Koreanisch
ky Kirgisisch
lt Litauisch
lv Lettisch
mk Mazedonisch
mn Mongolisch
mr Marathi
ms Malaiisch
nl Niederländisch
no Norwegisch
pa Punjabi
pl Polnisch
pt Portugiesisch
ro Rumänisch
ru Russisch
sa Sanskrit
sk Slowakisch
sl Slowenisch
sq Albanisch
sv Schwedisch
sw Swahili
ta Tamil
te Telugu
th Thai
tr Türkisch
tt Tatarisch
uk Ukrainisch
ur Urdu
uz Usbekisch
vi Vietnamesisch
zh Chinesisch

Table RevisionLevel_Enum

Lookup table for the revision level

Dependent tables:

  • Agent

Content

Code Description
checked checked
final revision final revision
review required review required
to be deleted to be deleted
unchecked unchecked

VIEWS


View Agent_Core

Agents that are available for a user and are not ignored

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO
DisplayText nvarchar (204) The name of the agent including indentation for synonyms NO
Version smallint The version of a agent record (revision number, internally filled by system) NO
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES
InheritedName nvarchar (255) The last names of the agent (if a person) YES
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES
Abbreviation nvarchar (50) Abbreviation of the agent YES
AgentType nvarchar (50) The type of the agent, e.g. person, company YES
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES
AgentGender nvarchar (50) The gender of the agent YES
Description nvarchar (1000) A description of the agent YES
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES
Notes nvarchar (MAX) Notes about the agent YES
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES
ValidFromDay tinyint The day of the begin of the exsistence of the agent YES
ValidFromMonth tinyint The month of the begin of the exsistence of the agent YES
ValidFromYear smallint The year of the begin of the exsistence of the agent YES
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES
ValidUntilDay tinyint The day of the end of the exsistence of the agent YES
ValidUntilMonth tinyint The month of the end of the exsistence of the agent YES
ValidUntilYear smallint The year of the end of the exsistence of the agent YES
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary. YES
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded YES
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died YES
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to” YES
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’ YES
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES
ValidFrom varchar (92) The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution YES
ValidUntil varchar (92) The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute YES

Depending on:

  • Agent
  • AgentID_UserAvailable

View AgentID_AvailableReadOnly

Available AgentIDs that are ReadOnly or Locked

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentID_Locked
  • AgentProject
  • ProjectUser

View AgentID_FullAccess

ID of agents with full access (neither read only or locked)

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentProject
  • ProjectProxy
  • ProjectUser

View AgentID_Locked

AgentIDs that are locked due to locking of the project

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentProject
  • ProjectProxy

View AgentID_ReadOnly

AgentIDs that are ReadOnly for a User or are locked due to locking of the project

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentID_Locked
  • AgentProject
  • ProjectUser

View AgentID_UserAvailable

IDs of the agent available for a user

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO

Depending on:

  • Agent
  • AgentProject
  • ProjectUser

View ProjectList

Projects available for a user

Column Data type Description Nullable
ProjectID int The ID of the project, Primary key NO
Project nvarchar (50) The name of the project as stored in the module DiversityProjects NO
ReadOnly int If the user has only read access to data of this project YES
IsLocked bit If the data within the project should not be changeed and the access for all users is restricted to read only YES

Depending on:

  • ProjectProxy
  • ProjectUser

View PublicAgent

Content of table Agent available for the public

Column Data type Description Nullable
DisplayText nvarchar (200) Corresponds to content of column AgentName NO
URI varchar (285) Combines BaseURL of the database and AgentID to provide unique identifier of the dataset YES
AgentID int Unique ID for the Agent (= Primary key) NO
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO
Version smallint The version of a agent record (revision number, internally filled by system) NO
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES
InheritedName nvarchar (255) The last names of the agent (if a person) YES
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES
Abbreviation nvarchar (50) Abbreviation of the agent YES
AgentType nvarchar (50) The type of the agent, e.g. person, company YES
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES
AgentGender nvarchar (50) The gender of the agent YES
Description nvarchar (1000) A description of the agent YES
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES
Notes nvarchar (MAX) Notes about the agent YES
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES
ValidFromDay tinyint The day of the begin of the exsistence of the agent YES
ValidFromMonth tinyint The month of the begin of the exsistence of the agent YES
ValidFromYear smallint The year of the begin of the exsistence of the agent YES
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES
ValidUntilDay tinyint The day of the end of the exsistence of the agent YES
ValidUntilMonth tinyint The month of the end of the exsistence of the agent YES
ValidUntilYear smallint The year of the end of the exsistence of the agent YES
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary. YES
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded YES
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died YES
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to” YES
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’ YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentNames
  • BaseURL
  • DefaultAgentNameDisplayType

View PublicContactInformation

Accumulated public address of an agent within a hierarchy of up to 4 levels

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) NO
ParentName nvarchar (200) Name of the superior agent within the hierarchy YES
AddressType nvarchar (50) Type of the adress, e.g. private YES
Country nvarchar (255) Country of the address YES
City nvarchar (255) City of the address YES
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES
Address nvarchar (255) Free text postal address of the agent YES
Telephone nvarchar (50) Phone number, including area code YES
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES
Telefax nvarchar (50) Fax number, including area code YES
Email nvarchar (255) E-mail address of the agent YES
URI nvarchar (255) URI pointing to a homepage containing further information YES
Notes nvarchar (MAX) Notes about the agent YES
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • AgentContactInformation_Public

View PublicIdentifier

Content of table AgentIdentifier available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
Identifier nvarchar (400) Identifier for the agent, part of PK NO
IdentifierURI varchar (500) URI of Identifier YES
Type nvarchar (50) Type of the identifier as defined in table AgentIdentifierType_Enum YES
Notes nvarchar (MAX) Notes about the agent YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentIdentifier

View PublicImage

Content of table AgentImage available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
URI varchar (255) The complete URI address of the image. This is only a cached value if ResourceID is available referring to the module DiversityResources NO
Description nvarchar (MAX) A description of the agent YES
Type nvarchar (50) The type of the image YES
Sequence int The sequence of the image YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentImage

View PublicReference

Content of table AgentReference available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
ReferenceTitle nvarchar (255) The title of the publication where information about the agent was published. Note this is only a cached value where ReferenceURI is present NO
ReferenceURI varchar (255) URI of reference where information about the agent, e.g. referring to the module DiversityReferences YES
ReferenceDetails nvarchar (50) Details within the reference, e.g. pages YES
ContainsImage tinyint If the reference contains an image of the agent YES
ContainsReferencelist tinyint If the reference contains a publication list of the agent YES
Notes nvarchar (255) Notes about the agent YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentReference

View PublicRelation

Content of table AgentRelation available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
RelatedAgentID int The AgentID of the related agent NO
RelationType nvarchar (50) The type of the relation between the agents, e.g. “parent of”, “child of”, “married to” YES
Notes nvarchar (255) Notes about the agent YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentRelation

View UserInfo

Information about the user as stored in table UserProxy

Column Data type Description Nullable
LoginName nvarchar (50) The login name of the user, Primary key NO
CombinedNameCache nvarchar (50) A combined name of the user, created on the base of an entry in the module DiversityUsers YES
UserURI varchar (255) Refers to UserInfo.UserID in database DiversityUsers YES
ProjectID int The ID of the default project of the user as stored in table ProjectProxy YES

Depending on:

  • UserProxy

View ViewAgentAddress

Accumulated address of an agent within a hierarchy of up to 4 levels

Column Data type Description Nullable
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) YES
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) YES
ParentName nvarchar (200) Name of the superior agent within the hierarchy YES
AddressType nvarchar (50) Type of the adress, e.g. private YES
Country nvarchar (255) Country of the address YES
City nvarchar (255) City of the address YES
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES
Address nvarchar (255) Free text postal address of the agent YES
Telephone nvarchar (50) Phone number, including area code YES
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES
Telefax nvarchar (50) Fax number, including area code YES
Email nvarchar (255) E-mail address of the agent YES
URI nvarchar (255) URI pointing to a homepage containing further information YES
Notes nvarchar (MAX) Notes about this address YES
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES

Depending on:

  • ViewAgentAddress0
  • ViewAgentAddress1
  • ViewAgentAddress2
  • ViewAgentAddress3
  • ViewAgentAddress4

View ViewAgentNames

The names of the agents as retrieved for the default display type with function AgentNames

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO

Depending on:

  • AgentNames
  • DefaultAgentNameDisplayType

View ViewBaseURL

Provides the basic address for accessing the database as defined in function BaseURL

Column Data type Description Nullable
BaseURL varchar (255) Basic address for accessing the database YES

Depending on:

  • BaseURL

View ViewDefaultAgentNameDisplayType

The default display type as set for the default project as defined in function DefaultAgentNameDisplayType

Column Data type Description Nullable
DefaultAgentNameDisplayType nvarchar (50) The default display type YES

Depending on:

  • DefaultAgentNameDisplayType

View ViewDiversityWorkbenchModule

Provides the name of the DiversityWorkbench module as defined in function DiversityWorkbenchModule

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) The name of the DiversityWorkbench module YES

Depending on:

  • DiversityWorkbenchModule
Dec 17, 2024

Diversity Agents

TABLES, VIEWS, FUNCTIONS, PROCEDURES, ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES

ER-Diagram


Table Agent

The main table with the data of the agent

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (= Primary key) NO -
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES Refers to table Agent
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitleDefault value: '' NO -
Version smallint The version of a agent record (revision number, internally filled by system)Default value: (1) NO -
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES Refers to table AgentTitle_Enum
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES -
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES -
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES -
InheritedName nvarchar (255) The last names of the agent (if a person) YES -
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES -
Abbreviation nvarchar (50) Abbreviation of the agent YES -
AgentType nvarchar (50) The type of the agent, e.g. person, companyDefault value: N’person' YES Refers to table AgentType_Enum
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES -
AgentGender nvarchar (50) The gender of the agent YES Refers to table AgentGender_Enum
Description nvarchar (1000) A description of the agent YES -
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES -
Notes nvarchar (MAX) Notes about the agent YES -
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES -
ValidFromDay tinyint The day of the begin of the exsistence of the agent YES -
ValidFromMonth tinyint The month of the begin of the exsistence of the agent YES -
ValidFromYear smallint The year of the begin of the exsistence of the agent YES -
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES -
ValidUntilDay tinyint The day of the end of the exsistence of the agent YES -
ValidUntilMonth tinyint The month of the end of the exsistence of the agent YES -
ValidUntilYear smallint The year of the end of the exsistence of the agent YES -
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary. YES -
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded YES -
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died YES -
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES Refers to table Agent
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to” YES Refers to table AgentSynonymisationType_Enum
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’Default value: N’unchecked’ YES Refers to table RevisionLevel_Enum
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES -
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.Default value: (0) YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
ContentLanguage nvarchar (50) The language of the content YES Refers to table LanguageCode_Enum

Depending on:

  • AgentGender_Enum
  • AgentSynonymisationType_Enum
  • AgentTitle_Enum
  • AgentType_Enum
  • LanguageCode_Enum
  • RevisionLevel_Enum

trgInsAgent

Setting the value of column AgentName according to standard derived from content of given values in columns InheritedNamePrefix, Inheritedname, GivenName, GivenNamePostfix, InheritedNamePostfix and AgentTitle


Table AgentContactInformation

The contact information resp. addresses of the agents

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) NO -
AddressType nvarchar (50) Type of the adress, e.g. private YES Refers to table AddressType_Enum
Country nvarchar (255) Country of the address YES -
City nvarchar (255) City of the address YES -
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES -
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES -
Address nvarchar (255) Free text postal address of the agent YES -
Telephone nvarchar (50) Phone number, including area code YES -
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES -
Telefax nvarchar (50) Fax number, including area code YES -
Email nvarchar (255) E-mail address of the agent YES -
URI nvarchar (255) URI pointing to a homepage containing further information YES -
Notes nvarchar (MAX) Notes about this address YES -
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES -
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise nullDefault value: N’Withhold by default’ YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • AddressType_Enum
  • Agent

trgInsAgentContactInformation


Table AgentDescriptor

The Descriptors for the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
DescriptorID int Unique ID for the descriptor, Part of PK NO -
Descriptor nvarchar (200) The DescriptorDefault value: '’ NO -
URL varchar (500) URL of the Descriptor. In case of a module related Descriptor, the link to the module entry resp. the related webserviceDefault value: '' YES -
DescriptorType nvarchar (50) Type of the Descriptor as described in table AgentDescriptorType_EnumDefault value: N’Descriptor' YES Refers to table AgentDescriptorType_Enum
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Agent
  • AgentDescriptorType_Enum

Table AgentExternalDatabase

The external databases from which data in the database may have been imported from

Column Data type Description Nullable Relation
ExternalDatabaseID int An ID to identify an external data collection of plant names (primary key, the ID has no meaning outside of the DiversityWorkbench system) NO -
ExternalDatabaseName nvarchar (100) The name of the data collection that has been integrated or can be linked to for further analysis YES -
ExternalDatabaseVersion nvarchar (255) The version of this data collection (either official version number, or dates when the collection was integrated) YES -
Rights nvarchar (500) A description of copyright agreements or permission to use data from the external database YES -
ExternalDatabaseAuthors nvarchar (200) The persons or institutions responsible for the external database YES -
ExternalDatabaseURI nvarchar (300) The link to the database provider resp. the external database YES -
ExternalDatabaseInstitution nvarchar (300) The institution responsible for the external database YES -
InternalNotes nvarchar (1500) Additional notes concerning this data collection YES -
ExternalAttribute_AgentID nvarchar (255) The table and field name in the external data collection to which PlantNameAnalysis.ExternalNameID refers YES -
PreferredSequence tinyint For selection in e.g. picklists: of several equal names only the name from the source with the lowest preferred sequence will be provided. YES -
Disabled bit If this source should be disabled for selection of names e.g. in picklists YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database. YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Table AgentExternalID

The ID’s of data that were imported from foreign souces

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
ExternalDatabaseID int The ID of an external taxonomic data collection as defined in AgentExternalDatabase (foreign key + part of primary key)Default value: '' NO Refers to table AgentExternalDatabase
ExternalAgentURI varchar (255) The URI (e.g. LSID) of the external agent YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Agent
  • AgentExternalDatabase

Table AgentHierarchyOther

Other hierarchies of the agent

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
HierarchyID int Identifier of the hierarchy, part of PK NO -
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy NO Refers to table Agent
ValidFrom datetime The start time of the hierarchy, e.g. when a person was employed in an institution YES -
ValidUntil datetime The end of a hierarchy, e.g. when an employment ended YES -
Notes nvarchar (MAX) Notes about the other hierarchy YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Agent

Table AgentIdentifier

Identifier for the agent

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
Identifier nvarchar (400) Identifier for the agent, part of PK NO -
IdentifierURI varchar (500) URI of Identifier YES -
Type nvarchar (50) Type of the identifier as defined in table AgentIdentifierType_Enum YES Refers to table AgentIdentifierType_Enum
Notes nvarchar (MAX) Notes about the identifier YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Agent
  • AgentIdentifierType_Enum

Table AgentImage

The images of the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
URI varchar (255) The complete URI address of the image. This is only a cached value if ResourceID is available referring to the module DiversityResources NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
Description nvarchar (MAX) Description of the resource YES -
Type nvarchar (50) The type of the image YES Refers to table AgentImageType_Enum
Sequence int The sequence of the imageDefault value: (1) YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise nullDefault value: N’Withhold by default' YES -

Depending on:

  • Agent
  • AgentImageType_Enum

trgInsAgentImage


Table AgentKeyword

The keywords for the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (foreign key + part of primary key) NO Refers to table Agent
Keyword nvarchar (200) The keyword NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Agent

trgInsAgentKeyword


Table AgentProject

The projects of the agents

Column Data type Description Nullable Relation
AgentID int Unique ID for the Agent (= Foreign key) NO Refers to table Agent
ProjectID int The ID of the projectDefault value: (0) NO Refers to table ProjectProxy
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Agent
  • ProjectProxy

Table AgentReference

References containing informations about the agent

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
ReferenceTitle nvarchar (255) The title of the publication where information about the agent was published. Note this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (255) URI of reference where information about the agent, e.g. referring to the module DiversityReferences YES -
ReferenceDetails nvarchar (50) Details within the reference, e.g. pages YES -
ContainsImage tinyint If the reference contains an image of the agent YES -
ContainsReferencelist tinyint If the reference contains a publication list of the agent YES -
Notes nvarchar (255) Notes about the reference YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Depending on:

  • Agent

trgInsAgentReference


Table AgentRelation

Relations of the agent to other agents

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO Refers to table Agent
RelatedAgentID int The AgentID of the related agent NO -
RelationType nvarchar (50) The type of the relation between the agents, e.g. “parent of”, “child of”, “married to” YES Refers to table AgentRelationType_Enum
Notes nvarchar (255) Notes about the relation YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Depending on:

  • Agent
  • AgentRelationType_Enum

trgInsAgentRelation


VIEWS


View Agent_Core

Agents that are available for a user and are not ignored

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO
DisplayText nvarchar (204) The name of the agent including indentation for synonyms NO
Version smallint The version of a agent record (revision number, internally filled by system) NO
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES
InheritedName nvarchar (255) The last names of the agent (if a person) YES
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES
Abbreviation nvarchar (50) Abbreviation of the agent YES
AgentType nvarchar (50) The type of the agent, e.g. person, company YES
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES
AgentGender nvarchar (50) The gender of the agent YES
Description nvarchar (1000) A description of the agent YES
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES
Notes nvarchar (MAX) Notes about the agent YES
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES
ValidFromDay tinyint The day of the begin of the exsistence of the agent YES
ValidFromMonth tinyint The month of the begin of the exsistence of the agent YES
ValidFromYear smallint The year of the begin of the exsistence of the agent YES
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES
ValidUntilDay tinyint The day of the end of the exsistence of the agent YES
ValidUntilMonth tinyint The month of the end of the exsistence of the agent YES
ValidUntilYear smallint The year of the end of the exsistence of the agent YES
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary. YES
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded YES
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died YES
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to” YES
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’ YES
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES
ValidFrom varchar (92) - YES
ValidUntil varchar (92) - YES

Depending on:

  • Agent
  • AgentID_UserAvailable

View AgentID_AvailableReadOnly

Available AgentIDs that are ReadOnly or Locked

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentID_Locked
  • AgentProject
  • ProjectUser

View AgentID_FullAccess

ID of agents with full access (neither read only or locked)

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentProject
  • ProjectProxy
  • ProjectUser

View AgentID_Locked

AgentIDs that are locked due to locking of the project

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentProject
  • ProjectProxy

View AgentID_ReadOnly

AgentIDs that are ReadOnly for a User or are locked due to locking of the project

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Foreign key) NO

Depending on:

  • AgentID_Locked
  • AgentProject
  • ProjectUser

View AgentID_UserAvailable

IDs of the agent available for a user

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO

Depending on:

  • Agent
  • AgentProject
  • ProjectUser

View ProjectList

Projects available for a user

Column Data type Description Nullable
ProjectID int The ID of the project, Primary key NO
Project nvarchar (50) The name of the project as stored in the module DiversityProjects NO
ReadOnly int If the user has only read access to data of this project YES
IsLocked bit If the data within the project should not be changeed and the access for all users is restricted to read only YES

Depending on:

  • ProjectProxy
  • ProjectUser

View PublicAgent

Content of table Agent available for the public

Column Data type Description Nullable
DisplayText nvarchar (200) Corresponds to content of column AgentName NO
URI varchar (285) Combines BaseURL of the database and AgentID to provide unique identifier of the dataset YES
AgentID int Unique ID for the Agent (= Primary key) NO
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO
Version smallint The version of a agent record (revision number, internally filled by system) NO
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES
InheritedName nvarchar (255) The last names of the agent (if a person) YES
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES
Abbreviation nvarchar (50) Abbreviation of the agent YES
AgentType nvarchar (50) The type of the agent, e.g. person, company YES
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES
AgentGender nvarchar (50) The gender of the agent YES
Description nvarchar (1000) A description of the agent YES
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES
Notes nvarchar (MAX) Notes about the agent YES
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES
ValidFromDay tinyint The day of the begin of the exsistence of the agent YES
ValidFromMonth tinyint The month of the begin of the exsistence of the agent YES
ValidFromYear smallint The year of the begin of the exsistence of the agent YES
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES
ValidUntilDay tinyint The day of the end of the exsistence of the agent YES
ValidUntilMonth tinyint The month of the end of the exsistence of the agent YES
ValidUntilYear smallint The year of the end of the exsistence of the agent YES
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary. YES
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded YES
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died YES
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to” YES
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’ YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentNames
  • BaseURL
  • DefaultAgentNameDisplayType

View PublicContactInformation

Accumulated public address of an agent within a hierarchy of up to 4 levels

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) NO
ParentName nvarchar (200) Name of the superior agent within the hierarchy YES
AddressType nvarchar (50) Type of the adress, e.g. private YES
Country nvarchar (255) Country of the address YES
City nvarchar (255) City of the address YES
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES
Address nvarchar (255) Free text postal address of the agent YES
Telephone nvarchar (50) Phone number, including area code YES
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES
Telefax nvarchar (50) Fax number, including area code YES
Email nvarchar (255) E-mail address of the agent YES
URI nvarchar (255) URI pointing to a homepage containing further information YES
Notes nvarchar (MAX) Notes about the agent YES
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • AgentContactInformation_Public

View PublicIdentifier

Content of table AgentIdentifier available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
Identifier nvarchar (400) Identifier for the agent, part of PK NO
IdentifierURI varchar (500) URI of Identifier YES
Type nvarchar (50) Type of the identifier as defined in table AgentIdentifierType_Enum YES
Notes nvarchar (MAX) Notes about the agent YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentIdentifier

View PublicImage

Content of table AgentImage available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
URI varchar (255) The complete URI address of the image. This is only a cached value if ResourceID is available referring to the module DiversityResources NO
Description nvarchar (MAX) A description of the agent YES
Type nvarchar (50) The type of the image YES
Sequence int The sequence of the image YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentImage

View PublicReference

Content of table AgentReference available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
ReferenceTitle nvarchar (255) The title of the publication where information about the agent was published. Note this is only a cached value where ReferenceURI is present NO
ReferenceURI varchar (255) URI of reference where information about the agent, e.g. referring to the module DiversityReferences YES
ReferenceDetails nvarchar (50) Details within the reference, e.g. pages YES
ContainsImage tinyint If the reference contains an image of the agent YES
ContainsReferencelist tinyint If the reference contains a publication list of the agent YES
Notes nvarchar (255) Notes about the agent YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentReference

View PublicRelation

Content of table AgentRelation available for the public

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
RelatedAgentID int The AgentID of the related agent NO
RelationType nvarchar (50) The type of the relation between the agents, e.g. “parent of”, “child of”, “married to” YES
Notes nvarchar (255) Notes about the agent YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES

Depending on:

  • Agent
  • AgentRelation

View UserInfo

Information about the user as stored in table UserProxy

Column Data type Description Nullable
LoginName nvarchar (50) The login name of the user, Primary key NO
CombinedNameCache nvarchar (50) A combined name of the user, created on the base of an entry in the module DiversityUsers YES
UserURI varchar (255) Refers to UserInfo.UserID in database DiversityUsers YES
ProjectID int The ID of the default project of the user as stored in table ProjectProxy YES

Depending on:

  • UserProxy

View ViewAgentAddress

Accumulated address of an agent within a hierarchy of up to 4 levels

Column Data type Description Nullable
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) YES
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) YES
ParentName nvarchar (200) Name of the superior agent within the hierarchy YES
AddressType nvarchar (50) Type of the adress, e.g. private YES
Country nvarchar (255) Country of the address YES
City nvarchar (255) City of the address YES
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES
Address nvarchar (255) Free text postal address of the agent YES
Telephone nvarchar (50) Phone number, including area code YES
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES
Telefax nvarchar (50) Fax number, including area code YES
Email nvarchar (255) E-mail address of the agent YES
URI nvarchar (255) URI pointing to a homepage containing further information YES
Notes nvarchar (MAX) Notes about this address YES
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES

Depending on:

  • ViewAgentAddress0
  • ViewAgentAddress1
  • ViewAgentAddress2
  • ViewAgentAddress3
  • ViewAgentAddress4

View ViewAgentNames

The names of the agents as retrieved for the default display type with function AgentNames

Column Data type Description Nullable
AgentID int Unique ID for the Agent (= Primary key) NO
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO

Depending on:

  • AgentNames
  • DefaultAgentNameDisplayType

View ViewBaseURL

Provides the basic address for accessing the database as defined in function BaseURL

Column Data type Description Nullable
BaseURL varchar (255) Basic address for accessing the database YES

Depending on:

  • BaseURL

View ViewDefaultAgentNameDisplayType

The default display type as set for the default project as defined in function DefaultAgentNameDisplayType

Column Data type Description Nullable
DefaultAgentNameDisplayType nvarchar (50) The default display type YES

Depending on:

  • DefaultAgentNameDisplayType

View ViewDiversityWorkbenchModule

Provides the name of the DiversityWorkbench module as defined in function DiversityWorkbenchModule

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) The name of the DiversityWorkbench module YES

Depending on:

  • DiversityWorkbenchModule

FUNCTIONS


Function AgentAddress

The address of the agent as collected from the hierarchy

Parameter DataType Description
@AgentID int The ID of the Agent
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key)
ParentName nvarchar (4000) -
AddressType nvarchar (50) Type of the adress, e.g. private
Country nvarchar (255) Country of the address
City nvarchar (255) City of the address
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city)
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box
Address nvarchar (255) Free text postal address of the agent
Telephone nvarchar (50) Phone number, including area code
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent
Telefax nvarchar (50) Fax number, including area code
Email nvarchar (255) E-mail address of the agent
URI nvarchar (255) URI pointing to a homepage containing further information
Notes nvarchar (MAX) Notes about the agent
ValidFrom datetime The date when this address became valid as date according to ISO 8601
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601

Depending on:

  • Agent
  • AgentContactInformation

Function AgentChildNodes

Returns the list of agents within the hierarchy underneath the agent with the given ID (=AgentID)

Parameter DataType Description
@ID int The AgentID of the agent for which the hierarchy should be retrieved
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle
Version smallint The version of a agent record (revision number, internally filled by system)
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof.
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution
InheritedName nvarchar (255) The last names of the agent (if a person)
Abbreviation nvarchar (50) Abbreviation of the agent
AgentType nvarchar (50) The type of the agent, e.g. person, company
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator”
Description nvarchar (1000) A description of the agent
Notes nvarchar (500) Notes about the agent
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year
ValidFromDay tinyint The day of the begin of the exsistence of the agent
ValidFromMonth tinyint The month of the begin of the exsistence of the agent
ValidFromYear smallint The year of the begin of the exsistence of the agent
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year
ValidUntilDay tinyint The day of the end of the exsistence of the agent
ValidUntilMonth tinyint The month of the end of the exsistence of the agent
ValidUntilYear smallint The year of the end of the exsistence of the agent
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary.
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to”
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null
ContentLanguage nvarchar (50) The language of the content

Depending on:

  • Agent

Function AgentContactInformation_Public

Provides the first contact information that is not withheld and valid including contact information of parent agents

Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key)
ParentName nvarchar (200) -
AddressType nvarchar (50) Type of the adress, e.g. private
Country nvarchar (255) Country of the address
City nvarchar (255) City of the address
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city)
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box
Address nvarchar (255) Free text postal address of the agent
Telephone nvarchar (50) Phone number, including area code
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent
Telefax nvarchar (50) Fax number, including area code
Email nvarchar (255) E-mail address of the agent
URI nvarchar (255) URI pointing to a homepage containing further information
Notes nvarchar (MAX) Notes about the agent
ValidFrom datetime The date when this address became valid as date according to ISO 8601
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601
LogUpdatedWhen smalldatetime Date and time when the data were last updated.

Depending on:

  • Agent
  • AgentContactInformation

Function AgentHierarchy

Returns the list of agents within the hierarchy starting at the topmost agent related to the agent with the given AgentID

Parameter DataType Description
@AgentID int The AgentID of the agent for which the hierarchy should be retrieved
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle
Version smallint The version of a agent record (revision number, internally filled by system)
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof.
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution
InheritedName nvarchar (255) The last names of the agent (if a person)
Abbreviation nvarchar (50) Abbreviation of the agent
AgentType nvarchar (50) The type of the agent, e.g. person, company
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator”
Description nvarchar (1000) A description of the agent
Notes nvarchar (500) Notes about the agent
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year
ValidFromDay tinyint The day of the begin of the exsistence of the agent
ValidFromMonth tinyint The month of the begin of the exsistence of the agent
ValidFromYear smallint The year of the begin of the exsistence of the agent
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year
ValidUntilDay tinyint The day of the end of the exsistence of the agent
ValidUntilMonth tinyint The month of the end of the exsistence of the agent
ValidUntilYear smallint The year of the end of the exsistence of the agent
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary.
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to”
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null
ContentLanguage nvarchar (50) The language of the content

Depending on:

  • Agent
  • AgentChildNodes
  • AgentTopID

Function AgentHierarchyAllSuperior

Returns the list of all superior agents within the hierarchy and other hierarchies related to the agent with the given AgentID

Parameter DataType Description
@AgentID int The ID of the Agent
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle

Depending on:

  • Agent
  • AgentHierarchyOther
  • AgentSuperiorList

Function AgentNames

Returns a table that lists all the agents with their names according to the selected display type

Parameter DataType Description
@DisplayType nvarchar (50) The type of the display as documented in the table dbo.AgentNameDisplayType_Enum
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle

Depending on:

  • Agent

Function AgentSuperiorList

Returns the list of superior agents as retrieved from the hierarchy

Parameter DataType Description
@AgentID int Unique ID for the Agent (= Primary key)
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle
Version smallint The version of a agent record (revision number, internally filled by system)
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof.
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution
InheritedName nvarchar (255) The last names of the agent (if a person)
Abbreviation nvarchar (50) Abbreviation of the agent
AgentType nvarchar (50) The type of the agent, e.g. person, company
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator”
Description nvarchar (1000) A description of the agent
Notes nvarchar (500) Notes about the agent
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year
ValidFromDay tinyint The day of the begin of the exsistence of the agent
ValidFromMonth tinyint The month of the begin of the exsistence of the agent
ValidFromYear smallint The year of the begin of the exsistence of the agent
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year
ValidUntilDay tinyint The day of the end of the exsistence of the agent
ValidUntilMonth tinyint The month of the end of the exsistence of the agent
ValidUntilYear smallint The year of the end of the exsistence of the agent
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary.
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to”
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null
ContentLanguage nvarchar (50) The language of the content
DisplayOrder int Display order according to the hierarchy with 1 for the current dataset und increasing values for higher levels in the hierarchy

Depending on:

  • Agent

Function AgentSynonymTopID

Returns the top AgentID within the synyonym hierarchy for a given AgentID

DataType: int

Parameter DataType Description
@AgentID int Unique ID for the Agent (= Primary key)

Depending on:

  • Agent

Function AgentSynonymy

Returns all agents within the synonymy of the given agent

Parameter DataType Description
@AgentID int Unique ID for the Agent (= Primary key)
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle
Version smallint The version of a agent record (revision number, internally filled by system)
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof.
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution
InheritedName nvarchar (255) The last names of the agent (if a person)
Abbreviation nvarchar (50) Abbreviation of the agent
AgentType nvarchar (50) The type of the agent, e.g. person, company
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator”
Description nvarchar (1000) A description of the agent
Notes nvarchar (500) Notes about the agent
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year
ValidFromDay tinyint The day of the begin of the exsistence of the agent
ValidFromMonth tinyint The month of the begin of the exsistence of the agent
ValidFromYear smallint The year of the begin of the exsistence of the agent
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year
ValidUntilDay tinyint The day of the end of the exsistence of the agent
ValidUntilMonth tinyint The month of the end of the exsistence of the agent
ValidUntilYear smallint The year of the end of the exsistence of the agent
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary.
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to”
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null
ContentLanguage nvarchar (50) The language of the content

Depending on:

  • Agent
  • AgentSynonymTopID
  • AgentSynonymyChildNodes

Function AgentSynonymyChildNodes

The depending synonymys of a given agent

Parameter DataType Description
@ID int The AgentID of the agent for which the depending synonymys should be retrieved
Column DataType Description
AgentID int Unique ID for the Agent (= Primary key)
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle
Version smallint The version of a agent record (revision number, internally filled by system)
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof.
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution
InheritedName nvarchar (255) The last names of the agent (if a person)
Abbreviation nvarchar (50) Abbreviation of the agent
AgentType nvarchar (50) The type of the agent, e.g. person, company
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator”
Description nvarchar (1000) A description of the agent
Notes nvarchar (500) Notes about the agent
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year
ValidFromDay tinyint The day of the begin of the exsistence of the agent
ValidFromMonth tinyint The month of the begin of the exsistence of the agent
ValidFromYear smallint The year of the begin of the exsistence of the agent
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year
ValidUntilDay tinyint The day of the end of the exsistence of the agent
ValidUntilMonth tinyint The month of the end of the exsistence of the agent
ValidUntilYear smallint The year of the end of the exsistence of the agent
ValidDateSupplement nvarchar (255) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’. The time of the valid date if necessary.
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources
SynonymisationType nvarchar (50) The type of the synonymisation like “replaced with”, “synonym to”
RevisionLevel nvarchar (50) The level of the revision of the agent, e.g. ‘unchecked’, ‘final revision’
PlaceOfBirth nvarchar (500) The place (e.g. a city) where a person was born or an institution was founded
PlaceOfDeath nvarchar (500) The place (e.g.a city) where the person died
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null
ContentLanguage nvarchar (50) The language of the content

Depending on:

  • Agent

Function AgentTopID

Returns the top ID within the hierarchy for a given AgentID from the table Agent.

DataType: int

Parameter DataType Description
@AgentID int The AgentID of the agent for which the top ID should be retrieved

Depending on:

  • Agent

Function BaseURL

Provides the basic address for accessing the database

DataType: varchar (255)


Function DefaultAgentNameDisplayType

The default display type as set for the default project

DataType: nvarchar (50)

Depending on:

  • DefaultProjectID
  • ProjectProxy

Function DefaultProjectID

Returns the default ProjectID for a user as set in table UserProxy

DataType: int

Depending on:

  • ProjectUser
  • UserProxy

Function DiversityWorkbenchModule

The name of the DiversityWorkbench module

DataType: nvarchar (50)


Function UserID

ID of the User as stored in table UserProxy

DataType: int

Depending on:

  • UserProxy

Function Version

The version of the database

DataType: nvarchar (8)


Function VersionClient

Version of the client software compatible with the version of the database

DataType: nvarchar (11)


PROCEDURES


Procedure procInsertAgentCopy

Creates a copy of a given agent and returns the AgentID of the new agent

Parameter DataType Description
@AgentID int The AgentID of the created agent
@CopyID int The AgentID of the agent that should be copied
@AgentName nvarchar (200) A temporary display text for the created agent

Depending on:

  • Agent
  • AgentContactInformation
  • AgentExternalID
  • AgentImage
  • AgentKeyword
  • AgentProject
  • AgentReference
  • AgentRelation

Procedure procSetVersionAgent

Setting the version of a dataset

Parameter DataType Description
@ID int The AgentID of the agent

Depending on:

  • Agent

Procedure SetUserProjects

Create database user and assign training projects

Parameter DataType Description
@User varchar (50) LoginName of the User

Depending on:

  • UserProxy

ROLES

Content of cell Permission
Not granted
Name of other role Inherited from other role
Granted

Role DiversityWorkbenchAdministrator

Role for the adminstration of the database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
AddressType_Enum Diversity Workbench User TABLE
Agent Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
Agent_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentContactInformation Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentContactInformation_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentDescriptor Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentDescriptor_log Diversity Workbench User Diversity Workbench Editor TABLE
AgentDescriptorType_Enum Diversity Workbench User TABLE
AgentExternalDatabase Diversity Workbench User TABLE
AgentExternalDatabase_log TABLE
AgentExternalID Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentExternalID_log TABLE
AgentGender_Enum Diversity Workbench User TABLE
AgentHierarchyOther Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentHierarchyOther_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentIdentifier Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentIdentifier_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentIdentifierType_Enum Diversity Workbench User TABLE
AgentImage Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentImage_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentImageType_Enum Diversity Workbench User TABLE
AgentKeyword Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentKeyword_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentNameDisplayType_Enum Diversity Workbench User TABLE
AgentProject Diversity Workbench User Diversity Workbench Editor TABLE
AgentProject_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentReference Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentReference_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentRelation Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentRelation_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AgentRelationType_Enum Diversity Workbench User TABLE
AgentSynonymisationType_Enum Diversity Workbench User TABLE
AgentTitle_Enum Diversity Workbench User TABLE
AgentType_Enum Diversity Workbench User TABLE
LanguageCode_Enum Diversity Workbench User TABLE
RevisionLevel_Enum Diversity Workbench User TABLE
Agent_Core Diversity Workbench User VIEW
AgentID_AvailableReadOnly Diversity Workbench User VIEW
AgentID_FullAccess Diversity Workbench User VIEW
AgentID_Locked Diversity Workbench User VIEW
AgentID_ReadOnly Diversity Workbench User VIEW
AgentID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
PublicAgent Diversity Workbench User VIEW
PublicContactInformation Diversity Workbench User VIEW
PublicIdentifier Diversity Workbench User VIEW
PublicImage Diversity Workbench User VIEW
PublicReference Diversity Workbench User VIEW
PublicRelation Diversity Workbench User VIEW
UserInfo Diversity Workbench Editor Diversity Workbench Editor VIEW
ViewAgentAddress Diversity Workbench User VIEW
ViewAgentNames Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDefaultAgentNameDisplayType Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
AgentAddress Diversity Workbench User FUNCTION
AgentChildNodes Diversity Workbench User FUNCTION
AgentContactInformation_Public Diversity Workbench User FUNCTION
AgentHierarchy Diversity Workbench User FUNCTION
AgentHierarchyAllSuperior Diversity Workbench User FUNCTION
AgentNames Diversity Workbench User FUNCTION
AgentSuperiorList Diversity Workbench User FUNCTION
AgentSynonymTopID Diversity Workbench User FUNCTION
AgentSynonymy Diversity Workbench User FUNCTION
AgentSynonymyChildNodes Diversity Workbench User FUNCTION
AgentTopID Diversity Workbench User FUNCTION
BaseURL Diversity Workbench User FUNCTION
DefaultAgentNameDisplayType Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procInsertAgentCopy Diversity Workbench Editor PROCEDURE
procSetVersionAgent Diversity Workbench Editor PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchEditor

Role DiversityWorkbenchEditor

Role with write access for the database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
AddressType_Enum Diversity Workbench User TABLE
Agent Diversity Workbench User TABLE
Agent_log TABLE
AgentContactInformation Diversity Workbench User TABLE
AgentContactInformation_log TABLE
AgentDescriptor Diversity Workbench User TABLE
AgentDescriptor_log Diversity Workbench User TABLE
AgentDescriptorType_Enum Diversity Workbench User TABLE
AgentExternalDatabase Diversity Workbench User TABLE
AgentExternalDatabase_log TABLE
AgentExternalID Diversity Workbench User TABLE
AgentExternalID_log TABLE
AgentGender_Enum Diversity Workbench User TABLE
AgentHierarchyOther Diversity Workbench User TABLE
AgentHierarchyOther_log TABLE
AgentIdentifier Diversity Workbench User TABLE
AgentIdentifier_log TABLE
AgentIdentifierType_Enum Diversity Workbench User TABLE
AgentImage Diversity Workbench User TABLE
AgentImage_log TABLE
AgentImageType_Enum Diversity Workbench User TABLE
AgentKeyword Diversity Workbench User TABLE
AgentKeyword_log TABLE
AgentNameDisplayType_Enum Diversity Workbench User TABLE
AgentProject Diversity Workbench User TABLE
AgentProject_log TABLE
AgentReference Diversity Workbench User TABLE
AgentReference_log TABLE
AgentRelation Diversity Workbench User TABLE
AgentRelation_log TABLE
AgentRelationType_Enum Diversity Workbench User TABLE
AgentSynonymisationType_Enum Diversity Workbench User TABLE
AgentTitle_Enum Diversity Workbench User TABLE
AgentType_Enum Diversity Workbench User TABLE
LanguageCode_Enum Diversity Workbench User TABLE
RevisionLevel_Enum Diversity Workbench User TABLE
Agent_Core Diversity Workbench User VIEW
AgentID_AvailableReadOnly Diversity Workbench User VIEW
AgentID_FullAccess Diversity Workbench User VIEW
AgentID_Locked Diversity Workbench User VIEW
AgentID_ReadOnly Diversity Workbench User VIEW
AgentID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
PublicAgent Diversity Workbench User VIEW
PublicContactInformation Diversity Workbench User VIEW
PublicIdentifier Diversity Workbench User VIEW
PublicImage Diversity Workbench User VIEW
PublicReference Diversity Workbench User VIEW
PublicRelation Diversity Workbench User VIEW
UserInfo VIEW
ViewAgentAddress Diversity Workbench User VIEW
ViewAgentNames Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDefaultAgentNameDisplayType Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
AgentAddress Diversity Workbench User FUNCTION
AgentChildNodes Diversity Workbench User FUNCTION
AgentContactInformation_Public Diversity Workbench User FUNCTION
AgentHierarchy Diversity Workbench User FUNCTION
AgentHierarchyAllSuperior Diversity Workbench User FUNCTION
AgentNames Diversity Workbench User FUNCTION
AgentSuperiorList Diversity Workbench User FUNCTION
AgentSynonymTopID Diversity Workbench User FUNCTION
AgentSynonymy Diversity Workbench User FUNCTION
AgentSynonymyChildNodes Diversity Workbench User FUNCTION
AgentTopID Diversity Workbench User FUNCTION
BaseURL Diversity Workbench User FUNCTION
DefaultAgentNameDisplayType Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procInsertAgentCopy PROCEDURE
procSetVersionAgent PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchUser

Role DiversityWorkbenchUser

Role with read only access to the database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
AddressType_Enum TABLE
Agent TABLE
Agent_log TABLE
AgentContactInformation TABLE
AgentContactInformation_log TABLE
AgentDescriptor TABLE
AgentDescriptor_log TABLE
AgentDescriptorType_Enum TABLE
AgentExternalDatabase TABLE
AgentExternalDatabase_log TABLE
AgentExternalID TABLE
AgentExternalID_log TABLE
AgentGender_Enum TABLE
AgentHierarchyOther TABLE
AgentHierarchyOther_log TABLE
AgentIdentifier TABLE
AgentIdentifier_log TABLE
AgentIdentifierType_Enum TABLE
AgentImage TABLE
AgentImage_log TABLE
AgentImageType_Enum TABLE
AgentKeyword TABLE
AgentKeyword_log TABLE
AgentNameDisplayType_Enum TABLE
AgentProject TABLE
AgentProject_log TABLE
AgentReference TABLE
AgentReference_log TABLE
AgentRelation TABLE
AgentRelation_log TABLE
AgentRelationType_Enum TABLE
AgentSynonymisationType_Enum TABLE
AgentTitle_Enum TABLE
AgentType_Enum TABLE
LanguageCode_Enum TABLE
RevisionLevel_Enum TABLE
Agent_Core VIEW
AgentID_AvailableReadOnly VIEW
AgentID_FullAccess VIEW
AgentID_Locked VIEW
AgentID_ReadOnly VIEW
AgentID_UserAvailable VIEW
ProjectList VIEW
PublicAgent VIEW
PublicContactInformation VIEW
PublicIdentifier VIEW
PublicImage VIEW
PublicReference VIEW
PublicRelation VIEW
UserInfo VIEW
ViewAgentAddress VIEW
ViewAgentNames VIEW
ViewBaseURL VIEW
ViewDefaultAgentNameDisplayType VIEW
ViewDiversityWorkbenchModule VIEW
AgentAddress FUNCTION
AgentChildNodes FUNCTION
AgentContactInformation_Public FUNCTION
AgentHierarchy FUNCTION
AgentHierarchyAllSuperior FUNCTION
AgentNames FUNCTION
AgentSuperiorList FUNCTION
AgentSynonymTopID FUNCTION
AgentSynonymy FUNCTION
AgentSynonymyChildNodes FUNCTION
AgentTopID FUNCTION
BaseURL FUNCTION
DefaultAgentNameDisplayType FUNCTION
DefaultProjectID FUNCTION
DiversityWorkbenchModule FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
procInsertAgentCopy PROCEDURE
procSetVersionAgent PROCEDURE
SetUserProjects PROCEDURE
Oct 16, 2024

Diversity Agents

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table

Column Data type Description
Code nvarchar (50) A text code that uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
ParentCode nvarchar (50) The code of the superior entry, if a hierarchy within the entries is necessary
ParentRelation nvarchar (50) Relation to parent entry, e.g. part of
Description nvarchar (500) Description of enumerated object, displayed in the user interface
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayEnable bit Enumerated objects can be hidden from the user interface if this attribute is set to false (= unchecked check box)
URL varchar (500) A link to further information about the enumerated object
InternalNotes nvarchar (500) Internal development notes about usage, definition, etc. of an enumerated object
Icon image A symbol representing this entry in the user interface
ModuleName varchar (50) If the enumerated entry is related to a DiversityWorkbench module or a related webservice, the name of the DiversityWorkbench module, e.g. DiversityAgents
RowGUID uniqueidentifier -Default value: newsequentialid()

Table AddressType_Enum

Lookup table for the types of the addresses

Dependent tables:

  • AgentContactInformation

Content

Code Description
office office address
private private address

Table AgentDescriptorType_Enum

The type of the Descriptors

Dependent tables:

  • AgentDescriptor

Table AgentGender_Enum

Gender of the agent: female or male

Dependent tables:

  • Agent

Content

Code Description
female
male

Table AgentIdentifierType_Enum

Types of the agent identifier, e.g. ISNI

Dependent tables:

  • AgentIdentifier

Content

Code Description
ISNI International Standard Name Identifier (ISO 27729)
ORCID Open Researcher Contributor Identification
ROR Research Organization Registry

Table AgentImageType_Enum

Types of images in table AgentImage, e.g. Logo

Dependent tables:

  • AgentImage

Content

Code Description
Logo Logo
Portrait Portrait

Table AgentNameDisplayType_Enum

Display types of the names of the agents, defining e.g. the position of title, given and inherited part of the name and their abbreviation

Dependent tables:

  • ProjectProxy

Content

Code Description
Abbr The international defined standard arbbreviation; e.g. L. for Linne
G. Ii Given name. Inherited name; e.g. H. Hertel
Gg Ii Given name InheritedName; e.g. Hannes Hertel
Ii, G. Inherited name, GivenName; e.g. Hertel, H.
Ii, Gg Inherited name, GivenName; e.g. Hertel, Hannes
Tt. G. Ii Titel Given name. Inherited name; e.g. Prof. H. Hertel
Tt. Gg Ii Titel Given name Inherited name; e.g. Prof. Hannes Hertel

Table AgentRelationType_Enum

Relation types of agents, e.g. Child of

Dependent tables:

  • AgentRelation

Content

Code Description
Child of
Married to
Parent of

Table AgentSynonymisationType_Enum

Synonymisation types of agents, e.g. synonym to

Dependent tables:

  • Agent

Content

Code Description
replaced with if the agent was replaced by another entry
synonym to if the agent is synonym to another agent

Table AgentTitle_Enum

Lookup table for the titles of the agents

Dependent tables:

  • Agent

Content

Code Description
Dr.
Frater
Pater
Prof.
Prof. Dr.

Table AgentType_Enum

Lookup table for the types of the agents

Dependent tables:

  • Agent

Content

Code Description
Collection
Company
Department
Group
Institution
Person
University

Table LanguageCode_Enum

The codes for the languages

Dependent tables:

  • Agent

Content

Code Description
af Afrikaans
ar Arabisch
az Aserbaidschanisch
be Belarussisch
bg Bulgarisch
ca Katalanisch
cs Tschechisch
da Dänisch
de Deutsch
el Griechisch
en Englisch
es Spanisch
et Estnisch
eu Baskisch
fa Farsi
fi Finnisch
fo Färingisch
fr Französisch
gl Galizisch
gu Gujarati
he Hebräisch
hi Hindi
hr Kroatisch
hu Ungarisch
hy Armenisch
id Indonesisch
is Isländisch
it Italienisch
ja Japanisch
ka Georgisch
kk Kasachisch
kn Kannada
ko Koreanisch
ky Kirgisisch
lt Litauisch
lv Lettisch
mk Mazedonisch
mn Mongolisch
mr Marathi
ms Malaiisch
nl Niederländisch
no Norwegisch
pa Punjabi
pl Polnisch
pt Portugiesisch
ro Rumänisch
ru Russisch
sa Sanskrit
sk Slowakisch
sl Slowenisch
sq Albanisch
sv Schwedisch
sw Swahili
ta Tamil
te Telugu
th Thai
tr Türkisch
tt Tatarisch
uk Ukrainisch
ur Urdu
uz Usbekisch
vi Vietnamesisch
zh Chinesisch

Table RevisionLevel_Enum

Lookup table for the revision level

Dependent tables:

  • Agent

Content

Code Description
checked checked
final revision final revision
review required review required
to be deleted to be deleted
unchecked unchecked
Jun 28, 2024

History

To inspect the history of a dataset click on the button. A form will open, showing all former states of the data in the tables with the current dataset at the top. The version is shown in the header of the main.

The version will be set automatically. If a dataset is changed the version will be increased if the last changes where done by a different user or the last change is more than 24 hours ago (for further details see topic Logging ).

For analysis of the succession of changes the log tables contain additional columns:

  • Kind of change: This column is set by the trigger inserting data into the log table
    • current version: This is the current state of the data in the table
    • UPDATE: This is the state of the data before an update happened
    • DELETE: This is the state of the data when the data have been deleted
  • Date of change: The date and time of the changes. This column has the default value getdate() that means the current date an time is set when any data are inserted into the log table
  • Responsible: The user reponsible for the changes. This column has the default value suser_sname() that means the current user is set when any data are inserted into the log table
  • LogID: A unique ID of the logtable. This column is an identity that means it is set by the database when any data are inserted into the log table
Mar 26, 2024

Logging

Changes within the database will be documented for each dataset with the time and the responsible user in the columns shown in the image below.

All main tables have a corresponding logging table. If you change or delete a dataset the orignial dataset will be stored in this logging table together with informations about who has done the changes and when it happend. To see the data stored in the logging tables, click on the button to open the history of a dataset.

Mar 26, 2024

Login administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the timespan (From - To) and the number of data sets where any activity of the current login has been found.

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

 

Creation of login

To create a new login click on the button. A window will open as shown below.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has no access will be listed in gray while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

 

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below).

There are 4 states of accessibility for projects

  •     Full access: The user can edit the data
  •      Read only access: The user can only read the data
  •      Locked: The project is locked. Nobody can change the data
  •     No access: The user has no access via a project

Projects are related to the module DiversityProjects. To get additional information about a project select it in the the list and click on the button. 

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

 

 

Overview for a login

If you see an overview of all permissions and project for a login, click on the button. A window a shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user and roles in the database. 

To remove a user, select it in the list and click on the button. 

 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates, that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

Mar 26, 2024

Diversity Agents

Linked server

Databases not available on the local server may be accessible via a linked server. Provided the option for loading the connections is set, the program will automatically try to connect to these databases. Otherwise you can connect to these databases as described in chapter ModuleConnections. To administrate the linked servers, choose Administration - Linked servers ... from the menu. A form (see below) will open where you can add linked servers and inspect the content of the available databases.

Use the  resp. buttons to add or remove a linked server. To add a linked server, you need the name of the server and the port, e.g. tnt.diversityworkbench.de, 5432, the login associated with the connection of the linked server e.g. TNT and the password for this login. The available databases will be listed as shown above. To inspect the content, select among the tables or views listed in the right part as shown above. Linked servers have certain restrictions for the availability of data, e.g. XML and geography data are not available via a linked server. For a table or view containing incompatible content you may encounter a corresponding error mentioning the reason for the incompatibility.

An expample for a linked server as provided for central databases is shown below (using the management studio for SQL-Server) Linked servers

Jul 30, 2024

Diversity Agents

Tools

These are the tools to handle the basic parts of the database. These tools are only available for the owner of the database and should be handled with care as any changes in the database may disable the connection of your client to the database. Before changing any parts of the database it is recommended to backup the current state of the database. To use these tools, choose Administation → Database → Database tools ... from the menu. A window will open as shown below.

Description

The Description section (see above) shows the basic definitions of the objects in the database and enables you to enter a description for these objects including tables and their columns, functions and their parameter etc. With the buttons SQL for adding, update and both you can generate SQL statements for the creation of the descriptions in your database. Use the button both if you are not sure if a description is already present as it will generate a SQL statement working with existing and missing descriptions (see below).

The button  Fill Cache  fills the table CacheDescription where all descriptions are collected for easy access.

 

Log table and trigger

In the Log table and trigger section (see below) click on the List tables button to see all tables within the database. The Table section shows the basic definitions of a selected table. If columns for logging the date and responsible user for inserting and updating the data are missing, you can use the Attach ... button to attach these columns to the table. Furthermore you may add a RowGUID to the table as e.g. a preparation for a replication.

In the Log table section (see below) you can create a logging table for the selected table in a format as used within the Diversity Workbench. Click on the Show SQL ... button to show the SQL-statement that will create the logging table. If an old logging table should be kept, choose the Keep old log table option. If your table should support the version setting from a main table, choose the Add the column LogVersion option. To finally create the logging table click on the Create LogTable ... button.

The triggers for insert, update and delete are created in the according sections (see below). If an old trigger exists, its definition will be shown in the upper part of the window. Click on the Show SQL button to see the definition of the trigger according to the current definition of the table in a format as used in the Diversity Workbench. If a trigger should set the version in a main table, which the current table is related to, choose the Add version setting to trigger option. To enable this option you must select the version table first. To finally create the trigger click on the Create trigger button. The update and delete triggers will transfer the original version of the data into the logging tables as defined above, where you can inspect the history of the data sets.

If so far no procedure for setting the version in a main table is defined, you can create this procedure in the last section. Click on the Show SQL button to see the definition and on the Create Procedure button to create the procedure (see below).

 

Preparation for replication

If you want to use replication within you module, the tables need certain columns and a log table. These preparations can be performed by a script, generated in the section Replication (see below). Select the tables you want to include in the process and create the script. This script can than be included in an update of the database. Please ensure that these changes are only be done by expert staff.

 

Clear logtables

If for any reason you want to clear the log tables of the database, this can be done in the Clear log tab as shown below. Click on the List tables button to list the log tables. Then select those that should be cleared and click on the Clear log of selected tables button (see below). Please keep in mind that any restoration of data from the log is only possible as long as the data can be retrieved from the log.

 

Data protection

To implement the General Data Protection Regulation of the European Union several steps have to be performed in a database:

  • Generate a skript using this tool (see below) to convert all tables and insert objects according to the requirements:
    • Add columns ID, PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Grant update to PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Create update trigger for UserProxy setting the PrivacyConsentDate
    • Create the function providing the ID of the user from UserProxy
    • Create the function providing the name of the user from UserProxy
    • Create the function PrivacyConsentInfo providing common information
    • For every table:
      • Insert users from a table into UserProxy (if missing so far)
      • Insert users from the corresponding log table into UserProxy (if missing so far)
      • Change the constraints for the logging columns (User_Name() → UserID())
      • Replace user name with ID in logging columns
      • Replace user name with ID in logging columns of the log table
      • Adapt description of the logging columns
  • Include the skript in an update of the database
  • Check the database for update triggers, functions using e.g. CURRENT_USER, USER_NAME, SUSER_SNAME etc. where user names must be replaced with their IDs. Create a script performing these tasks and include it into an update for the database
  • Adapt the client to the now changed informations (e.g. query for responsible etc.)

After these changes the only place where the name of a user is stored is the table UserProxy together with the ID. Removing the name (see below) will remove any information about the user leaving only a number linked to the information within depending data.

To generate a script for the objects and changes needed to implement the General Data Protection Regulation use the Data protection tab as shown below. The generated script will handle the standard objects (logging columns) but not any additional circumstances within the database. For these you need to inspect the database in detail and create a script to handle them on your own.

To set the website where detailed information about the handling of the General Data Protection Regulation within the DiversityWorkbench resp. the current database is provided, click on the button on the Info site tab. If unchanged, the default site for the DiversityWorkbench is set (see below).

If for any reason a user wants his name to be removed from the database, select the users name from the list as shown below and click on the  button (see below).

May 16, 2024

Diversity Agents

No-SQL Interface

JSON Cache

Databases of the modules provid a No-SQL interface where the data of the main table and the depending tables are merged as JSON.

Table JsonCache

Content of table JsonCache restricted to public available data

Column Data type Description Nullable Relation
ID int Unique ID for the Dataset, Primary key NO ID of the source
URI varchar (500) The URL as combination of BaseURL and ID NO BaseURL and ID of the source
DisplayText nvarchar (500) Representation in the interface NO Main table of the source
LogUpdatedWhen datetime Date and time when the data were last updated NO -
Data json Data related to the current dataset NO -

procFillJsonCache is started by an update trigger trgUpd… of the main table in the database

Interface in clients

All modules provide data via a cache table. In the header of the clients you can inspect the content of the JsonCache with a click on the button. For modules with a difference between local and public data, you can inspect the content of the public data with a click of the right mouse button.

Update

Apart of the update via the Trigger (see below) you can update the JsonCache via the update button underneath the button.

To update the JsonCache for the whole database select Administration - JsonCache… from the menu. a window as shown below will open where you can update the JsonCache for single datasets or the whole database.

Summary

graph TD;
    TaxonName[Main table in database] 
    trgUpdTaxonName[trgUpd.. of main table in database]
    TaxonName --> |Update in table| trgUpdTaxonName
    proc[Procedure procFillJsonCache setting the content in table JsonCache]
    trgUpdTaxonName --> proc
graph TD;    
    Mainform[Main form]
    ButtonShow[Button show JsonCache of current dataset]
    Mainform --> ButtonShow
    Left[Show Data]
    ButtonShow --> |Left click| Left
graph TD;    
    Mainform[Main form]
    Admin[Administration menu]
    Mainform --> Admin
    Cache[JsonCache...]
    Admin --> Cache
    Adminform[Administration form]
    Cache --> Adminform
    AdminUpdateSingle[Update single dataset]
    Adminform --> AdminUpdateSingle
    AdminUpdateDB[Update for whole database] 
    Adminform --> AdminUpdateDB
Jul 16, 2024

Diversity Agents

Documentation

Tools for the database documentation

These are the tools to describe the parts of the database and create documentations of the structure. To use these tools, choose Administation - Database - Documentation… from the menu. A window will open as shown below.

Click on the List objects button to list the objects of the database. With the  button resp. button you can select resp. deselect the types in the type selection and the object in the list.

Select the objects that should be listed all button resp. none button you can select resp. deselect the types in the type selection and the object in the list.

Select the objects that should be included in the documentation:

  • Tables
    • Trigger
  • Views
  • Roles
  • Functions and procedures
  • Context

… and exclude the objects that should not be included in the documentation:

  • Logging tables
  • Enumeration tables
  • Old versions of objects
  • System objects
  • Deprecated objects

 

The button Set default seletion will select all items in the list without:

  • System objects
  • Older version of an object indicated by the number at the last position
  • Logging tables
  • Enumeration tables
  • Objects with a description starting with e.g. outdated, deprecated, obsolete etc.
  • HTML options:
    • include index for objects
    • include NULL / NOT NULL
    • include relations and dependencies
    • include Description
    • exclude standard trigger
    • exclude definition
    • include permissions for *_Enum etc.
    • exclude obsolete columns
    • exclude columns starting or ending with the given strings
    • include list of tables that are depending on a table

The buttons Add to seletion and  Remove from seletion  will use the given strings with * as wildcard to add resp. remove items from the selection.

With the Context  option you can show or hide the context area for the html and media wiki tab as shown above.

HTML, MediaWiki, JSP-Wiki

To create a documentation choose among the provided options and click on the button Create ... documentation to create the documentation in one of the available formats (HTML, MediaWiki, JSP-Wiki). 

Oct 18, 2024

Subsections of Documentation

Diversity Agents

Documentation

chm

With the chm tab you can generate index and keyword html files as well as markdown files for a website generated out of the hhc and hhk files of the HTML Help Workshop for the creation of chm manual as described in the video .

The button Generate keywords for HUGO creates a text file keywords.txt containing the keywords needed for the HUGO manual in a simple format. A pre- or postfix is set for every module to avoid conflicts. Use the Open button to open the file in a text editor.

Oct 19, 2024

Diversity Agents

Documentation

HUGO

In the HUGO / HTML tab you generate markdown files according to HUGO and the relearn theme.

The conversion and adaptions are explained in a short tutorial: Video starten

For enumeration tables the content can be exported as explained in a short tutorial: Video starten

In the tab you can fix links in markdown files according to HUGO shortcodes.

The fixes for broken links are explained in a short tutorial: Video starten

The adaptions for links for HUGO as related references are explained in a short tutorial: Video starten

To map the files in the original links to new files in the documentation follow the steps shown in a short tutorial: Video starten

Installation of HUGO

Update des Themes

um das Theme auf die letzte Version zu bringen kann man den Befehl git submodule update --remote --merge themes/relearn verwenden

Übersetzung des Bestands an html

  • Übersetzung der *.html Seiten mit pandoc in *.md
  • Aufbau einer Ordnerstruktur die dem Index der chm Datei entspricht
  • Das Basisdokument der Ordner wird in die Ordner verschoben und in _index.md umbenannt
    • Dort im Frontmatter steht der Titel der im Menü angezeigt wird, e.g.:
      --- 
      title: Installation 
      ---  

Überarbeitung der md Dateien

  • Korrektur der Bildverweise
    • Ordner mit den Bildern in den Ordner static kopieren
    • von e.g. ![](img/...) in ![](img/...)
    • ACHTUNG - Case sensitiv. Namen müssen stimmen
    • Icons gegebenenfalls freistellen für Darkmode
  • Entfernung aller störenden Formatierungsangaben
  • Entfernung der Kopfzeile (Überschrift wird von HUGO automatisch erzeugt)
  • Korrektur der internen Verweise
    • ändern von [![](img/VideoDE.svg?class=inlineimg)](http://media.snsb.info/Tutorials/dwb/Editing/OeffentlicheKontaktdaten.webm) zu [![Video starten](img/VideoDE.svg?class=inlineimg)](http://media.snsb.info/Tutorials/dwb/Editing/OeffentlicheKontaktdaten.webm)
      • ansonsten wird das Bild gezeigt statt das Video zu starten
    • ändern von
      [Contact](Contact.htm)
      zu e.g.
      [Contact](editingdata/contact)
    • Wenn als Basisadresse in hugo.toml etwas angegeben wurde, e.g. baseURL = "http://www.diversityworkbench.de" dann muss diese auch für Verweise innerhalb der Files verwendet werden.
      • e.g. Bildverweise ![](img/IcoFeedback.gif?class=inlineimg)
      • Dateiverweise [Anmelden](database)
      • HUGO relearn erzeugt für Überschriften Anker die man ansteuern kann, e.g. kann man ### Table **AgentResource** über die Adresse database/database/#table-agentresource erreichen. Ein Index Eintrag dafür wäre e.g. [AgentResource](database/database/#table-agentresource). ACHTUNG - Case sensitiv: ### Table **AgentResource** wird in #table-agentresource übersetzt
    • Kommentare starten mit # ohne folgendes Leerzeichen

Frontmatter

You can change the frontmatter to a default using the documentation tool

  • Steht am Anfang der Datei und ist bei yaml durch --- oben und unten abgegrenzt, e.g.
    ---
    title: Login administration
    linktitle: Logins
    weight: 5
    menuPre: img/Documentation.svg
    alwaysopen: false
    ---
  • Seiten die noch in Entwicklung sind kann man mit draft: true im Frontmatter markieren. Diese werden dann nicht in die Ausgabe übernommen
  • Der Titel wird mit title: Login administration angegeben. Dieser erscheint dann auch in der Seite als Überschrift
  • Der Text im Menü kann abweichend definiert werden mit linktitle: Logins. Ansonsten erscheit der Titel im Menü
  • Die Reihenfolge im Menü kann mit weight: 5 angegeben werden. Ansonsten wird alphabetisch sortiert
  • Ein Logo kann man mit `menuPre: img/LinkedServer.svg
  • Wenn das Untermenue erst beim Anwählen geöffnet werden soll: alwaysopen: false

Template files

Starting with a Dash: If the first line of your Markdown file starts with a dash (-), Hugo might misinterpret it as a YAML delimiter, leading to an error

Bilder

You can adapt the images to a default using the documentation tool

  • Icons die e.g. in den Text integriert werden sollen, müssen folgedermassen eingebaut werden:
    • ![](img/Database.svg?class=inlineimg)
  • Die Bilder am Anfang der Seite werde wie folgt eingebaut:
    • ![](img/LinkedServer.svg?class=headerimg)

mit px wird das Bild mitgezoomt, bei vw bleibt es gleich gross

  • noch nicht zu svg konvertierte Bilder die im Fliesstest erscheinen sollen werden wie folgt eingebunden:
    • ![](img/Delete.svg?class=inlineimg)
  • sonstige Bilder mit
    • ![](img/Delete.svg)

mit der Angabe ...lightbox=false wird verhindert, dass ein Bild beim Anklicken mit der Maus geöffnet wird. Dies sollte bei Bildern die nicht nach svg konvertiert wurden und nicht im Fliesstext erscheinen nicht verwendet werden, damit der User bei kleinen Bildern diese in Originalauflösung betrachten kann. Unten 2 Beispiele

![](img/Delete.svg?class=inlineimg)

![](img/Delete.svg?class=inlineimg)

Für Bilder die aus der Quelle fontawesome kommen kann man hier suchen: fontawesome. Es funktionieren nicht alle die dort bereitstehen. Daher bitte testen!

Für Links innerhalb des Manuals kann man shortcodes verwenden. Dafür entweder auf den Namen der Datei oder auf Links von Überschriften (ab ##) verwenden. Diese müssen innerhalb des Manuals eindeutig sein. Für Header als erstes Zeichen # dann Überschrift und alles lower case und Leerzeichen werden durch - ersetzt. Beispiel:

## Main form of diversityexsiccatae

wird zu sofern es sich in der gleichen Datei befindet: 2 x { und % relref "#main-form-of-diversityexsiccatae" % und 2 x }

Für Links ausserhalb der Datei werden Verweise unter Einschluss des Dateinamens verwendet:

Verweis auf ein Kapitel innerhalb einer Datei 2 x { und % relref "diversityexsiccatae#main-form-of-diversityexsiccatae" % und 2 x }

bzw. nur auf die Datei 2 x { und % relref "diversityexsiccatae" % und 2 x }

Leerzeichen zwischen 2 x { und % und % und 2 x } entfernen

Von ausserhalb kann e.g. eine Überschrift mit https://www.diversityworkbench.demodules/diversityexsiccatae/index.html#main-form-of-diversityexsiccatae aufgerufen werden. Diese können direkt aus dem Manual kopiert werden.

  • hierfür das Logo in den Ordner static kopieren
  • im Ordner layouts einen Ordner partials anlegen
  • dort eine Datei logo.html anlegen
    • in dieser auf das Logo verweisen e.g.:
      <h4><b>DiversityAgents</b></h4>
      <img src="/DA_4D.svg">
  • in static - layouts - partials die Datei menu-footer.html anlegen und anpassen

favicon

Im Ordner static den Ordner images anlegen Datei favicon.ico in der Ordner static/images kopieren

Einschliessen von Dateien

Das Verzeichnis templates enthält Dateien die in andere Dateien über eine shortcode eingeschlossen werden können, e.g.:  2 x { und % include file="templates/template_workbench.md" % und 2 x } Diese Dateien dürfen kein frontmatter enthalten. Shortcodes müssen überprüft werden, da diese in der Regel nicht ausgewertet werden.

ER-Diagramm

dieses kann als Mermaid eingebaut werden, e.g.

 
graph LR;
    A[Agent] --> B[AgentContact<br/>Kontaktdaten der Agents]
    A --> C[AgentReference]
    A --> D[AgentIdentifier]
    A --> E[AgentResource]
    A --> F[AgentExternalID]
    G[AgentExternalDatabase] --> F[AgentExternalID]

soll das Diagramm zoombar sein wird die Version 5.23 des Themes benoetigt. Ausserdem kann der Parameter nur für die Shortcode Version angegeben werden, nicht für die Codefences:

2 x { und % mermaid align="center" zoom="true" % und 2 x }
... 
(remove space between 2 x { und  and < resp > and  und 2 x } in header and footer for correct code)
...
2 x { und % /mermaid % und 2 x }

Anpassung des Themes

  • es werden 2 eigene Themes bereitgestellt

    • im Verzeichnes
      • themes
        • relearn
          • static
            • css:
            • theme-dwb-dark.css
            • theme-dwb.css

    diese an DWB Anforderungen anpassen

    • in \themes\relearn\static\css\theme.css
      #body img.inline {
          display: inline !important;
          margin: 0 !important;
          vertical-align: middle;
          /* vertical-align: bottom; */
      }
    • in \themes\relearn\static\css\theme-dwb.css
      /*--MENU-HEADER-BG-color: rgba( 28, 144, 243, 1 );*/ /* Background color of menu header */
      --MENU-HEADER-BG-color: rgba( 220, 220, 220, 1 ); /* Background color of menu header */
      --MENU-HEADER-BORDER-color: rgba( 51, 161, 255, 1 ); /*Color of menu header border */
      

      –MENU-SEARCH-color: rgba( 255, 255, 255, 1 ); /* Color of search field text / /–MENU-SEARCH-BG-color: rgba( 22, 122, 208, 1 );/ / Search field background color (by default borders + icons) / –MENU-SEARCH-BG-color: rgba( 90, 90, 90, 1 ); / Search field background color (by default borders + icons) / /–MENU-SEARCH-BORDER-color: rgba( 51, 161, 255, 1 );/ / Override search field border color / –MENU-SEARCH-BORDER-color: rgba( 0, 0, 0, 1 ); / Override search field border color */

Konfiguration - in hugo.toml:

```native
baseURL = "http://www.diversityworkbench.de"
languageCode = "en-us"
title = "DiversityAgents"
theme = "relearn"

[outputs] home = ["HTML", "RSS", "SEARCH", "SEARCHPAGE"] section = ["HTML", "RSS", "PRINT"] page = ["HTML", "RSS", "PRINT"]

[params] themeVariant = [ "auto", "dwb", "dwb-dark" ]

</code></pre>
<h2 id="start-des-testservers">Start des Testservers:</h2>
<ul>
<li>mit einem Terminal in das Verzeichnis des Projekts wechseln</li>
<li>dort <code>hugo server </code> eingeben.</li>
<li>bei Problem mit Sonderzeichen: den Inhalt der Datei config.toml in hugo.toml kopieren und config.toml löschen (beide sollten wenn vorhanden UTF8 sein - werden manchmal als UTF16 angelegt - dieses dann nach UTF8 ändern)
<ul>
<li>Error: &ldquo;&hellip;\diversityworkbench\hugo.toml:1:1&rdquo;: unmarshal failed: toml: invalid character at start of key: ÿ</li>
</ul>
</li>
<li>Im Browser an die angegebene Adresse navigieren, e.g. <code>localhost:1313</code></li>
<li>Wenn als Basisadresse in hugo.toml etwas angegeben wurde, e.g. <code>baseURL = &quot;http://www.diversityworkbench.de&quot;</code> dann muss die passende Adresse eingeben werden also e.g. <code>localhost:1313</code></li>
</ul>
Oct 19, 2024

Diversity Agents

Documentation

MediaWiki

With the MediaWiki tab you can generate markdown files according to MediaWiki.

Oct 19, 2024

Diversity Agents

Update

Update of database and client

If either the database or the client needs to be updated, the menu will show an additional entry: Update.

Database update

To update the database, choose Update Update database … from the menu. See chapter Database update for details.

Client update

To update the client, choose Update Update client … and download the lastest version of the client. ee chapter Update client for details.

Jul 30, 2024

Subsections of Update

Diversity Agents

Update

Client software

Replace the files and folders of your installation of DiversityCollection with the files you received by e-mail or downloaded from the DiversityWorkbench portal. The database will not be influenced by this replacement. After starting the new software you need to transfer the settings of the previous version. When you start the program and connect to a database, the program will check if it is compatible with the database or if the database needs an update. In any of these cases an update entry in the menu will appear. If a new version of the client is available, this menu will contain an update client … entry. Click on it to open the webpage where you may download the client as shown below.

 

Jul 30, 2024

Diversity Agents

Update

Database

Update database to current version

If you are the owner of the database (Database role = dbo) and the database needs to be updated, the menu will contain an update database … entry. Select this entry to open a window as shown below to run the provided update scripts, delivered with the client software. These scripts need to run consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either have to run the script DiversityCollectionUpdate_020501_To_020504 or the scripts DiversityCollectionUpdate_020501_To_020502, DiversityCollectionUpdate_020502_To_020503 and DiversityCollectionUpdate_020503_To_020504. The program will guide you through these steps and check for the scripts. All you need to do is click the Start update button. 

Update of all databases on a server

If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:

DiversityCollection.exe UpdateDatabase 127.0.0.1 5432

The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.

Jul 30, 2024

Diversity Agents

Errorlog

If any error messages show up while working with the application, you can find further details concerning the part of the application where the error occurred and the parameters involved in the file e.g. DiversityCollectionError.log in the Module DiversityCollection located in your resources directory.

To open the errorlog, choose Help - ErrorLog from the menu. A window will open showing the content of the errolog. By default the errorlog will be reset at program start. You can keep the errorlog if needed by chossing Help - Errorlog - Keep error log from the menu. A button will appear that allows you to clear the error log manually: Help - Clear ErrorLog.

Jul 30, 2024

Diversity Agents

Module connections

Connections between the modules of the Diversity Workbench

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. DiversityAgents is referred by several modules. To scan for references from these modules on data in DiversityAgents choose Data - Scan modules - from the menu (see image below).

With these options the program will scan all sources of the selected module as listed in the connections for references to the current agent. After selecting an agent in the tree, the sources of the selected modules together with the linked data will be listed as shown below.

Select a link to see a summary of the linked data (see below).

To get further information about an item click on the button. If so far the path to the respective application has not been set, you will get a corresponding message (see below).

Click on the button to set the path to the application (see below).

By default the path to the application is C:\Program Files (x86)\DiversityWorkbench\Diversity...\Diversity.…exe as shown.

Jul 30, 2024

Diversity Agents

Resources

The resources directory is set via the menu (Administration - Resources).

There are 3 possibilities for the resources directory:

  • Select any directory you have read/write access (User defined)
  • Select the "Home" directory of the user
  • Select the "My Documents" directory of the user

The default is set to Home. This directory will contain all files the user needs access to (see image below as an example for the module DiversityAgents).

Certain directories are hidden (Query) and are handled by the software i.e. the content should not be changed by the user. The other folders are generated by the software if missing, e.g. Export for any exports (see below).

Optional copy

By default all files the software needs from the application directory will be copied into the selected resources directory of the user. You can change this behaviour to one of the options listed below:

  • Copy files at program start
  • Add missing files at program start
  • Do not copy

With the next start of the program the software will act according to the selected behaviour. If you change from the Do not copy option to one of the other options the software will act at once according to the new option and e.g. copy missing directories and files into the user directory.

Jan 3, 2025

Diversity Agents

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024

Diversity Collection

Scope of DiversityCollection within the Diversity Workbench

DiversityCollection is part of the database framework DiversityWorkbench. Within this framework, the application DiversityCollection is confined to the management of specimens in scientific collections. In this context, it is designed to document any action concerning the collection, storage, exchange, and treatment of specimens in a collection and is also appropriate for storing observation data. DiversityCollection is distinguished from other collection management systems by focusing on the biological relationships between organisms collected together as one or more specimens (e.g. host, parasite and hyperparasite, symbionts, etc.). Each module within the Diversity Workbench is focused on a specific data domain. DiversityCollection stores only data connected with the handling of collection specimens and observations. Data from other realms, such as taxonomy, are handled in separate modules. For an overview of the available modules, see the image below. DiversityCollection can also be used as a stand-alone application.   

Outline

The central entity in DiversityCollection is the Specimen. It represents the observed or collected ’thing’, which may be, for example, a plant, an animal, a fossil, or a mineral. The gathering of a specimen takes place in an event. For each specimen, detailed descriptions of place can be recorded. For most specimens, only a part. The specimen is or contains one or more objects that are organisms, minerals, etc. and are called units or organisms in DiversityCollection. Taxonomic identification is based on the unit level. A unit can stretch over several parts, and a part can contain several units.

Data management sectors of the application

Sector Description
Series An expedition, monitoring or similar that involves the collection event or observations at single spots
Event The location of an observation or the spot where a specimen was collected during, for example, an expedition
Localisation Localisation of an observation or collection site
Site Property Properties of e.g. a collection site like the type of the habitat
Collecting Method Methods used for the observation or collection of specimen
Specimen Observed or collected specimen like those collected during a collection event
Collector The observers or collectors of specimen
Objects The objects like taxa or minerals observed or collected
Identification Identifications of the organisms, minerals etc.
Analysis Any analysis applied to characterise the objects
Analysis methods The methods that have been used to analyse the objects
Part The parts of a collected specimen that are stored in a collection, e.g. as herbarium sheets
Collection The collection where the collected objects are stored
Processing Processing applied to the parts of a specimen
Processing methods Methods that have been used for the processing
Transaction Actions like sending specimen as a loan to another collection
Project The projects that a specimen is a part of
Images Can be taken for the EventSeries, the CollectionEvent, the CollectionSpecimen as well as organisms and parts of a specimen
References The references related to a specimen, organism, identification or part of a specimen

Usage example

The image below gives an overview of some typical data represented in DiversityCollection, along with the symbols used throughout the program. In this example, a herbarium sheet containing a plant collected during an expedition is identified and analysed. The herbarium sheet is loaned to another collection where a DNA sample is extracted. All this information about the specimen, its storage, treatment, and derived information is stored in DiversityCollection:

  • A typical specimen may have been collected at a CollectionEvent during an expedition. . The site of the CollectionEvent can be localised and characterised and methods have been used. The collectors collected twigs of the plant and fungi growing on the plants.
  • The organisms on the specimen were identified several times and analysed where methods have been used.
  • The collected samples are stored as herbarium sheets and specimens in a collection. .
  • The manager sent some of the samples for which he had a request from a requester to another collection.
  • The samples were collected as part of a project .
  • Certain parts were cultivated and DNA extracted which was processed where methods have been used.
  • Images were taken for the EventSeries, the CollectionEvent, the CollectionSpecimen as well as organisms and parts of this specimen.

 

Main sectors

The image below gives you a simplified overview of the main parts of the DiversityCollection database.

For details in various sections see the overviews

DiversityCollection 4.x is based on Microsoft SQL-Server 2016 or later and the .Net Framework, Version 4.8.

For licence and copyright see the licence section.

Glossary

Apr 8, 2025

Subsections of Collection

Diversity Collection

Download

Current version

4.4.17 (2025-04-17)

Download

  • Transaction hierarchy: Fixed missing display of the transaction hierarchy.

4.4.16 (2025-04-14)

svn revision 6500 (DC), 6475 (DWB)

Version 4.4.16 no longer available - Please download the new current version

  • New material category core sample

  • Labelprinting: Fixed a problem when creating labels with author names starting with ‘de’.

  • GridView: Fix of an incorrect validation error when SpecimenID is contained in the display fields

  • Identification: Fix for the Issue “DC hangs after entering an identification and then switching to another field”

  • Deleting datasets: Fix for Issue “Menu entries/buttons are partially disabled after new data record is deleted”

  • CacheDB

    • ExecuteSqlSkalarInCacheDB - extention with optional check if data are present to avoid exception
      • several calls of ExecuteSqlSkalarInCacheDB including check
    • UserControlLookupSource
      • SubsetTable.TaxonCommonName
        • including columuns ReferenceTitle, LogUpdatedWhen
        • Version set to 3
      • SubsetTable.ScientificTerm: ExternalID added
        • Version set to 3
      • CompareLogDatePostgres - Check if any data exist
    • FormCacheDatabase
      • CreateSourceView: Check if source exists excluding procedures
      • UserControlLookupSource.SubsetTable.procTaxonNameHierarchy: SQL corrected
      • initDiagnostics: Test if anything is present
      • ScientificTerms: Fixed message
      • initTarget: Check existence
  • Datasets:

    • DatasetCollectionSpecimen: Column Problems in table CollectionSpecimen changed to nvarchar Max

Database updates

DiversityCollectionUpdate_020649_to_020650
  • ISSUE #14
    • CollectionSpecimen: Change Problems to nvarchar(MAX)
    • FirstLines_4: Change Problems to nvarchar(MAX)
    • FirstLinesPart_2: Change Problems to nvarchar(MAX)
    • FirstLinesUnit_4: Change Problems to nvarchar(MAX)
DiversityCollectionUpdate_020648_to_020649
  • New material category core sample
  • Function CollectionChildNodes optimized
  • 2 new indices for table Collection solving timeout problems in FormCollection when retrieving the collection hierarchy
DiversityCollectionCacheUpdate_010031_to_010032
  • TaxonCommonName
    • Removing PK of Table TaxonCommonName
    • Add columns ReferenceTitle and LogUpdatedWhen with default ‘1900-01-01 00:00:00’ to table TaxonCommonName
    • Changing size of column CommonName to 220 and column BaseURL to 255
    • Adding new PK to table TaxonCommonName including LogUpdatedWhen
  • ScientificTerm: Add column ExternalID
DiversityCollectionCacheUpdatePG_000019_to_000020
  • TaxonCommonName
    • Removing PK of Table TaxonCommonName
    • Add columns ReferenceTitle and LogUpdatedWhen to table TaxonCommonName
    • Changing size of column CommonName to 220 and column BaseURL to 255
    • Adding new PK to table TaxonCommonName including LogUpdatedWhen
  • ScientificTerm: Add column ExternalID

Cachedatabase updates

Postgres packages
  • ABCD 11:
    • abcd__unit_gathering: Formatting of the “DateTime_ISODateTimeBegin” field, in ABCD - DateTimeISO format.
    • encode_uri(text) - for encoding uris from https://stackoverflow.com/a/60260190
    • Adaption of ABCD_Unit with encoded RecordURI and strict ISODAteTimeFormat
    • abcd__measurementorfact: MeasurementDateTime format to ISO8601
    • ABCD_RecordBasis_MaterialCategories new mapping

Upcoming version

8.0

Database updates

DiversityCollectionUpdate_020649_to_020650
  • New material category core sample
  • Function CollectionChildNodes optimized
  • 2 new indices for table Collection solving timeout problems in FormCollection when retrieving the collection hierarchy

Previous versions

4.4.15 (2024-10-11)

svn revision 6274 (DC), 6271(DWB)

Download

  • Bugfix for adding a regulation to a list of specimens via menu Data-Transfer-ToTransaction
  • CacheDatabase: Bugfixes - Database updates (Postgres packages)
    • ABCD 10: Bugfix: set publisher of main project in citation field (in function abcd___projectcitation - restrict publisher to main project)
    • ABCD_BayernFlora 5: ABCD__BayernFlora_: Bugfix for problems with unique index “ABCD_Unit_Associations_UnitAssociation_pkey”

4.4.14 (2024-09-04)

  • internal interim release. Please download and use version 4.4.15!

4.4.13 (2024-08-09)

svn revision 6203, 6204

Download

  • Default for timeout for loading resources from web (e.g. images) set to 1 sec: TimeoutWeb in DiversityWorkbench.WorkbenchSettings.settings - TimeoutWeb.
  • Transaction:
    • Several bugfixes copying transaction within hierarchy: HierarchicalEntity.toolStripButtonCopyHierarchy_Click Line 364
    • Inclusion of request.
  • Bugfix setting analysis control.
  • Bugfix grid view - timeout for database included.
  • Query
    • Adding missing analysis and descriptor icon in query.
    • Adding filter options for collection task
  • Bugfix creating new collectors - restricted to specimen.
  • Bugfix editing internal relations.
  • Bugfix inserting geography for unit - restricted to unit.
  • Bugfix selecting parts for an exhibition
  • Event property
    • Bugfix in setUserControlModuleRelatedEntrySourceProperty
  • Maintenance
    • Synchronizing - Agents - Missing connection - Similar names
      • Bugfix: Removal of surplus % signs in update query.
    • Bugfix: Searching for referenced data: DiversityCollection.Forms.ReferencedDataFind Line 22693
  • Inclusion of table editor in form for collection event.
  • Exhibition including option for printing
  • Cache database
    • Optimizing upload of sources: DiversityCollection.CacheDatabase.UserControlLookupSource.TransferToCache(ref string Report, InterfaceCacheDatabase InterfaceCacheDB) Line 1512, 1850, 1953
    • Optimized messages for transfer of sources to Postgres
  • Collection
    • Query including logcolumns
    • Collection: Transfer to parent location based on location hierarchy

Updates in DWB Libraries

  • Import wizard with optional translation of \r\n in data into line break
  • Optional copy behaviour at program start

Database updates

DiversityCollectionUpdate_020646_to_020647
  • FirstLines_4: Optimized Query for IdentificationUnit
  • Enabling requests in transaction
  • New function CollectionEventSeriesHierarchySuperior
  • trgInsCollectionEvent - Bugfix
DiversityCollectionUpdate_020647_to_020648
  • Granting delete and update for Annotation to editor
  • Disable triggers for update of related tables Annotation and ExternalIdentifier
  • UserCollectionList - Inclusion of missing columns

4.4.12 (2024-06-17)

Download

svn revision 6136

  • Statistics
    • Design bugfix showing images of project taxa
  • Bugfix in specimen grid
  • Inclusion of optional setting for charts for queries linked to modules
  • Bugfix for 4 dll’s taken from wrong source
  • Query for missing regulations
  • CacheDatabase
    • Bugfix in CacheDB.SetTransferActive: Check existence of data in SourceTable to avoid exception
    • Bugfix in UserControlLookupSource.ReportFile: Path for file corrected
  • IPM: Redesign of collection hierarchy
  • Setting of user defined service for QR-Code generation.
  • Bugfix in FormCollectionSpecimen.PreSelectTreeNodeTableSequence: Checking for missing columns
  • Label print
    • QR-Code
      • Bugfix - missing QR-codes implemented
      • Bugfix generating QR-code for stable identifier
      • Bugfix generating QR-code for external identifier
      • Restriction to part labels
      • Inclusion of size in context menu to enable changing the default size (= 500)

Updates in DWB Libraries

  • A bufix in the import wizard changes the behaviour related to the import of the table Organism in part. Please use insert instead of merge to perform the previous results

Database updates

DiversityCollectionUpdate_020645_to_020646
  • Collection
    • new type rack
    • Redesign of collection location
      • CollectionLocation depending on column LocationParentID
      • CollectionLocationAll depending on column LocationParentID
      • CollectionLocationChildNodes depending on column LocationParentID
      • CollectionLocationMulti depending on column LocationParentID
      • CollectionLocationSuperior depending on column LocationParentID
  • Grants for StableIdentifier and StableIdentifierBase in case they are missing
  • procInsertCollectionEventCopy - include tables for Method
  • Trigger handling deletion of data tables Annotation and ExternalIdentifier
    • CollectionEvent
    • CollectionSpecimen
    • IdentificationUnit
    • CollectionSpecimenPart
    • CollectionSpecimenReference
    • Transaction
  • FirstLines_4: Adaption of length of LableTitle in Table CollectionSpecimen

Updates in DWB Libraries

4.4.11 (2024-04-22)

Download

  • Transaction
    • Several bugfixes when creating transactions.
  • Label print
    • QR-Codes: Changing from deprecated google api to SNSB service.
  • Statistics
    • Additional table for taxon images
  • Datawithholding reason for specimen shown in label and tooltip

4.4.10 (2024-04-18)

Download

  • Redesign of IPM
  • Several bugfixes in Statistics and additional tab for taxon hierarchy

Updates in DWB Libraries

4.4.9 (2024-01-18)

Download

  • Bugfix Transaction showing administrative collections

  • Bugfixes in Im- & Export (see DiversityWorkbench 4.2.12)

  • Bugfix in prepareToolStripDropDownButtonsEventLocalisation in main form and lookup table DtLocalisationSystem to ensure correct init of drop down list

  • Bugfix maintenance when removing orphaned identifier and annotiations

4.4.8 (2023-12-18)

Download

  • Several bugfixes for AccessionNumbers containing ' sign
  • Bugfix in FormCollectionSpecimen.fillSpecimen: testing dataset existence
  • Export
    • Bavarikon:
      • Including qualifier
      • bav18 removed
      • bav20 adapted
  • Maintenance
    • Events - Coordinates - Check geography: Bugfix setting cache values
    • Synchronizing Taxa - Families, Orders: Adding options to restrict to empty colums and taxa
  • Transaction
    • Balance: Bugfix in case of missing value for administrative collection
    • Redesign of handling regulations:
      • Display of title in interface
      • Display of documents in interface depending on permissions
      • Testing type of transaction before insert
  • ImportWizard
    • Analysis selection showing hierarchy and AnalysisID
  • Form for handling collection events

Database updates

DiversityCollectionUpdate_020644_to_020645
  • CollectionEventSeriesHierarchy: Add DateSupplement
  • CollectionEventRegulation: Add column TransactionID
  • Setting the relation for column TransactionID
  • Setting the values for the new column TransactionID
  • trgDelCollectionEventRegulation
  • trgUpdCollectionEventRegulation
  • Regulations: Deprecated objects in database
  • Relation between CollectionTask and Transaction
  • CollectionID in table CollectionSpecimen deprecated
  • CollectionChildNodes - optimized
  • Setting the select permission on sql_expression_dependencies for the Editor to enable imports
  • EventSeriesChildNodes - Description and Notes to nvarchar(max)
  • EventSeriesHierarchy - Description and Notes to nvarchar(max)

4.4.7 (2023-09-05)

Download

  • Bugfix setting password

4.4.6 (2023-09-01)

Download

  • Statistics with progressbar and state information for project and error report.
  • Bugfix in enumeration administration
  • Setting the datawithholding reasons for the current project Video starten
  • Bugfix transaction showing dates

Database updates

DiversityCollectionUpdate_020643_to_020644
  • CollectionAgent - removing IX_CollectionAgentSequence to ensure database backup
  • CollectionChildNodes - Adding missing columns
Cache database - Schema
DiversityCollectionCacheUpdateSchema_000035_to_000036
  • procPublishCount - inclusion of new tables
  • CacheProjectReference - Add column IsCitation
  • procPublishProjectReference - JOIN with CacheMetadata
Postgres - Schema
DiversityCollectionCacheUpdatePGSchema_000025_to_000026
  • New table CacheProjectDescriptor - Bugfix

4.4.5 (2023-08-17)

Download

  • EventSeries
    • Descriptors for the event series Video starten
    • Date supplement included
  • Agents (collector, responsible for identification, …): Showing valid name retrieved from DiversityAgents Video starten
    • Customize: Option for display of valid agent name included
  • Bugfix setting database
  • Bugfix setting series title in tree
  • Bugfix setting menu permission

Database updates

02.06.43

  • CollectionEventSeries
    • CollEventSeriesDescriptorType_Enum - Enumeration for series descriptor types including triggers and logtable
    • CollectionEventSeriesDescriptor - Descriptors for event series, triggers and log table adapted
    • New column DateSupplement including adaption of log table and trigger
    • Adaptions for functions - add DateSupplement:
      • EventSeriesSuperiorList
      • EventSeriesHierarchy
      • EventSeriesChildNodes
  • CollectionAgent
    • trgInsCollectionAgent adapted to synchron insert
    • disable IX_CollectionAgentSequence if present to ensure insert

4.4.4 (2023-07-25)

  • Cache database

    • Package Floraraster: Bugfix in script for functions floraraster__KartenRasterPunkte_tbl and floraraster__sippen_basis
  • Copy of dataset: Copy of event only included Video starten

  • bavarikon export: Date with 10 places and Permlink added

  • Maintenance:

    • Synchronisation with DiversityReferences - obsolete tables removed
    • Correcting sequence of collectors Video starten
  • Mainform - hierarchy nodes

    • Date changed to IsoDate and time removed if 0
    • Bugfix - adding missing color for table Analysis
  • Exhibition: Change to positive list for valid collection types

  • Spreadsheet:

    • TK-sheet includes hidden RowGUID for collectors by default
    • Bugfix for collector sheet
  • 4.2.5

  • Database updates

    • 02.06.42:

      • CollectionAgent - trgInsCollectionAgent adapted to synchron insert;
      • CollectionSpecimen.LabelTranscriptionNotes changed to nvarchar (MAX);
      • Grants for DataManager;
      • procCopyCollectionSpecimen2: Copy event only included;
    • Postgres packages

      • FloraRaster: Bugfixes in script

       

4.4.3 (2023-06-21)

  • Maintenance
    • Synchronization with DiversityScientificTerms included
    • Bugfix searching for vernacular terms missing a connection
    • References: Transfer data from deprecated for reference in tables CollectionSpecimen and Identification into new table CollectionSpecimenReferences
  • Documentation - Conversion of html to md and vice versa included
  • Main form - Entity adaptions of titles included
  • Enabling "-" sign in login name when creating logins
  • Bugfix removing logins
  • ImportWizard: Deprecated columns for reference in tables CollectionSpecimen and Identification removed

4.4.2 (2023-05-31)

  • Data.Table Bugfix for missing content
  • TableEditor: several bugfixes
  • Query: Bugfix for count conditions
  • Bugfix opening spreadsheet
  • Spreadsheet startup optimized
  • Switching between combobox and textbox for the lable title
  • Bugfix maintenance searching for agents missing a connection

 

4.4.1 (2023-05-22)

  • CacheDB
    • Bugfix getting column list of table
  • Maintenance
    • Bugfix retrieving names from DA including selection of valid names in case of not unique or ambigous names
    • Display of details in agent selection
  • Bugfix ModuleRelatedEntry
  • Testing server connection
  • Import wizard
    • Specimen with many identifiers
    • Restriction to datasource values enabled
  • Query: New options for selection of reverse relations
  • Main form:
    • Bugfix in tree for inverse relations
    • Bugfix getting ID of inverse relation

Database updates

  • 02.06.41: IdentifierSpecimen: Extension with column ReferencedTable to enable insert; CollectionEventLocalisation_Core: Excluding log columns and geography as String; CollectionSpecimenRelationInversList: Listing all internal relations in reverse perspective; CollectionSpecimenRelationInvers: Content of function CollectionSpecimenRelationInversList for improved performance; CollectionSpecimenRelationInternal: All internal relations irrespective of the direction;

 

4.4 (2023-05-05)

  • Maintenance
    • Bugfix splitting collectors including buttons for selection and deselection of items

4.3.249 (2023-05-03)

  • Maintenance
    • Bugfix splitting collectors including buttons for selection and deselection of items
    • Bugfixes synchronizing agents names missing a connection
      • Listing collisions in the like query and inspection of colliding datasets
  • Bugfix showing names for last updates
  • Bugfix creating logins
  • Bugfix for display text for part list
  • Bugfix in usercontrolModuleRelatedEntry: Setting the cursor to the original position after getting the autocomplete source
  • Bugfix wiriting reports for cacheDB transfer
  • CacheDB: Showing server processes
    • Database updates

      • 02.06.40: CollectionSpecimen_Core2: converting logging user from ID to Text

      • Postgres packages

        • ABCD 9: Bugfix abcd___projectcitation - restriction to main project
        • ABCD_BayernFlora: ABCD__BayernFlora_EndangeredSpeciesBase taxnr 3808 added
        • FloraRaster: Bugfix script, FloraRaster_EndangeredSpeciesBase taxnr 3808 added

4.3.248 (2023-04-20)

  • Ensure correct login and password entry
  • Bugfixes with webservices Index Fungorum and Tropicos
  • Bugfix remote query control
  • Bugfixes maintenance
  • Bugfix connecting to linked servers
  • Bugfix reading REST-services for DTN
  • Bugfix maintenance getting agents in text comparision
  • Export for bavarikon with optional separation of files and translation of countries

 

4.3.247 (2023-04-06)

  • Bugfix checking existence of ID in userControlModuleRelatedEntry

  • Index Fungorum - removing trailing year from name returned by xml result

  • Bugfix transfer previous settings

  • Bugfix setting TK25 map

  • Documentation:    

    • Bugfix showing context controls
    • Option for logo and metadata included
    • chm - including metadata
  • Database updates

    • 02.06.39: Missing grants for definition; Missing descriptions in enums; Missing descriptions for tables, triggers, views, ... (Part 4);

4.3.246 (2023-03-24)

  • Data - Export - XML:
  • Transaction:
    • Bugfix setting admin. collection
    • Chart for history
  • Bugfix getting information from DTN database located on linked server
  • Bugfix getting project data from DP
  • Bugfix in basic update script
  • Several bugfixes in restore for archive
  • Checking loops in unit hierarchy including selection for top unit

4.3.245 (2023-03-14)

  • Module related query:

    • Setting height of query form to current window
    • Several bugfixes connecting to CacheDB
  • Import wizard

    • Bugfix checking duplicates
  • Maintenance

    • Bugfix coordinate conversion
  • Documentaton

    • Several bugfixes creating index files from chm infos
  • Statistics

    • History of activity
  • CacheDB

    • Bugfix transferring project descriptors

4.3.244 (2023-02-27)

Download

4.3.243 (2023-02-20)

Download

4.3.242 (2023-02-14)

Download

4.3.241 (2023-02-07)

Download

4.3.240 (2023-01-31)

Download

4.3.239 (2023-01-26)

Download

4.3.238 (2023-01-12)

Download

4.3.216

  • Startup Window
  • New taxonomic groups for insects
  • Exhibition handling
  • Collection plans: Editing geometrie of locations

4.3.219

  • Locking of projects
  • Timeout for connections and startup
  • IPM: Automatic generation of tasks
  • Collection plans: bugfix
  • Administration of enumerations
  • Bugfix external identifier administration

4.3.2[20]

  • Query: Unit in part included
  • Bugfix editing enumerations (' handling included)
  • Timeouts optimized and bugfix for start timeout
  • Bugfix IPM chart
  • Button for setting IPM pests included
  • Collection editing - return to selected tree node after saving

4.3.2[21]

  • Bugfix IPM chart
  • IPM - Plan set to read only
  • Opt. orientation of images according to EXIF infos .
  • Bugfix showing EXIF infos
  • EXIF infos included in image selection

4.3.222

  • Import of Projects: optional restriction to matching type .
  • Maintenance: Bugfix synchronizing taxonimic names via text
  • Project hierarchy including icons corresponding to project type

4.3.223

  • Display of subcollection content redesigned .
  • Bugfix subcollections - exclusion of current specimen
  • Enable search for subcollection content
  • Transfer to collection with optional expansion to whole result list
  • Display plan in main form
  • Query for collection including plan and type

4.3.224

  • New columns RecordingDate und LocationGeometry for CollectionImage
  • New table CollCollectionImageType_Enum and type of image related to this table
  • Optional saving old plans as image including geometry
  • Bugfix collection manager
  • For Collection - Button to transfer all selected collections in a parent collection
  • Bugfix: Showing subcollection content for top level collections
  • Including EXIF information for CollectionImage
  • ImportWizard: Translation of values based upon a table in the database

4.3.225

  • Table editor for collection images added
  • Bugfix showing collection plan in main form
  • Detail images for IPM including position in main image
  • Several bugfixes

4.3.226

  • Connection to database - setting accept button to enable login without mouse actions
  • Query for DataWithholdingReasonDate included
  • Manual editing for Geography in tables CollectionEventLocalisation, CollectionEventSeries and IdentificationUnitGeoAnalysis
  • Spreadsheet with autosuggest
  • TableEditor with autosuggest
  • Starting form traks time for single steps
  • Import wizard: Optional translation of value for attachment
  • Connection menu with Reconnection option

4.3.227

  • CacheDB: Inclusion of AgentIdentifier in sources from DiversityAgents
  • Autosuggest for textboxes in main form
  • Several bugfixes in Event series grid
  • Bugfix query for external identifier: Obsolet query for type removed
  • Autosuggest for textboxes in Grids (Specimen, Images, Organisms, Parts, Collection events, Event series)
  • Progress info window while conneting to database
  • Connection to database: Databases restricted to list, selection within list enabled
  • Bugfix creating archives
  • Autosuggest: Optional exclusion of columns
  • Import wizard: Several bugfixes for translation table, reload of previous selected table, clearing content and reload after change of translation table

4.3.228

  • CacheDB: Bugfix package add ons
  • Startup: Bugfix optimizing messages

4.3.229

  • Query:
    • Removal of obsolet specimen identifier
    • No autocomplete for Count queries
    • Bugfix for Count queries for not optimized query
    • Bugfix preselection for optimized query in combination with count queries
    • Relation:
      • Type included
      • Internal included
    • UTM added
    • Bugfix preselection of nodes for fields checking presence of content
  • Cache database:
    • Diagnostics including search for corrupted NameURIs
    • Diagnostics including search for missing NameURIs
  • Maintenance
    • Bugfix converting coodinates
    • Conversion of UTM coordinates to WGS84 including rounding of values and grid zone
  • Spreadsheet
    • Bugfix starting event grid
    • Bugfix setting autocomplete
  • Bugfix Recording method for localisation

4.3.230

  • Bugfix editing coordinates
  • Submenue for collection and task complemented with superior entry
  • autosuggest in Specimengird changed to suggest

4.3.231

  • Processing duration changed to ISO format
  • Maintenance
    • Bugfix synchronizing agents via text
    • Bugfix synchronizing taxa via text
  • Multicolumns for main form
  • Startposition for event form corrected
  • Query
    • Bugfix for Count
    • Count with < and > operator
    • Collection event: Datawithholding included

4.3.232

  • Selection of material category and taxonomic groups can be restricted via project
  • Bugfix LookupTable: TaxonomicGroups including ParentCode
  • New form for project dependent enumerations
  • Form table editor with optional setting of column width
  • Menu:
    • new entries for editing project dependent enumerations
    • new entries for label type, taxonomic groups and material category within enumeration menu
    • new entries for editing tables LocalisationSystem and Property
      Customization - Projekte fuer TaxonomicGroups und MaterialCategories
  • Maintenance:
    • Bugfix synchronization text for taxa
  • Query:
    • Bugfix resetting booleans\

4.3.233, 4.3.234

  • Query: Bugfix for Labeltitle
  • Images: New button for display in WebView for Specimen, Event and Series
  • Grid: Bugfix copy
  • Bugfix setting printing restriction
  • Multicolumn sorting with position change
  • Bugfix setting display text for multicolumn query
  • Bugfix adding missing parameter to collection event method
  • Bugfix preselection of nodes
  • Data - getting PK for views via basic table
  • Bugfix deleting items in querylist
  • Bugifx setting display text for multicolumn selection
  • Bugfix adding items using multicolumn selection
  • Bugfix in generation of QR-Code for stable identifier
  • Bugfix setting tree node selection

4.3.235

  • Bugfixes in query for transactions with inaccessible documents
  • Bugfix getting PK for view
  • Setting of changes in main form due to permissions if restricted to changes in projectlist
  • Bugfix showing last editor of dataset
  • Autocomplete depending on source
  • Fixing of source : 4 Options
    • No fixing (local values for autocomplete)
    • Webservice (selection via combobox)
    • Database (values from local or remote database)
    • Cache database (values from data imported into cache database)
  • Loading of linked server datasources optional for faster start
  • Loading of translations optional for faster start
  • Fixing source from cache database as source for DiversityAgents, DiversityGazetteer, DiversityReferences, DiversitySamplingPlots and DiversityScientificTerms
  • Taxonlist: Restriction for timerange, Bugfix Export, Export including time restriction and analysis description
  • Transfer selected data to collection event series
  • Bugfix setting query results to restricted
  • Bugfix event series hierarchy
  • New button for removing event series
  • Harmonization of icon for event series
  • Clearing dataset in case of empty result list
  • Creation of index and keyword file from chm content
  • Optional restriction of displayed subcollection content for large collections
  • Bugfix connection administration
  • Redesign of module related entry using table layout panel
  • Administration of connections: Requery of database list
  • UsercontrolModuleRelatedEntry: Requery of local source
  • Bugfix FormLoginAdminGetProjects getting project databases
  • Bugfix Query list
  • Setting default for optimizing and remembering of query with context menu
  • Collection with many order query and type and description as new order columns
  • Bugfix showing dates in many order columns query
  • CacheDB: Inhibit loading of source views or sources when loading of conncetions is set to no.
  • Documentation: Final message and Button for opening folder containing html file
  • Form remote query: Bugfix for query in context of many order columns
  • Bugfix setting toolbar permissions
  • Bugfix showing and revoking of display of accepted names

4.3.236

  • Cache database:
    • New table for project descriptor
  • Bugfix Multicolumns in Query
  • Creating markdown for index and keywords in manual
  • Bugfix creating index files for manual
  • Index and keyword files with css instead of font
  • Bugfix export wizard

4.3.237

  • Bugfix not optimized query in combination with many order columns
  • Query including Depth
  • ExportWizard including Depth
  • Bugfix setting Identification
  • Bugfix getting next and previous items in query for many order columns
  • Bugfix inserting missing identity column in query for many order columns
  • Bugfix Taxonlist: Several identifications produced wrong sums - restricted to last identification
  • Bugfix maps: Browser control replaced by WebView2 due to trouble with Google API
  • Old browser removed from map control
  • Bugfix usercontrolModuleRelatedEntry - Control had not been set properly in all events
  • Collection:
    • Hiding hierarchy and restiction of hierarchy to parent datasets resp. parents including children
    • Bugfix building hierarchy
    • Bugfix closing form

4.3.238

  • Redesign for prometheus API
  • Bugfix collection hierarchy
  • Bugfix Archive creation
  • Bugfix getting coordinates from GoogleMaps
  • Bugfix system tools: setting description for views
  • Bugfix predefined queries
  • Maintenance:
    • Removal of orphaned relations
    • Bugfix retrieval from Geonames
    • Bugfix comparing Coordinates for TK25 using source from linked server
  • Documentation - listing objects and HTML:
    • New button for selection of default choise of database object
    • Bugfix for function
    • Bugfix for showing definitions for views
  • Cache database
    • System tools included
    • Adaption of SystemTools for handling CacheDB

4.3.239

  • Redesign of xaml control for plans
  • Tableeditor with trimming of content
  • Bugfix sorting collectors
  • Bugfix showing GoogleMaps
  • Query:
    • Bugfix for predefined queries
    • Bugfix for ManyOrderColumns
  • Maintenance
    • Bugfix synchronizing agents with similar names
  • Database tools:
    • Description including trigger
  • Collection 
    • Several bugfixes showing hierarchy
    • Button to enable location
    • Button for display of part nodes in Collection tree
    • Setting minimal height for collection plan

4.3.240

  • Documentation:
    • Bugfix by reducing open connections
    • Bugfix getting description of parameter of function
    • In HTML docu:
      • Bugfix getting parameter description of functions derived from basic objects
      • Bugfix listing depending objects
  • Collection: ,
    • Button for switching between administrative and location hierarchy in main form
    • Bugfixes setting image
    • Setting default type for new collections depending on parent type
  • Bugfix searching localities in GoogleMaps
  • Query:
    • Bugfix setting text for multicolumn query
    • Bugfix setting table for query column
    • Bugfix setting text for core-views as main query table
  • Formfunctions:
    • Bugfix filling table
    • Bugfix setting connection
  • Data.Routine - getting type of dependent objects

 

4.3.241

  • Collection:
    • Bugfixes showing Plans
    • Bugfix opening form with empty list
    • Bugfixes getting value for scale
    • Bugfixes setting scale
    • Bugfixes moving scale
  • IPM
    • Bugfix reading Prometheus sensors
    • Several bugfixes saving Prometheus apis
    • Sorting prometheus sensors
  • CacheDB
    • Bugfix opening project filter
    • Systemtools - separation of objects by schema
  • Bugfixes setting password
  • Enumeration administration
    • Bugfix setting images
    • Bugfix setting images in tree
    • Bugfix setting parent
    • Bugfix setting transparency of user defined images
    • Bugfix retrieving images from database
    • Bugfix removing entries
    • Bugfix setting forcolor
    • Bugfix setting transparency for images from database
    • Bugfix building menu hierarchy

 

4.3.242

  • Documentation:

    • Redesign for html controls
    • Html including css
    • Default selection of database objects
    • Notes containing information about excluded objects
      • Checkbox for optional inclusion of these notes
    • Bugfix setting exclusions
    • In HTML docu:
      • Optional exclusion of:
        • standard triggers
        • enumeration tables
        • deprecated columns
        • logging columns
        • obsolete
        • any column
      • Optional inclusion of table dependency
      • Generation of css files if missing
  • Database tools:

    • Button for filling table CacheDescription
    • Button for showing content of table CacheDescription
  • Old webbrowser replaced with new WebView in:

    • CacheDB Diagnostics and BioCASE
    • Database tools at EU DSGVO
    • Documentation: Chm conversion, markdown generation, content
    • FormAnalysis
    • UsercontrolGIS and Usercontrol_GIS
    • FormMaintenance
    • FormStatistics
  • Specimen grid:

    • Bugfix saving new dataset
    • Bugfix passing invisible columns
    • Bugfix adding parts
    • Selection of collection from form if missing
  • Customize display: Bugfix setting default collection

 

4.3.243

  • Query:
    • Bugfix remote query for lists in database, e.g. DST
    • New button to check ProcessID
  • Bugfix running parallel clients with same database connection
  • Documentation:
    • Home button linking to index.html
    • Favicon for sites
    • Bugfix retrieving column description for views
    • chm conversion to html including standard css files
    • Documentation of enum tables

 

4.3.244

  • Several bugfixes getting connections
  • New implementation for webservice IndexFungorum

 

4.3.245

  • Documentation:
    • Generation of markdown files from html files
    • Bugfix generating semantic media wiki

 

 

Database updates

  • 02.06.24: new table CacheDescription; procFillCacheDescription; New collection types subdivided container and sensor; New taxonomic group artefact; New transaction type for warnings; New columns for geometry in table Collection and all depending objects; Grants for DataManager; New tables TaskType_Enum, TaskDateType_Enum, TaskModuleType_Enum, Task, Task_log including trigger; Functions TaskHierarchySeparator, TaskCollectionHierarchySeparator, TaskChildNodes, TaskHierarchy, TaskHierarchyAll; New tables TaskResult, TaskResult_log including trigger; new tables TaskModule, TaskModule_log and trigger; New tables CollectionTask, CollectionTask_log including trigger; Functions CollectionTaskChildNodes, CollectionTaskCollectionHierarchyAll, CollectionTaskHierarchy, CollectionTaskHierarchyAll, CollectionTaskParentNodes; New tables CollectionTaskImage, CollectionTaskImage_log, CollectionTaskMetric, CollectionTaskMetric_log including trigger;
  • 02.06.25: Update content in TaskType_Enum; CollectionTaskHierarchyAll including new column TaskDisplayText; CollectionHierarchySuperior including column Type; CollectionHierarchyAll using Acronym if present; New collection type trap; New task Types IPM and Pest; Disabling not used Task Types; Recreate CacheDescription; procFillCacheDescription - include entity;
  • 02.06.26: Task and all dependent objects: Adding column MetricUnit; Collection types for handling locations; Task types for treatment; ManagerCollectionList: optimizing and bugfix for child nodes; trgInsCollectionTask - use CollectionID if provided;
  • 02.06.27: New table CollTaskMetricAggregation_Enum; Table CollectionTaskMetric - Add column Aggregation; TaskType_Enum - adding type Battery (Charge of a battery) and Bycatch;
  • 02.06.28: trgInsCollectionTask - use CollectionID if provided; CollTaxonomicGroup_Enum: new taxonomic groups for insects; TaskType_Enum: new task exhibition;
  • 02.06.29: ProjectProxy: new column IsLocked; New view CollectionSpecimenID_Locked, CollectionSpecimenID_AvailableReadOnly - include CollectionSpecimenID_Locked; CollectionSpecimenID_ReadOnly - include CollectionSpecimenID_Locked
  • 02.06.30: New collection type area; New columns RecordingDate and LocationGeometry for CollectionImage; New table CollCollectionImageType_Enum;
  • 02.06.31: CollectionTaskImage: new column ObjectGeometry; CollUnitRelationType_Enum: new entry gall inducing; CollMaterialCategory_Enum: new entry pinned specimen; Collection: new column LocationParentID and LocationPlanDate - including all triggers and depending functions; New functions for secondary collection hierarchy: CollectionLocationChildNodes, CollectionLocationMulti, CollectionLocation, CollectionLocationAll, CollectionLocationSuperior.
  • 02.06.32: New LocalisationSystem UTM including description in Entity; New views CollectionSpecimenID_CanEdit and CollectionEventID_CanEdit;
  • 02.06.33: New tables ProjectMaterialCategory and ProjectTaxonomicGroup including trigger; procCopyCollectionSpecimen2: Bugfix for getting correct Specimen ID;
  • 02.06.34: CollectionSpecimen_Core2: Removal of LocalityDescription from Date; CollectionEvent_Core2 - new column for date; trgUpdCollectionSpecimen - Removal of obsolet part and adaption to DSGVO; Check new tables ProjectMaterialCategory and ProjectTaxonomicGroup including trigger; Check procCopyCollectionSpecimen2;
  • 02.06.35: EventSeriesChildNodes - Bugfix and optimizing; trgUpdCollectionSpecimen - Bugfix including trailing commands;
  • 02.06.36:: Missing descriptions for tables, views, ... (Part 1); Adding defaults in table TaskModule if missing; New entry Prometheus in TaskModuleType_Enum for IPM; New column PropertyURI in table CollectionSpecimenImageProperty including trigger;
  • 02.06.37: Removing user defined types to ensure compatiblity to SIARD; Missing descriptions for tables, triggers, views, ... (Part 2);
  • 02.06.38: CollectionLocation in case it is missing; TransactionList_H7 in case it is missing; New Collection Type hardware for e.g. network components; CacheDescription - add Columns Type and Schema; procFillCacheDescription - include System, Views, Procedures, Functions; Removing user defined objects to ensure compatiblity to SIARD; Missing descriptions for tables, triggers, views, ... (Part 3);
  • 02.06.39: Missing descriptions in enums; Missing descriptions for tables, triggers, views, ... (Part 4);

 

Cache Datebase Schema updates

  • 33: Table ProjectEventProperty for blocking Property; Transfer existing data into ProjectEventProperty; procPublishCollectionEventProperty - blocking EventProperty;
  • 34: procPublishCollectionEventLocalisation - fill Accuracy according to precision;
  • 35: procPublishProjectAgent - JOIN with CacheMetadata; procPublishProjectAgentRole - JOIN with CacheMetadata; New table CacheProjectDescriptor; procPublishProjectDescriptor; procPublishCount - include CacheProjectDescriptor;

 

Postgres datebase updates[]

  • 19: New table AgentIdentifier;

 

Postgres datebase schema updates[]

  • 25: New table CacheProjectDescriptor;

 

Package ABCD updates[]

  • 8: ABCD_ContentContact: Restriction to main project; ABCD_TechnicalContact: Restriction to main project;

 

Libraries - DiversityWorkbench

The chapters below describe features that are available in several modules of the Diversity Workbench resp. provided via a shared library like DiversityWorkbench.dll

DiversityWorkbench

Upcoming version

4.2.13

  • Export wizard
    • Bugfix searching for parent of start table
  • Query
    • Bugfix when QueryMainTableLocal is null

Current version

4.2.12

  • Import wizard
    • Bugfixes for duplicate check if no data are available
  • Export wizard
    • Bugfixes if no data are available in parent table
    • Showing generated SQL commands

Previous versions

4.2.11

  • Import wizard
    • Bugfixes for duplicate check for data containing ’ in values of checked column
    • Bugfixes for column pre- and postfix containing ’ in values
    • Option to prevent insert into column
    • Description for columns expanded and redesigned
  • Bugfixes setting linked servers
  • JsonCache: New interface for the modules containing a json summary for datasets

4.2.10

  • Webservice Catalogue of Life available
  • Several bugfixes

4.2.9

  • UserControlQueryList: Dropdownwidth for column selection set to 200 to ensure readablility

4.2.8 (2023-08-30)

  • UserControlQueryList - bugfix if for readonly no valid boolean expression is returned
  • Documentation
    • Bugfix - Listing objects
    • Bugfix - Setting title
    • Bugfix - Selecting schema
    • Bugfix init HUGO replacements

4.2.7 (2023-08-17)

  • Formfunctions
    • Bugfix missing command in function public bool initSqlAdapter(ref System.Data.SqlClient.SqlDataAdapter Adapter, string SQL, System.Data.DataTable Table)
    • Bugfix WorkbenchUnit in function public static string getDatabaseNameFromURI(string URI)
    • Bugfix Project.cs - using ViewBaseURL instead of function or linked server
  • Archive
    • Optional inclusion of log tables
    • Bugfixes resetting database
    • Several bugfixes getting data
    • Several bugfixes restoring archive
    • Progress bars included
    • Extension for setting specific query to get IDs for temp table

4.2.6 (2023-08-01)

  • Documentation
    • Bugfix listing objects
    • HUGO
      • Export of enumeration table content
  • Updating depending datasets Video starten.
    • Context menu:
      • Adding current dataset.
      • Adding all datasets from the list.
      • Showing content of the list.
      • Clearing the list.
  • Bugfix setting backlinks for DiversityCollection linked to DiversityAgents
  • Bugfix setting SQL for backlink updates
  • Bugfix setting backlinks for DiversityProjects linked to DiversityAgents
  • Bugfix setting images in tree of FormEnumAdministration
  • FormFunctions: public static string IsoDate(string Text, bool SpaceAsSeparator = true, bool RestrictToDate = false) expanded with optional restriction to date

4.2.5 (2023-07-25)

  • TableEditor:
    • Bugfix in initForm
  • Enumeration administration:
    • Table editor included
  • Agent - Bugfix getting synonyms in unit values
  • Formfunctions - Autocompletion - Bugfix missing Alias for table
  • Documentation
    • HUGO
      • Export as markdown for HUGO included
      • Replacements and adaptions for HUGO included
  • Spreadsheet:
    • Optional inclusion of RowGUID for tables where PK should be edited Video starten
    • Hiding RowGUID by default

4.2.4 (2023-07-12)

  • FormFunctions:
    • public static string IsoDate(string Text, bool SpaceAsSeparator = true)
  • Documentation:
    • Default output set to HUGO
    • HUGO output
      • Index removed
      • Application objects removed
      • ER-diagram located underneath table header
      • Bugfix ER-diagram path
      • Bugfix Enum output
      • Include menu icon

WpfControls

Current version

1.0.1

  • Bugfix rescanning image if values for height and width are missing
  • Showing message for button ShowDetail if no detail is defined

Diversity Collection

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Nov 28, 2024

Diversity Collection

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.

Diversity Collection

Menu

Connection

  • Create database: Create a new database on the server. You will need system administrator permissions to create a database.
  • Database: Select one of the databases available on the server. Only databases for which the user has access permissions will be listed.
  • Reconnect to database: Reconnect to the current database, e.g., if certain settings are to be made after the reconnection.
  • Module connections: Edit the connections to the other modules within the DiversityWorkbench.
  •  Timeout for web response: Set the timeout duration for web queries, e.g., when downloading images from the web.
  •  Timeout for queries: Set the timeout duration for database queries.
  •  Timeout for connection: Set the timeout duration for connection to a database.
  •  Timeout for start: Set the timeout duration for queries during the start of the application.
  •  Transfer previous settings: Transfer the settings for the IP address and port of the server, name of the database, login, etc., of a previous version of the client to the current version.
  •  Current acivity on server: List the processes on the database server.
  •  Ask on exit: The application should confirm the exit if the main window is closed.
  •  Quit: Quit the application and stop all processes started by the application.

Grid

  • Specimens: Switch to grid mode to edit the specimen dataset in list view.
  • Images: Switch to grid mode to edit the specimen images dataset in list view.
  •  Organisms: Switch to grid mode to edit the organism dataset in list view.
  •  Parts: Switch to grid mode to edit the specimen parts dataset in list view.
  •  IPM: Integrated pest management.
  •  Collection events: Switch to grid mode to edit the dataset of the CollectionEvents in list view.
  •  Event series: Switch to grid mode to edit the dataset of the CollectionEventSeries in list view.
  • Table editor: Edit data as selected in the query data directly in the data tables.
    • Event series table …: Edit data of the collection event series table.
    • Event table …: Edit data of the collection event table.
    • Event method table …: Edit data of the methods used during a collection event.
    • Event parameter table …: Edit the values of the parameters for the methods used in a collection event.
    • Localisation table …: Edit data of the collection event localisation table.
    • Site table …: Edit data of the collection site table.
    • Specimen table …: Edit data of the specimen table.
    • Collector table …: Edit data of the collector table.
    • Relation table …: Edit data of the specimen relation table.
    • Image table …: Edit data of the specimen image table.
    • Organism table …: Edit data of the organism table.
    • Identification table …: Edit data of the identification table.
    • Analysis table …: Edit data of the organism analysis table.
    • Analysis method table …: Edit data of the organism analysis method table.
    • Analysis parameter table …: Edit data of the organism analysis parameter table.
    • Geo analysis table …: Edit data in the geo analysis table.
    • Part table …: Edit data of the specimen part table.
    • Part description …: Edit data of the specimen part description table.
    • Organism in part …: Edit data of the organism in part description table.
    • Processing table …: Edit data of the specimen processing table.
    • Processing method table …: Edit data of the processing method table.
    • Processing parameter table …: Edit data of the processing parameter table.
    • Reference table …: Edit data of the reference table.
    • Transaction table …: Edit data of the transaction table.
    • Specimen transaction …: Edit data of the collection specimen transaction table.
    • Annotation table: Edit data of the annotation table.
      • Event annotations …: Edit collection event annotations.
      • Specimen annotations …: Edit collection specimen annotations
      • Organism annotations …: Edit organism annotations.
      •  Part annotations …: Edit specimen part annotations.
    • Identifier table: Edit data of the identifier table.
      • Event identifier …: Edit collection event identifier.
      • Specimen identifier …: Edit collection specimen identifier.
      • Organism identifier …: Edit organism identifier.
      • Part identifier …: Edit specimen part identifier.
    • Set timeout …: Set the timeout for database queries.
  •  Spreadsheets: Edit data in configurable tables.
    • Event sheet …: Edit event and dependent data with one line per event.
    • TK25 sheet …: Edit organism and dependent data in relation to TK25 information and create distribution maps.
    • Organism sheet …: Edit organism and related data with one line per organism.
    • Mineral sheet …: Edit mineral and related data with one line per mineral.
    • Part sheet …: Edit part and related data with one line per part.
    • Collector sheet …: Edit collectors name with one line per collector.
    • Image sheet …: Edit image and related data with one line per image.
    • Analysis sheet …: Edit analysis and dependent data with one line per analysis.

Query

  • Show query: Show or hide the query list.
  • Predefined queries: All predefined queries will be listed.
  • Scan mode: Change to scan mode to open the data set of a specimen by scanning the barcode.
  • Scan mode collection: Change to the collection scan mode to list all specimens within a collection by scanning the barcode that identifies that collection.

Data

  •  Import
    •  Import wizard: Import data from tab-separated text files.
      •  Import Series …: Import event series from tab-separated text files.
      •  Import Events …: Import events from tab-separated text files.
      •  Import Specimen …: Import specimen data from tab-separated text files.
      • Import Observations …: Import observation data from tab-separated text files.
      •  Import Analysis …: Import analysis definitions from tab-separated text files.
      • Import Collections …: Import collections from tab-separated text files.
      •  Import Methods …: Import method definitions from tab-separated text files.
      •  Import Processings …: Import processing definitios from tab-separated text files.
      • Import Transactions …: Import transactions from tab-separated text files.
      • Import Task …: Import general tasks from tab-separated text files.
      • Import Collectiontask …: Import collection-related tasks from tab-separated text files.
  •  Export
    • Wizard: Export data via a wizard.
      • Event series …: Export event series.
      • Events …: Export collection events.
      • Specimen …: Export specimen.
      • Organisms …: Export organisms.
      • Parts …: Export specimen parts.
      • Transactions …: Export transactions of specimen parts.
    • XML …: Export data as an XML file.
      • ABCD: Export data as an XML file according to the ABCD standard.
      • GPI/JSTOR: Export data as an XML file according to the GPI/JSTOR standard.
    • Export list …: Export a tab-separated file with the data of the specimen.
    •  CSV (bcp): Export data of the entire database as csv files.
  •  Replication: Synchronise the content of 2 databases.
    •  Add publisher …: Add a replication publisher for the replication.
    •  Replication publisher …: Database and server publishing data for replication.
      •  Download …: Download data from the data provider in your local database.
      • Merge …: Merge contents between your local database and the replication provider.
      • Upload …: Upload data from your local database to the replication provider.
      •  Remove …: Remove the replication provider.
    •  Clean database …: Clean your local database.
  • Archive: Archives of projects.
    • Administrate archives …: Administrate the projects that should be included in a schedule-based archiving.
    •  Create archive …: Create and archive of project data.
    • Reset database …: Reset the database, i.e. remove all user data.
    • Restore archive …: Restore project data from an archive.
    • Create schema …: Generate schema files describing the database tables for the project.
  • Cache DB: Export data of selected projects into a cache database.
  •  Backup database: Create a backup of the entire database.
  •  Transfer: Transfer data sets.
    •  to collection …: Transfer all parts of the selected specimen into a collection.
    •  to project …: Transfer the selected specimen into an additional project.
    •  to transaction …: Transfer the selected specimen into an additional transaction.
    •  to event series: Transfer the data selected in the query results into a CollectionEventSeries.
  •  All identifiers: List all identifiers in the selected dataset.
  •  All annotations: Edit all annotations in the selected dataset.
  •  Remove specimen: Remove the selected specimen from the database.
  •  Remove from project: Remove the selected specimen from an additional project.
  • Restore from log: Restore data that had been deleted from the log tables.
  •  Save data set: Save current data set.
  •  Scan modules: Scan connected modules for references to the selected agent.
  •  Collection events: Get access to the collection event data independent of the specimen.

Administration

  • Analysis: Administration of the analysis methods used for the specimens.
  •  Change password: Changing the password of a user (only available for SQL-Server accounts).
  • Collections: Administration used for the collections.
  •  Collection tasks: Administration of collection tasks.
    • IPM: Integrated pest management.
    • Prometheus: Administration of prometheus sources.
    • Exhibitions: Administration of exhibitions
  •  Tasks: Administration of tasks.
  • Customise display: Customising the display of the window, e.g., the material categories and taxonomy groups that should be visible when creating a new entry.
  • Database: Administration of the database.
    • Description: Administration of the descriptions and messages within the application.
    • Database tools: Tools for the administration of the objects in the database - for experts only!.
    • Documentation: Documentation of the structure of the database.
    •  Logins: Administration of the logins of the server and their permissions in the databases.
    • Maintenance: Maintenance of database entries, especially if connected to other modules.
    •  Queries: Creating and editing predefined queries.
    • Rename database: Rename the current database.
    • Set published address: Setting the address published for links by other modules.
    •  Transfer log: Transfer logging data into a separate database.
    •  Enumerations: Administration numeration tables.
  •  External datasources: Administration of the external data sources of data imported into DiversityCollection.
  •  External identifier: Administration of the external identifier.
  • Kiosk mode: Set the client into the Kiosk mode.
  • Linked server: Administration of the linked server
  • Material categories: Administration of the material categories.
  • Methods: Administration of the methods used for CollectionEvents, Analysis and Processing.
  •  Processing: Administration of the processing procedures applied in the collection.
  • Projects: Administration of the projects.
  • Resources directory: Setting the directory for the resources
  • Retrieval type: Administration of the retrieval types.
  •  Site properties: Administration of the properties of collection sites.
  •  Stable identifier: Administration of the stable identier.
  •  Taxonomic groups: Administration of the taxonomic groups.
  • Transaction management: Management of transactions, managers, loans etc.
    • Transactions: Administration of the transactions e.g. loans, exchange etc.
    •  Expired loans …: Administration of expired loans. This menu entry will appear when expired loans are in collections where the current user is a curator.
    •  Loan requests …: Administration of loan requests for the collections for which a user is a collection manager. This menu entry will appear when loan requests are for the managed collections where the current user is a collection manager.
    • My requests …: Administration of the loan requests of a user. This menu entry will appear when a user places requests for specimens.
    •  Loan requesters …: User having the right to place requests for specimen of a collection.
    •  Collection managers …: Administration of the users who manage collections and are, e.g., responsible for the administration of the transactions.
    •  Collection users …: Administration of user access to data within collections.
    •  Transfer to transaction …: Transfers data into a transaction.
  •  Withhold data: Edit the withholding reasons for the selected data.

Help

  •  Manual: Opens the online manual.
  •  Feedback: Opens a window for sending feedback.
  • Feedback history …: Opens a window for browsing former feedback.
  • Edit feedback …: Opens a window for editing feedback sent to the administrator (for admins only).
  •  Statistics: Overview of changes within the projects and edited specimen.
  • Info …: Show the program version and related information.
  • Websites: Websites related to DiversityCollection.
    • Download applications …: Download DiversityCollection from the website of the DiveristyWorkbench project.
    • Information model …: Inspect the information model on the website of the DiveristyWorkbench project.
    • Diversity mobile …: Website of DiversityMobile, the mobile application for collecting data stored in DiversityCollection.
    • GitHub: Resouces on GitHub.
      • SNSB: Resources provided by the Staatliche Naturwissenschaftliche Sammlungen Bayerns.
      • ZFMK: Resources provided by the Zoologische Forschungsmuseum Alexander Koenig.
  •  ErrorLog: Open the errorlog of the appliaction.

Update

  • Update database: Update the database to the current version.
  •  Update client: Download the current version of the client.
  • Quit: Quit the application and stop all processes started by the application.

Shortcuts

Some of the menus are accessible via shortcuts, e.g.:

  • ALT + D = Data
  • ALT + D + S = Save
Apr 22, 2025

Diversity Collection

Tutorial

First steps

This tutorial will guide you through the first basic steps to enter a single data set in DiversityCollection.

Before you start, you must have the client DiversityCollection installed and have access to a database. For more information, see the chapter Installation and Access to the database.

To start the program either select the application from the start menu or double click on the DiversityCollection.exe in the directory in which you have copied the files of DiversityCollection.

The main window will open.

 

Connect to server and database

The first time you open this window, you’ll need to connect to the server and a database.

You can also watch a short German video showing the login process: Video starten.

  1. Click the button or select Connection → Database… from the menu.
  2. A window will open where you can enter your account information and select the database you want to work with (see the screenshots below).

   

  1. After connecting to the server and choosing a database click on the OK button to connect to the database and return to the main window.
  2. The icon in the top right corner of the main window indicates that you are now connected to the database. The tooltip of this button shows your current login information (see below).

 

Next chapters

This tutorial continues in the sections listed below.

 

Mar 21, 2025

Subsections of Tutorial

Diversity Collection

Tutorial

Creation

Tutorial - Creating a new dataset

At the beginning of this tutorial, we will create a first dataset step-by-step.

A short introductory video (in German) is also available: Video starten.

Add a new dataset

 

  1. Each record must be linked to a project. Therefore, the first step is to select a project within the query conditions (see point 1 in the image above), and then start the query (see point 2). If no project is selected, the program will remind you to choose one.

  2. To enter a new dataset, click the button in the top left corner (see point 3).

  3. If accession numbers are available in the database, the software will ask whether you want to use the next available number (see chapter Accession for more information). Click “OK” to search for the next available accession number, starting with your current number.

  4. The new entry will appear in the Query results list on the left. Select it to view the specimen tree structure on the right (see point 4 in the image above). All details and input fields will be displayed in the right part of the window (see point 5). NOTE: If you haven’t specified an accession number, the entry will appear as shown above. Otherwise, the assigned accession number will be displayed.

Enter data for the specimen

  1. To enter your data for the specimen, click on the corresponding entry in the upper part of the tree (see point 3 in the image below).

  2. This opens the input fields in the right-hand section, where you can enter the details (see point 4).

  3. In the middle section of the form, several buttons will appear that let you add more information about the specimen (see point 5). These options are explained in the following chapters of this tutorial.

  

More detailed information

For more information on specimen trees see the chapter Specimen tree. If you want to define parts of your specimen, see the Storage chapter.

For more information on the query results, see the chapter Specimen list and an overview of the menu bar, visit the Data Handling chapter.

Next chapters

This tutorial continues in the sections listed below.

Apr 22, 2025

Diversity Collection

Tutorial

Event

Tutorial - CollectionEvent

Specimens stored in a collection are gathered during a CollectionEvent. This CollectionEvent keeps for example information about the geographic locality, the habitat, the collection date. For more detailed information about CollectionEvents see the chapter CollectionEvent.

Add a collection event

  1. To add a collection event to your specimen, select the specimen in the tree (within the image below the blue marked ID:651640).
  2. Click on the button to add a new CollectionEvent (see point 1 in the screenshot below).

  

  1. This will add an entry for the CollectionEvent to the upper tree, as shown below.
  2. Select this entry in the tree (see item 2 in the image below) to open the CollectionEvent fields.

Enter data to the collection event

  1. Select the collection event entry in the tree (see item 2 in the image below) to open the CollectionEvent fields.
  2. Enter the date (see point 3 in the image below) of the CollectionEvent. Clicking the dropdown button (see image below) will open a calendar where you can select the date.
  3. Enter the description of the locality (see point 4 in the image below).
  4. To save the previous data, click on the button (see point 5 in the image below).

 

  1. You now have the option to enter further information about the location, such as coordinates, named places, etc., by clicking on the button (see point 6 in the image above).

Next chapters

This tutorial continues in the sections listed below.

 

Mar 21, 2025

Diversity Collection

Tutorial

Localisation

You can add additional location information to your collection event, such as coordinates, named places, etc.. In this tutorial we will look at the three main options, such as “WGS84 coordinates”, “NamedArea (DiversityGazetteer)” and “Altitude (mNN)”.

Add location information

  1. Click on the button button (see point 6 in the image below).

 

  1. Select an option from the list (see image below).

The three main options are:

New Coordinates WGS84

Using Google Maps you can add the exact coordinates of the location.

  1. Click the button (see point 6 in the image above)

  2. Select Coordinates WGS84 (Longitude / Latitude) (Google Maps uses WGS84).

  3. This will add a new entry to the tree view. Select it (see point 1 in the image below) to open the details for that entry.

  4. Next, click the button (see point 2 in the image below).

  5. A window will open (see figure below) where you can set the coordinates simply by dragging the map with the mouse. The coordinates correspond to the center of the map, symbolized by the . Click on the OK button to save the coordinates.

     

  6. In the main window, the coordinates are stored in two locations – see the screenshot below. In the upper area, you can set the values ​​and choose a different display format, as shown here – the more familiar format with degrees, minutes, and seconds. Change the values ​​and click the button to change the original input. At the same time, the numeric values ​​are saved in fields that cannot be edited by the user (see below).

 

New Named Area (Diversity Gazetteer)

  1. To enter a place name via the Diversity Gazetteer, select “New Named Place (Diversity Gazetteer)” from the list.

  2. An entry will be added to the overview tree in the center of the window, as shown below.

  3. Select it to open the fields for that entry (see item 1 in the image below).  

  4. To open the connection to the DiversityGazetteer click the button (see point 2 in the image above).

  5. A window will open as shown below.

  6. Enter a search string - for example the city you wish to find (see point 3 in the image below)

  7. Start the query with a click on button (see point 4 in the image below).

     

  8. The query results are listed in the center of the form. Select a result. To guide you to the correct entry, the details of the respective location are displayed to the right of the list. The base displays a map with the corresponding coordinates. After selecting the correct entry (see point 5 in the image above), click OK to return to the main window (see point 6 in the image above).

  9. As shown below, the data retrieved from the gazetteer is displayed in different panels. In addition to the location name, the DiversityGazetteer displays the coordinates and country, as shown below.

     

  10. The area where you entered the name is now locked and prevents you from changing the entry (see image below). Next to the location field, you will find the link to the external module. Click it for more details.

     

  11. If you wish to remove the connection to the external module click on the button. This will keep all entries (country, place, coordinates) but remove the connection to DiversityGazetteer.  

New Altitude (mNN)

The last information we provide about the location is the altitude.

  1. Click on button (see point 6 of the first image of this site)

  2. Select New Altitude (mNN) (see point 1 in the image below).

  3. Select the new entry in the overview to open the data fields (see point 2 in the image below).

  4. Let’s suppose you have only feet values available - change the display format to feet (see point 3 in the image below). Enter your values (see point 4 in the image below) and click on button (see point 5 in the image below) to save your entries. Now your values are converted to meter (the internal format of DiversityCollection) automatically. If you now change the display format to meter, you can see the result. The program calculates an average value for the altitude and accuracy in meter corresponding to the accuracy of your original values (see below). The original values of your entry are saved in the Notes field.

     

Next chapters

This tutorial continues in the sections listed below.

 

 

Mar 21, 2025

Diversity Collection

Tutorial

Event Series

If you need a hierarchical order of your CollectionEvents or want to organize several CollectionEvents, for example to document expeditions, you can achieve this with a CollectionEventSeries. For more detailed information about CollectionEventSeries see the section CollectionEventSeries.

Create a new EventSeries

  1. To create a new EventSeries select the ColletionEvent in the specimen tree (see point 1 in the image below).
  2. Click on button Add a new event series (see point 2 in the screenshot below).

 

  1. The entry for the new EventSeries appears in the tree view (see point 3 in the image below).

    • If the new EventSeries is not displayed in the tree view, click the button Show parent event series to the right of the tree view.  
  2. Select the CollectionEventSeries entry in the tree view to enter the details for this EventSeries (see point 4 in the image below).

 

  1. To enter the date of the CollectionEventSeries, click the dropdown button to open a calendar where you can select the date.

  2. Next, enter the description of the location (see point 6 in the image below).

  3. To save the data entered so far, click the button.

Create hierarchies of CollectionEvents and CollectionEventSeries

Events and event series can be organized hierarchically.

Create a new CollectionEventSeries hierarchy

To create a hierarchy for your CollectionEvents and CollectionEventSeries, select the created EventSeries in the tree (see step 1 in the image above).

  1. Before adding a new event series, change the page view of the tree. Click the button in the top left corner next to the tree view and select Show event hierarchy.
  2. Select the EventSeries in the tree. In our example Mehrere Sammlungen.
  3. Add a second EventSeries New EventSeries and proceed analogously as described above in the chapter Create a new EventSeries.
  4. Finally drag the CollectionEvent to its position within the hierarchy of the CollectionEventSeries entries. In our example, the event 12.02.2025 Botanical Garden Munich is dragged under the event series “New Event Series”.

 

Add a CollectionEvent to an existing CollectionEventSeries

You can also add a CollectionEvent to an existing CollectionEventSeries.

  1. Select the CollectionEvent in the tree view.

  2. Click on the button .

  3. The window Collection event series will open. Click on the filter button to search for all CollectionEventSeries.

  4. Select the one you want to assign the event to and click OK.

Next chapters

This tutorial continues in the sections listed below.

 

Mar 21, 2025

Diversity Collection

Tutorial

Specimen

Specimens are the entities stored in a collection. For more detailed information about CollectionSpecimen see the section CollectionSpecimen.

 

Assign an accession number

  1. To set the accession number for the CollectionSpecimen select it in the overview (see point 1 in the image above)

  2. Next enter the accession number (see point 2 in the image above).  OR

  3. Search for the next available accession number, click the corresponding button as shown above (see point 3 in the image above). A window will open as shown below. Start the search for a available accession number. If the query was successful, click OK to add the new accession number to your data record.

     

Assign projects

Each dataset must be linked to at least one project. But you can assign as many projects as you want.

  1. To add another project to access your data, click the button in the project list (see point 4 in the image above).
  2. This opens a dialog where you can select a project from those defined in DiversityCollection (see image below). The project will then be added to the list of projects for this specimen. 

 

Next chapters

This tutorial continues in the sections listed below.

 

Mar 21, 2025

Diversity Collection

Tutorial

Collector

Collectors

Collectors are the people or groups responsible for the gathering of the specimen. In the DiversityWorkbench framework the collectors are managed in the module DiversityAgents. There may be several collectors for one specimen. For more detailed information about Collectors see the chapter Collectors.

Add collectors to a specimen

You can add and link existing collector(s) in the DiversityAgents module, and add new collector(s) without linking.

  1. Select the specimen in the tree.
  2. Click the button to add a new collector (see point 1 in the image below).
  3. Select the collector in the overview (see point 2 in the image below).
  4. Click on the button to open the interface of the DiversityAgents module (see point 3 in the image below).

 

  1. A window for DiversityAgents will open.
  2. There you can enter search criteria (see point 1 in the image below) and click on the button to start the query (see point 2 in image below).

  1. Select the entry from the query result (see point 3 in image the above) and click on the OK button (see point 4 in the image above) to link the name in DiversityCollection.
  1. To insert a collector click on the button (see point 1 in the image below)
  2. Select the New collector 2 (see point 2 in the image below).
  3. Enter the beginning of the name in the name field (see point 3 in the image below). All entries already stored in the database will be listed, beginning with the entered phrase. The list will be updated according to your entries in the field. You can either select a matching entry or enter a new name if it is not included in the displayed list.
  1. If the collector has a field number, enter that number (see point 4 in the image below).

 

  1. Finally save your changes.

 

Next chapters

This tutorial continues in the sections listed below.

Mar 21, 2025

Diversity Collection

Tutorial

Relation

In DivesityCollection you have the ability to define and manage connections between data. Specifically, the module supports two types of relations:

  1. Internal Relations: These are connections to specimen that already reside within DiversityCollection.

  2. External Relations: These are connections to specimen that are not managed within DiversityCollection.

For further information on relations see the chapter Relation.

1. Internal relations

  1. To enter a relation to a specimen in DiverisityCollection select the specimen in the tree (see point 1 in image below)
  2. Click on the button (see point 2 in image below).

 

  1. A window will open where you can search for the related specimen.
  2. In the window enter your restrictions (see point 1 in the image below)
  3. Start the query (see point 2 in image below).
  4. Select the related specimen from the result list (see point 3 in image below)
  5. Click OK (see point 4 in image below) to insert the relation.

 

  1. Select the relation entry (see point 1 in the image below) to display the details fields.
  2. Enter the type of the relation (see point 2 in the image below).  

 

2. External relations

  1. To enter a relation to a specimen from a foreign collection, create a relation (see point 1 in the image below)
  2. Select it in the tree view (see point 2 in the image below).
  3. Enter the name of the specimen (see point 3 in the image below).
  4. Select the type of relation (see point 4 in the image below).
  5. If a dataset exists for the collection, you can select it from the list (see step 5 in the image above). (Otherwise you must first add the collection to the list. For more information see the chapter Collection)

 

Next chapters

This tutorial continues in the sections listed below.

Mar 21, 2025

Diversity Collection

Tutorial

Organisms

(= Identification Units)

The organisms or items in a CollectionSpecimen are considered as IdentificationUnits. A specimen may contain multiple IdentificationUnits, e.g., an insect (1) feeding on a fungus (2) growing as a parasite on a plant (3). For more detailed information about Organisms (=IdentificationUnits) see the chapter Organisms.

Presets

To focus on the specimen and its organisms, hide all other entries in the tree by clicking the corresponding buttons on the left side of the specimen tree. The yellow background of a button indicates that the respective information is not currently displayed (see point 1 in the image below).

Add a new organism

You can add any number of organisms to a specimen. Organism types are selected from a list. To add a new organism, follow the next steps.

  1. Select the specimen entry in the tree (see point 2 in the image below).
  2. Then select the appropriate organism from the list, in our example a plant .

  1. This will insert an entry for the organism ( ) along with an identification ( ) below the entry for the specimen ( ) (see the image below).

  2. To view the details of the organism, or to enter the details, select the organism entry in the tree. (see point 1 and 2 in the image below)

  1. To view the details of the identification entry, or to enter the details such as taxon name, etc. , select the identification entry in the tree. (see point 1 and 2 in the image below and follow the next section Add details to the identification).

Information about identifications

You can add as many identification as you like to an organism. See Section Enter an additional identification for an organism for more information.

Add details to the identification

To view the information for the identification, select the identification entry in the tree view (see point 1 in the image above). The fields for the identification will appear to the right of the tree view (see point 2 in the image above).

You can enter taxonomic names in different ways.

  1. Enter the taxonomic name without linking it.

  2. Link the taxonomic name to a module, such as DiversityTaxonNames, or to a webservice.

All options are demonstrated below using examples.

Enter a taxonomic name without linking

In the first example, we will enter a taxonomic name for the plant without linking it.

  1. Select the entry for the identification in the tree (see point 1 in the image below).
  2. In the identification area of the main window, enter a taxonomic name by simply typing it in the Tax. name field (see point 2 in the image below).
  3. To save the data set and display the taxonomic name in the tree, click on the button (see point 3 in the image below).

In our second example, we link a taxonomic name to the module DiversityTaxonName.

Information about remote modules and webservices

For more information about linking to remote modules, see chapter remote query.

Please note: To demonstrate the various possibilities simultaneously, we previously added two more organisms, like a fungus and an insect to our specimen example. How this works is described in Chapter Enter more organisms to a specimen.

In our second example we add a linked taxonomic name to the fungus.

  1. Select the identification of the fungus in the tree (see point 1 in the image below).
  2. In the identification area of the main window, click on button to open the window for the remote modules (see point 2 in the image below).

In the newly opened window, you must first select the database of the module or the webservice you want to link.

  1. Select the database DiversityTaxonNames_Fungi (see point 1 in the image below).
  2. Enter the search conditions, e.g. the beginning of the taxonomic name (see point 2 in the image below).
  3. Start the query (see point 3 in the image below).
  4. From the result list select the taxonomic name (see point 4 in the image below).
  5. Click OK (see point 5 in the image below) to transfer the selected name to the main form.  

The name of the selected taxon is inserted into the “Taxonomic name” field along with the link to the data source (see figure below). The taxonomic name cannot be edited directly as long as it is linked to a data source (highlighted in yellow). To remove the link, use the button . To view the details of the linked name in the data source, click the button .

In our third example, we link a taxonomic name to the webservice Catalogue Of Life.

Information about remote modules and webservices

For more information about linking to remote modules, see chapter remote query.

Please note: To demonstrate the various possibilities simultaneously, we previously added two more organisms, like a fungus and an insect to our specimen example. How this works is described in Chapter Enter more organisms to a specimen.

In our third example we add a linked taxonomic name to the insect.

  1. Select the identification of the insect in the tree (see point 1 in the image below).
  2. In the identification area of the main window, click on button to open the window for the remote modules (see point 2 in the image below).

In the newly opened window, you must first select the database of the module or the webservice you want to link.

  1. Select the webservice CatalogueOfLife (see point 1 in the image below).
  2. Enter the beginning of the taxonomic name (see point 2 in the image below).
  3. Start the query (see point 3 in the image below).
  4. From the result list select the taxonomic name (see point 4 in the image below).
  5. Click OK (see point 5 in the image below) to transfer the selected name to the main form.  

The name of the selected taxon will be inserted into the “Taxonomic Name” field along with the link to the data source (see figure below). The taxonomic name cannot be edited directly while linked to a data source (yellow background). To remove the link, click the button . To view the details of the linked name as stored in the data source, click the button .

Enter more organisms to a specimen

To enter more organisms living on the plant (see point 2 in the image below) select the plant in the tree (see point 1 in the image below) and create new organisms as described above in section Add a new organism

 

Enter an additional identification for an organism

To enter an additional identification for an organism, select it in the tree (see point 4 in the image below) and click the button (see point 5 in the image below). This will insert a dataset for an additional identification of the organism below the organism, as shown below.

Next chapters

This tutorial continues in the sections listed below.

Mar 21, 2025

Diversity Collection

Tutorial

Storage tree (= specimen parts tree)

A specimen may contain multiple parts, which may be housed in multiple collections. These parts may represent different material categories, such as herbarium sheets, microscopic slides etc.
For more detailed information about “Specimen Parts” see the chapter Parts of the specimen.

There is also a German video for this chapter Video starten.

View the storage tree

The parts of the specimen are displayed in the storage tree, below the main specimen tree.

  1. To display this tree, click on the button below the specimen tree (see point 1 in the image below).

  2. A window will open in which you must select the material category of the part you want to insert (see the image below). Select “herbarium sheets” from the list.

  3. Another dialog window will open, where you must enter the collection in which your samples are stored (see the image below).

  4. Select the collection from the list or hierarchy and click “OK” to close the dialog. The lower tree now contains the selected material with all organisms (see all organisms in the image below).

Edit the storage tree

Assume that the insect is not present in the specimen, but was only observed during sampling, for example. To document this, remove the insect entry from the Display in label list to the Units not included in part list.

  1. Select it (see point 1 in the image above)

  2. Remove it (see point 2 in the image above) (click on the < button). The result is shown below.

Switch to the location tree view

To view the exact location within the collection, click the button on the left side of the tree. The tree view will change as shown below, listing all collections and subcollections along with the parts of the item.

You can print a label for a stored part of the specimen. Therefore you have to open the “print and label” view.

  1. Select the part in the tree (see point 1 in the image below).

  2. To open the “print and label” area, click the dropdown menu in the upper right corner of the header and select Printing (see point 2 in the image below).

  3. The “print and label” view is now displayed (see the image below).

  4. Click the button (see point 3 in the image below) to select a schema file (e.g., Standard.xslt).

  5. Then click the button to create a preview of the label (see point 4 in the image below).

Next

This tutorial continues in the sections listed below.

 

 

Mar 21, 2025

Diversity Collection

Tutorial

Query

To search for data in the database, use the query area in the left panel (see the image below). You can query almost any field in the database. You can also customize the view and specify the query options you want.

Structure of the query panel

All fields belonging to the query are displayed in the query area in the left panel (see figure above).

  1. In the lower area (see point 1 in the image above), you can enter your query criteria, such as selecting a project and specifying an accession number. You can also specify which query fields are displayed (see section Customize your query conditions).

  2. In the middle area (see point 2 in the image above) you will find all buttons that trigger a search etc.

  3. The results are listed in the upper panel (see point 3 in the image above). If you select a result by clicking on it, all details are displayed in the panels to the right of the query.

For more detailed information, see the chapter Query.

Customize your query conditions

  1. To customize and set your query conditions click on the button in the top panel (see point 4 in the image above).

  2. A window will open as shown below.

     

With the Maximum number of results you may limit the package size which should be retrieved from the server. For a slow connection to the database server choose a low value (e.g. 100 as set by default).

The Limit for drop-down lists restricts the maximum number of drop-down lists which should be created. For a slow connection to the database server choose a low value. The default is set to 0 which means no drop-down lists will be created.

Click on the Check none button to clear the previous selection. Then select the entries

  • Project → Project
  • Specimen → Accession number of specimen
  • Specimen → The user who created the data set
  • Specimen → The date when the data set was created
  • Event → Collection date
  • Organism → Organism present
  • Organism → Only observed
  • Storage → Material category
  • Image → Type

Click OK to close the window. Your query conditions will be displayed as in the image below.

Project → Project: Here you may choose from a list of possible entries. Select your current project.

Collection specimen → Acc. Nr.: From the operator drop-down list choose “~” and enter the first letters of your accession number. You may include wildcards. Other options are e.g. “-” for a range or “>” for a lower limit. The conditions will be interpreted as text! So 2 will be listed after 10 etc.

Collection specimen → Creat. by.: From the operator drop-down list choose “=” and choose your user name from the list.

Collection specimen → Cre. dat.: From the operator drop-down list choose “=” and choose the current date with the help of the calendar.

Collection event → Date: >From the operator drop-down list choose “=” and enter the current year in the last field.

Organism → Presence: From the operator drop-down list choose “•” which means that an organism is present.

Organism → Only obs: Uncheck the checkbox to find organisms which were not only observed.

Part of a specimen → Mat.cat.: Use the button on the right of the combobox to open the hierarchy and select “herbarium sheet”.

After all query conditions are set, click on the button to start the query. In the result list you should find the specimen created in this tutorial. If the remember query option is a activ, the last query will be saved and is availabel after a restart.

 

 

Mar 21, 2025

Diversity Collection

Queries - overview

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .
 

 

 

Jan 14, 2025

Subsections of Query

Diversity Collection

Optimized query

To speed up the query you may use the optimized version.

Icons

Standard query: Optimized query:

The optimized query in combination with the remembering option includes the functionality to preselect data depending on the query restrictions, e.g. if you search for an identification and enter a taxonomic name the first identification matching the restrictions will be preselected in the main window as shown below.

Default

To set the “optimized query” and the “remember last query” option as default, go to AdministrationCustomize display in the menu of the main window. In the tab Defaults and miscellaneous select the “Optimized and “Remember” option. The buttons are hidden in the main window, providing more space.

![](diversitycollection/Query_Customize display_Defaults.png)

Many columns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

 

Aug 19, 2024

Diversity Collection

Predefined queries

Besides setting queries for specimens via the query options you may define separate predefined user-specific queries. These are listed in the menu topic Query - Predefined queries

If you choose one of these predefined queries, the query options will be hidden and the command of the query will be shown at the base of the specimen list. The first line shows the title of the query, the next lines contain the description followed by the part of the query command which restricts the selection of the data sets (= WHERE-clause of the SQL-statement).

 

To return to the user-defined query click on the Show query conditions button.

If you are an administrator, you may create new queries for users. To create a predefined query choose Administration - Queries... from the menu. A window will open as shown below, where you may create, edit and test your queries.

 

In the upper field you define the WHERE-clause of the SQL string of your query. Keep in mind that the queries can refer to different tables, depending on the order column chosen by the user. Thus, queries in DiversityCollection should start with the reference to the primary key of the main table (CollectionSpecimenID in table CollectionSpecimen and depending tables). The lower field contains the description for the query as shown in the user interface. To test a query use the Test count and Test query buttons.

Oct 4, 2024

Diversity Collection

Query Operators

When entering your query conditions, you have various operators to choose from. The available operators are shown in the tables below.

Availability: t = text, n = numeric, d = date, h = hierarchy, x = XML, e = EXIF, g = geography, a = annotation, m = module\

Op. Meaning Example Avail.
search for an entry like… (you may use wildcards) Pinus s[iy]lvestris % tn---e--
= search for an entry exactly equal to … Pinus silvestris L. tndh----
search for an entry not like... Pinus s[iy]lvestris % (you may use wildcards) tn------
search for an entry where a value is missing … tndhxeg-
search for an entry where a value is present … tndhxeg-
- search for an entry between … and … 2000 - 2003 tnd-----
| search within a list of entries, separated by "|" or one line per value. If wildcards ("%", "_") are included the query will search for values like the given values 2000 | 2003 ... | 2000 2003 tn------
search with exclusion of a list of entries with one value per line. Wildcards will be ignored 2000 2003 tn—–m
search with exclusion of a list of entries with one value per line. Wildcards will be ignored 2000 2003 tn—–m
± search for an entry where only parts of the date are present… -.-.2006 --d-----
Δ search including children in a hierarchy … M-Fungi ---h----
/ Search for entries containing a given XML node (not for EXIF) settings ----x---
¬ Search for entries not containing a given XML node (not for EXIF) settings ----x---
Search for entries with a maximal distance of … POINT(24.24 45.243) | 50 km ------g-
O Search for entries within an area POLYGON(34.5 ... ------g-
¤ Search for entries outside an area POLYGON(34.5 ... ------g-
+H Search for entry including lower hierarchy Picea | Picea abies -------m
+S Search for entry including synonyms Picea abies | Pinus abies -------m
+HS Search for entry including lower hierarchy and symonyms Picea | Picea abies | Pinus abies -------m

Operators for datasets

Operator Meaning
search for missing datasets ...
search for existing datasets ...

Operators for text

Operator Meaning Example
search for an entry like ... Pinus s[iy]lvestris % (you may use wildcards)
= search for an entry exactly equal to ... Pinus silvestris L.
search for an entry not like ... Pinus s[iy]lvestris% (you may use wildcards)
search for an entry where a value is missing ...
search for an entry where a value is present ...
- search for an entry between ... and ... 2000 - 2003
| search within a list of entries, separated by "|" or one line per value. If wildcards ("%", "_") are included the query will search for values like the given values 2000 | 2003 ... | 2000 2003
search with exclusion of a list of entries with one value per line. Wildcards will be ignored 2000 2003
search with exclusion of a list of entries with one value per line. Wildcards will be ignored 2000 2003

Operators for numeric data

Operator Meaning Example
= search for an entry exactly equal to … Pinus silvestris L.
< search for an entry lower than ... 2006
> search for an entry higher than ... 2006
- search for an entry between ... and ... 2000 - 2003
| search within a list of entries, separated by "|" or one line per value 2000 | 2003
search within a list of entries with one value per line 2000 2003
search with exclusion of a list of entries with one value per line 2000 2003
search for an entry where a value is missing ...
search for an entry where a value is present

Operators for date values

Operator Meaning Example
= search for an entry exactly equal to ... 20.3.2006
< search for an entry lower than ... 20.3.2006
> search for an entry higher than ... 20.3.2006
- search for an entry between two dates... 20.3.2006 - 29.3.2006
± search for an entry where only parts of the date are present... -.-.2006
search for an entry where the date is missing …
search for an entry where the date is present and complete …

Oparators for hierachy

Operator Meaning Example
= search for an entry exactly equal to ... M-Fungi
search for an entry which is not equal to … M-Fungi
search for missing entry ...
search for present entry ...
Δ search including children in a hierarchy ... M-Fungi

Operators for XML

Operator Meaning Example
~ Search for entries like a given text (for EXIF) RDF
/ Search for entries containing a given XML node (not for EXIF) settings
¬ Search for entries not containing agiven XML node (not for EXIF) settings
search for missing entry ...
search for present entry ...

Operators for geography

Use (via local files or manual creation) resp. (via DiversityGazetteer) button to set geography

Operator Meaning Example
Search for entries with a maximal distance of ... POINT(24.24 45.243) | 50 km
O Search for entries within an area POLYGON(34.5 ...
¤ Search for entries outside an area POLYGON(34.5 ...
search for missing entry...
search for present entry ...

For yes/no fields exists a checkbox with 3 options: = yes, = no, = undefined

For a search within a lists (using the |, ∈ or ∉ operator) you may double click in the text field to open a window where you can enter your values. To separate the values either use the "|" sign or a new line as shown in the image below.

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris
Jan 14, 2025

Scan mode

Scanner

With the scan mode you may use a barcode scanner or the camera of your computer or tablet using e.g. bcWebCam to search for a specimen. To work with the scan mode select the Scan mode in the Query menu. The query part will be hidden and the field for the scanned identifier will be accessible for the entry via the scanner. As possible identifiers you can choose among the accession number of the specimen , the ID of the specimen ID, the accession number of the part or the identifier of the organism . If the field for the entry of the identifier is not activated, move the mouse to the field to activate it. Once you scan the barcode the program will start the search for the specimen in the database. To return to another query mode deselect the Scan mode.

If the results captured by the scanner do not correspond to the scanned codes, the timer intervall may need an adaption to your scanner. To set the timer interval of the scanner, click on the button. The default is set to 200 ms. Change it until the results captured by the scanner correspond to the codes.

 

The second scan mode for collection codes (stable identifier for collections) or the name of the collection will list all specimen within a collection. For the query of collection names these must be unique within the database. The query for collections may include depending collections. By default only specimen of the selected collection will be shown. Click on the button above the button to change to the mode including specimen in depending collections.

 

 

Jan 14, 2025

Diversity Collection

Queries - many columns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Apr 7, 2025

Diversity Collection

Result list

The result list displays the specimens found in a query.

The specimens may be displayed with their e.g. with their accession number. To change the information of the specimen shown in the list, choose among the option provided in the order by: combobox. Some possibilities are shown above: identifications, storage location or collectors number. After you changed the selection of the displayed information, you have to start the query to see it in the result list. To view further information on the chosen field simply place the mouse in the field. A text box will appear with the description of the field (see below).

 

You may restrict the maximum number of specimens and queryoptions (click on the button), if you have for example a slow connection to the database. As a default the maximum number is set to 100. If the number of data sets according to your query is higher than the maximum value set in the query options, it will be indicated in the header of the list.

To ensure that restrictions set in the query conditions will be applied to the specimen list make sure that you choose matching restrictions and order columns as shown below. In the upper example corresponding fields were used for restricting the query and the display (Tax. name). Here the query results will be restricted to said field.

 

In the second example a different field for the restriction was chosen (Last ident. <> Tax. name). The query result in consequence will list all data sets with entries found in the field Tax. name and entries which match the restriction (see below).

 

To search for specimens enter the restrictions in the fields for the search conditions and click on the button. The specimens found in the database will be shown in the result list. To add specimens with differing search conditions click on the button. If the list of items is longer than your maximum number of returned items you may browse the next items with the button. If you wish to remove entries from the selected list, choose them in the list and click on the button. This will not delete the data from the database but remove them from your query result.

The result list will contain data with Read only access. For these data all controls and menus for editing the data will be disabled except the button for adding annotations .

Here are some examples you may select for display in the result list:

AccessionNumber: One entry is shown for each specimen with its corresponding accession number.

Last identification: The last identification for every unit in a specimen is shown in the list. As there can be several units in one specimen, several entries for one specimen may appear in the list.

Storage location: The storage location of every part of a specimen stored in the collections is shown in the list. As parts of a specimen can be stored in several collections under different names, several entries for one specimen may appear in the list.

Collecting number: The collecting number given by the collector of every sample of a specimen is shown in the list. A specimen may have several collectors each with a different number. Therefore, several entries for one collection specimen may appear in the list.

Apr 7, 2025

Diversity Collection

Editing the data

The main window of the DiversityCollection client contains two main areas. On the left you find the query and the results of this query. On the right the data of the data set selected in the results list is shown. The upper part of the data area shows images, labels etc. In the lower part you find two trees that give you an overview and access to the data. The data of an entry selected in one of the trees is shown in the data editing section. 

Common comments

To see the descriptions of the fields, just move the mouse over the field you want to know more about. A tip-text window will open, showing the description of the expected content of this field (see image below). These descriptions are also available in the documentation for the tables

The descriptions of some of the drop-down fields are too long to be shown in the drop-down column. However, for a selected entry you can place your mouse over the hierarchy selector. A tip-text window will appear (see image below) where the full text of the description is shown. 

Mar 19, 2025

Subsections of Editing

Diversity Collection

Data in tables

Besides of the main form, DiversityCollection provides 3 editors of the data in tabular form:

  • Table editors : Provide single table based access to the data of the query results in the main form
  • Grids : Provide predefined tabular access to the data of the query results in the main form
  • Spreadsheets : Provide predefined tabular access including the possibility to query and filter data and can be used as starting form

See a short tutorial for an introduction Video starten.

Comparison of tabular forms

Property Table editors Grids Spreadsheets
Range One table Predefined selection of tables Predefined selection of tables
Query Depending on main form Depending on main form Own query
Filter Restricted Restricted Direct query in database
Column sequence Fixed Changeable Fixed
Start form No No Yes
Different versions No No Yes
Read only projects No access No access Read only mode
Data in map No No In TK25 sheet

 

Jan 14, 2025

Subsections of Data in Tables

Diversity Collection

Grids

To edit the data in a data grid, select Grid mode for the specimen , the organisms , the parts , the images the collection events or the collection event series from the menu. A window will open where each dataset from the query result list is represented in a single line for a specimen, an organism, a CollectionEvent or a CollectionEventSeries respectively. Please note that in this view, only a limited part of the data is visible. For example, only the most recent identification of an organism is displayed. This is shown in the image below, where two organisms (marked with red arrows) are not visible in the grid view because only the latest identification per organism is shown.

When using grid mode for organisms, all organisms will appear, but only with their most recent identification.

 

Customise column headers

The names of the columns can be changed using the database description.

 

Customise fiel visibility

The selection of the visible fields can be adjusted in the tree above the list. Change the selection of the columns and click on the Set columns button.

 

 

Customise column width and sequence

To adjust the width of the columns or the height of the rows, either drag the border with the mouse or double-click on the border to obtain the optimum size for a column. You can also click the button for the optimal height of the rows or the button for the optimal width of the columns. To change the width and sequence of the columns, drag the columns to the position of your choice or adjust the width to your preference. These changes will be saved for this session and the next time you use grid mode. To return to the original sequence of the columns, click the Reset sequence button.

 

Sorting the data

To sort the data in the grid, click in the header of the column you want to use as the sorting column. The sort will persist even if you change values in that column. This means that if you change a value in the sort column, the changed record will be placed in the new position according to its new value. The sorting of a column is indicated by an arrow indicating the direction of sorting (up or down) and by a thicker right margin of that column (see image below).  

 

 

Find and replace

To use the find and replace functions, you must either select part of the field in this column or click the button to select the whole column. You can then select the function you wish to use (remove, insert, append or replace). To replace a part of the text in the selected fields, type the text to be replaced and type the replacement in the appropriate fields. To start the replacement, click on the button. To insert a string to the beginning of all entries in the selected fields, click the button. To append a string to all entries in the selected fields, click the button. To remove all entries from the selected fields, click the button.

 

Transfer from spreadsheet

You can transfer data from a spreadsheet, such as Excel or Calc. Copy the relevant columns from your spreadsheet and paste them into DiversityCollection. Click in the top-left cell where the data should be inserted, then open the context menu (click the right mouse button) and select Insert to paste the data.

 

Editing

Some columns cannot be edited directly, but are linked to external modules or services. These columns are displayed as buttons. Click on the button to access the service. If a value is linked to an entry in an external module, the background will change to [yellow], and the text will no longer be editable.

 

Together with the links (as shown in the example above [Link to DiversityAgents]), you can also select columns that allow you to remove links to modules (e.g. [Remove link for collector] in image above). These columns appear as buttons . Simply click on the button associated with a link to remove the connection to the corresponding module. After doing so, you can edit the text field containing the previously linked value.

Some values are linked to a predefined list of options. To change such a value, use the drop-down list available in the column.

 

New dataset

If you click on the empty line at the base of the data grid, you will be asked if you wish to create a new dataset. The program will ask you for a new accession number and the project of the new dataset. Another way to create a new dataset is to use the copy button . Simply click on the row you wish to create a copy of and then click on the copy button . For details see the Data section. A copy of the dataset will be inserted at the base of the data grid.

 

Saving the data

To save all changes, click the button. To undo all changes since the last time the datasets were saved, click the button. To save the changes to the current dataset use the button. To undo the changes in the current dataset, click the button. If you click the OK button, you will be asked if you want to save the changes before the window closes. If you click the Cancel button or close the window, your changes will not be saved. To export the data displayed in the grid as a text file with tabs as column separators, click on the button. 

 

Apr 25, 2025

Subsections of Grids

Diversity Collection

Series Grid

Grid mode for the CollectionEventSeries

To edit the data in a data grid choose the Grid mode for the CollectionEventSeries from the menu. A window will open where every data set for a CollectionEventSeries from the query result list is restricted to one line (see below). 

 

Customize the window

To change the width of a column simply use your mouse to adapt the width to your preference. To hide or show parts of the window use the button for the hierarchy tree and the button for the images in the upper right corner of the window. If the parts are shown, the icon will have red background e.g. .

History and feedback

To inspect the history of a data set click on the button. A window will open as described in the History chapter. To send a feedback use the  button. Details are described in the Feedback chapter.

Sorting of the data

To sort the data in the grid simply click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. This means if you change a value in the sorting column, the changed data set will be placed at the new position according to its new value. The sorting of a column will be indicated by an arrow for the direction of the sorting (up or down) and by a thicker right border of this column (see image below).  

 

 

Handling the data

To save the changes click on the button. To insert new data sets use the button for a CollectionEventSeries and the button for a CollectionEvent.

 

 

Jan 14, 2025

Diversity Collection

Event Grid

Grid mode for the CollectionEvents

To edit the data of the CollectionEvents in a data grid choose the Grid mode for the event from the menu. A window will open where every data set for a CollectionEvent from the query result list is restricted to one line. Please keep in mind you can only see a limited part of the data while in this view. For example only a part of the localisation will be displayed (see below).

 

Customize the window

To change the width of a column simply use your mouse to adapt the width to your preference. To hide or show parts of the window use the button for the setting of the visible columns, the button for the hierarchy tree and the button for the images in the upper right corner of the window. If the hierarchy tree is visible (, see below), you have access to the CollectionEventSeries which are linked to the CollectionEvents. Here you can edit the hierarchy via drag & drop. Please keep in mind that ramifications within the hierarchy can only be realized using EventSeries with CollectionEvents placed within and specimen placed within the CollectionEvents. To insert a new EventSeries use the button below the tree.

To change the width and sequence of the columns simply use your mouse to drag the columns to the position of your choice or adapt the width to your preference. These changes will be saved for this session as well as for the next time you use the grid mode. To return to the original sequence of the columns click on the Reset sequence button.

 

Customize visibility of fields

The selection of the visible fields can be adapted in the tree above the list. Change the selection of the columns and click on the Set columns button.

 

 

Sorting of the data

To sort the data in the grid simply click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. This means if you change a value in the sorting column, the changed data set will be placed at the new position according to its new value. The sorting of a column will be indicated by an arrow for the direction of the sorting (up or down) and by a thicker right border of this column (see image below).  

 

[Formatting the grid]

To adapt the width of the columns or the height of the rows either drag the border with the mouse or double click the border to get the optimal size for one column. You may also click on the button for an optimal height of the rows or the button for an optimal width of the columns.

 

 

Handling the data

Find and replace

To use the find and replace functions you must either select a part of the field in this column or click on the button to select the entire column. You may then choose the function you wish to apply (remove, insert, append or replace). To replace a part of a text in the selected fields enter the text which should be replaced and enter the replacement in the corresponding fields. To start the replacement click the button. To insert a string to the beginning of all entries in the selected fields click the button. To append a string to all entries in the selected fields click the button. To remove all entries from the selected fields click the button.

 

Editing

Some columns can not be edited directly but are linked to external modules or services. These columns appear as buttons. Simply click on the button to call the service. If a value is linked to an entry in an external module, the background will change to [yellow] and you will not be able to change the text.

 

Together with the links (in the example above [Link to DiversityAgents]) you can select columns that provide the possibility to release the links to the modules (e.g. [Remove link for collector] in image above). These columns will appear as buttons . Simply click on the button related to a link to release the link to the corresponding module. After that you can edit the text field containing the linked value.

Some values are linked to a list of values. Use the drop-down list to change the value in one of these columns.

 

Saving the data

To save all changes click on the button. To undo the all changes since the last time the data sets were saved click on the button. To save the changes in the current data set use the button. To undo the changes in the current data set click the button. If you click the OK button, you will be asked whether you would like to save the changes before the window will be closed. If you click the Cancel button or close the window your changes will not be saved. To export the data shown in the grid as a text file with tabs as column separators click on the button. 

 

 

 

Dec 4, 2024

Diversity Collection

Specimen Grid

Grid mode for CollectionSpecimen

To edit the data of the specimens in a data grid choose the Grid mode for the specimen from the menu. A window will open where every data set for a specimen from the query result list is restricted to one line. Please keep in mind you can only see a limited part of the data while in this view. For example only the last identification of an organism will be displayed. This is demonstrated in the image below where two organisms, indicated with the red arrows, will not appear in the grid. If you use the grid mode for the organisms, all organisms will appear with their last identification.

 

Customize visibility of fields

The selection of the visible fields can be adapted in the tree above the list. If this part is hidden click on the button to make it accessible. Change the selection of the columns and click on the [Set columns] button.

 

 

Customize column width and sequence

To adapt the width of the columns or the height of the rows either drag the border with the mouse or double click the border to get the optimal size for one column. You may also click on the button for an optimal height of the rows or the button for an optimal width of the columns. To change the width and sequence of the columns simply use your mouse to drag the columns to the position of your choice or adapt the width to your preference. These changes will be saved for this session as well as for the next time you use the grid mode. To return to the original sequence of the columns click on the Reset sequence button.

 

Sorting of the data

To sort the data in the grid simply click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. This means if you change a value in the sorting column, the changed data set will be placed at the new position according to its new value. The sorting of a column will be indicated by an arrow for the direction of the sorting (up or down) and by a thicker right border of this column (see image below).  

 

 

Find and replace

To use the find and replace functions you must either select a part of the field in this column or click on the button to select the entire column. You may then choose the function you wish to apply (remove, insert, append or replace). To replace a part of a text in the selected fields enter the text that should be replaced and enter the replacement in the corresponding fields. To start the replacement click the button. To insert a string to the beginning of all entries in the selected fields click the button. If the selected column is a link to a module or webservice, a button will appear where you can search for a linked data set. The insert will set the selected column and related columns according to the linked data set. Thus, if you choose e.g. a value from the DiversityGazetteer, the coordinates and the country will be changed as well. Click on the link to see all related information. To reset the link use the button. To append a string to all entries in the selected fields click the button. To remove all entries from the selected fields click the button.

 

Transfer from spreadsheet

You can transfer data from a spreadsheet e.g. Excel or Calc. Copy the columns of this data from the spreadsheet and then insert it in DiversityCollection. Click in the upmost left cell where this data should be transferred to and use the context menu (click the right mouse button) to insert the data.

 

Editing

Some columns can not be edited directly but are linked to external modules or services. These columns appear as buttons. Simply click on the button to call the service. If a value is linked to an entry in an external module, the background will change to yellow and you will not be able to change the text.

 

Together with the links (in the example above [Link to DiversityAgents]) you can select columns that provide the possibility to release the links to the modules (e.g. [Remove link for collector] in image above). These columns will appear as buttons . Simply click on the button related to a link to release the link to the corresponding module. After that you can edit the text field containing the linked value.

Some values are linked to a list of values. Use the drop-down list to change the value in one of these columns.

If you click in the empty line at the base of the data grid, you will be asked if you wish to create a new data set. The program will ask you for a new accession number and the project of the new data set. Another way to create a new data set is the copy button . Simply click in the line you wish to create a copy of and then click on the copy button . For details see the Data section. A copy of the data set will be inserted at the base of the data grid.

In the grid view for the organisms a part of the columns can not be edited. These columns contain data which can be related to several organisms. This is indicated by a gray background.

The Relation has two states:

either external (the column [Related specimen URL] will be shown in the interface) or internal.   (the column [Related specimen display text] will be shown in the interface) Use the [Relation is internal] column to change the state and the [Link to DiversityCollection for relation] column to set an internal relation. 

 

Saving the data

To save all changes click on the button. To undo all changes since the last time the data sets were saved click on the button. To save the changes in the current data set use the button. To undo the changes in the current data set click the button. If you click the OK button, you will be asked whether you would like to save the changes before the window will be closed. If you click the Cancel button or close the window your changes will not be saved. To export the data shown in the grid as a text file with tabs as column separators click on the button. 

 

Inserting new data

To insert a new data set simply click in the last empty line of the data grid. The program may ask you to specify a project in which the new data should be placed. In the grid for the organisms a window will open as shown below.

 

Here you have the option to insert the new data set of the organism in the last specimen in the grid or to create a new specimen for the organism. In the second case you can specify the accession number of the new specimen. Use the Find Acc. Nr. button to search for the next free accession number in the database which matches your entry in the Accession number field.

For new data sets you can specify certain project settings e.g. the material category of a part of the specimen. The taxonomic group of a new organism will correspond to the first organism in your last specimen unless you specify a certain taxonomic group in the project settings for the project you are working in. To enter or change a setting you need the module DiversityProjects. For further information please turn to the documentation provided with this module. 

 

Copy data

To copy a data set select the line of the data grid you wish to create a copy of and click on the button. For further details, see the chapter Copy specimen.

 

 

Jan 14, 2025

Diversity Collection

Grid

Organisms

To edit the data of the organisms in a data grid choose the Grid mode for the organisms from the menu. A window will open where every data set for an organism from the query result list is restricted to one line. Please keep in mind that you can only see a limited part of the data in this view. For example only the last identification of an organism will be displayed. 

In the grid view for the organisms a part of the columns can not be edited. These columns contain data which can be related to several organisms. This is indicated by a gray background.

Customize the window

To change the width and sequence of the columns simply use your mouse to drag the columns to the position of your choice or adapt the width to your preference. These changes will be saved for this session as well as for the next time you use the grid mode. To return to the original sequence of the columns click on the Reset sequence button.

To adapt the width of the columns or the height of the rows either drag the border with the mouse or double click the border to get the optimal size for one column. You may also click on the button for an optimal height of the rows or the button for an optimal width of the columns.

The selection of the visible fields can be adapted in the tree above the list. Change the selection of the columns and click on the Set columns button.

 

Analysis

In this grid you can edit up to 10 different types of analysis, however, only the last analysis will be shown for each type. By default the available analysis types will be generated dynamically depending on the data. If you need an additional type in the grid, simply return to the main form and enter the required type in one of the data sets. If you wish to specify which analysis you want to see in the grid, you can set the list in the options. Click on the button to open a window as shown below.

Here you can restrict the range of the dates of the analysis and the types of the analysis which should be displayed. To change the entries in the list use the and buttons to add or delete entries.

 

Sorting of the data

To sort the data in the grid simply click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. This means if you change a value in the sorting column, the changed data set will be placed at the new position according to its new value. The sorting of a column will be indicated by an arrow for the direction of the sorting (up or down) and by a thicker right border of this column (see image below).  

 

 

Handling the data

Some columns can not be edited directly but are linked to external modules or services. These columns appear as buttons. Simply click on the button to call the service. If a value is linked to an entry in an external module, the background will change to [yellow] and you will not be able to change the text.

 

Together with the links (in the example above [Link to DiversityAgents]) you can select columns that provide the possibility to release the links to the modules (e.g. [Remove link for collector] in image above). These columns will appear as buttons . Simply click on the button related to a link to release the link to the corresponding module. After that you can edit the text field containing the linked value.

Some values are linked to a list of values. Use the drop-down list to change the value in one of these columns.

If you click in the empty line at the base of the data grid, you will be asked if you wish to create a new data set. The program will ask you for a new accession number and the project of the new data set. Another way to create a new data set is the copy button . Simply click in the line you wish to create a copy of and then click on the copy button . For details see the Data section. A copy of the data set will be inserted at the base of the data grid.

In the grid view for the organisms a part of the columns can not be edited. These columns contain data which can be related to several organisms. This is indicated by a gray background.

Find and replace

To use the find and replace functions you must either select a part of the field in this column or click on the button to select the entire column. You may then choose the function you wish to apply (remove, insert, append or replace). To replace a part of a text in the selected fields enter the text which should be replaced and enter the replacement in the corresponding fields. To start the replacement click the button. To insert a string to the beginning of all entries in the selected fields click the button. To append a string to all entries in the selected fields click the button. To remove all entries from the selected fields click the button.

To save all changes click on the button. To undo all changes since the last time the data sets were saved click on the button. To save the changes in the current data set use the button. To undo the changes in the current data set click the button. If you click the OK button, you will be asked whether you would like to save the changes before the window will be closed. If you click the Cancel button or close the window your changes will not be saved. To export the data shown in the grid as a text file with tabs as column separators click on the button. 

To copy a dataset select the line of the data grid which you wish to create a copy of and click on the button. A copy of the selected data set will be added at the base of the spreadsheet. 

 

 

Jan 14, 2025

Diversity Collection

Grid

Organisms of a specimen

To edit the data of the organisms of a specimen select the specimen entry in the tree and click on the button in the panel on the right. A window as shown below will open with the functionality of the grid for the organisms but restricted to the organisms of the current specimen.

 

 

 

Jan 14, 2025

Diversity Collection

Part Grid

Grid mode for the parts of the specimen

To edit the data of the parts in a data grid choose the Grid mode for the Parts...  from the menu. A window will open where every data set for a part from the query result list is restricted to one line. Please keep in mind you can only see a limited part of the data while in this view. For example only the last processing or analysis of a certain type of a part will be displayed.

 

Customize the window

To change the width and sequence of the columns simply use your mouse to drag the columns to the position of your choice or adapt the width to your preference. These changes will be saved for this session as well as for the next time you use the grid mode. To return to the original sequence of the columns click on the Reset sequence button.

To adapt the width of the columns or the height of the rows either drag the border with the mouse or double click the border to get the optimal size for one column. You may also click on the button for an optimal height of the rows or the button for an optimal width of the columns.

The selection of the visible fields can be adapted in the tree above the list. Change the selection of the columns and click on the Set columns button.

 

Analysis

In this grid you can edit up to 10 different types of processing, however, only the last analysis will be shown for each type. To specify which analysis you wish to see in the grid click on the button to open a window as shown below.

Here you can restrict the range of the dates of the analysis and the types of the analysis which should be displayed. To change the entries in the list use the and buttons to add or delete entries. For taxonomic groups which miss certain types of analysis the columns will be blocked.

 

Processing

In this grid you can display up to 5 different processings, however, only the last processing will be shown. You can define a time range for the processing that should be displayed and / or restrict the processing to a certain type (see image below). For material categories which miss certain types of processing the columns will be blocked.

 

Sorting of the data

To sort the data in the grid simply click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. This means if you change a value in the sorting column, the changed data set will be placed at the new position according to its new value. The sorting of a column will be indicated by an arrow for the direction of the sorting (up or down) and by a thicker right border of this column (see image below).  

 

Selecting of the data

To restrict the data in the grid you can filter an entry. Select the entry for which you want to filter and click on the button. To remove data from the grid select the rows which should be removed and click on the   button.   

 

Handling the data

Some columns can not be edited directly but are linked to external modules or services. These columns appear as buttons. Simply click on the button to call the service. If a value is linked to an entry in an external module, the background will change to [yellow] and you will not be able to change the text.

 

Together with the links (in the example above [Link to DiversityAgents]) you can select columns that provide the possibility to release the links to the modules (e.g. [Remove link for collector] in image above). These columns will appear as buttons . Simply click on the button related to a link to release the link to the corresponding module. After that you can edit the text field containing the linked value.

Some values are linked to a list of values. Use the drop-down list to change the value in one of these columns.

If you click in the empty line at the base of the data grid, you will be asked if you wish to create a new data set. The program will ask you for a new accession number and the project of the new data set. Another way to create a new data set is the copy button . Simply click in the line you wish to create a copy of and then click on the copy button . For details see the Data section. A copy of the data set will be inserted at the base of the data grid.

In the grid view for the parts a part of the columns can not be edited. These columns contain data which can be related to several parts. This is indicated by a gray background.

 

Find and replace

To use the find and replace functions you must either select a part of the field in this column or click on the button to select the entire column. You may then choose the function you wish to apply (remove, insert, append or replace). To replace a part of a text in the selected fields enter the text which should be replaced and enter the replacement in the corresponding fields. To start the replacement click the button. To insert a string to the beginning of all entries in the selected fields click the button. To append a string to all entries in the selected fields click the button. To remove all entries from the selected fields click the button.

To save all changes click on the button. To undo all changes since the last time the data sets were saved click on the button. To save the changes in the current data set use the button. To undo the changes in the current data set click the button. If you click the OK button, you will be asked whether you would like to save the changes before the window will be closed. If you click the Cancel button or close the window your changes will not be saved. To export the data shown in the grid as a text file with tabs as column separators click on the button. 

To copy a dataset select the line of the data grid which you wish to create a copy of and click on the button. A copy of the selected data set will be added at the base of the spreadsheet. 

 

 

Jan 14, 2025

Diversity Collection

Image Grid

Grid mode for the images of the specimen

To edit the data of the images in a data grid choose the Grid mode for the Images...  from the menu. A window will open where every data set for an image from the query result list is restricted to one line (see below). 

 

Sorting of the data

To sort the data in the grid simply click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. This means if you change a value in the sorting column, the changed data set will be placed at the new position according to its new value. The sorting of a column will be indicated by an arrow for the direction of the sorting (up or down).  

 

Selecting the data

To restrict the data in the grid you can filter an entry. Select the entry for which you want to filter and click on the button. To remove data from the grid select the rows which should be removed and click on the   button.   

 

Handling the data

Some columns can not be edited directly because they are linked to external modules or services. These columns appear as buttons. Simply click on the button to call the service. If a value is linked to an entry in an external module, the background will change to [yellow] and you will not be able to change the text.

Next to the links there are columns which allow you to remove a link to the corresponding module . Simply click on the button to remove the link. After that you can edit the text field containing the linked value.

Some values are linked to a list of values (e.g. Image type). Use the drop-down list to change the value in one of these columns.

 

Find and replace

To use the find and replace functions you must either select a part of the field in this column or click on the button to select the entire column. You may then choose the function you wish to apply (remove, insert, append or replace). To replace a part of a text in the selected fields enter the text which should be replaced and enter the replacement in the corresponding fields. To start the replacement click the button. To insert a string to the beginning of all entries in the selected fields click the button. To append a string to all entries in the selected fields click the button. To remove all entries from the selected fields click the button.

To data are automatically saved when you close the window. To undo all changes click on the button.  

 

 

Jul 3, 2024

Diversity Collection

Table Editors

For the data selected in the main window the table editors offer a direct access to the tables of the database as shown in the image below. In the hierarchy tree of the main window every entry corresponds to a table in the database, marked for the image below for the tables CollectionEvent and IdentificationUnit. Underneath the menu Grid select one of the Table editors (see below). For an introduction see a short tutorial Video starten.

A window with the content of the table will open. Columns with a [gray background] can not be edited here. Columns with a [light gray background] are linked to the contents of lookup tables where you can change according to the contents of these tables. If you are using the optimzed query certain columns that are linked to lookup tables show the translated content instead of the IDs. With the [ ID ] button you can change back to the original, not translated content of the table. The tables below are examples for those that are included for direct access via a table editor:

Select Set timeout ... from the menu to increase the default timeout from 5 seconds to a higher value, e.g. for greater amounts of data.  

With the button you can set the widths of the columns according to the header and the content. With the button the width is set to the content. After the column width is set, this will be indicated with a yellow background . Click again on the button to release the setting of the column width .

  For more details see chapter TableEditor

Mar 20, 2025

Diversity Collection

Spreadsheets

The program provides several spreadsheets with different focus:

  • Event
    • Main table: CollectionEvent
    • The focus is the collection event
  • TK25
    • Editing data that are linked to a TK25 entry.
    • The sheet provides a link to distribution maps with the option to select data via these maps
  • Organism
  • Mineral
    • Focus on mineral specimen
  • Part
  • Collector
    • Main table: CollectionAgent
    • All collectors of a specimen
  • Image
    • Main table: CollectionSpecimenImage
    • All images of a specimen
  • Analysis
    • Main table: Analysis
    • Administration of the analysis

The spreadsheets similar to the grids provide a tabular access to the data. In addition you can search and filter data independent from the main form. For an introduction see two short tutorials Video starten (overview), Video starten (tables and columns). To open a spreadsheet, choose Grid - Spreadsheets - and then one of the provided versions, e.g. Organisms from the menu. A window as shown below will open where the data are marked and organized according to the database tables. If values in one of the tables are missing, this will be indicated with a grey background. The colors correspond to the overview for the database.

Start

To use any of the spreadsheets as a starting window, click on the  button. Now the application will directly open the spreadsheet with the same parameters when you close it. Video starten

 

Database

To change to another database, click on the button and choose the database as described here. Please keep in mind that the main form will connect to the new selected database. 

 

Project

If a user has read only projects available, a button will appear in front of the project. Click on this button to change to the list of projects with read only access. The window will change into the Read only mode (see below). To return to the list of projects with write access, just click no the button again. After changing the source for the project list, the project label will blink with red to remind you, to select a project from the list. Video starten

 

Getting the data

The data are always restricted to one project, selected in the corresponding field (see image above) and restricted to the first top lines as specified in the Max. res. field. To change to the next or previous block of data, use the resp. button. 

The program will organize the data in blocks indicated by the colors as shown above. In the example above the first block contains 2  Organisms all belonging to the block starting with  Hildesheim... for the Event and M-0014196 for the Specimen. The next block then starts with  Hildesheim... indicated by a change in the color containing 2 Organisms. For most of the spreadsheets, the presence of the Event in the data is a prerequisit. As long as you do not sort or filter the data (see below), these blocks will be consistent with the data. As soon as you filter or sort the data, these blocks may be split and may not correspond to the data blocks in the database any more. In the example below you see the effect of sorting by the column Taxon on breaking up the blocks. E.g. the block for the specimen M-0036950 is split into 2.

 

SQL

The query used for the retrieval of the data can be accessed with a click on the SQL button.

 

Filtering

To filter the content of a table you can apply a filter either on the whole table or on each of the columns of the table.

Table filter

This filter will apply on the whole table. Click in the black box next to the filter area and select one of the filter options as shown below.

  • : Filled (all visible columns)
  • : Empty (all visible columns)
  • : Data in table do exist
  • Ø: Data in table do not exist

Tutorial:

Column filter

Tutorial: Video starten

This filter will apply on a single column of a table. To set a filter click in the field underneath the column name. A window as shown below will open. With a click on the button you can enter a value from the current content of the column as filter.

Here you set the sorting (see below), enter the search string and choose among several ways of comparison with the contents in the database:

  • =: The content must be exactly like the given value
  • : The content must be different to the given value
  • ~: The content must be similar to the given value, use wildcards % for any string or _ for a single character
  • ¬: The content must NOT be similar to the given value, use wildcards % for any string or _ for a single character
  • <: The content must be smaller than the given value
  • >: The content must be bigger than the given value
  • |: The content must be in a given list of values
  • : The content must NOT be in a given list of values

For columns linked to modules of the DiversityWorkbench there may be additional options. E.g. for a column linked to DiversityTaxonNames you get 3 additional options:

  • +H: Include lower Hierarchy
  • +S: Include Synonyms
  • +H+S: Include lower Hierarchy and Synonyms

After selecting one of these options, you will be asked for the database and the project where the data should be taken from. In the next step the corresponding names as retrieved from the selected source will be listed (see below). To change the filter click on the button and on the button to remove it.

Sorting

↓↑ Tutorial: Video starten

The data can be sorted by each visible column. If you click into the field underneath the column name a window will open as described above. To change between the modes of sorting, just click on the current sorting. The modes are:

  • -: Not sorted
  • : Sorted in ascending sequence
  • : Sorted in descending sequence

After all parameters are set, the sort mode and filter settings will be shown in the field underneath the column name (see image below). The number indicates the sequence within the sorting columns.

 

Timeout

After all parameters are set, click on the button. If for any reason you get a timeout, meaning the query for the data takes too long, either simplify your query or adapt the time for the query after a click on the button. If you do not want to restrict the time for the queries, set the value to 0. The default value is 30 seconds. 

 

Read only mode

<> Tutorial: Video starten

The formatting of the sheet including the color indication of tables and data blocks is rather time consuming. If these are not needed, e.g. for exporting the data, you can switch to the Read only mode for higher performance. For projects with read only access (see above), the mode is automatically set to Read only

 

Editing

Video starten

To edit the data, just change them. If data are missing, type or select a value in the corresponding field. To remove data, click on the x field. This will remove all entries dependent on this entry that means all data right from the entry in the same line resp. block and any depending data. If there are any depending data, a window will open as shown below listing these data. Click OK if you want to remove the selected data including all depending data as shown in the window.

 

To change the content of several values in a column, either select the whole column with a click on the  button or select the fields manually. To avoid the pop-up of data-entry windows e.g. for columns with a lookup list, click no the button. Once you have selected the contents to change, select the mode of change:

  • Prepend: Insert the given value at the beginning of the content
  • Append: Append the given value at the end of the content
  • Overwrite: Remove current content and insert given value
  • Replace: Replace a string in the content with the given value
  • Clear: Remove the content

After selecting the change mode, enter the text in the field where necessary and click on the corresponding button to perform the changes.

With the context menu (mark area and right click) you can Remove data (for single data fields with a list behind), Tranfer or Copy the content into the clipboard and Insert the content of the clipboard into the selected cells. Tutorial: Video starten

Locked columns

Columns that can not be edited are indicated with a lighter background color of the header and a gray text of title and content. These columns contain e.g. database generated content or data from lookup tables.

Inclusion of RowGUID

By default the primary key can not be changed in the spreadsheet. In some cases you may want to change parts of the primary key. To do this, you must include the column RowGUID in the list of selected columns. The program will ensure that the changed data do not collide with existing data, that is having the same primary key. See an example in a short tutorial:

 

Fixed sources

Tutorial: Video starten

For columns that are linked to a remote module, you can fix the source for the query. If the source is fixed, the query will directly contact the source as shown in the image below. To set resp. change the source, click on the button. A window will open where you can select either a webservice or a source database together with a project within the database. To remove the source, click on the button (only visible if a source is present).

To see an overview for the fixed sources, click on the button. A window will open where all sources are listed with the source for the current column marked with a yellow background. 

 

A "right-click" on the button in the main form will show the settings as well and with a click on the button you can set the connection for the selected column. If a column depends on values from the data as for example the relations to the module DiversityTaxonNames with a dependence on the taxonomic group, the relation will change with the selected row, depending on the data retrieved from the selected row. If there is no connection to the related module defined, the button will appear gray and if the column has no relation to a module, the button will appear like

If the source is not fixed the query will start as described here.

Settings

- To change the data shown in the query results, either click on the header of the tables, e.g. Event for that table. A window as shown below will open where you can select or deselect columns, change their headers etc. Red columns need to be filled (either by the database, the program or the user). In the Alias field you can rename the columns to your preferences. The button will show a description of the columns. For columns linked to a module, the current settings for the link will be shown in addition to the description. To display a column in the sheet use the checkbox . If a column is needed, but should be hidden, select the checkbox. Displayed columns are indicated by a yellow background while hidden columns get a light yellow background. Certain columns are required (indicated by a purple color) and can not be removed e.g. if they are involved in a link to a remote module like in the example below the columns FamilyCache and OrderCache. Columns linked to a module are indicated by a blue color.

The button allows you to include one of the tables missing in the sheet (see image below). After selection of the table, select the column(s) you want to include in the sheet as shown in the image above.

To store resp. load settings, use the resp. button. If a setting file has been corrupted click on the button to remove it and restart with factory settings. The spreadsheet will always start with the previous settings. The location where the settings are stored are set under Administration - Resources directory ... . For an introduction see a short tutorial Video starten.

 

Column width

Tutorial: Video starten

The width of the columns can be set manually (in the filter area) or automatically with a click on the button. A window will open where you can choose and set the parameters for setting the column width.

 

Adding

Tutorial: Video starten

To add new data, use the area underneath the data table. You can enter preset values that will be used for the new data. If the new data should be added to existing entries, select the corresponding row. Then click on the + field of the datarange that should be inserted. If preset values are given, all corresponding tables will be filled together with the new inserted data. Defaults for the responsibles can be set under Administration - Customize Display. If a column is linked to a remote module, the corresponding columns will be filled together with the selection of the link, so e.g. if you select a link for a taxonomic name to a DiversityTaxonNames the columns for the taxon and if available the familiy etc. will be filled as well. To remove a linked value, select it a choose Remove from the context menu (right click).

Export

Tutorial: Video starten

To export the data as a tab separated text file (UTF8), click on the button. You will be asked if you want to include the hidden columns. These are the primary keys you may need for statistic evaluations etc.

Feedback

To send a feedback to the developer of the software, create a screenshot and click on the  button. 

Details

Tutorial: Video starten

To see all details of a dataset, select the dataset in the sheet and click on the button. A window, corresponding to the main form will open, showing all data related to the selected specimen. 

 

Image

Tutorial: Video starten

If an image is present a preview will be shown in the right upper area of the window. Click on it to see the image in a separate form. The images are restricted to the first image of one source, so e.g. in the organisms sheet only the first image of the specimen linked with this organism will be shown while images of e.g. linked to none or another organism or the collection event will not be addressed. 

Jan 14, 2025

Subsections of Spreadsheets

Diversity Collection

Spreadsheet

Maps

Introduction: Video starten

For certain spreadsheets you can display the content in a map. The content will be displayed with the GIS-Editor like in the example below.

To set the symbols etc. representing the values, click on the button. A window as shown below will open, where you can set the parameters for the map. 

Transparency

For the creation of heat maps, the transparency of the symbols displayed in the map can be set to a value below 255 (= no transparency). Video starten

 

Symbols

Introduction to Symbols: Video starten

The symbols can be linked to the value within the database. A typical example would be the status of a plant, e.g. endagered, rare etc. stored as an analysis. Choose the Table where the values should be taken from. Now you can choose the column within the table. The different values will be listed and you can attribute a symbol together with the size to every listed value. In the image below, the symbols are linked to the values of a column named Last Nr for a certain analysis. 

The tables in the drop down list (see above) correspond to the content and definitions in the spreadsheets. Accordingly the values the symbols are linked to are restricted to the current content of the spreadsheet. As an alternative and in preparation for data containing other values to get the whole range of possible values you can select the source for the values from the whole database. Click on the button to select the source table. The programm will try to find the relevant data an make a proposal as shown in the image below.

If the proposal does not fit, set the source manually: In the window that will open as shown below, choose the source table for the values and click OK. (The table names in this list correspond to those in the database) 

This will open the source table as shown below. Here choose the column for a filter, e.g. AnalysisID, select the type of comparision and enter the restriction value. Now you can click on the button to restrict the values. In the example below the values were restricted to the analysis with the ID = 2. Finally select the column containing the values you need (AnalysisResult in the example below) and click OK (see below). 

Now all values from the source are listed, not only those contained in the data form the spreadsheet (see below). The button will change to and will now remove the source, to return to the values contained in the spreadsheet. If certain values should not appear in the map, choose as symbol. 

If the list does not contain a missing value, a separate control will appear at the end of the list, where you can set the symbol for missing values (see below).

The size of the symbols can be set either for every symbol or for all symbols with the button Set this size for all symbols. Another option is to link the size of the symbols to a numeric value within the data (see below). Choose the table and the column within this table containing the numeric value. Video starten

 

Colors

Introdoction to colors: Video starten

The colors can be linked to numeric values within the database. Select the table and the column where the values should be taken from. Now click on the button to add colors and the restrictions linked to the colors as shown below. 

 

Legend

Introduction to legend: Video starten

With a click on the button, you can open a window listing all symbols and colors with their attributed values (see below). In the spreadsheet window, click on the button underneath the button to open the legend. 

 

Evaluation

There are 3 types of maps available:

Map for WGS84 geography of organisms

For this map type you have to set the table and the column containing the WGS84 geography, i.e. a content like POINT(45 … )  for the organism as shown below. Every entry will be shown in the map with its exact geography.

 

Map with WGS84 coordinates

For this map type you have to set the table and the column containing the WGS84 geography, i.e. a content like POINT(45 … ) for the collection event as shown below. Every entry will be shown in the map with the symbol placed in the center of its geography.

 

Map for objects aggregated according to TK25 quadrants

Filter table / Column: For this map type all objects within a TK25 quadrant will be aggregated to one value. For the filter according to which the aggreagation is performed, you have to select the table and the column containing the combination of the TK25 identifier and the quadrant (see below).

Gazetteer for retrieval of TK25 coordinates. The coordinates for the symbols will be obtained from a gazetteer module. Please select the source as shown in the example below.

Sequence of the symbols as shown in the map: The sequence of the symbols resp. the states linked to these symbols can be set here. Use the button to add an entry at the end of the list and the button to clear the whole list. To remove a single entry from the list, just click the entry you want to remove.  

With the option Keep last valid symbol if later data are missing you can keep the last valid symbol if in the later evaluated data the correspondig values are missing.  

 

Map

To display your data in a predefined map you can set this map with a click on the button as shown below.

With the option Show details in map the tooltip in the map will display the details of the data as selected in the spreadsheet (see below). The widths in the tooltip roughly corresponds to those set in the spreadsheet. Tutorial: Video starten

 

Maps for organism geography, WGS84 coordinates of the collection event and TK25

Tutorial: Video starten

After the parameters for the map are set you can choose among 3 types of maps:

Map with WGS84 geography of the organisms

This map will show the geography of the organisms.

 

Map with WGS84 coordinates of the collection event

This map will show all entries with a WGS84 geography.

 

Map for objects aggregated according to TK25 quadrants

This map will aggregate all entries according to the TK25 quadrants as shown below.

To select the data that should be edited either use the frame (as described in GIS: Save samples  and  GIS: Settings ) or select resp. deselect single data with the mouse. Click OK to close the map and return to the spreadsheet containing only the data selected in the map for further editing. For the TK25 map the filter will be set for the TK25/Quadrant column while for the WGS84 map the filter will be set for the column IdentificationUnitID corresponding to organisms shown in the map. The column IdentificationUnitID will be shown in the spreadsheet if you use the later filter. Short tutorial: Video starten

As only one symbol and color can  be shown for every quadrant, a certain routine is used for the determination.

Color: For the color sortable values must be provided, e.g. the year or a period. The sorting will be according to the values were the highest value (e.g. the last year or period as determined by the user, see above) is preferred.

Symbol: For the symbol the sorting is determined by the user (see above).

The default routine for the determination:

  • Reduce the values for the quadrant to the first digit e.g. 2413 will be reduced to 2
  • Test every data row in the table that corresponds to the filter value (e.g. TK25 + Quadrant as determined by the user, see above).
    • The geography can not be determined - ignore this row. (The geography is determided via a gazetteer, see above)
    • The value for the color is missing - ignore this row.
    • The value for the color found in the data row is higher than the value found so far
      • Use this row to determine the color
    • The value for the color in the data row is higher than the color value associated with the symbol found so far
      • Use this row to determine the symbol
        • The row contains NO value for the symbol and the option " Keep last valid symbol if later data are missing" is NOT selected
          • Use the symbol for missing values (determined by the user, see above)
    • The value for the color in the data row is equal to the color value associated with the symbol found so far
      • The value for the symbol in the row is above the value found so far
        • Use this row to determine the symbol
  • No value for a symbol is found
    • Use the symbol for missing values (determined by the user, see above)

 

Mar 20, 2025

Diversity Collection

Collection Event

Main sectors

The image below gives you a overview of the main parts related to the collection event.

Specimens stored in a collection are gathered during a CollectionEvent. This CollectionEvent keeps for example information about the geographic locality, the habitat, the collection date. During a CollectionEvent several specimens may have been collected. To create a new event for a specimen click on the button. If a specimen has not been assigned to a CollectionEvent, you can assign the specimens to an existing event with a click on the button. If you assign the specimen to an existing event, a window will open where you can search for the events already included in the database as shown below. Choose an event and click OK to assign the specimen to this event. If you click OK without selecting any CollectionEvent, the current CollectionEvent will be removed from the CollectionSpecimen.

 

To get access to the collection event data independent of specimen select Data - Collection event… from the menu.

In the tree view the CollectionEvent is symbolized by an icon as shown below. 

 

The CollectionEvents can be organized in a hierarchy either by using CollectionEventSeries or sampling plots. If your CollectionEvents belong e.g. to an expedition, you should preferably use CollectionEventSeries for the organization.

If your samples are taken e.g. on a regular basis from permanent sampling plots, you may prefer to use the module DiversitySamplingPlots to document the geography and other details of the sampling plots and use the CollectionEvents only to document the collection date.

To edit the data of the CollectionEvent choose it in the tree view to open the detail fields as shown below. If the collection date does not correspond to a certain day, you may use the Suppl. field to enter e.g. a range or a series of dates or the T.span field to document a certain time span.

 

The text shown in the tree view is composed of the date of the CollectionEvent and the description of the locality. For each CollectionEvent you can enter several geographicallocations and properties. To see the locality according to the coordinates stored in the database you can check the Maps. For each CollectionEvent you can enter images related to this event.

If other specimens were collected during the same CollectionEvent, they will be displayed once the entire hierarchy of the EventSeries is shown. To do this click on the button in the panel on the left side of the tree. See EventSeries for further details. You can also move a specimen to another event by drag and drop.

Besides of a plain text description of the methods used during the CollectionEvent, you may insert methods as defined in the chapter Methods. Use the and buttons to add or remove methods from the list (see below)

If parameters are added to the methods after you added the method to the event, these new parameters will not automatically be available in the event method. The new parameters must be added via the Maintenance or with a click on the button. A window as shown below will open where you can select the parameters that may be added.

Data are stored in the table CollectionEvent.

Mar 19, 2025

Subsections of Event

Diversity Collection

Collection Event Series

If you need a hierarchical order of your CollectionEvents or want to organize several CollectionEvents, for example, to document expeditions, you can achieve this with a CollectionEventSeries.

For a better differentiation between events and CollectionEventSeries, there is blue text in the hierarchy as well as the editing part, and a different icon . A CollectionEventSeries can contain other CollectionEventSeries and CollectionEvents. Information about the geographic locality, properties of the collection site, date of collecting etc., is stored in the CollectionEvent. To show or hide the CollectionEventSeries, you have two options. In the panel on the left of the tree the button will show the superior EventSeries of the current CollectionEvent as shown below.

 

The button will show the entire hierarchy of the EventSeries as shown below.

 

To edit the data of an EventSeries, select it in the tree to display the detail fields as shown below.

New Event Series

To insert a new CollectionEventSeries click on the button. If there are no CollectionEventSeries so far, the CollectionEvent will be placed within the new CollectionEventSeries. If there are CollectionEventSeries present, the new CollectionEventSeries will be placed below the selected CollectionEventSeries. To assign a CollectionEvent to an existing CollectionEventSeries already available in the database, click on the button.

To move an item within the hierarchy, just drag it with the mouse to whatever position it should be placed in. Keep in mind that specimens can only be placed in CollectionEvents and CollectionEvents only in CollectionEventSeries.

Removing EventSeries

If you want to delete a CollectionEventSeries or a CollectionEvent, remove all depending CollectionEventSeries, CollectionEvents and specimens and click on the  button. A specimen can not be deleted here.

If you want to remove a CollectionEvent from the current CollectionEventSeries, click on the button.

Moving into Event Series

If you want to transfer the data selected in the query results into a CollectionEventSeries, choose Data - Transfer - to event series… from the menu. If only a part of the items in the query results is selected, you will be asked whether all data in the list should be transferred. To transfer only the selected data, click NO. To transfer the entire list, click YES. Note: Only samples that are already part of a collection event can be transferred. Items without a collection event will not be included.

Images

To display the images, choose  Series images   in the header menu. To add images to a CollectionEventSeries, click the button. To remove an image, use the button. With the button you can switch to a new Chromium-based browser for the display of images. The presence of images in an event series is indicated by a yellow background on the lower of the buttons in the upper right corner. These buttons may be used as a shortcut to display the images .

To zoom a sector of the image, simply move the mouse over the image. A red square will indicate the zoomed area. To set the size of the image to the original resolution, click on the button. To adapt the size of the image to the available space in the form, click on the button. To change the orientation of the image use the appropriate buttons ( flip horizontally, flip vertically, rotate right, rotate left). To view the image in a separate form, click on the button. If the image should not be published, e.g., on the internet, enter any reason in the Withhold reason field. Besides images, you can also store other media

Descriptors

To add descriptors to an event series, you must first add descriptor types. Choose Administration - Enumerations - Event series - Desprictor from the menu, or click the button in the descriptor section. A window will open where you can manage the available descriptor types. Use the resp. buttons to add or remove a descriptor to the event series.

Hierarchy

If you want to change to another specimen listed in the CollectionEventSeries, select it in the hierarchy and click on the  button.

The current specimen, together with the event and all superior CollectionEventSeries will be highlighted.

Geography

The CollectionEventSeries can contain a geographical object (using WGS84) such as a point, a line, an area, etc. To edit or show the geographical object related to the CollectionEventSeries, either click on the Geography button in the details next to the notes field select the Map in the header to show the maps and use the GIS editor .

Storage

The data of the CollectionEventSeries is stored in the table CollectionEventSeries.

Apr 22, 2025

Diversity Collection

Event Images

The specimens stored in a collection are gathered during a CollectionEvent. To insert an image related to a CollectionEvent, select the event image in the header menu to display the images of the collection event. In case the event images are not displayed, a yellow (image(s) present) resp. gray (no image) backgroud of the tiny buttons at the upper right corner indicates the presence of images .

In the list (see below) click on the  button. If you want to delete an image, click on the  button.  For more details see the section Images.

With the button you can change to a new chromium based browser for the display of images.

If for any reason an image should not be published i.e. shown on a website, enter the reason in the field Withholding reason. Only images where this field is empty will be shown e.g. on websites. The EXIF data are extracted from the image during the import, e.g. via DiversityMobile.

Data is stored in the table CollectionEventImage .

Mar 20, 2025

Diversity Collection

Geography

Details about the type can be entered in the area “Geography”.

The geographical distribution of the type specimen according to the protologue can be typed in the field Locality of the area Typification in DiversityTaxonNames. In the area Geography names according to a standard can be entered as a list as shown above. To remove an entry from the list click on the button. To add an entry click on the button. A form will open where you can choose geographical places from the module DiversityGazetteer. To open the link to the module, click on the  button and search for the region as described in the chapter Module relatedentry.

 

The data of the geography of the taxa are stored in DiversityTaxonNames in table TaxonGeography.

Mar 19, 2025

Diversity Collection

Maps of samples in the database

If there are WGS84 coordinates available for your collection site, an event series or single organisms, you can use GoogleMaps to display these locations.

To use this service you need access to the internet. Select the Map for display in the header area to show the maps. Here you can display maps of CollectionEventSeries, CollectionEvent, Organism as well as Distribution maps. To display the maps you can either use the browser, the web viewer, the GIS viewer or the GIS editor. By default the map will show the location of the CollectionEvent using the browser as shown below.

The two options browser and web viewer in principle provide the same function, but rely on different controls. Due to incompatiblities between controls and the google web API you may have to test both to display a map.

For the CollectionEventSeries, the CollectionEvent or the Organism you can use any geographical object like points, lines, areas, etc. to describe the location. The browser will always display these objects as points (see left image below) whereas with the GIS editor you can see and edit the real objects (see right image below).

 

The data of the geographical objects is stored in the table CollectionEventSeries for the collection event series, the table CollectionEventLocalisation for the collection event and the table IdentificationUnitGeoAnalysis for the organisms.

Mar 20, 2025

Diversity Collection

Distribution maps

If WGS84 coordinates are available for your collection sites, you can create distribution maps of your samples in the database. To use this service you need access to the internet. Choose Map in the header to show the maps. To display distribution maps choose the appropriate option from the first drop down list in the mapscontrol.

To add data sets to the distribution search for the data sets you want to see in the map, mark them in the list (either use the button to mark all data sets, mark a list/single data sets or check the option for the distribution map) and click the button. To display the map click on the button. The displayed localities in the map will not change until you add new localities or click the button to start with a new distribution map. If you want to set different icons for the positions of different series of your samples, set the style of the icon (symbol, color, size etc.) in the menu before you add them to the distribution list.

To show a distribution map of all the specimens found in your query as shown below, select the option Distribution from the drop down menu. For the display in the map you can choose either the Browser (see below) or the GIS-Editor. In the browser all objects will be shown with their center coordinates and the number of specimens that can be depicted is limited, thus, it may be necessary to restrict your query. With the GIS editor all objects will be shown with their whole geography (e.g. an area will not be reduced to its central coordinates) and there is no limit to the number. Furthermore you can vary the symbols for different groups.

 

The upper distribution map is restricted to coordinates of the collection event . If you want to include coordinates from the organisms , choose the distribution map including organisms . For the positions of the organisms in this map, the ID of the organism ( = IdentificationUnitID, 528577 in example below) is shown as identifier and the last identification ( = LastIdentificationCache) as display text (Ajuga reptans L. in example below).

If you want to restrict the display to the organisms, click on the  button to open the window for custimizing the display (see below) and deselect all localisation systems for the collection event.

While in the GIS tool the objects are represented with their real geography (see above), in the browser every object is reduced to a single point. For an introduction see a short tutorial .

 

Jan 14, 2025

Diversity Collection

Sampling Plots

If your samples are collected at constant sampling plots, you may use the module DiversitySamplingPots to describe said SamplingPlots. For a better differentiation between events and the SamplingPlots there is a brown text in the hierarchy as well as a different icon . A SamplingPlot can contain other SamplingPlots and CollectionEvents. Information about the geographic locality and properties of the collection site can be stored in the SamplingPlot, while the collecting date must be stored in the CollectionEvent. To show or hide the SamplingPlots you have two options. In the panel on the left of the tree the button will show the superior SamplingPlots of the current CollectionEvent as shown below.

 

The button will show the entire hierarchy of the SamplingPlots as shown below.

 

If you select a SamplingPlot in the hierarchy, two buttons will appear in the bar to the left of the tree. With the button will show the entire hierarchy of the SamplingPlots as shown below.> button you can retrieve a taxon list for the SamplingPlot. With the button you can retrieve a summary of the information on a SamplingPlot (see image below).

To edit the data of a SamplingPlot please use the module DiversitySamplingPlots.

The link to the module DiversitySamplingPlots is stored in the table CollectionEventLocalisation.

Mar 20, 2025

Diversity Collection

Habitats and properties of the collection site

For the description of the habitat select the CollectionEvent or an existing collection site property . The description is entered in the field Habitat (see below).

To enter a new property of the collection site select the CollectionEvent or an existing collection site property . Then choose the type of the property you wish to enter from the drop-down menu as shown below. Only items which are not already set for a CollectionEvent will appear in the list. You can customize the selection of visible items.

 

The list is dependent on the availability of terminologies for site descriptions. Details for the property can be entered if you choose the item in the hierarchy. The person responsible for the entry as well as notes can be entered in the corresponding fields as shown below.

 

To delete entries use the  button. You can enter a value by either typing the name of the collection site property or by selection from the module DiversityScientificTerms. To search for properties from this module click on the  button. The current user’s name will be inserted as the responsible user. You may change this by either typing or through selection from the module DiversityAgents.

As an alternative to the button, you may select the property via a chart with a click on the button. A window as shown below will open. To select an item from the chart click no the entry you want to select and close the window with a click on the OK button.

The data concerning the habitats is stored in the table CollectionEventProperty.

 

Administration of properties (resp. terminologies)

To administrate the available properties of collection sites, choose Administration - Site properties… from the menu. A window as shown below will open, where you can delete existing site properties and add new site properties.

To add new properties, click on the button, select the new entry in the list and choose the appropriate parsing method.

Properties should be linked to the module DiversityScientificTerms. To link the property to the module, click on the  button. A window as shown below will open, where you can search for the terminology provided by the module. Please keep in mind, that the ID of the terminology will be used for the new entry and that this ID must be unique. Turn to your administrator if any difficulties occur.

After choosing the terminology from DiversityScientificTerms, the new property will be displayed as shown below..

 

Mar 19, 2025

Diversity Collection

Specimens

Main sectors

The image below gives you an overview of the main sectors related to the collectiom specimen.

Specimens are the entities stored in a collection. For handling the data use the appropriate buttons (new specimen , copy , delete). See the Data section for further details. Directly attached to the specimen is the data about accession, label, exsiccatae, notes, reference and the availability. A specimen may be composed of several units. Any problems concerning the specimen should be entered into the problems field.

The header of the main window shows some important parameters for the selected specimen. On the left side the accession number is shown. In the center you find the last identification of the main IdentificationUnit according to the display order. The [http:/] link shows the public address of the selected item. Click on it to see the public available values. The next field shows the internal IDs (field CollectionSpecimenID in table CollectionSpecimen and CollectionEventID in table CollectionEvent) and the Versions for the specimen and the CollectionEvent. For details about the version of a data set see the Version topic. The availability of a specimen can be changed by entering an appropriate reason in the field Withholding reason.

If the specimen is a type, the header will show the type state and the identification connected with the type (see below).

To inspect the history of a specimen click on the button. For further details see the History section.

Top area

In the header menu you can determine what is shown in the upper part of the window. Choose on of the options: will show the printing area, images for the specimen, the images for the  collection event and the images of the collection event series. will show the maps. To hide the upper part, select Hide.

The tiny buttons in the upper right corner provide a shortcut to the image displays and indicate the existence of images by a yellow background

The data are stored in the table CollectionSpecimen .

Mar 20, 2025

Subsections of Specimen

Diversity Collection

Data handling

The controls for handling data sets in the database are located in the left upper part of the window as shown in the image below. A step-by-step introduction for the creation of new data sets is provided in the Tutorial.

  • To SAVE the changes in a data set click on the button. If you select another data set from the list of results, the current changes will be saved automatically.
  • To UNDO the changes in a data set, click on the button. This will recover the original data unless the changes have been saved or changes were done in certain tables or hierarchies were the data must be stored to display the hierarchy.
  • To create a NEW entry in the database click on the button. This will create a new record of a specimen and show it in the list of results.
  • To COPY the data of a specimen record choose it from the list and click on the button. For further details, see the chapter Copy specimen.
  • - To DELETE a data set you must have the proper rights (e.g. be a member of the group Administator). Select the dataset you want to delete it in the list and click on the button.

To delete all selected specimen choose Data - Remove specimen... from the menu. A window as shown below will open where you can choose if the data from the log and the collection events should be included in the removal.

Mar 19, 2025

Diversity Collection

Copy specimen

For an introduction see a short tutorial . To copy specimen click on the button. A window will open where you can choose several options for your copies.

In the first tab choose in which way the CollectionEvent - if present - for the new data sets should be created (see image below). In the first option the new specimen will be located in the same collection event as the original dataset. In the second option a new collection event copied from the original will be created while in the last option the data in the collection event will be ignored altogether. 

 

 

In the Accession number tab you can search for or enter the accession number you wish to use for your new data set (see below).

 

In the Projects tab you can add additional projects for you new datasets (see below).

 

In the Relations tab you can add relations between the original dataset and the copy in either direction (see below).

 

In the Include... tab you can choose the ranges of data that should be included in the copy (see below). Click on the All or None buttons to select all resp. none of the tables.

 

In the Number of copies tab you can specify the number of copies. If you checked Create an accession number for the new data set, the program will list all accession numbers which will be created (see below). After you changed the number of copies, click on the button to refresh the list.

 If you do not wish to create new accession numbers for the copies the list will not be shown (see below).

 

Copy event

If only the event data should be copied and a selected specimen should be transferred into the new event you can choose the last option (see below). This option is only available for events containing several specimen.

 

 

Jan 23, 2025

Diversity Collection

Tree for the specimen

The upper tree in the window provides an overview for all the data linked with the specimen. With the buttons in the left panel you may hide or show certain nodes in the tree. If for example you do not wish to see the collectors, simply click on the button and they will be hidden in the tree. The button will change to a grey version and the background will turn yellow to show that there is hidden data of the collectors.

If the CollectionEvent is part of a CollectionEventSeries, a drop-down button will appear where you may select between 3 states:

  • = show the parent EventSeries
  • = show the entire hierarchy of the EventSeries
  •     = hide the EventSeries
  •     = hide the EventSeries

If the CollectionEvent is linked to a SamplingPlot, a drop-down button will appear where you may select between 3 states:

  • = show the parent SamplingPlots
  • = show the entire hierarchy of the SamplingPlots
  • = hide the SamplingPlots
  •     = hide the SamplingPlots

If both options are available, you may choose between the CollectionEventSeries or the SamplingPlot hierarchy. If the entire hierarchy for the EventSeries or the SamplingPlots is displayed, the items not included in the current data set will be displayed with gray icons, e.g. . To change to one of these use the button. For the Events, the EventSeries, the Plots and the Specimen a button will appear which will give you access to a taxon list of the selected item.

The panel on the right side of the tree is used for editing the data, for example the button will insert a new collector. For further details see the special sections. For data with [Read only] access these panels are disabled except the button for adding annotations

Dec 7, 2024

Diversity Collection

Display order

Tutorial: Video starten

The display order defines the sequence in which the units within this specimen will appear on e.g. a label. The first unit will be printed in the header of the label, others are included in the text below. You can change the display order by using the   buttons. If a unit should not appear on the label, transfer it to the hide list using the  button. The  button returns it to the list to be shown on a label. The first unit can not be transferred to the hide list.

The upper section shows the display orders of the units within the whole specimen. The lower section shows the display orders in a specimen part. If you print a label without reference to a part, the display order for the entire specimen as in the upper section will be used. This part is also accessible if you click on the button in the right panel of the upper tree, which will appear if you e.g. select the specimen.     

If you print a label with reference to a part, the display order for the part as in the lower section will be used. This area will be shown when you select a specimen part in the lower tree. In addition to the display order you can specify whether an organism is present in a selected part of a specimen. With the button you can transfer all organisms into the part.

To change the sequence of the parts according to e.g. the name instead of setting all entries one by one, you may choose among the options shown in the image below (Name, Identifier, ID).

 

 

Jan 14, 2025

Diversity Collection

Accession

The accession of a specimen in a collection is documented with its accession number and the date of the accession if available.

If the specimen was received from another collection, this may be documented with the name of the depositor and the number in the original collection (Dep.Nr).

If the current project (= as selected in the query list) contains a duplicate of the accession number, a button will appear. This gives you the opportunity to switch to the specimen with the duplicate accession number.

If a new specimen is entered you can use the button to search for the next free accession number. A window will open as shown below, where you can begin the search. The search will start with the number you provide as a starting point. 

 

The system will try to find the next free number based on the accession numbers available in the database. As accession numbers can be assigned to a specimen as well as a part of a specimen, you have the option to include accession numbers in both places in the query. Click OK to use the recommended number for the specimen.

Data concerning the accession and deposition are stored in the table CollectionSpecimen.

Mar 20, 2025

Diversity Collection

Specimen image

To see the specimen images select the specimen image in the header menu. Each specimen may be documented with several images. The images are stored as their path, either locally or provided by a server. To enter a new image click on the button. For more details see the section Images.

To delete an image select it from the list and click on the button (see below).

To change the sequence of the images, use the resp. buttons to change the position of the selected image. To adapt the sequence of the whole list, you can select one of the options offered when you click on the button: Ordering ascending resp. descending by the name (= URI) or the creation date of the images. For a short introduction see the tutorial Video starten.

With the button you can change to a new chromium based browser for the display of images.

To change the image sequence for a whole project, use the functionality within maintenance maintenance.

To document the relation of an image to an organism or a part of the specimen choose the corresponding entries from the drop-down lists Organisms: and/or Part:.

To restrict the displayed images to either images which are related to a certain part or a certain organism within the specimen, choose e.g. the organism in the tree. If the selected organism is related to any image the button (see below) will change to .  

Click on the button to restrict the images displayed in the list to those, which are related to e.g. the selected organism. The button will receive a red background to remind you of the restriction. Next to the image list a button will appear which enables you to show all images again.

The data is stored in the table CollectionSpecimenImage.

Mar 19, 2025

Diversity Collection

Projects

Setting of projects Effect on specimen within Projects
Full access to all projects User can edit data
Any project read only User can read data
Any project locked No user can edit data
No access to project User cannot see data

Every CollectionSpecimen may be assigned to any number of projects. To assign a specimen to a project click on the button. To add a project where you have no access to, use the button. To remove a specimen from a project select the project from the list and click on the button.

If there are projects, to which you have [no access] to, these will be listed in a separate list at the top as shown below.

 

Projects, to which you have Read only access will be listed in a separate list at the top as shown below.

Data from Read only projects can be seen but not edited. Only Annotations can be added (see image below).

To transfer all selected specimen into an additional project choose Data → Transfer → To project... from the menu. A window will open where you can select the project to which the specimen should be added.

To remove all selected specimen from an additional project choose Data → Remove from project... from the menu. A window will open where you can select the project from which the specimen should be removed. The last project in which a specimen is placed can not be removed.

 

The data are stored in the table CollectionProject.

Details of the projects within the DiversityWorkbench are stored in the database DiversityProjects. To access further information on a project click on the button. To edit details in projects you require the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you may use the synchronize function in the useradministration window as shown below. If DiversityProjects is not available, you may create a new project by clicking the button. If DiversityProjects is available, use the synchronize function .

To import new projects from the DiversityProjects, select Administration - Projects from the menu. A window as below will open where the available projects are restricted to the type "Collection" . (Short introduction: Video starten)

 

To select a project of a different type or missing type, deselect the restriction (see below).

The present project list details about the projects available in DiversityCollection.

the diagram below shows all tables with direct relations to the project tables. For more details see the sections Analysis, Processing and Image description.

 

Mar 20, 2025

Diversity Collection

Notes and problems

To enter notes or problems connected with the specimen select it in the hierarchy. The data form will open the corresponding fields. The Original notes are the notes found on the label of the specimen, made by the original collector or from a later revision. Additional notes are those made by the editor of the specimen record, e. g. doubtful identification or locality.

In the Problems area enter the description of a problem which occurred during data editing. Typically these entries should be deleted after help has been obtained. Do not enter scientific problems here. Use Additional notes for such permanent problems!

The data is stored in the table CollectionSpecimen.

For notes on data created by users with no permission for editing see the chapter Annotation

Mar 20, 2025

Diversity Collection

Organisms And Identifications

Main sectors

The image below gives you an overview of the main sectors related to the organisms.

Each specimen can contain several organisms and each organism may have been identified several times as shown in the image below.

 

To see the list of organisms within a Specimen, CollectionEvent, EventSeries or SamplingPlot use the taxon list function.

Jan 14, 2025

Subsections of Organisms

Diversity Collection

Organisms

(= Identification Units)

The items or organisms in one CollectionSpecimen are regarded as IdentificationUnits. One specimen can contain several IdentificationUnits e.g. an insect (1) feeding on a fungus (2) growing as a parasite on a plant (3). To add a new organism use the drop-down menu as shown below to select the taxonomic group to which the new organism belongs to.

 

To specify the taxonomic groups that are shown in the drop-down menu select Administration - Customize display ... from the menu.

The organisms of the specimen are shown in the tree. To edit the relations between the organisms simply drag and drop. In case of a shortcut in the hierarchy you will be asked to select the start of the hierarchy as described in the video: Video starten. The name of the organism under which the specimen is stored in the collection is [underlined]. To delete an organism select it in the tree and click on the button.

To enter details about one of the organisms like e.g. gender or life stage, select it in the tree. The fields for the details of this organism will be displayed in the right area of the window as shown below.

If the Identification unit is e.g. not a complete organism you can enter a description for this IdentificationUnit. Either type you description or choose one of the predefined descriptions via combobox or hierarchy: Use the combobox to select a description as found for the same taxonomic group in the database or use the hierarchy-selector to select a predefined description. An additional description can be entered for an IdentificationUnit within part of a CollectionSpecimen.

Taxonomic hierarchy - family and order

The entries for the family and the order of the taxon are either set when linking to a taxonomic database or set manually when no link to a taxonomic database exists.

 

If no link to a taxonomic database exists you may enter the family and the order after clicking on the button. To transfer these entries to other specimens with the same genus use the maintenance functions as described under Maintenance - family andorder.

Parts of units

If a unit contains parts which have to be documented, you can do this by setting the relation to the substrate to "Part of".

 

In the tree the background of a part will be grey as shown below for the unit-tree und the tree depicting the storage of a sample. The name of the part will correspond to the identifier set for this part. The icon will correspond to the description of the part provided you choose one of the preset options contained in the drop-down list. You may of course enter any description for the unit. A unit that is part of another unit can not get an identification. Identifications are restricted to the main unit.

  

 

Parent-child relations

If a unit is a genetic child of a parent, choose "Child of" as type of the relation. If there are 2 parents like mother and father that you want to document, click on the button next to the relation type. A window will open where you can choose among the organisms (= units) in your sample. The second parent will be indicated with the symbol in the tree (see below).

For details about exsiccatal series and analysis see the related topics. You can sort your IdentificationUnits e.g. for display on a label with the displayorder button. Each IdentificationUnit can have several identifications.

With the template you can define and copy predefined values into the data (see chapter Template).  

If there are images which are related to the current organism, the button for the restriction of the images will be enabled ( ). Click on it to restrict the images to this organism. The button will get a red background to remind you about the restriction and in the image list a button will appear that enables you to show all images.

Non biological units

Non biological units like soil, rock or mineral do not have biology related characters like family or sex. These are therefore not displayed for these groups. 

The data for the organisms and non biological units are stored in the table IdentificationUnit.

 

Mar 20, 2025

Diversity Collection

Taxonomic Group

The organisms and corresponding objects stored in the database are organized in taxonomic groups to facilitate the recognition in multi organism samples and to enable a specific design for the analysis where e.g. plants differ in recorded measurements from mammals. The taxonomic groups are roughly orientated on the taxonomy but are not meant to replace the taxonomy for which there are other possibilities for entry. The list of taxonomic groups visible for the creation of new entries may be restricted as described in the chapter about the customization.

To administrate the taxonomic groups, choose Administration - Taxonomic groups... from the menu. A window as shown below will open. 

To add resp. remove a taxonomic group use the resp. button. To set the superior taxonomic group use the button. With the button you can set a symbol for the taxonomic group. Please keep in mind, that this will be converted into a 16 x 16 size icon. In the lower part of the window, you can add and edit translations for display texts, abbreviations etc. for all contexts available.

If a taxonomic group has been disabled it will not appear in the lists for the user and will be displayed without an image in with grey text color in the tree (see below). After reenabling a group you have to reopen the form to see the icon for the group.

At the base of the window, the projects that are restricted to an entry are listed (see Video starten). To administrate the projects that should restrict the available taxonomic groups, choose Administration - Enumerations - Project - Taxonomic group... from the menu. A window as shown below will open. If a project is restricted, the client settings will be ignored (see chapter Customize). 

To add resp. remove a material category for a project use the resp. button.

The non-biological taxonomic groups like soil, rock or mineral will for an identification not be linked to DiversityTaxonNames but to DiversityScientificTerms (see image below and the short tutorial Video starten ). If you add a new taxonomic group anything outside the predefined groups animal, alga, bacterium, bryophyte, fungus, gall, lichen, myxomycete, plant or virus will be regarded as non-biological. The sources for direct access using the buttons are linked to the taxonomic groups (see Settings).

Apr 3, 2025

Diversity Collection

Retrieval Type

The ways the data about organisms and corresponding objects stored in the database are retrieved are documented as retrieval type.

To administrate the retrieval types, choose Administration - Retrieval types... from the menu. A window as shown below will open. 

To add resp. remove a retrieval type use the resp. button. To set the superior type use the button. 

Jul 3, 2024

Diversity Collection

Analysis

The organisms in a specimen can be analysed by analysis types defined in the database. In the tree the analysis entries are symbolized with an icon. Only the types of analysis that were assigned to the group of the organism can be selected. An analysis always refers to an organism and may also refer to a part of a specimen. An analysis that refers to a part of a specimen will be shown in the tree for the parts as shown in the examples below.

To show or hide the analysis items in the tree use the button in the left panel. This button has 3 states. In the default state the analysis entries will be shown as above. If you click a second time it will change to the hierarchy mode and the entries will appear as shown in the tree below. The last state will hide the entries.

To insert a new analysis to an organism select the organism in the upper tree. Then select the type of the analysis from the drop down list as shown below.

To delete an analysis, select it in the tree and use the button in the panel on the left. To edit the details of an analysis, select it in the tree and enter data into the fields as shown below. To enter or inspect an URI given for a single analysis, click on the button.

If an analysis refers to a part of the specimen, you can document this by choosing the respective part from the list (see field Part above). The analysis will then be shown in the tree for the parts of the specimen as well. Alternatively you may directly choose the organism in the part tree and create the analysis for this part of the organism in the part tree. If you used any tools defined in the toolsection, you can include the usage of these tools.

In case the measurement unit of the analysis set to DNA (see below) ... 

... the Result is edited as shown below.

A click on the button opens a separate window (see below) with additional options for editing the sequence.

 

Administration

If you require further information about an analysis click on the button. A window for the analysis administration will open. If you have the proper rights you can edit the analysis types used in your collection as shown below. This window is also accessible via the menu entry Administration - Analysis...

For the import and export of data it is sometimes necessary to know the IDs of the analysis types. To see the IDs, click on the [ ID] button to display them as shown in the image below.

The types of an analysis are restricted by the taxonomic group of the organism or object to be analysed and from the projects. You may edit the list of taxonomic groups resp. projects, which can use a certain analysis, using the and button. To add all used taxonomic groups resp. projects, you can use the buttons. For details about handling data see the data section. If you add a taxonomic group or a project to an analysis, all children of this analysis will be available for these taxonomic groups resp. projects as well (see image below). Thus, in the example above it is sufficient to enter the taxonomic group and the project in the analysis Mammals to have access to all analysis within this superior analysis as shown in the tree. The different types of analysis are organized in a hierarchy. To organize. Some of the entries may only serve for structuring purposes (e.g. Mammals as shown above) and should not be used to document the analysis of the specimen. To ensure this, check the checkbox [Only hierarchy]

There are 3 states for result lists in the main form. (1) No result list will be generated if a measurement unit is defined, for example if you specify "mm" as the measurement unit. (2) If no measurement unit is defined, the program will collect all values given so far and present these values as a list. (3) Some types of analysis need categorized values. Enter these values together with their description in the Result list as shown below using the and buttons respectively. To show values different from the entries in the Result column change the entries in the Display text column.

 

If you want to access or inspect an URI given for an analysis type, click on the button. The URI related to the analysis will then be displayed in the window below.

Besides of a plain text description of the analysis, you may insert methods as defined in the chapter Methods. Use the and buttons to add or remove methods from the list (see below). The added methods will be marked with sequential number (see Mark.: ... ) to allow several methods of the same type.

Every method may have several parameters that will automatically be available to take your values. If the definitions of the parameters have been changed, you may add missing parameters with the button. A window as shown below will open where you can select the missing parameters you want to add.

To view the history of a dataset, click on the button. A window with the history will open. For more details see the section History.

Mar 20, 2025

Diversity Collection

Geography of organisms

The geographical position of organisms (using WGS84) can be recorded along with the date, for example, to document migration patterns or the distribution of an organism. In the tree, the geographical entries are symbolised by an icon, as shown below.

To display the corresponding map, activate Maps and click the button. To edit an existing geographical entry, use the GIS editor. If you are adding a new geographical position and existing entries are already shown on the map, remove them from the map before inserting the new location.

Apr 21, 2025

Diversity Collection

Identification

Each organism or unit may have been identified several times. The identifications are listed in the tree under the organism as shown in the image below. To create a new identification choose the organism from the tree and click on the icon. The last identification will always be taken as the valid one and set at the top of the list. To insert an older identification at the base of the list click on the icon.

 

To hide / show the identifications in the tree click on the icon on the right panel next to the tree. To enter a confirmation of an identification choose it in the tree and then click on the button. To move an identification to the end or the start of the list use the or button respectively. To delete an identification select it in the tree and click the  button. To enter details for an identification choose it in the tree. You can then enter the details in the form opening on the right side of the tree as shown below.

 

The taxonomic name of an organism can be selected from either the names already available in DiversityCollection or from the module DiversityTaxonNames. To choose from the local names type the beginning of the name and click on the drop-down button  to get a list of available names. You can use wildcards according to SQL.

To select a taxonomic name from an external database click on the button. A window will open where you can search for a taxonomic name. For taxonomic names provided by the module DiversityTaxonNames you can use a shortcut. Click on the button to set the source in the window that will open. After the source is set, the pin and drop-down box will change their colors as shown below to indicate that the taxonomic names are not longer derived from the content in DiversityCollection but from the selected DiversityTaxonNames database.

The links will be set separate for every taxonomic group and may be changed at any time with a click on the button. To release the link to the remote database, click on the  button and than select Cancel in the window where you select the database. The pin will change to and the data will again be derived from the local values in DiversityCollection.

For identifications linked to a DiversityTaxonNames database you may activate the Show accepted names option. Accepted names will then be shown with a green color while for synonyms the accepted name will be displayed above the current name (see below).

 

Non biological units

Non biological units like soil, rock or mineral do not have biology related information like a qualifier or a type status. These are therefore not displayed for these groups. Furthermore the source for the names is not DiversityTaxonNames but DiversityScientificTerms (see a short tutorial Video starten, ). If the source for a non biological unit is set to a DiversityScientificTerms database (see above ) a button will appear. With a click on this button you can select the term from a chart as shown below.

 

In the database the data for the identification is stored in the table Identification.

Mar 20, 2025

Diversity Collection

Supplementary (dependent) identification

For an identification of a non biological unit with the source DiveristyScientificTerms you may add a supplementary identification . The availability of this option depends on the first identification. For example a geological sample with the identification "Basanit" may get supplementary identifications like "Glasige Matrix" of the type "Zement/Matrix" and "Porphyrisch" of the type "Relative Korngrösse". The available supplementary types are defined in the module DiversityScientificTerms. For further information about dependencies among terms please consult the manual of DiversityScientificTerms.

To insert a supplementary identification related to DiversityScientificTerms click on the button. A window as shown below will open with the database set according to the main identification and the available term restricted to those as defined as dependent to the selected type of the main identification as defined in the DiversityScientificTerms database.

 

The type of the supplemental name is included in front of the supplementary name as shown below and a type can be given several times to indicate ranges or distinct items.

 

Jul 3, 2024

Diversity Collection

Taxon List

Tutorial: Video starten

To see the list of organisms within a Specimen , CollectionEvent , EventSeries or SamplingPlot click on the button which will appear, if you select one of the corresponding items in the tree (see below).

A window will open as shown below where you can gather additional information stored in the module DiversityTaxonNames. You may include the sex and the sum of the number of units as stored in table IdenticationUnit or the number based on the organisms in the list.

To retrieve information stored in the module DiversityTaxonNames for names which are linked to this module select the taxonomic group of the organism. Then select the option Include information from taxonomic lists. A combobox will appear where you may select the taxonomic database. Next, select the project in the combobox and finally the analysis. After all options are selected, click the button to refresh the data. With the From and Until option you can restrict the result depending on the collection date. To export the results in a tab-separated list use the button.

Jul 3, 2024

Diversity Collection

Parts

Storage and trees for the parts of the specimen

Main sectors

The image below gives you an overview of the main sectors related to the organisms.

In the tree at the base of the window the parts of the specimen with their related data are shown. This tree is only shown when parts are present. To insert parts when the tree is hidden use the button and follow the upcoming dialogs. This tree depicts the parts either in accordance to their relation to each other in the specimen tree (click on the icon in the panel on the left) ...

 

... or depending on the collections where the parts are stored (click on the icon in the panel on the left).

 

With the buttons in the left panel you may hide or show certain nodes in the tree. If e.g. you do not wish to see the processings, simply click on the button and they will be hidden in the tree. The button will change to a grey version and the background will turn yellow, to show you that there is hidden data of the processings.

The panel on the right of the tree is for editing the data, for example the button will insert a new transaction. For data with [Read only] access these panels are disabled except the button for adding annotations . For further details see the sections Transaction and Processing.

Jan 14, 2025

Subsections of Storage

Diversity Collection

Part

Parts of the specimen

A specimen can contain several parts which may be stored in several collections. These parts may represent different material categories, e.g. herbarium sheets, microscopic slides etc. The parts are shown in the part tree under the main tree. This tree depicts the parts either in accordance to their relation to each other in the specimen tree (click on the icon in the panel on the left) - see first image below - or in relation to the collections where the parts are stored (click on the icon in the panel on the left) - see second image below. Here the two parts of the specimen are located in two collections. To add a new part use the drop-down field in the panel on the right of the tree and choose the material category of the new part. The material categories which appear in this list can be customized. You can set the a default collection for new parts. If the default collection is not set, you will be asked to name the collection of the new part. If the part is derived from another part, select this in the tree before creating the new part. The new part will then be added as a child of the old part. You can later edit these relations by drag & drop. If you wish to create a copy of a part, use the button in the panel on the right side of the tree. To insert parts when the tree is hidden use the button and follow the upcoming dialogs. As another option you can transfer all specimens in the result list of a query via the menu Data - Transfer - To collection ... into a collection. Please keep in mind that next to adding part existing part will be transferred to the selected collection as well. Video starten

To see the whole content of a collection, click on the button. All specimens within the collections will be listed as shown below with e.g. their accession number, accession number of the part, storage location, collection date and/or locality as set in Customize Video starten

If an organism is present in a part of the specimen, it will be shown in the tree. To edit its presence select the specimen part in the tree and edit the Display order as shown below.

In the example above, all organisms are present in the specimen. However, the fungus Cystotheca lanestris was chosen not to appear on the label and was transferred to the Hide list. This is symbolized by a grey icon in the tree. You may enter a description for an organism as a whole or for the organism within a certain part. The slide, symbolized by the icon, was created from the sample. Thus, in the specimen tree it is shown as a child of the specimen symbolized by the icon. Concerning the organisms only the fungus Arthrocladiella is found on the slide. Thus, in the tree it is the only organism shown as child of the slide. In the display order the two other organisms appear in the Units not in part list (see below).

To move the organisms between the lists use the > and < buttons. In the list Show in label you may change the sequence of the organisms with the and buttons in the panel at the base of the list. The organism at the top will be the one taken as the main organism, e.g. for printing a label.

To see changes of the stock of the part click on the button . A window will open listing all previous volumns together unit, the date and the responsible user.

To change the sequence of the parts according to e.g. the name instead of setting all entries one by one, you may choose among the options shown in the image below (Name, Identifier, ID).

To edit the details of a part select it in the tree to open the fields as shown below.

The identifier, e.g. the taxonomic name under which the specimen can be found in the collection is entered in the field Storage location. You can search for this entry in the query.

With the template you can define and copy predefined values into the data (see chapter Template).  

To search for a free accession number use the button (see chapter Accession). To enter the storage location you may use the drop-down button to select from e.g. the identifications within the specimen. The source for the list can be specified under Administration - Customize display ... (see below). 

The drop-down button for the Notes will provide you with a list of all entries in this field, filtered with your entry in the text field. You may use wildcards like "%" or "_" (see Wildcards).

In the collection tree, the specimens are shown with their dependence upon each other based on their location in Collections. To get information about a collection simply select it in the tree. If you have the required rights, you may use the button to open the administration of the collections. This form is accessible under the menu entry Administration - Collections... as well.

The material category of a specimen part is indicated by the icon in the hierarchy.

Here some examples:

bones: bones or skeleton from vertebrates
cultures: living cultures of organisms
drawing: original line or color drawing
herbarium sheets: capsules or sheets as stored in a botanical collection
icons: icons, images etc. stored in a botanical collection
micr. slide: glass plate with sections of specimen for microscopic studies
specimen: specimen stored in a collection\

Specimens can be included in a transaction. Every stored part of a specimen may be treated with several processings.

If there are images which are related to the current part, the button for the restriction of the images will be enabled ( ). Click on it to restrict the images to this part. The button will receive a red background    to remind you of the restriction and in the image list a button will appear which enables you to show all images.

To edit the parts of the specimens in a table see the chapter Grid forparts, use the Table editor for the Part table or the Part sheet from the Spreadsheets.

The data is stored in the table CollectionSpecimenPart.

Mar 20, 2025

Diversity Collection

Parts

Material categories

The objects stored in a collection is organized in material categories to facilitate the recognition of specimen containing diverse materials and to enable a specific design for the processing where e.g. bones differ in treatment from DNA samples. The list of material categories visible for the creation of new entries may be restricted as described in the chapter about the customization.

To administrate the material categories, choose Administration - Material categories... from the menu. A window as shown below will open. 

To add resp. remove a material category use the resp. button. To set the superior material category use the button. With the button you can set a symbol for the material category. Please keep in mind, that this will be converted into a 16 x 16 size icon with black regarded as background and translated to transparent Video starten. For the translations for display texts, abbreviations etc. please see the chapter about database description.

At the base of the window, the projects that are restricted to an entry are listed (see Video starten). To administrate the projects that should restrict the available material category choose Administration - Enumerations - Project - Material category... from the menu. A window as shown below will open.  If a project is restricted, the client settings will be ignored (see chapter Customize).

To add resp. remove a material category for a project use the resp. button.

To add a more detailed description of a part, please use the Descriptions of specimen parts and are involved in the mapping for ABCD.

Mar 20, 2025

Diversity Collection

Processing

Every specimen can be processed, e.g. for preparation or preservation. Processings can be applied to a specimen or a part of a specimen. In the hierarchy for the parts the processings are indicated by the icon and a blue text. If there are any processings available, they will be indicated by the icon in the tool bar. Please keep in mind that the availability of the processings depend upon the material category and the current project as described below. You can hide or show the processings in the hierarchy with a click on the icon in the very left bar (see below). The images below show a processing in the collection and the specimen tree for the parts respectively.

You can enter a new processing for either the entire specimen or a part of the specimen. To do this select the specimen or part in the hierarchy and choose a processing from the list as shown below.

The duration of the processing is saved in ISO8601 format by default indicated by the ISO icon with separate fields for year to second (see below). To change to text format, click on the ISO icon that will change to ISO and the separate fields will be replaced by a text box containing the value. If separate fields are only available if the value is in ISO 8601 format. If the start date for the processing is given the processing duration can be set via the calender. In case of the ISO format selected this will be translated into the corresponding period. In case of the ISO format deselected the date will be inserted. See a short introduction for an overview: Video starten

To delete a processing select it and click on the button. To edit the data for a processing select it in the hierarchy. The window will show you the fields related to the processing. You may add methods for the processing as defined in section Method

(If you previously used any tools defined in the toolsection, these are deprecated and replaced by methods).

 

Administration

If you have the required rights you may edit the processing types in the menu entry Administration - Processing...

In this window you can define the processings used in your collection. To add a new processing click on the button, to delete a processing select it and click on the button. The processings are related to material categories within the database. To add a new material category or projects, which should be connected to the selected processing, click on the button in the panel right of the material categories or the projects. A window will open where you need to select the desired material category or project respectively (see below).

The processing types are organized in a hierarchy. Some of the entries may only serve for structuring as Maceration in the example below and should not be used to document the processing of specimen parts. To ensure this check the checkbox [Only hierarchy]. For the import and export of data it is sometimes necessary to know the ID's of the analysis types. To see the ID's of the data sets click on the [ID] button. The ID's will then be displayed as in the image shown below.

Besides of a plain text description of the processing, you may insert methods as defined in the chapter Methods. Use the and buttons to add or remove methods from the list (see below). The added methods will be marked with sequential number to allow several methods of the same type. Every method may have several parameters that will automatically be available to take your values. If the definitions of the parameters have been changed, you may add missing parameters with the button. A window will open where you can select the missing parameters you want to add.

To view the history of a data set, click on the button. A window with the history will open. For more details see the section History.

The data of the processing is stored in the table CollectionSpecimenProcessing.

Mar 20, 2025

Diversity Collection

Description of the parts of the specimen

Tutorial: Video starten

A part of a specimen may be characterized with links to a standardized vocabulary from DiversityScientificTerms. Use the button to add and the button to delete descriptions (see below). If the description refers to a certain unit, you may select it in the list as shown below. 

The data is stored in the table CollectionSpecimenPartDescription

Mar 20, 2025

Diversity Collection

Collector

The people or groups responsible for the gathering of the specimen are stored in the table CollectionAgent. There may be several collectors for one specimen. In the tree the collectors are symbolized by the icon as shown below.

 

To hide or show the collectors in the tree use the icon in the left panel (it will change to a grey version with a yellow background when the collectors are hidden). To insert a collector choose either the specimen or an existing collector in the tree and then click on the icon in the right panel. Select a collector in the tree to enter details. In the right part of the window the detail fields will appear as shown below.

 

If a collector should refer to a dataset in the module DiversityAgents (where more details like addresses may be stored) click on the  button. If in the module DiversityAgents a synonym is choosen, you will get the data of the correct name instead. The sequence of the collectors (e.g. for print on a label) as shown in the tree can be changed by with the   and  buttons in the panel on the right side of the tree.

With the template you can define and copy predefined values into the data (see chapter Template).  

To remove a collector select the entry in the tree and click on the  button.

You can search for the gathering numbers of the collectors in the query.

Data of the collectors is stored in the table CollectionAgent.

Mar 20, 2025

Diversity Collection

Reference

For Specimen, Unit, Identification or Part

Tutorial: Video starten

To each specimen, organism or part you can add references. To add a reference select the specimen (symbolized by the barcode ), organism (e.g. , , ), identification or part (e.g. , , ) in the tree and click on the button in the panel right of the tree. This adds a reference to the selected item as shown in the image below.

The entries may be linked to the module DiversityReferences.

The data is stored in the table CollectionSpecimenReference.

Mar 20, 2025

Diversity Collection

Relation

Each specimen may have relations to other specimens. For example a duplicate, a specimen isolated from the same material or a part of a specimen may be located in another collection. Another example is link to e.g. GenBank where information connected to the specimen can be found. This can be documented by adding relations to these specimens. To add a relation select the specimen (symbolized by the barcode ), organisms (e.g. , , ) or part (e.g. , , ) in the tree. You may then either add a relation to a local specimen using the button or add a relation to a remote specimen using the button in the button panel on the right side. To show or hide the relations in the tree use the and buttons. For an overview see a short tutorial Video starten.

 

Internal relation

To add an internal relation to a local specimen use the button. A window will open where you may search for the related specimen.

Select the related specimen from the query result list and click OK to close the window and establish the relation. In the left image below you can see an internal relation while the image on the right shows a reverse relation from another specimen. 

 

In the case of internal relations you can navigate to the related specimens using the button.

If linked dataset of a relation is removed, the orphaned relation can be removed in the maintenance. Video starten

To search for specimen with internal relations either source or target of the relation use the Internal relation section in the query

 

External relation

To add an external relation to a specimen which is not administrated in the database DiversityCollection use the button. In the image below you can see a relation to a specimen in an external collection.

 

Deleting relations

To delete a relation select it in the tree and click on the  button.

Relations to units and parts  

If the relation should be If the relation should be referred to an organism, part or organism in a part either select the organism or part in the tree and add the relation or use the mouse to drag the relation into the correct position (see examples below).

Specimen

Organism

Part

Organism in Part

 

Details of the relations

Together with the relation the details of the dataset is shown in the overview tree. To hide these details click on the button (see example below).

Editing the data

To edit the data for a relation click on the entry in the tree. In the right part of the window the details of the data set will be shown (see below).

 

The data is stored in the table CollectionSpecimenRelation.

Mar 19, 2025

Diversity Collection

Exsiccatae

Exsiccatal series and related information are administrated in the module DiversityExsiccatae. For a search in the data provided by this module click on the button.

For direct access to the information about the exsiccatal series in this module you require the application DiversityExsiccatae.exe in your application directory, the database DiversityExsiccatae and a valid account in the database. For more information see the DiversityWorkbench Portal.

Jul 3, 2024

Diversity Collection

Images

Creating and removing images

To insert a new image click on the  button. A window will open where you can enter the path and file name of the image. Click on the button to search for a web address of an image as shown below.

URL of image

The URL for images can not be changed in the main form. Instead you have to create an image with the new URL and delete the image based on the old URL.

To edit the URL, please use the TableEditor for the corresponding image table.

To use an image available as a local file click on the button to search in your local directories. You can upload this file via a webservice to the server of an institution providing the DiversityMediaService. To use this service you may rename your image either using a GUID or according to the accession number including date and time. Use the upload button to upload your image to the server.

To delete an image select it from the list and click on the  button.

Setting the maximal size for an image

To prevent the application getting irresponsive due to large images, you can set the maximal size of images. If an images exeeds the set size it will not be shown together with the size of the image as shown in the image below.

Orientation and zoom level of the images

To zoom a specific sector of an image simply drag the mouse over the preferred area of the image. A red square will indicate the zoomed area. To set the size of the image to its original resolution click on the  button. To adapt the size of the image to the available space in the form click on the  button. To change the orientation of the image use the appropriate buttons (  flip horizontal,  flip vertical,  rotate right,  rotate left).

Using EXIF information for image orientiation

To correct the orientation of an image according to the rotation documentend in the EXIF data, click on the button. The button will activate the orientation according to the EXIF information indicated by a yellow background . An example is demonstrated in the video: Video starten.

Separte window for images

To view the image in a separate form click on the button.

Fixing path issues

For images with a path containing escape signs (e.g. %2F) the translation of these sign can be suppressed using the %2F resp. / button.

Withholding images

If the image should not be published e.g. on the internet, enter any reason in the Withhold. reason - field. Next to images you can store other media.

High resolution images

For images where a high resolution version is available, a zoom button will appear as shown below.

Click on the zoom button to open a window to see details of the image as shown below (using krpano/ software).

 

Description of images

For the description of a medium see the chapter Imagedescription.

Datatables

Data is stored in the tables CollectionSpecimenImage, CollectionEventImage , CollectionEventSeriesImage and CollectionImage.

Apr 8, 2025

Subsections of Images

Diversity Collection

Image Description / EXIF

The EXIF content is derived from the original image (see below). This will be automatically extracted from the image.

To extract the EXIF content of an image, the image must be accessible from a local directory and the exiftool.exe (see below) must be available in the application directory.

Jul 3, 2024

Diversity Collection

Media

Next to images you can store audio and video files. Click on the [>>>] button (see below)

 

To open Windows Media Player and play the content of the media. You must have Windows Media Player installed to use this function. For the description of a medium see the chapter Image description.

Jan 14, 2025

Diversity Collection

Media Service

The webservice DiversityMediaService provides the possibility to upload media files like images, audio recordings, etc. to a server. The usage of this webservice includes several preconditions (please turn to your administrator):

  • You need an account in the DiversityWorkbench module DiversityAgents with your login in DiversityCollection linked to this account
  • Your project has to be registered on the server
  • You have to rename your media file according to the settings of the server e.g. using a GUID (see image below)

Use the upload button to upload your image to the server.

Jul 3, 2024

Diversity Collection

Methods

The methods used for collection events, the analysis of the organisms or the processing of the material. To administrate these methods, choose Administration → Methods ... from the menu (only for Administrator). A window as shown below will open. For an introduction see a short tutorial Video starten.

There are 2 lists where you can define for which analysis resp. processing the selected method may be used. If the checkbox For collection event is checked, this method may be used for collecting events. To organize your methods you can add methods with the checkbox Only for hierarchy set to true . For these methods the sections for entering details are disabled. The methods may contain several parameters as shown above. To insert a parameter click on the  button. If a parameter should only allow predefined values, check the Use dedicated values for a parameter checkbox and add values using the  button. With the buttons you can remove parameters or predefined values.

To view the history of a dataset, click on the button. A window with the history will open. For more details see the section History. For any comments to this part of the application, use the feedback function.

In the main form you can add a method to a collectionevent or a processing. Choose the respective item in the tree and click on the button to add a method (see below). Depending on the selected method, you get a list of parameters for which the values can be set. For the parameters where default values are available, these will be inserted when adding the method.

You may add several methods for one analysis resp. processing or collection event as shown above.

 

Jan 14, 2025

Diversity Collection

Annotation

If you are a user, having no rights to edit any data in the database, you can still add annotations for a collection event, a collection specimen, a part of a collection specimen or an organism (= identification unit). With annotations you can start a discussion about items in the database where annotations refer to previous annotations on the same subject. 

For data where you have Read Only access, you can still add annotations.

The available types are annotation and problem. To add an annotation, select the corresponding data in the tree view. In the tool panel on the right of the tree view a button will appear: if no annotations have been added so far or if there are annotations for this entry. A window will open as shown below.

To add an annotation, click on the button and select the type of the annotation. If you want to add an annotation depending on an existing annotation, select the superior annotation in the tree and click on the button. The annotation will be shown in the tree with the details listed below (see image below).

Enter your annotation in the text box as shown above. You can enter a title or subject for your annotation or select one from the list. You may enter a link and a source as shown above. The source may be related to the module DiversityAgents.

To delete an annotation you have to be either an administrator or a data manager. Select the annotation and click on the button.

If you want to see all annotations of the current specimen choose Data - All annotations... from the menu. All annotations will be listed as shown below.

Data for the annotations are stored in the table Annotation.

Mar 20, 2025

Diversity Collection

Collection Management

Main sectors

The image below gives you an overview of the main sectors related to the collection.

Collections are managed by collection managers (see Administration → Transaction management → Collection managers ... in the menu), who organize the transfer of specimen between collections and track the exchangebalances . Any transfer of specimen is organized via transactions (see Administration → Transaction management → Transaction ... in the menu).

An overview is given in the image below.

 

Mar 19, 2025

Subsections of Collection

Diversity Collection

Collection

The parts of a specimen can be stored in several collections. To see the place where a specimen or parts of it are stored use the lower tree and click on the icon to select the display according to the collections as shown below and in a short tutorial Video starten.

In the tree shown above select the collection to display the data fields as shown below.

To be able to edit the details of a collection, you must be a collection manager of this collection. The restrictions for the access for editing the collections are defined in the CollectionManager section.

At the base of the fields you find the default collection, used for the creation of new specimen parts. Specimen parts that are not created as a part of another part will be placed in this collection. Use the button to edit this entry (see below) For another possiblity to edit this value choose Administration - Customizedisplay from the menu.

Administration of the collections

If you need further information about a collection click on the button or choose Administration - Collections... from the menu to open the window for the collection administration (this menu entry is only available for collection managers). This will open a window (see below) where you can edit the collections used in your database for which you are a collection manager. You can choose among several options to show resp. hide the hierarchy:

  • Show whole hierarchy
  • Superior datasets and children of current dataset
  • Restrict to superior datasets
  • Hide the hierarchy

Cache tables for the hierarchy

To improve the responsiveness of the application the hierarchies of the collection are cached in tables for the collection, the location and the user availability. These cached data must be kept in sync with the main data.

After changes in the collections or their hierarchy a button will remind you to save the changes in the cache tables. The list below contains all objects in the database involved in the caching of the data

CollectionHierarchy
  • Accessed by user
    • view CollectionHierarchy_All
    • table function CollectionHierarchyAll based on CollectionHierarchy_All
  • Behind the scenes to provide cached data
    • stored procedure procRefreshCollectionHierarchyCache
    • table CollectionHierarchyCache
    • scalar function CollectionHierarchyRefillBlocked
    • table function CollectionHierarchyRefillCache
    • table function CollectionChildNodes
CollectionLocation
  • Accessed by user
    • view CollectionLocation_All
    • table function CollectionLocationAll based on CollectionLocation_All
  • Behind the scenes to provide cached data
    • stored procedure procRefreshCollectionLocationCache
    • table CollectionLocationCache
    • scalar function CollectionLocationRefillBlocked
    • table function CollectionLocationRefillCache
    • table function CollectionLocationChildNodes
UserCollectionList
  • Accessed by user
    • view CollectionListForUser
    • table function CollectionLocationAll based on CollectionListForUser
  • Behind the scenes to provide cached data
    • stored procedure procRefreshUserCollectionListCache
    • table UserCollectionListCache
    • scalar function UserCollectionListCacheRefillBlocked
    • table function CollectionChildNodes
    • table CollectionUser_log + trigger for logging of delete
ManagerCollectionList
  • Accessed by user
    • view CollectionListForManager
    • table function ManagerCollectionList based on CollectionListForManager
  • Behind the scenes to provide cached data
    • stored procedure procRefreshUserCollectionListCache
    • table UserCollectionListCache
    • scalar function UserCollectionListCacheRefillBlocked
    • table function CollectionChildNodes
    • table CollectionManager_log + trigger for logging of delete

Specimen placed in the collections

With the botton, you can display the specimen stored in a collection within the hierarchy (see below).

As an alternative the specimens stored in a selected collection can be listed in the specimen list. You can hide / show this list using the [  ]/ button. The specimen list will appear as shown below. Click on the collection in the tree view to fill the list and see the specimens that contain parts which are placed in the current collection. To transfer the parts of certain specimen from the current collection to another collection, choose them in the list and click on the button. To change to a specimen from this list click on the button.

As an alternative you may select the specimen in the main form a choose Data - Transfer - To Collection ... from the menu. A window will open where you can select the collection in which you want to transfer the specimen. With this option [ALL] parts of the selected specimen will be transferred into the selected collection.

Creating new collections

To create a new collection use the button either above the Query results or the button right of the hierarchy, where the new collection will be placed underneath the collection selected in the hierarchy. To copy a collection either use the button or the button. The latter will copy the collection including all child collections. To set the superior collection, use the button. The user creating the new collection will automatically be inserted as a collectionmanager for this collection. To remove a collection, any collection manager must be removed from this collection first. Click on the button to open a window for the administration of the collection managers. For new versions of the database the removal of the link of collection managers to deleted collection will be done automatically. To transfer collections in the list as children into another collection, click on the button in the upper left corner.

 

Administration of collection types

To administrate the types for the collections, click on the button. A window will open where you can create new types and add icons representing a type (see below).

Use the     buttons to add resp. remove a type and the     buttons to handle the hierarchy. For new types you can use the button to add an icon for the new type.

The type regulation is provided for the collections that are meant to administrate the access to transactions of the type regulation. See chapter Transaction or further details.

Images

If there are images depicting the collection a yellow background will indicate the availability of these images. To show the images, click on the show images button. The button will get a red background and this will open the area for the images as shown below. Use the new and delete buttons to add or delete images of your collection. For further details about handling images see chapter Images.

 

Plan

If a floor plan is available for a collection this will be indicated by a yellow background . For details see chapter collection floor pan

Label

To print labels for e.g. drawers, click on the print button. The area for printing the labels will be shown (see below). Further details about printing labels are described in the chapter Label.

For the generation of QR-Codes there are 2 options:

 

Data in tables

To edit the contents of the tables in the table editor select   - Collection resp.   - Image  from the menu. For Details see chapter TableEditors.

History

To view the history of a dataset, click on the button. A window with the history will open. For more details see chapter History.

Data

For details about handling data see the Data section. Data of the collections is stored in the table Collection.

Mar 19, 2025

Diversity Collection

Collection Manager

Collection managers are users with the right to edit the transactions for a collection, including loan, purchase, inventory etc. To administrate the collection managers you must be in the administrator group. Either choose - Administration - Transaction management - Collection managers from the menu or Administration - Collection and there the button to open the editing window for the collection managers as shown below.

Use the < and > buttons to edit the list of the collections for which the selected collection manager can create and edit transactions.

After changes in the collection managers you will be reminded to save the changes in the cache tables.

The collection managers can be listed with their names or their logins. Change this with the list by option at the base of the list. If after e.g. a database have been moved to another server, the may exist logins with names not matching those on the server. Click on the agent synchonisation button to correct this. In case of duplicate permissions you might get a list with these duplicates where you have to remove the duplicate permissions.

For details about handling the collections see the Transaction section. Data of the collection managers is stored in the table CollectionManager.

Apr 17, 2025

Diversity Collection

Collection User

The access of users to collections can be restricted. To edit the collection list for a user choose - Administration - Transaction management - Collection users ... from the menu. A window will open, where you can add or remove collections a user has access to as shown below. The access [includes all subordinate collections]. This means adding a collection to the list a user has access to also grants the user access to the subcollections as defined in the hierarchy of the collection. In the example shown below the second entry is not necessary as it is already included in the first entry.

Use the < and > buttons to edit the list of the collections for which the selected user has access to.

After changes in the collection users you will be reminded to save the changes in the cache tables.

If a user has no collections in the list, all collections are available for this user.

A collection manager has access to the collections he is allowed to manage as well as those in the list as a collection user.

Data of the collections is stored in the table CollectionUser.

Mar 19, 2025

Diversity Collection

Collection Location

Tutorial: Video starten

There are 2 hierarchy available for collections (showing the whole hierarchy or only the parent datasets):

  • Administration
  • Location

To enable the location hierarchy, either in the custom settings - in the menu choose  Administration - Customize display...  and then in the Defaults and miscellaneous tab set the option or in the collection window click on the in the top.

By default the hierarchy according to the administration is displayed (see example below).

The location nodes in the tree indicate that these nodes have a location parent, different from the administration parent. To change to the hierarchy according to the location select the  option underneath the hierarchy (see below).

To set resp. remove a parent location click on the     resp.    button. With the    button a window will open where you can choose the parent location for the current dataset.

After changes in the collections or their hierarchy a botton will remind you to save the changes in the cache tables.

As an alternative to transfer collections in the list as children into another parent location, click on the Transfer to location button in the upper left corner with a brown background, right of the Transfer to parent collection that refers to the administrative hierarchy of the collections. A Window will list all locations in the current database and the software will ensure that the transfer will not lead to loops in the hierarchy. Transfers that would result in a loop will be listed in an error message.

Jan 24, 2025

Diversity Collection

Floor plan resp. geometry

If a floor plan is available for a collection this will be indicated by a yellow background. To provide the floor plan of a collection choose from the menu and click on the button to select the floor plan. Click on the button to save the plan.

To provide the geometry of a certain area within e.g. a drawer the same can be applied with an image of the drawer as plan. The floor plans are inhertited to depending collections and the geometry of a parent collection will be indicated by a dotted line (see below). The field Height keeps the height of e.g. a sensor for temperature.

Besides floor plans you may as well specify certain positions within e.g. a drawer (see below and the tutorial Video starten).

Restriction of access to files

The access to files on the server can be restricted with a .htaccess file within the directory. An example for the content of the file is shown below

AuthType basic
AuthName "Protected Directory"
AuthUserFile /.htpasswd
AuthGroupFile /dev/null
Require valid-user

To allow users access to the directory these users must be listed in the .htpasswd file

Run the following command to create an .htpasswd file for a user (replace user1 with the desired username): htpasswd -c /.htpasswd user1

Enter a password for user1. The encrypted password will be stored in the .htpasswd file. Confirm that the .htpasswd file has permissions set to 644.

Setting the scale: ↔

To set the scale for a floor plan with a scale provided in the plan, click on the button. A blue bar will appear that can be dragged and changed in length to a object of known size, e.g. a scale in the plan. After the scale is set, click on the button and the floor plan will be overlaid with the scale as shown above. The width of the whole plan will be shown in field [Width].

 

Setting the geometry: □

To set the geometry of e.g. a room, click on the  button. A red rectangle will appear as an overlay in the plan that can be dragged into the right position. The × button removes the geometry from the current dataset. Click on the button to store the geometry.

 

Zoom

To zoom the floor plan use the slider at the left or the mouse wheel. To return to the original size with a click on the [1:1] button. If the current dataset has a geometry you can use the [ ]  button to zoom in the geometry. With the  button you can show the whole image. 

Jul 26, 2024

Diversity Collection

External Identifier

External identifier may be added for a collection event, a collection specimen, a part of a collection specimen, an organism (= identification unit), a reference or a transaction. To add an external identifier, select the entry it should be attached to and click on the button. A window as shown below will open. 

Select the type of the identifier, enter the identifier itself and close the form to save the identifier. To remove an identifier use the button.

To administrate the types of external identifiers choose Administration - External identifier ... from the menu. A window as shown below will open listing the available types.

To add or remove a certain type, use the and buttons. To edit the relations between the identifiers use the resp. button.

Data for the external identifiers are stored in the table ExternalIdentifier. In an upcoming version these data will be transferred into new tables (Identifier, IdentifierForEvent etc.).

Mar 20, 2025

Diversity Collection

Regulations

Adding to event and part

As a first step the regulations resp. their title must be added for the collection events either via the button or for several events in the maintenance.

Then you can select a specimen part part and use the button to select a regulation from the list in the events.


graph TD;
    EventStart[Add regulation to collection event] --> |<i class="fas fa-globe"></i>| Button(For current collection event)
    EventStart --> Maintenance(For several collection events)
    Maintenance -->|<i class="fas fa-cog"></i>| MaintenanceRegulation[Maintenance - Regulations]
    Button --> Event[Collection event] 
    Event --> Part[Add regulation to specimen part]
    MaintenanceRegulation --> Event

To add a regulation to a specimen part, choose the part to which the regulation should be added and click on the button. A window as below will open, listing all available regulations (see below) ...

Choose the regulation you want to insert and click OK. The regulation will be inserted as shown below.

To remove any regulation use the button.

Documents

Depending on your permissions you can see the documents stored for a regulation when you select the regulation listed for the event.

If you do not have the needed permissions, you will get a corresponding result as shown below.

In case the selected reglulation contains no documents, this will be indicated as shown below.

Administration

To administrate the regulations choose Administration - Transaction management - Transaction  ... from the menu. See chapter Transaction for further details.

Datatables

The diagram below shows the tables involved in the regulations.

 

Jan 14, 2025

Diversity Collection

Transaction

Main sectors

The image below gives you an overview of the main sectors related to the transaction.

Prerequisites to use transactions

The transfer of a specimen between collections is handled with transactions. There are two prerequisites to use transactions in DiversityCollection. You are required to be in the user group CollectionManager (see UserAdministration) and the collections in which you have the right to handle transactions must have been assigned to you is shown in the CollectionManagers section.

Historical development

To create charts for the historical development see chapter Charts.

Visibility of transactions

A specimen may be involved in diverse transactions between collections like loan, purchase, gift or exchange. The transactions are shown in the tree for the parts of a specimen and symbolized with e.g. an icon. For specimens which are still on loan an icon is shown while a returned loan is symbolized with an icon (see image below). A data embargo will be symbolized with an icon. If there are older accession numbers linked to a specimen involved in a transaction, these numbers can be documented together with the entry of the transaction of the respective part of the specimen.

          

To customize the sequence and format of the transactions shown in the tree, choose Administration → Customize display ... from the menu and see the chapter customize for further details.

As an administrator you can edit and add entries to the Standard comments for transactions click on the button in the header. For details see chapter customize.

If you are a CollectionManager, you may take a look at the details of a transaction. Select the specimen part in the tree and click on the button which will be shown in the details next to the name of the transaction. This will open the window for the transactions as described below.

 

To edit the transactions choose Administration - Transactions from the menu. A window will open as shown below. In the tree at the top the relations between the transactions are shown. To create a transaction dependent on another transaction choose the superior transaction in the tree and click on the button in the panel right of the tree. With the button you may create a copy of a transaction. To delete a specimen from the list click on the button. To transfer all selected specimen in an existing transaction choose Data → Transfer → To transaction... from the menu and choose the transaction where the specimen with all their parts should be included. In two following dialogs you may restrict the transferred parts to a certain collection or material category. The data for the transactions is stored in the tables Transaction and CollectionSpecimenTransaction.

The ID of the transaction is shown in the header. Behind the ID the maintenance button may appear in case of missing units in parts which e.g. for the creation of sending letters may cause unexpected results. Click on the maintenance button to open the maintenance for fixing this problem. With the feedback button you can send a feedback to the software developer. To view the history of a data set click on the history button. A window with the history will open. For more details see the section History. The  settings button will open the settings for the transaction. The edit table button opens a table editor for the selected transactions. For large hierarchies the retrieval from the database may be time consuming. To hide the hierarchy use the botton resp. to show the hierarchy. The list for the specimen may be shown or hidden  .

Data entry

On this page you may edit the data of a transaction. Every transaction is linked to an administrating collection (symbolized by the key ) and can be edited exclusively by CollectionManagers of this collection. To appoint managers choose Administration - Managers from the menu.

The transactions can be organized in a hierarchy as shown in the image above, if e.g. you wish to keep together all loans to a certain institution. To create a transaction of an inferior transaction choose the superior transaction in the tree and click on the button in the panel at the right side of the tree. To create of copy of a transaction, use the button and the button to delete it. If you want to change the position within the hierarchy, select the transaction and click on the button. A window will open where you can select the new parent. Depending on the type of transaction you have up to 3 dates, e.g. for a loan you have a begin date, an end date and in case of a prolongation an end date of the prolongation.

There are the following types of transaction:

Transaction type Description
embargo Temporary data embargo for specimen that should not be published within the specified period
exchange the exchange of specimens between institutions
gift the gift of specimens to an institution
inventory the inventory of specimens within an institution
loan the loan of specimens of an institution to an external loan taker
permanent loan permanent loan of specimens of an institution to an external loan taker
permit permit or certificate for the collection of specimen
purchase the purchase of specimen by an institution
regulation a regulation concerning a specimen in a collection
removal a removal of a specimen from a collection
return a complete or partial return of a loan
transaction group an entry to organize your transactions

The fields display in the Details tab will vary with the type of the transaction as e.g. an embargo does not need any address information. For the addresses use the links to the module DiversityAgents as shown in the image above. You may optionally enter a collection and the program will then use the corresponding address as described below. As the recipient of e.g. a loan may not be entered in DiversityAgents, you can enter the name of the person directly in the To-address. The use of the collection as a reference in the From and To section is deprecated. Please use a link to the module DiversityAgents instead. If you need these controls please open the settings and select the Show all address fields option.

 

Common notes

On the tab pages for generating documents you need to specify a xml-schema for your document. Click on the button to choose one of the predefined schemas or create your own. To edit the schema files (*.xslt) you may use a text editor or software like e.g. EditiX. If you do not specify a schema for your form (i.e. the field for the path of the schema is empty - see below), you will see the XML output created by the database as shown below.

To choose a schema click on the button and select a schema from the list. DiversityCollection contains several ready to use schemas in the folder Transaction - Schemas - Sending.

 

Feel free to change these schemas according to your own needs (editors are available e.g. from http://www.altova.com/). Choose the schema you need and click on the button to create a document. To print the document use the printer button. To store the current document for later reference in Documents click on the save button. An example for a document is shown below.

Sending list

The specimens will be listed with their accession number, an optional label of the part, the material category and if available the country and the collection year to ensure discrimination in case a specimen contains more than one part. If available a permit will be shown at the last position (see image below).

In the sending list - to see the details of a permit - click on the line containing the permit. The details will for the permit will be shown as in the example below.

 

Finding addresses

The addresses used for the documents are taken from the module DiversityAgents, where addresses are stored. Therefore the entries must at some point be linked to an entry in this module. The program will try to find an address as shown below: First the transaction partners (from ... and to ...) will be checked. If no address is available (e.g. if the transaction partner is not linked to an entry in DiversityAgents), the program will try to find an address in one of the superior transactions from the transaction partners found there. If no address exists in these transactions, the program will try to get an address from the collections. Therefore, a transaction partner linked to DiversityAgents is only necessary if either there are no addresses for the collections or you wish to use a different address. The search path as described is summarized in the image below. 

No Access

If the data contain datasets, where you have no access to, this will be indicated as shown below.  

The access to the data rely on the result of the view TransactionList, combining the transactions with missing administrating collection and those where the current user is a member of the group CollectionManager with allowance for the collection where the transaction is administrated. Transactions within a hierarchy to which the user has no access will be displayed with gray titles.   

 

Mar 20, 2025

Subsections of Transaction

Diversity Collection

Transaction Loan

Loans of specimen from a collecting are documented with the transaction type loan (see below).

For a loan granted to a loan taker, create a new transaction and set its type to loan. The loan needs an administrating collection, which is the collection in which the specimen included in the loan are located and for which the current user is registrated as collectionmanager . The addresses are entered as links to DiversityAgents in the From and To areas. The To area provides a recipient for inclusion in the address. The collections in the From and To area may be used optionally as source of the address. The Begin and End fields mark the time span for the loan. If the time of the loan should be prolonged, use the Prol.: field to enter the new end date. Standard comments can be edited (Admin only) in the Customize section. In the Sending, Confirmation and Reminder sections you can create documents for the communication with the loan taker. Documents as sent to or received from the loan taker are available in the Saved documents section. If after the end of the loan all or a part of the specimen are returned, create a Return transaction as child of the loan (see image above) and include all returned specimen in this return transaction.

 

Jan 14, 2025

Subsections of Loan

Diversity Collection

Transaction Sending

In the sending tab page of the transaction window you can create the covering note for a sent sample. To choose a schema click on the button and select a schema from the list. DiversityCollection contains several ready to use schemas in the folder Transaction - Schemas.

To add a specimen to the list, you can use a barcode scanner. The code detected by the scanner will be displayed in the field behind the symbol and entered in the list below. If no scanner or barcode is available, use the combobox underneath, enter the first letters of the accession number of the specimen and select your specimen from the drop down list. In case your scanner is reading only parts of the barcode try to adjust the timer interval - click on the scanner button to open a window as shown below.

 

To restrict the selection of the specimens and parts of the specimens, you can check the Restrict to collection ... and Restrict to material ... options. To remove a specimen from the list, use the button under the specimen list. If you want to see the details of a specimen, choose it in the list and click on the button. Click on the scanner button to create the document as shown below. The upper list shows the parts on loan while the parts in lower list are returned to another institution. For more details about the upper list see chapter transaction.

Jan 14, 2025

Diversity Collection

Transaction Confirmation

On this page you may create an inquiry letter for a package sent, e.g. if a parcel was sent to a loan taker and no confirmation that the parcel reached its destination was returned so far.

With the button choose the schema you need. Click on the button to create a document. To print the document use the button. To store the current document for later reference in Documents click on the button.

Jul 4, 2024

Diversity Collection

Transaction Forwarding

Specimen on loan may be forwarded to another institution. A forwarding can only be part of a loan. Select the loan of which the specimens should be forwarded and add a new transaction as a child of the loan. Then set the type of this new transaction to forwarding as transaction type.

... and use the button to move the selected specimen from the initial loan into the list of forwarded items (see below).

Jul 4, 2024

Diversity Collection

Transaction Reminder

If a loan or forwarding is due to return or a loan taker did not meet the deadline, you may create a prompt note here.

With the button choose the schema you need. Click on the button to create a document. To print the document use the button. To store the current document for later reference in Documents click on the button.

In the upper right list the missing specimen and at the lower right list the returned specimen are listed.

 

Jul 4, 2024

Diversity Collection

Transaction Return

If a loan is returned, a child transaction of the type return is created, containing the returned items of the superior transaction. To do this, choose the loan in the tree and add a new transaction as child as shown below. Then set the type of this new transaction to return.

The state of the specimen will always be kept with the loan and you can add return incidents as long as there are specimens on loan. A return incident can only be part of a loan transaction. To transfer items into the return transaction, you have two options: can mark the items in the [loan list]that should be transferred and click on the button or click into the [text field] rightof the icon and use a barcode scanner. To remove an item of the return list, mark it in the [list of returned items] and click on the button. 

To you may create a notice of arrival here. With the button choose the schema you need. Click on the button to create a document. To print the document use the button. To store the current document for later reference in Documents click on the button.

 

Jul 4, 2024

Subsections of Return

Diversity Collection

Transaction Partial Return

If parts of a loan were returned, create a letter of acknowledgment here.

With the button choose the schema you need. Click on the button to create a document. To print the document use the button. To store the current document for later reference in Documents click on the button.

 

You have two options to enter returned specimen. Use the and buttons respectively to move items between the lists or use a barcode scanner . Move the mouse cursor into the field for barcode detection and scan the barcode. The specimen will be automatically inserted into the list for the returned specimen. In case your scanner is reading only parts of the barcode try to adjust the timer interval. Click on the button to open a window as shown below. Here you may set the interval to a value which is compatible with your scanner. If you wish to see the details of a specimen, choose it in the list and click on the button.

 

Jul 4, 2024

Diversity Collection

Transaction

Request

There are 2 ways to enter a request for a loan.

  • You are a CollectionManager and want to insert a foreign request. This request may be the starting point of a loan. To add a corresponding loan to the request, choose the request in the hierarchy and click on the copy botton. A loan depending on the request will be added.

  • You want to place your own request in a collection. In this case you must be granted the role Requester (see Loginadministration for further details). The grants are given by the CollectionManagers for their collections. To enable a user to place requests choose Administration - Transaction management - Loan requesters ... from the menu. A window will open as shown below.

As a CollectionManager you may give requesters access to the collections you manage. Click on the < or > button to add or remove collections from the list for which a user may place a request. If the option Include subcollections is chosen, a user is able to request specimens stored in subcollections of the administrating collection. To give you an overview of the subcollections the hierarchy of the collection is shown in the tree below the list.

If you are a CollectionManager and there are requests for your collections, the administration menu will contain a Loan requests ... entry. Choose it in order to open a window listing the requests for specimen in your collections.

If you have entered a request for specimen in a foreign collection, the administration menu will contain a  My requests... entry. To inspect your request choose this entry from the menu to open a window as shown below. The window will show your requests and loans from foreign collections.

To enter a new request click on the button. Use the button to search for specimen in the collection and the button to remove unwanted specimen from your list.

Jan 14, 2025

Diversity Collection

Transaction Printing

In addition to special pages for creating letters along with a loan, this page provides the possibility to print cover letters, inventories etc. You may restrict the selected specimen to the current collection, include subcollections or all related collections - simply activate the corresponding checkboxes.

To add a specimen to the list you may either use the combobox or a barcode scanner. To use the barcode scanner move your mouse cursor into the pink field on the right of the scanner. In case your scanner is reading only parts of the barcode, try to adjust the timer interval. Click on the button to open a window where you may set the timer interval to a different value. To remove a specimen from the list select it and click on the button.

With the button choose the schema you need. Click on the button to create a preview of the document. To print the document use the button. To store the current document for later reference in Documents click on the button.

Jul 4, 2024

Diversity Collection

Documents related to a transaction

The page Saved documents stores all the documents created or received along with a transaction. A display text is automatically generated containing the type of the transaction and the date. You may change this if you prefer a different text.

To add a document either use the button after creating a preview of a letter e.g. for Sending .

Next to the internal documents created within the program, you can include external documents. You may scan an external document and create a screenshot of it. Then create a new entry (click on the  button) and use one of these options: Add URI of document or  Add image of document. The first option uses public available sources from a webserver while with the second option later screenshots will be stored directly in the database and are not accessible outside the database. If you want to print the document, double click on the image to open a window enabling the printing of the document . For the first option you may use the “https://…” button to search for an URL in your default browser instead of the inbuilt browser of the software which may not provide the whole functionality of a modern browser.

In the lower part you may enter the text that should be shown in the interface (Display text), the type and notes related to the document. With the type you may organize your documents as needed.

Dependent on the software installed on your local computer, pdf files may open in the program or the default browser installed on your computer. To avoid the automatic opening of these files deselect the option and use the button of open them.

Jul 4, 2024

Diversity Collection

Transaction Balance

This is the balance for the exchange between two collections.

With the button choose the schema you need. Click on the button to create a document. To print the document use the button. To store the current document for later reference in Documents click on the button. To include either the subcollections of any related collection or the collections of the current transaction select the corresponding checkboxes.

 

Jul 4, 2024

Diversity Collection

Transaction Permit

Permits for collecting specimen parts are documented with the transaction type permit (see below).

Documents as received by the permitting institution can be entered under Saved documents (see below).

To add a permit to a specimen part, choose the part to which the regulation should be added and click on the button. A window will open as shown below where you can select the permit you want to insert.

In the main window, click on the permit to see the details as shown below. The details of a permit will as well be shown for datasets in a sending list for a loan (see chapter Transaction).

Jan 14, 2025

Diversity Collection

Transaction Regulation

To administrate the regulations choose Administration - Transaction management - Transaction  ... from the menu. A window as shown below will open where the you can administrate and create regulations (see below).

Documents can be added as e.g. screenshots or webresources. See below and for further details the chapter Transaction - Documents

Jan 14, 2025

Diversity Collection

Transaction Removal

If specimens were removed from a collection e.g. by destruction or loss, you can create a transaction of the type removal and add parts of the specimen in question to this removal. If a specimen is part of a removal, it is shown as in the image below.

To create a removal choose Administration → Transaction management → Transaction from the menu, create a new transaction and choose the type removal for the new transaction (see below).

Jul 5, 2024

Diversity Collection

Transaction Embargo

If specimens should not be published for a certain period, you are able to create a transaction of the type embargo and add parts of the specimen in question to this embargo. If a specimen is part of an embargo, it is shown as in the image below for current and past or future embargos .

To create an embargo choose Administration → Transaction management → Transaction from the menu, create a new transaction and choose the type embargo for the new transaction. The period of the embargo is defined by its Beginning and End (see below).

To see the parts of a specimen that where selected and are included in an embargo choose Administration → Withhold data...  from the menu.

Jul 5, 2024

Diversity Collection

Transaction Identifier

The page Identifier stores any additional identifier related to the transaction (see below). 

For the administration of the types of identifiers see chapter External identifier.

Jan 14, 2025

Diversity Collection

Transaction Payment

The page Payments stores any payment within the transaction. To set the default currency (only dbo), choose Administration - Customize display from the menu. In the Transaction area use the Currency button to set the default currency for all payments. This is done with the setup of the database and can not be changed after any payment has been entered.

To add or remove payments use the and buttons. To set default currency for all payments in the database choose Administration - Customize display... from the menu and in the opening window the section Transaction (see chapter Customize).

Jan 14, 2025

Diversity Collection

Transaction Agent

The page Agents stores additional agents involved in the transaction (see image below) that are not recorded otherwise. 

Jul 4, 2024

Diversity Collection

Transaction Chart

The page Chart provides the option to create charts for the historical development of transactions (see image below). Video starten

A direct access is available via the menu: Administration - Transaction management - Statistics.

 

Jul 4, 2024

Diversity Collection

Templates for data

For several ranges in the data, you can define templates which can than be copied into the data. To define the template, click on the button. A window as shown below will open, where you can enter the data for the template.

Use the button to save changes in the template, the button to clear all entries and the copy options to take values from the data into the template. With the filling option you can decide in which way values from the template are written into the data. This option can be set as well under the menu Administration - Customize display and then Defaults and miscellaneous - Template (see below). 

 

There are 3 possibilities:

  • Copy values from the template only if there are no entries in the data
  • Ask the user if there are differing contents in data and template whether the template values should be copied into the data
  • Copy the values from the template irrespective of any content in the data

 

To copy the values defined in the template into your data just click on the button.

In case you select that the program should ask (see above), a window as shown below will open where you have to select those entries from the template that should be copies into the data. Use the buttons all resp. none to select resp. deselect all columns.

Dec 7, 2024

Diversity Collection

Task

Main sectors

The image below gives you an overview of the main sectors related to the tasks.

Tasks are used for example to organize IMP within a collection. The tasks possible for a collection are defined within the table Task. The tables related to tasks within a collection are shown in the diagramm below. The table Task contains the definitions for the tasks. The tables TaskResult and TaskModule contain predefined list for results resp. links to a DiversityWorkbench module. Types for the tasks are defined in the table TaskType_Enum. The table CollectionTask finally contains the tasks for a collection, the table CollectionTaskMetric numeric values collected e.g. by a sensor and the table CollectionTaskImage holding any related resources like images.

To define tasks, choose  Administration - Task  from the menu. A window as shown below will open.

View  

To show the site of the URI fo the task if available, choose show URI.

Import

To import data from a tab separated text file, choose from the menu. For further details see chapter ImportWizard.

Types

To edit types click on the button.

Table editor

To edit the data with the datatable click on the button. For details check the TableEditors section.

Feedback

To send a feedback to the software developer click on the feedback button. 

History

To view the history of a dataset, click on the history button. A window with the history will open. For more details see the section History.

 

Details  

The details of the task like e.g. type or display text are set in the upper part underneath the hierarchy (see above), the details for Collection tasks are defined in the lowest part. Only those properties that are specified by any text or definition are availabe for the depending collection tasks. There are several contents that are possible for a

Colletion task:

  • Specimen part: If the collection task is related to a certain part of a specimen in the collection
  • Transaction: If the collection task is related to a certain transaction
  • URI: If the collection task should contain an URI, the description for the URI
  • Responsible: If there is a responsible person or institution for a task, the corresponding description
  • Date: If the collection task should contain a date and or time.
    • You can choose among several options:
      • Date
      • Date from to
      • Date & Time
      • Date & Time from to
      • Time
      • Time from to
    • Begin: If present, the description of the begin
    • End: If present, the description of the endS
  • Description: If the collection task should contain a desciption, the description for the desciption
  • Notes:: If the collection task should contain notes, the description for the notes
  • Metric:: If the collection task contains values collected from a sensor e.g. via Prometheus, the description for the metric
  • Numeric: If the collection task should contain a numeric value, the description for the numeric value
  • Yes/No: If the collection task should contain a boolean value, the description for the Boolean value
  • Module: If the collection task should contain a link to a module of the DiversityWorkbench, the description and the type of the module. There are several modules for which links may be defined
    • DiversitAgents
    • DiversitCollection
    • DiversitGazetteer
    • DiversitProjects
    • DiversitSamplingPlots
    • DiversitScientificTerms
    • DiversitTaxonNames If the values should be taken from a list, the entries are defined here as shown in the image below  
  • Result: If the collection task should contain a text result, the description for the result. Similar to the module you can provide a list of values for selection as shown in the image below.  

insert a new analysis to an organism select the organism in the upper tree. Then select the type of the analysis from the drop down list as shown below.

Jan 14, 2025

Subsections of Task

Diversity Collection

Exhibition

The exhibitions are organized via Tasks. For a introduction see a short tutorial Video starten. DiversityCollection provides a predefined template if you want to organize exhibitions in your collection. You can provide floor plans for your collection and pinpoint the locations for your exhibition. To edit exhibitions choose Administration - Collection tasks  - Exhibitions ... from the menu. A window as shown below will open.

To add a new exhibition click on the button in the lower left. To remove a selected exhibition use the . To edit a selected exhibition use the button. To send any feedback concerning exhibitions and this form, click on the  button (see above).

To set the default responsible for actions within the exhibition resp. collection tasks, click on the button and select the User responsilbe for new tasks option (see below).

 

Exhibitions

To add an exhibition click on the button in the lower left. A window as shown below will open.

You may enter the start and end of the exhibition. Next you will be asked for the title of the exhibition (see below).

Next you have to select a location within the collection where the exhibition will be placed and as last step the timeperiod for the transfer of the part in the exhibition (see below).

Now the new exhibition will be shown in the list (see below).

To edit a selected exhibition use the button. A window as shown below will open, where you can edit the details of the exhibition. For further information see chapter Collectiontask.

If you want to delete an exhibition use the button. You will be asked before the exhibition and all it depending entries will be removed from the database (see below).

 

Parts

To add parts to an exhibition, click on the button for the parts. A window as shown below will open, where you can set the begin and / or end of the transfer into the exhibition.

Next you have to select a location within the collection where the part will be placed (see below).

A window for selecting the parts will open (see below)

If the list contains more than 1 specimen you will be asked if you want to insert all specimens in the list. You may choose to expand the inserted specimen from only the selected to the whole list (see below).

If there the list contains parts that are placed within the selected collection, the program will inform you that these parts will not be inserted in the exhibition as they are already there.

The new parts will than be inserted into the exhibition. Select a part in the list to see the details (see below). For more details, click on the button.

Collections

As soon as there are parts available the Collections will be listed in the upper right. Select the first empty line to show all parts transferred into the exhibition. If you select a collection, the displayed parts will be restricted to this restricted. If there are parts with their primiary location in the selected collection these will be listed directly below the collections (see below).

Plan

To see the plan of a collection, click on the button (see below). For more details see chapter Collection.

Printing

To print an overview of the parts in an exhibition, click on the generate report button. In the printer area you can generate and print reports either for all collections in the list or a single selected collection.

The collection hierarchy selects the part (e.g. a room) for which the report will be created. You can choose the time range for the report. If no Schema is selected plain xml will be generated. With the open file button choose a schema applied for the report. There are several schemas provided by the software, but you can create some of your own. You can include plans of your collection.

To create the report, click on the create report button. To print it, use the button.

Jan 14, 2025

Diversity Collection

Task

Import

To import data into the Task and Collection Task tables, select Data → Import → Wizard and then

  • import Task …
  • import Collectiontask …

A window will open where you can import your data as described in the import section.

Jan 14, 2025

Diversity Collection

Task types

The types for tasks are defined within the table TaskType_Enum. The define new types click on the  button in the task window. A window as shown below will open.

There are several predefined task types, but you can add additional types of your own. The types underneath the type DiversityWorkbench are types for tasks related to a module of the DiversityWorkbench. 

Jul 3, 2024

Diversity Collection

Import / Export

There are several import mechanisms:

An overview of some options for the im- and export of data is shown in the image below. The export and reimport of tab-separated list as well as the image import are deprecated and are only kept for comapatibility. Please use the import wizard for any imports into the database. An example for a dataflow from the original source to a webportal is shown here.

For details see chapters:

Jan 14, 2025

Subsections of Import Export

Diversity Collection

Archive

Create archive

The data related to a project can be exported into an archive. Choose Data - Archive - Create archive... from the menu. A window as shown below will open.

Select the project you want to create an archive of and click on the Find the data =\\\ button. The data related with the project will be imported into temporary tables to allow you to inspect them in advance of the creation of the archive (use the buttons to see the data). To create the archive, click on the Create the archive button. A directory will be created containing a XML file for every table. 

 

Reset database

Before you restore an archive, please make sure that the data from the archive do not interfere with the data in the database. In order to avoid problems you should clean the database from any user data. To clear the database from any user data, choose  Data - Archive - Reset database... from the menu. A window as shown below will open listing all tables and the number of data within these tables. Click on the Reset database  button to remove any of these data including any data in the log tables.

 

Restore archive

To restore an archive choose Data - Archive - Restore archive... from the menu. A window as shown below will open listing the tables in the database. To restore an archive click on the Choose archive directory button and select the directory containing the archive files. Next click on the Read data =\\\ button to import the data from the XML files into temporary tables.

With a click on the buttons you can inspect the content of the temporary tables. Finally click on the Restore the archiv button.

 

Plan schedule based archive creation

To administrate the schedule based creation of archives choose Data - Archive - Administrate archives... from the menu. A window as shown below will open listing the projects in the database. Select the project that should be included in the schedule based creation of archives. To create an archive for all selected projects, click on the Create archives button. The protocol of a previous archiving is shown as in the image below. [Successful runs] are indicated with a green color while [failures] have a red background (see below).

 

Creation of xsd schemata

Next to the data, the archive files contain a xsd description of the tables. To create xsd schemata independent of the content, select Data - Archive- Create schema from the menu. A windows as shown below will open with the list of all tables where the main tables of the database are preselected.

To change this selection you may use the  check all and  check none buttons resp. the Add to selection and Remove from selection options using * as a wildcard. Click on the  Create schemata button to create the schemata for the selected tables in the predefined directory. The  open button will open this directory containing the created files. The schemata contain the name of the DiversityWorkbench module and its version, the definition of the table, the primary key and the colums together with their datatype and description.  

Creation of archives as a backgroud process

To archive the data in a scheduler based background process, you can start the application with the following arguments:

  • Archive
  • Server of the SQL-server database
  • Port of SQL-server
  • Database with the source data
  • Optional: Directory where the archive directories should be created

C:\DiversityWorkbench\DiversityCollection> DiversityCollection.exe Archive snsb.diversityworkbench.de 5432 DiversityCollection C:\DiversityWorkbench\DiversityCollection\Archive

The application will create the archives, generate the protocols as described above and quit automatically after the job is done. The user starting the process needs a Windows authentication with access to the SQL-Server database and proper rights to archive the data. If the last argument is not given the default directory /…/ApplicationDirectory/Archive will be used.

 

 

 

Dec 1, 2024

Diversity Collection

Export

There are several options to export your data. You can either export data of the entire database or the content of the data sets listed in the specimen list.

Export data of the whole database

Export of the content of the entire database is possible either as a backup on the database server or as export as csv files. See the Backup chapter for more details.

Export data of selected specimens

There are several export mechanisms:

Jan 14, 2025

Subsections of Export

Diversity Collection

Export

ABCD

Outdated

Outdated but kept for compatibility.

  In the current version only the main data from DiversityCollection will be exported to ABCD.

To export the data of the specimen selected in the specimen list following the ABCD schema2.06 choose Data → Export → XML (ABCD Schema)... from the menu. A window will open where you can set some additional parameters defined in ABCD and BioCASE respectively as shown below.

To start the export click on the Start export button. The data will be exported into a file in your application directory. Click on the button to inspect the exported data (see below).

 

Apr 9, 2025

Diversity Collection

Export

Botanischer Informationsknoten Bayern

(BIB)

Outdated

Outdated but kept for compatibility.

 

To export the data of the specimen selected in the specimen list according to the Botanischer Informationsknoten Bayern choose Data → Export → Floristic lists → BIB ... from the menu. A window will open as shown below. The data sets will be exported in 2 files according to the format of BIB.

Apr 9, 2025

Diversity Collection

Export CSV

To export the tables of the database in a tabulator, comma or semicolon separated format, choose Data → Export → Export CSV... from the menu. A window as shown below will open where you can select the tables to be exported in sections Selection criteria and in the Tables for export.

A prerequisite for this export is that the bcp program is installed on your computer. This has either been installed together with the installation of SQL-Server or you have to install the Microsoft Command Line Utilities for SQL Server.

To start the export click on the Start export button. By default the data will be exported into a directory ...\Export\<database_name> below your application directory. Click on the button to select a different target directory before starting export.

 

After export the tables are marked with green background, if table schema and data were exported successfully. If only the data were exported, this is marked with yellow background, if nothing was exported, the background is red. A detailed export report can be viewed by a click on the export result file name.

Jul 5, 2024

Diversity Collection

Export Wizard

The export wizard provides a possibility to export the data selected in the main form. The data are exported as tab separated text file. The export may include transformations of the data as well as information provided by linked modules and webservices. Choose Data - Export - Export wizard from the menu and then select one of the export targets (Event, Specimen, ...). For a short introduction see the tutorial.  

Adding tables

There are the following ways to add tables:

  • One parallel table
  • Several parallel tables according to selected data
  • Dependent table

All options will include the depending tables as defined for the default table. The option for several tables will add as many tables as there are found in the data.

If you added parallel tables, you should set the sequence of the datasets within these tables: For the columns that should be used for sorting the data, set the ordering sequence to a value > 0 and choose if the ordering sequence should be ascending or descending .

Certain columns in the database may provide information linked to another table or a module resp. webservice . Click on the button to add a linked value.

Adding and editing file columns

To add columns to the exported file, use the buttons. In the textbox at the top of the file column, you can change the header for the column. To change the position of a file column use the resp. button. To fuse a column with the previous column, click in the gray bar on the left side of the column that will change to for fused columns. To remove a file column, use the button. Pre- and postfixes for the columns can directly be entered in the corresponding fields. To apply transformations on the data click on the button.  

Filter

To filter the exported data, use the filter function. Click on the button and enter the text for the filter. Only data matching the filter string will be exported. If a filter is set, the button will have a red background to remind you of the filter. The filter may be set for any number of columns you need for the restriction of the exported data.  

Rowfilter

This filter in contrast to the filter above strictly applies to the row according to the sequence of the data. For an explanation see a short tutorial Video starten.

 

Test

To test the export choose the Test tab, set the number of lines that should be included in the test and click on the Test export button. To inspect the result in a separate window, click on the button.

SQL

If you want to inspect the SQL commands created during the test check this option. To see the generated SQL click on the SQL button after the Test export. A window containing all commands including their corresponding tables will be shown.

 

Export

To export your data to a file, choose the Export tab. If you want to store the file in different place use the button to choose the directory and edit the name of the file if necessary. Check the include a schema option if you want to save a schema together with your export. To start the export, click on the Export data   button. To open the exported file, use the button.

 

Export to SQLite

To export your data into a SQLite database, choose the Export to SQLite tab. You may change the preset name of the database in order to keep previous exports. Otherwise you overwrite previous exports with the same filename. To start the export, click on the Export data   button. To view the exported data, use the button.

 

Schema

To handle the settings of your export, choose the Schema tab. To load a predefined schema, click on the button. To reset the settings to the default, click on the button. To save the current schema click on the button. With the button you can inspect the schema in a separate window.

Jul 5, 2024

Subsections of Export Wizard

Diversity Collection

Export Wizard Transformation

The exported data may be transformed e.g. to adapt them to a format demanded by the user. Click on the button to open a window as shown below. For an introduction see a short tutorial Video starten.

Here you can enter 6 types of transformation that should be applied to your data. Cut out parts,  Translate contents from the file, RegEx apply regular expressions or Replace text and apply Calculations Σ or Filters on the data from the file. All transformations will be applied in the sequence they had been entered. Finally, if a prefix and/or a postfix are defined, these will be added after the transformation. To remove a transformation, select it and click on the button.

 

Cut

With the cut transformation you can restrict the data taken from the file to a part of the text in the file. This is done by splitters and the position after splitting. In the example below, the month of a date should be extracted from the information. To achieve this, the splitter '.' is added and then the position set to 2. You can change the direction of the sequence with the button Seq starting at the first position and starting at the last position. Click on the button Test the transformation to see the result of your transformation.

With the Start at Pos. option the given splitters will be converted into space (' ') and the whole string starting with the given position will be used (see below).

 

Translate

The translate transformation translates values from the file into values entered by the user. In the example above, the values of the month should be translated from roman into numeric notation. To do this click on the button to add a translation transformation (see below). To list all different values present in the data, click on the button. A list as shown below will be created. You may as well use the and buttons to add or remove values from the list or the button to clear the list. Then enter the translations as shown below. Use the save button to save entries and the Test the transformation button to see the result. 

To load a predefined list for the transformation use the   button. A window as shown below will open. Choose the Encoding of the data in your translation source and indicate if the First line contains column definition. Click OK to use the values from the file for the translation.

 

Regular expression

The transformation using regular expressions will transform the values according to the entered Regular expression and Replace by values. For more details please see documentations about regular expressions.

 

Replacement

The replacement transformation replaces any text in the data by a text specified by the user. In the example shown below, the text "." is replaced by "-". 

 

Calculation 

The calculation transformation Σ performs a calculation on numeric value, dependent on an optional condition. In the example below, 2 calculations were applied to convert 2-digit values into 4 digit years.

 

Filter 

The filter transformation compares the values from the data with a value entered by the user. As a result you can either Export content into file or Export fixed value. To select another column that should be compared, click on the button and choose a column from the file in the window that will open. If the column that should be compared is not the column of the transformation, the number of the column will be shown instead of the symbol. To add further filter conditions use the button. For the combination of the conditions you can choose among AND and OR. 

 

 

 

 

 

 

Jul 5, 2024

Diversity Collection

Export Wizard

Tutorial

This tutorial demonstrates the export of a small sample from the database. For an introduction see a short tutorial Video starten.

Choosing the data

In the main form, select the data that should be exported (only the data displayed in the query results are exported).

Exporting the data

Choose Data → Export → Wizard → Organism ... from the menu. A window as shown below will open where the available tables for export are listed in the upper left area. To show the data columns of a table, select this table in the list.

 

Adding additional tables

In this example, we want to add as many parallel identification tables as present in the data. To do this, click on the button of the Identification table. At the end of the list (depending on your data) the additional tables are added (see below).

 

Setting the sequence for the tables

To set the sequence of the Identifications, select the first table and for the column IdentificationSequence set sorting sequence to 1 and the direction for sorting to descending

 

Choosing data from linked modules

Some columns provide the possibility to add data from linked tables or modules. In this example we choose the column NameURI linking to the module DiversityTaxonNames (see below).

To provide linked values, click on the button. A window as shown below will open, where you can choose among the provided services.

After the service is selected, you will be asked for the value provided by the service (see below).

Now the selected link is added underneath the column as shown below. You can add as many links as you need for your export.

For some modules there are values that refer to other modules with a name like [Link to ...] as shown in the example below.

If you select one of theses values, you will be asked to select the service or database linked to this modul (see below)

... and then to select one of the provided columns (see below)

Within the form this linked values will be marked as shown below. If several results are retrieved these will be separated with by " | ".

 

Adding columns to the file

To add columns to the exported file, click on the buttons for the columns resp. linked values. In this example select all Family values and the TaxonomicName (see below).

 

Fusing columns

The families should appear as one column and as the sources can exist only once for each identification we can fuse these columns. To do so, click on the delimiters between these columns (see below).

 

Setting the headers

By default the headers for the exported data are set according to the names of the columns in the database. To change this, edit them as shown below where TaxonomicName has been changed to Taxon (see below). For fused columns only the header in the first column will be used.

 

Testing

To test the export, click on the Test export button. The result depends on the content in your data but should look similar as shown below.

 

Export

To finally export the data, choose the Export tab. By default the data will be exported into tab separated file in a directory in the application directory (see below). You can change the directory (click on the button). You can choose the Include schema option to create a schema that you may reuse in a later export.

Jul 5, 2024

Diversity Collection

Export

Global Plant Initiative

(JSTOR)

To export the data of the specimen selected in the specimen list according to the Global Plant Initiative / JSTOR choose Data → Export → XML  → GPI / JSTOR ... from the menu. A window will open where you can set some additional options for the export (see below). The data sets will be exported according to the JSTOR Plant Science Handbook (June 2011).

If the data does not fulfill the criteria of the Global Plant Initiative / JSTOR, the errors will be listed as shown below. You have to fix these errors in your data to create a valid export file. To start the export click on the Start export button. The data will be exported into a file in your application directory. Click on the button to inspect the exported data (see below).

 

If the data are not [restricted to names linked to a thesaurus] (see option in image above), the export will take information like the family from the linked thesaurus if available (e.g. DiversityTaxonNames). Otherwise information stored in DiversityCollection will be used (if available). If neither is available the export will insert a message like "not assigned" and the error report will contain a message like "Family is missing".

Dec 1, 2024

Diversity Collection

Label

Select the printer in the header menu to switch to the printing mode. If your specimen contains more than one part, choose the part of the specimen for which the label should be generated. The sequence is shown in the image below and in a short tutorial .

 

Additional information about a label is entered in the label section (see image below). The title may contain a longer text that can be displayed by switching from a combobox to a textbox using the resp. button to return to the combobox. The data are stored in the table CollectionSpecimen.

 

The organisms of a specimen are printed on a label according to the display order.

Schema

If you do not select a schema file, i.e. the textbox Schema file: is empty, you will see the generated XML-file as shown in the image below. The XML file is the base for all label types you wish to generate. To create your own labels simply design your own XSLT-schema file . See e.g. http://www.w3.org/TR/xslt for further information about schema files.

To print a label for a specimen you have to select a schema file. There are default schema files available in the folder LabelPrinting/Schemas in your application directory (see below). This is the default place to store schema files.

Click on the  button to open the directory. You will find several prepared schema files among which you can choose or change them to your own needs or create new ones respectively. The schema file /LabelPrinting/Schemas/Templates/LabelTemplates.xslt provides templates for the other schema files. If this file is missing the generation of the label may fail and you will get a warning. You may give a title for the print in the field Title. From the Collection and MaterialCategory available for the selected specimen choose one from the list (Coll./Mat.). To generate the label for the current specimen click on the  button. To generate labels for all specimens selected in your query click on the  button (you may use the button to select all specimens). If you need duplicates of your labels change the number in the duplicates box to the desired value. You can print 1 - 99 duplicates of one label. If there are more than 20 specimens in the list, you receive a warning whether you really wish to create all these labels as this could be somewhat time consuming. The labels are generated as XML files with XSLT-schema files, transformed to HTML-files and depicted in a browser. To print the label click on the  button.

Duplicates

If you wish to print labels for duplicates which are stored in a different collection, the duplicate should be a child of the original specimen as shown in the example below.

 

Depending on the schema you use, the label will be marked as duplicate and contain a reference to the original specimen (see below).

Save

If you wish to save the generated files for later printing, click on the  button to do so. Note that the program will by default create a file Label.xml and in case a schema file is specified a file Label.htm in the LabelPrinting directory which will be overwritten every time you generate a new label. Thus, you need to save the file under a different name or in a different directory to prevent the program to erase this data.

If you wish to print labels for all the specimens in the specimen list, you can restrict these to the collection and the material category of the current specimen part (see image above).

Accession number

If you wish to reformat the accession number, you may choose among the options provided by the program, e.g. conversion of arabic to roman numbers (BSPG-1988-007-00001 → BSPG-1988-VII-00001). Select the format from the combobox Conversion shown above.

 

Codes

For a short tutorial about the inclusion of codes in the label see a short tutorial .

Code 39

If you use Code 39 for your labels and wish to print the barcodes on the labels, you need the font  , which is included in the DiversityCollection package. Place this font in the folder where your fonts are stored (e.g.: C:\WINNT\Fonts). If the font is not available, the barcode will appear as the accession number between two '*' signs. If this font does not do the job you may try other fonts, e.g. code 39 fromlogitogo. Download the font, copy it into your fonts directory and adapt the xslt file according to the line below: <xsl:variable name=\"FontBarcode\"\> font-size: 10pt; font-family:[Code-39-Logitogo]\</xsl:variable\>

QR-code

The QR-codes are restricted to labels for specimen parts. Select a part in the lower tree to enable the QR-codes.

To include a QR-Code in the label, activate the QR-Code generator and select the source for the QR code. For certain sources you can specify the type of the source (see below).

  • AccessionNumber
  • CollectorsEventNumber
  • DepositorsAccessionNumber
  • ExternalIdentifier
  • PartAccessionNumber
  • StableIdentier
  • StorageLocation

Depending on your XSLT-schema the QR code will appear in your label (see below). By Default the QR-Codes are generated via a an Api provided by the SNSB IT-Center using a python library, which is only available if you have access to the Internet. The created QR-Code images will be stored in the folder LabelPrint/img with the filenames corresponding to the ID of the specimen part. This folder will be cleared for every printout. So if you want to keep the label you need to copy the created file Lable.html together with the folder img.

You can change the default size and the default service for generating the QR-code. Use the context menu of the QR-code button to open a window where you can enter either the size or the template of your preferred service as in the example shown below where the parameter {0} corresponds to the text that should be coded e.g. the accession number (as selected in the interface) and parameter {1} the size in pixel (as integer) for the QR code.

https://services.snsb.info/qrcode/?size={1}&text={0}

Mar 20, 2025

Diversity Collection

Export

Naturgucker

Outdated

Outdated but kept for compatibility.

  To export the data of the specimen selected in the specimen list according to naturgucker choose Data → Export → Floristic lists → Naturgucker ... from the menu. A window will open as shown below. The data sets will be exported in a file according to the format of Naturgucker. In the form you can choose among the taxonomic groups and analysis provided in the selected data.

Apr 9, 2025

Diversity Collection

Cache Database

The cache databases for DiversityCollection are designed as sources for preformatted data for publication in e.g. public user portals like GBIF. For an introduction see a short tutorial   . The cache database by default has a name corresponding to the main source database, e.g. DiversityCollectionCache and is located on the same server and by itself is the source for the data in Postgres (Version 9.4 or above) cache databases located on any Windows or Linux server (see image below). An overview for the basic steps is provided in chapter Basic steps forpublication of data via the cache database.

 

Generating the cache database

To create a cache database you need to be a system administrator (s. Login administration). The creation of the cache database is described in the chapter Creation of the cache database.

 

Projects

The publication and transfer of the data is always related to a project. Every project has its own database schema containing the data tables etc. The metadata are defined via settings in a DiversityProjects database. The Projects module provides a stable identifier for each Project. The basic address has to be set in the Project module (choose Administration - Stable identifier ... in the menu). Please turn to the module DiverisityProjects for further information. The metadata will be transferred into a table in the cache database. For further details see chapter Projects in the cachedatabase.

 

Scientific terms, agent, taxonomy and other sources

As well as data from DiversityCollection, data from other modules like DiversityScientificTerms containing terms, DiversityTaxonNames containing the taxonomy, including accepted names and synonyms are transferred into the cache database and may be retrieved from the local server or a linked server. The data of these sources are stored and transferred independent from the project data. For further details see the chapters about agents, terms and taxonomy.

 

Jan 14, 2025

Subsections of Cache Database

Diversity Collection

Data Flow

Import / Export - example for a data flow

In the image below, an expample for a data flow from the original source to the final GBIF-portal is shown. As a first step the data are imported via the Import wizard are imported into the database. After the data are given free for publication, they are transferred into the cachedatabase .  From there they are transferred into a Postgresdatabase containing a package for conversion into ABCD. Finally the BioCASE tool for mapping the data is used to provide the data for GBIF.

Jan 14, 2025

Cache Database

Tutorial

Basic steps for publication of data via the cache database

1 - Create the cache database

To create a cache database as shown in a short tutorial and in the chapter Creation of the cachedatabase you need to be a system administrator (s. Login administration). After this step the cache database should be available and you can create a Postgres database as final target of your data.

2 - Create a Postgres database

The final formatting of the data e.g. for publication via webservice are performed in a Postgres database. If no server providing Postgres is available, you may install Postgres on your local machine (see https://www.postgresql.org/ for further information). The creation and administration of a Postgres database is described in a short tutorial and in chapter Administration of the Postgres cachedatabases.

3 - Insert sources for taxonomic names, scientific terms, agents etc.

This step is optional and depends upon the availability of a source for e.g. taxonomic names. You may either use sources from your local server or the public available sources provided by tnt.diversityworkbench.de (turn to http://www.snsb.info for further information). For a introduction see a short tutorial . The needed settings are described in chapter Sources from othermodules.  

4 - Insert a project

The data published in the cache database are organized according to the projects. Add a project as shown in a short tutorial and described in chapter Projects in the cachedatabase. In the source database, make sure that the data within this project are not withheld from publication (see chapter Availability of data sets for more details) and that the ranges you want to publish are set properly (see chapter Restrictions for the datatransfer into the cachedatabase).  

5 - Transfer the data

The final transfer of the data is described in chapter Sources for other modules and chapter Transfer of the data.

6 - Publish

Publish or export the data

To export the data or prepare them for publication according to the specifications of webservices etc. the data frequently need to be formatted. This is done with packages as described in chapter Administration of the Packages.

7 - BioCASe

Map data via BioCASe (only for ABCD consuming publishers like GBIF)

For publishers using ABCD like GBIF, use the BioCASe provider software and mapping tool to link the data formatted with the ABCDpackage.   

Jan 14, 2025

Create Cache Database

Creation of the cache database

To create a cache database you need to be a system administrator (s. Login administration). To create the cache database, choose Data - Cache database ... from the menu. If so far no cache database exists, you will be asked if a new one should be generated. Next you have to select the corresponding DiversityProjects database placed on the same server. If the stable identifier has not been defined in this DiversityProjects database, you get a message, that this has to be done first. Please see the manual of DiversityProjects for details. Next you have to select the corresponding DiversityAgents database placed on the same server. Finally you are asked for the name of the Cachedatabase. We recommend to accept the suggestion shown in the dialog. After the generation of the cache database a window as shown below will open. For an introduction see a short tutorial .

Click on the Update button to update the database to the latest version. A window as shown below will open. Click on Start update to execute all the scripts needed for the latest version of the database.

During the update you may encounter under certain circumstances the message that the test of the generic functions failed (see below).

The most probable reason for this is that the name of your projects database does not correspond to the specifications of the update-script. This error can easily be fixed. As an administrator use the Microsoft SQL Server Management Studio. In the directory of your cache database select the Scalar-valued Function dbo.ProjectsDatabase()

... and use Modify from the context menu. In the Code of the function (see below) change the last set @DB = ... to the real name of your projects database.

The result may look as shown below. After the change, press F5 to execute the script.

After the function returns the correct name of the ProjectsDatabase, the update script should proceed without further error messages.

Jan 14, 2025

Cache Database

Logins

Cache database - User administration

There are 2 roles in the cache database with a general access to the data: CacheAdmin (for the administration and transfer of the data) and CacheUser (with read only access).

To administrate the logins in the SQL-Server database, click on the button to open a window as shown below. To administrate the access for other logins, you have to be a System administator. For further details please see the chapter about the login administration for the main database.

 

Postgres database

To handle the logins and user groups on the Postgres database server, click on the button. A window as shown below will open, where you can create and delete logins and groups. For the logins you can change their membership in groups and their properties (see below). On the left you find 2 lists, with the upper list containing the logins and the list below with the groups resp. roles. For the logins you can set the general properties as shown below. The login postgres is created with the installation of the database and is the login for the administration of the database including the updates etc. For details about predefined properties like Is superuser, please turn to the Postgresdocumentation

In the Membership in groups area you can define the groups in which the login is a member (see below). 

For the groups you can change their membership in other groups and their permissions (see below). 

Jun 4, 2024

Cache Database Configuration

Configuratation of the cache databases

The cache databases for DiversityCollection are designed as sources for preformated data for publication in e.g. public user portals like GBIF. There may be several cache databases which can be located on several servers. The restrictions of the published data are defined in the main database via projects, data withholding and embargos. The publication of the data is allways related to a project, defined in DiversityProjects, holding the metadata that will be transfered into the cache database. Therefore every dataset copied from the source into the cache database contains a reference to the project (ProjectID). The publication of the data includes several steps:

  • Setting of restrictions within the original data with data withholding
  • Selection of the project
  • Transfer of the data into the cache database
  • Conversion of the data into the format required by the portal

In Addition to the data transfered from DiversityCollection, the data for the taxonomy has to be transfered from the relevant sources. The links to these sources and the project dependent retrieval are stored in the cache database.

The image below gives an overview for the process described above.

To configure your cache databases, choose Administration → Cache database from the menu. A window will open as shown below.

 

Creation of a cache database

If no cache database has been defined so far, use the button to create a new cache database. You have to be a System administrator to be able to create a cache database. You will be asked for the server, the port used by the server, the directory of the database files, the name of the new cache database and finally the name of the projects database where the metadata of the projects transfered into the cache database are stored.

To delete a once created cache database, use the button. 

 

Updates of the cache database

After the new cache database has been created or if you select an outdated cache database, a button Update database will appear, instructing you to run updates for the cache database. Click on the button to open a window as shown below. 

All update scripts for the database will be listed. Click on the Start update button to update the database to the current version. 

 

Login administration

To handle the data for the cache database a user needs access to the data on the source database, the cache database, the project database and the taxon databases. To administrate the users that can transfer data into the cache database use the button Login administration. For details see the chapter Loginadministration

 

Configuration, Projects

Data transfer to the cache database is linked to projects . To add a project of which the data should be transfered into the cache database click on the button. For every project that should be transferred you have several options for configuration:

  • Restriction of transfered taxonomic groups
  • Restriction of transfered material categories
  • Restriction of transfered localisations
    • Restriction of the precision of the coordinates
  • Restriction of transfered images

Data types handle the data for the cache database. A user needs access to the data in the [source] database, the [cache] database, the [project] database and the [taxon] databases. To administrate the users who can transfer data into the cache database, use the button Login administration. For details see the chapter Login administration

Restriction

  • Taxonomic groups
  • Material categories
  • Localisation systems
  • Images

To restrict the Taxonomic groups, Material catagories, Localisation systems or Images that are transferred to the cache database choose the corresponding options and select those that should be transferred into the cache database in the tab pages that are added. 

Coordinate precision

To reduce the precision of the coordinates of the localisation systems transferred to the cache database you can check the corresponding option and determine the number of digits after the decimal point. 

 

Taxonomy

The collection data may be linked to sources holding taxonomic information ( DiversityTaxonNames). To provide this information add all sources used in your collection data and transfer the corresponding data into the cache database. The data in the taxonomic sources are organized by projects, thus, you need to provide the sequence of the projects that should be imported into the cache database for every source. A name will be imported only once. This means that the name with synonymy to the first imported project will be imported, all following data with this name will be ignored.

 

Jan 14, 2025

Anonym Colletors

Anonymous collectors

If collectors should be published as an anonym string, edit the Anonymous collectors list. Use the > button to move a collector from the selected project into the list of anonymous collectors. To remove a collector from this list, just delete it from the table (see below).

In the cache database these collectors will be translated into the selected Anonymisation and a number, e.g. Anonymus 1. So the data of one collector can still be recognized without revealing the name of the collector.

 

 

 

 

May 3, 2024

Cache Database

Linked Server

Transfer of data to Postgres via linked server

For projects with great amounts of data the preferred way to transfer data is a linked server. To use a linked server you have too install the ODBC driver software for Postgres on your SQL-Server, e.g. provided here: postgresql. Download and install the software, e.g.:

 

After the software has been installed, add a ODBC datasource.

Configured to access your Postgres cache database.

Now you can add a linked server in the SQL-Server Management Studio (see below). 

Configure the linked server using Microsoft OLE DB provider for ODBC Drivers and the new created ODBC source as Data source (see below).

Now you are prepared to transfer your data on the fast route to the postgres database.

 

Configure the linked server using Microsoft OLE DB provider for ODBC Drivers and the new created ODBC source as Data source (see below).ow you can add a linked server in the SQL-Server Management Studio (see below). edit the general settings for the transfer, click on the  button in the main form. A window as shown below will open. Here you can set the timeout for the transfer in minutes. The value 0 means that no time limit is set and the program should try inifinite to transfer the data. Furthermore you can set the parameters for the transfer of the data in chunks. If the amount of data is above a certain threshold, it is faster to devide the data into smaller chunks. The threshold for transfer into the cache database and into the Postgres database can be set as shown below, together with the maximal size of the chunks.

 

The scheduled transfer is meant to be lanched on a server on a regular basis, e.g. once a week, once a day, every hour etc. . The transfer of the data via the scheduled transfer will take place according to the settings. This means the program will check if the next planned time for a data transfer is passed and only than start to transfer the data. To include a source in the schedule, check the selector for the scheduler. To set the time and days scheduled for a transfer, click on the button. A window as shown below will open where you can select the time and the day(s) of the week when the transfer should be executed.

 

The planned points in time a shown in the form as shown below.

 

The protocol of the last transfer can seen as in the window above or if you click on the button. If an error occurred this can be inspected with a click no the button.

If another transfer on the same source has been started, no further transfer will be started. In the program this competing transfer is shown as below.

You can remove this block with a click on the button. In opening window (see below) click on the button. This will as well remove error messages from previous transfers.

 

A further option for restriction of the transfers is the comparision of the date when the last transfer has been executed. Click on the button to change it to . In this state the program will compare the dates of the transfers and execute the transfer only if new data are available.

 

 

 

 

 

Jun 4, 2024

Cache Database

Projects

Projects in the cache database

The data transferred into the [cache database] are always transferred according to a project they belong to. If no projects were added so far the window will appear like shown below. For an introduction see a short tutorial .

To add a new project for the transfer into the cache database, click on the Add project button. In the area below a new entry as shown below will appear. The area on the right shows the number of datasets in the project in the [source database] together with the date of the last update. To ensure the separation of the data between the projects, DiversityCollection creates a separate schema for every project named Project_[name of the project] together with needed roles, tables etc..

In case there are projects where you do not have access to, this will be indicated as shown below.

In case a project has been renamed in the main database, a button will appear as shown below. The displayed name corresponds to the name in the main database. To see the original name, click on the button.

 

Before transferring data you have to update the project schema to the latest version, indicated by the appearance of an update button . Click on the button to open a window as shown below. Click on the Start update button to update the schema to the latest version.

After the update the database is ready to transfer data into. 

Besides the restrictions in the source database, you can set further restrictions for this transfer. Click on the button to edit the datawithholding reasons for the data of the project. Click on the button and choose the ranges of the data that should be transferred (see below).

To transfer the data you have 3 options as described in the Transfer chapter.

Afterwards the number and date of the transferred data are visible as shown below.

To inspect the transferred data use the View content button. A window as shown below will open where all tables containing the data of the project are listed.

Click on the button to filter the content. A window as shown below will open. Choose the column for the filter, the operator (e.g. = ) and the filter value (see below).

Now click on the button to add the filter criteria to the table filter. You may add as many criteria as needed (see below). With the button you can clear the filter..

Before you can transfer the data into the Postgresdatabase, you have to connect to the Postgres database and click on the button to establish the project and run necessary updates . After the project is established and up to date, use the button to transfer the data in the Postgres area (see below).

If a project is exported into another Postgres database on the same server, these databases will be listed underneath the Postgres block (see image below). For an overview of all target Postgres databases click on the button.

If the target is placed on the current server, the text will appear in black (see image below). Packages will be listed for the other targets as well.

 

In the Postgres database you can install packages to adapt the data to any needed format.

 

 

 

 

 

Jan 14, 2025

Cache Database

Diagnostics for the cache database

To test data completeness of data targets you can use the diagnostics . Choose the project and the target you want to test and start the diagnostics. If the data in a postgres database should be included in the test, please connect to this database before starting the test. The result of the diagnose as shown below marks missing information. 

 

May 3, 2024

Diversity Collection

Cache database

Infrastructure

For the administration of the data that are published via the cache database, certain tables as shown below are used. These are either placed in the schema dbo or a schema named according to the published project, e.g. Project_Test for a project with the name Test. 

Central tables

There are a number of tables placed in the schema dbo that are accessible by all projects. 

Project tables

The central project tables contain the information about the projects that are published together with the target (Postgres) databases and the packages including optional add-ons into which they had been transferred. This information is used to ensure a recovery in case of a loss of the targets.

 

 

Source tables

To access sources from other modules (e.g. DiversityAgents) there are tables for the storage of the principal access to the modules and a number of tables containing the data (depending on the module).

Access tables

These tables contain the principal access like the name of the view defined to access the data. The example below lists the tables defined for the module DiversityAgents, but there are corresponding tables for every module accessed by the cache database. 

Data tables

These tables contain the data provided by the module and therefore depend on the module. The example below lists the tables defined for the module DiversityAgents, but there are corresponding tables for every module accessed by the cache database. 

To access the data in the module there are views generated by the client. The name of these views are composed according to the name of the database, the server and the project to ensure a unique name. These are stored in the table AgentSource and are used by the client for a transfer of the data from the module database into the tables in the cache database. The example below lists the views for the module DiversityAgents. 

Project tables

These tables contain the data of the projects with every project having its own schema. These tables correspond to the tables in the main database of the module with certain limitations (no logging columns, internal notes etc.)

Project procedures for the data transfer into the project tables

For every project table there is a procedure that transfers the data from the main database into the cache table. The names of these procedures are procPublish + the name of the table in the main database e.g. procPublishAnalysis for the transfer from the table Analysis into the table CacheAnalysis.

 

Jan 14, 2025

Subsections of Infrastructure

Diversity Collection

Cache database

TABLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table Agent

The main table with the data of the agent

Column Data type Description Nullable Relation
BaseURL varchar (500) The basic URL as defined in the module database NO -
AgentID int Unique ID for the Agent (= Primary key) NO -
AgentURI varchar (255) The link to the dataset, i. e. the BaseURL + the AgentID YES -
AgentParentID int The AgentID of the superior agent if agents are organized within a hierarchy YES -
AgentName nvarchar (200) The whole name of the agent as shown e.g. for selection in an user interface. For persons this entry will be generated as follows: LastName, FirstNames, AgentTitle NO -
AgentTitle nvarchar (50) The title of the agent, e.g. Dr., Prof. YES -
GivenName nvarchar (255) The first names of the agent (if a person) or the name of e.g. an institution YES -
GivenNamePostfix nvarchar (50) Variable part of name, correctly placed at end of given names YES -
InheritedNamePrefix nvarchar (50) Variable part of name, correctly placed at the beginning of the inherited names YES -
InheritedName nvarchar (255) The last names of the agent (if a person) YES -
InheritedNamePostfix nvarchar (50) Additions after inherited name, like generation (Jr., III.) or names of religious orders YES -
Abbreviation nvarchar (50) Abbreviation of the agent YES -
AgentType nvarchar (50) The type of the agent, e.g. person, company YES -
AgentRole nvarchar (255) The role of an agent esp. a person within an organization. e.g. “Database Administrator” or “Curator” YES -
AgentGender nvarchar (50) The gender resp. sex of the agent YES -
Description nvarchar (1000) A description of the agent YES -
OriginalSpelling nvarchar (200) Name as originally written in e.g. chinese or cyrillic letters YES -
Notes nvarchar (MAX) Notes about the agent YES -
ValidFromDate datetime The date of the begin of the exsistence of the agent, e.g. the birthday of a person or the founding of an institution, calculated from ValidFromDay, - Month and -Year YES -
ValidUntilDate datetime The date of the end of the exsistence of the agent, e.g. death of a person or closing of an institute, calculated from ValidUntilDay, - Month and -Year YES -
SynonymToAgentID int The AgentID of the agent which was selected as a replacement for the current agent, e.g. if to equal datasets were imported from different sources YES -
ProjectID int The ID of the project in the module database containing the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
SourceView nvarchar (200) The name of the source view of the data NO -

Table AgentContactInformation

The contact information resp. addresses of the agents

Column Data type Description Nullable Relation
AgentID int Refers to the ID of Agent (= Foreign key and part of primary key) NO -
DisplayOrder tinyint Display order of records in user interface. DisplayOrder 1 corresponds to the preferred address (= part of primary key) NO -
AddressType nvarchar (50) Type of the adress, e.g. private YES -
Country nvarchar (255) Country of the address YES -
City nvarchar (255) City of the address YES -
PostalCode nvarchar (50) ZIP or postcode of the address (usually output before or after the city) YES -
Streetaddress nvarchar (255) Usually street name and number, but may also contain post office box YES -
Address nvarchar (255) Free text postal address of the agent YES -
Telephone nvarchar (50) Phone number, including area code YES -
CellularPhone nvarchar (50) The number of a mobile telephone device of the agent YES -
Telefax nvarchar (50) Fax number, including area code YES -
Email nvarchar (255) E-mail address of the agent YES -
URI nvarchar (255) URI pointing to a homepage containing further information YES -
Notes nvarchar (MAX) Notes about this address YES -
ValidFrom datetime The date when this address became valid as date according to ISO 8601 YES -
ValidUntil datetime The date of the expiration of the validity of this address as date according to ISO 8601 YES -
SourceView nvarchar (200) The name of the source view of the data NO -
BaseURL varchar (500) - NO -

Table AgentIdentifier

Column Data type Description Nullable Relation
AgentID int - NO -
Identifier nvarchar (190) - NO -
IdentifierURI varchar (500) - YES -
Type nvarchar (50) - YES -
Notes nvarchar (MAX) - YES -
SourceView varchar (128) - NO -
BaseURL varchar (500) - NO -

Table AgentImage

Column Data type Description Nullable Relation
AgentID int - NO -
URI varchar (255) - NO -
Description nvarchar (MAX) - YES -
Type nvarchar (50) - YES -
Sequence int - YES -
SourceView varchar (128) - NO -
BaseURL varchar (500) - NO -

Table AgentSource

The sources for the data from a module database accessed via a view defined in the cache database

Column Data type Description Nullable Relation
SourceView nvarchar (200) the name of the view retrieving the data from the database NO -
Source nvarchar (500) The name of the source, e.g. the name of the project as defined in the source module YES -
SourceID int The ID of the source, e.g. the ID of the project as defined in the source module YES -
LinkedServerName nvarchar (500) If the source is located on a linked server, the name of the linked server YES -
DatabaseName nvarchar (50) The name of the database where the data are taken from YES -
Subsets nvarchar (500) Subsets of a source: The names of the tables included in the transfer separted by " " YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES -
LastUpdatedWhen datetime The date of the last update of the data YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Version int -Default value: (0) YES -

Table AgentSourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
SourceView nvarchar (200) SourceView as defined in table AgentSource NO Refers to table AgentSource
Target nvarchar (200) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO -
LastUpdatedWhen datetime The date of the last update of the project data YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -

Table AgentSourceView

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
AgentID int - NO -
SourceView nvarchar (128) The name of the source view of the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -

Table bcpPostgresTableDefinition

Column Data type Description Nullable Relation
SchemaName varchar (200) - NO -
TableName varchar (200) - NO -
ColumnName varchar (200) - NO -
DataType varchar (50) - YES -
OrdinalPositon int - YES -

Table Gazetteer

Column Data type Description Nullable Relation
BaseURL varchar (255) - NO -
NameID int - NO -
Name nvarchar (400) - NO -
LanguageCode nvarchar (50) - YES -
PlaceID int - NO -
PlaceType nvarchar (50) - YES -
PreferredName nvarchar (400) - NO -
PreferredNameID int - NO -
PreferredNameLanguageCode nvarchar (50) - YES -
ProjectID int - NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
SourceView nvarchar (200) The name of the source view of the data NO -
NameURI varchar (255) - YES -
ExternalNameID nvarchar (50) - YES -
ExternalDatabaseID int - YES -

Table GazetteerExternalDatabase

Column Data type Description Nullable Relation
ExternalDatabaseID int - NO -
ExternalDatabaseName nvarchar (60) - NO -
ExternalDatabaseVersion nvarchar (255) - NO -
ExternalAttribute_NameID nvarchar (255) - YES -
ExternalAttribute_PlaceID nvarchar (255) - YES -
ExternalCoordinatePrecision nvarchar (255) - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table GazetteerSource

Column Data type Description Nullable Relation
SourceView nvarchar (200) the name of the view retrieving the data from the database NO -
Source nvarchar (500) - YES -
SourceID int - YES -
LinkedServerName nvarchar (500) If the source is located on a linked server, the name of the linked server YES -
DatabaseName nvarchar (50) The name of the database where the data are taken from YES -
Subsets nvarchar (500) Subsets of a source: The names of the tables included in the transfer separted by " " YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES -
LastUpdatedWhen datetime The date of the last update of the data YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Version int -Default value: (0) YES -

Table GazetteerSourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
SourceView nvarchar (200) SourceView as defined in table GazetteerSource NO Refers to table GazetteerSource
Target nvarchar (200) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO -
LastUpdatedWhen datetime The date of the last update of the project data YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -

Table GazetteerSourceView

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
NameID int - NO -
SourceView nvarchar (128) The name of the source view of the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -

Table ProjectPublished

The projects published via the cache database (Details about the projects are defined in DiversityProjects)

Column Data type Description Nullable Relation
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO -
Project nvarchar (50) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects) YES -
CoordinatePrecision tinyint Optional reduction of the precision of the coordinates within the project YES -
ProjectURI varchar (255) The URI of the project, e.g. as provided by the module DiversityProjects. YES -
LastUpdatedWhen datetime The date of the last update of the project data YES -
LastUpdatedBy nvarchar (50) The user reponsible for the last update. YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transfer YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Restriction nvarchar (MAX) An additional restriction of the content of the published data YES -

Table ProjectTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectPublished
LastUpdatedWhen datetime The date of the last update of the project data YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
TargetID int The ID of the server, relates to table Target NO Refers to table Target
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
UseBulkTransfer bit If the bulk transfer should be used for the transfer of data YES -

Table ProjectTargetPackage

Packages for projects as documented in the table Package in the Postgres database

Column Data type Description Nullable Relation
ProjectID int Refers to ProjectID in table ProjectTarget NO Refers to table ProjectTarget
TargetID int Referes to TargetID in table ProjectTarget NO Refers to table ProjectTarget
Package nvarchar (50) Package installed for this project target NO -

Table ProjectTargetPackageAddOn

The installed add-ons for packages

Column Data type Description Nullable Relation
ProjectID int Refers to ProjectID in table ProjectTarget NO Refers to table ProjectTargetPackage
TargetID int Referes to TargetID in table ProjectTarget NO Refers to table ProjectTargetPackage
Package nvarchar (50) Package installed for this project target NO Refers to table ProjectTargetPackage
AddOn nvarchar (50) Add-on installed for this package NO -

Table ProjectTransfer

The transfers of data of a project

Column Data type Description Nullable Relation
ProjectID int ID of the project, part of PK NO Refers to table ProjectPublished
TransferDate datetime Date of the transfer. Part of PKDefault value: getdate() NO -
ResponsibleUserID int The ID of the user as stored in table UserProxy of the source database, responsible for the transferDefault value: (-1) YES -
TargetID int If the transfer regards a postgres database, the ID of the target (= Postgres database) as stored in table Target YES Refers to table Target
Package nvarchar (50) If the transfer regards a package, the name of the package, otherwise empty YES -
Settings nvarchar (MAX) The versions, number of transfered data etc. of the objects concerned by the transfer [format: JSON] YES -

Table ReferenceRelator

Column Data type Description Nullable Relation
RefID int - NO -
Role nvarchar (3) - NO -
Sequence int - NO -
Name nvarchar (255) - NO -
AgentURI varchar (255) - YES -
SortLabel nvarchar (255) - YES -
Address nvarchar (1000) - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table ReferenceTitle

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
RefType nvarchar (10) - NO -
RefID int - NO -
RefDescription_Cache nvarchar (255) - NO -
Title nvarchar (4000) - NO -
DateYear smallint - YES -
DateMonth smallint - YES -
DateDay smallint - YES -
DateSuppl nvarchar (255) - NO -
SourceTitle nvarchar (4000) - NO -
SeriesTitle nvarchar (255) - NO -
Periodical nvarchar (255) - NO -
Volume nvarchar (255) - NO -
Issue nvarchar (255) - NO -
Pages nvarchar (255) - NO -
Publisher nvarchar (255) - NO -
PublPlace nvarchar (255) - NO -
Edition smallint - YES -
DateYear2 smallint - YES -
DateMonth2 smallint - YES -
DateDay2 smallint - YES -
DateSuppl2 nvarchar (255) - NO -
ISSN_ISBN nvarchar (18) - NO -
Miscellaneous1 nvarchar (255) - NO -
Miscellaneous2 nvarchar (255) - NO -
Miscellaneous3 nvarchar (255) - NO -
UserDef1 nvarchar (4000) - NO -
UserDef2 nvarchar (4000) - NO -
UserDef3 nvarchar (4000) - NO -
UserDef4 nvarchar (4000) - NO -
UserDef5 nvarchar (4000) - NO -
WebLinks nvarchar (4000) - NO -
LinkToPDF nvarchar (4000) - NO -
LinkToFullText nvarchar (4000) - NO -
RelatedLinks nvarchar (4000) - NO -
LinkToImages nvarchar (4000) - NO -
SourceRefID int - YES -
Language nvarchar (25) - NO -
CitationText nvarchar (1000) - NO -
CitationFrom nvarchar (255) - NO -
LogInsertedWhen datetime -Default value: getdate() YES -
ProjectID int - NO -
SourceView nvarchar (200) - NO -
ReferenceURI varchar (255) - YES -
AuthorsCache nvarchar (1000) - YES -

Table ReferenceTitleSource

Column Data type Description Nullable Relation
SourceView nvarchar (200) the name of the view retrieving the data from the database NO -
Source nvarchar (500) - YES -
SourceID int - YES -
LinkedServerName nvarchar (500) If the source is located on a linked server, the name of the linked server YES -
DatabaseName nvarchar (50) The name of the database where the data are taken from YES -
Subsets nvarchar (500) Subsets of a source: The names of the tables included in the transfer separted by " " YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES -
LastUpdatedWhen datetime The date of the last update of the data YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Version int -Default value: (0) YES -

Table ReferenceTitleSourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
SourceView nvarchar (200) SourceView as defined in table ReferenceSource NO Refers to table ReferenceTitleSource
Target nvarchar (200) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO -
LastUpdatedWhen datetime The date of the last update of the project data YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -

Table ReferenceTitleSourceView

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
RefID int - NO -
SourceView nvarchar (128) The name of the source view of the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -

Table SamplingPlot

Holds cached data from DiversitySamplingPlots as base for other procedures.

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
PlotID int - NO -
PartOfPlotID int - YES -
PlotURI nvarchar (255) - YES -
PlotIdentifier nvarchar (500) - YES -
PlotGeography_Cache nvarchar (MAX) - YES -
PlotDescription nvarchar (MAX) - YES -
PlotType nvarchar (50) - YES -
CountryCache nvarchar (50) - YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
ProjectID int - YES -
SourceView nvarchar (200) The source of the data,i.e. the name of the view in the database NO -

Table SamplingPlotLocalisation

Column Data type Description Nullable Relation
PlotID int - NO -
LocalisationSystemID int - NO -
Location1 nvarchar (255) - YES -
Location2 nvarchar (255) - YES -
LocationAccuracy nvarchar (50) - YES -
LocationNotes nvarchar (MAX) - YES -
Geography nvarchar (MAX) - YES -
AverageAltitudeCache float - YES -
AverageLatitudeCache float - YES -
AverageLongitudeCache float - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table SamplingPlotProperty

Column Data type Description Nullable Relation
PlotID int - NO -
PropertyID int - NO -
DisplayText nvarchar (255) - YES -
PropertyURI varchar (255) - YES -
PropertyHierarchyCache nvarchar (MAX) - YES -
PropertyValue nvarchar (255) - YES -
Notes nvarchar (MAX) - YES -
AverageValueCache float - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table SamplingPlotSource

Column Data type Description Nullable Relation
SourceView nvarchar (200) the name of the view retrieving the data from the database NO -
Source nvarchar (50) - YES -
SourceID int - YES -
LinkedServerName nvarchar (400) If the source is located on a linked server, the name of the linked server YES -
DatabaseName nvarchar (400) The name of the database where the data are taken from YES -
Subsets nvarchar (500) List of additional data transferred into the cache database separated by YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES -
LastUpdatedWhen datetime The date of the last update of the dataDefault value: getdate() YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Version int -Default value: (0) YES -

Table SamplingPlotSourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
SourceView nvarchar (200) SourceView as defined in table SamplingPlotSource NO Refers to table SamplingPlotSource
Target nvarchar (200) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO -
LastUpdatedWhen datetime The date of the last update of the project dataDefault value: getdate() YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -

Table SamplingPlotSourceView

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
PlotID int - NO -
SourceView nvarchar (128) The name of the source view of the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -

Table ScientificTerm

Holds cached data from DiversityScientificTerms as base for other procedures.

Column Data type Description Nullable Relation
RepresentationURI nvarchar (255) - NO -
DisplayText nvarchar (255) - YES -
HierarchyCache varchar (900) - YES -
HierarchyCacheDown nvarchar (900) - YES -
RankingTerm nvarchar (200) - YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
SourceView nvarchar (200) The source of the data,i.e. the name of the view in the database NO -
RepresentationID int - NO -
BaseURL varchar (500) - NO -

Table ScientificTermSource

Column Data type Description Nullable Relation
SourceView nvarchar (200) the name of the view retrieving the data from the database NO -
Source nvarchar (50) - YES -
SourceID int - YES -
LinkedServerName nvarchar (400) If the source is located on a linked server, the name of the linked server YES -
DatabaseName nvarchar (400) The name of the database where the data are taken from YES -
Subsets nvarchar (500) List of additional data transferred into the cache database separated by YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES -
LastUpdatedWhen datetime The date of the last update of the data YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Version int -Default value: (0) YES -

Table ScientificTermSourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
SourceView nvarchar (200) SourceView as defined in table ScientificTermSource NO Refers to table ScientificTermSource
Target nvarchar (200) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO -
LastUpdatedWhen datetime The date of the last update of the project data YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -

Table ScientificTermSourceView

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
RepresentationID int - NO -
SourceView nvarchar (128) The name of the source view of the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -

Table SourceTransfer

The transfers of data of a source

Column Data type Description Nullable Relation
Source nvarchar (50) The type of the source, e.g. Taxa, part of PK NO -
SourceView nvarchar (200) The name of the main view for the data defined for retrieving the data from the source. Part of PK NO -
TransferDate datetime Date of the transfer, part of PKDefault value: getdate() NO -
ResponsibleUserID int The ID of the user as stored in table UserProxy of the source database, responsible for the transferDefault value: (-1) YES -
TargetID int If the transfer regards a postgres database, the ID of the target (= Postgres database) as stored in table Target YES Refers to table Target
Settings nvarchar (MAX) The versions, number of transfered data etc. of the objects concerned by the transfer [format: JSON] YES -

Table Target

The postgres databases as targets for the data

Column Data type Description Nullable Relation
TargetID int ID of the target on a postgres server, PK NO -
Server nvarchar (255) Name or IP of the Server NO -
Port smallint Port for accessing the server NO -
DatabaseName nvarchar (255) The name of the database NO -
TransferDirectory varchar (500) Directory on the Postgres server used for the transfer of data YES -
BashFile varchar (500) BashFile on the Postgres server used for conversion of the data YES -
MountPoint varchar (50) Mount point name of the transfer folder YES -

Table TaxonAnalysis

Column Data type Description Nullable Relation
NameID int - NO -
ProjectID int - NO Refers to table TaxonList
AnalysisID int - NO Refers to table TaxonAnalysisCategory
AnalysisValue nvarchar (MAX) - YES -
Notes nvarchar (MAX) - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table TaxonAnalysisCategory

Column Data type Description Nullable Relation
AnalysisID int - NO -
AnalysisParentID int - YES -
DisplayText nvarchar (50) - YES -
Description nvarchar (MAX) - YES -
AnalysisURI varchar (255) - YES -
ReferenceTitle nvarchar (600) - YES -
ReferenceURI varchar (255) - YES -
SourceView nvarchar (200) - NO Refers to table TaxonSynonymySource
SortingID int - YES -
BaseURL varchar (500) - NO -

Table TaxonAnalysisCategoryValue

Column Data type Description Nullable Relation
AnalysisID int - NO Refers to table TaxonAnalysisCategory
AnalysisValue nvarchar (255) - NO -
Description nvarchar (500) - YES -
DisplayText nvarchar (50) - YES -
DisplayOrder smallint - YES -
Notes nvarchar (500) - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table TaxonCommonName

Column Data type Description Nullable Relation
NameID int - NO -
CommonName nvarchar (300) - NO -
LanguageCode varchar (2) - NO -
CountryCode varchar (2) - NO -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table TaxonList

Column Data type Description Nullable Relation
ProjectID int - NO -
Project nvarchar (50) - NO -
DisplayText nvarchar (50) - YES -
SourceView nvarchar (200) - NO Refers to table TaxonSynonymySource
BaseURL varchar (500) - NO -

Table TaxonNameExternalDatabase

Column Data type Description Nullable Relation
ExternalDatabaseID int - NO -
ExternalDatabaseName nvarchar (800) - YES -
ExternalDatabaseVersion nvarchar (255) - YES -
Rights nvarchar (500) - YES -
ExternalDatabaseAuthors nvarchar (200) - YES -
ExternalDatabaseURI nvarchar (300) - YES -
ExternalDatabaseInstitution nvarchar (300) - YES -
ExternalAttribute_NameID nvarchar (255) - YES -
SourceView nvarchar (200) - NO Refers to table TaxonSynonymySource
BaseURL varchar (500) - NO -

Table TaxonNameExternalID

Column Data type Description Nullable Relation
NameID int - NO -
ExternalDatabaseID int - NO -
ExternalNameURI varchar (255) - YES -
SourceView nvarchar (200) - NO -
BaseURL varchar (500) - NO -

Table TaxonSynonymy

Holds cached data from DiversityTaxonNames as base for other procedures.

Column Data type Description Nullable Relation
NameID int - NO -
BaseURL varchar (255) - NO -
TaxonName nvarchar (255) - YES -
AcceptedNameID int - YES -
AcceptedName nvarchar (255) - YES -
TaxonomicRank nvarchar (50) - YES -
SpeciesGenusNameID int - YES -
GenusOrSupragenericName nvarchar (200) - YES -
NameParentID int - YES -
TaxonNameSinAuthor nvarchar (2000) - YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
ProjectID int - YES -
AcceptedNameSinAuthor nvarchar (2000) - YES -
NameURI varchar (255) - YES -
SourceView nvarchar (200) The source of the data, e.g. the name of the database NO Refers to table TaxonSynonymySource

Table TaxonSynonymySource

Column Data type Description Nullable Relation
SourceView nvarchar (200) - NO -
Source nvarchar (500) - YES -
SourceID int - YES -
LinkedServerName nvarchar (500) If the source is located on a linked server, the name of the linked server YES -
DatabaseName nvarchar (50) - YES -
Subsets nvarchar (500) List of additional data transferred into the cache database separated by YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES -
LastUpdatedWhen datetime The date of the last update of the data YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: ‘0’ YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -
Version int -Default value: (0) YES -

Table TaxonSynonymySourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable Relation
SourceView nvarchar (200) SourceView as defined in table TaxonSynonymySource NO Refers to table TaxonSynonymySource
Target nvarchar (200) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO -
LastUpdatedWhen datetime The date of the last update of the project data YES -
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES -
IncludeInTransfer bit If the project should be included in a schedule based data transferDefault value: (1) YES -
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferredDefault value: (0) YES -
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6Default value: (0) YES -
TransferTime time The time when the transfer should be executedDefault value: ‘00:00:00.00’ YES -
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES -
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES -
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES -

Table TaxonSynonymySourceView

Column Data type Description Nullable Relation
BaseURL varchar (500) - NO -
NameID int - NO -
SourceView nvarchar (128) The name of the source view of the data NO -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
Jul 5, 2024

Diversity Collection

Cache database

VIEWS

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

View Agents_TNT_TNTagents

Column Data type Description Nullable
BaseURL varchar (255) - YES
AgentID int - NO
AgentParentID int - YES
AgentName nvarchar (200) - NO
AgentTitle nvarchar (50) - YES
GivenName nvarchar (255) - YES
GivenNamePostfix nvarchar (50) - YES
InheritedNamePrefix nvarchar (50) - YES
InheritedName nvarchar (255) - YES
InheritedNamePostfix nvarchar (50) - YES
Abbreviation nvarchar (50) - YES
AgentType nvarchar (50) - YES
AgentRole nvarchar (255) - YES
AgentGender nvarchar (50) - YES
Description nvarchar (1000) - YES
OriginalSpelling nvarchar (200) - YES
Notes nvarchar (MAX) - YES
ValidFromDate datetime - YES
ValidUntilDate datetime - YES
SynonymToAgentID int - YES
ProjectID int - NO
LogUpdatedWhen smalldatetime - YES

View Agents_TNT_TNTagents_C

Column Data type Description Nullable
BaseURL varchar (255) - YES
AgentID int - NO
DisplayOrder tinyint - NO
AddressType nvarchar (50) - YES
Country nvarchar (255) - YES
City nvarchar (255) - YES
PostalCode nvarchar (50) - YES
Streetaddress nvarchar (255) - YES
Address nvarchar (255) - YES
Telephone nvarchar (50) - YES
CellularPhone nvarchar (50) - YES
Telefax nvarchar (50) - YES
Email nvarchar (255) - YES
URI nvarchar (255) - YES
Notes nvarchar (MAX) - YES
ValidFrom datetime - YES
ValidUntil datetime - YES
LogUpdatedWhen smalldatetime - YES

View Agents_TNT_TNTagents_I

Column Data type Description Nullable
BaseURL varchar (255) - YES
AgentID int - NO
URI varchar (255) - NO
Type nvarchar (50) - YES
Sequence int - YES
Description nvarchar (MAX) - YES
LogUpdatedWhen smalldatetime - YES

View Agents_TNT_TNTagents_ID

Column Data type Description Nullable
BaseURL varchar (255) - YES
AgentID int - NO
Identifier nvarchar (190) - YES
IdentifierURI varchar (500) - YES
Type nvarchar (50) - YES
Notes nvarchar (MAX) - YES
LogUpdatedWhen smalldatetime - YES

View Sources

Column Data type Description Nullable
SourceView nvarchar (400) The name of the source view of the data YES
URI nvarchar (255) - YES
DisplayText nvarchar (500) - YES
ID int - YES
BaseURL nvarchar (500) The basic URL as defined in the module database YES

View TaxonNames_Insecta_TNT_IBFnames

Column Data type Description Nullable
NameID int - NO
BaseURL varchar (52) - NO
TaxonName nvarchar (255) - YES
AcceptedNameID int - NO
AcceptedName nvarchar (255) - YES
TaxonomicRank nvarchar (50) - NO
GenusOrSupragenericName nvarchar (200) - NO
SpeciesGenusNameID int - YES
TaxonNameSinAuthor nvarchar (1058) - YES
ProjectID int - NO
AcceptedNameSinAuthor nvarchar (1058) - YES
LogUpdatedWhen smalldatetime - YES

View TaxonNames_Insecta_TNT_IBFnames_C

Column Data type Description Nullable
BaseURL varchar (255) - YES
NameID int - NO
CommonName nvarchar (220) - NO
LanguageCode varchar (2) - NO
CountryCode varchar (2) - NO
LogUpdatedWhen smalldatetime - YES

View TaxonNames_Insecta_TNT_IBFnames_E

Column Data type Description Nullable
BaseURL varchar (255) - YES
ExternalDatabaseID int - NO
ExternalDatabaseName nvarchar (800) - NO
ExternalDatabaseVersion nvarchar (255) - YES
Rights nvarchar (500) - YES
ExternalDatabaseAuthors nvarchar (200) - YES
ExternalDatabaseURI nvarchar (300) - YES
ExternalDatabaseInstitution nvarchar (300) - YES
ExternalAttribute_NameID nvarchar (255) - YES
LogUpdatedWhen datetime - YES

View TaxonNames_Insecta_TNT_IBFnames_EID

Column Data type Description Nullable
BaseURL varchar (255) - YES
NameID int - NO
ExternalDatabaseID int - NO
ExternalNameURI varchar (255) - YES
LogUpdatedWhen datetime - YES

View TaxonNames_Insecta_TNT_IBFnames_H

Column Data type Description Nullable
BaseURL varchar (255) - YES
NameID int - NO
NameParentID int - YES
LogUpdatedWhen smalldatetime - YES

View TaxonNames_Insecta_TNT_IBFnames_L

Column Data type Description Nullable
BaseURL varchar (255) - YES
ProjectID int - NO
Project nvarchar (50) - NO
DisplayText nvarchar (50) - YES

View TaxonNames_Insecta_TNT_IBFnames_LA

Column Data type Description Nullable
BaseURL varchar (255) - YES
NameID int - NO
ProjectID int - NO
AnalysisID int - NO
AnalysisValue nvarchar (MAX) - YES
Notes nvarchar (MAX) - YES
LogUpdatedWhen smalldatetime - YES

View TaxonNames_Insecta_TNT_IBFnames_LAC

Column Data type Description Nullable
BaseURL varchar (255) - YES
AnalysisID int - NO
AnalysisParentID int - YES
DisplayText nvarchar (50) - YES
Description nvarchar (MAX) - YES
AnalysisURI varchar (255) - YES
ReferenceTitle nvarchar (800) - YES
ReferenceURI varchar (400) - YES
SortingID int - YES
LogUpdatedWhen datetime - YES

View TaxonNames_Insecta_TNT_IBFnames_LACV

Column Data type Description Nullable
BaseURL varchar (255) - YES
AnalysisID int - NO
AnalysisValue nvarchar (255) - NO
Description nvarchar (500) - YES
DisplayText nvarchar (50) - YES
DisplayOrder smallint - YES
Notes nvarchar (500) - YES
LogUpdatedWhen smalldatetime - YES

View ViewAnalysis

View for analysis used in the published data

Column Data type Description Nullable
AnalysisID int - NO
AnalysisParentID int - YES
DisplayText nvarchar (50) - YES
Description nvarchar (MAX) - YES
MeasurementUnit nvarchar (50) - YES
Notes nvarchar (MAX) - YES
AnalysisURI varchar (255) - YES
OnlyHierarchy bit - YES
LogUpdatedWhen datetime - YES

View ViewAnnotation

View for all annotations

Column Data type Description Nullable
AnnotationID int - NO
ReferencedAnnotationID int - YES
AnnotationType nvarchar (50) - NO
Title nvarchar (50) - YES
Annotation nvarchar (MAX) - NO
URI varchar (255) - YES
ReferenceDisplayText nvarchar (500) - YES
ReferenceURI varchar (255) - YES
SourceDisplayText nvarchar (500) - YES
SourceURI varchar (255) - YES
IsInternal bit - YES
ReferencedID int - NO
ReferencedTable nvarchar (500) - NO
LogUpdatedWhen datetime - YES

View ViewCollection

View for all not withheld collections

Column Data type Description Nullable
CollectionID int - NO
CollectionParentID int - YES
CollectionName nvarchar (255) - NO
CollectionAcronym nvarchar (10) - YES
AdministrativeContactName nvarchar (500) - YES
AdministrativeContactAgentURI varchar (255) - YES
Description nvarchar (MAX) - YES
Location nvarchar (255) - YES
CollectionOwner nvarchar (255) - YES
DisplayOrder smallint - YES
LogUpdatedWhen datetime - YES

View ViewCollectionAgent

View for all not withheld collectors

Column Data type Description Nullable
CollectionSpecimenID int - NO
CollectorsName nvarchar (255) - NO
CollectorsSequence datetime2 - YES
CollectorsNumber nvarchar (50) - YES
CollectorsAgentURI varchar (255) - YES
LogUpdatedWhen datetime - YES

View ViewCollectionEvent

View for all not withheld collection events

Column Data type Description Nullable
CollectionEventID int - NO
Version int - NO
CollectorsEventNumber nvarchar (50) - YES
CollectionDate datetime - YES
CollectionDay tinyint - YES
CollectionMonth tinyint - YES
CollectionYear smallint - YES
CollectionDateSupplement nvarchar (100) - YES
CollectionTime varchar (50) - YES
CollectionTimeSpan varchar (50) - YES
LocalityDescription nvarchar (MAX) - YES
HabitatDescription nvarchar (MAX) - YES
ReferenceTitle nvarchar (255) - YES
CollectingMethod nvarchar (MAX) - YES
Notes nvarchar (MAX) - YES
CountryCache nvarchar (50) - YES
ReferenceDetails nvarchar (50) - YES
LocalityVerbatim nvarchar (MAX) - YES
CollectionEndDay tinyint - YES
CollectionEndMonth tinyint - YES
CollectionEndYear smallint - YES
LogUpdatedWhen datetime - YES

View ViewCollectionEventLocalisation

View for all not withheld localisations

Column Data type Description Nullable
CollectionEventID int - NO
LocalisationSystemID int - NO
Location1 nvarchar (255) - YES
Location2 nvarchar (255) - YES
LocationAccuracy nvarchar (50) - YES
LocationNotes nvarchar (MAX) - YES
DeterminationDate smalldatetime - YES
DistanceToLocation varchar (50) - YES
DirectionToLocation varchar (50) - YES
ResponsibleName nvarchar (255) - YES
ResponsibleAgentURI varchar (255) - YES
AverageAltitudeCache float - YES
AverageLatitudeCache float - YES
AverageLongitudeCache float - YES
RecordingMethod nvarchar (500) - YES
Geography nvarchar (MAX) - YES
LogUpdatedWhen datetime - YES

View ViewCollectionEventProperty

View for all not withheld collection site properties

Column Data type Description Nullable
CollectionEventID int - NO
PropertyID int - NO
DisplayText nvarchar (255) - YES
PropertyURI varchar (255) - YES
PropertyHierarchyCache nvarchar (MAX) - YES
PropertyValue nvarchar (255) - YES
ResponsibleName nvarchar (255) - YES
ResponsibleAgentURI varchar (255) - YES
Notes nvarchar (MAX) - YES
AverageValueCache float - YES
LogUpdatedWhen datetime - YES

View ViewCollectionExternalDatasource

View for all external datasources

Column Data type Description Nullable
ExternalDatasourceID int - NO
ExternalDatasourceName nvarchar (255) - YES
ExternalDatasourceVersion nvarchar (255) - YES
Rights nvarchar (500) - YES
ExternalDatasourceAuthors nvarchar (200) - YES
ExternalDatasourceURI nvarchar (300) - YES
ExternalDatasourceInstitution nvarchar (300) - YES
InternalNotes nvarchar (1500) - YES
ExternalAttribute_NameID nvarchar (255) - YES
PreferredSequence tinyint - YES
Disabled bit - YES
LogUpdatedWhen datetime - YES

View ViewCollectionProject

View for all not withheld collection specimen within the projects

Column Data type Description Nullable
CollectionSpecimenID int - NO
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO
LogUpdatedWhen datetime - YES

View ViewCollectionSpecimen

View for all not withheld specimen

Column Data type Description Nullable
CollectionSpecimenID int - NO
LabelTranscriptionNotes nvarchar (255) - YES
OriginalNotes nvarchar (MAX) - YES
LogUpdatedWhen datetime - YES
CollectionEventID int - YES
AccessionNumber nvarchar (50) - YES
AccessionDate datetime - YES
AccessionDay tinyint - YES
AccessionMonth tinyint - YES
AccessionYear smallint - YES
DepositorsName nvarchar (255) - YES
DepositorsAccessionNumber nvarchar (50) - YES
ExsiccataURI varchar (255) - YES
ExsiccataAbbreviation nvarchar (255) - YES
AdditionalNotes nvarchar (MAX) - YES
ReferenceTitle nvarchar (255) - YES
ReferenceURI varchar (255) - YES
ExternalDatasourceID int - YES

View ViewCollectionSpecimenImage

View for all not withheld collection specimen images

Column Data type Description Nullable
CollectionSpecimenID int - NO
URI varchar (255) - NO
ResourceURI varchar (255) - YES
SpecimenPartID int - YES
IdentificationUnitID int - YES
ImageType nvarchar (50) - YES
Notes nvarchar (MAX) - YES
LicenseURI varchar (500) - YES
LicenseNotes nvarchar (500) - YES
DisplayOrder int - YES
LicenseYear nvarchar (50) - YES
LicenseHolderAgentURI nvarchar (500) - YES
LicenseHolder nvarchar (500) - YES
LicenseType nvarchar (500) - YES
CopyrightStatement nvarchar (500) - YES
CreatorAgentURI varchar (255) - YES
CreatorAgent nvarchar (500) - YES
IPR nvarchar (500) - YES
Title nvarchar (500) - YES
LogUpdatedWhen datetime - YES

Depending on:

  • CollectionSpecimenImage

View ViewCollectionSpecimenPart

View for all not withheld collection specimen parts

Column Data type Description Nullable
SpecimenPartID int - NO
DerivedFromSpecimenPartID int - YES
PreparationMethod nvarchar (MAX) - YES
PreparationDate datetime - YES
PartSublabel nvarchar (50) - YES
CollectionID int - NO
MaterialCategory nvarchar (50) - NO
StorageLocation nvarchar (255) - YES
Stock float - YES
Notes nvarchar (MAX) - YES
CollectionSpecimenID int - NO
AccessionNumber nvarchar (50) - YES
StorageContainer nvarchar (500) - YES
StockUnit nvarchar (50) - YES
ResponsibleName nvarchar (255) - YES
LogUpdatedWhen datetime - YES

View ViewCollectionSpecimenProcessing

View for all not withheld collection specimen processings

Column Data type Description Nullable
CollectionSpecimenID int - NO
SpecimenProcessingID int - NO
ProcessingDate datetime - YES
ProcessingID int - NO
Protocoll nvarchar (100) - YES
SpecimenPartID int - YES
ProcessingDuration varchar (50) - YES
ResponsibleName nvarchar (255) - YES
ResponsibleAgentURI varchar (255) - YES
Notes nvarchar (MAX) - YES
LogUpdatedWhen datetime - YES

View ViewCollectionSpecimenReference

View for all not withheld references

Column Data type Description Nullable
CollectionSpecimenID int - NO
ReferenceID int - NO
ReferenceTitle nvarchar (400) - NO
ReferenceURI varchar (500) - YES
IdentificationUnitID int - YES
SpecimenPartID int - YES
ReferenceDetails nvarchar (500) - YES
Notes nvarchar (MAX) - YES
ResponsibleName nvarchar (255) - YES
ResponsibleAgentURI varchar (255) - YES
LogUpdatedWhen datetime - YES

View ViewCollectionSpecimenRelation

View for all not withheld collection specimen processings

Column Data type Description Nullable
CollectionSpecimenID int - NO
RelatedSpecimenURI varchar (255) - NO
RelatedSpecimenDisplayText varchar (255) - NO
RelationType nvarchar (50) - YES
RelatedSpecimenCollectionID int - YES
RelatedSpecimenDescription nvarchar (MAX) - YES
Notes nvarchar (MAX) - YES
IdentificationUnitID int - YES
SpecimenPartID int - YES
LogUpdatedWhen datetime - YES

View ViewExternalIdentifier

View for all external identifiers

Column Data type Description Nullable
ID int - NO
Type nvarchar (50) - YES
Identifier nvarchar (500) - YES
URL varchar (500) - YES
Notes nvarchar (MAX) - YES
ReferencedTable nvarchar (128) - NO
ReferencedID int - NO
LogUpdatedWhen datetime - YES

View ViewIdentification

View for all identifications

Column Data type Description Nullable
CollectionSpecimenID int - NO
IdentificationUnitID int - NO
IdentificationSequence smallint - NO
IdentificationDay tinyint - YES
IdentificationMonth tinyint - YES
IdentificationYear smallint - YES
IdentificationDateSupplement nvarchar (255) - YES
IdentificationCategory nvarchar (50) - YES
IdentificationQualifier nvarchar (50) - YES
VernacularTerm nvarchar (255) - YES
TaxonomicName nvarchar (255) - YES
NameURI varchar (255) - YES
Notes nvarchar (MAX) - YES
TypeStatus nvarchar (50) - YES
TypeNotes nvarchar (MAX) - YES
ReferenceTitle nvarchar (255) - YES
ReferenceDetails nvarchar (50) - YES
ResponsibleName nvarchar (255) - YES
LogUpdatedWhen datetime - YES

View ViewIdentificationUnit

View for all not withheld identification units

Column Data type Description Nullable
CollectionSpecimenID int - NO
IdentificationUnitID int - NO
LastIdentificationCache nvarchar (255) - NO
TaxonomicGroup nvarchar (50) - NO
RelatedUnitID int - YES
RelationType nvarchar (50) - YES
ExsiccataNumber nvarchar (50) - YES
DisplayOrder smallint - NO
ColonisedSubstratePart nvarchar (255) - YES
FamilyCache nvarchar (255) - YES
OrderCache nvarchar (255) - YES
LifeStage nvarchar (255) - YES
Gender nvarchar (50) - YES
HierarchyCache nvarchar (500) - YES
UnitIdentifier nvarchar (50) - YES
UnitDescription nvarchar (50) - YES
Circumstances nvarchar (50) - YES
Notes nvarchar (MAX) - YES
NumberOfUnits smallint - YES
OnlyObserved bit - YES
RetrievalType nvarchar (50) - YES
LogUpdatedWhen datetime - YES

View ViewIdentificationUnitAnalysis

View for all not withheld identification units

Column Data type Description Nullable
AnalysisID int - NO
AnalysisNumber nvarchar (50) - NO
AnalysisResult nvarchar (MAX) - YES
ExternalAnalysisURI varchar (255) - YES
ResponsibleName nvarchar (255) - YES
ResponsibleAgentURI varchar (255) - YES
AnalysisDate nvarchar (50) - YES
SpecimenPartID int - YES
Notes nvarchar (MAX) - YES
CollectionSpecimenID int - NO
IdentificationUnitID int - NO
LogUpdatedWhen datetime - YES

View ViewIdentificationUnitGeoAnalysis

View for all not withheld geo analysis

Column Data type Description Nullable
CollectionSpecimenID int - NO
IdentificationUnitID int - NO
AnalysisDate datetime - NO
Geography nvarchar (MAX) - YES
Geometry nvarchar (MAX) - YES
ResponsibleName nvarchar (255) - YES
ResponsibleAgentURI varchar (255) - YES
Notes nvarchar (MAX) - YES
LogUpdatedWhen datetime - YES

Depending on:

  • IdentificationUnitGeoAnalysis

View ViewIdentificationUnitInPart

View for all not withheld identification units in a specimen part

Column Data type Description Nullable
Description nvarchar (500) - YES
CollectionSpecimenID int - NO
IdentificationUnitID int - NO
SpecimenPartID int - NO
DisplayOrder smallint - NO
LogUpdatedWhen smalldatetime - YES

View ViewMetadata

View for metadata

Column Data type Description Nullable
ProjectID int - NO
SettingID int - NO
Value nvarchar (MAX) - NO
LogUpdatedWhen smalldatetime - YES

View ViewProcessing

View for processings

Column Data type Description Nullable
ProcessingID int - NO
ProcessingParentID int - YES
DisplayText nvarchar (50) - YES
Description nvarchar (MAX) - YES
Notes nvarchar (MAX) - YES
ProcessingURI varchar (255) - YES
OnlyHierarchy bit - YES
LogUpdatedWhen datetime - YES

View ViewTaxononmy

View for all identifications including the accepted names and synonyms as derived from the table TaxonSynonymy

Column Data type Description Nullable
CollectionSpecimenID int - NO
IdentificationUnitID int - NO
IdentificationSequence smallint - NO
IdentificationDay tinyint - YES
IdentificationMonth tinyint - YES
IdentificationYear smallint - YES
IdentificationDateSupplement nvarchar (255) - YES
IdentificationCategory nvarchar (50) - YES
IdentificationQualifier nvarchar (50) - YES
VernacularTerm nvarchar (255) - YES
TaxonomicName nvarchar (255) - YES
NameURI varchar (255) - YES
Notes nvarchar (MAX) - YES
TypeStatus nvarchar (50) - YES
TypeNotes nvarchar (MAX) - YES
ReferenceTitle nvarchar (255) - YES
ReferenceDetails nvarchar (50) - YES
SynonymName nvarchar (255) - YES
AcceptedName nvarchar (255) - YES
TaxonomicRank nvarchar (50) - YES
AcceptedNameURI varchar (255) - YES
GenusOrSupragenericName nvarchar (255) - YES
TaxonNameSinAuthor nvarchar (2000) - YES
ValidTaxonName nvarchar (255) - YES
ValidTaxonWithQualifier nvarchar (560) - YES
ValidTaxonNameSinAuthor nvarchar (2000) - YES
ValidTaxonIndex nvarchar (259) - YES
ValidTaxonListOrder int - NO
ResponsibleName nvarchar (255) - YES

View ViewWithholdAgent

View for all withheld collectors of published specimen

Column Data type Description Nullable
CollectionSpecimenID int - NO

View ViewWithholdPart

View for all withheld parts of published specimen

Column Data type Description Nullable
SpecimenPartID int - NO

View ViewWithholdUnit

View for all withheld units of published specimen

Column Data type Description Nullable
IdentificationUnitID int - NO
Jul 5, 2024

Diversity Collection

Cache database

FUNCTIONS and PROCEDURES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

FUNCTIONS


Function BaseURLofSource

The URL of the source database as defined in the source database, e.g. http://tnt.diversityworkbench.de/collection

DataType: nvarchar (500)


Function DiversityWorkbenchModule

DataType: nvarchar (50)


Function HighResolutionImagePath

This function translates the path of an image into the corresponding path of a web resource with of high resolution version of the image. Currently only valid for installations on the SNSB-Server. May be changed to adapt to other installations

DataType: nvarchar (500)


Function ProjectsDatabase

The name of the DiversityProjects database where the project definition are found

DataType: nvarchar (255)


Function ServerURL

The URL of the server where the database is installed

DataType: nvarchar (255)


Function SourceDatabase

The name of the source database, e.g. DiversityCollection

DataType: nvarchar (255)


Function SourceDatabaseTrunk

The name of the source database without the leading “Diversity”, e.g. Collection

DataType: nvarchar (255)


Function Version

DataType: nvarchar (8)


PROCEDURES


Procedure procBcpExport


Procedure procBcpInitExport


Procedure procBcpRemoveFile


Procedure procBcpViewCreate


Procedure procProjectName


Procedure procTaxonNameHierarchy


Procedure procTransferAgent


Procedure procTransferAgentContactInformation


Procedure procTransferGazetteer


Procedure procTransferReferenceTitle


Procedure procTransferScientificTerm


Procedure procTransferTaxonSynonymy


Procedure procUnitIDforABCD

Jul 5, 2024

Diversity Collection

Cache database

ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Role CacheAdmin

Read/write access to objects related to cache database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
AnnotationType_Enum User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
LanguageCode_Enum TABLE
MeasurementUnit_Enum TABLE
ParameterValue_Enum User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
TaskDateType_Enum User TABLE
TaskModuleType_Enum User TABLE
TaskType_Enum User TABLE
ViewCollectionSpecimenImage User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
DiversityWorkbenchModule User FUNCTION
Version User FUNCTION
Inheriting from roles:
  • CacheUser

Role CacheUser

Reading access to objects related to the cache database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
AnnotationType_Enum User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
LanguageCode_Enum TABLE
MeasurementUnit_Enum TABLE
ParameterValue_Enum User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
TaskDateType_Enum User TABLE
TaskModuleType_Enum User TABLE
TaskType_Enum User TABLE
ViewCollectionSpecimenImage User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
DiversityWorkbenchModule User FUNCTION
Version User FUNCTION
Inheriting from roles:
  • User
Jul 5, 2024

Diversity Collection - Cache DB

Sources from other modules

To provide details from other modules like DiversityTaxonNames, DiversityAgents, DiversityScientificTerms etc. in the cached data, this information is transferred into the cache database together with the data from DiversityCollection database. Use the add button to add a source for the data you need. The data for the cache database are provided via views that will be created for you. With the find button you can list the sources used in the projects to get a hint of what may be needed. The tables and view for the sources are placed in the schema dbo in the SQL-Server cache database and public in the Postgres cache databases. In case a new version for the source is available you get a notation like Needs recreation to version 2 . In this case you can either try to update the source with a click on the button or remove the source with a click on the button and use the button to recreate the source. For an introduction see a short tutorial . For the inclusion of sources from services like Catalogue of Life see the chapter Sources from webservices.

Subsets

The sources of some module provide additional subsets to the main data. To select the subsets that should be transferred to the cache database, click on the button. In the upcoming dialog (see the example for DiversityTaxonNames below) select those subsets you want to transfer in addition to the basic list. By default all subsets are selected.

Transfer

Single manual transfer

To transfer the data of a single source into the  cache database use the next button and the details button to inspect the content.

To transfer the data into the Postgres database, you have to connect with a database first. Use the next button to transfer the data from the  cache database into the  Postgres database. The button will transfer the data of all sources in the list into the cache database (see below).

Scheduled transfer

To transfer the data of all sources into the  cache database and all available Postgres databases, use the scheduledtransfer as background process. With this transfer all available Postgres databases will be included in the data transfer. These targets are indicated underneath the Postgres block (see image below).

If the target is placed on the current server, the text will appear in black as shown below.

 

Removal

With the button you can remove the sources together with the views (see above).

 

 

 

Apr 8, 2025

Subsections of Sources

Cache Database

Taxonomy

Sources for the taxonomy

To provide the taxonomy with accepted names and synonyms for the identifications in the cached data, this information is transferred into the [cache database] together with the data from the collection database. To add a source from a database on the local or a a linked server, use the button. In the appearing dialogs, select the database and the project of the data. The data for the cache database are provided via views that will be created. To inspect the data from the views, click on the button. With the button you can remove the views (see below). To restrict the data subsets that are transferred to the cache database, click on the button. In the upcoming dialog (see below) select those subsets you want to transfer in addition to the basic name list.

To transfer the data into the cache database resp. [Postgres database] use the buttons and the buttons to inspect the content. To transfer resp. inspect data within the Postgres database, you have to connect with a database first.

With the buttons you can transfer all sources in the list from the original source into the cache database resp. into the Postgres database.

 

 

 

 

 

 

Jun 7, 2024

Cache Database

Terms

Sources for the scientific terms

To provide details from DiversityScientificTerms in the cached data, this information is transferred into the [cache database] together with the data from the collection database. Use the button to add a source for the data you need. The data for the cache database are provided via views that will be created. To select a source for the schedule based transfer resp. the transfer with the  buttons, use the checkbox. To see the protocol of the transfers, click on the button. To transfer all sources that had been selected  use the button (Source database to cache database) resp.  button (Cache database to Postgres database). To inspect the data from the views, click on the button. With the button you can remove the views (see below). To transfer the data into the  cache database resp. Postgres database use the buttons and the buttons to inspect the content. To transfer resp. inspect data within the Postgres database, you have to connect with a database first.

 

 

 

 

Jun 4, 2024

Cache Database

Webservices

Sources from webservices

To provide details for datasets linked to webservices like Catalogue ofLife etc. in the cached data, this information can be transferred into the cache database together with the data from the DiversityCollection database. Use the button to add the webservice you need.

Transfer

To transfer the data of a webservice into the  cache database use the button. A window a shown below will open where you must select all projects that should be checked for data related to the webservice you selected. Only names found within these projects will be transferred.

Use the buttons to inspect the content. Names that are already present will not be transferred again. So if you need these values to be updated you have to remove it (see below) and add it again. Links that refer to lists of names instead of single names will not be inserted. These links will be stored in the Errorlog to enable their inspection.

To transfer the data into the Postgres database, you have to connect with a database first. Use the button to transfer the data from the cache database into the  Postgres database and the buttons to inspect the content.

 

Removal

With the button you can remove the sources.

 

 

 

Jun 4, 2024

Agents

Sources for the agents

To provide details for the agents in the cached data, this information is transferred into the cache database together with the data from the collection database. Use the button to add a source. The data for the cache database are provided via views that will be created. To inspect the data from the views, click on the button. With the button you can remove the views (see below). To restrict the data subsets that are transferred to the cache database, click on the button. In the upcoming dialog select those subsets you want to transfer in addition to the basic name list. To transfer the data into the cache resp. Postgres database use the buttons and the buttons to inspect the content. To transfer resp. inspect data within the Postgres database, you have to connect with a database first.

 

 

 

 

Jun 7, 2024

Cache Database Transfer

Transfer of the data

To transfer the data you have several options:

  • Single transfer : Transfer data of a single project
  • Transfer via bcp : Transfer data of the data via bcp
  • Bulk transfer : Transfer data of all projects and sources selected for the schedule based transfer

With the resp. button you can decide if the data should be checked for updates. If this option is active ( ) the program will compare the contents and decide if a transfer is needed. If a transfer is needed, this will be indicated with a red border of the transfer button . If you transferred only a part of the data this will be indicated by a thin red border for the current session . The context menu of the button View differences will show the accession numbers of the datasets with changes after the last transfer (see below).

 

Embargo

If an embargo has been defined in DiversityProjects, a message will be shown (see below) and you well get a warning if you start a transfer. The automatic transfer for projects with an embargo will be blocked.

 

Competing transfer

If a competing transfer is active for the same step, this will be indicated as shown below. While this transfer is active, any further transfer for this step will be blocked.

If this competing transfer is due to e.g. a crash and is not active any more, you have to get rid of the block to preceed with the transfer of the date. To do so you have to reset the status of the transfer. Check the scheduler as shown below. This will activate the button.

Now click on the button to open the window for setting the scheduler options as shown below.

To finally remove the block by the [Active transfer], click on the button. This will remove the block and you can preceed with the transfer of the data.

 

Single transfer

To transfer the data for a certain project, click on the button in the Cache- or Postgres data range (see below).

A window as shown below will open, where all data ranges for the transfer will be listed. With the  button you can set the timeout for the transfer of the data where 0 means infinite and is recommended for large amounts of data. With the button you can switch on resp. of the generation of a report. To stop the execution in case of an error click on the button. The button will change from to and the execution will stop in case of an error. Click on the Start transfer button to start the transfer.

After the data are transferred, the number and data are visible as shown below.

After the data are transferred successful transfers as indicated by an error by . The reason for the failure is shown if you click on the button. For the transfer to the Postgres database the number in the source and the target will be listed as shown below indicating deviating numbers of the data. For the detection of certain errors it may help to activate the logging as described in the chapter TransferSettings.

 

To inspect the first 100 lines of the transferred data click on the button.

 

Bulk transfer

To transfer the data for all projects selected for the schedule based transfer, click on the button in the cache- or Postgres data range (see below).

Together with the transfer of the data, reports will be generated and stored in the reports directory. Click on the button in the Timer area to open this directory. To inspect data in the default schemas (dbo for SQL-Server and public for Postgres ) outside the project schemata, use the buttons shown in the image above.

 

Transfer as background process

Transfer data from database to cache database and all Postgres databases

To transfer the data as a background process use the following arguments:

  • CacheTransfer
  • Server of the SQL-server database
  • Port of SQL-server
  • Database with the source data
  • Server for Postgres cache database
  • Port for Postgres server
  • Name of the Postgres cache database
  • Name of Postgres user
  • Password of Postgres user

For example:

C:\DiversityWorkbench\DiversityCollection> DiversityCollection.exe CacheTransfer snsb.diversityworkbench.de 5432 DiversityCollection 127.0.0.1 5555 DiversityCollectionCache PostgresUser myPostgresPassword

The application will transfer the data according to the settings, generate a protocol as described above and quit automatically after the transfer of the data. For an introduction see a short tutorial . The user starting the process needs a Windows authentication with access to the SQL-Server database and proper rights to transfer the data. The sources and projects within DiversityCollection will be transferred according to the settings (inclusion, filter, days and time). The transfer will be documented in report files. Click on the button to access these files. For a simulation of this transfer click on the Transfer all data according to the settings button at the top of the form. This will ignore the time restrictions as defined in the settings and will start an immediate transfer of all selected data.

To generate transfer reports and document every step performed by the software during the transfer of the data use a different first argument:

  • CacheTransferWithLogging
  • ...

C:\DiversityWorkbench\DiversityCollection> DiversityCollection.exe CacheTransferWithLogging snsb.diversityworkbench.de 5432 DiversityCollection 127.0.0.1 5555 DiversityCollectionCache PostgresUser myPostgresPassword

To transfer only the data from the main database into the cache database use a different first argument:

  • CacheTransferCacheDB
  • ...

To transfer only the data from the cache database into the postgres database use a different first argument:

  • CacheTransferPostgres
  • ...

The remaining arguments correspond to the list above. The generated report files are located in the directory .../ReportsCacheDB and the single steps are witten into the file DiversityCollectionError.log.

History

For every transfer of the data along the pipeline, the settings (e.g. version of the databases) the number of transferred data together with the execution time and additional information are stored. Click on the  button in the respective part to get a list of all previous transfers together with these data (see below).

Infrastructure

Sources

The transfer of the data from the main databases into the cache database is handled via views and stored procedures in the cache database that are generated by the program. The views provide the data in the main databases while the procedures refer to these views to copy the data from the tables in the main database into the cache database. The views are listed in the table [Module]Source where [Module] is the Name of the module without the leading “Diversity”.

As an example for the module DiversityAgents the cache database contains a view Agents_TNT_TaxRefagents where the source is the module DiversityAgents, the server is TNT and the project is TaxRefagents. The views for a source are listed in the table AgentSource. This view refers to the corresponding data in the module. The procedure procTransferAgent selects data in the view and copies the data into the table Agent.

For source objects the schema is dbo.

Projects

The transfer of the data from the main database into the cache database is handled via views and stored procedures in the cache database that are generated by the program. The views provide the data in the main database while the procedures refer to these views to copy the data from the tables in the main database into the cache database.

As an example the cache database contains a view ViewAnalysis that selects data in the table Analysis in the main database. The procedure [Project].procPublishAnalysis refers to the view and copies the data into the table [Project].CacheAnalysis where [Project] is the schema of the project.

The transfers together with information on the versions, settings etc. are listed in the table ProjectTransfer.

Jan 14, 2025

Subsections of Transfer

Cache Database Transfer

Transfer of the data triggered by a batch command

Transfer as background process

Transfer data from database to cache database and all Postgres databases

The server has to start the application with a Windows account with access to the database server and the databases with the following permissions/roles:

  • DiversityCollection:
    • Role CacheAdmin
  • DiversityProjects:
    • Role DiversityWorkbenchUser
  • Additional sources, e.g. DiversityTaxonNames:
    • In every database from which data should be transferred: Role DiversityWorkbenchUser or corresponding roles

 

 

To transfer the data as a background process use the following arguments:

  • CacheTransfer
  • Server of the SQL-server database
  • Port of SQL-server
  • Database with the source data
  • Server for Postgres cache database
  • Port for Postgres server
  • Name of the Postgres cache database
  • Name of Postgres user
  • Password of Postgres user

For example:

C:\\DiversityWorkbench\\DiversityCollection\> DiversityCollection.exe CacheTransfer snsb.diversityworkbench.de 5432 DiversityCollection 127.0.0.1 5555 DiversityCollectionCache postgres myPassword

The application will transfer the data according to the settings, generate a protocol as described above and quit automatically after the transfer of the data. For an introduction see a short tutorial . The user starting the process needs a Windows authentication with access to the SQL-Server database and proper rights to transfer the data. The sources and projects within DiversityCollection will be transferred according to the settings (inclusion, filter, days and time). The transfer will be documented in report files. Click on the button to access these files. For a simulation of this transfer click on the Transfer all data according to the settings  button at the top of the form.

 

Jan 14, 2025

Cache Database

Transfer Settings

Settings for the transfer of the projects in the cache database

To edit the general settings for the transfer, click on the button in the main form. A window as shown below will open. Here you can set the timeout for the transfer in minutes. The value 0 means that no time limit is set and the program should try infinite to transfer the data.

The transfer via bcp does not rely on these numbers and uses a much faster way of transfer, yet its needs detailed configuration. If you are connected to a postgres database, the transfer directory and the bash file for conversion and import can be set in the last line.

 

Logging

For the detection of certain errors it may help to log the events of the transfer by activating the logging: . The logging is set per application, not per database. So to detect errors in a transfer started by a scheduler on a server, you have to activate the logging in the application started by the server. The log is written into the error log of the application. To see the content of the log either use the Protocol section or in the main window select Help - ErrorLog from the menu.

 

Stop on error

In case of an error during the transfer you can stop the transfer: . The stop in case of an error is set per application, not per database. So to stop the transfer in case of errors in a transfer started by a scheduler on a server, you have to activate this in the application started by the server.

 

Scheduled transfer

The scheduled transfer is meant to be launched on a server on a regular basis, e.g. once a week, once a day, every hour etc.. The transfer of the data via the scheduled transfer will take place according to the settings. This means the program will check if the next planned time for a data transfer is passed and only than start to transfer the data. To include a source in the schedule, check the selector for the scheduler. To set the time and days scheduled for a transfer, click on the button. A window as shown below will open where you can select the time and the day(s) of the week when the transfer should be executed.

The planned points in time are shown in the form as shown below.

The protocol of the last transfer can be seen as in the window above or if you click on the button. If an error occurred this can be inspected with a click no the button.

If another transfer on the same source has been started, no further transfer will be started. In the program this competing transfer is shown as below.

You can remove this block with a click on the button. In opening window (see below) click on the button. This will as well remove error messages from previous transfers.

A further option for restriction of the transfers is the comparison of the date when the last transfer has been executed. Click on the button to change it to . In this state the program will compare the dates of the transfers and execute the transfer only if new data are available.

 

 

 

 

 

Jan 14, 2025

Diversity Collection

Transfer Protocol

The protocol of any transfer is written into the error log of the application. To examine the messages of the transfers within the cache database you may for every single step click on the button in the transfer window in case an error occurred. In the main window the protocol for all transfers is shown in the Protocol  part. A click on the button requeries resp. shows the protocol. The option will show the line numbers of the protocol and the option will restrict the output to failures and errors stored in the protocol. By default both options are seleted and the number of lines is restricted to 1000. In case of longer protocols change the number of lines for the output. The button will show the protocol in the default editor of your computer. The button will clear the protocol.

 

Jan 8, 2025

Cache Database

Transfer Via BCP

Transfer of data from SQL-Server to Postgres via bcp

To transfer large amounts of data from the SQL-Server database to a Postgres database the normal path is clearly too slow. For these cases an alternative option is provided using the transfer in a csv file on a shared folder on the server where the Postgres databases are hosted.   

If the shared directory, mount point and the bash file are set (see below - on first tab [Update, Sources] ) the batch transfer can be activated. Click e.g. on the button to set the values. The window that will open offers a list with existing entries for the respecitive value. Please ask the postgres server administrator for details.

To use the batch transfer for a project, click in the checkbox as shown below.

The image for the transfer will change from to . Now the data of every table within the project will be transferred via bcp. To return to the standard transfer, just deselect the checkbox.   

To stop the execution in case of an error click on the button in the window that will open after you clicked the button to start the transfer. The button will change from to and the execution will stop in case of an error. The objects created for the transfer (csv file, tables) of the data will not be removed to enable an inspection. 

Details about the setup are described in the chapter Setup for thetransfer via bcp.

Details about the export are described in the chapter Export using thetransfer via bcp.  

 

 

Jun 4, 2024

Subsections of Transfer Via BCP

Cache Database

Transfer Via BCP Export

Export using the transfer via bcp

Overview

The image shows an overview of the steps described below. The numbers in the arrows refer to the described steps.   

 

Export

Initialization of the batch export

In the shared directory folders will be created according to .../<Database>/<Schema>. The data will be exported into a csv file in the created schema (resp. project) folder in the shared directory. The initialization of the export is performed by the procedure procBpcInitExport (see below and [ 1 ] in the overview image above). 

Creation of view as source for the batch export

To export the data into the file a view (see below) will be created transforming the data in the table of the SQL-Server database according to the requirements of the export (quoting and escaping of existing quotes). The creation of the view is performed by the procedure procBcpViewCreate (see above and [ 2 ] in the overview image above).

The views provide the data from the SQL-Server tables in the sequence as defined in the Postgres tables and perform a reformatting of the string values (see example below).

CASE WHEN \[AccessionNumber\] IS NULL THEN NULL ELSE \'\"\' + REPLACE(\[AccessionNumber\], \'\"\', \'\"\"\') + \'\"\' END AS \[AccessionNumber\]

 

Export of the data in to a csv file in the transfer directory

To data will be exported using the procedure procBcpExort (see above and [ 3 ] in the overview image above) into a csv file in the directory created in the shared folder (see below).

Creation of a table as target for the intermediate storage of the data

For the intermediate storage of the data, a temporary table (..._Temp) is created (see below and [ 4 ] in the overview image above). This table is the target of the bash import described below.

 

Bash conversion and import of the data in to the intermediate storage table

As Postgres accepts only UTF-8 without the Byte OrderMark (BOM) the exported csv file must be converted into UTF-8 without BOM. For this purpose there are scripts provided for every Windows-SQL Server instance (/database/exchange/bcpconv_INSTANCE). These scripts accept the UTF-16LE file that should be converted as an argument in dependence of the name of the instance, e.g. for INSTANCE 'devel':

/database/exchange/bcpconv_devel DiversityCollectionCache_Test/Project_GFBio202000316SNSB/CacheCollectionSpecimen.csv

The scripts are designed as shown below (for INSTANCE 'devel'):

#!/bin/bash iconv -f UTF16LE -t UTF-8 /database/exchange/devel/\$1 \|sed \'1s/\^\\xEF\\xBB\\xBF//\' \| tr -d \'\\r\\000\'

AS a first step  iconv converts the file from UTF-16LE to UTF-8.

AS next step  sed removes the Byte Order Mark (BOM).

AS final step  tr  removes NULL characters.

Import with COPY

The script above is used as source for the import in Postgres using the psql COPY command as shown in the example below (for INSTANCE 'devel').

COPY \"Project_GFBio202000316SNSB\".\"CacheCollectionSpecimen_Temp\" FROM PROGRAM \'bash /database/exchange/bcpconv_devel DiversityCollectionCache_Test/Project_GFBio202000316SNSB/CacheCollectionSpecimen.csv\' with delimiter E\'\\t\' csv;

The options set the tab sign as delimiter:   with delimiter E\'\\t\'  and csv as format of the file: csv .

Within the csv file empty fields are taken as NULL-values and quotes empty strings "" are taken as empty string. All strings must be included in quotation marks ("...") and quotation marks (") within the strings must be replaced by 2 quotation marks ("") - see example below. This conversion is performed in the view described above. 

any\"string  &rarr;  \"any\"\"string\"

Bash conversion and Import with COPY relate to [ 5 ] in the overview image above. The COPY command is followed by a test for the existance of the created file.

 

Backup of the data from the main table

Before removing the old data from the main table, these data are stored in a backup table (see below and [ 6 ] in the overview image above). 

 

Removing data from the main table

After a backup was created and the new data are ready for import, the main table is prepared and as first step the old data are removed (see [ 7 ] in the overview image above).

 

Getting the primary key of the main table

To enable a fast entry of the data, the primary key must be removed. There the definition of this key must be stored for recreation after the import (see below and [ 8 ] in the overview image above). 

 

Removing the primary key from the main table

After the definition of the primary key has been extracted from the table, the primary key is removed (see below and [ 9 ] in the overview image above). 

 

Inserting data from the intermediate storage into the main table and clean up

After the data and the primary key has been removed, the new data are transferred from the temporary table into the main table (see [ 10 ] in the overview image above) and the number is compared to the number in the temporary table to ensure the correct transfer. 

In case of a failure the old data will be restored from the backup table (see [ 11 ] in the overview image above). 

After the data have been imported the primary key is restored (see [ 12 ] in the overview image above). Finally the intermediate table and the backup table (see [ 13 ] in the overview image above) and the csv file (see [ 14 ] in the overview image above) are removed. 

 

 

 

Jul 5, 2024

Cache Database

Transfer Via BCP Setup

Setup for the transfer via bcp

There are several preconditions to the export via bcp.  

bcp

The export relies on the external bcp software that must have been installed on the database server.To test if you have bcp installed, start the command lind and type bcp. If bcp is installed you get a result like shown below.

 

SQL-Server

The transfer via bcp is not possible with SQL-Server Express editions. To use this option you need at least SQL-Server Standard edition.

To enable the transfer the XP-cmd shell must be enabled on the SQL-Server. Choose Facets from the context menu as shown below.

In the window that will open change XPCmdShellEnabled to True as shown below.

 

Login cmdshell

The update script for the cache database will create a login cmdshell used for the transfer of the data (see below). This login will get a random password and connecting to the server is denied. This login is needed to execute the transfer procedures (see below) and should not be changed. The login is set to disabled as shown below.

Stored procedures

Furthermore 4 procedures and a table for the export of the data in a shared directory on the Postgres server are created (see below).

  

 

Login PostgresBulkExport

You have to create a Windows login (e.g. PostgresBulkExport) on the server with full access to the shared directory and set this account as the server proxy:

Open Windows Administrative Tools - Computer Management - System-Tools - Local Users and Groups
left klick on folder Users and select New User...

In the window that will open enter the details for the user and create the user (e.g. PostgresBulkExport) and click ** OK** to create the user.

In the File Explorer select the shared folder where the files from the export will be stored. From the context menu of the shared folder (e.g. u:\\postgres) select Properties In the Tab security click on button  Edit… In the window that will open click on button  Add… Type or select the User (e.g. PostgresBulkExport) and click OK

Select the new user in the list and in Permissons check Full Controll at Allow Leave with Button OK Close Window with Button OK

Go through the corresponding steps for the share (e.g. u:) to ensure access.

As an alternative you may use SQL to great the Login:

CREATE LOGIN \[DOMAIN\\LOGIN\] FROM WINDOWS;

where DOMAIN is the domain for the windows server and LOGIN is the name of the windows user.

exec sp_xp_cmdshell_proxy_account \'DOMAIN\\LOGIN\',\'[?password?]\';

where DOMAIN is the domain for the windows server, LOGIN is the name of the windows user and PASSWORD is the password for the login.

After the user is created and the permissions are set, set this user as cmdshell proxy (see below)

creat a new login:

  • Open Sql Server Managment Studio \
  • select Security \
  • select Logins \
    • in the context menu select New Login …
    • in the window that will open, click on the Search... button
      • Type in object name (e.g.: PostgresBulkExport)\
      • click on the Button Check Names  (name gets expanded with domain name)\
      • click button OK twice to leave the window and create the new login

in the context menu select Properties and include the login in the users of the cache database (see below)  

On the database server add this user as new login and add it to the cache database. This login must be in the database role CacheUser to be able to read the data that should be exported (see below).

 

Login PostgresTransfer

Another login (e.g. PostgresTransfer) on the Windows server is needed with read only access to the shared directory to read the exported data and import them into the Postgres database. This login is used by the Postgres server to access the shared directory. It does not need to have interactive login permissions.

 

Shared directory on Windows-server

On the Windows side the program needs an accessible shared directory in which sub-directories will be created and into which the files will be exported. This directory is made accessible (shared folder) to CIFS/SMB with read only access for the login used for the data transfer (e.g. PostgresTransfer). This shared directory is mounted on the Postgres server using CIFS (/database/exchange/INSTANCE). The INSTANCE is an identifier/server-name for the windows server. If more windows server deliver data to one postgres server these INSTANCE acronyms need to be unique for each windows server.

On the Windows-server this directory is as available as "postgres". The directory will be mounted depending on the INSTANCE under the path /database/exchange/INSTANCE. The corresponding fstab entries for the INSTANCEs 'bfl and 'devel' are:

/etc/fstab:
//bfl/postgres /database/exchange/bfl cifsro,username=PostgresTransfer,password=[[?password?]]
//DeveloperDB/postgres /database/exchange/devel cifsro,username=PostgresTransfer,password=[[?password?]]
command meaning
[?Instance?]/postgres is the UNC path to the shared folder
/database/exchange/[?Instance?] is local path on the postgres server where to mount the shared folder
PostgresTransfer is the windows user name to access the shared folder
?password? is the password for the windows user to access the shared folder

These mounts are needed for every Windows-server resp. SQL-Server instance. Instead of fstab you may use systemd for mounting.

 

Bugfixing and errorhandling

If you get the following error:

An error occurred during the execution of xp_cmdshell. A call to \'LogonUserW\' failed with error code: \'1326\'.

This means normally, that the passwort is wrong, but could also be a policy problem. First recrate the proxy user with the correct password:

use \[Master\];
-- Erase Proxy user:
exec sp_xp_cmdshell_proxy_account Null;
go

-- create proxy user:
exec sp_xp_cmdshell_proxy_account \'[?domain?]\\PostgresBulkExport\',\'[?your password for PostgresBulkExport?]\';\
go

And if this does not work, change the policy: Add proxy user in the group to run as batch job:

Open the Local Security Policy

  • Local Policies
    • User Rights Assignment

Log on as a batch job Add user or group ... Type user in object name field (e.g. PostgresBulkExport) Leave Local Security Policy editor by clicking Button OK twice

For further information see https://www.databasejournal.com/features/mssql/xpcmdshell-for-non-system-admin-individuals.html

NOT FOR PRODUCTION!

Setup of a small test routine.

Remove cmdshell account after your tests and recreate it with the CacheDB-update-scripts from DiversityCollection (Replace [?marked values?] with the values of your environment):

USE \[master\];
CREATE LOGIN \[cmdshell\] WITH PASSWORD = \'[?your password for cmdshell?]\',
CHECK_POLICY=OFF;
CREATE USER \[cmdshell\] FOR LOGIN \[cmdshell\];
GRANT EXEC ON xp_cmdshell TO \[cmdshell\];\

-- setup proxy
CREATE LOGIN \[[?domain?]\\PostgresBulkExport\] FROM WINDOWS;
exec sp_xp_cmdshell_proxy_account\
\'[?domain?]\\PostgresBulkExport\',\'[?your password for PostgresBulkExport?]\';\

USE \[[?DiversityCollection cache database?]\];
CREATE USER \[cmdshell\] FOR LOGIN \[cmdshell\];

-- allow execution to non privileged users/roles
grant execute on \[dbo\].\[procCmdShelltest\] to \[CacheUser\];
grant execute on \[dbo\].\[procCmdShelltest\] to \[[?domain?]\\AutoCacheTransfer\];


-- recreate Proxy User:

exec sp_xp_cmdshell_proxy_account Null;
go

-- create proxy user:
exec sp_xp_cmdshell_proxy_account '[?domain?]\\PostgresBulkExport\',\'[?your password for PostgresBulkExport?]\';
go

-- Make a test:
create PROCEDURE \[dbo\].\[procCmdShelltest\]
with execute as \'cmdshell\'  
AS
SELECT user_name();  \-- should always return \'cmdshell\'
exec xp_cmdshell \'dir\';
go

execute \[dbo\].\[procCmdShelltest\];
go

-- Should return two result sets
-- \'cmdshell\'
-- and the filelisting of the current folder


-- Check Proxy user:
-- The proxy credential will be called ##xp_cmdshell_proxy_account##.

select credential_identity from sys.credentials where name = '##xp_cmdshell_proxy_account##\';

-- should be the assigned windows user, e.g. [?domain?]\\PostgresBulkExport

 

Settings for the bulk transfer

To enable the bulk transfer via bcp enter the path of the directory on the Postgres server, the mount point of the postgres server and the bashfile as shown below.

To use the batch transfer for a project, click in the checkbox as shown below.

The image for the transfer will change from to . Now the data of every table within the project will be transferred via bcp. To return to the standard transfer, just deselect the checkbox.   

 

Role pg_execute_server_program

The user executing the transfer must be in the role pg_execute_server_program.

 

Jun 4, 2024

Cache Database Restrictions

Restrictions for the data transfer into the cache database

The restrictions of the published data are defined in the main database via projects , data withholding and embargos .

In the cache database further restrictions can be set for every project and include

The collectors may be anonymized. For the localisation systems it is possible to restrict the precision of the coordinates. To set these restrictions, click on the  button. A window as shown below will open.

Restrict the localisation systems , the site properties, the taxonomic groups , the material categories , the analysis and by moving the entries between the Not published and Published list. For an overview see a short tutorial .

Specimen

A filter for the specimen can be added in the first tab by the creation of a restriction applied on the specimen within a project as shown below and explained in the video Video starten.

Define the filter with the options described below. Test the restiction with the button and save it with the button. The restrictions will be converted into a SQL statement as shown below that will be applied in the filter for the transfer (see below). With the button you can remove the filter.

  • order by: The values that should be displayed in the result list.
  • /: Hide resp. show the area for the restriction.
  • : Start query according to the Query conditions
  • : Convert the Query conditions into a restriction
  • Project: Select projects that should be included in the restriction
    • + or |: If projects should be combined with AND resp. OR
    • : Add projects to the list for the restriction as shown below:
      • : Remove project from the list
  • Specimen Accession number: Filter for the accession number of the specimen
  • Storage: If a specimen part should be present
  • Transaction: If a transaction should be present
  • Image: If a specimen image should be present
Jan 14, 2025

Cache Database

Postgres

Administration of the databases

To create a Postgres cache database, you must be connected with a server running Postgres  (Version 12.0 or above). To connect to a server, click on the
button and enter the connection parameters. If no cache database has been created so far you get a message that no database is available and will be connected to the default database postgres.\

Click on the button to create a new cache database (see below). You will be asked for the name of
the database and a short description.

After the database was created, you have to update the database to the current version. Click on the Update
button to open a window listing all needed scripts. To run these scripts just click on the
Start update button. After the update the database is ready to take your data. Subsequent
updates may become necessary with new versions of the database. For an introduction see a short tutorial
.
To remove the current database from the server, just click on the button.

In the image on the right you see a screenshot from the tool pgAdmin III. You may use this tool
to inspect your data and administrate the database independent from DiversityCollection. Please keep in mind, that any
changes you insert on this level may disable your database from being used by DiversityCollection as a sink for your cache
data. The data are organized in schemata, with public as the default
schema. Here you find functions for marking the database as a module of the Diversity
Workbench and the version of the database. The function highresolutionimagepath translates local image paths into paths for high resolution images. To use this function it must be adapted to your local server settings. The tables in this schema
are TaxonSynonymy where the data derived from DiversityTaxonNames are stored and
ScientificTerm where the data derived from DiversityScientificTerms are stored. For every project a separate schema is created (here Project_BFLsorbusmmcoll). The project schemata contain 2
functions for the ID of the project and the version. The data are stored in the
tables while the packages in their greater part are realized as
views and functions extracting and converting the data from the
tables according to their requirements. 

Jan 14, 2025

Subsections of Postgres

Cache Database Postgres

Copy & Replace DB

Copy Postgres databases

To copy a Postgres database, click on the  button. A window will appear where you can copy the database including the data or as an empty database with the same tables etc. as the original database.

The option including the data only needs the name for the new database (see below).

To create an empty copy, you have to give the directory where two needed programs (pg_dump.exe and psql.exe) are located. If these are missing, you have to install Postgres first.

If you create an empty copy, a window will appear two times (see below) where you have to enter the password for accessing the database.

 

Replace Postgres databases

see chapter

 

Rename Postgres databases

To rename the current database, click on the button. A window will open where you can enter the new name for the database. Click OK to change the name..

 

Delete Postgres databases

To delete the current database just click on the button. You will get a message if you are sure where you have to click the YES button to delete the current database. 

 

 

 

Jun 4, 2024

Cache Database Postgres

Replace DB

Replace Postgres databases

To replace a database with another, click on the button. A window as below will appear. After you selected the database, which should be replaced, the software will compare the two databases and list differences (see below). If differences are found and you still want to replace the database, click on the [ Enable incongruent replacement ] button, to allow this. Then click no the Replace button. The database that should be replaced will be deleted and the current database will get the name of the replaced database.

The option  Restrict to sources with critical content  will restrict the output of the test to the main table as well as tables with content regarded as critical for a replacement. If you deselect this option, all tables will be listed as shown below.

If the number of datasets in a table corresponds in both databases, this table is regarded as congruent and marked with a (see above). If content is new, this will be marked with a and not regarded as critical. On the other hand missing content will be regarded as critical and marked with a (see below).

If the number of datasets differ between tables, but are not missing in eiter, this will be regarded as not critical and marked with (see below).

Further states for comparision of the tables are:

  • Update when any part needs an update to the current version.
  • Error when a part is missing as a whole.

With the option  Keep a copy of the current database a copy of the original database will be kept.

Jun 4, 2024

Cache Database

Packages

Administration of the Packages

The formatting of the data according to the specifications of webservices etc. is done with packages. There is a growing list of packages provided with the software. For new packages either turn to the developers or create a package of your own. The packages are realised as view, functions etc. reading the data in the tables without any changes to the data. They therefore can be inserted and removed without any effects on the original data. The naming of the objects within a package follow the schema [Name of the package]_... as shown in the images below. For an introduction see a short tutorial .  

To administrate the packages installed within one project, click on the button. A window as shown below will open listing all available packages.

Click on the button to establish the selected package. To ensure the current version of the package, click on the Update to vers. ... button (see below).

A window will open where all the needed scripts will be listed. For packages keeping the data in their own tables like ABCD it may be necessary to adapt the timeout for database commands. Click on the button and enter an appropriate value. For large amounts of data the value 0 is recommended, which means infinite. To remove a package use the button and the button to get information about the package. To inspect the data provided by the package, click on the button. A window as shown below will open listing all package related objects. In the case of ABCD BioCASe is depending on the schema public (see  below). For every object (table, view, column, ... ) the description is shown in the lower part of the window. With a click on the  button you can generate a description of all objects in the package.

With a click on the button you can generate a description of all objects in the package (see below).

The package ABCD creates additional views in the schema public as BioCASE is unable to handle schemata. Therefore the package ABCD can only be installed for one project (= schema) in a database. Some packages provide add-ons to adapt them to special specifications.

To export the content of a package, click on the button. A window as shown below will open listing the main views of the package. You can export the data as XML (creating a directory with one xml file for every view) or as SQLite database (creating a SQLite database containing the tables).

A package (e.g. ABCD) may contain e.g. materialized views. These need an update after the data have been transferred to the Postgres database. Click on the Transfer data button to update these views or perform other necessary steps after the data have been transferred. A window as shown below will open, listing the transfer steps for the package.

Choose the steps that should be transferred and click on the Start transfer button to transfer the data resp. update the materialized views.

 

Apr 9, 2025

Subsections of Packages

Cache Database

ABCD

Mapping for the ABCD package

  • ABCD_ContentContact: ABCD entity /DataSets/DataSet/ContentContacts/ContentContact

    • ProjectID: ID of the project. Retrieved from DiversityProjects. PK of table Project

    • Email: ABCD 2.06 entity /DataSets/DataSet/ContentContacts/ContentContact/Email. The email address of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table AgentContactInformation with data retrieved from DiversityAgents - Column Telephone

    • Name: ABCD 2.06 entity /DataSets/DataSet/ContentContacts/ContentContact/Name. The name of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table Agent with data retrieved from DiversityAgents -

    • Columns GivenName and InheritedName for persons resp. GivenName for other types

    • Phone: ABCD 2.06 entity /DataSets/DataSet/ContentContacts/ContentContact/Phone. The phone address of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table AgentContactInformation with data retrieved from DiversityAgents - Column Email

    • Address: ABCD 2.06 entity /DataSets/DataSet/ContentContacts/ContentContact/Address. The address address of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table AgentContactInformation with data retrieved from DiversityAgents - Column Address

  • ABCD_DatasetGUID: ABCD entity /DataSets/DataSet/DatasetGUID

    • ProjectID: ID of the project. Retrieved from DiversityProjects. PK of table Project
    • DatasetGUID: ABCD: Dataset/DatasetGUID. Retrieved from DiversityProjects - StableIdentifier (= basic address for stable identifiers + ID of the project)
  • ABCD_EFG_UnitStratigraphicDetermination_Chronostratigraphy:

    • ChronostratigraphicName: ABCD EFG: /EarthScienceSpecimen/UnitStratigraphicDetermination/ChronostratigraphicAttributions/ChronostratigraphicAttribution/ChronostratigraphicName . Retrieved from column DisplayText in table CacheCollectionEventProperty for Property Chronostratigraphy
  • ABCD_EFG_UnitStratigraphicDetermination_Lithostratigraphy: LithostratigraphicName: ABCD EFG: /EarthScienceSpecimen/UnitStratigraphicDetermination/LithostratigraphicAttributions/LithostratigraphicAttribution/LithostratigraphicName . Retrieved from column DisplayText in table CacheCollectionEventProperty for Property Lithostratigraphy

  • ABCD_MeasurementOrFact: ABCD entity /DataSets/DataSet/Units/Unit/MultiMediaObjects/MultiMediaObject/

    • Parameter: ABCD: Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/Parameter. Retrieved from table Analysis - DisplayText
    • UnitOfMeasurement: ABCD: Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/UnitOfMeasurement. Retrieved from table Analysis - MeasurementUnit
    • LowerValue: ABCD: Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/LowerValue. Retrieved from table IdentificationUnitAnalysis - AnalysisResult
    • MeasurementDateTime: ABCD: Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasurementDateTime. Retrieved from table IdentificationUnitAnalysis - AnalysisDate
    • MeasuredBy: ABCD: Unit/MeasurementsOrFacts/MeasurementOrFact/MeasurementOrFactAtomised/MeasuredBy. Retrieved from table IdentificationUnitAnalysis - ResponsibleName
    • AnalysisNumber: Retrieved from table IdentificationUnitAnalysis - AnalysisNumber
  • ABCD_MetaData: View on original ABCD_Metadata due to case sensitiv naming

  • ABCD_Metadata: ABCD entity /DataSets/DataSet/Metadata

    • Description_Representation_Details: ABCD: Dataset/Metadata/Description/Representation/Details. Retrieved from DiversityProjects - Project - PublicDescription
    • Description_Representation_Title: ABCD: Dataset/Metadata/Description/Representation/Title. Retrieved from DiversityProjects - Settings - ABCD - Dataset - Title
    • Description_Representation_URI: ABCD: Dataset/Metadata/Description/Representation/URI. Retrieved from DiversityProjects - Settings - ABCD - Dataset - URI
    • RevisionData_DateModified: ABCD: Dataset/Metadata/RevisionData/DateModified. Retrieved from the first level SQL-Server cache database for DiversityCollection corresponding to the date and time of the last transfer into the cache database (ProjectPublished.LastUpdatedWhen)
    • Owner_EmailAddress: ABCD: Dataset/Metadata/Owners/Owner/EmailAddress. Retrieved from DiversityProjects - Settings - ABCD - Owner - Email
    • Owner_LogoURI: ABCD: Dataset/Metadata/Owners/Owner/LogoURI. Retrieved from DiversityProjects - Settings - ABCD - Owner - LogoURI
    • IPRStatements_Copyright_URI: ABCD: Dataset/Metadata/IPRStatements/Copyrights/Copyright/URI. Retrieved from DiversityProjects - Settings - ABCD - Copyright - URI
    • IPRStatements_Disclaimer_Text: ABCD: Dataset/Metadata/IPRStatements/Disclaimers/Disclaimer/Text. Retrieved from DiversityProjects - Settings - ABCD - Disclaimers - Text
    • IPRStatements_Disclaimer_URI: ABCD: Dataset/Metadata/IPRStatements/Disclaimers/Disclaimer/URI. Retrieved from DiversityProjects - Settings - ABCD - Disclaimers - URI
    • IPRStatements_License_Text: ABCD: Dataset/Metadata/IPRStatements/Licenses/License/Text. Retrieved from DiversityProjects - Settings - ABCD - Disclaimers - Text
    • IPRStatements_License_URI: ABCD: Dataset/Metadata/IPRStatements/Licenses/License/URI. Retrieved from DiversityProjects - Settings - ABCD - Disclaimers - URI
    • IPRStatements_TermsOfUse_Text: ABCD: Dataset/Metadata/IPRStatements/TermsOfUseStatements/TermsOfUse/Text. Retrieved from DiversityProjects - Settings - ABCD - TermsOfUse - Text
    • Owner_Organisation_Name_Text: ABCD: Dataset/Metadata/Owners/Owner/Organisation/Name/Representation/Text. Retrieved from DiversityProjects - Settings - ABCD - Owner - OrganisationName
    • Owner_Organisation_Name_Abbreviation: ABCD: Dataset/Metadata/Owners/Owner/Organisation/Name/Representation/Abbreviation. Retrieved from DiversityProjects - Settings - ABCD - Owner - OrganisationAbbrev
    • Owner_Address: ABCD: Dataset/Metadata/Owners/Owner/Addresses/Address. Retrieved from DiversityProjects - Settings - ABCD - Owner - Address
    • Owner_Telephone_Number: ABCD: Dataset/Metadata/Owners/Owner/TelephoneNumbers/TelephoneNumber/Number. Retrieved from DiversityProjects - Settings - ABCD - Owner - Telephone
    • IPRStatements_IPRDeclaration_Text: ABCD: Dataset/Metadata/IPRStatements/IPRDeclarations/IPRDeclaration/Text. Retrieved from DiversityProjects - Settings - ABCD - IPR - Text
    • IPRStatements_IPRDeclaration_Details: ABCD: Dataset/Metadata/IPRStatements/IPRDeclarations/IPRDeclaration/Details. Retrieved from DiversityProjects - Settings - ABCD - IPR - Details
    • IPRStatements_IPRDeclaration_URI: ABCD: Dataset/Metadata/IPRStatements/IPRDeclarations/IPRDeclaration/URI. Retrieved from DiversityProjects - Settings - ABCD - IPR - URI
    • IPRStatements_Copyright_Text: ABCD: Dataset/Metadata/IPRStatements/Copyrights/Copyright/Text. Retrieved from DiversityProjects - Settings - ABCD - Copyright - Text
    • IPRStatements_Copyright_Details: ABCD: Dataset/Metadata/IPRStatements/Copyrights/Copyright/Details. Retrieved from DiversityProjects - Settings - ABCD - Copyright - Details
    • IPRStatements_License_Details: ABCD: Dataset/Metadata/IPRStatements/Licenses/License/Details. Retrieved from DiversityProjects - Settings - ABCD - Disclaimers - Details
    • IPRStatements_TermsOfUse_Details: ABCD: Dataset/Metadata/IPRStatements/TermsOfUseStatements/TermsOfUse/Details. Retrieved from DiversityProjects - Settings - ABCD - TermsOfUse - Details
    • IPRStatements_TermsOfUse_URI: ABCD: Dataset/Metadata/IPRStatements/TermsOfUseStatements/TermsOfUse/URI. Retrieved from DiversityProjects - Settings - ABCD - TermsOfUse - URI
    • IPRStatements_Disclaimer_Details: ABCD: Dataset/Metadata/IPRStatements/Disclaimers/Disclaimer/Details. Retrieved from DiversityProjects - Settings - ABCD - Disclaimers - Details
    • IPRStatements_Acknowledgement_Text: ABCD: Dataset/Metadata/IPRStatements/Acknowledgements/Acknowledgement/Text. Retrieved from DiversityProjects - Settings - ABCD - Acknowledgements - Text
    • IPRStatements_Acknowledgement_Details: ABCD: Dataset/Metadata/IPRStatements/Acknowledgements/Acknowledgement/Details. Retrieved from DiversityProjects - Settings - ABCD - Acknowledgements - Details
    • IPRStatements_Acknowledgement_URI: ABCD: Dataset/Metadata/IPRStatements/Acknowledgements/Acknowledgement/URI. Retrieved from DiversityProjects - Settings - ABCD - Acknowledgements - URI
    • IPRStatements_Citation_Text: ABCD: Dataset/Metadata/IPRStatements/Citations/Citation/Text. Retrieved from DiversityProjects: First dataset in table ProjectReference where type = ‘BioCASe (GFBio)’. Authors from table ProjectAgent with type = ‘Author’ according to their sequence. If none are found ‘Anonymous’. Current year. Content of column ProjectTitle in table Project. Marker ‘[Dataset]’. ‘Version: ’ + date of transfer into the ABCD tables as year + month + day: yyyymmdd. If available publishers: ‘Data Publisher: ’ + Agents with role ‘Publisher’ from table ProjectAgent. URI from table ProjectReference if present. If entry in table ProjectReference is missing taken from Settings - ABCD - Citations - Text
    • IPRStatements_Citation_Details: ABCD: Dataset/Metadata/IPRStatements/Citations/Citation/Details. Retrieved from DiversityProjects - Settings - ABCD - Citations - Details
    • IPRStatements_Citation_URI: ABCD: Dataset/Metadata/IPRStatements/Citations/Citation/URI. Retrieved from DiversityProjects - Settings - ABCD - Citations - URI
    • DatasetGUID: ABCD: Dataset/DatasetGUID. Retrieved from DiversityProjects - StableIdentifier (= basic address for stable identifiers + ID of the project)
  • ABCD_MultiMediaObject: ABCD entity /DataSets/DataSet/Units/Unit/MultiMediaObjects/MultiMediaObject/

    • fileUri: ABCD: Unit/MultiMediaObjects/MultiMediaObject/FileURI. Retrieved from table CollectionSpecimenImage - URI
    • fileFormat: ABCD: Unit/MultiMediaObjects/MultiMediaObject/Format. Retrieved from table CollectionSpecimenImage - URI - extension
    • DisplayOrder: Retrieved from table CollectionSpecimenImage - DisplayOrder converted to 8 digit text with leading 0
    • ProductURI: ABCD: Unit/MultiMediaObjects/MultiMediaObject/ProductURI. Retrieved from table CollectionSpecimenImage - URI. For projects where a high resolution image is available, the path of the high resolution image
    • IPR_License_Text: ABCD: Unit/MultiMediaObjects/MultiMediaObject/IPR/Licenses/License/Text. Retrieved from table CollectionSpecimenImage - LicenseType
    • IPR_License_Details: ABCD: Unit/MultiMediaObjects/MultiMediaObject/IPR/Licenses/License/Details. Retrieved from table CollectionSpecimenImage - LicenseNotes
    • IPR_License_URI: ABCD: Unit/MultiMediaObjects/MultiMediaObject/IPR/Licenses/License/Details. Retrieved from table CollectionSpecimenImage - LicenseURI
    • CreatorAgent: ABCD: Unit/MultiMediaObjects/MultiMediaObject/Creator. Retrieved from table CollectionSpecimenImage - CreatorAgent
    • IPR_Copyright_Text: ABCD: Unit/MultiMediaObjects/Copyrights/Copyright/Text. Retrieved from table CollectionSpecimenImage - CopyrightStatement with inserted ©
    • IPR_TermsOfUse_Text: ABCD: Unit/MultiMediaObjects/TermsOfUseStatements/TermsOfUse/Text. Retrieved from DiversityProjects - Settings - ABCD - TermsOfUse - Text
  • ABCD_TechnicalContact: ABCD entity /DataSets/DataSet/TechnicalContacts/TechnicalContact

    • ProjectID: ID of the project. Retrieved from DiversityProjects. PK of table Project

    • Email: ABCD 2.06 entity /DataSets/DataSet/TechnicalContacts/TechnicalContact/Email. The email address of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table AgentContactInformation with data retrieved from DiversityAgents - Column Telephone

    • Name: ABCD 2.06 entity /DataSets/DataSet/TechnicalContacts/TechnicalContact/Name. The name of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table Agent with data retrieved from DiversityAgents - Columns GivenName and InheritedName for persons resp. GivenName for other types

    • Phone: ABCD 2.06 entity /DataSets/DataSet/TechnicalContacts/TechnicalContact/Phone. The phone of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table AgentContactInformation with data retrieved from DiversityAgents - Column Email

    • Address: ABCD 2.06 entity /DataSets/DataSet/TechnicalContacts/TechnicalContact/Address. The address of the agent.

      Retrieved from DiversityProjects - ProjectAgent - linked via URL to the source in table AgentContactInformation with data retrieved from DiversityAgents - Column Address

  • ABCD_Unit:

  • ABCD_Unit_Associations_UnitAssociation: ABCD entity /DataSets/DataSet/Units/Unit/Associations/UnitAssociation

    • AssociatedUnitID: ABCD: Unit/Associations/UnitAssociation/AssociatedUnitID. Retrieved from DiversityCollection: AccessionNumber of the associated specimen if present, otherwise the CollectionSpecimenID + ’ / ’ + IdentificationUnitID of the Unit + only if a part is present ’ / ’ + AccessionNumber of the part if present otherwise SpecimenPartID
    • SourceInstitutionCode: ABCD: Unit/Associations/UnitAssociation/AssociatedUnitSourceInstitutionCode. Retrieved from DiversityProjects - Settings - ABCD - Source - InstitutionID
    • SourceName: ABCD: Unit/Associations/UnitAssociation/AssociatedUnitSourceName. Retrieved from DiversityProjects, column Project in table Project
    • AssociationType: ABCD: Unit/Associations/UnitAssociation/AssociationType. Retrieved from DiversityCollection, column RelationType in table IdentificationUnit AssociationType_Language: ABCD: Unit/Associations/UnitAssociation/AssociationType. Retrieved from View = en
    • Comment: ABCD: Unit/Associations/UnitAssociation/Comment. Retrieved from DiversityCollection, column RelationType + ’ on ’ + LastIdentificationCache from table IdentificationUnit from the related unit
    • Comment_Language: ABCD: Unit/Associations/UnitAssociation/Comment. Retrieved from View = en
    • IdentificationUnitID: Retrieved from DiversityCollection, column IdentificationUnitID from table IdentificationUnit
    • UnitID: ABCD: Unit/Associations/UnitAssociation/AssociatedUnitID. Retrieved from DiversityCollection, CollectionSpecimenID of specimen + ‘-’ + IdentificationUnitID of unit + ‘-’ + SpecimenPartID of part if part is present
    • KindOfUnit: Retrieved from DiversityCollection, column MaterialCategory in table CollectionSpecimenPart
    • SpecimenPartID: Retrieved from DiversityCollection, column SpecimenPartID in table CollectionSpecimenPart
    • CollectionSpecimenID: Retrieved from DiversityCollection, column CollectionSpecimenID in table CollectionSpecimen
  • ABCD_Unit_Gathering: ABCD entity /DataSets/DataSet/Units/Unit/Gathering Country_Name: ABCD: Unit/Gathering/Country/Name. Retrieved from column CountryCache in table CollectionEvent

    • ISO3166Code: ABCD: Unit/Gathering/Country/ISO3166Code. Retrieved from DiversityGazetteer according to column CountryCache in table CollectionEvent
    • DateTime_ISODateTimeBegin: ABCD: Unit/Gathering/DateTime/ISODateTimeBegin. Retrieved from columns CollectionYear, CollectionMonth and CollectionDay in table CollectionEvent
    • LocalityText: ABCD: Unit/Gathering/LocalityText. Retrieved from column LocalityDescription in table CollectionEvent
    • SiteCoordinateSets_CoordinatesLatLong_LatitudeDecimal: ABCD: Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/LatitudeDecimal. Retrieved from column AverageLatitudeCache in table CollectionEventLocalisation depending on the sequence defined for the project
    • SiteCoordinateSets_CoordinatesLatLong_LongitudeDecimal: ABCD: Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/LongitudeDecimal. Retrieved from column AverageLongitudeCache in table CollectionEventLocalisation depending on the sequence defined for the project
    • IdentificationUnitID: Retrieved from column IdentificationUnitID in table IdentificationUnit
    • SiteCoordinateSets_CoordinatesLatLong_SpatialDatum: ABCD: Unit/Gathering/SiteCoordinateSets/SiteCoordinates/CoordinatesLatLong/SpatialDatum. Retrieved from View = WGS84
  • ABCD_Unit_Gathering_Agents: ABCD entity /DataSets/DataSet/Units/Unit/Gathering

    • GatheringAgent_AgentText: ABCD: Unit/Gathering/Agents/GatheringAgent/AgentText. Retrieved from columns CollectorsName + if present ’ (no. ’ + CollectorsNumber + ‘)’ in table CollectionAgent
    • CollectionSpecimenID: Retrieved from column CollectionSpecimenID in table CollectionAgent
  • ABCD_Unit_Gathering_Stratigraphy_ChronostratigraphicTerm: ABCD entity /DataSets/DataSet/Units/Unit/Gathering

    • Term: ABCD: Unit/Gathering/Stratigraphy/ChronostratigraphicTerms/ChronostratigraphicTerm. Retrieved from column DisplayText in table CacheCollectionEventProperty for Property Chronostratigraphy
  • ABCD_Unit_Gathering_Stratigraphy_LithostratigraphicTerm: ABCD entity /DataSets/DataSet/Units/Unit/Gathering

    • Term: ABCD: Unit/Gathering/Stratigraphy/LithostratigraphicTerms/LithostratigraphicTerm. Retrieved from column DisplayText in table CacheCollectionEventProperty for Property Lithostratigraphy
  • ABCD_Unit_Identification_Extension_EFG: ABCD entity /DataSets/DataSet/Units/Unit/

  • ABCD_Unit_SpecimenUnit: ABCD search type within an identification unit

    • NomenclaturalTypeDesignation_TypifiedName_FullScientificName: ABCD: /DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/TypifiedName/FullScientificNameString. Retrieved from TaxonomicName in table Identification
    • NomenclaturalTypeDesignation_TypeStatus: ABCD: /DataSets/DataSet/Units/Unit/SpecimenUnit/NomenclaturalTypeDesignations/NomenclaturalTypeDesignation/TypeStatus. Retrieved from column TypeStatus in table Identification
    • Preparation_PreparationType: ABCD: /DataSets/DataSet/Units/Unit/SpecimenUnit/Preparations/Preparation/PreparationType. Retrieved from column MaterialCategory in table CollectionSpecimenPart and translated according to GBIF definitions resp. no treatment for observations
Apr 10, 2025

Cache Database Packages

Add Ons

Administration of the Add-Ons for Packages

For certain packages there are add-ons available to adapt a package to the special specifications of e.g. a project. To add an add-on, click on the button as shown below. A window as shown below will open listing all available add-ons.

After the add-on has been added, you need to update it to the current version of the add on with a click on the Update to vers. ... button (see below). A window will open where all the needed scripts will be listed. Some add-ons are exclusive, meaning that no further add-ons can be added and further updates of the package are organized via the add-on as shown below. To remove an add-on you have to remove the package with a click on the button. With a click on the button to get information about the add-on.

An Add-on defines a version of the package it is compatible with. Add-ons can not be removed as they perform canges in the package. To remove an Add-on, remove the package and reinstall it. If a package containing an Add-on needs an update you have to remove the package as well and reinstall it.

Jun 4, 2024

Diversity Collection

BioCASE

To publish your data on portals like GBIF data can be provided in the ABCD standard using BioCASe for mapping your data (see below). Use the ABCD package to convert the data into a format prepared for BioCASe. Configure the database and map the fields according to the examples.

For details about the BioCASe software please see the provided documentation. DiversityCollection transfers the data for every project in a separate schema. As BioCASe so far is unable to handle schemata in Postgres additional views for the package ABCD are created in the schema public and you need to provide a single database for every project.

 

Step by Step

To provide the data for BioCASe you need to transfer the data from DiversityCollection together with all auxiliary sources (Taxa, References, Gazetteer) depending on your data from the SQL-Server database to the SQL-Server cache database and from there to the Postgres cache database. In the Postgres database you need the package ABCD for mapping your data to BioCASe.

 

Metadata

The metadata for ABCD are taken from the project data in the module DiversityProjects to which the data in DiversityCollection are linked to. The metadata include links to DiversityAgents within DiversityProjects. That means that to receive all needed data in the project you must ensure that the agent data used within the project have been transferred to the Cache database as well. If addresses of the agents are needed, these must be unlocked. For further information see the manuals within DiversityProjects and DiversityAgents. The table below shows the source for several ABCD nodes.

Database Table Column ABCD Node
DiversityAgents Agent
DiversityAgents AgentContactInformation Email  
DiversityAgents AgentContactInformation Address  
DiversityProjects Project

These metadata are defined as Settings as shown below as children of the setting ABCD. The following ABCD topics are taken from the settings in DiversityProjects:

  • TaxonomicGroup
  • Dataset including GUID, Coverage, Version, Creators, Icon, Dates etc.
  • TechnicalContact
  • ContentContact
  • OtherProvider
  • Source
  • Owner
  • IPR
  • Copyright
  • TermsOfUse
  • Disclaimers
  • Acknowledgements
  • Citations (if Reference is missing - see below)
  • RecordBasis
  • RecordURI
  • KindOfUnit
  • HigherTaxonRank

For further information about the configuration of the settings in DiversityProjects, please see the manual for this module.

 

Metadata - Stable identifier = DatasetGUID

The DatasetGUID in ABCD is taken from the stable identifier defined in the module DiversityProjects for the database in combination with the ID of the project. To set the stable identifier choose Administration - Stable identifier from the menu in DiversityProjects and enter the basic path (e.g. see below). This stable identifier can only be set once. After it is set you will get a message as shown below.

Metadata - License

The license information for ABCD are taken from the first entry in the IPR & Licenses section in DiversityProjects (see below) where the first entry is the one entered first.

Metadata - Citation text

The citation for the project follows the form [<Authors>].] [<Title>][. [Dataset]. Data Publisher:] [<Data_center_name>]. [<URI>].

The Authors are taken from the Agents section (see below) where all agents with the role Author are included according to their sequence in the list and separated by ;.

The [<Publication_year>] is the year of the publication i.e.the current year. The [ <Title>] corresponds to the[Title] of the project. The [<Data_center_name>] istaken from the Agents section. Here the first agent with the role Publisher is used. The [<URI>] is taken from the field URI of the citation with the type BioCASe (GFBio) in the Citations & References section (see below).

 

Gathering - IsoCode

The IsoType for a country is taken from corresponding information in the module DiversityGazetteer. To ensure these information is available in the cache database, insert a source for a gazetteer project containing this information (see below).

 

Identification

The ABCD schema provided with this software is NOT including information from the module DiversityTaxonNames, so sources for Taxa are not needed by default. If for your own needs you decide to add additional data for the identifications from the module DivesityTaxonNames, ensure that the data corresponding to the names in your identifications are transferred from DiversityTaxonNames (see below).

 

Postgres database

The package ABCD providing the objects for mapping your data for BioCASE contains objects in the schema public. Therefore you need one database for every project you want to provide for BioCASE and the sources mentioned above have to be transferred in each of these databases.

 

Transfer

To provide the data for BioCASE you need to transfer all auxiliary sources as described above (Taxa, References, Gazetteer) depending on your data and the project data themselves from the SQL-Server databases to the SQL-Server cache database and from there to the Postgres cache database . The package itself needs a further transfer step if data have been changed after the creation of the package as the parts of the data in the Postgres database are imported into tables or materialized views according to the specifications of ABCD.

Dec 4, 2024

Subsections of Import

Import GFBio

Import GFBio

Import data from GFBio online service

For a short introduction see .

In the menu choose Data - Import - GFBio to open a window as shown below. Enter the login data (User + Password) and the Key of the project. To retrieve the data click on the Connect button. The software will retrieve the data provided for the project as shown below. Information concerning agents will be taken from the selected DiversityAgents database and the project selected within this database. The GFBio portal does not enforce roles for all the agents enter. If you want to add a role for agents where no role has been given in the GFBio portal, you may choose a default.

If you get an error message about missing identifier types, please open Administration - Identifier types… and insert the missing types.

If all needed types are available click Start import to import the data either into an existing project or a new project that you may include in an existing parent project.

May 3, 2024

Diversity Collection

Import Wizard

The examples below are from the module DiversityAgents, but are valid for any other module as well.

With the current solution please ensure that there are no concurrent imports in the same database.

For some imports like e.g. for Collections in DiversityCollection you will be reminded to update the cache tables for the hierarchies.

With this import routine, you can import data from text files (as tab-separated lists) into the database. A short introduction is provided in a video Video starten. Choose Data Import Wizard Agent from the menu. A window as shown below will open that will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choose for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

Choosing the File and Settings

  • File: As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Choosing a file will automatically set the default directory for the import files. To avoid setting this directory, deselect the option Adapt default directory in the context menu of the button to open the file.
  • Encoding: Choose the Encoding of the file, e.g. Unicode. The preferred encoding is UTF8.
  • Lines: The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the
  • First line: The option First line contains the column definition decides if this line will not be imported.
  • Duplicates: To avoid duplicate imports you can Use the default duplicate check - see a video Video starten for an explanation.
  • Language: If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data.
  • Line break: With the option Translate \r\n to line break the character sequence \r\n in the data will be translated in a line break in the database.
  • SQL statements: To save all SQL statements that are generated during a test or import, you can check the option Record all SQL statements. Video starten
  • Schema: Finally you can select a prepared Schema (see chapter Schema below) for the import.

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

The import of certain tables can be paralleled. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import information of logging columns like who created and changed the data, click on the include logging columns button in the header line. This will include additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue background (see below and chapter Table data).

Merging data

You can either import your data as new data or Merge them with data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported. Otherwise the data will be updated.

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

Empty content will be ignored e.g. for the Merge or Update option. To remove content you have to enter the value NULL. As long as the column will allow emty values, the content will be removed using the NULL value.

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you which actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive columns, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparison   = For all merge types other than insert columns for comparison with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

Testing

- To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and then click on the Test data in line:  button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display any errors that occurred as shown below. All datasets marked with a red background, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets:

  • INSERT
  • MERGE
  • UPDATE,
  • No difference
  • Attach
  • No data

The colors of the table columns indicate whether a column is decisive , a key column or an attachment column .  

If you suspect, that the import file contains data already present in the database, you may test this and extract only the missing lines in a new file. Choose the attachment column (see chapter Attaching data) and click on the button Check for already present data. The data already present in the database will be marked red (see below). Click on the button Save missing data as text file to store the data not present in the database in a new file for the import. The import of agents contains the option Use default duplicate check for AgentName that is selected by default. To ensure the employment of this option the column AgentName must be filled according to the generation of the name by the insert trigger of the table Agent (InheritedNamePrefix + ' ' + Inheritedname + ', ' + GivenName  + ' ' + GivenNamePostfix + ', ' + InheritedNamePostfix + ', ' + AgentTitle - for details, see the documentation of the database).

If you happen to get a file with a content as shown below, you may have seleted the wrong encoding or the encoding is incompatible. Please try to save the original file as UTF8 and select this encoding for the import. 

Import

- With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below). You optionally can include a description of your schema and with the button you can generate a file containing only the description.


Schedule for import of tab-separated text files into DiversityAgents

  • Target within DiversityAgents: Agent
  • Database version: 02.01.13
  • Schedule version: 1
  • Use default duplicate check:
  • Lines: 2 - 7
  • First line contains column definition:
  • Encoding: UTF8
  • Language: US

Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings according to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

Description

- A description of the schema may be included in the schema itself or with a click on the Import button generated as a separate file. This file will be located in a separate directory Description to avoid confusion with import schemas. An example for a description file is shown below, containing common settings, the treatment of the file columns and interface settings as defined in the schema.

Jan 14, 2025

Subsections of Wizard

Diversity Collection

Import Wizard

Columns

If the content of a file should be imported into a certain column of a table, mark it with the checkbox.

Decisive columns

The import depends on the data found in the file where certain columns can be selected as decisive. Only those lines will be imported where data are found in any of these decisive columns. To mark a column as decisive, click on the icon at the beginning of the line (see below).

In the example shown below, the file column Organims 2 was marked as decisive. Therefore only the two lines containing content in this column will be imported.

 

Key columns

For the options Merge, Update and Attach the import compares the data from the file with those already present in the database. This comparison is done via key columns. To make a column a key column, click on the icon at the beginning of the line. You can define as many key columns as you need to ensure a valid comparison of the data.

 

Source

The data imported into the database can either be taken From file or the same value that you enter into the window or select from a list can be used For all datasets. If you choose the From file option, a window as shown below will pop up. Just click in the column where the data for the column should be taken from and click OK (see below).

If you choose the For all option, you can either enter text, select a value from a list or use a checkbox for YES or NO.

 

Transformation

The data imported may be transformed e.g. to adapt them to a format demanded by the database. For further details please see the chapter Transformation.

 

Copy

If data in the source file are missing in subsequent lines as shown below,

you can use the Copy line option to fill in missing data as shown below where the blue values are copied into empty fields during the import. Click on the button to ensure that missing values are filled in from previous lines.

 

 

Prefix and Postfix

In addition to the transformation of the values from the file, you may add a pre- and a postfix. These will be added after the transformation of the text. Double-click in the field to see or edit the content. The pre- and a postfix values will only be used, if the file contains data for the current position.

Column selection

If for any reason, a column that should take its content from the imported file misses the position of the file or you want to change the position click on the button. In case a position is present, this button will show the number of the column. A window as shown below will pop up where you can select and change the position in the file.

 

Multi column

The content of a column can be composed from the content of several columns in the file. To add additional file columns, click on the button. A window as shown below will pop up, showing you the column selected so far, where the sequence is indicated in the header line. The first column is marked with a blue background while the added columns are marked with a green background (see below).

To remove an added column, use the button (see below).

 

Information

The button opens a window displaying the information about the column. For certain datatypes additional options are included (see Pre- and Postfix).

Oct 11, 2024

Diversity Collection

Import Wizard

Transformation

The data imported may be transformed e.g. to adapt them to a format demanded by the database. A short introduction is provided in a video Video starten. Click on the button to open a window as shown below.

Here you can enter 4 types of transformation that should be applied to your data. Cut out parts,  Translate contents from the file, RegEx apply regular expressions or Replace text in the data from the file. All transformations will be applied in the sequence they had been entered. Finally, if a prefix and/or a postfix are defined, these will be added after the transformation. To remove a transformation, select it and click on the button.

 

Cut

With the cut transformation you can restrict the data taken from the file to a part of the text in the file. This is done by splitters and the position after splitting. In the example below, the month of a date should be extracted from the information. To achieve this, the splitter '.' is added and than the position set to 2. You can change the direction of the sequence with the button Seq starting at the first position and starting at the last position. Click on the button Test the transformation to see the result of your transformation.

 

Translate

The translate transformation translates values from the file into values entered by the user. In the example above, the values of the month cut out from the date string should be translated from roman into numeric notation. To do this click on the button to add a translation transformation (see below). To list all different values present in the data, click on the button. A list as shown below will be created. You may as well use the and buttons to add or remove values from the list or the button to clear the list. Then enter the translations as shown below. Use the save button to save entries and the Test the transformation button to see the result. 

To load a predefined list for the transformation use the button. A window as shown below will open. Choose the encoding of the data in your translation source, if the first line contains the column definition and click on the  button to open a file. Click OK to use the values from the file for the translation.

 

Regular expression

The RegEx transformation using regular expressions will transform the values according to the entered Regular expression and Replace by vales. For more details please see documentations about regular expressions.

 

Replacement

The replacement transformation replaces any text in the data by a text specified by the user. In the example shown below, the text "." is replaced by "-". 

 

Calculation 

The Σ calculation transformation performs a calculation on numeric value, dependent on an optional condition. In the example below, 2 calculations were applied to convert 2-digit values into 4 digit years.

 

Filter 

The filter transformation compares the values from the file with a value entered by the user. As a result you can either Import content of column in file or Import a fixed value. To select another column that should be compared, click on the button and choose a column from the file in the window that will open. If the column that should be compared is not the column of the transformation, the number of the column will be shown instead of the symbol. To add further filter conditions use the button. For the combination of the conditions you can choose among AND and OR. 

Oct 10, 2024

Diversity Collection

Import Wizard

Tutorial

This tutorial demonstrates the import of a small file into the database. The following data should be imported (the example file is included in the software):   At the end of this tutorial you will have imported several datasets and practiced most of the possibilities provided by the import wizard. The import is done in 2 steps to demonstrate the attachment functionality of the wizard.

Import of the collection events

Choose Data → Import → Wizard → import Specimen ... from the menu. A window as shown below will open. This will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choose for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

 

Choosing the File

As a first step, choose the File] from where the data should be imported. The currently supported format is [tab-separated text]. Than choose the Encoding of the file, e.g. Unicode. The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The [not imported parts] in the file are indicated as shown below with a gray background. If the First line contains the column definition this line will not be imported as well. If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data. Finally you can select a prepared Schema (see chapter Schema below) for the import.

 

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

Certain tables can be imported in parallel. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import information of logging columns like who created and changed the data, click on button in the header line. This will include a additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

 

Attaching data

You can either import your data as new data or [Attach] them to data in the database. Select the import step [Attachment] from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue backgroud (see below and chapter Table data).

 

Merging data

You can either import your data as new data or Merge them wih data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported, otherwise the data will be updated..

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

 

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you what actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive colums, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparision   = For all merge types other than insert columns for comparision with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for you test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display you any errors that occurred as shown below. All datasets marked with a [red backgroud], produced some error.  

To see the list of all errors, double click in the [error list window] in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets: [INSERT], [MERGE], [UPDATE], [No difference]. [Attach], [No data]. The colors of the table colums indicate whether a colums is [decisive] , a [key column] or an [attachment column].  

In case you get an error because you can not specify the analysis you may have to enter an analysis. Choose Administration - Analysis from the menu. If no analysis is available create a new analysis and link it to your project and the taxonomic groups that are imported. For more datails see the chapter Analysis.

 

Import

With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings.

Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

 

 

Jan 14, 2025

Diversity Collection

Replication

If you wish to work with your data on a local database (called subscriber), e.g. on your laptop, not linked to a database on a central server (called publisher) and these data should be synchronized with the data in the database on the server, you may use the replication function of DiversityCollection. To install the database on your local computer see the installation section.

To use the replication function you require the roles Replicator or Administrator.

Add Publisher

To define a publishing database choose Data Replication Add Publisher from the menu. A window will open where you choose the publisher. After the publisher is set, you may transfer data between your local database (subscriber) and the publisher. This function is only available for administrators.

Remove Publisher

To remove a publisher from the list choose Data Replication Publisher Remove from the menu (where Publisher is the name of the publishing database on the publishing server). This function is only available for administrators.

 

Clean database

Initially you may wish to remove all previous data from your local database (subscriber). Choose Data Replication Clean database ... from the menu. A window will open as shown below where you may choose the ranges which should be cleared:

  • Definitions = the basic definitions within the database, e.g. the available taxonomic groups.
  • Descriptions = the descriptions and their translations of the tables and columns of the database.
  • Project, User = the available projects and users.
  • Basic data = basic data like the collection.
  • Data = the specimen, organisms etc.

Choose the data ranges you wish to clear and click on the button. All tables which contain data will be listed as shown below.

 

Choose the tables which should be cleared and click on the Clean database button. Please keep in mind that you can not delete data from a table as long as there is data in a related table depending on the data you wish to delete. The sequence of the tables is organized to avoid these problems.

 

Download

To download data from the publisher choose Data Replication Publisher Download from the menu (where Publisher is the name of the publishing database on the publishing server). A form will open as shown below. Choose the project of the data and the data ranges (see above) which you wish to download. Click on the button to list the tables containing data. To start the download click on the Start download button. With the Force download, ignore conflicts option you can decide whether or not the data in your local database (= Subscriber) should be checked for changes before you download the data from the publisher.

If not all data should be included in the replication, you have the option to set a filter. Click on the button for the table where the data should be filtered to set this filter. A window as shown below will open.

All columns of the table will be listed and allow you to set the filter. To inspect the filtered data, click on the button. Click on the button to see the current filter. If a filter is set this will be indicated with a blue background .

 

Merge

To merge data from your local subscriber database with the publisher you must first choose a project. Choose Data Replication Publisher Merge from the menu (Publisher is the name of the publishing database on the publishing server). As described for the download, choose the data ranges and click on the button. To start the upload click on the Start merge button.

 

Upload

To transfer data from your local subscriber database to the publisher you must first choose a project. Choose Data Replication Publisher Upload** from the menu ([Publisher] is the name of the publishing database on the publishing server). As described for the download, choose the data ranges and click on the button. To start the upload click on the Start upload button. With the Force upload, ignore conflicts option you can decide whether or not the data in server (= Publisher) should be checked for changes before you upload the data from your local database (= Subscriber).

As described for the download, data may be filtered with a click on the button (see above).

 

Tools

To fix problems that may interfere with the replication you find some tools under the menu Data Replication Publisher Tools ... from the menu (Publisher is the name of the publishing database on the publishing server). A window will open as shown below.

You may synchronize the RowGUIDs between basic subscriber and publisher tables if for any reason these are differing, e.g. due to manual insert. Choose the table that should be synchronized. The tables will be compared for both publisher and subscriber. The datasets with identical key but different RowGUID will be listed (see above). Click on the Start update button to synchronize the RowGUIDs

 

Conflict

If the transfer of data was successful, the numbers of the transferred data will be shown as below.

During the download or upload a conflict may occur, if the data has been edited in both databases. This will be indicated as shown below.

Click on the button to open a window as shown below where you can choose between the two versions of the data as found in the publisher and the subscriber database.

The conflicting columns are marked red. For text values the program will create a combination of both values (see above) in a merged version of the data. Choose the preferred version of the data and click Solve conflict button. If you can not solve a conflict, use the Ignore conflict or Stop conflict resolution buttons respectively.

 

Report

At the end of each transfer a report will be created with a summary for every table which has been included.

 

Jan 14, 2025

Diversity Collection

Stable identifier

Stable identifiers are generated from a basic URL and the IDs from the database. To set the basic URL select Administration - Stable identifier ... from the menu. A window as shown below will open, where you can set the basic URL for the stable identifier either for the whole database or for every project. With the button you can copy the current URL to all projects in the list.

The Test button creates a QR code for the URL as shown above using a google api (http://chart.apis.google.com). The stable identifier consits of the basis address as set above, followed by the part that identifies the object in the database as shown in the examples below. For an introduction see a short tutorial .

Icon Table Stable identifier
Specimen http://id.snsb.info/snsb/Collection_SNSB/312 = [Server]/[Instance]/[Alias for database]/[CollectionSpecimenID]
Unit http://id.snsb.info/snsb/Collection_SNSB/312/789 = [Server]/[Instance]/[Alias for database]/[CollectionSpecimenID]/[IdentificationUnitID]
Part http://id.snsb.info/snsb/Collection_SNSB/312/789/283 = [Server]/[Instance]/[Alias for database]/[CollectionSpecimenID]/[IdentificationUnitID]/[SpecimenPartID]
Collection http://id.snsb.info/snsb/Collection_SNSB/Collection/23 = [Server]/[Instance]/[Alias for database]/[Table]/[CollectionID]
Transaction http://id.snsb.info/snsb/Collection_SNSB/Transaction/4 = [Server]/[Instance]/[Alias for database]/[Table]/[TransactionID]

In the examples above [ http://id.snsb.info] is the server, [snsb] is the instance on the server that may correspond to an organization etc. like ZSM or SMNK. [Collection_SNSB] is an alias for the database corresponding to the name of the database without the leading string Diversity. The following numbers point on the keys of the datasets in the main tables. The last two examples point to separate tables within the database and the following number correspond to the key for these tables.

An additional id service is necessary to make direct use of the stable identifiers. This id service redirect a given stable identifier to another web-page which shows data about the identifier. This can be HTML or xml-rdf according to the CETAFrecommendations. The id service needs further information to redirect to those websites. For the redirection to a BioCase-Provider installation or a xml-rdf-service, the information can be retrieved from the main database. The necessary roles and logins for this id service can be generated by pressing the button at the buttom of the window. This buttom will not be visible if the corresponding roles etc. already do exist.

Dec 4, 2024

Diversity Collection

Fequently Asked Questions

Common

  • What are the modules of the DiveristyWorkbench
    • see chapters Module der DiversityWorkbench
    • and the video Video starten
      (Kurze Vorstellung aller Module der DWB, Erläuterung der Einbindung von Modulen, Kurzer Abriss der CacheDB).
  • How to install the software
    • see chapter Installation
    • and the video Video starten
      (Herunterladen und Installation der Software mit Setup, Start über Icon auf Desktop und Programm Menü, Dateien in Program und Benutzerverzeichnis).
  • How to install the application without admin permissions
    • see chapter Installation ohne Installer (= ohne Setup)
    • and the video Video starten
      (Fehlende Adminrechte oder mehrere Versionen, Inhalt der *.bat Datei: Verzeichnis auf Desktop anlegen, Software herunterladen und Start der *.bat Datei, Verzeichnis auf Desktop).
  • How to set the directory for program files
    • see chapter Ordner und Dateien
    • and the video Video starten
      (Dateien in Program und Benutzer Verzeichnis, Kopie von Dateien aus Programm Verzeichnis in von Benutzer festgelegtes Verzeichnis, Festlegen der Position des Verzeichnisses).
  • How to handle the errorlog
    • see chapter Fehlerprotokoll
    • and the video Video starten
      (Position im Verzeichnis, Zugang über Software, Versand mit Feedback, optionale Erhaltung bei Programmstart).
  • How to set the display of print, images and maps
    • see chapter Top area
    • and the video Video starten
      (Einstellung der Anzeige im oberen Bereich, Markierung vorhandener Bilder und Ansteurung, Anzeige von Karten).
  • How to check links from DiversityDescriptions to dataset in DiversityCollection
  • How to speed up the application
    • see chapter Query options
    • and the video Beschleunigen Video starten
      (Übersetzung abschalten, Exssiate ausblenden, akzeptiere Namen ausblenden, Kein Scan von DD, Linked Server nur bei Bedarf abfragen, Datenquellen in die CacheDB importieren, Webabfragen eingschränken, Zahl der Objete aus der Sammlung einschränken).
  • How to get an overview of the projects in DiversityCollection including statistics
    • see chapter Statistics
    • and the video Statistik - Zeitverlauf Video starten
      (Ausgabe von Stastik einer Institution, Einschränkung auf Neudaten, Darstellung getrennt nach Projekten).

Database

  • How to get accesss to a database
    • see chapter Login
    • and the video Video starten
      (Verbindungseinstellungen, Anmeldungsoptionen, Auswahl der Datenbank, Anzeige der Verbindungsparameter, Anzeige aller verfügbaren Datenbanken).
  • How to get set the timeouts for accessing the database
    • see chapter Timeout
    • and the video Video starten
      (Einstellung des Timeouts für Datenbank und Webabfragen).
  • How to restore updated data
    • see chapter History
    • and the video Video starten (Änderung von Daten, Speicherung in Logtabelle, Wiederherstellung).
  • How to restore deleted data
    • see chapter Restore from log
    • and the video Video starten (Einstiegspunkte für Wiederherstellung, Löschung der Daten incl. Eventseries über Maintenance, Wiederherstellung von Event mit Series sowie einzelne Specimen).
  • How to test if the database server is accessible
    • see chapter Login
    • and the video Video starten
      (Eingabe nicht erreichbarer IP, fehlgeschlagener Versuch der Verbindung, analoger Ping in Eingabeaufforderung, VPN als Beispiel, erfolgreiche Verbindung zum localhost).

Administration

Projects

  • How to set the access to projects
    • see chapter Projekte - Zugriff und Sperren
    • and the video Video starten
      (Arten den Zugriffs auf Daten in Abhängigkeit vom Projekt, Sperren von Projekt, Trigger in der Datenbank).
  • How to synchronize projects with the module DiversityProjects
    • see chapter Projekte - Import
    • and the video Video starten
      (Modularer Aufbau der DWB, Zuordnung von Projekten über Typ, Verknüpfung der Module über Link, Details in DiversityProjects, Import in DiversityCollection mit optionaler Beschränkung auf den Typ Collection, Titel und Link in der Tabelle).
  • How to restrict taxonomic groups for projects

Enumerations

  • How to edit enumerations
    • see chapter enumerations
    • and the video Video starten
      (Aufbau von Enum Tabellen, Zugang im Programm, Beispiel für Standard Aufzählungstabelle, Zugang über Admin-Menue, Beispiel für Tabelle mit Projektbezug, Zugang über Projektliste, Tabelle LocalisationSystem).
  • How to set images for the enumerations
    • see chapter Aufzählungen - Bilder
    • and the video Video starten
      (Vorstellung Beilspieldaten, Tabelle in Datenbank mit Spalte Icon, Vorstellung der Beispielbilder (Größe, Hintergrund), Formular für Materialkategorien, Setzen der Bilder für die Demoeinträge, Änderung der Hierarchie, Ansicht im Hauptformular in Menü und Baum).

Withholding data

  • How to withhold data from publication via the cache database
    • see chapter Dataset Availability
    • and the video Video starten
      (Erläuterung anhand des Manuals, Vorstellung der Beispieldaten, Sperroptionen an Einzeldatensatz, Bearbeitung aller Datensätze aus Suchergebnis, Bearbeitung der Datensätze eines Projekts, Entfernung einer Sperre, Setzen einer Sperre).

Customization

  • How to customize the application
    • see chapter Aktuellen Namen anzeigen
    • and the video Video starten
      (Vorstellung der Beispieldaten in DC und DA. Setzen der Option für Anzeige in DC. Anzeige in DC).

Query

  • How to customize the query
    • see chapter Suchkriterien - allgemeine
    • and the video Video starten
      (Auswahl von Projekt um Rechte zu ermitteln, Umstellung der Ergebnisliste, Speicherung von Sucheinstellung, Sortierung, optimierte Abfragen, Operatoren für Suche).
  • How to use special options in the query
    • see chapter Suchkriterien - spezielle
    • and the video Video starten
      (Datum teilweise vorhanden, Geographie: Abstand, innerhalb und ausserhalb von Fläche, mehrfache Angabe von Kriterien, hierarchische Suche, Vorhandene Daten, XML (EXIF), Identfier, Annotation, Withholding in Specimen und Eventtabellen).
  • How to remember previous options in the query
    • see chapter Abspeichern von Suchkritierien
    • and the video Video starten
      (Sicherung über Remember Queryconditions, Speicherort der Ablage, Suche mit optimized Query, Speicherung von Abfragen (optimiert und nicht optimiert), Predefined Query, Scan mode).
  • How to use options in the query related to other modules
    • see chapter Modul bezogene Suche
    • and the video Video starten
      (Suche von Daten mit Verknüpfung zu DiversityTaxonNames: Liste von Namen, Hierarchie, Synonymy, Suche ohne Verknüfung).
  • How to use lists in the query
    • see chapter Suche in Datenbanken mit Listen
    • and the video Video starten
      (DiversityScientificTerms mit Terminologien, Minerale als Anwendungsfall für DST, Zugriff auf Daten in DST, Liste in combobox, Hierarchie der Listen im Menü mit lokalem Server, linked Servern und Webservices mit Beispiel, Suche nach passendem Eintrag in DST und Eintrag in DC).
  • How to use a prefix in the query
    • see chapter Suchen mit Prefix
    • and the video Video starten
      (Eingabe von Prefix, Suche mit Sortierung nach numerischem Wert).
  • How to use many columns in the query
    • see chapter Suchen mit mehreren Spalten
    • and the video Video starten.
      (Aktivierung über optimierte Suche, Hinzufügen von Spalten, Setzen der Breite, Ersetzen von Spalten, Ausblenden von Buttons durch setzen als Default).
  • How to organize the columns in a multi column search
    • see chapter Query - Many columns
    • and the video Video starten.
      (Sortierung der Suche, Hinzufügen von Spalten und Sortierung, änderung der Position der Spalten, Entfernen und Zurücksetzen der Spalten).

Editing

  • How to create a new dataset
    • see chapter Neuen Datensatz anlegen
    • and the video Video starten.
      (Anlegen ohne und mit Hochzählen der Belegnummer, Kopieren mit Sammelereignis, Hochzählen der Belegnummer, zusätzliche Projekte, Beziehungen, Einschliessen von abhängigen Daten, Import, Spreadsheet, Grids).
  • How to handle relations to other datasets
    • see chapter Beziehungen
    • and the video Video starten.
      (Beziehung zu Objekten innerhalb und ausserhalb der Datenbank, für Specimen, Organismen und Teile, Wechseln zu Datensatz, Baum Ausblenden, Beziehung zu externen Daten).
  • How to handle methods
    • see chapter Methoden
    • and the video Video starten.
      (übersicht, Abhängigkeit von Projekt und Typ, Verwaltung über Methoden und Analyen und Prozessierung, Eingabe, Eintrag der Parameter, Nachtragen von Parametern).
  • How to handle references
    • see chapter Literaturverweise
    • and the video Video starten. (übersicht, Eintrag für Sammelereignis, Beleg etc., Beziehung zu Datenbank oder Webservice).

Modules

  • How to link to data in other modules or webservices
    • see chapter Verbindung zu Modulen
    • and the video Video starten. übersicht, Module connections: direkte zugriffe, Linked Server, Webservices, manuell eingerichtete Verbindungen, Festlegung von Quelle für Taxa und direkter Zugriff, Anzeige der eingereichteten Verbindung, Speicherort in Datenbank.
  • How to fix the source for linking data
    • see chapter Quellen festlegen
    • and the video Video starten. Festlegung der Quellen, Beispiel für lokale Daten, Datenbank, CacheDB, Webservice.
  • How to use the cache database as source for linking data
    • see chapter Cache Datenbank als Zwischenspeicher für Datenquellen
    • and the video Video starten.
      (Position von Linked Server und Cache Datenbank, Einstellung der Ladens der Linked Server beim Start, Ansicht unter Module connections, Auswahl einer Quelle aus der Cache Datenbank, Darstellung in Settings, Taxon Datenbanken und Quellen in Cache Datenbank).
  • Which webservices are available for linking data
    • see chapter Webservices
    • and the video Video starten.
      (übersicht in Module connections, RLL, Index Fungorum, Eintrag der Hierarchie, Mycobank, PalaeoDB, Catalogue of Life, PESI).
  • How to use a table to link data to external sources
    • see chapter Auswahl über Tabelle
    • and the video Video starten.
      (Festlegung der Quellen, Beispiel für Chronostratigrafie, Bestimmung und Beschreibung).
  • How to handle defective links to external sources
    • see chapter Falsche Links
    • and the video Video starten.
      (Beispiel mit falschem Link, Daten im Tableeditor, Links mit ID = -1, Aufruf des Inhalts mit Fehlermeldung und Anzeige des Inhalts bzw. Suche nach neuem Link).

Images

  • How to set the sequence of images
    • see chapter Reihenfolge
    • and the video Video starten.
      (Sortierung nach Datum oder Uri für Beleg oder für Projekt über Maintenance).
  • How to fix the orientiation of images
    • Orientierung Video starten.
      (Optionale Ausrichtung der Bilder anhand von EXIF Informationen).

Event

  • How to create distribution maps
    • Verbreitungskarten Video starten.
      (Verbreitungskarte für Sammelereignis, Abwählen von Typen, Karte mit Organismen, Ansicht in Broser und GIS-Editor, Abwählen von Typen.)
  • How to import and handle UTM coordinates
    • see chapter UTM
    • and the video Video starten.
      (Import mit Wizard, Konvertierung nach WGS84, Rundung etc., Ergänzung des Planquadrats im Spreadsheet)
  • How to copy collection events including the transfer of specimen
    • see chapter Fundort kopieren
    • and the video Video starten.
      (Vorstellung der Beispieldaten, Beispiel für Beleg bei dem dieses Kopieren nicht möglich ist, Kopieren eines Fundorts mit mehreren Belegen, Ausblenden der Teile die nicht den Fundort betreffen, Kopieren des Fundorts und verschieben des Belegs in neuen Fundort)

Event series

  • How to move collection events within event series
    • see chapter Series
    • and the video Video starten.
      (Transfer von Sammelereignis in Sammelserie. Einzeln und für mehrere. Entfernen von Event aus Sammelserie)
  • How to add descriptions to event series
    • see chapter Beschreibung mit Deskriptoren
    • and the video Video starten.
      (Vorstellung der Beispieldaten, Struktur in Verwaltung der Typen, 2 Arten von Deskriptor abhängig von Verknüpfung mit einem Modul. Nach Verknüpfung von Daten mit einem Modul kann diese Verknüpfung nicht mehr geändert werden. Setzen von Bilder für die Deskriptoren. Ansicht der Deskriptoren im Hauptformular mit Daten und den Optionen für den Dateneintrag)

Organisms

  • What do taxonomic groups decide and what are the sources
    • see chapter Taxonomic Groups
    • and the videos
      • .
      • Video starten.
        (übersicht, Quelle aus DTN oder DST, Festlegung von Analysen, Quellen für Namen).
  • How to get the list of taxa for an event, plot etc.
    • see chapter Anzeige von Taxon Listen
    • and the video Video starten.
      (Übersicht, Einschränkung auf taxonomische Gruppe, Einschränkung auf Datenbank und Anzeige von Analyse und Herkunft aus DTN. Einschränkung auf Zeitraum. Export und Anzeige der exportierten Daten).
    • Bestimmungen Video starten.
      (Quellen DTN und DST, Texteingabe, Datenbank und Webservice als Quelle, Anzeige der akzeptierten Namen).
    • Kreisschluss entfernen Video starten.
      (Beispieldatensatz bei dem Organismen nicht angezeigt werden, Tabelleninhalt mit IDs und Kreisschluss, Abfrage nach Startpunkt der Hierarchie, Korrektur und korrekte Darstellung des Datensatzes).

Parts

  • Einfügen von Teilen Video starten.
    (Hinzufügen für einzelnen Beleg, Verschieben in Sammlung).
  • Reihenfolgen Video starten.
    (Festlegung für Units und Teile, Speicherort in Tabellen, Ausgeblendete mit grauem Icon, Reihenfolge abhängig von Auswahl im Programm, Sortierung nach Namen, Identifier oder ID, Berücksichtigung von Beziehungen).
  • Bescheibung Video starten.
    (Information aus DST, Information an Teil oder Organismus im Teil).
  • Anzeige Teilsammlung Video starten.
    (Inhalt von Sammlung, Anzeige in Hauptformular, Einstellung der dargestellten Felder).
  • Anzeige von Inhalt von Sammlungen einschränken Video starten.
    (Anzeige des Inhalts von Untersammlung, Anzeige und Meldung bei Abbruch, Änderung der Einstellung in Customize Display, Meldung nach Änderung).
  • Processing
    • Dauer Video starten.
      Dauer der Prozessierung, Speicherung als ISO 8601 oder Datum, Auswahl mit Kalender und übersetzung in ISO-Format.

TableEditor

  • Allgemeines und Formatierung Video starten.
    (übersicht, Darstellung von Lookup Tabellen, Zeilennummern, Löschen, Einstellung der Spaltenbreite, Logtabelle).
  • Daten verschieben Video starten.
    (Copy, Paste, Delete mit Kontextmenü).
  • Filtern Video starten.
    (Einstellung des Werts nach Auswahl, Gross/klein-Schreibung, Typ der Filterung, Numerische Werte).
  • Editieren Video starten.
    (Auswahl des Bereichs, Typ der änderung, Insert, Append, Replace, Löschen, Bearbeitung von Feldern mit hinterlegten Werten).
  • Steuerzeichen Video starten.
    (Ersetzen von Platzhalter für Tabulator und Return durch die entsprechenden Steuerzeichen anhand von Beispielen mit Contextmenü).
  • Export Video starten.
    (Export als tabseparierter Text, Export als SQLite Datenbank).

Spreadsheet

  • Editoren im Vergleich Video starten.
    (Ansteuerung im Client, Unterschiede bei Darstellung, Quelle, Filterung, Reihenfolge der Spalten, Startformular, Versionen, Read only Zugriff, Karten).
  • Übersicht Video starten.
    (Farbkodierung, Datenblöcke, Beispieldaten, Spreadsheet für Sammelereignisse, Spreadsheet für Organismen, Spreadsheet für Teile, Zuordnung der Bilder, Spreadsheet für Bilder).
  • Tabellen und Spalten Video starten.
    (Ausblenden von Tabellen, Ausblenden von Spalten, Einblenden von Spalten, Umbenennung von Spalten, Hinzufügen von Tabellen, Typen von Tabellen, Einblenden von Lookup-Tabelle und normalen Tabellen).
  • Ø Tabellenfilter Video starten.
    (Typen der Filter, Beispiele für die 4 Typen, Löschung von Spaltenfilter bei Anwendung von Tabellenfiltern, Einstellung in Tabellenansicht).
  • Spaltenfilter Video starten.
    (Typen der Filter, Beispiel für Vergleich, Werteliste, Hierarchy und Synonyme, Ansicht in Tabellendarstellung).
  • ↑↓Sortieren Video starten.
    (Sortierung anhand der ID, Anzeige der Reihenfolge, Auflösung der Blöcke, Darstellung in der Tabelleansicht).
  • Schemata Video starten.
    (Festlegung des Speicherpfads, Abspeicherung verschiedener Varianten, Defaulteinstellungen, benannte Schemata, Aufruf benannter Schemata, XML-Ansicht).
  • Spaltenbreite Video starten.
    (Gleiche Breite beim Start, Festlegung einzeln oder für alle nach Kopfzeilen, Inhalt oder beidem).
  • Bilder Video starten.
    (Position von Bildern, Kodierung der Bildanzeige für Anzeige in Spaltenüberschrift, Einfügen von Bildern).
  • Editieren Video starten.
    (Bearbeitbarkeit von Feldern, PK gesperrt, berechnete Felder, Eingabefeld für neue Bestimmung, Lookup Felder, Datenblöcke - ändern nach Auflösung von Datenblock).
  • Editieren mehrerer Daten Video starten.
    (Möglichkeiten, Demonstation von Overwrite, Replace, Append, Prepend, Clear, Lookupfelder, NotNull, Schlüsselfelder, berechnete Spalten und deren Aktualisierung).
  • Verbindung zu Modulen Video starten.
    (Einstellungen in Settings, Spalten mit Verknüpfung, Einrichtung über Pin, Eintrag für mehrere Felder, Einblendung notwendiger Felder, Datenabhängige Quelle bei Bestimmung, Spalte für Filterung, Darstellung über Kontextmenü und in Settings).
  • +x Hinzufügen und Löschen Video starten.
    (Eintrag in leere Felder, Eintrag mit Fusszeile, Löschen einschliesslich abhängiert Tabellen, Voreinstellungen für neue Datensätze in der Tabellenansicht).
  • Kontext Menü Video starten.
    (Kopieren mit Zwischenspeicher, Ausschneiden, Löschen, Setzen des Templates für neue Daten).
  • Projekte und ReadOnly Video starten.
    (Read only Projekte, Umschalten auf Read only Darstellung).
  • Start Video starten.
    (Festlegung des Ablageorts, Festlegung als Startfenster, Inhalt der Startdatei, Start mit Spreadsheet, Abwahl der Startoption).
  • Details Video starten.
    (Eine Zeile mit reduzierten Daten, Zugriff auf gesamten Datenbestand hinter Zeile im Read only Modus).
  • Export Video starten.
    (Spalten in Tabellenansicht, SQL-Abfrage in Datenbank, Export als Textfile mit und ohne ausgeblendeten Spalten als UTF8).
  • Maps
    • Karten Video starten.
      (FÜr TK25, 3 Typen, Einstellungen für Darstellung, Quellen für Karten, Beispiele für Organismen, WGS84 und TK25).
    • Farben Video starten.
      (Beispiel für Jahr, Auswahl der Spalte, Festsetzung der Bereiche und der Farben, Setzen der Symbolgröße, Festlegung der Gruppierung, des Gazetteers und der Hintergrundkarte).
    • Symbole Video starten.
      (Beispiel für TK25, Festlegung der Quelle (Status), Einstellungen für Karte: Spalte, vollständige Wertetabelle aus Lookuptabelle, Setzen der Symbole und der Größe, Festlegung der Gruppierung, Gazetteer und Hintergrundkarte. Symbol für fehlende Angaben, Liste des Inhalts. Optionen: Wiederholung von Daten, Erhaltung des letzten gültigen Werts. Angabe der Reihenfolge der Werte).
    • Legende Video starten.
      (Anzeige der Legende für die Karte über Menü).
    •     Transparenz Video starten.
      (Darstellung von Heatmap, Filtern nach Quelle, Festlegung der Geography, Festlegung von Quelle, Symbol und Größe, Festlegung von Karte und Transparenz. Darstellung der Quelle. Darstellung mit Farbe).
    • Symbolgrösse aus Daten Video starten.
      (Festlegung der Geographie und dargestellter Daten, Einstellungen für Karte: Quelle für Symbol, Quelle für Farbe, Quelle für Geographie und Hinergrundkarte. Darstellung mit Transparenz. Darstellung von fehlenden Werten).
    • Auswählen in Karte Video starten.
      (Filtern in Karte mit Auswahlrechteck).
    • Details in Karte Video starten.
      (für TK25: Anpassung der Spaltenbreite über Spreadsheet. Einblendung von Wiederholungen).

Import

Wizard

  • Überblick Video starten.
    (Importmöglichkeiten, Beispiel für Specimen aus Tutorial, Umwandlung der Origialquelle in Text, Auswahl der Datei, Auswahl des Schemas, Test für erste Zeile, Fehlerbehebung durch Einstellung des Projekts, Import der Daten, Schema mit Fehlerprotokoll, Ansicht der importierten Daten).
  • Datei Video starten.
    (Allgemeine Auswahl von Quellen und Zielen, Auswahl der Datei, Encoding, Importierter Bereich, erste Zeile, Sprache).
  • Sichern der SQL Befehle Video starten. (Aufruf des Wizards, Option zum Sichern der Befehle, Demonstration bei Test, Ansicht der fehlgeschlagenen Befehle, Ansicht aller Befehle in der Datei mit den gesicherten Befehlen)
  • Anhängen Video starten.
    (Schlüssel für angehängte Daten, Festlegung der Position).
  • Zusammenführen Video starten.
    (Beispiel aus Tutorial: Festlegung von Merging für Daten, Festlegung von Schlüsselfeldern, Erläuterung von Insert, Merge, Update, Attach).
  • übersetzung mit Werten aus Tabelle Video starten.
    (übersetzung von Text in ID mit 3 Optionen: Tabelle in Datenbank, Werte aus Datei, manueller Eintrag).

Export

  • Stable identifier Video starten.
    (Einstellung in Label, Export in CacheDB, Administration pro Projekt oder für gesamte Datenbank, innerhalb der Datenbank als Funktion, Eintrag in CacheDB in Tabellen CacheIdentificationUnit, Typen der Stable Identifier: Specimen, Unit, Part, Collection, Transaction).

CacheDatabase

  • Overview .
  • Übersicht Video starten.
    (Allgemeiner Pfad der Daten, Metadaten in DP aus GFBio, ImportWizard für Daten in DC und DTN, Filtermöglichkeiten in Quelle und CacheDB, Projekte in Schemata, Auftrennung für Biocase, Aufbereitung für ABCD, Transfer manuell oder automatisiert durch Server. überprüfung auf Datenänderungen. Dokumentation des Transfers mit allen Parametern, Konfiguration für BioCASe).
  • Datenbank anlegen Video starten.
    (überblick aus Manual, Anlegen der CacheDB, Einspielen der Updates).
  • Postgres Datenbank anlegen Video starten.
    (übersicht, Verbinden mit Server, Anlegen der Datenbank, Einspielen der Updates).
  • Datenquellen anlegen Video starten.
    (übersicht, Position in Datenbank, Hinzufügen einer Quelle für Taxa, Datenbank und Projekt auswählen, Festlegen der Teile, übertragung der Daten, Ansicht der Daten, übertragung nach Postgres, Ansicht der Daten).
  • Projekt anlegen Video starten.
    (überblick, Ansicht in Datenbank, Anlegen des Projekts, Einspielen der Updates, Filter einstellen, Verunschärfung der Koordinaten, Ansicht in Datenbank - Tabellen in eigenem Schema, Anlegen des Projekts in Postgres DB, Einspielen der Updates, Ansicht in Datenbank - neues Schema mit Tabellen, Anlegen von Package und Einspielen der Updates, Ansicht in Datenbank - zusätzliche Tabellen für Package ABCD).
  • Automatisierung des Datentransfers Video starten.
    (übersicht, Einstellung für Taxa - Zeitpunkt, Kontrolle auf änderungen, entsprechend für Projekte. Durchführung durch vom Server gestarteter Scheduler, Test der Automatisierung, Sperrung anderer Transfers).
  • What are the options for filtering data for the transfer into the cache database
    • see chapter Sperren
    • and the video Video starten.
      (übersicht, Projekte, Embargo (Transaction), Datawithholding in Daten und in übersicht, Sperren bei übertrag, Anonymisierung von Sammler).
  • How to filter specimen
    • see chapter Sperren
    • and the video Video starten.
      (Specimen in mehreren Projekten mit teilsweiser Sperrung, Filter in Cachedatenbank für die Specimen. Demonstration der Möglichkeiten der Filter. Projekte mit und/oder kombinieren. Belegnummer filtern. Zusammenfassung).
  • Pakete Video starten.
    (übersicht, Beispiel ABCD und Bayernflora, Anlegen von ABCD und Einspielen der Updates, Neue Objekte in Datenbank, Einspielen des AddOn für BayernFlora, Transfer der Daten).

Labelprint

  • Etikettendruck - Übersicht Video starten.
    (Aktivierung des Druckbereichs, Druck von Teilen, Ausgabe als XML, Auswahl von Schemafile, Beispiel für XSLT, Titel, Einschränkung auf Sammlung und Material, Duplikate, Druck der Liste, Speicherung als html, Festlegung der Reihenfolge).
  • Etikettendruck - Codes Video starten.
    (Barcode - Voraussetzung: Font in XSLT file, Schriftsatz im Verzeichnis Fonts, QR-Code Voraussetzungen: Eintrag im XSLT-File, Zugriff auf Google-API, Versionen des QR-Codes, StableIdentifier - Festlegung der Basis für Projekt oder Datenbank).
  • Etikettendruck - XML nach HTML Video starten.
    (Umsetzung der XML-Ausgabe über XSLT Schema und eingebundenem Template in HTML, Lage der Dateien, Demonstration anhand von Breite und Fettdruck).
    • Beispiel 1 Video starten.
      (Position der Dateien im Verzeichnis, Bereinigung eines Pfadfehlers, Auslagerung in separate Template Datei, Einfügen des fehlenden Teils, Einbinden des neuen Templates).

Wizard

  • Export mit Assistent Video starten.
    (Beispieldaten, Versionen des Exports, Buttons für mehrfache Ausgabe von Tabellen, Information aus verbundenen Modulen (Familie), Auswahl der Felder, Test, Anpassung der Sortierung, Zusammenziehen von Feldern, Export mit Schema).
    • Filter Video starten.
      (Beispieldaten, Demonstration der 2 Filtertypen).
    • Transformation Video starten.
      (übersetzung von Datum, Zerlegung, übersetzung, 2 Formeln, Prefix, Zusammenfassen).

Others

  • Bavarikon Video starten.
    (Vorstellung des Portal, Fenster im Programm, Einstellung der Parameter, Erzeugung der Exportdatei im Bavarikon-XML-Format, Daten in Tabellenansicht, Ansicht der XML-Datei im Browser).

Archive

  • Archiv erstellen Video starten.
    (Automatisierte Erstellung durch Server, Manuelle Erstellung, Suche nach Daten, Erstellung, Inhalt einer xml-Datei, Protokoll).

Collection

  • Sammlungsverwaltung Video starten.
    (übersicht, Ansicht der Sammlungen und Untersammlungen im Client, Verwaltung, Hierarchie, Bilder, Label mit QR-Code, Verwalter der Sammlung).
  • Sammlungen verschieben Video starten.
    (gleichzeitiges Verschieben von Sammlungen innerhalb der Hierarchie mit Verhinderung von Kurzschluss).
  • Darstellung der Hierarchie Video starten.
    (Ausblenden der Hierarchie, nur übergeordnete Datensätze darstellen, abhängige Datensätze einschliessen oder gesamte Hierarchie darstellen).
  • Optionale Hierarchie für Orte Video starten.
    (Freischalten der Option, Darstellung im Hauptformular und Umschalten der Hierarchien, Darstellung im Formular der Sammlung, Umschalten auf Ortshierarchie, Button zur Anzeige des Inhalts).
  • Plan Video starten.
    (Setzen des Grundrisses, Setzen des Massstabs, Setzen der Geometrie für die Objekte mit Editieren, Erläuterung der administativen und räumlichen Hierarchie, Ansicht der übergeordneten räumlichen Objekte).
  • Kastendigitalisierung - Übersicht Video starten.
    (Hierarchie für Verwaltung und Räumlichkeiten, Import der Kästen mit Wizard, Darstellung nach Import, Import des Inhalts mit Wizard, 2 Hierarchien, Bereiche innerhalb eines Kastens).
  • Kastendigitalisierung - Bereich Video starten.
    (Vorstellung der Beispieldaten, Einblenden des Sammlungsinhalts, Anlegung eines Breichs in Kasten, Verschieben des Inhalts, Markierung des Bereichs, Anlegung von Unterbereichen, Verschieben des Inhalts, Markierung der Unterbereiche, Ansicht im Hauptformular).

Transaction

Dokumentendruck

  • Beispiel 1 Video starten.
    (übersicht, Ansicht der Sammlungen und Untersammlungen im Client, Verwaltung, Hierarchie, Bilder, Label mit QR-Code, Verwalter der Sammlung).
  • Historische Entwicklung Video starten.
    (übersicht der ausgewerteten Felder, Arten der Ausgabe, Typen und Sammlungen, Einstellung des Startjahrs, Ausgabe separiert nach Sammlungen und Typen, Einschliesen der als Zahl eingebenen Werte am Beispiel von Geschenken).

Task

  • Ausstellung Video starten. Temporärer transfer eines Objekts aus dem Magazin in eine Ausstellung.

Maintenance

  • Abgleich von Koordinaten mit den davon gecachten Werten Video starten.
    (Ablage der Koordinaten in 3 Feldgruppen, 2 Typen des Abgleichs: Cache und Geographie).
  • Koordinaten ausserhalb eines Gebiets Video starten.
    (Quelle - Gazetteer: Umriss für Bereich, Auswahl der Vergleichsfläche, Suche nach Abweichungen, Anzeige im Hauptformular ).
  • Entfernung verwaister Daten Video starten.
    (übersicht nicht automatisch gelöschter Objekte, Löschen von Beispieldaten, Auswahl von Projekt um Rechte zu ermitteln, Suche nach Series ohne Ergebnis, Suche nach Event mit abhängigen Daten, Entfernung, Suche nach Series, Entfernung, Suche nach Annotations und Identifier).
  • Entfernung verwaister Beziehungen Video starten.
    (Übersicht zu Typen von Beziehungen, BaseURL der Datenbank, Beispieldatensätze in Datenbank, Beispieldatensätze im Programm, Datensatz mit nur lesendem Zugriff, Beispiele für externe Beziehungen, Beispiel für gültige Beziehung, Beispiel für ungültige Beziehung, Suche in Maintenance und Löschung der verwaisten Beziehungen, Kontrolle der Datensätze).
  • Sammelereignisse vereinen Video starten.
    (Beispieldaten, Suche nur mit Ort, Suche ohne Bilder, Suche mit Datum, Verschieben von Informationen in Hauptereignis, Vereinen der Sammelereignisse).
  • C0 Steuerzeichen entfernen Video starten.
    (Wiki - C0 codes, Entfernung an Beispiel von einzelner Spalte, Ignorieren von Zeichen, Suche in allen Textfeldern der Datenbank).
  • Sammler zuordnen Video starten.
    (Vorstellung der Beispieldaten, Zuordnung mittels Suche nach identischem Eintrag, Zuordnung mit Suche nach ähnlichen Einträgen, Auswahl des korrekten Eintrags aus DA, Demonstration einer Kollision innerhalb eines Belegs, Zuordnung weiterer Sammler und Ansicht in der Datenbank).
  • Sammler teilen Video starten.
    Vorstellung der Beispieldaten, Trennung am Komma, Ergebnis der Trennung, Trennung am & Zeichen, Ergänzung der Einträge, Ergebnis mit Kollision, Ansicht des Datensatzes mit Kollision, Ergebnisliste der bisherigen Teilung, Wechsel auf einzelene Datensätze, Trennung der einzelnen Datensätze mit verbleibender Kollision, Ergebnisliste mit verbleibendem Datensatz mit Kollision.
  • Literatur transfer Video starten.
    Vorstellung der Problematik, Tabellen in Datenbank mit obsoleten Feldern. In Maintenance Suche nach fehlenden Einträgen. Unterschied zwischen Abgleich über Existenz und Titel. Übertrag der Daten in Tabelle. Ansicht übertragener Daten
  • Abgleich mit DiversityScientificTerms Video starten.
    (Vorstellung der Problematik, Vorstellung der Beispieldaten, Verknüpfung von Bestimmungen, Ausgabe der Belegnummern, Auswahl der Datensätze für Update, Kontrolle mittels Detailansicht, Abgleich mit Pflanzengesellschaften, Einschliessen der Hierarchie, Abgleich von vorhandenen Chronostratigraphien, Suche nach Abweichungen, Ansicht in DST, Einschliessen der Hierarchie, Invertieren der Hierarchie)

Tools

  • Index und Schlüsselwort Dateien fuer Webseite erstellen  Video starten.
    (Manual mit Index und Schlüsselwörtern, HTML Help Workshop und zugehörige Dateien, Erstellen der Dateien mit DWB, hhc und hhk Dateien im Verzeichnis, Auswahl der Dateien und Erstellen der html Dateien, Einbinden in HTML Help Workshop, Entpacken für Verwendung als Webseite).
  • Beschreibung von Datenbankobjekten  Video starten.
    (Beschreibung von Objekten mit Database tools. Vorstellung des Formulars an einem Beispiel. Buttons für SQL-Statements und Beispielskript, Cachetabelle - Befüllung über Prozedur. Vorstellung des Formulars Documentation für Erzeugung von Beschreibungen im Manual. Vorstellung des Formulars für benutzerdefinierte Beschreibungen. Inhalt der Cachetabelle).
  • Dokumentation von Enum-Tabellen  Video starten.
    (Aufruf Formular, Voreinstellungen über Button, Abruf der Tabellen und Auswahl der Enum Tabellen, Struktur der Tabellen in Datenbank, Code der Seite mit css und favicon Verweisen, Inhalt der erzeugten Datei, favicon als SVG und als Ersatz PNG Datei).

Diversity Collection

Statistics

To see the activity and the state of revision within a project choose Help - Statistics … from the menu. A form as shown below will open containing a summary of the project, for the current user and for lists.

 

The statistics for a single project can be exported with a click on the button.

The history provides a simple overview for the activity within projects (see below).

 

Aug 1, 2024

Diversity Collection

Customization

Customization of the application

DiversityCollection provides several ways to adapt the forms to your needs. There are special adaptations for the mainwindow and for the grid view. General adaptations are performed with the context.

Aug 1, 2024

Subsections of Customization

Diversity Collection

Entities, contexts, usage and languages

DiversityCollection may be used in diverse contexts like collection management, observations or field mapping. To ensure that a user working in a certain area will see the descriptions corresponding to his domain the DiversityWorkbench provides the possibility to define corresponding contexts.

To set the context and the language for the program choose Administration - Customize display … from the menu. A window will open as shown below where you may select the language and the context which should be used. By default the language will be set according to the settings of your operating system, however, you may change it here. The default language within DiversityCollection is English. If you select a certain context, the tables in the lower part of the form will show you the special setting within this context. These settings are edited as described below.  

For the documentation of the tables used for the storage of the entity related data please see the section Entity tables.

To edit the entities choose Administration - Application description … from the menu. A window will open as shown below where you may edit the entities defined for the program.

 

Group for the display of the entity

If in a user interface certain entities should be displayed in a group, enter the name of the group here. 

Usage

If nothing is defined for the usage of an entity, it will be handled according to the rights of the user. In certain context an entity may be set to e.g. read only, inapplicable or not used. In case of the later two possibilities the entity will not appear in the interface of the program. For example, transaction management (e.g. loan) will not be handled with a mobile device, thus the corresponding entities will be set to “not used”. Use the Insert new usage button to insert a new usage for an entity. To edit the possible usages choose Administration - Usage … from the menu.

  • inapplicable: An entity which may not be applied in a certain context will not be shown in a user interface, e.g. the depositors accession number in the context observation. 
  • preset: An entity will have a preset value, e.g. ‘determination’ for the identification category in the context observation.
  • read only: An entity may not be changed.
  • hidden: An entity should be hidden from the user interface.   

Context

The default context is General. Thus, in the beginning you will find all representations within this context. Within the representation, when a certain context is missing, the program will search for a representation in the parent context until a representation is found. To edit the context choose Administration - Context … from the menu. A window will open as shown below where you may edit the context.

 

Representation

An entity may have differing representations in different contexts. For example a CollectionEvent may correspond to an observation or gathering in other contexts. Use the Entity and Representation menu to fill in missing entries. If an only if entity should receive a different title or description in the user interface, enter the values in the table. If nothing is defined in a certain context, the program will walk up the tree defined with the parent code (see the image above) to find available values for the title or description of the entity. The highest entry in the hierarchy is the context General with the language English. If you define deviating values for the display text, the abbreviation or the description, you must at least enter values in the highest entry (General, English) as a default value for all other entities. 

Language

TThe default language used in DiversityCollection is English. Thus, in the beginning you will find all descriptions etc. in English. All representations may be defined for any language. Use the Representation menu to automatically fill in missing entries of a language. If there are changes in the original description of tables or columns in the database, choose

Representation - Update descriptions according to database/strong> from the menu to import the updated descriptions for the English version and context “General”.

Entity

To insert missing entities use the Entity menu. To insert all missing tables of a database choose Entity - Insert all missing tables … from the menu. A window will open listing the missing tables. Use the [Exclude: … ] field and [Requery] button to remove certain tables from the list, e.g. if you do not wish to define entities for log tables, enter *_log and then click [Requery]. You may repeat this until the list contains only tables you wish to use.

 

You find corresponding functions for single tables and for entries in a table. The later function is restricted to tables with a primary key with one column. A window will open where you map the columns, provided for the entity documentation to columns in the table, of which you wish to import the entries (see image below).

 

This may be necessary, if e.g. certain entries in a table should not be used in a certain context or if you wish to translate the contents into another language. 

Jan 30, 2025

Diversity Collection

Enumerations

There are several enumerations resp. lookup tables, that by default contain predefined entries. All these tables and the content of some of these are listed here. An example for the design of these tables is shown below. For an introduction see the video .

As a database owner you may edit the content of these tables keeping in mind, that changes may have unprecedented effects in the program. So you should the test the effects after changing the data before keeping changes. To access these tables choose Administraion - Enumerations from the menu. Depending of the table you select a window as show below will open.

Extended options

For enumerations with different design the window will change.

Project dependency

For enumerations with a optional dependency on the projects the data are linked to an example is shown below. For an introduction on this topic see the video:

Images

Some enumeration tables provide the option for setting images that are linked to the selected entries shown in the client. For an introduction on this topic see the video:

Special tables

For the tables LocalisationSystem and Property (properties of the collection sites) the content of certain columns can be edited as shown below.

Mar 25, 2025

Diversity Collection

Customize the main form

The main window can be customised in several parts. To change the visible parts in the main window select Administration - Customize display … from the menu. A window (see below) will open where you can select the groups which should be displayed. In the first tab you can change the visibility for the taxonomic groups and material categories.

In the second tab (see below) you can set

  • visibility of the localisation systems displayed in a distribution map
  • the localisation systems available for the selection in the drop down menus
  • the collection site properties available for the selection in the drop down menus
  • the source for the country list from a gazetteer
  • the direction of the hierarchy derived from a gazetteer and written into the cached value representing the gazetteer entry
  • the separator in the hierarchy derived from a gazetteer and written into the cached value representing the gazetteer entry

Defaults and miscellaneous

In the third tab (see below) you can add the name of the responsible person or choose the current user for several entries and show/hide the controls for the exsiccata.

 

Timeout

The timeout for web resources and databases either added manually or via linked server can be set to adapt to the velocity of the available net. If you set the Timeout for web response to 0, the application will ignore any resources retrieved from the web. By default these values are set to 30 seconds This is demonstrated in a short tutorial Video starten.  

Responsible

You can choose to either use the current user or a specified user as a responsible for new datasets for various tables (see image above).

Storage location

The source for the list for the storage location can be set as shown below:

  • Taxonomic names from identifications within the selected specimen
  • Storage locations already entered for the parts within the collection where the part is stored
  • Storage locations already entered for the parts within the whole database

Template copy mode

 

There are 3 possibilities:

  • Copy values from the template only if there are no entries in the data
  • Ask the user if there are differing contents in data and template whether the template values should be copied into the data
  • Copy the values from the template irrespective of any content in the data

Subcollection content

The display text for the content of the subcollection can be composed of the fields listed below:

  • Accession number of the specimen
  • Accession number of the part
  • First identification of the first organism
  • Storage location of the first part
  • Locality of the collection event
  • Collection date

The maximal content of a subcollection can be restricted hire for new parts can set here as well.

The default collection for new parts can set here as well.

Miscellaneous

Use translations: If the data fields for the exsiccatal series should be displayed.

Show exsiccata: If the data fields for the exsiccatal series should be displayed.

Show accepted names: With this option the names linked to DiversityTaxonNames will be checked for the synonymy status. Accepted names will be shown with a green color and for synonyms the accepted name will be displayed above the current name (see below).

   

Show valid names: With this option the valid names linked to DiversityAgents will be shown. Valid names will be shown with a green color and will be displayed above the current name. Video starten

Scan DiversityDescriptions: If accessible DiversityDescriptions databases should be scanned for links to the current dataset.

Load datasources: If the datasources on linked servers should be loaded together with the start of the programm.

Autocompletion

Use autocompletion for all textboxes: Available in upcoming version - If this option is choosen, textboxes will autocomplete starting with the specified text length.

You can choose the mode of the autocompletion. There are 4 options:

  • Node: No autocompletion
  • Append: Append the first fitting entry
  • Suggest: Provide a list corresponding to the typed text
  • Suggest & Append: Provide a list corresponding to the typed text and append the first fitting

Use query charts

Inclusion of charts for queries linked to modules: If you choose this option, you get access to data of linked modules via charts as described in chapter charts. Keep in mind that this option may slow down the application.

Query

To set the option for optimized queries and the option to remember the query settings as default, select the Optimized resp. Remember option. This will speed up the query in many cases as it will preselect data depending on the query restrictions, e.g. if you search for an identification and enter a taxonomic name the first identification matching the restrictions will be preselected in the main window. Aditionally the corresponding buttons in the query form will be hidden providing more space. 

Resources directory

The directory for the resource can be set with as shown in the area below. Here parameters for example the spreadsheets are stored. See chapter Resources for details.

Time for tooltip

You can set the time for which the tooltip should be shown. In the customize window the setting will be changed instantly while in the main windows the setting will only be effectiv after restart of the application. 

You have 3 options:

  • Set the time the tooltip should be visible to 1 up to 5 seconds
  • Set the time the tooltip should be visible to no limit
  • Hide the tooltip

Transaction

Transaction display sequence

To customize the sequence and format of the transactions shown in the tree, choose Administration → Customize display … from the menu and then select the part Transaction (see below). If you want to change the default sequence and/or display type, click on the button. Use the and buttons to change the position of a certain type of transaction and choose one of the display types. To reset these settings to the database default, use the button. If your transactions are organized within a hierarchy, you can include the titles of the superior hierarchies with the Include superior transaction in title option. 

Transaction standard comments

As an administrator you can add entries to the Standard comments for transactions (see above) that are used to enter standard phrases into the comment field of a transaction.

Default currency

The default currency for all transaction payments in the database is Euro. To change the default currency click on the Currency button. 

Settings

The tab Settings shows an overview of all settings set by the user e.g. when linking the sources for identification to a certain database or webservice via the button (see below). Relations to Diversityworkbench modules include the database and the project as shown below. With the Reset button, you can clear the whole settings. These settings can not be defined here, but are set in the main form in the corresponding parts e.g. the identification. These settings are stored in the database for every user (UserProxy → Settings). 

 

Jan 14, 2025

Diversity Collection

Maintenance

To open the maintenance form choose Administration - Maintenance ... from the menu. With the maintenance functions you can update values cached from other modules or external webservices. DiversityCollection can be linked with several other modules of the DiversityWorkbench. If you link a data source to another module, the URI of the data set in the other module together with one or several cached values will be stored in DiversityCollection. Due to changes in the source modules these cached values may differ from the original values. To get the actual values you can use the synchronize functions for taxonomic names, family and orders, people, exsiccatal series, geographical names and references. Further functions provided by maintenance are a search for duplicate accession numbers, the insert of updated taxonomic names, the removal of orphaned CollectionEventSeries and CollectionEvents etc., the search for additional geographical information based on WGS84 coordinates and the conversion of coordinate systems.

With the button   you can set the timeout for critical queries used within maintenance and feedbacks can be sent with the button .

Jan 14, 2025

Subsections of Maintenance

Synchronizing

With the maintenance functions you can update values cached from other modules or external webservices. DiversityCollection can be linked with several other modules of the DiversityWorkbench. If you link a data source to another module, the URI of the data set in the other module together with one or several cached values will be stored in DiversityCollection. Due to changes in the source modules these cached values may differ from the original values. To get the actual values you can use the synchronize functions for taxonomic names, family and orders, people, exsiccatal series, geographical names and references.

Jan 14, 2025

Subsections of Synchronizing

Maintenance - Identification

Taxonomic names

Taxonomic names may be linked to an external source. To synchronize the entries for the taxonomic names derived from the module DiversityTaxonNames choose Administration → Maintenance… from the menu. A window will open as shown below. Choose the tab TaxonNames. There are two ways to synchronize taxonomic names. You may either Synchronize taxonomic names based on the link via an URI for entries where the link to a taxonomic database is already established or you may Synchronize taxonomic names missing a connection where no link is established and you can query for identical names in one of the databases.

The taxonomic names are stored in the field TaxonomicName in the table Identification. Select a taxonomic database and a project and taxonomic group which should be synchronized. Start the query with a click on the Check for differences button.

 

If the taxonomic information has been imported into the cache database, you may use the data from there to speed up the synchronization.

The form will list all differences found. With the Select same genus and species button you can restrict the selected entries to those where the genus and species are identical in the source and the entry in collection. The other buttons will either select all or no entry .

To update the database click on the Start update button. If you wish to have a more detailed look on your data, you need to check the Include accession number checkbox before starting the query. A button Close form and check dataset in database will appear which will take you back to a single data set in the database.

 

Synchronize taxonomic names missing a connection

Select a taxonomic database and a project within this database, a project in the collection database and a taxonomic group to search for identical names. Start the query with a click on the Check for identical names button. You have several options to search for fitting names:

Compare whole name

Search for an exact match. With the option Excl. auth. you can extend the search for names where the authors are missing in the identifications.

Compare first parts

Search for names fitting in first parts of the name as shown below. If the names do not match exactly, you may either update the name ( Update similar name) in the collection database or import the name from the DiversityTaxonNames as a new identification ( Insert as new name** - see options in the window depicted below).

If you choose the option Restrict to last identification, the former identifications of an organism will be ignored.

If you choose the option Include fuzzy search, the program will try to find names with up to 3 differences. The search with this option is rather time consuming and should only be used for a small number of datasets.

In the result list only matching names will be checked (column OK). The other results will be marked indicating the difference.

If several similar names were found, these lines will be marked with a blue background. To select one of the similar names click on the Select valid name button. A window will open as shown below listing all similar names found in Index Fungorum. Select one name and click OK to use it.

If for any reason links to webservices or modules are broken , e.g. when a webservice changes its address, you can search for these (see below). Please make sure, that you are connected with all source databases used for the taxa. Otherwise connections to these sources would be assumed as broken. Choose the Project, for which you want to search for broken links and optional restrict the search on a Source and a Taxonomic group. Click on the button to start the search.

The broken links will be listed as shown below. With the Check dataset in database you can inspect a single dataset. With the Select all and Select none buttons you can select resp. deselect all datasets and show the selected datasets with the Close form and check whole list in the database button in the main window.

 

Update the display text for organisms according to last identification

If for any reason the displayed text for an organism does not correspond to the last identification, this can be fixed under the Synchronize last identification tab. Just click on the Search for organisms where the displayed text does not correspond to the last identification   button to list the deviating display text and then on the Update the displayed text for organisms according to the last identification button to synchronize the displayed text with the last identification.

Mar 20, 2025

Subsections of Identification

Maintenance

Family and order

To synchronize the entries for the family, order and hierarchy of taxa derived from the module DiversityTaxonNames choose Administration → Maintenance from the menu. A window will open as shown below. To synchronize the higher taxonomic entries for entries linked to the module DiversityTaxonNames choose the tab Hierarchy. These entries are stored in the fields FamilyCache,OrderCache and HierarchyCache in the table IdentificationUnit.

Select a taxonomic database, a project and a taxonomic group and then choose whether you wish to synchronize the family, order or hierarchy. If you wish to inspect single data sets you need to check the Include accession number checkbox. Then click on the Check for differences   button to start the query.

The form will list all differences found as shown above. To update the database click on the Start update button.

Mar 20, 2025

Maintenance

Renaming identifications

If you wish to add updated taxonomic names for specimen in the database, you can use the bulk insert function. Choose the project, the taxonomic group and the taxonomic name for which the new identification should be added. As shown in the window below you may enter additional information about this identification. By default the Only last identification option is checked to prevent you from searching in older identifications. If you uncheck this option, the program will search for any identification, irrespective whether it is the last or an older identification.

If you wish to check single data sets check the Include accession numbers option. A new button will appear

which will enable you to close the window and turn to a specimen selected in the table. 

To search for names click on the Test button. The found names will be listed in the table as shown below. To insert the new identification click the Start insert button.

Aug 1, 2024

Maintenance

Accepted Names

If you wish to add accepted taxonomic names for specimen in the database were the synonyms are used, you can use the insert function for accepted names. Choose the project, the taxonomic group for which the new identification should be added as well as the source for the taxonomic names and the projects within the taxonomic source from which the new identifications should be taken. As shown in the window below you may enter additional information in the notes field.

Click on the Search for accepted names button to find the accepted names that may be inserted. If you wish to check single data set, select this dataset in the grid and click on the Close form and check dataset in database button.  

If some of the names should not be added, deselect them as shown for the 3. name in the example below. To select or deselect all names you can use the All resp. None buttons. To insert the selected names, click on the Start insert button.

Aug 1, 2024

Maintenance

Identification Terms

Vernacular terms may be linked to an external source. To synchronize the entries for the terms derived from the module DiversityScientificTerms choose Administration → Maintenance… from the menu. A window will open as shown below. In the Synchronize databases tab choose the tab Identification terms. There are two ways to synchronize scientific terms. You may either Synchronize terms based on the link via an URI for entries where the link to a scientific terms database is already established or you may Synchronize terms missing a connection where no link is established and you can query for identical terms in one of the databases.

The terms are stored in the field VernacularTerm in the table Identification. Select a database containing scientific terms, a project and the group which should be synchronized. Finally you have to decide which part should be synchronized, either the term or the hierarchy where the hierarchy is available in two variants (upwards or downwards). Start the query with a click on the Check for differences button.

 

The form will list all differences found. The other buttons will either select all or no entry .

To update the database click on the Start update button. If you wish to have a more detailed look on your data, you need to check the Include accession number checkbox before starting the query. A button Close form and check dataset in database will appear which will take you back to a single data set in the database.

 

Synchronize terms missing a connection

Select a database containing scientific terms from the list and a terminology within this database, a project in the collection database and a group to search for identical terms. For the hierarchy you can choose between the hierarchy from the term upwards to superior terms resp. the hierarchy from the top term to the selected term. Start the query with a click on the Check for identical terms button.

In the result list only terms with a single match will be checked (column OK).

If several similar terms were found, these lines will be marked with a blue background. To select one of the similar terms click on the Select valid term button. A window will open as shown below listing all similar terms found. Select one term and click OK to use it.

 

Mar 20, 2025

Maintenance

Scientific Terms

To synchronize the entries with the module ScientificTerms choose Administration → Database → Maintenance from the menu. A window will open as shown below. On the tab page Synchonizing, you can synchronize the content in DiversityCollection with the linked resources or search for new links via text.

To synchonize the content for linked data select the database, the project, the table and the target for which the entries should be synchronized. There are 2 targets for the synchronization: The term itself and the hierarchy. There are 3 tables which may contain links to DiversityScientificTerms:  Vernacular terms, Site properties and Part descriptions).

To synchronize linked data start the query click on the Search for differences button. Terms with differing content will be listed as shown below.

To include the hierarchy in the comparision, check the Compare hierarchy option as well if the hierarchy derived from DiversityScientificTerms should be from the option Top→ Detail or Detail → Top . As shown below 2 more columns will be included, containing the hierarchies in DiversityCollection and DiversityScientificTerms

To establish new connections for terms corresponding to terms in DiversityScientificTerms (see below) click on the Search for identical terms button. All matching terms will be listed.

As with the query for linked data, you may include the hierarchy. In addition there are two options to restrict the search: Restrict to terms like … and Restrict to max. results … . The option Include accession number will split the data according to the specimen as shown below. With this option set, you can inspect the content of single specimen in the list using the button (see below).

In the result list you can select the data that should be included in the update in the first column (OK ) by de/selection of single lines or with the buttons Select all resp. Select none. To update the database click on the Start update button.

 

Aug 1, 2024

Maintenance

Agents

Synchronize via URI

To synchronize the names of collectors, determinators etc. which are linked to the module DiversityAgents choose Administration - Maintenance from the menu. A window will open as shown below. On the tab page Collection <→ Agents select the project for which the agents should be synchronized. There are 9 tables which may contain links to DiversityAgents: Collection, CollectionAgent, CollectionEventLocalisation, CollectionEventProperty, CollectionSpecimen, CollectionSpecimenProcessing, Identification, IdentificationUnitAnalysis and Transaction. Choose one of these tables for the synchronization. Then start the query with a click on the  button. The type name is written as defined by the default display type in the module DiversityAgents - for more information please see the documentation on DiversityAgents.

The form will list all differences found. To update the database click on the button. If you wish to have a more detailed look on one of the data sets in the list, you need to check the “Include accession number” checkbox before starting the query. A button will appear which will take you back to a single data set in the database.

You can either update the cached names for entries which are linked to DiversityAgents as described above or you can search for possible links based on the names as shown below. In addition to the options described above you may choose the display type for the query to find any possible match as names may be written like “Hertel, H.”, “H. Hertel” etc. Video starten

Next to a search for identical names you can search for similar names. Enter a search string in the  Like field  and click on the  Search for similar names  button. The deteted datasets will be listed as shown below. For those dataset where there are more than 1 possible link in the DiversityAgents database you have to choose the correct link with a click on the  Select valid names  button.

For those dataset where there are more than 1 possible link in the DiversityAgents database you have to choose the correct link with a click on the  Select valid names  button. A window as shown below will open, where you can select the valid name. Click on the button to show details of an agent.

 

The dataset where the update collides with existing data will be listed in the  tab. Use the   Check selected dataset   button to inspect these data (see below).

 

Splitting collectors

If the collectors had been written in one field with separators like & you can split these to create a separate entry for every collector (see below). Choose the project, enter the separator or select one of the predefined separators and click on the Search for names to split button. The result will be shown as in the example below. Click on the Start update button to split the collectors. If several separators had been used you have to do the splitting for every single separator.

The dataset where the split collides with existing data will be listed in the  tab. Use the   Check selected dataset   button to inspect these data.

Mar 20, 2025

Maintenance

Exsiccatae

To synchronize the abbreviations of the exsiccatal series titles which are linked to the module DiversityExsiccatae choose Administration → Maintenance… from the menu. A window will open as shown below. On the tab page Collection <→ Exsiccatae select the project for which the titles should be synchronized. The title is stored in the field ExsiccataAbbreviation in the table CollectionSpecimen. Select the project which should be synchronized and start the query by clicking on the  button.

The form will list all differences found. To update the database click on the button. If you wish to have a more detailed look at your data, you need to check the “Include accession number” checkbox before starting the query. A button will appear which will take you back to a single data set in the database.

 

 

Mar 20, 2025

Maintenance

References

To synchronize the titles of the references which are linked to the module DiversityReferences choose Administration → Maintenance from the menu. A window will open as shown below. On the tab page Collection <→ References select the project for which the reference titles should be synchronized. With the first option you can Search for differences in the reference. There are 3 tables which may contain links to DiversityReferences: CollectionEvent, CollectionSpecimen and Identification. Choose one of these tables for synchronization. Start the query with a click on the Check for differences button.

The form will list all differences found. To update the data click on the Start update button.

As a second option you can Search for references with the same title as found in the module DiversityReferences (see below).

If there is more than 1 reference matching the entry in DiversityCollection, select the line and click on the Select valid button to choose the correct reference.

Next to the references in the tables mentioned above, you can perform the same checks for references stored in the table Annotation related to the tables  CollectionEvent, CollectionSpecimen, CollectionSpecimenPart and IdentificationUnit. To use this option, check Annotations for this table and select the table that should be checked (see below) 

Mar 20, 2025

Orphaned data

The removal of certain data may leave orphaned data as shown in the image below. The removal of a specimen may leave event data without any relation to a specimen. As the access to the data is organized via projects this relation is removed as well. So orphaned data are accessible by anyone. Orphaned data may on the other hand exist due to the preparation of events for upcoming expeditions and the like. Therefore care should be taken when removing orphaned data to not remove preparations of other users. For an overview see a short tutorial Video starten.

Aug 1, 2024

Subsections of Orphaned

Maintenance

Orphaned Event

CollectionEvents & CollectionEventSeries

The removal of orphaned event data is described in the Maintenance capters CollectionEventSeries and CollectionEvent.

 

Jan 14, 2025

Maintenance

Unrelated Data

CollectionEvents

Provided you have the proper rights you may remove unlinked data sets in the tables CollectionEvent and CollectionEventSeries. To delete events which are not linked to any data in the database use the tab page [Remove unrelated events]. These unrelated data sets may e.g. be derived from specimens which were transferred to another CollectionEvent. Click on the [List unrelated events] button to list all events which are not related to a specimen. The found CollectionEvents will be listed in the upper part of the form. The lower part shows the localisations and the event properties related to these CollectionEvents. These must be deleted first before you can delete the events related to these data sets. Otherwise only the events with no relations to localisations or properties will be deleted.

 

 

CollectionEventSeries

To delete CollectionEventSeries with no relation to CollectionEvents or other event series choose the tab page [Remove unrelated event series]. Click the [List unrelated event series] to list these series and the [Delete unrelated event series] button to delete them.

 

Aug 1, 2024

Maintenance

Orphaned Annotations

Provided you have the proper rights you may remove orphaned data sets in the table Annotation. To delete annotations which are not linked to any data in the database use the tab page Orphaned data - Annotations. These orphaned data sets may e.g. be derived from specimens which were deleted. Click on the List orphaned annotations button to list all annotations and their related tables which are orphaned. The found annotations will be listed in the form. Click on the remove orphaned annotations button to remove the data.

 

 

Aug 1, 2024

Maintenance

Orphaned Identifier

As described for the annoations above you can delete orphaned external identifier in the tab Orphaned data - Identifier (see below).

   

Aug 1, 2024

Maintenance

Orphaned Relations

As described for the annoations above you can delete orphaned internal relations in the tab Orphaned data - Relation (see below) Video starten.

 

Aug 1, 2024

Diversity Collection

Maintenance Event & series

CollectionEvents - orphaned events

Provided you have the proper rights you can remove orphaned data sets in the tables CollectionEvent and CollectionEventSeries. To delete events which are not linked to any data in the database use the tab page Orphaned data - Event. These unrelated data sets may e.g. be derived from specimens that were transferred to another CollectionEvent. Click on the Find orphaned data button to list all events which are not related to a specimen. The found CollectionEvents and their dependend data will be listed as shown below. Click on the Start removal button to delete the data.

 

 

Country, Place and Altitude via GeoNames

If your data sets contain WGS84 Coordinates, you can use the webservice www.geonames.org to insert or update the country, the place or the altitude of your collection sites. Choose the tab Set place and country, the project you wish to update and an optional upper limit of the data sets (recommended for slow connections). Click the Query GeoNames button to start the query. According to the selected option (only if missing / when different / for all entries) the retrieved data will be marked with colors as shown in the images below.

White The data set will be inserted or changed
Red An error occured
Grey According to the selected option this data set will not be inserted or changed
Yellow The data set has been deselected and will not be inserted or changed
Green The data set has been inserted or changed

In the first column you can deselect a data set for the update. To inspect a single data set from the list select it and click on the Close window and check data set button. To update the data set click on the Set countries button.

As for countries, the places will be listed as shown below.

To insert or update the selected data sets click the Insert places button.

 

The image above shows the data for the altitude. After the update all updated data sets will be marked green (see below).

 

Sampling plots

If your data contains references to sampling plot coordinates, you can update the locality description according to the name of the sampling plot (see image below). Click on the Start search button to find links to SamplingPlots where the locality description does not correspond to the name of the sampling plot. You can restrict the search to missing locality descriptions and attach the name of the sampling plot to the existing entry in the locality description. Use the Start update button to set the locality description according to your settings and the differences found.

Method parameters

If your events contain methods where parameters for these methods had been added afterwards, you can add these missing parameters. You may restrict the search for missing parameters to certain methods and projects (see image below). Click on the Find differences button to search for missing parameters and on the Start update button to add them to the methods used in the events.

If your data contain or needs coordinates, please see the corresponding chapter on adding and calculatingcoordinates.

 

Collection date

If your events contain missing or invalid collection dates you may search for these in the Collection date section (see below). Use the button to search for these datasets. In the upper part of the window datasets with complete parts for a valid date but missing dates are listed. These can be updated with a click on the button. In the lower part of the window you find data with date parts that would result in an invalid date. Click in one of the lines and then on the button to close the window and inspect and fix the listed data.

 

Jan 14, 2025

Subsections of Event & Series..

Maintenance

Event Series

To delete CollectionEventSeries with no relation to CollectionEvents or other event series choose the tab page Orphaned data -   Series. Click the List orphaned event series button to list these series. The detected data will be listed as shown below. In case there are orphaned images these must be deleted first (see below). Click on the Delete orphaned event images and and the Delete orphaned event series button to delete the data.

Aug 1, 2024

Maintenance

Gazetteer

Maintenance - Gazetteer

To synchronize the entries derived from the module DiversityGazetteer choose Administration → Maintenance from the menu. A window will open as shown below. On the tab page Gazetteer select the database containing the gazetteer data and the project for which the entries should be synchronized. There are 2 parts for the synchronization: The Place and the Coordinates. Select one of these parts for synchronization. To start the query click on the Check for differences   button.

The form will list all detected differences. To update the database click on the Start update  button.

To set links to the DiversityGazetteer for places which are not linked so far choose the second tab under Collection <→ Gazetteer for synchronization of places missing a connection to the DiversityGazetteer. Choose the database and the project and click on the Start query button. The results will be listed as shown below.

Many places have identical names in different regions. Names where several results were found are marked in blue. To choose the correct name among the list of results, click on the  Select valid place button and select the correct name from the list as shown below.

Finally, click on the Start update button to enter the results in the database.

Aug 1, 2024

Diversity Collection

Maintenance

Event Coordinates

Add Coordinates

If your data contain coordinates you can add additional coordinates in a different system for those dataset, where entries of the additional coordinate system are missing. E.g. you can add WGS84 coordinates on the basis of Gauss Krueger coordinates. In the Add coordinates tab choose the project you want to update and an optional upper limit of the datasets. Then select the source coordinates and the coordinate system these should be converted into. Click on the Start conversion button to start the conversion. If a conversion is not possible, the fields for the target system will be empty as shown below. The option Keep accuracy ensures that the accuracy if present in the original data will be copied into the new generated coordinates. Click the Insert coordinates button to insert the new coordinates into you datasets. 

Add WGS84 Coordinates for UTM

For adding WGS84 coordinates on the basis of existing UTM entries, you may have to specify the grid zone if this is missing in the data. By default the resulting WGS84 coordinates are rounded to 6 places corresponding to an accuracy of 1 m. In case you want to avoid the rounding of the calculated values, uncheck the Round to option (see below). By default the accuracy of the original data is kept. If you uncheck the Keep accuracy option the software will calculate an approximate value according to the given data. 

Check the video for an overview regarding UTM:

Calculate Coordinates

If your data contain coordinates e.g. written as non numeric entries like 59°21’W 10°12’S you can try to calculate numeric values from these entries (see below). Select the project, the maximal number that should be parsed and the type (currently only WGS84). Then start the conversion with a click on the start calculation button. Click the Insert coordinates button to insert the new coordinates into your datasets. 

 

Check Coordinates

If your data contain coordinates these may be inconsistent between the 3 places the coordinates are stored. To fix these inconsistencies use the functions showed in the image below and a short tutorial

For comparision of the cache values you may try to use numeric values as base for the comparision.

Add Coordinates for TK25 entries

If your data contain TK25 (= MTB) entries you can try to retrieve the coordinates and geography for these entries from data in the module DiversityGazetteer (see below). If the source database is located on a different server, select the source from the list (for adding source databases see chapter Connections). As the retrieval of the geographical data is rather time consuming, you may restrict the number datasets tested. Choose a project and click on the Find differences button to search for coordinates. Click the Start update button to update the TK25 entries with the found coordinates. 

Add TK25 entries for WGS84 coordinates

If your data contain WGS84 coordinates you can try to retrieve TK25 (= MTB) entries for these entries from data in the module DiversityGazetteer (see below). Select the source for the geographical information. If the source database is located on a different server and not connected via a linked server, select the source from the list (for adding source databases see chapter Connections). As the retrieval of the geographical data is rather time consuming, you may restrict the number datasets tested. By default the range for the search is restricted (Lat.: 47.1 - 55.2 and Long.: 6.0 - 15.2) to avoid the inclusion of coordinates where no TK25 information is expected. Choose a project and click on the Find missing TK25 button to search for coordinates. If you want to check a single dataset in the main form, mark this dataset and click on the button Close form and check dataset in database . Click the Start insert button to insert the TK25 entries for the found coordinates. 

A precondition for the above described handling of the TK25 datasets is the availablity of the corresponding data in the Gazetteer database. The current range is shown in the image below. 

 

Coordinates outside TK25

If your data contain WGS84 coordinates outside TK25 (= MTB) entries these can be detected in the Coordinates ouside TK25 part. Choose the project and click on the Find differences button. All entries with coordinates outside a TK25 entry for the same event will be listed (see below). Click on the Close form and check all detected datasets in main form  button to close the form and list the detected datasets in the main form.  

 

Find coordinates outside an area

If your data contain coordinates these may be positioned outside an area e.g. due to swapping latitude and longitude. You can detect these errors by comparing all coordinates within a project with an area as provided by DiversityGazetteer. In the maintenance form choose Events - Coordinates - Coordinates outside area. You may restrict the search with the country, the localisation sytem and the description of the locality (please use wildcards like %). The areas for comparison are provided by DiversityGazetteer. Choose one of the sources for areas. With the and buttons you can edit the list of area types from which the area is selected. Click on the Choose area for comparison button to select the area the coordinates should be compared with. A window will open where you can select among the areas provided by the DiversityGazetteer database you selected as a source. Finally click on the Find coordinates outside the area button. All corresponding localisations will be listed as shown in the image below. To inspect a single dataset, select it in the list and click on the Check selected dataset button. To edit the data in the main form, click on the Edit datasets in main form button. If you mark some datasets in the list, the selection in the main form will be restricted to these. Otherwise all datasets from the list will be shown. For an introduction see a short tutorial

 

Aug 1, 2024

Maintenance

Sampling Plots

To synchronize the entries derived from the module DiversitySamplingPlots choose Administration → Maintenance from the menu. A window will open as shown below. On the tab page Collection <→ SamplingPlots select the project for which the entries should be synchronized. There are 2 targets for the synchronization: The plot identifier (as stored in the field Location1), the Geography and the cached coordinates in table CollectionEventLocalisation. Select the project, one of targets for the synchronization and the DiversitySamplingPlots database. To start the query click on the  button.

The form will list all differences found. With the first column (OK) you may deselect certain entries which you do not wish to change. To update the database click on the button. If you wish to have a more detailed look on your data, you need to check the Include accession number checkbox before starting the query. A button will appear which will take you back to a single data set in the database.

 

Mar 20, 2025

Maintenance

Event Merge

Searching

If collection events with equal data should be merged, select the tab Events - Merge events as shown below. You may choose a project, a year, a country and the maximal number of results to restrict the search. By default all columns of the table CollectionEvent and additional information from the tables CollectionEventLocalisation and CollectionEventProperty as well as the exisitence of methods and images are included. To find similar events with different entries in certain parts, you can deselect those parts where there is no match in the data. To start the query select a project and click on the   Search for equal events  button. In the tree on the left, the result of the query will be displayed (see below). The events are sorted by their ID with the lowest values as top events of the groups.

 

Details

Click on an event to see the details for the event. For a complete inspection of the data of an event, click on any  event node in the tree and then on the button to open a separate window showing the details for the event including depending data (see below). You may open as many of these inspection windows as needed. The content will be displayed according to the time of display. For inspection of the top event you therefore have to close and reopen the window after a transfer of missing data as described below.

Merge event data

The target of the merge is always the top node of a group. To transfer missing data from events linked to the top event, select a depending event and click on the   insert missing values in top event  button. This will copy all missing data of the selected event in the top event. Finally select those events that should be merged and click on the   merge selected events  button.

 

Aug 1, 2024

Maintenance

Accession number duplicates

The database will warn but not prevent you from entering an accession number several times e.g. via an import. In the main form a duplicateaccession number is indicated with a red background. To check for duplicate accession numbers choose Administration - Maintenance from the menu. In the window that will open, choose the tab page  Specimen as shown below. You can restrict the query to a project or leave the project empty in order to compare with all the available projects. For a restriction to certain numbers you may enter a filter (using wildcards, see below). To start the query click on the Check for duplicates button.

The form will list all duplicates found as shown above. To switch to a data set in the database select it in the table and click on the Close form and check dataset in database button. To see only the selected rows, click on the Close form and check selected rows . To list all duplicates in the main form click on the Close form and check whole list in database . To compare the contents of duplicates, select the duplicate in the list and click on the button. A window as shown below will open. All tables containing the data of the duplicates will be shown.

Use the button to optimize the width of the columns. The columns in the tables are marked with different colors as shown in the image above. For the comparison of the data key columns will be ignored unless you choose the option Compare text key columns. To restrict the displayed tables and columns to those with differences, choose the Restrict to differences option (see below). In the window for comparing the data, editing is not possible, but you can open another client and edit the duplicated data. To show changes in the data performed e.g. in a second client, click on the button.

Jan 14, 2025

Maintenance

Retrieval Type

To find observations (= organisms without a part in a collection) with missing retrieval type choose Organisms - Retrieval type in the maintenance form as shown below. After selection of the project, click on the Find missing retrieval types button. The organisms missing a retrieval type will be listed as shown below. To inspect a single dataset, select it in the list and click on the Show selected dataset button. To edit the data in the main form, choose those you want to edit as shown in the image below and click on the Edit data in main form button. If nothing is selected all data will be listed. If you want to insert the missing retrieval type, selected the proper type from the list and click on the Insert retrieval type button

Aug 1, 2024

Maintenance

Storage

Maintenance - Insert missing organisms in specimen parts

To print a label for your samples you need to specify which of the organisms in the specimen should be shown on the label. If for any reason the organisms where not included into the parts as shown in the image below, you may do this belated for all data sets for a selected project.

Select the print tab as well as the project and click on the [Check for missing units in parts] button. The missing entries will be listed as shown below. To insert them click on the corresponding button.

 

Set storage location to last identification

The image below displays the option to synchronize the storage location with the last identification. Select the project and Search for differing storage . All parts with differing storage location will be listed. To check a single dataset, select it in the list and click on the Check dataset button. A click on the Update storage locations button writes the new versions of the storage locations in the database.

 

Aug 1, 2024

Maintenance

Analysis

To add a new analysis depending on present entries choose Administration - Maintenance from the menu. A window will open as shown below. On the tab page Analysis select the project, the taxonomic group, the analysis etc. for which the analysis should be added. To check the numbers present in the database, click on the button. The numbers will be listed in the area on the right. To test the data that would be added with you settings, click on the test button. To check a single dataset in the database, select it in the result list and click on the button. This will close the window and open the selected dataset in the main window. If finally you want to insert the data as shown in the area on the right, click on the button.

Aug 1, 2024

Maintenance

Images

The sorting of images may be changed for a whole project. Choose Administration - Maintenance from the menu. A window will open as shown below. On the tab page Images select the project for which the images should be sorted. There are 4 options to sort the images (see image below). Click on the button to list all images that may be sorted. To write the selected sorting into the database click the button Change sequence of images .

Aug 1, 2024

Maintenance

Administration of Regulations

To insert regulations like the Nagoya protocol choose Administration → Maintenance from the menu. A window will open as shown below. On the tab page Regulations select the project and the country for which the regulations should be entered. Select the collection and/or accession date where the search for the data should be started. A click on the Search for events button will start the search and list all detected data as shown below.

If the data should be withheld from publication e.g. via the cache database, enter the corresponding withholding reason . These withholding reasons will only be inserted if the specimens are not already withheld for other reasons.

Click on the button to find the regulation that should be inserted.

With the Start entry of the regulations button the withholding reasons and regulations will be inserted.

The regulations will be inserted as shown below.

 

Aug 1, 2024

Maintenance

Remove C0-codes

To remove C0 codes from text columns in the database choose Administration - Maintenance from the menu. A window will open as shown below. On the tab page Tools either start a query for all tables and columns in the database or select the table and column you want to test for the existance of C0 codes in the data. The data will be checked for C0 codes from 1 - 31 excluding 9, 10 and 13. If C0 codes are detected, these will be listed as shown below with C0 codes indicated by the ■ sign. You can either ignore this sign or remove it from the data using the corresponding buttons. 

Aug 1, 2024

Maintenance

Insert missing organisms in specimen parts

To print a label for your samples you need to specify which of the organisms in the specimen should be shown on the label. If for any reason the organisms where not included into the parts as shown in the image below, you may do this belated for all data sets for a selected project.

Select the print tab as well as the project and click on the Check for missing units in parts button. The missing entries will be listed as shown below. To insert them click on the corresponding button.

Aug 1, 2024

Maintenance

Reference Transfer

To transfer references from deprecated columns in the tables CollectionSpecimen and Identification into the new table CollectionSpecimenReference choose Administration → Maintenance from the menu. A window will open as shown below. On the tab page References you find the tabs for the transfer of the data. You may restrict the search to a project and have 2 types to match with existing data, either the Existence that will search for any data in the table CollectionSpecimenReference or the Title searching for content with the same title. Start the search with a click on the Search for references button. To show the details of a detected dataset, use the Show details button. To finally transfer the data into the new table, click on the Transfer data button. 

 

Mar 20, 2025

Collectors

Sequence

There may be datasets where the sequence of the collectors in one specimen are the same. To fix this error, use the Collector tab as shown below.

Click on the search button to search for the corresponding data. Then click on the update button to add the number of milliseconds to the last collector corresponding to the number of collectors detected. This will finally change the sequence according to the alphabetical order.

Aug 1, 2024

Subsections of Internals

Database

The image below shows the main datadomains within DiversityCollection.

The diagram shows the main tables of the database marked according to their logical groups. In the center the table CollectionSpecimen holds specimen data e.g. the accession number. On the left you find the tables containing collection event data and on the right tables related to the organisms and their identifications. Further logical groups are collectors, projects, storage and transaction.

Additional tables not included in the diagram above e.g. for the Task are shown in the chapters below.

The database for DiversityCollection based on Microsoft SQL-Server 2016 or above.

May 3, 2024

Subsections of Database

Subsections of Structure

Diversity Collection

TABLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table Analysis

Analysis types used within the database

Column Data type Description Nullable Relation
AnalysisID int ID of the analysis (primary key) NO -
AnalysisParentID int Analysis ID of the parent analysis, if it belongs to a certain type documented in this table YES Refers to table Analysis
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface YES -
Description nvarchar (MAX) Description of the analysis YES -
MeasurementUnit nvarchar (50) The measurement unit used for the analysis, e.g. mm, µmol, kg YES -
Notes nvarchar (MAX) Notes on this analysis YES -
AnalysisURI varchar (255) URI referring to an external documentation of the analysis YES -
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entriesDefault value: (0) YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table AnalysisResult

Value lists for analysis types with predefined values, e.g. “0, 1, 2, 3, …” for Red list category. Includes description etc. for the values in the list.

Column Data type Description Nullable Relation
AnalysisID int ID of the analysis (primary key) NO Refers to table Analysis
AnalysisResult nvarchar (255) The categorized value of the analysis NO -
Description nvarchar (500) Description of enumerated object displayed in the user interface YES -
DisplayText nvarchar (50) Short abbreviated description of the object displayed in the user interface YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Notes nvarchar (500) Internal development notes on usage, definition, etc. of an enumerated object YES -
LogInsertedBy nvarchar (50) Name of user to first enter (typ or import) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Point in time when the data was first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data last.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Point in time when this data was updated last.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Analysis

Table AnalysisTaxonomicGroup

The types of analysis which are available for a taxonomic group

Column Data type Description Nullable Relation
AnalysisID int Analysis ID, foreign key of table Analysis. NO Refers to table Analysis
TaxonomicGroup nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key) NO -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Analysis

Table Annotation

Annotations to datasets in the database

Column Data type Description Nullable Relation
AnnotationID int ID of the annotation (primary key) NO -
ReferencedAnnotationID int If an annotation refers to another annotation, the ID of the referred annotation YES Refers to table Annotation
AnnotationType nvarchar (50) The type of the annotation as defined in AnnotationType_Enum, e.g. ReferenceDefault value: N’Annotation' NO Refers to table AnnotationType_Enum
Title nvarchar (50) Title of the annotation YES -
Annotation nvarchar (MAX) The annotation entered by the user NO -
URI varchar (255) The complete URI address of a resource related to the annotation. May be link to a module, e.g. for the annotation type reference YES -
ReferenceDisplayText nvarchar (500) The title of the reference. If the entry is linked to an external module like DiversityReferences, the cached display text of the referenced data set YES -
ReferenceURI varchar (255) If the entry is linked to an external module like DiversityReferences, the link to the referenced data set YES -
SourceDisplayText nvarchar (500) The name of the source. If the entry is linked to an external module like DiversityAgents, the cached display text of the referenced data set YES -
SourceURI varchar (255) If the entry is linked to an external module like DiversityAgents, the link to the referenced data set YES -
IsInternal bit If an annotation is restricted to authorized users of the database YES -
ReferencedID int The ID of the data set in the table the annotation refers to NO -
ReferencedTable nvarchar (500) The name of the table the annotation refers to NO -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • AnnotationType_Enum

trgInsAnnotation

updating the logging columns


Table AnonymCollector

Anonyms for collectors of whom the names should not be published

Column Data type Description Nullable Relation
CollectorsName nvarchar (400) The name of the collector, PK NO -
Anonymisation nvarchar (50) The anonymisation phrase for the collector YES -

Table CacheDatabase2

Table holding the cache databases connected to the database

Column Data type Description Nullable Relation
Server varchar (50) The name or IP of the server where the cache database is located NO -
DatabaseName varchar (50) The name of the cache database NO -
Port smallint The port of the server where the cache database is located NO -
Version varchar (50) The version of the cache database YES -

Table CacheDescription

Table for temperary storage of description of database objects derived e.g. from tables Entity, EntityRepresentation etc.

Column Data type Description Nullable Relation
TableName varchar (50) The name of the table NO -
ColumnName varchar (50) The name of the table column NO -
LanguageCode varchar (50) The language code for the descriptionDefault value: ’en-US' NO -
Context nvarchar (50) A context e.g. as definded in table EntityContext_EnumDefault value: ‘General’ NO -
DisplayText nvarchar (50) The text for the table or column as shown e.g. in a user interface YES -
Abbreviation nvarchar (20) The abbreviation for the table or column as shown e.g. in a user interface YES -
Description nvarchar (MAX) The description for the table column YES -
ID int A unique ID NO -
Type varchar (20) Type of the entryDefault value: ‘COLUMN’ YES -
Schema varchar (100) Schema of the entryDefault value: ‘dbo’ YES -

Table Collection

The collections where the specimen are stored

Column Data type Description Nullable Relation
CollectionID int Unique reference ID for the collection (= primary key) NO -
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection YES Refers to table Collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information NO -
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum YES -
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection YES -
AdministrativeContactAgentURI varchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents YES -
Description nvarchar (MAX) A short description of the collection YES -
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection YES -
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection YES -
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry YES -
LocationGeometry geometry (MAX) Geometry of the collection within the floor plan YES -
LocationHeight float Height from ground level, e.g. for the position of sensors YES -
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location YES Refers to table Collection
LocationPlanDate datetime The date when the plan for the collection has been created YES -
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc. YES Refers to table CollCollectionType_Enum
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollCollectionType_Enum

Table CollectionAgent

The collector(s) of CollectionSpecimens

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key) NO Refers to table CollectionSpecimen
CollectorsName nvarchar (255) Name of the Collector NO -
CollectorsAgentURI varchar (255) The URI of the Agent, e.g. as stored within the module DiversityAgents YES -
CollectorsSequence datetime2 The order of collectors in a team. Automatically set by the database systemDefault value: sysdatetime() YES -
CollectorsNumber nvarchar (50) Number assigned to a specimen or a batch of specimens by the collector during the collection event (= ‘field number’) YES -
Notes nvarchar (MAX) Notes on the collector, e.g. if the name is uncertain YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimen

trgInsCollectionAgent

Setting the version of the dataset


Table CollectionEvent

The event where and when the specimen were collected

Column Data type Description Nullable Relation
CollectionEventID int Unique ID for the table CollectionEvent (= primary key) NO -
Version int The version of the data set. Automatically set by the system.Default value: (1) NO -
SeriesID int The ID of the related expedition. Relates to the PK of the table CollectionExpedition (foreign key). YES Refers to table CollectionEventSeries
CollectorsEventNumber nvarchar (50) Number assigned to a collection event by the collector (= ‘field number’) YES -
CollectionDate datetime The cached date of the collection event calulated from the entries in CollectionDay, -Month and -Year. YES -
CollectionDay tinyint The day of the date of the event or when the collection event started YES -
CollectionMonth tinyint The month of the date of the event or when the collection event started YES -
CollectionYear smallint The year of the date of the event or when the collection event started YES -
CollectionEndDay tinyint The day of the date of the event or when the collection event ended YES -
CollectionEndMonth tinyint The month of the date of the event or when the collection event ended YES -
CollectionEndYear smallint The year of the date of the event or when the collection event ended YES -
CollectionDateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event comprises a period. The time of the event, if necessary. YES -
CollectionDateCategory nvarchar (50) Category of the date of the identification e.g. “system”, “estimated” (= foreign key, see in table CollEventDateCategory_Enum) YES Refers to table CollEventDateCategory_Enum
CollectionTime varchar (50) The time of the event or when the collection event started YES -
CollectionTimeSpan varchar (50) The time span e.g. in seconds of the collection event YES -
LocalityDescription nvarchar (MAX) Locality description of the locality exactly as written on the original label (i.e. without corrections during data entry) YES -
LocalityVerbatim nvarchar (MAX) Locality as given in historical context, documents and labels YES -
HabitatDescription nvarchar (MAX) Geo-ecological description of the locality exactly as written on the original label (i.e. without corrections during data entry) YES -
ReferenceTitle nvarchar (255) The title of the publication where the collection event was published. Note that this is only a cached value where ReferenceURI is present YES -
ReferenceURI varchar (255) URI (e.g. LSID) of the source publication where the collection event is published, may e.g. refer to the module DiversityReferences YES -
ReferenceDetails nvarchar (50) The exact location within the reference, e.g. pages, plates YES -
CollectingMethod nvarchar (MAX) Description of the method used for collecting the samples, e.g. traps, moist chambers, drag net YES -
Notes nvarchar (MAX) Notes on the collection event YES -
CountryCache nvarchar (50) The country where the collection event took place. Cached value derived from an entry in CollectionEventLocalisation YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
DataWithholdingReasonDate nvarchar (50) The reason for withholding the collection date YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEventSeries
  • CollEventDateCategory_Enum

trgInsCollectionEvent

Setting the date in case of valid date columns


Table CollectionEventImage

The images showing the collection site resp. place of the observations

Column Data type Description Nullable Relation
CollectionEventID int Part of primay key, refers to unique ID for the table CollectionEvent (= foreign key) NO Refers to table CollectionEvent
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO -
ResourceURI varchar (255) The URI of the resource (e.g. see module DiversityResources) YES -
ImageType nvarchar (50) Type of the image, e.g. map YES Refers to table CollEventImageType_Enum
Notes nvarchar (MAX) Notes to this image concerning the CollectionEvent YES -
Description xml (MAX) Description of the image YES -
Title nvarchar (500) Title of the resource YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES -
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEvent
  • CollEventImageType_Enum

trgInsCollectionEventImage

Setting the version of the dataset


Table CollectionEventLocalisation

The geographic localisation of a CollectionEvent

Column Data type Description Nullable Relation
CollectionEventID int Refers to the ID of CollectionEvent (= foreign key and part of primary key) NO Refers to table CollectionEvent
LocalisationSystemID int Refers to the ID of LocalisationSystem (= foreign key and part of primary key) NO Refers to table LocalisationSystem
Location1 nvarchar (255) Either a named location selected from a thesaurus (e.g. ‘Germany, Bavaria, Kleindingharting’) or altitude range or other values (e. g. 100-200 m) YES -
Location2 nvarchar (255) Corresponding value to Location1 e.g. ID or URI of gazetteer or thesaurus YES -
LocationAccuracy nvarchar (50) The accuracy of the determination of this locality YES -
LocationNotes nvarchar (MAX) Notes on the location YES -
DeterminationDate smalldatetime Date of the determination of the geographical localisation YES -
DistanceToLocation varchar (50) Distance from the specified place to the real location of the collection site (m) YES -
DirectionToLocation varchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north) YES -
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES -
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES -
Geography geography The geography of the localisation YES -
RecordingMethod nvarchar (500) The method or device used for the recording of the localisation YES -
AverageAltitudeCache float Calculated altitude as parsed from the location fields YES -
AverageLatitudeCache float Calculated latitude as parsed from the location fields YES -
AverageLongitudeCache float Calculated longitude as parsed from the location fields YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEvent
  • LocalisationSystem

trgInsCollectionEventLocalisation

Setting missing geographical values on base of given values


Table CollectionEventMethod

The methods used during a collection event

Column Data type Description Nullable Relation
CollectionEventID int Refers to ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionEvent
MethodID int ID of the setting, part of primary key NO Refers to table Method
MethodMarker nvarchar (50) A marker for the method, part of primary keyDefault value: ‘1’ NO -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEvent
  • Method

Table CollectionEventParameterValue

The values of the parameter of the methods used within a collection event

Column Data type Description Nullable Relation
CollectionEventID int Unique ID for the table CollectionEvent (= foreign key and part of primary key) NO Refers to table CollectionEventMethod
MethodID int ID of the method tool. Referes to table Method (= foreign key and part of primary key) NO Refers to table CollectionEventMethod and table Parameter
MethodMarker nvarchar (50) A marker for the method, part of primary keyDefault value: ‘1’ NO Refers to table CollectionEventMethod
ParameterID int ID of the parameter tool. Referes to table Parameter (= foreign key and part of primary key) NO Refers to table Parameter
Value nvarchar (MAX) The value of the parameter, if different of the default value as documented in the table Parameter YES -
Notes nvarchar (MAX) Notes concerning the value of the parameter YES -
LogInsertedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogInsertedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • CollectionEventMethod
  • Parameter

Table CollectionEventProperty

A property of a collection site, e.g. exposition, slope, vegetation. May refer to Diversity Workbench module DiversityScientificTerms

Column Data type Description Nullable Relation
CollectionEventID int Refers to the ID of CollectionEvent (= foreign key and part of primary key) NO Refers to table CollectionEvent
PropertyID int The ID of the property of the collection site, foreign key, see table Property NO Refers to table Property
DisplayText nvarchar (255) The text for the property as shown e.g. in a user interface YES -
PropertyURI varchar (255) URI referring to an external data source e.g. DiversityTerminology YES -
PropertyHierarchyCache nvarchar (MAX) A cached text of the complete name of the descriptor including superior categories, if present YES -
PropertyValue nvarchar (255) The value of a captured feature, e.g. temperature, pH, vegetation etc. If there is a range, this is the lower or first value YES -
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES -
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES -
Notes nvarchar (MAX) Notes on the property of the colletion site. YES -
AverageValueCache float For numeric values - a cached average value according to the YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEvent
  • Property

trgInsCollectionEventProperty

Setting the version of the dataset


Table CollectionEventRegulation

Regulation applied to a collection event

Column Data type Description Nullable Relation
CollectionEventID int Part of primay key, refers to unique ID for the table CollectionEvent (= foreign key) NO Refers to table CollectionEvent
Regulation nvarchar (400) Regulation as defined in the table Regulation. Used to ensure, that user checked correct entry with authorized stuff NO -
TransactionID int Refers to unique TransactionID for the table Transaction (= foreign key) YES Refers to table Transaction
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEvent
  • Transaction

Table CollectionEventSeries

The series whithin which collection events take place

Column Data type Description Nullable Relation
SeriesID int Primary key. The ID for this series of collection events (= primary key) NO -
SeriesParentID int The ID of the superior series of collection events YES Refers to table CollectionEventSeries
Description nvarchar (MAX) The description of the series of collection events as it will be printed on e.g. the label NO -
SeriesCode nvarchar (50) The user defined code for a series of collection events YES -
Notes nvarchar (MAX) Notes on this series of collection events YES -
Geography geography The geography of the series of collection events YES -
DateStart datetime Point in time when the series of collection events started YES -
DateEnd datetime Point in time when the series of collection events ended YES -
DateCache datetime The first date of the depending events, used for sorting the expeditions [controlled by the database] YES -
DateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event series comprises a period. The time of the event, if necessary. YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table CollectionEventSeriesDescriptor

The Descriptors for the CollectionEventSeries

Column Data type Description Nullable Relation
SeriesID int Unique ID for the CollectionEventSeries (foreign key + part of primary key) NO Refers to table CollectionEventSeries
DescriptorID int Unique ID for the descriptor, Part of PK NO -
Descriptor nvarchar (200) The DescriptorDefault value: '’ NO -
URL varchar (500) URL of the Descriptor. In case of a module related Descriptor, the link to the module entry resp. the related webserviceDefault value: '’ YES -
DescriptorType nvarchar (50) Type of the Descriptor as described in table CollectionEventSeriesDescriptorType_EnumDefault value: N’Descriptor’ YES Refers to table CollEventSeriesDescriptorType_Enum
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEventSeries
  • CollEventSeriesDescriptorType_Enum

Table CollectionEventSeriesImage

The images showing the sites of a series of collection events, e.g. an expedition

Column Data type Description Nullable Relation
SeriesID int Unique ID for the table CollectionEventSeries (= foreign key and part of primary key) NO Refers to table CollectionEventSeries
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO -
ResourceURI varchar (255) The URI of the resource (e.g. see module DiversityResources) YES -
ImageType nvarchar (50) Type of the image, e.g. map YES Refers to table CollEventSeriesImageType_Enum
Notes nvarchar (MAX) Notes to this image of the collection site YES -
Description xml (MAX) Description of the image YES -
Title nvarchar (500) Title of the resource YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e.g. Creative Common licenses YES -
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionEventSeries
  • CollEventSeriesImageType_Enum

Table CollectionExternalDatasource

CollectionExternalDatasource document the sources of the names.

Column Data type Description Nullable Relation
ExternalDatasourceID int An ID to identify an external data collection of the collected specimen (primary key, the ID has no meaning outside of the DiversityWorkbench system) NO -
ExternalDatasourceName nvarchar (255) The name of the data collection which has been integrated or can be linked to for further analysis YES -
ExternalDatasourceVersion nvarchar (255) The version of this data collection (either official version number or dates when the collection was integrated) YES -
Rights nvarchar (500) A description of copyright agreements or permission to use data from the external database YES -
ExternalDatasourceAuthors nvarchar (200) The persons or institutions responsible for the external database YES -
ExternalDatasourceURI nvarchar (300) The URI of the database provider or the external database YES -
ExternalDatasourceInstitution nvarchar (300) The institution responsible for the external database YES -
InternalNotes nvarchar (1500) Additional notes on this data collection YES -
ExternalAttribute_NameID nvarchar (255) The table and field name in the external data collection to which CollectionExternalID refers YES -
PreferredSequence tinyint For selection in e.g. picklists: of several equal names only the name from the source with the lowest preferred sequence will be provided. YES -
Disabled bit If this source should be disabled for selection of names e.g. in picklists YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table CollectionImage

The images showing the collection

Column Data type Description Nullable Relation
CollectionID int Refers to the ID of Collection (= foreign key and part of primary key) NO Refers to table Collection
URI varchar (255) The complete URI address of the image. NO -
ImageType nvarchar (50) Type of the image, e.g. label YES Refers to table CollCollectionImageType_Enum
Notes nvarchar (MAX) Notes on the collection image YES -
Description xml (MAX) Description of the image YES -
Title nvarchar (500) Title of the resource YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e.g. Creative Common licenses YES -
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
LocationGeometry geometry (MAX) Geometry of the collection e.g. within a floor plan YES -
RecordingDate datetime The recording date of the resource YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
LogInsertedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogInsertedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollCollectionImageType_Enum
  • Collection

Table CollectionManager

Collection managers within DiversityCollection responsible for specimen transactions

Column Data type Description Nullable Relation
LoginName nvarchar (50) A login name which the user uses to access the DivesityWorkbench, Microsoft domains, etc.. NO -
AdministratingCollectionID int ID for the collection for which the Manager has the right to administrate the transaction. Corresponds to AdministratingCollectionID in table Transaction. NO Refers to table Collection
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Collection

Table CollectionProject

The projects within which the collection specimen were placed

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimen
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectProxy
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimen
  • ProjectProxy

trgInsCollectionProject

Setting LastChanges in table ProjectProxy


Table CollectionSpecimen

The data directly attributed to the collected specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key) NO -
Version int The version of the data setDefault value: (1) NO -
CollectionEventID int Refers to the ID of table CollectionEvent (= foreign key and part of primary key) YES Refers to table CollectionEvent
AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752” YES -
AccessionDate datetime The date of the accession calculated from the entries in AccessionDay, -Month and -Year YES -
AccessionDay tinyint The day of the date when the specimen was acquired in the collection YES -
AccessionMonth tinyint The month of the date when the specimen was acquired in the collection YES -
AccessionYear smallint The year of the date when the specimen was acquired in the collection YES -
AccessionDateSupplement nvarchar (255) Verbal or additional accession date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES -
AccessionDateCategory nvarchar (50) Category of the date of the accession e.g. “system”, “estimated” (= foreign key, see in table CollDateCategory_Enum) YES Refers to table CollDateCategory_Enum
DepositorsName nvarchar (255) The name of the depositor(s) (person or organization responsible for deposition). Where entire collections are deposited, this should also contain the collection name (e.g. ‘Herbarium P. Döbbler’) YES -
DepositorsAgentURI varchar (255) The URI of the depositor(s) (person or organization responsible for deposition) YES -
DepositorsAccessionNumber nvarchar (50) Accession number of the specimen within the previous or original collection, e.g. ‘D-23948’ YES -
LabelTitle nvarchar (MAX) The title of the label e.g. for printing labels. YES -
LabelType nvarchar (50) Printed, typewritten, typewritten with handwriting added, entirely in handwriting, etc. YES Refers to table CollLabelType_Enum
LabelTranscriptionState nvarchar (50) The state of the transcription of a label into the database: ‘Not started’, ‘incomplete’, ‘complete’ YES Refers to table CollLabelTranscriptionState_Enum
LabelTranscriptionNotes nvarchar (MAX) User defined notes on the transcription of the label into the database YES -
ExsiccataURI varchar (255) If specimen is an exsiccata: The URI of the exsiccata series, e.g. as stored within the DiversityExsiccata module YES -
ExsiccataAbbreviation nvarchar (255) If specimen is an exsiccata: Standard abbreviation of the exsiccata (not necessarily a unique identifier; editors or publication places may change over time) YES -
OriginalNotes nvarchar (MAX) Notes found on the label of the specimen by the original collector or from a later revision YES -
AdditionalNotes nvarchar (MAX) Additional notes made by the editor of the specimen record, e.g. ‘doubtful identification/locality’ YES -
Problems nvarchar (255) Description of a problem which occurred during data editing. Typically these entries should be deleted after help has been obtained. Do not enter scientific problems here; use AdditionalNotes for such permanent problems! YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise nullDefault value: N’Withhold by default’ YES -
InternalNotes nvarchar (MAX) Internal notes which should not be published e.g. on websites YES -
ExternalDatasourceID int An ID to identify an external data collection of the collected specimen (primary key, the ID has no meaning outside of the DiversityWorkbench system) YES Refers to table CollectionExternalDatasource
ExternalIdentifier nvarchar (100) The identifier of the external specimen as defined in the external data source YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollDateCategory_Enum
  • CollectionEvent
  • CollectionExternalDatasource
  • CollLabelTranscriptionState_Enum
  • CollLabelType_Enum

Table CollectionSpecimenImage

The images of a collection specimen or of an organism (stored in table IdentificationUnit) within this specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimen and table IdentificationUnit
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO -
ResourceURI varchar (255) The URI of the image, e.g. as stored in the module DiversityResources. YES -
SpecimenPartID int Optional: If the data set is not related to a part of a specimen, the ID of a related part (= foreign key) YES Refers to table CollectionSpecimenPart
IdentificationUnitID int If image refers to only one out of several IdentificationUnits for a specimen, refers to the ID of an IdentificationUnit for a collection specimen (= foreign key) YES Refers to table IdentificationUnit
ImageType nvarchar (50) Type of the image, e.g. photograph YES Refers to table CollSpecimenImageType_Enum
Notes nvarchar (MAX) Notes on the specimen image YES -
Description xml (MAX) Description of the image YES -
Title nvarchar (500) Title of the resource YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES -
LicenseURI varchar (500) The URI of the license for the resource YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
LicenseNotes nvarchar (500) Notice on license for the resource YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
DisplayOrder int The order in which the images should be shown in a interface YES -
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimen
  • CollectionSpecimenPart
  • CollSpecimenImageType_Enum
  • IdentificationUnit

CollectionSpecimenImage_URI

Deprecated

trgInsCollectionSpecimenImage

Setting the version of the dataset


Table CollectionSpecimenImageProperty

The properties of images of a collection specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimenImage
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO Refers to table CollectionSpecimenImage
Property varchar (255) The property of the image NO -
Description nvarchar (MAX) If description of the property of the image YES -
ImageArea geometry (MAX) The area in the image the property refers to YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -
PropertyURI varchar (500) The URI of the property of the image, e.g. a link to module DiversityScientificTerms YES -

Depending on:

  • CollectionSpecimenImage

Table CollectionSpecimenPart

Parts of a collected specimen. Includes a possible hierarchy of the parts

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimen and table CollectionSpecimenPart
SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key). NO -
DerivedFromSpecimenPartID int SpecimenPartID of the specimen from which the current specimen is derived from YES Refers to table CollectionSpecimenPart
PreparationMethod nvarchar (MAX) The method used for the preparation of the part of the specimen, e.g. the inoculation method for cultures YES -
PreparationDate datetime Point in time when the part was preparated e.g when it was separated from the source object YES -
AccessionNumber nvarchar (50) Accession number of the part of the specimen within the collection, if it is different from the accession number of the specimen as stored in the table CollectionSpecimen, e.g. “M-29834752” YES -
PartSublabel nvarchar (50) The label for a part of a specimen, e.g. “cone”, or a number attached to a duplicate of a specimen YES -
CollectionID int ID of the collection as stored in table Collection (= foreign key, see table Collection) NO Refers to table Collection
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum)Default value: N’specimen’ NO Refers to table CollMaterialCategory_Enum
StorageLocation nvarchar (255) A code identifying the place where the specimen is stored within the collection. Frequently the accepted scientific name is used as storage location code. YES -
Stock float Number of stock units, if the specimen is stored in separated units e.g. several boxes or vessels (max. 255) YES -
StockUnit nvarchar (50) If empty, the stock is given as a count, else it contains the unit in which stock is expressed, e.g. µl, ml, kg etc. YES -
StorageContainer nvarchar (500) The container in which the part is stored YES -
ResponsibleName nvarchar (255) Name of the person or institution responsible for the preparation YES -
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the preparation (= foreign key) as stored in the module DiversityAgents YES -
Notes nvarchar (MAX) Notes on the storage of the sample YES -
DataWithholdingReason nvarchar (255) If the specimen part is withhold, the reason for withholding the data, otherwise null. YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Collection
  • CollectionSpecimen
  • CollMaterialCategory_Enum

trgInsCollectionSpecimenPart

Setting the version of the dataset


Table CollectionSpecimenPartDescription

Description of the specimen part with a standardized vocabulary as defined in the module DiversityScientificTerms

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimenPart
SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key). NO Refers to table CollectionSpecimenPart
PartDescriptionID int ID of the description (Part of primary key) NO -
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) YES -
Description nvarchar (MAX) The descrition of the part. Cached value if DescriptionTermURI is used YES -
DescriptionTermURI varchar (500) Link to a external datasource like a webservice or the module DiversityScientificTerms where the description is documented YES -
Notes nvarchar (MAX) Notes about this description YES -
DescriptionHierarchyCache nvarchar (MAX) Hierarchy of the description. For values linked to a module, a cached value provided by the module YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimenPart

Table CollectionSpecimenProcessing

The processing which was applied to a collected specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimen and table CollectionSpecimenPart
SpecimenProcessingID int Unique ID of the processing of a specimen or part of a specimen, part of primary key NO -
ProcessingDate datetime Point in time of the start of the processing YES -
ProcessingID int ID of the processing method. Refers to ProcessingID in table Processing (foreign key)Default value: (1) NO Refers to table Processing
Protocoll nvarchar (100) The label of the processing protocol YES -
SpecimenPartID int Optional: If the data set is related to a part of a specimen, the ID of a related part (= foreign key, see table CollectionSpecimenPart) YES Refers to table CollectionSpecimenPart
ProcessingDuration varchar (50) The duration of the processing including the unit (e.g. 5 min) or the end of the processing starting at the processing date (e.g. 23.05.2008) YES -
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES -
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES -
Notes nvarchar (MAX) Notes on the processing YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -
ToolUsage xml (MAX) The tools used for the processing and their usage or settings. YES -

Depending on:

  • CollectionSpecimen
  • CollectionSpecimenPart
  • Processing

trgInsCollectionSpecimenProcessing

Setting the version of the dataset


Table CollectionSpecimenProcessingMethod

The methods used for a processing of a specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= Foreign key and part of primary key) NO Refers to table CollectionSpecimenProcessing
SpecimenProcessingID int Refers to the ID of the specimen processing (= foreign key and part of primary key) NO Refers to table CollectionSpecimenProcessing
MethodID int ID of the method, part of primary key NO Refers to table MethodForProcessing
MethodMarker nvarchar (50) A marker for the method, part of primary keyDefault value: ‘1’ NO -
ProcessingID int ID of the processing. Refers to ProcessingID in table Processing (foreign key)Default value: (1) NO Refers to table MethodForProcessing
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimenProcessing
  • MethodForProcessing

Table CollectionSpecimenProcessingMethodParameter

The parameter values of a method used for the processing of a specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= Foreign key and part of primary key) NO Refers to table CollectionSpecimenProcessingMethod
SpecimenProcessingID int Refers to ID of CollectionSpecimenProcessing (= Foreign key and part of primary key) NO Refers to table CollectionSpecimenProcessingMethod
ProcessingID int ID of the processing. Refers to ProcessingID in table Processing (= Foreign key and part of primary key)Default value: (1) NO Refers to table CollectionSpecimenProcessingMethod
MethodID int ID of the method (= Foreign key and part of primary key) NO Refers to table CollectionSpecimenProcessingMethod and table Parameter
MethodMarker nvarchar (50) A marker for the method, part of primary keyDefault value: ‘1’ NO Refers to table CollectionSpecimenProcessingMethod
ParameterID int ID of the parameter. Referes to table Parameter (= Foreign key and part of primary key) NO Refers to table Parameter
Value nvarchar (MAX) The value of the parameter if different of the default value as documented in the table Parameter NO -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimenProcessingMethod
  • Parameter

Table CollectionSpecimenReference

A reference related to the collection specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to unique ID of collection specimen record (part of primary key) NO Refers to table CollectionSpecimen and table IdentificationUnit
ReferenceID int Unique reference ID for the reference record (part of primary key) NO -
ReferenceTitle nvarchar (400) The title of the publication related to the specimen or parts of it. Note that this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (500) URI of the reference, e.g. a connection to the module DiversityReferences YES -
IdentificationUnitID int If relation refers to a certain organism within a specimen, the ID of an IdentificationUnit (= foreign key) YES Refers to table IdentificationUnit
IdentificationSequence smallint Referes to table Identification: The sequence of the identifications. YES -
SpecimenPartID int If the relation refers to a part of a specimen, the ID of a related part (= foreign key) YES Refers to table CollectionSpecimenPart
ReferenceDetails nvarchar (500) The exact location within the reference, e.g. pages, plates YES -
Notes nvarchar (MAX) Notes about the reference YES -
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES -
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimen
  • CollectionSpecimenPart
  • IdentificationUnit

Table CollectionSpecimenRelation

The relations of a collection specimen to other collection specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Unique reference ID for the collection specimen record (primary key) NO Refers to table CollectionSpecimen and table IdentificationUnit
RelatedSpecimenURI varchar (255) URI of the related specimen NO -
RelatedSpecimenDisplayText varchar (255) The name of a related specimen as shown e.g. in a user interface NO -
RelationType nvarchar (50) Type of the relation between the specimen (= foreign key, see table CollRelationType_Enum) YES Refers to table CollSpecimenRelationType_Enum
RelatedSpecimenCollectionID int ID of the Collection as stored in table Collection (= foreign key, see table Collection) YES Refers to table Collection
RelatedSpecimenDescription nvarchar (MAX) Description of the related specimen YES -
IdentificationUnitID int If relation refers to a certain organism within a specimen, the ID of an IdentificationUnit (= foreign key) YES Refers to table IdentificationUnit
SpecimenPartID int If the relation refers to a part of a specimen, the ID of a related part (= foreign key) YES Refers to table CollectionSpecimenPart
Notes nvarchar (MAX) Notes on the relation to the specimen YES -
IsInternalRelationCache bit If the relation represents a connection between specimen in this databaseDefault value: (1) NO -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Collection
  • CollectionSpecimen
  • CollectionSpecimenPart
  • CollSpecimenRelationType_Enum
  • IdentificationUnit

trgInsCollectionSpecimenRelation

Setting the version of the dataset


Table CollectionSpecimenTransaction

The transactions in which a specimen was involved

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimenPart
TransactionID int Unique ID for the table Transaction (= foreign key and part of primary key) NO Refers to table Transaction
SpecimenPartID int Optional: If the data set is related to a part of a specimen, the ID of a related part (= foreign key, see table CollectionSpecimenPart) NO Refers to table CollectionSpecimenPart
AccessionNumber nvarchar (255) Accession number which has been assigen to the part of the specimen, e.g. in connection with a former inventory. YES -
TransactionReturnID int Unique ID for the table Transaction (= foreign key) for the return of a part that has been on loan YES -
TransactionTitle nvarchar (200) Title as in related table Transaction. Used for validation of correct entry of transaction with type regulation (see insert trigger) YES -
IsOnLoan bit True, if a specimen is on loan YES -
LogInsertedBy nvarchar (50) Name of user to first enter (typ or import) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Point in time when the data was first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set last.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Point in time when this data set was updated last.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimenPart
  • Transaction

trgInsCollectionSpecimenTransaction

Rollback of regulations if corresponding datasets are missing in table CollectionEventRegulation


Table CollectionTask

A task for a collection. Details are defined in table Task

Column Data type Description Nullable Relation
CollectionTaskID int PK of the table NO -
CollectionTaskParentID int Relation to PK for hierarchy within the data YES Refers to table CollectionTask
CollectionID int Relation to table Collection. Every ColletionTask needs a relation to a collection NO Refers to table Collection
TaskID int Relation to table Task where details for the collection task are defined NO Refers to table Task
DisplayOrder int Display order e.g. in a report. Data with value 0 will not be includedDefault value: (1) YES -
DisplayText nvarchar (400) The display text of the module related data as shown e.g. in a user interface YES -
CollectionSpecimenID int Refers to the CollectionSpecimenID of CollectionSpecimenPart (= foreign key and part of primary key) YES Refers to table CollectionSpecimenPart
SpecimenPartID int Unique ID of the part of the collection specimen the task is related to. YES Refers to table CollectionSpecimenPart
TransactionID int ID of a transaction. Related to PK of table Transaction YES Refers to table Transaction
ModuleUri varchar (500) The URL of module related data YES -
TaskStart datetime The start date and or time of the collection tasks. The type is defined in table Task YES -
TaskEnd datetime The end date and or time of the collection tasks. The type is defined in table Task YES -
Result nvarchar (400) A text result either taken from a list or entered. The type is defined in table Task YES -
URI varchar (500) The URI of the collection tasks. The type is defined in table Task YES -
NumberValue real The numeric value of the collection tasks. The type is defined in table Task YES -
BoolValue bit The boolean of the collection tasks. The type is defined in table Task YES -
MetricDescription nvarchar (500) Description of the metric e.g. imported from a time series database like Prometheus YES -
MetricSource varchar (4000) The source of the metric e.g. the PromQL statement for the import from a timeseries database Prometheus YES -
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature YES -
ResponsibleAgent nvarchar (500) The name of the responsible person or institution YES -
ResponsibleAgentURI varchar (500) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES -
Description nvarchar (MAX) The description of the collection tasks. The type is defined in table Task YES -
Notes nvarchar (MAX) The notes of the collection tasks. The type is defined in table Task YES -
LogInsertedBy nvarchar (50) Name of the creator of this data setDefault value: dbo.UserID() YES -
LogInsertedWhen smalldatetime Point in time when this data set was createdDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: dbo.UserID() YES -
LogUpdatedWhen smalldatetime Point in time when this data set was updated lastDefault value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Collection
  • CollectionSpecimenPart
  • Task
  • Transaction

trgInsCollectionTask

Inserting CollectionID of parent entry if missing


Table CollectionTaskImage

The images showing the CollectionTask

Column Data type Description Nullable Relation
CollectionTaskID int Refers to the ID of CollectionTask (= foreign key and part of primary key) NO Refers to table CollectionTask
URI varchar (255) The complete URI address of the image. NO -
ImageType nvarchar (50) Type of the image, e.g. label YES -
Notes nvarchar (MAX) Notes on the CollectionTask image YES -
Description xml (MAX) Description of the image YES -
Title nvarchar (500) Title of the resource YES -
ObjectGeometry geometry (MAX) The geometry of an object placed within the image YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e.g. Creative Common licenses YES -
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
DisplayOrder smallint The display order of the image YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
LogInsertedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogInsertedBy nvarchar (50) Name of the creator of this data setDefault value: dbo.UserID() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: dbo.UserID() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionTask

Table CollectionTaskMetric

The metric related to a collection task

Column Data type Description Nullable Relation
CollectionTaskID int Refers to the ID of CollectionTask (= foreign key and part of primary key) NO Refers to table CollectionTask
MetricDate datetime Date and time of the metric, part of PK NO -
Aggregation nvarchar (50) The Aggregation applied for retrieval of the value, e.g. max, avg etc.Default value: N’none’ NO Refers to table CollTaskMetricAggregation_Enum
MetricValue real The value of the metric YES -
LogInsertedBy nvarchar (50) Name of the creator of this data setDefault value: dbo.UserID() YES -
LogInsertedWhen smalldatetime Point in time when this data set was createdDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: dbo.UserID() YES -
LogUpdatedWhen smalldatetime Point in time when this data set was updated lastDefault value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionTask
  • CollTaskMetricAggregation_Enum

Table CollectionUser

Users of collections within DiversityCollection

Column Data type Description Nullable Relation
LoginName nvarchar (50) A login name which the user uses to access the DivesityWorkbench, Microsoft domains, etc.. NO -
CollectionID int ID for the collection for the user has access to administrate the transaction. NO Refers to table Collection
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Collection

Table Entity

The entities in an application e.g. the tables and columns in a database

Column Data type Description Nullable Relation
Entity varchar (500) The name of the entity, e.g. Table.Column.Content within the database or a unique string for e.g. a message within the DiversityWorkbench e.g. “DiversityWorkbench.Message.Connection.NoAccess”, PK NO -
DisplayGroup nvarchar (50) If DiversityWorkbench entities should be displayed in a group, the name of the group YES -
Notes nvarchar (MAX) Notes on the entity YES -
Obsolete bit True if an entity is obsolete. Obsolete entities may be kept to ensure compatibility with older modules YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table EntityRepresentation

The description of the entity in a certain context in different languages

Column Data type Description Nullable Relation
Entity varchar (500) The name of the entity. Foreign key, relates to table Entity NO Refers to table Entity
LanguageCode nvarchar (50) ISO 639: 2-letter codes for the language of the content NO Refers to table EntityLanguageCode_Enum
EntityContext nvarchar (50) The context for the representation, e.g. “Exchange with ABCD”, “collection management” or “observation” as defined in table EntityContext_Enum NO Refers to table EntityContext_Enum
DisplayText nvarchar (50) The text for the entity as shown e.g. in a user interface YES -
Abbreviation nvarchar (20) The abbreviation for the entity as shown e.g. in a user interface YES -
Description nvarchar (MAX) The description of the entity YES -
Notes nvarchar (MAX) Notes on the representation of the entity YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Entity
  • EntityContext_Enum
  • EntityLanguageCode_Enum

Table EntityUsage

The usage of an entity in a certain context, e.g. hidden, readonly

Column Data type Description Nullable Relation
Entity varchar (500) The name of the entity. Foreign key, relates to table Entity NO Refers to table Entity
EntityContext nvarchar (50) The context for the representation, e.g. “Exchange with ABCD”, “collection management” or “observation” as defined in table EntityContext_Enum NO Refers to table EntityContext_Enum
Accessibility nvarchar (50) If the access of entity is resticted to e.g. read only or it can be edited without restrictions YES Refers to table EntityAccessibility_Enum
Determination nvarchar (50) If a value is determined e.g. by the system or the user YES Refers to table EntityDetermination_Enum
Visibility nvarchar (50) If the entity is visible or hidden from e.g. a user interface YES Refers to table EntityVisibility_Enum
PresetValue nvarchar (500) If a value is preset, the value or SQL statement for the value, e.g. ‘determination’ for identifications when using a mobile device during an expedition YES -
Notes nvarchar (MAX) Notes on the usage of the entity YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Entity
  • EntityAccessibility_Enum
  • EntityContext_Enum
  • EntityDetermination_Enum
  • EntityVisibility_Enum

Table ExternalIdentifier

An external identier related to a dataset, e.g. a DOI

Column Data type Description Nullable Relation
ID int ID of the identifier (Primary key) NO -
ReferencedTable nvarchar (128) The name of the table the external identifier refers to NO -
ReferencedID int The ID of the data set in the table the external identifier refers to NO -
Type nvarchar (50) The type of the identifier as defined in table ExternalIdentifierType YES Refers to table ExternalIdentifierType
Identifier nvarchar (500) The identifier YES -
URL varchar (500) A URL with further informations about the identifier YES -
Notes nvarchar (MAX) Notes about the identifier YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • ExternalIdentifierType

Table ExternalIdentifierType

The type of an external identier, e.g. DOI

Column Data type Description Nullable Relation
Type nvarchar (50) The type of external identifiers (primary key) NO -
ParentType nvarchar (50) The superior type of this type YES -
URL varchar (500) A URL providing further informations about this type YES -
Description nvarchar (MAX) The description of this type YES -
InternalNotes nvarchar (MAX) Internal notes about the type YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newid() NO -

Table Identification

The identifications of the organisms within a specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table Identification and table IdentificationUnit
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO Refers to table Identification and table IdentificationUnit
IdentificationSequence smallint The sequence of the identifications. The last identification (having the highest sequence) is regarded as validDefault value: (1) NO -
DependsOnIdentificationSequence smallint if the identification depends on another identification, e.g. for rocks where several terms from a terminology should be included YES Refers to table Identification
IdentificationDate datetime The date of the identification calculated from the entries in IdentificationDay, -Month and -Year YES -
IdentificationDay tinyint The day of the identification YES -
IdentificationMonth tinyint The month of the identification YES -
IdentificationYear smallint The year of the identification. The year may be empty if only the day or month are known. YES -
IdentificationDateSupplement nvarchar (255) Verbal or additional identification date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES -
IdentificationDateCategory nvarchar (50) Category of the date of the identification e.g. “system”, “estimated” (= foreign key, see in table CollDateCategory_Enum) YES Refers to table CollIdentificationDateCategory_Enum
VernacularTerm nvarchar (255) Name or term other than a taxonomic (= scientific) name, e.g. ‘pine’, ’limestone’, ‘conifer’, ‘hardwood’ YES -
TermURI varchar (500) The URI of the term, e.g. as provided by the module DiversityScientificTerms. YES -
TaxonomicName nvarchar (255) Valid name of the species (including the taxonomic author where available). Example: ‘Rosa canina L.’ YES -
NameURI varchar (255) The URI of the taxonomic name, e.g. as provided by the module DiversityTaxonNames. YES -
IdentificationCategory nvarchar (50) Category of the identification e.g. ‘determination’, ‘confirmation’, ‘absence’ (= foreign key, see table CollIdentificationCategory_Enum) YES Refers to table CollIdentificationCategory_Enum
IdentificationQualifier nvarchar (50) Qualification of the identification e.g. “cf.”," aff.", “sp. nov.” (= foreign key, see table CollIdentificationQualifier_Enum) YES Refers to table CollIdentificationQualifier_Enum
TypeStatus nvarchar (50) If identification unit is type of a taxonomic name: holotype, syntype, etc. (= foreign key, see table CollTypeStatus_Enum) YES Refers to table CollTypeStatus_Enum
TypeNotes nvarchar (MAX) Notes on the typification of this specimen YES -
Notes nvarchar (MAX) User defined notes, e.g. the reason for a re-determination / change of the name, etc. YES -
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES -
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollIdentificationCategory_Enum
  • CollIdentificationDateCategory_Enum
  • CollIdentificationQualifier_Enum
  • CollTypeStatus_Enum
  • IdentificationUnit

trgIdentificationInsert

Updating the LastIdentificationCache in IdentificationUnit

trgInsIdentification

Updating empty date columns depending on a given date


Table IdentificationUnit

Organism which is present in or on a collectied specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimen and table IdentificationUnit
IdentificationUnitID int ID of the IdentificationUnit (= part of primary key). Usually one of possibly several organisms present on the collected specimen. Example: parasite with hyperparasite on plant leaf = 3 units, NO -
LastIdentificationCache nvarchar (255) The last identification as entered in table Identification NO -
FamilyCache nvarchar (255) A cached value of the family of the taxon of the last identification. Can be set by the editor, if NameURI in table Identification is NULL, otherwise set by the system. YES -
OrderCache nvarchar (255) A cached value of the order of the taxon of the last identification. Can be set by the editor, if NameURI in table Identification is NULL, otherwise set by the system. YES -
HierarchyCache nvarchar (500) A cached value fo the superior taxonomy of the last identification as derived from a taxonomic data provider YES -
TaxonomicGroup nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key) NO Refers to table CollTaxonomicGroup_Enum
OnlyObserved bit True, if the organism was only observed rather than collected. It is therefore not present on the preserved specimen. Example: Tree under which the collected mycorrhizal fungus grew.Default value: (0) YES -
RelatedUnitID int The IdentificationUnitID of the organism or substrate on which this organism is growing (= foreign key) YES Refers to table IdentificationUnit
RelationType nvarchar (50) The relation of a unit to its substrate, e.g. parasitism, symbiosis etc. as stored in CollRelationType_Enum (= foreign key) YES Refers to table CollUnitRelationType_Enum
ParentUnitID int The IdentificationUnitID of a parent organism of which this organism is a child of (= foreign key). YES Refers to table IdentificationUnit
ColonisedSubstratePart nvarchar (255) If a substrate association exists: part of the substrate which is affected in the interaction (e.g. ’leaves’, if a fungus is growing on the leaves of an infected plant) YES -
LifeStage nvarchar (255) Examples: ‘II, III’ for spore generations of rusts or ‘seed’, ‘seedling’ etc. for higher plants YES -
Gender nvarchar (50) The sex of the organism, e.g. ‘female’ YES -
NumberOfUnits smallint The number of units of this organism, e.g. 400 beetles in a bottle YES -
NumberOfUnitsModifier nvarchar (100) A modifier for the number of units of this organism, e.g. ca. 400 beetles in a bottle YES -
ExsiccataNumber nvarchar (50) If specimen is an exsiccata: Number of current specimen within the exsiccata series YES -
ExsiccataIdentification smallint Refers to the IdentificationSequence in Identification (= foreign key). The name under which the collectied specimen or this organism is published within an exsiccata. YES -
UnitIdentifier nvarchar (50) An identifier for the identification of the unit, e.g. a number painted on a tree within an experimental plot YES -
UnitDescription nvarchar (50) Description of the unit, especially if not an organism but parts or remnants of it were present or observed, e.g. a nest of an insect or a song of a bird YES -
Circumstances nvarchar (50) Circumstances of the occurence of the organism YES Refers to table CollCircumstances_Enum
RetrievalType nvarchar (50) The way the data about the unit were retrieved, e.g. observation, literature YES Refers to table CollRetrievalType_Enum
DisplayOrder smallint The sequence in which the units within this specimen will appear on e.g. a label where the first unit may be printed in the header and others in the text below. 0 means the unit should not appear on a label.Default value: (1) NO -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
Notes nvarchar (MAX) Further information on the organism or interaction, e.g. infection symptoms like ‘producing galls’ YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollCircumstances_Enum
  • CollectionSpecimen
  • CollRetrievalType_Enum
  • CollTaxonomicGroup_Enum
  • CollUnitRelationType_Enum

trgInsIdentificationUnit

setting the display oder for the new unit to the next number if none or an already present on was given


Table IdentificationUnitAnalysis

The analysis values taken from an organism resp. object

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table IdentificationUnit and table IdentificationUnitInPart
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO Refers to table IdentificationUnit and table IdentificationUnitInPart
AnalysisID int Analysis ID, foreign key of table Analysis. NO Refers to table Analysis
AnalysisNumber nvarchar (50) Number of the analysis NO -
AnalysisResult nvarchar (MAX) The result of the analysis YES -
ExternalAnalysisURI varchar (255) An URI for an analysis as defined in an external datasoure YES -
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES -
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES -
AnalysisDate nvarchar (50) The date of the analysis YES -
SpecimenPartID int ID of the part of a specimen (optional, foreign key) if the analysis was done with a part of the specimen (see table CollectionSpecimenPart). YES Refers to table IdentificationUnitInPart
Notes nvarchar (MAX) Notes on this analysis YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -
ToolUsage xml (MAX) The tools used for the analysis and their usage or settings. YES -

Depending on:

  • Analysis
  • IdentificationUnit
  • IdentificationUnitInPart

trgInsIdentificationUnitAnalysis

Setting the version of the dataset


Table IdentificationUnitAnalysisMethod

The methods used for an analysis

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= Foreign key and part of primary key) NO Refers to table IdentificationUnitAnalysis
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO Refers to table IdentificationUnitAnalysis
MethodID int ID of the method, part of primary key NO Refers to table MethodForAnalysis
MethodMarker nvarchar (50) A marker for the method, part of primary keyDefault value: ‘1’ NO -
AnalysisID int ID of the processing. Refers to AnalysisID in table Processing (foreign key)Default value: (1) NO Refers to table IdentificationUnitAnalysis and table MethodForAnalysis
AnalysisNumber nvarchar (50) Number of the analysis NO Refers to table IdentificationUnitAnalysis
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: suser_sname() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • IdentificationUnitAnalysis
  • MethodForAnalysis

Table IdentificationUnitAnalysisMethodParameter

The parameter values of a method used for an analysis

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= Foreign key and part of primary key) NO Refers to table IdentificationUnitAnalysisMethod
IdentificationUnitID int ID of the identification unit (= Foreign key and part of primary key) NO Refers to table IdentificationUnitAnalysisMethod
AnalysisID int ID of the analysis. Refers to AnalysisID in table Analysis (= Foreign key and part of primary key)Default value: (1) NO Refers to table IdentificationUnitAnalysisMethod
AnalysisNumber nvarchar (50) Number of the analysis (= Foreign key and part of primary key) NO Refers to table IdentificationUnitAnalysisMethod
MethodID int ID of the method (= Foreign key and part of primary key) NO Refers to table IdentificationUnitAnalysisMethod and table Parameter
MethodMarker nvarchar (50) A marker for the method, part of primary keyDefault value: ‘1’ NO Refers to table IdentificationUnitAnalysisMethod
ParameterID int ID of the parameter tool. Referes to table Parameter (= Foreign key and part of primary key) NO Refers to table Parameter
Value nvarchar (MAX) The value of the parameter if different of the default value as documented in the table Parameter YES -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • IdentificationUnitAnalysisMethod
  • Parameter

Table IdentificationUnitGeoAnalysis

The geographical position or region of an organism at a certain time

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table IdentificationUnit
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO Refers to table IdentificationUnit
AnalysisDate datetime The date of the analysis NO -
Geography geography The geography where the organism resp. object was located according to WGS84, e.g. a point (latitide, longitude and altitude) YES -
Geometry geometry (MAX) The geometry of the place the organism resp. object was observed, e.g. an area YES -
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES -
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES -
Notes nvarchar (MAX) Notes on this analysis YES -
LogCreatedWhen datetime Point in time when this data set was created YES -
LogCreatedBy nvarchar (50) Name of the creator of this data set YES -
LogUpdatedWhen datetime Point in time when this data set was updated last YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set last YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • IdentificationUnit

Table IdentificationUnitInPart

The list of the organisms which are found in a part of the specimen

Column Data type Description Nullable Relation
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO Refers to table CollectionSpecimenPart and table IdentificationUnit
IdentificationUnitID int ID of the identification unit in table IdentificationUnit (= part of primary key). Usually one of possibly several organisms present on the collection specimen. Example: parasite with hyperparasite on plant leaf = 3 units, NO Refers to table IdentificationUnit
SpecimenPartID int ID of the part of a specimen (optional, foreign key), if the identification unit is located on a part of the specimen (see table CollectionSpecimenPart). NO Refers to table CollectionSpecimenPart
DisplayOrder smallint The sequence in which the units within this part will appear on e.g. a label where the first unit may be printed in the header and others in the text below. 0 means the unit should not appear on a label.Default value: (1) NO -
LogInsertedBy nvarchar (50) Name of the user to first enter (typ or import) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Point in time when the data was first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data last.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Point in time when this data was updated last.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollectionSpecimenPart
  • IdentificationUnit

trgInsIdentificationUnitInPart

Setting the version of the dataset


Table LocalisationSystem

The geographic localisation systems, e.g. coordinates

Column Data type Description Nullable Relation
LocalisationSystemID int Unique ID for the localisation system (= Primary key) NO -
LocalisationSystemParentID int LocalisationSystemID of the superior LocalisationSystem YES Refers to table LocalisationSystem
LocalisationSystemName nvarchar (100) Name of the system used for the determination of the place of the collection, e. g. Gauss-Krüger, MTB, GIS NO -
DefaultAccuracyOfLocalisation nvarchar (50) The default for the accuracy of values which can be reached with this method YES -
DefaultMeasurementUnit nvarchar (50) The default measurement unit for the localisation system, e.g. m, geograpic coordinates YES -
ParsingMethodName nvarchar (50) Internal value, specifying a programming method used for parsing text in fields Location1/Location2 in table CollectionLocalisation YES -
DisplayText nvarchar (50) Short abbreviated description of the localisation system as displayed in the user interface YES -
DisplayEnable bit Specifies, if this item is enabled to be used within the database. Localisation systems can be disabled to avoid seeing them, but keep the definition for the future. YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Description nvarchar (255) Description of the localisation method YES -
DisplayTextLocation1 nvarchar (50) Short abbreviated description of the attribute Location1 in the table CollectionGeography as displayed in the user interface YES -
DescriptionLocation1 nvarchar (255) Description of the attribute Location1 in the table CollectionGeography as displayed in the user interface YES -
DisplayTextLocation2 nvarchar (50) Short abbreviated description of the attribute Location2 in the table CollectionGeography as displayed in the user interface YES -
DescriptionLocation2 nvarchar (255) Description of the attribute Location2 in the table CollectionGeography as displayed in the user interface YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table Method

Methods used within the database

Column Data type Description Nullable Relation
MethodID int ID of the Method (Primary key) NO -
MethodParentID int MethodID of the parent Method, if it belongs to a certain type documented in this table YES Refers to table Method
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entriesDefault value: (0) YES -
DisplayText nvarchar (50) Name of the Method as e.g. shown in user interface YES -
Description nvarchar (MAX) Description of the Method YES -
MethodURI varchar (255) URI referring to an external documentation of the Method YES -
ForCollectionEvent bit If a method may be used during a collection event YES -
Notes nvarchar (MAX) Notes on this method YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table MethodForAnalysis

Methods available for a Analysis

Column Data type Description Nullable Relation
AnalysisID int ID of the table Analysis (foreign key and part of primary key) NO Refers to table Analysis
MethodID int ID of the table Method (foreign key and part of primary key) NO Refers to table Method
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Analysis
  • Method

Table MethodForProcessing

Methods available for a processing

Column Data type Description Nullable Relation
ProcessingID int ID of the table Processing (foreign key and part of primary key) NO Refers to table Processing
MethodID int ID of the table Method (foreign key and part of primary key) NO Refers to table Method
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Method
  • Processing

Table Parameter

The variable parameters within a method

Column Data type Description Nullable Relation
MethodID int ID of the Method (foreign key and part of primary key) NO Refers to table Method
ParameterID int ID of the Parameter (part of primary key) NO -
DisplayText nvarchar (50) Name of the parameter as e.g. shown in user interface YES -
Description nvarchar (MAX) Description of the parameter YES -
ParameterURI varchar (255) URI referring to an external documentation of the Parameter YES -
DefaultValue nvarchar (MAX) The default value of the parameter YES -
Notes nvarchar (MAX) Notes on this parameter YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Method

Table Processing

The processings of the specimen

Column Data type Description Nullable Relation
ProcessingID int ID of the processing (primary key) NO -
ProcessingParentID int The ID of the superior type of the processing YES Refers to table Processing
DisplayText nvarchar (50) The display text of the processing as shown e.g. in a user interface YES -
Description nvarchar (MAX) Description of the processing YES -
Notes nvarchar (MAX) Notes on the processing YES -
ProcessingURI varchar (255) A URI for a processing as defined in an external data source YES -
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entriesDefault value: (0) YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table ProcessingMaterialCategory

The processings which are possible for a certain material category

Column Data type Description Nullable Relation
ProcessingID int ID of the processing. Refers to ProcessingID in table Processing (foreign key)Default value: (1) NO Refers to table Processing
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.Default value: N’specimen’ NO -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Processing

Table ProjectAnalysis

The types of the analysis which are available for a project

Column Data type Description Nullable Relation
AnalysisID int ID of the analysis (primary key) NO Refers to table Analysis
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectProxy
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Analysis
  • ProjectProxy

Table ProjectMaterialCategory

The material categorys which are possible for a certain Project

Column Data type Description Nullable Relation
ProjectID int ID of the Project. Refers to ProjectID in table ProjectProxy (foreign key)Default value: (1) NO Refers to table ProjectProxy
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.Default value: N’specimen’ NO Refers to table CollMaterialCategory_Enum
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollMaterialCategory_Enum
  • ProjectProxy

Table ProjectProcessing

The types of processing available within a project

Column Data type Description Nullable Relation
ProcessingID int ID of the table Processing (foreign key and part of primary key) NO Refers to table Processing
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectProxy
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Processing
  • ProjectProxy

Table ProjectTaxonomicGroup

The taxonomic group which are possible for a certain Project

Column Data type Description Nullable Relation
ProjectID int ID of the Project. Refers to ProjectID in table ProjectProxy (foreign key)Default value: (1) NO Refers to table ProjectProxy
TaxonomicGroup nvarchar (50) Taxonomic group of specimen. Examples: ‘plant’, ‘animal’, etc.Default value: N’plant’ NO Refers to table CollTaxonomicGroup_Enum
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • CollTaxonomicGroup_Enum
  • ProjectProxy

Table ProjectUser

The projects which a user can access

Column Data type Description Nullable Relation
LoginName nvarchar (50) A login name which the user uses to access the DivesityWorkbench, Microsoft domains, etc.. NO Refers to table UserProxy
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectProxy
ReadOnly bit If the user has only read access to data of this projectDefault value: (0) YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • ProjectProxy
  • UserProxy

trgInsProjectUser

Setting ReadOnly in dependence of locked projects


Table Property

The list of the properties that can be specified for the collection site

Column Data type Description Nullable Relation
PropertyID int Unique ID for the property (= primary key) NO -
PropertyParentID int PropertyID of the superior property YES Refers to table Property
PropertyName nvarchar (100) Name of the system used for the description of the collection site, e.g. Chronostratigraphy NO -
DefaultAccuracyOfProperty nvarchar (50) The default for the accuracy of values which can be reached with this method YES -
DefaultMeasurementUnit nvarchar (50) The default measurement unit for the characterisation system, e.g. pH YES -
ParsingMethodName nvarchar (50) Internal value, specifying a programming method used for parsing text in table CollectionEventProperty NO -
DisplayText nvarchar (50) Short abbreviated description of the site property as displayed in the user interface YES -
DisplayEnabled bit Specifies, if this item is enabled to be used within the database. Properties can be disabled to avoid seeing them, but keep the definition for the future.Default value: (1) YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Description nvarchar (MAX) Description of the property YES -
PropertyURI varchar (1000) The URI of the property, e.g. as provided by the module DiversityScientificTerms. YES -
PropertyType nvarchar (50) Type of the collection site property, e.g. Chronostratigraphy YES Refers to table PropertyType_Enum
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • PropertyType_Enum

Table ReplicationPublisher

Databases providing data via replication

Column Data type Description Nullable Relation
DatabaseName varchar (255) The name of the publishing database NO -
Server varchar (255) The name or address of the server where the publishing database is located NO -
Port smallint The port used by the server YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -

Table Task

The Tasks of the collection

Column Data type Description Nullable Relation
TaskID int ID of the Task (primary key) NO -
TaskParentID int The ID of the superior type of the Task YES Refers to table Task
DisplayText nvarchar (50) The display text of the Task as shown e.g. in a user interface YES -
Description nvarchar (MAX) Description of the Task YES -
Notes nvarchar (MAX) Notes on the Task YES -
TaskURI varchar (500) A URI for a Task as defined in an external data source YES -
Type nvarchar (50) The type of the task as defined in table TaskType_EnumDefault value: ‘Task’ YES Refers to table TaskType_Enum
ModuleTitle nvarchar (50) The title for module related data for collection tasks. Not available in depending collection task if empty YES -
ModuleType nvarchar (50) The DiversityWorkbench module to which a task is related. Not available in depending collection task if empty YES Refers to table TaskModuleType_Enum
SpecimenPartType nvarchar (50) The description of the collection specimen part to which a task is related. Not available in depending collection task if empty YES -
TransactionType nvarchar (50) The description of the transaction to which a task is related. Not available in depending collection task if empty YES -
ResultType nvarchar (50) The display text for the results as shown in a user interface. Not available in depending collection task if empty YES -
DateType nvarchar (50) The date and time details defined for a task. Not available in depending collection task if empty YES Refers to table TaskDateType_Enum
DateBeginType nvarchar (50) The definition of the begin for date and time details defined for a task. Not available in depending collection task if empty YES -
DateEndType nvarchar (50) The definition of the end for date and time details defined for a task. Not available in depending collection task if empty YES -
NumberType nvarchar (50) The definition for the numeric value as shown in a user interface. Not available in depending collection task if empty YES -
BoolType nvarchar (50) The definition for the boolean value as shown in a user interface. Not available in depending collection task if empty YES -
MetricType nvarchar (50) The definition for the metric as shown in a user interface. Not available in depending collection task if empty YES -
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature YES -
DescriptionType nvarchar (50) The definition for the description as shown in a user interface. Not available in depending collection task if empty YES -
NotesType nvarchar (50) The definition for the notes as shown in a user interface. Not available in depending collection task if empty YES -
UriType nvarchar (50) The definition for the URI as shown in a user interface. Not available in depending collection task if empty YES -
ResponsibleType nvarchar (50) The definition for the responsible agent as shown in a user interface. Not available in depending collection task if empty YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: dbo.UserID() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: dbo.UserID() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • TaskDateType_Enum
  • TaskModuleType_Enum
  • TaskType_Enum

Table TaskModule

Data from DiversityWorkbench modules used used within a task

Column Data type Description Nullable Relation
TaskID int ID of the task, part of PK, relates to PK of table Task NO Refers to table Task
DisplayText nvarchar (400) Display text as provided by the module, part of PK NO -
URI varchar (500) URI linking the dataset of the module YES -
Description nvarchar (MAX) Optional description of the linked data, e.g. the common name for taxa YES -
Notes nvarchar (MAX) Notes related to the dataset YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) ID of the creator of this data setDefault value: dbo.UserID() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: dbo.UserID() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Task

Table TaskResult

List or results provided for the CollectionTask of the corresponding type

Column Data type Description Nullable Relation
TaskID int ID of the task, part of PK, relates to PK of table Task NO Refers to table Task
Result nvarchar (400) The result, part of PK NO -
URI varchar (500) A URI of the result providing further information YES -
Description nvarchar (MAX) The description of the entry YES -
Notes nvarchar (MAX) Notes about the entry YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) ID of the creator of this data setDefault value: dbo.UserID() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: dbo.UserID() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Task

Table Transaction

Transactions like loan, borrow, gift, exchange etc. of specimen, if they are e.g. permanently or temporary transfered from one collection to another

Column Data type Description Nullable Relation
TransactionID int Unique ID for the transaction (= primary key) NO -
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy YES Refers to table Transaction
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or outDefault value: N’exchange’ NO Refers to table CollTransactionType_Enum
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO -
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES -
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction. NO Refers to table Collection
MaterialDescription nvarchar (MAX) Description of the material of this transactionDefault value: '’ YES -
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.Default value: N’specimen’ YES -
MaterialCollectors nvarchar (MAX) The collectors of the material YES -
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation YES -
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift YES Refers to table Collection
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES -
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES -
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES -
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift YES Refers to table Collection
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES -
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES -
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES -
NumberOfUnits int The number of units which were (initially) included in the transaction YES -
Investigator nvarchar (200) The investigator for whose study a transacted material was sent YES -
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES -
BeginDate datetime Date when the transaction started YES -
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES -
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner YES -
DateSupplement nvarchar (100) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. YES -
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES -
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents YES -
ResponsibleName nvarchar (255) The person responsible for this transaction YES -
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents) YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: user_name() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Collection
  • CollTransactionType_Enum

Table TransactionAgent

Agents involved in the transaction

Column Data type Description Nullable Relation
TransactionID int Unique ID for the transaction, refers to table Transaction (= part of primary key and foreign key) NO Refers to table Transaction
TransactionAgentID int Unique ID for the Agent within the transaction (= part of primary key) NO -
AgentName nvarchar (500) Name of the person or institution YES -
AgentURI varchar (500) Link to the source for further informations about the agent, e.g in the module DiversityAgents YES -
AgentRole nvarchar (500) Role of the agent within the transaction YES -
Notes nvarchar (MAX) Notes about the agent YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Transaction

Table TransactionComment

The standard text phrases for transactions

Column Data type Description Nullable Relation
Comment nvarchar (400) Text as transferred into the comment of a transaction NO -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table TransactionDocument

The history of transactions or the documents connected to the transactions

Column Data type Description Nullable Relation
TransactionID int Unique ID for the transaction, refers to table Transaction (= part of primary key and foreign key) NO Refers to table Transaction
Date datetime The date of the event of a transaction NO -
TransactionText nvarchar (MAX) The text of a transaction document YES -
TransactionDocument image A scanned document connected to this transaction YES -
DisplayText nvarchar (255) A display text as shown e.g. in a user interface to characterize the document YES -
DocumentURI varchar (1000) A link to a web resource of the document the document YES -
DocumentType nvarchar (255) The type of the document YES -
InternalNotes nvarchar (MAX) Internal notes on this transaction YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Transaction

Table TransactionPayment

The payments within a transaction

Column Data type Description Nullable Relation
TransactionID int Unique ID for the transaction, refers to table Transaction (= part of primary key and foreign key) NO Refers to table Transaction
PaymentID int Unique ID for the payment (= part of primary key) NO -
Identifier nvarchar (500) An identifer for the payment like a booking number or invoice number YES -
Amount float Amount of the payment in the default currency as defined in TransactionCurrency YES -
ForeignAmount float If the payment was not in the default curreny as defined in TransactionCurrency, the amount of the payment in foreign curreny YES -
ForeignCurrency nvarchar (50) If the payment was not in the default curreny as defined in TransactionCurrency, the foreign currency of the payment YES -
PayerName nvarchar (500) Name of the person or institution paying the amount YES -
PayerAgentURI varchar (500) Link to the source for further infomations about the payer, e.g in the module DiversityAgents YES -
RecipientName nvarchar (500) Agent receiving the payment YES -
RecipientAgentURI varchar (500) Link to the source for further infomations about the recipient of the payment, e.g in the module DiversityAgents YES -
PaymentDate datetime Date of the payment YES -
PaymentDateSupplement nvarchar (50) Supplement to the date of the payment, e.g. if the original date is not a real date like ‘summer 1920’ or ‘1910 - 1912’ YES -
PaymentURI varchar (500) A link to an external administration system for the payment YES -
Notes nvarchar (MAX) Notes about the payment YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Transaction
Mar 19, 2025

Diversity Collection

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table

Column Data type Description
Code nvarchar (50) A text code that uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
ParentCode nvarchar (50) The code of the superior entry, if a hierarchy within the entries is necessary
ParentRelation nvarchar (50) Relation to parent entry, e.g. part of
Description nvarchar (500) Description of enumerated object, displayed in the user interface
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayEnable bit Enumerated objects can be hidden from the user interface if this attribute is set to false (= unchecked check box)
URL varchar (500) A link to further information about the enumerated object
InternalNotes nvarchar (500) Internal development notes about usage, definition, etc. of an enumerated object
Icon image A symbol representing this entry in the user interface
ModuleName varchar (50) If the enumerated entry is related to a DiversityWorkbench module or a related webservice, the name of the DiversityWorkbench module, e.g. DiversityCollEventSeriess
RowGUID uniqueidentifier -Default value: newsequentialid()

Table AnnotationType_Enum

The types of an annotation as used in table Annotation

Dependent tables:

  • Annotation

Table CollCircumstances_Enum

Circumstances of the occurence of the organisms

Dependent tables:

  • IdentificationUnit

Content

Code Description
bred animal born in captivity (domestic, zoo, or farm animales)
captivity wild animal or plant raised in captivity
cultivated cultivated in enclosed conditions (greenhouse plants, fungi, bacteria, etc. in laboratory or biotechnology conditions)
experiment material cultivated or treated under experimental conditions (including, e.g., infection experiments)
imported imported material of uncertain provenence (e.g. food items)
natural occurrence under natural conditions
planted planted in open agriculture, horticulture, or silviculture
unknown unknown circumstances of occurrence

Table CollCollectionImageType_Enum

The types of a collection, e.g. cupboard, drawer, box, rack etc.

Dependent tables:

  • CollectionImage

Content

Code Description
area area resp. section within a collection, e.g. within a insect case
image image of a collection, e.g. a insect case
plan Old plan optional including geometry of a collection

Table CollCollectionType_Enum

The types of a collection, e.g. cupboard, drawer, box, rack etc.

Dependent tables:

  • Collection
  • Content

Code Description DisplayText
area An area within a collection, e.g. within an insect display case area
box box box
collection A collection of objects collection
container container container
cupboard cupboard cupboard
department department department
drawer drawer drawer
freezer freezer freezer
fridge fridge fridge
hardware hardware hardware e.g. for sensor network
institution institution institution
location location location
radioactive Place where radioactive objects are stored radioactive
room room room
sensor A sensor for e.g. temperature or pests sensor
steel locker steel locker steel locker
subdivided container A container subdivided into chambers subdivided container
trap A trap for monitoring pest e.g. for IPM trap

Table CollDateCategory_Enum

The categories for the collection date

Dependent tables:

  • CollectionSpecimen

Table CollEventDateCategory_Enum

The categoies of the collection date

Dependent tables:

  • CollectionEvent

Content

Code Description
actual The given date is the real date
estimated The given date was estimated by the user
system The given date was generated by the system

Table CollEventImageType_Enum

The types of the images taken from a collection event

Dependent tables:

  • CollectionEventImage

Content

Code Description DisplayText ParentCode
aerial photography photography from an elevated position e.g. an aerial drone aerial photography
audio audio file related to an event sound
audio (for transcription) audio file of spoken comments related to an event that might be deleted after transcription into the database sound /recorded speech audio
biotope photography photography of a whole biotope where the specimen are observed resp. collected biotope photography
documentation a still image of a document or paperwork associated with an event, e. g. field books documentation
drawing, painting original line or color drawing of an event drawing, painting
image still image of any raster or vector format without any further information regarding the content type, e. g. graphic designs, plans and maps, vector graphics 2D, 3D models image
landscape photography photography of the landscape where the specimen are observed resp. collected landscape photography
map image of a map where the specimen are observed resp. collected map image
photograph photographic still image of an event; e. g. trap, trawl net photograph
supporting files text-xml or text-WKT encoded files, assigned to multimedia objects supporting files
video e. g. video file related to an event moving image

Table CollEventSeriesDescriptorType_Enum

The type of the Descriptors

Dependent tables:

  • CollectionEventSeriesDescriptor

Table CollEventSeriesImageType_Enum

The types of the images taken from a collection event series

Dependent tables:

  • CollectionEventSeriesImage

Content

Code Description DisplayText ParentCode
aerial photography photography from an elevated position e.g. an aerial drone aerial photography
audio audio record of e.g. the song of an observed bird sound
audio (for transcription) audio file of spoken comments related to an event or event series that might be deleted after transcription into the database sound /recorded speech audio
documentation a still image of a document or paperwork associated with an event series, e. g. field books documentation
drawing, painting original line or color drawing of an event series drawing, painting
image still image of any raster or vector format without any further information regarding the content type, e. g. graphic designs, plans and maps, vector graphics 2D, 3D models image
landscape photography photography of the landscape where the specimen are observed resp. collected landscape photography
map image of a map where the specimen are observed resp. collected map image
moving image e. g. video file related to an event series moving image
photograph photographic still image of an event series; e. g. trap, trawl net photograph
supporting files text-xml or text-WKT encoded files, assigned to multimedia objects supporting files

Table CollIdentificationCategory_Enum

The categories of an identification, e.g. determination, confirmation etc.

Dependent tables:

  • Identification

Content

Code Description
absence When nomenclatural type material has been used up in previous studies, or if a mixed collection contains e.g. several fungi but none fits the protologue
confirmation The examination confirms a previous identification
correction Correction of a misidentification supposedly due to a typing error.
determination The determination of the material results in a new identification or correction
dubious The material is assumed as dubiously belonging to the identified taxon or the observation is assumed as dubiously belonging to the identified taxon
expert assignment The assignment of occurrence data to a new taxon following expert opinion, without study of material
implicit The identification can be logically deduced from the type material, e.g. in the case of Yes/No type specimens.
negative The material is identified as not belonging to the identified taxon or the observation is verified as not belonging to the identified taxon
preference Assigning preference to an older determination over the most recent one. Differs from a confirmation only in that the object has not been re-examined. The choice is based on the expertise of the person effecting the earlier identification
renaming e.g. assigning a species to a new genus or a purely nomenclatural change
revision The correction of a former determination of the material
type annotation annotated as original material (e. g. syntype, paratype), e.g. done by a scientist by adding type labels to the material as part of a curatorial process
type designation designated as type material (i. e. lectotype, neotype, epitype or their duplicates; ICBN 2006, Art. 7.5, 7.10-11 + N2, Art. 9.7-11, 9.20, 9A, Art. 37.3; nomenclatural action undertaken by the person who is treating the nomenclature of the taxon)
type indication indicated as type material (ICBN 2006, Art. 37.1-4, 37A, Art. 7.5, Art. 24.3; any nomenclatural action, e. g. by the person who described the taxon, other than type designation)

Table CollIdentificationDateCategory_Enum

The categories of the identification date

Dependent tables:

  • Identification
  • Content

Code Description
actual The given date is the real date
collection date The collection date has been taken as the identification date
estimated The given date was estimated by the user
system The given date was generated by the system

Table CollIdentificationQualifier_Enum

The identification qualifiers, e.g. cf. spec., s.l. etc.

Dependent tables:

  • Identification

Content

Code Description
(select this for identifications that are certain)
? unspecified doubtful identification (aff. or cf., or applicable taxonomic rank not known)
aff. forma ‘affinis’ = similar to, but probably not the named forma
aff. gen. ‘affinis’ = similar to, but probably not the named genus
aff. sp. ‘affinis’ = similar to, but probably not the named species
aff. subsp. ‘affinis’ = similar to, but probably not the named subspecies
aff. var. ‘affinis’ = similar to, but probably not the named variety
agg. aggregate
cf. forma doubtful identification of forma or forma specialis. Example: ‘Ech. ferruginea cf. f. rubra’
cf. gen. doubtful genus identification. Examples: ‘cf. Abies’, ‘?Abies’
cf. hybrid doubtful identification of hybrid. Example: cf. Salix alba x fragilis
cf. sp. doubtful species identification (genus identification certain). Example: ‘Abies cf. alba’
cf. subsp. doubtful identification of subspecies. Example: ‘Abies alba cf. ssp. alba’
cf. var. doubtful identification of variety. Example: ‘Echinonema ferruginea cf. var. campestris’
s. l. sensu lato
s. str. sensu stricto
sp. only the genus is given, the information relates to a single, unspecified species
sp. nov. only the genus is given, it is assumed that the unidentified species is new
spp. only the genus is given, the information covers several unspecified species

Table CollLabelTranscriptionState_Enum

The states of the transcription of a label

Dependent tables:

  • CollectionSpecimen

Content

Code Description
complete all data from label transferred in database
curator review required curator for transcription / review required
extern review required extern curator for transcription / review required
final curator review specimen has been finally reviewed by curator
first curator review specimen has been reviewed by curator for first time
incomplete transcription started by technical staff
not started transcription not started

Table CollLabelType_Enum

The types of a label, e.g. handwritten, typed etc.

Dependent tables:

  • CollectionSpecimen

Content

Code Description DisplayText
handwriting all data in handwriting handwriting
mixed data typed with handwriting comments mixed
typed all data typed typed

Table CollMaterialCategory_Enum

The material categories of the specimen, e.g. slide, culture etc.

Dependent tables:

  • CollectionSpecimenPart
  • ProjectMaterialCategory

Content

Code Description DisplayText ParentCode
bones bones or skeleton from vertebrates bones preserved specimen
complete skeleton complete skeleton complete skeleton bones
cones cones of e.g. Gymnospermae, not stored together with the herbarium sheet cones preserved specimen
cultures living cultures of organisms cultures living specimen
DNA lyophilised DNA lyophilised DNA lyophilised DNA sample
DNA sample DNA sample DNA sample other specimen
drawing original line or color drawing drawing drawing or photograph
drawing or photograph A record describing a static visual representation (digital or physical) drawing or photograph medium
dried specimen dried specimen dried specimen preserved specimen
earth science specimen A record describing a geo-scientific object which is no pure mineral, rock or fossil specimen (but a mixture), or a geo-scientific specimen with unknown traits earth science specimen other specimen
egg egg, e.g. of a bird or insect egg other specimen
fossil bones fossil bones or skeleton from vertebrates fossil bones fossil specimen
fossil complete skeleton fossil complete skeleton of a vertrebrate fossil complete skeleton fossil bones
fossil incomplete skeleton fossil incomplete skeleton of a vertrebrate fossil incomplete skeleton fossil bones
fossil otolith fossil otolith of fishes fossil otolith fossil bones
fossil postcranial skeleton fossil postcranial skeleton of a vertrebrate fossil postcranial skeleton fossil bones
fossil scales fossil scales of fish fossil scales fossil specimen
fossil shell fossil shell of animal fossil shell fossil specimen
fossil single bones fossil single bones of a vertrebrate fossil single bones fossil bones
fossil skull fossil skull of a vertrebrate fossil skull fossil bones
fossil specimen A record describing a preserved specimen that is a fossil fossil specimen specimen
fossil tooth fossil tooth of an animal fossil tooth fossil bones
herbarium sheets capsules or sheets as stored in a botanical collection herbarium sheets dried specimen
human observation A record describing an output of a human observation process human observation observation
icones icones, images etc. stored in a biological collection icones drawing or photograph
incomplete skeleton incomplete skeleton incomplete skeleton bones
living specimen A record describing a specimen which is alive (not preserved) living specimen specimen
machine observation A record describing an output of a machine observation process machine observation observation
material sample A record describing the physical result of a sampling (or subsampling) event (sample either preserved or destructively processed) material sample other specimen
medium medium like sound recordings, videos, images and the like medium
micr. slide glass plate with specimen for microscopic study micr. slide other specimen
mineral specimen A record describing a preserved specimen which is a mineral mineral specimen other specimen
mould mould of animal mould fossil specimen
nest nest, e.g. of a bird or insect nest other specimen
observation observation observation
other specimen A record describing a specimen which is not indicated as preserved, living, fossil or mineral other specimen specimen
otolith otolith of fishes otolith bones
pelt pelt, skin or fur of an animal pelt preserved specimen
photogr. print photographic print (color or black/white) photogr. print drawing or photograph
photogr. slide image in the form of a photographic slide for projection photogr. slide drawing or photograph
pinned specimen pinned specimen, e.g. insects in a insect case pinned specimen dried specimen
postcranial skeleton postcranial skeleton postcranial skeleton bones
preserved specimen A record describing a preserved specimen (not living) preserved specimen specimen
SEM table table with specimen for Scanning electron microscopy SEM table other specimen
shell shell e.g. of a snail shell preserved specimen
single bones single bones single bones bones
skull skull of a vertebrate skull bones
sound sound recoding sound medium
specimen specimen stored in a collection specimen
TEM specimen specimen preparation for Transmission electron microscopy TEM specimen other specimen
thin section thin section thin section other specimen
tissue sample tissue sample tissue sample other specimen
tooth tooth of an animal tooth bones
trace trace e.g. footprints of an animal trace other specimen
trace fossil trace fossil of animal trace fossil fossil specimen
vial vial, flask or similar container vial preserved specimen

Table CollRetrievalType_Enum

The types data about organisms were retrieved

Dependent tables:

  • IdentificationUnit

Content

Code Description
human observation A record describing an output of a human observation process
literature A record describing an output of a literature research
machine observation A record describing an output of a machine observation process

Table CollSpecimenImageType_Enum

The type of an image of a specimen, e.g. label

Dependent tables:

  • CollectionSpecimenImage

Content

Code Description DisplayText ParentCode
audio e. g. audio file related to a specimen, observation or unit sound
audio (for transcription) e. g. audio file of spoken comments related to a specimen, observation or unit that might be deleted after transcription into the database sound /recorded speech audio
drawing original line or color drawing and painting of a specimen, observation or unit drawing, painting image
image still image of any raster or vector format without any further information regarding the content type, e. g. graphic designs, plans and maps, vector graphics 2D, 3D models image
label a still image of a document or paperwork associated with a specimen, observation or unit, e. g. herbarium label, file card documentation image
LM photograph photographic still image of a specimen, observation or unit from light microscopy LM photograph image
photograph photographic still image of a specimen, observation or unit; e. g. macro images of an object photograph
SEM image photographic still image of a specimen, observation or unit from scanning electron microscopy SEM photograph image
supporting files text-xml or text-WKT encoded files, assigned to multimedia objects supporting files
TEM image photographic still image of a specimen, observation or unit from transmission electron microscopy TEM photograph image
video e. g. video file related to an specimen, observation or unit moving image

Table CollSpecimenRelationType_Enum

Types of the relation between specimen

Dependent tables:

  • CollectionSpecimenRelation

Content

Code Description
Duplicate specimen or specimen part from the same location and time, designated by the same collector as such (may be one organism or not)
public database public database
Same location different specimens from the same location, but potentially different time and collector
Specimen part material originated from one specimen, e.g. dried material + cultured material or wet material + DNA or tissue sample

Table CollTaskMetricAggregation_Enum

The aggregation applied for retrieval of values, e.g. avg, max etc.

Dependent tables:

  • CollectionTaskMetric

Content

Code Description
avg the average value of a period
max the maximal value within a period
min the minimal value within a period
none no aggregation applied
range the difference between the maximal and minimal value within a period
sum the sum of values within a period

Table CollTaxonomicGroup_Enum

The taxonomic groups of the organisms

Dependent tables:

  • IdentificationUnit
  • ProjectTaxonomicGroup

Content

Code Description DisplayText ParentCode
alga alga alga
amphibian amphibian amphibian vertebrate
animal Animalia (= Metazoa) animal
artefact An item made or given shape by humans, such as a tool or a work of art artefact
arthropod Arthropoda: insects, spiders, crabs etc. arthropod evertebrate
bacterium bacteria/prokaryotic bacterium
bird bird bird vertebrate
bryophyte Marchantiomorpha (liverworts), Anthocerotophyta (hornworts) and Bryophyta (mosses) bryophyte
cnidaria Cnidaria: sea anemones, corals, jellyfish, sea pens, hydra cnidaria evertebrate
Coleoptera Coleoptera Coleoptera insect
Diptera Diptera Diptera insect
echinoderm Echinodermata: sea urchins, starfish, and their allies echinoderm evertebrate
evertebrate Animalia (= Metazoa) excl. Chordata evertebrate animal
fish fish fish vertebrate
fungus Eumycota: mushrooms, sac fungi, yeast, molds, rusts, smuts, etc. fungus
gall growth modification or deformation of plant tissue or fungal plectenchyma, induced by a different organism gall
Heteroptera Heteroptera Heteroptera insect
Hymenoptera Hymenoptera Hymenoptera insect
insect Hexapoda: insects, springtails, diplurans, and proturans insect arthropod
Lepidoptera Lepidoptera Lepidoptera insect
lichen Lichenized Eumycota lichen
mammal mammal mammal vertebrate
mineral A record describing a preserved specimen which is a mineral mineral
mollusc Mollusca: Snails, clams, mussels, squids, octopi, chitons, and tusk shells mollusc evertebrate
myxomycete Myxomycota slime mould
other other/anorganic other
plant Lycophytes, ferns and seedplants plant
reptile reptile reptile vertebrate
rock A record describing a preserved specimen which is a rock rock
soil soil soil
soil horizon soil horizon soil horizon soil
spider Spider: Including Araneae (Mesothelae, Mygalomorphae and Araneomorphae) spider arthropod
unknown unknown group unknown
vertebrate Chordata vertebrate animal
virus virus virus

Table CollTransactionType_Enum

The types of the transactions of the specimen, e.g. loan, exchange

Dependent tables:

  • Transaction

Content

Code Description
embargo Temporary data embargo for specimen that should not be published within the specified period
exchange Exchange of specimens between e.g. collections
forwarding a forwarding of specimens of a loan to another institution
gift A gift of specimens to e.g. a collection
inventory An inventory of e.g. a collection
loan A temporary loan of specimens of a collection to e.g. another collection
permanent loan A permanent loan of specimens of a collection to e.g. another collection
permit permit or certificate for the collection of specimen
purchase A purchase of specimens by a collection
regulation a regulation, provisio or stipulation e.g. in the context of the Nagoya protocoll
removal the removal of specimens from an institution, e.g. by damage, loss etc.
return a partial return of a loan
transaction group the superior dataset for a group of transactions
warning A warning e.g. against biocides in samples

Table CollTypeStatus_Enum

The type statuses of the identifications, e.g. Isotype

Dependent tables:

  • Identification

Content

Code Description
allolectotype A paralectotype specimen that is the opposite sex of the lectotype. The term is not regulated by the ICZN. [Zoo.]
alloneotype A paraneotype specimen that is the opposite sex of the neotype. The term is not regulated by the ICZN. [Zoo.]
allotype A paratype specimen designated from the type series by the original author that is the opposite sex of the holotype. The term is not regulated by the ICZN. [Zoo.]
conserved type The one specimen or other element conserved as type for a name of a subdivision of a genus or of an infraspecific taxonand listed in ICN, App. III and IV (typ. cons.)
cotype A deprecated term no longer recognized in the ICZN; formerly used for either syntype or paratype [see ICZN Recommendation 73E]. [Zoo.]
epitype An epitype is a specimen or illustration selected to serve as an interpretative type when any kind of holotype, lectotype, etc. is demonstrably ambiguous and cannot be critically identified for purposes of the precise application of the name of a taxon (see Art. ICBN 9.7, 9.18). An epitype supplements, rather than replaces existing types. [Bot./Bio.]
ex-Epitype A strain or cultivation derived from epitype material. Ex-types are not regulated by the botanical or zoological code. [Bot.]
ex-Holotype A strain or cultivation derived from holotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
ex-Isotype A strain or cultivation derived from isotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
ex-Lectotype A strain or cultivation derived from lectotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
ex-Neotype A strain or cultivation derived from neotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
ex-Paratype A strain or cultivation derived from paratype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
ex-Syntype A strain or cultivation derived from neotype material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
ex-Type A strain or cultivation derived from some kind of type material. Ex-types are not regulated by the botanical or zoological code. [Zoo./Bot.]
hapantotype One or more preparations of directly related individuals representing distinct stages in the life cycle, which together form the type in an extant species of protistan [ICZN Article 72.5.4]. A hapantotype, while a series of individuals, is a holotype that must not be restricted by lectotype selection. If a hapantotype is found to contain individuals of more than one species, however, components may be excluded until it contains individuals of only one species [ICZN Article 73.3.2]. [Zoo.]
holotype The one specimen or other element used or designated by the original author at the time of publication of the original description as the nomenclatural type of a species or infraspecific taxon. A holotype may be ’explicit’ if it is clearly stated in the originating publication or ‘implicit’ if it is the single specimen proved to have been in the hands of the originating author when the description was published. [Zoo./Bot./Bio.]
iconotype A drawing or photograph (also called ‘phototype’) of a type specimen. Note: the term “iconotype” is not used in the ICBN, but implicit in, e. g., ICBN Art. 7 and 38. [Zoo./Bot.]
isoepitype a duplicate of an epitype
isolectotype A duplicate of a lectotype, compare lectotype. [Bot.]
isoneotype A duplicate of a neotype, compare neotype. [Bot.]
isoparatype A duplicate of a paratype
isosyntype A duplicate of a syntype, compare isotype = duplicate of holotype. [Bot.]
isotype An isotype is any duplicate of the holotype (i. e. part of a single gathering made by a collector at one time, from which the holotype was derived); it is always a specimen (ICBN Art. 7). [Bot.]
lectotype A specimen or other element designated subsequent to the publication of the original description from the original material (syntypes or paratypes) to serve as nomenclatural type. Lectotype designation can occur only where no holotype was designated at the time of publication or if it is missing (ICBN Art. 7, ICZN Art. 74). [Zoo./Bot.] – Note: the BioCode defines lectotype as selection from holotype material in cases where the holotype material contains more than one taxon [Bio.].
neotype A specimen designated as nomenclatural type subsequent to the publication of the original description in cases where the original holotype, lectotype, all paratypes and syntypes are lost or destroyed, or suppressed by the (botanical or zoological) commission on nomenclature. In zoology also called “Standard specimen” or “Representative specimen”. [Zoo./Bot./Bio.]
not a type For specimens erroneously labelled as types an explicit negative statement may be desirable. [General]
original material Specimens and illustrations indicated in the protologue of a name (see ICBN Art. 9 Note 2 for details)
paralectotype All of the specimens in the syntype series of a species or infraspecific taxon other than the lectotype itself. Also called “lectoparatype”. [Zoo.]
paraneotype All of the specimens in the syntype series of a species or infraspecific taxon other than the neotype itself. Also called “neoparatype”. [Zoo.]
paratype All of the specimens in the type series of a species or infraspecific taxon other than the holotype (and, in botany, isotypes). Paratypes must have been at the disposition of the author at the time when the original description was created and must have been designated and indicated in the publication. Judgment must be exercised on paratype status, for only rarely are specimens explicitly cited as paratypes, but usually as “specimens examined,” “other material seen”, etc. [Zoo./Bot.]
plastoholotype A copy or cast of holotype material (compare Plastotype).
plastoisotype A copy or cast of isotype material (compare Plastotype).
plastolectotype A copy or cast of lectotype material (compare Plastotype).
plastoneotype A copy or cast of neotype material (compare Plastotype).
plastoparatype A copy or cast of paratype material (compare Plastotype).
plastosyntype A copy or cast of syntype material (compare Plastotype).
plastotype A copy or cast of type material, esp. relevant for fossil types. Not regulated by the botanical or zoological code (?). [Zoo./Bot.]
secondary type A referred, described, measured or figured specimen in the original publication (including a neo/lectotypification publication) that is not a primary type.
supplementary type A referred, described, measured or figured specimen in a revision of a previously described taxon.
syntype One of the series of specimens used to describe a species or infraspecific taxon when neither a single holotype by the original author, nor a lectotype in a subsequent publication has been designated. The syntypes collectively constitute the name-bearing type. [Zoo./Bot.]
topotype One or more specimens collected at the same location as the type series (type locality), regardless of whether they are part of the type series. Topotypes are not regulated by the botanical or zoological code. Also called “locotype”. [Zoo./Bot.]
type a) A specimen designated or indicated any kind of type of a species or infraspecific taxon. If possible more specific type terms (holotype, syntype, etc.) should be applied. b) the type name of a name of higher rank for taxa above the species rank. [General]
typotype the specimen used to prepare an illustration where the latter is the type

Table CollUnitRelationType_Enum

The type of relation between organisms within one specimen, e.g. growing on

Dependent tables:

  • IdentificationUnit

Content

Code Description
Association in association with (unspecific statement if no further information about interaction b/w 2 organisms is available)
Child of child association (i.e. in the literal genetical sense, not in an abstract sense)
Endophytic in endophytic organism growing in plants without causing symptoms (possibly mutualistic or opportunistic parasite)
Found on Organism found on 2nd organism
Gall inducing Growth movement or swelling growth of (pseudo-)tissue or organ of a host organism caused by an organism.
Growing on substrate statement: organism growing on 2nd organism, living stages directly observed (i.e. assoc. not due to diaspores alone)
Isolated from substrate statement: organism isolated from 2nd organism, no living stages observed (i.e. possibly due to surface contamination)
Lichenization mutualistic symbiosis between a fungus and algae (= 2nd organism)
Mutant of A mutant of the parent organism
Mutualism mutualistic symbiosis, both partners profit from each other
Mycorrhiza of mycorrhizal association of a fungus with a plant (= 2nd organism)
Parasitic (accid.) parasitic on an ‘accidential host’ (in the sense of Nannfeldt): with strong infection pressure, another organism growing between infected organisms may become infected.
Parasitic (facul.) facultatively parasitic on host (= 2nd organism)
Parasitic (oblig.) obligately parasitic on host (= 2nd organism)
Parasitic (quest.) questionably parasitic on host (= 2nd organism), parasitic interaction is presumed, but doubtful/unverified
Parasitic on the taxon is parasitizing its host (regardless of type, i.e. holo-/meta-/hemi-biotrophic, or pertho-/necrotrophic)
Parent/Child parent/child association (i.e. in the literal genetical sense, not in an abstract sense)
Part of belongs to the same organism resp. unit, e.g. a branch is part of a tree
Pollinator of organism 1 is the pollinator of a plant (organism 2)
Predator/Food organism 1 is the predator of organism 2 (i. e. 2 is food of 1)
Saprophytic on organism growing saprophytic on 2nd organism, living stages directly observed (i.e. assoc. not due to diaspores alone)
Sibling both organisms are siblings (have the same parents)

Table EntityAccessibility_Enum

The type of accessibility of database objects within a certain context

Dependent tables:

  • EntityUsage

Table EntityContext_Enum

The context in which the application is used, e.g. collection - administration, field-mapping

Dependent tables:

  • EntityRepresentation
  • EntityUsage

Table EntityDetermination_Enum

The way a value of an entry is determined, e.g. calculated, defined by the user etc.

Dependent tables:

  • EntityUsage

Table EntityLanguageCode_Enum

The codes for the languages used for the entities

Dependent tables:

  • EntityRepresentation

Table EntityUsage_Enum

The usage of an entity, e.g. hidden, readonly


Table EntityVisibility_Enum

Type of visibility of an entity as used in table EntityUsage

Dependent tables:

  • EntityUsage

Table LanguageCode_Enum

The codes for the languages

Content

Code DisplayText
af Afrikaans
ar Arabisch
az Aserbaidschanisch
be Belarussisch
bg Bulgarisch
ca Katalanisch
cs Tschechisch
da Dänisch
de Deutsch
el Griechisch
en Englisch
es Spanisch
et Estnisch
eu Baskisch
fa Farsi
fi Finnisch
fo Färingisch
fr Französisch
gl Galizisch
gu Gujarati
he Hebräisch
hi Hindi
hr Kroatisch
hu Ungarisch
hy Armenisch
id Indonesisch
is Isländisch
it Italienisch
ja Japanisch
ka Georgisch
kk Kasachisch
kn Kannada
ko Koreanisch
ky Kirgisisch
lt Litauisch
lv Lettisch
mk Mazedonisch
mn Mongolisch
mr Marathi
ms Malaiisch
nl Niederländisch
no Norwegisch
pa Punjabi
pl Polnisch
pt Portugiesisch
ro Rumänisch
ru Russisch
sa Sanskrit
sk Slowakisch
sl Slowenisch
sq Albanisch
sv Schwedisch
sw Swahili
ta Tamil
te Telugu
th Thai
tr Türkisch
tt Tatarisch
uk Ukrainisch
ur Urdu
uz Usbekisch
vi Vietnamesisch

Table MeasurementUnit_Enum

The measurement units, e.g. m


Table ParameterValue_Enum

Distinct values for a parameter of a method

Depending on:

  • Parameter

Table PropertyType_Enum

The types of a Property, e.g. Chronostratigraphy

Dependent tables:

  • Property

Table TaskDateType_Enum

The type of a task, e.g. freezing etc.

Dependent tables:

  • Task

Table TaskModuleType_Enum

The type of a task, e.g. freezing etc.

Dependent tables:

  • Task

Table TaskType_Enum

The type of a task, e.g. freezing etc.

Dependent tables:

  • Task
May 3, 2024

Diversity Collection

VIEWS

The following objects are not included:

  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

View AnnotationEvent

Annotations linked to table CollectionEvent

Column Data type Description Nullable
AnnotationID int ID of the annotation (primary key) NO
CollectionEventID int ID of the collection event. Refers to PK of table CollectionEvent NO
ReferencedAnnotationID int If an annotation refers to another annotation, the ID of the referred annotation YES
AnnotationType nvarchar (50) The type of the annotation as defined in AnnotationType_Enum, e.g. Reference NO
Title nvarchar (50) Title of the annotation YES
Annotation nvarchar (MAX) The annotation entered by the user NO
URI varchar (255) The complete URI address of a resource related to the annotation. May be link to a module, e.g. for the annotation type reference YES
ReferenceDisplayText nvarchar (500) The title of the reference. If the entry is linked to an external module like DiversityReferences, the cached display text of the referenced data set YES
ReferenceURI varchar (255) If the entry is linked to an external module like DiversityReferences, the link to the referenced data set YES
SourceDisplayText nvarchar (500) The name of the source. If the entry is linked to an external module like DiversityAgents, the cached display text of the referenced data set YES
SourceURI varchar (255) If the entry is linked to an external module like DiversityAgents, the link to the referenced data set YES
IsInternal bit If an annotation is restricted to authorized users of the database YES

Depending on:

  • Annotation

View AnnotationPart

Annotations linked to table CollectionSpecimenPart

Column Data type Description Nullable
AnnotationID int ID of the annotation (primary key) NO
SpecimenPartID int ID of the collection specimen part. Refers to PK of table CollectionSpecimenPart NO
ReferencedAnnotationID int If an annotation refers to another annotation, the ID of the referred annotation YES
AnnotationType nvarchar (50) The type of the annotation as defined in AnnotationType_Enum, e.g. Reference NO
Title nvarchar (50) Title of the annotation YES
Annotation nvarchar (MAX) The annotation entered by the user NO
URI varchar (255) The complete URI address of a resource related to the annotation. May be link to a module, e.g. for the annotation type reference YES
ReferenceDisplayText nvarchar (500) The title of the reference. If the entry is linked to an external module like DiversityReferences, the cached display text of the referenced data set YES
ReferenceURI varchar (255) If the entry is linked to an external module like DiversityReferences, the link to the referenced data set YES
SourceDisplayText nvarchar (500) The name of the source. If the entry is linked to an external module like DiversityAgents, the cached display text of the referenced data set YES
SourceURI varchar (255) If the entry is linked to an external module like DiversityAgents, the link to the referenced data set YES
IsInternal bit If an annotation is restricted to authorized users of the database YES

Depending on:

  • Annotation

View AnnotationSpecimen

Annotations linked to table CollectionSpecimen

Column Data type Description Nullable
AnnotationID int ID of the annotation (primary key) NO
CollectionSpecimenID int ID of the collection specimen. Refers to PK of table CollectionSpecimen NO
ReferencedAnnotationID int If an annotation refers to another annotation, the ID of the referred annotation YES
AnnotationType nvarchar (50) The type of the annotation as defined in AnnotationType_Enum, e.g. Reference NO
Title nvarchar (50) Title of the annotation YES
Annotation nvarchar (MAX) The annotation entered by the user NO
URI varchar (255) The complete URI address of a resource related to the annotation. May be link to a module, e.g. for the annotation type reference YES
ReferenceDisplayText nvarchar (500) The title of the reference. If the entry is linked to an external module like DiversityReferences, the cached display text of the referenced data set YES
ReferenceURI varchar (255) If the entry is linked to an external module like DiversityReferences, the link to the referenced data set YES
SourceDisplayText nvarchar (500) The name of the source. If the entry is linked to an external module like DiversityAgents, the cached display text of the referenced data set YES
SourceURI varchar (255) If the entry is linked to an external module like DiversityAgents, the link to the referenced data set YES
IsInternal bit If an annotation is restricted to authorized users of the database YES

Depending on:

  • Annotation

View AnnotationUnit

Annotations linked to table IdentificationUnit

Column Data type Description Nullable
AnnotationID int ID of the annotation (primary key) NO
IdentificationUnitID int ID of the IdentificationUnit. Refers to PK of table IdentificationUnit NO
ReferencedAnnotationID int If an annotation refers to another annotation, the ID of the referred annotation YES
AnnotationType nvarchar (50) The type of the annotation as defined in AnnotationType_Enum, e.g. Reference NO
Title nvarchar (50) Title of the annotation YES
Annotation nvarchar (MAX) The annotation entered by the user NO
URI varchar (255) The complete URI address of a resource related to the annotation. May be link to a module, e.g. for the annotation type reference YES
ReferenceDisplayText nvarchar (500) The title of the reference. If the entry is linked to an external module like DiversityReferences, the cached display text of the referenced data set YES
ReferenceURI varchar (255) If the entry is linked to an external module like DiversityReferences, the link to the referenced data set YES
SourceDisplayText nvarchar (500) The name of the source. If the entry is linked to an external module like DiversityAgents, the cached display text of the referenced data set YES
SourceURI varchar (255) If the entry is linked to an external module like DiversityAgents, the link to the referenced data set YES
IsInternal bit If an annotation is restricted to authorized users of the database YES

Depending on:

  • Annotation

View CollectionAgent_Core

Table CollectionAgent restricted to available datasets

Column Data type Description Nullable
CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key) NO
CollectorsName nvarchar (255) Name of the Collector NO
CollectorsAgentURI varchar (255) The URI of the Agent, e.g. as stored within the module DiversityAgents YES
CollectorsSequence datetime2 The order of collectors in a team. Automatically set by the database system YES
CollectorsNumber nvarchar (50) Number assigned to a specimen or a batch of specimens by the collector during the collection event (= ‘field number’) YES
Notes nvarchar (MAX) Notes on the collector, e.g. if the name is uncertain YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES

Depending on:

  • CollectionAgent
  • CollectionSpecimenID_Available

View CollectionEvent_Core2

List for accessible content of table CollectionEvent with preformated date column

Column Data type Description Nullable
CollectionEventID int Unique ID for the table CollectionEvent (= primary key) NO
Version int The version of the data set. Automatically set by the system. NO
SeriesID int The ID of the related expedition. Relates to the PK of the table CollectionExpedition (foreign key). YES
CollectorsEventNumber nvarchar (50) Number assigned to a collection event by the collector (= ‘field number’) YES
CollectionDate datetime The cached date of the collection event calulated from the entries in CollectionDay, -Month and -Year. YES
CollectionDay tinyint The day of the date of the event or when the collection event started YES
CollectionMonth tinyint The month of the date of the event or when the collection event started YES
CollectionYear smallint The year of the date of the event or when the collection event started YES
CollectionEndDay tinyint The day of the date of the event or when the collection event ended YES
CollectionEndMonth tinyint The month of the date of the event or when the collection event ended YES
CollectionEndYear smallint The year of the date of the event or when the collection event ended YES
CollectionDateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event comprises a period. The time of the event, if necessary. YES
CollectionDateCategory nvarchar (50) Category of the date of the identification e.g. “system”, “estimated” (= foreign key, see in table CollEventDateCategory_Enum) YES
CollectionTime varchar (50) The time of the event or when the collection event started YES
CollectionTimeSpan varchar (50) The time span e.g. in seconds of the collection event YES
LocalityDescription nvarchar (MAX) Locality description of the locality exactly as written on the original label (i.e. without corrections during data entry) YES
LocalityVerbatim nvarchar (MAX) Locality as given in historical context, documents and labels YES
HabitatDescription nvarchar (MAX) Geo-ecological description of the locality exactly as written on the original label (i.e. without corrections during data entry) YES
ReferenceTitle nvarchar (255) The title of the publication where the collection event was published. Note that this is only a cached value where ReferenceURI is present YES
ReferenceDetails nvarchar (50) The exact location within the reference, e.g. pages, plates YES
ReferenceURI varchar (255) URI (e.g. LSID) of the source publication where the collection event is published, may e.g. refer to the module DiversityReferences YES
CollectingMethod nvarchar (MAX) Description of the method used for collecting the samples, e.g. traps, moist chambers, drag net YES
Notes nvarchar (MAX) Notes on the collection event YES
CountryCache nvarchar (50) The country where the collection event took place. Cached value derived from an entry in CollectionEventLocalisation YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
DataWithholdingReasonDate nvarchar (50) The reason for withholding the collection date YES
CollectionDate_YMD varchar (94) - YES

Depending on:

  • CollectionEvent
  • CollectionEventID_AvailableNotReadOnly

View CollectionEventID_CanEdit

List for CollectionEventID (PK of table CollectionEvent) a user can edit

Column Data type Description Nullable
CollectionEventID int Refers to the ID of table CollectionEvent (= foreign key and part of primary key) YES

Depending on:

  • CollectionProject
  • CollectionSpecimen
  • ProjectUser

View CollectionEventID_UserAvailable

List for CollectionEventID (PK of table CollectionEvent) a user has access to

Column Data type Description Nullable
CollectionEventID int Refers to the ID of table CollectionEvent (= foreign key and part of primary key) YES

Depending on:

  • CollectionProject
  • CollectionSpecimen
  • ProjectUser

View CollectionEventLocalisation_Core

Content of table CollectionEventLocalisation excluding log columns and geography

Column Data type Description Nullable
CollectionEventID int Refers to the ID of CollectionEvent (= foreign key and part of primary key) NO
LocalisationSystemID int Refers to the ID of LocalisationSystem (= foreign key and part of primary key) NO
Location1 nvarchar (255) Either a named location selected from a thesaurus (e.g. ‘Germany, Bavaria, Kleindingharting’) or altitude range or other values (e. g. 100-200 m) YES
Location2 nvarchar (255) Corresponding value to Location1 e.g. ID or URI of gazetteer or thesaurus YES
LocationAccuracy nvarchar (50) The accuracy of the determination of this locality YES
LocationNotes nvarchar (MAX) Notes on the location YES
DeterminationDate smalldatetime Date of the determination of the geographical localisation YES
DistanceToLocation varchar (50) Distance from the specified place to the real location of the collection site (m) YES
DirectionToLocation varchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north) YES
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES
AverageAltitudeCache float Calculated altitude as parsed from the location fields YES
AverageLatitudeCache float Calculated latitude as parsed from the location fields YES
AverageLongitudeCache float Calculated longitude as parsed from the location fields YES
RecordingMethod nvarchar (500) The method or device used for the recording of the localisation YES
Geography nvarchar (MAX) The geography of the localisation YES

Depending on:

  • CollectionEventLocalisation

View CollectionSpecimen_Core2

List of accessible dataset of table CollectionSpecimen containing additional data from table CollectionEvent

Column Data type Description Nullable
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key) NO
Version int The version of the data set. Automatically set by the system. NO
CollectionEventID int Unique ID for the table CollectionEvent (= primary key) YES
AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752” YES
AccessionDate datetime The date of the accession calculated from the entries in AccessionDay, -Month and -Year YES
AccessionDay tinyint The day of the date when the specimen was acquired in the collection YES
AccessionMonth tinyint The month of the date when the specimen was acquired in the collection YES
AccessionYear smallint The year of the date when the specimen was acquired in the collection YES
AccessionDateSupplement nvarchar (255) Verbal or additional accession date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
AccessionDateCategory nvarchar (50) Category of the date of the accession e.g. “system”, “estimated” (= foreign key, see in table CollDateCategory_Enum) YES
DepositorsName nvarchar (255) The name of the depositor(s) (person or organization responsible for deposition). Where entire collections are deposited, this should also contain the collection name (e.g. ‘Herbarium P. Döbbler’) YES
DepositorsAgentURI varchar (255) The URI of the depositor(s) (person or organization responsible for deposition) YES
DepositorsAccessionNumber nvarchar (50) Accession number of the specimen within the previous or original collection, e.g. ‘D-23948’ YES
LabelTitle nvarchar (MAX) The title of the label e.g. for printing labels. YES
LabelType nvarchar (50) Printed, typewritten, typewritten with handwriting added, entirely in handwriting, etc. YES
LabelTranscriptionState nvarchar (50) The state of the transcription of a label into the database: ‘Not started’, ‘incomplete’, ‘complete’ YES
LabelTranscriptionNotes nvarchar (255) User defined notes on the transcription of the label into the database YES
ExsiccataURI varchar (255) If specimen is an exsiccata: The URI of the exsiccata series, e.g. as stored within the DiversityExsiccata module YES
ExsiccataAbbreviation nvarchar (255) If specimen is an exsiccata: Standard abbreviation of the exsiccata (not necessarily a unique identifier; editors or publication places may change over time) YES
OriginalNotes nvarchar (MAX) Notes found on the label of the specimen by the original collector or from a later revision YES
AdditionalNotes nvarchar (MAX) Additional notes made by the editor of the specimen record, e.g. ‘doubtful identification/locality’ YES
ReferenceTitle nvarchar (255) The title of the publication where the collection event was published. Note that this is only a cached value where ReferenceURI is present YES
ReferenceURI varchar (255) URI (e.g. LSID) of the source publication where the collection event is published, may e.g. refer to the module DiversityReferences YES
Problems nvarchar (255) Description of a problem which occurred during data editing. Typically these entries should be deleted after help has been obtained. Do not enter scientific problems here; use AdditionalNotes for such permanent problems! YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
CollectionDate varchar (94) The cached date of the collection event calulated from the entries in CollectionDay, -Month and -Year. YES
Locality nvarchar (MAX) LocalityDescription from table CollectionEvent YES
Habitat nvarchar (MAX) HabitatDescription from table CollectionEvent YES
InternalNotes nvarchar (MAX) Internal notes which should not be published e.g. on websites YES
ExternalDatasourceID int An ID to identify an external data collection of the collected specimen (primary key, the ID has no meaning outside of the DiversityWorkbench system) YES
ExternalIdentifier nvarchar (100) The identifier of the external specimen as defined in the external data source YES
LogCreatedWhen datetime Point in time when this data set was created YES
LogCreatedBy nvarchar (50) Name of the creator of this data set YES
LogUpdatedWhen datetime Point in time when this data set was updated last YES
LogUpdatedBy nvarchar (50) Name of the person to update this data set last YES

Depending on:

  • CollectionEvent
  • CollectionSpecimen
  • CollectionSpecimenID_Available
  • UserProxy

View CollectionSpecimenID_Available

CollectionSpecimenIDs a user has access to including CollectionSpecimenIDs not linked to a project

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO

Depending on:

  • CollectionProject
  • CollectionSpecimen
  • ProjectUser

View CollectionSpecimenID_AvailableReadOnly

CollectionSpecimenIDs a user has read only access to including CollectionSpecimenIDs from locked projects

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO

Depending on:

  • CollectionProject
  • CollectionSpecimenID_Locked
  • ProjectUser

View CollectionSpecimenID_CanEdit

CollectionSpecimenIDs a user has access to excluding those with read only access

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO

Depending on:

  • CollectionProject
  • ProjectUser

View CollectionSpecimenID_Locked

CollectionSpecimenIDs of locked projects

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO

Depending on:

  • CollectionProject
  • ProjectProxy

View CollectionSpecimenID_ReadOnly

CollectionSpecimenIDs a user has read only access to including CollectionSpecimenIDs from locked projects

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO

Depending on:

  • CollectionProject
  • CollectionSpecimenID_Locked
  • ProjectUser

View CollectionSpecimenID_UserAvailable

CollectionSpecimenIDs a user has access to including CollectionSpecimenIDs not linked to a project

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO

Depending on:

  • CollectionProject
  • CollectionSpecimen
  • ProjectUser

View CollectionSpecimenPart_Core2

Content of table CollectionSpecimenPart restricted to those avaliable for a user including the collection hierarchy

Column Data type Description Nullable
Collection nvarchar (1158) Hierarchy of the collection separated by " " followed by StorageLocation resp. AccessionNumber and Sublabel
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key). NO
DerivedFromSpecimenPartID int SpecimenPartID of the specimen from which the current specimen is derived from YES
PreparationMethod nvarchar (MAX) The method used for the preparation of the part of the specimen, e.g. the inoculation method for cultures YES
PreparationDate datetime Point in time when the part was preparated e.g when it was separated from the source object YES
AccessionNumber nvarchar (50) Accession number of the part of the specimen within the collection, if it is different from the accession number of the specimen as stored in the table CollectionSpecimen, e.g. “M-29834752” YES
PartSublabel nvarchar (50) The label for a part of a specimen, e.g. “cone”, or a number attached to a duplicate of a specimen YES
CollectionID int ID of the collection as stored in table Collection (= foreign key, see table Collection) NO
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum) NO
StorageLocation nvarchar (255) A code identifying the place where the specimen is stored within the collection. Frequently the accepted scientific name is used as storage location code. YES
StorageContainer nvarchar (500) The container in which the part is stored YES
Stock float Number of stock units, if the specimen is stored in separated units e.g. several boxes or vessels (max. 255) YES
StockUnit nvarchar (50) If empty, the stock is given as a count, else it contains the unit in which stock is expressed, e.g. µl, ml, kg etc. YES
Notes nvarchar (MAX) Notes on the storage of the sample YES
PartAccessionNumber nvarchar (50) - YES

Depending on:

  • CollectionHierarchyAll
  • CollectionSpecimenID_UserAvailable
  • CollectionSpecimenPart

View CollectionSpecimenRelationInternal

List of specimen with a relation to a specimen within the same database or where another specimen within the database has defined a relation to

Column Data type Description Nullable
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key) YES
RelatedSpecimen_CollectionSpecimenID int CollectionSpecimenID of the related specimen YES
RelatedSpecimenDisplayText nvarchar (255) The name of a related specimen as shown e.g. in a user interface YES
RelationType nvarchar (50) Type of the relation between the specimen (= foreign key, see table CollRelationType_Enum) YES
RelatedSpecimenCollectionID int ID of the Collection as stored in table Collection (= foreign key, see table Collection) YES
RelatedSpecimenDescription nvarchar (MAX) Description of the related specimen YES
Notes nvarchar (MAX) Notes on the relation to the specimen YES

Depending on:

  • baseURL
  • CollectionSpecimen
  • CollectionSpecimenRelation

View CollectionSpecimenRelationInvers

Content of function CollectionSpecimenRelationInversList: List of specimen where another specimen within the database has defined a relation to

Column Data type Description Nullable
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key) NO
RelatedSpecimenCollectionSpecimenID int The CollectionSpecimenID of the dataset that refers to the current dataset NO
RelatedSpecimenAccessionNumber nvarchar (50) The AccessionNumber of the dataset that refers to the current dataset YES
RelationType nvarchar (50) Type of the relation between the specimen (= foreign key, see table CollRelationType_Enum) YES
RelatedSpecimenCollectionID int ID of the Collection as stored in table Collection (= foreign key, see table Collection) YES
Notes nvarchar (MAX) Notes on the relation to the specimen YES

Depending on:

  • CollectionSpecimenRelationInversList

View CollectionSpecimenTransactionRequest

PK and supplementary columns of Table CollectionSpecimenTransaction with TransactionType loan or request the user has access to as a CollectionManager or the user has created and access to as a CollectionRequester

Column Data type Description Nullable
CollectionSpecimenID int Refers to ID of CollectionSpecimen (= foreign key and part of primary key) NO
TransactionID int Unique ID for the table Transaction (= foreign key and part of primary key) NO
SpecimenPartID int Optional: If the data set is related to a part of a specimen, the ID of a related part (= foreign key, see table CollectionSpecimenPart) NO
IsOnLoan bit True, if a specimen is on loan YES
LogInsertedBy nvarchar (50) Name of user to first enter (typ or import) the data. YES
LogInsertedWhen smalldatetime Point in time when the data was first entered (typed or imported) into this database. YES

Depending on:

  • CollectionSpecimenTransaction
  • TransactionRequest

View FirstLinesIdentification

Content of table Identification restricted to last identification of a IdentificationUnit

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO
IdentificationSequence smallint The sequence of the identifications. The last identification (having the highest sequence) is regarded as valid NO
IdentificationDate datetime The date of the identification calculated from the entries in IdentificationDay, -Month and -Year YES
IdentificationDay tinyint The day of the identification YES
IdentificationMonth tinyint The month of the identification YES
IdentificationYear smallint The year of the identification. The year may be empty if only the day or month are known. YES
IdentificationDateSupplement nvarchar (255) Verbal or additional identification date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
IdentificationDateCategory nvarchar (50) Category of the date of the identification e.g. “system”, “estimated” (= foreign key, see in table CollDateCategory_Enum) YES
VernacularTerm nvarchar (255) Name or term other than a taxonomic (= scientific) name, e.g. ‘pine’, ’limestone’, ‘conifer’, ‘hardwood’ YES
TaxonomicName nvarchar (255) Valid name of the species (including the taxonomic author where available). Example: ‘Rosa canina L.’ YES
NameURI varchar (255) The URI of the taxonomic name, e.g. as provided by the module DiversityTaxonNames. YES
IdentificationCategory nvarchar (50) Category of the identification e.g. ‘determination’, ‘confirmation’, ‘absence’ (= foreign key, see table CollIdentificationCategory_Enum) YES
IdentificationQualifier nvarchar (50) Qualification of the identification e.g. “cf.”," aff.", “sp. nov.” (= foreign key, see table CollIdentificationQualifier_Enum) YES
TypeStatus nvarchar (50) If identification unit is type of a taxonomic name: holotype, syntype, etc. (= foreign key, see table CollTypeStatus_Enum) YES
TypeNotes nvarchar (MAX) Notes on the typification of this specimen YES
Notes nvarchar (MAX) User defined notes, e.g. the reason for a re-determination / change of the name, etc. YES
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES
LogCreatedWhen datetime Point in time when this data set was created YES
LogCreatedBy nvarchar (50) Name of the creator of this data set YES
LogUpdatedWhen datetime Point in time when this data set was updated last YES
LogUpdatedBy nvarchar (50) Name of the person to update this data set last YES

Depending on:

  • FirstLinesIdentificationUnit
  • Identification

View Identification_Core2

Content of table Identification restricted to those available for a user

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO
IdentificationSequence smallint The sequence of the identifications. The last identification (having the highest sequence) is regarded as valid NO
IdentificationDate datetime The date of the identification calculated from the entries in IdentificationDay, -Month and -Year YES
IdentificationDay tinyint The day of the identification YES
IdentificationMonth tinyint The month of the identification YES
IdentificationYear smallint The year of the identification. The year may be empty if only the day or month are known. YES
IdentificationDateSupplement nvarchar (255) Verbal or additional identification date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
IdentificationDateCategory nvarchar (50) Category of the date of the identification e.g. “system”, “estimated” (= foreign key, see in table CollDateCategory_Enum) YES
VernacularTerm nvarchar (255) Name or term other than a taxonomic (= scientific) name, e.g. ‘pine’, ’limestone’, ‘conifer’, ‘hardwood’ YES
TaxonomicName nvarchar (255) Valid name of the species (including the taxonomic author where available). Example: ‘Rosa canina L.’ YES
NameURI varchar (255) The URI of the taxonomic name, e.g. as provided by the module DiversityTaxonNames. YES
IdentificationCategory nvarchar (50) Category of the identification e.g. ‘determination’, ‘confirmation’, ‘absence’ (= foreign key, see table CollIdentificationCategory_Enum) YES
IdentificationQualifier nvarchar (50) Qualification of the identification e.g. “cf.”," aff.", “sp. nov.” (= foreign key, see table CollIdentificationQualifier_Enum) YES
TypeStatus nvarchar (50) If identification unit is type of a taxonomic name: holotype, syntype, etc. (= foreign key, see table CollTypeStatus_Enum) YES
TypeNotes nvarchar (MAX) Notes on the typification of this specimen YES
Notes nvarchar (MAX) User defined notes, e.g. the reason for a re-determination / change of the name, etc. YES
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES

Depending on:

  • CollectionSpecimenID_Available
  • Identification

View IdentificationUnit_Core2

Content of table IdentificationUnit restricted to those available for a user

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
IdentificationUnitID int ID of the IdentificationUnit (= part of primary key). Usually one of possibly several organisms present on the collected specimen. Example: parasite with hyperparasite on plant leaf = 3 units, NO
LastIdentificationCache nvarchar (255) The last identification as entered in table Identification NO
FamilyCache nvarchar (255) A cached value of the family of the taxon of the last identification. Can be set by the editor, if NameURI in table Identification is NULL, otherwise set by the system. YES
OrderCache nvarchar (255) A cached value of the order of the taxon of the last identification. Can be set by the editor, if NameURI in table Identification is NULL, otherwise set by the system. YES
TaxonomicGroup nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key) NO
OnlyObserved bit True, if the organism was only observed rather than collected. It is therefore not present on the preserved specimen. Example: Tree under which the collected mycorrhizal fungus grew. YES
RelatedUnitID int The IdentificationUnitID of the organism or substrate on which this organism is growing (= foreign key) YES
RelationType nvarchar (50) The relation of a unit to its substrate, e.g. parasitism, symbiosis etc. as stored in CollRelationType_Enum (= foreign key) YES
ColonisedSubstratePart nvarchar (255) If a substrate association exists: part of the substrate which is affected in the interaction (e.g. ’leaves’, if a fungus is growing on the leaves of an infected plant) YES
LifeStage nvarchar (255) Examples: ‘II, III’ for spore generations of rusts or ‘seed’, ‘seedling’ etc. for higher plants YES
Gender nvarchar (50) The sex of the organism, e.g. ‘female’ YES
NumberOfUnits smallint The number of units of this organism, e.g. 400 beetles in a bottle YES
ExsiccataNumber nvarchar (50) If specimen is an exsiccata: Number of current specimen within the exsiccata series YES
ExsiccataIdentification smallint Refers to the IdentificationSequence in Identification (= foreign key). The name under which the collectied specimen or this organism is published within an exsiccata. YES
UnitIdentifier nvarchar (50) An identifier for the identification of the unit, e.g. a number painted on a tree within an experimental plot YES
UnitDescription nvarchar (50) Description of the unit, especially if not an organism but parts or remnants of it were present or observed, e.g. a nest of an insect or a song of a bird YES
Circumstances nvarchar (50) Circumstances of the occurence of the organism YES
DisplayOrder smallint The sequence in which the units within this specimen will appear on e.g. a label where the first unit may be printed in the header and others in the text below. 0 means the unit should not appear on a label. NO
Notes nvarchar (MAX) Further information on the organism or interaction, e.g. infection symptoms like ‘producing galls’ YES
HierarchyCache nvarchar (500) A cached value fo the superior taxonomy of the last identification as derived from a taxonomic data provider YES
RetrievalType nvarchar (50) The way the data about the unit were retrieved, e.g. observation, literature YES
ParentUnitID int The IdentificationUnitID of a parent organism of which this organism is a child of (= foreign key). YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
NumberOfUnitsModifier nvarchar (50) A modifier for the number of units of this organism, e.g. ca. 400 beetles in a bottle YES

Depending on:

  • CollectionSpecimenID_Available
  • IdentificationUnit

View IdentificationUnitDisplayOrder1

Content of table IdentificationUnit restricted to those available for a user and DisplayOrder = 1

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
IdentificationUnitID int ID of the IdentificationUnit (= part of primary key). Usually one of possibly several organisms present on the collected specimen. Example: parasite with hyperparasite on plant leaf = 3 units, NO
LastIdentificationCache nvarchar (255) The last identification as entered in table Identification NO
FamilyCache nvarchar (255) A cached value of the family of the taxon of the last identification. Can be set by the editor, if NameURI in table Identification is NULL, otherwise set by the system. YES
OrderCache nvarchar (255) A cached value of the order of the taxon of the last identification. Can be set by the editor, if NameURI in table Identification is NULL, otherwise set by the system. YES
TaxonomicGroup nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key) NO
OnlyObserved bit True, if the organism was only observed rather than collected. It is therefore not present on the preserved specimen. Example: Tree under which the collected mycorrhizal fungus grew. YES
RelatedUnitID int The IdentificationUnitID of the organism or substrate on which this organism is growing (= foreign key) YES
RelationType nvarchar (50) The relation of a unit to its substrate, e.g. parasitism, symbiosis etc. as stored in CollRelationType_Enum (= foreign key) YES
ColonisedSubstratePart nvarchar (255) If a substrate association exists: part of the substrate which is affected in the interaction (e.g. ’leaves’, if a fungus is growing on the leaves of an infected plant) YES
LifeStage nvarchar (255) Examples: ‘II, III’ for spore generations of rusts or ‘seed’, ‘seedling’ etc. for higher plants YES
Gender nvarchar (50) The sex of the organism, e.g. ‘female’ YES
NumberOfUnits smallint The number of units of this organism, e.g. 400 beetles in a bottle YES
ExsiccataNumber nvarchar (50) If specimen is an exsiccata: Number of current specimen within the exsiccata series YES
ExsiccataIdentification smallint Refers to the IdentificationSequence in Identification (= foreign key). The name under which the collectied specimen or this organism is published within an exsiccata. YES
UnitIdentifier nvarchar (50) An identifier for the identification of the unit, e.g. a number painted on a tree within an experimental plot YES
Circumstances nvarchar (50) Circumstances of the occurence of the organism YES
DisplayOrder smallint The sequence in which the units within this specimen will appear on e.g. a label where the first unit may be printed in the header and others in the text below. 0 means the unit should not appear on a label. NO
Notes nvarchar (MAX) Further information on the organism or interaction, e.g. infection symptoms like ‘producing galls’ YES

Depending on:

  • CollectionSpecimenID_UserAvailable
  • IdentificationUnit

View ManagerSpecimenPartList

List based on content of table CollectionSpecimenPart restricted to those with an AccessionNumber and available for a CollectionManager

Column Data type Description Nullable
AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752” YES
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key) NO
SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key). NO
AccessionNumberSpecimen nvarchar (50) - YES
AccessionNumberPart nvarchar (50) - YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum) NO
CollectionName nvarchar (50) - YES

Depending on:

  • CollectionSpecimen
  • CollectionSpecimenPart
  • ManagerCollectionList

View ProjectList

List of projects available for a user

Column Data type Description Nullable
Project nvarchar (50) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects) YES
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO
ReadOnly int If the user has only read access to data of this project YES
ProjectURI varchar (255) The URI of the project, e.g. as provided by the module DiversityProjects. YES

Depending on:

  • ProjectProxy
  • ProjectUser

View ProjectListNotReadOnly

List of projects a user can edit

Column Data type Description Nullable
Project nvarchar (50) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects) YES
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO

Depending on:

  • ProjectProxy
  • ProjectUser

View RequesterSpecimenPartList

List of possible request for a user based on table CollectionSpecimenPart

Column Data type Description Nullable
AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752” YES
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key) NO
SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key). NO
AccessionNumberSpecimen nvarchar (50) - YES
AccessionNumberPart nvarchar (50) - YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum) NO
CollectionName nvarchar (50) - YES

Depending on:

  • CollectionSpecimen
  • CollectionSpecimenPart
  • RequesterCollectionList

View TransactionForeignRequest

Content of table Transaction with TransactionType = request a CollectionManager has access to

Column Data type Description Nullable
TransactionID int Unique ID for the transaction (= primary key) NO
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy YES
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out NO
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES
AdministratingCollectionID int ID for the collection for which the Manager has the right to administrate the transaction. Corresponds to AdministratingCollectionID in table Transaction. NO
MaterialDescription nvarchar (MAX) Description of the material of this transaction YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. YES
MaterialCollectors nvarchar (MAX) The collectors of the material YES
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift YES
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES
NumberOfUnits smallint The number of units which were (initially) included in the transaction YES
Investigator nvarchar (50) The investigator for whose study a transacted material was sent YES
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES
BeginDate datetime Date when the transaction started YES
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner YES
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES
ResponsibleName nvarchar (255) The person responsible for this transaction YES
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents) YES

Depending on:

  • CollectionManager
  • Transaction

View TransactionList

Content of table Transaction missing a AdministratingCollectionID resp. those available for a CollectionManager

Column Data type Description Nullable
TransactionID int Unique ID for the transaction (= primary key) NO
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy YES
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out NO
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES
AdministratingCollectionID int ID for the collection for which the Manager has the right to administrate the transaction. Corresponds to AdministratingCollectionID in table Transaction. NO
MaterialDescription nvarchar (MAX) Description of the material of this transaction YES
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. YES
MaterialCollectors nvarchar (MAX) The collectors of the material YES
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift YES
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents YES
NumberOfUnits smallint The number of units which were (initially) included in the transaction YES
Investigator nvarchar (200) The investigator for whose study a transacted material was sent YES
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES
BeginDate datetime Date when the transaction started YES
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner YES
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES
ResponsibleName nvarchar (255) The person responsible for this transaction YES
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents) YES
DateSupplement nvarchar (100) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. YES

Depending on:

  • CollectionManager
  • Transaction

View TransactionList_H7

Content of table Transaction missing a AdministratingCollectionID resp. those available for a CollectionManager including a hierarchy with up to 7 levels

Column Data type Description Nullable
TransactionID int Unique ID for the transaction (= primary key) NO
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy YES
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out NO
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
HierarchyDisplayText nvarchar (1621) Hierarchy of the transaction represented by the TransactionTitle separated by " " for up to 7 levels
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES
AdministratingCollectionID int ID for the collection for which the Manager has the right to administrate the transaction. Corresponds to AdministratingCollectionID in table Transaction. NO
MaterialDescription nvarchar (MAX) Description of the material of this transaction YES
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. YES
MaterialCollectors nvarchar (MAX) The collectors of the material YES
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift YES
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents YES
NumberOfUnits int The number of units which were (initially) included in the transaction YES
Investigator nvarchar (200) The investigator for whose study a transacted material was sent YES
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES
BeginDate datetime Date when the transaction started YES
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner YES
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES
ResponsibleName nvarchar (255) The person responsible for this transaction YES
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents) YES
DateSupplement nvarchar (100) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. YES

Depending on:

  • CollectionManager
  • Transaction

View TransactionPermit

Content of table Transaction restricted to those with TransactionType = permit

Column Data type Description Nullable
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out NO
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction. NO
MaterialDescription nvarchar (MAX) Description of the material of this transaction YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. YES
MaterialCollectors nvarchar (MAX) The collectors of the material YES
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation YES
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES
NumberOfUnits int The number of units which were (initially) included in the transaction YES
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES
Investigator nvarchar (200) The investigator for whose study a transacted material was sent YES
BeginDate datetime Date when the transaction started YES
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES
DateSupplement nvarchar (100) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. YES
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents YES
ResponsibleName nvarchar (255) The person responsible for this transaction YES
TransactionID int Unique ID for the transaction (= primary key) NO

Depending on:

  • Transaction

View TransactionRegulation

Content of table Transaction restricted to those with TransactionType = regulation a user has access to

Column Data type Description Nullable
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
TransactionID int Unique ID for the transaction (= primary key) NO

Depending on:

  • Transaction
  • TransactionList

View TransactionRequest

Content of table Transaction with TransactionType loan or request the user has access to as a CollectionManager or the user has created and access to as a CollectionRequester

Column Data type Description Nullable
TransactionID int Unique ID for the transaction (= primary key) NO
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy YES
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out NO
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES
AdministratingCollectionID int ID for the collection for which the Manager has the right to administrate the transaction. Corresponds to AdministratingCollectionID in table Transaction. NO
MaterialDescription nvarchar (MAX) Description of the material of this transaction YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. YES
MaterialCollectors nvarchar (MAX) The collectors of the material YES
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift YES
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES
NumberOfUnits smallint The number of units which were (initially) included in the transaction YES
Investigator nvarchar (50) The investigator for whose study a transacted material was sent YES
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES
BeginDate datetime Date when the transaction started YES
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner YES
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES
ResponsibleName nvarchar (255) The person responsible for this transaction YES
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents) YES

Depending on:

  • TransactionForeignRequest
  • TransactionUserRequest

View TransactionUserRequest

Content of table Transaction with TransactionType loan or request a CollectionRequester has created and access to

Column Data type Description Nullable
TransactionID int Unique ID for the transaction (= primary key) NO
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy YES
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out NO
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface NO
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing YES
AdministratingCollectionID int ID for the collection for which the requester has the right to request specimen. Corresponds to AdministratingCollectionID in table Transaction. NO
MaterialDescription nvarchar (MAX) Description of the material of this transaction YES
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. YES
MaterialCollectors nvarchar (MAX) The collectors of the material YES
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift YES
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift YES
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift YES
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift YES
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents) YES
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift YES
NumberOfUnits smallint The number of units which were (initially) included in the transaction YES
Investigator nvarchar (50) The investigator for whose study a transacted material was sent YES
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner YES
BeginDate datetime Date when the transaction started YES
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted YES
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner YES
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page YES
ResponsibleName nvarchar (255) The person responsible for this transaction YES
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents) YES

Depending on:

  • CollectionRequester
  • Transaction

View UserGroups

List of the groups the users are asigned to

Column Data type Description Nullable
CombinedNameCache nvarchar (255) The short name of the user, e.g. P. Smith NO
LoginName nvarchar (50) A login name which the user uses to access the DivesityWorkbench, Microsoft domains, etc. NO
UserGroup nvarchar (128) - NO

Depending on:

  • UserProxy

View ViewBaseURL

Content of function dbo.BaseURL()

Column Data type Description Nullable
BaseURL varchar (255) - YES

Depending on:

  • BaseURL

View ViewCollectionEventImage

Content of table CollectionEventImage converting XML to nvarchar and excluding Log columns

Column Data type Description Nullable
CollectionEventID int Part of primay key, refers to unique ID for the table CollectionEvent (= foreign key) NO
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO
ResourceURI varchar (255) The URI of the resource (e.g. see module DiversityResources) YES
ImageType nvarchar (50) Type of the image, e.g. map YES
Notes nvarchar (MAX) Notes to this image concerning the CollectionEvent YES
Description nvarchar (MAX) Description of the image YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES

Depending on:

  • CollectionEventImage

View ViewCollectionEventSeriesImage

Content of table CollectionEventSeriesImage converting XML to nvarchar and excluding Log columns

Column Data type Description Nullable
SeriesID int Unique ID for the table CollectionEventSeries (= foreign key and part of primary key) NO
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO
ResourceURI varchar (255) The URI of the resource (e.g. see module DiversityResources) YES
ImageType nvarchar (50) Type of the image, e.g. map YES
Notes nvarchar (MAX) Notes to this image of the collection site YES
Description nvarchar (MAX) Description of the image YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e.g. Creative Common licenses YES
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES

Depending on:

  • CollectionEventSeriesImage

View ViewCollectionImage

Content of table Collection converting XML to nvarchar and excluding Log columns

Column Data type Description Nullable
CollectionID int Refers to the ID of Collection (= foreign key and part of primary key) NO
URI varchar (255) The complete URI address of the image. NO
ImageType nvarchar (50) Type of the image, e.g. label YES
Notes nvarchar (MAX) Notes on the collection image YES
Description nvarchar (MAX) Description of the image YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e.g. Creative Common licenses YES
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES

Depending on:

  • CollectionImage

View ViewCollectionSpecimenImage

Content of table CollectionSpecimenImage converting XML to nvarchar and excluding Log columns

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
URI varchar (255) The complete URI address of the image. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO
ResourceURI varchar (255) The URI of the image, e.g. as stored in the module DiversityResources. YES
SpecimenPartID int Optional: If the data set is not related to a part of a specimen, the ID of a related part (= foreign key) YES
IdentificationUnitID int If image refers to only one out of several IdentificationUnits for a specimen, refers to the ID of an IdentificationUnit for a collection specimen (= foreign key) YES
ImageType nvarchar (50) Type of the image, e.g. photograph YES
Notes nvarchar (MAX) Notes on the specimen image YES
Description nvarchar (MAX) Description of the image YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
CreatorAgent nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES
LicenseURI varchar (500) The URI of the license for the resource YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI nvarchar (500) The link to a module containing futher information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
LicenseNotes nvarchar (500) Notice on license for the resource YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
DisplayOrder int The order in which the images should be shown in a interface YES
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES

Depending on:

  • CollectionSpecimenImage

View ViewDiversityWorkbenchModule

Content of function dbo.DiversityWorkbenchModule()

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) - YES

Depending on:

  • DiversityWorkbenchModule

View ViewIdentificationUnitGeoAnalysis

Content of table IdentificationUnitGeoAnalysis converting geography and geometry to nvarchar and excluding Log columns

Column Data type Description Nullable
CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key) NO
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key) NO
AnalysisDate datetime The date of the analysis NO
Geography nvarchar (MAX) The geography where the organism resp. object was located according to WGS84, e.g. a point (latitide, longitude and altitude) YES
Geometry nvarchar (MAX) The geometry of the place the organism resp. object was observed, e.g. an area YES
ResponsibleName nvarchar (255) Name of the person or institution responsible for the determination YES
ResponsibleAgentURI varchar (255) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents. YES
Notes nvarchar (MAX) Notes on this analysis YES

Depending on:

  • IdentificationUnitGeoAnalysis
May 3, 2024

Diversity Collection

FUNCTIONS and PROCEDURES


The following objects are not included:

  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

FUNCTIONS

Function AgentOneString

Returns a result set that contains a string with all Collectors of a Specimen

Parameter DataType Description
@CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key)
Column DataType Description
CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key)
CollectorsNameString nvarchar (1000) -
CollectorsNameStringNumber nchar (1500) -

Depending on:

  • CollectionAgent

Function AnalysisChildNodes

Content of table Analysis containing all children for a given AnalysisID defined via the relation in column AnalysisParentID

Parameter DataType Description
@ID int The AnalysisID for which the children should be returned
Column DataType Description
AnalysisID int ID of the analysis (primary key)
AnalysisParentID int Analysis ID of the parent analysis, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (500) Description of the analysis
MeasurementUnit nvarchar (50) The measurement unit used for the analysis, e.g. mm, µmol, kg
Notes nvarchar (1000) Notes on this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
RowGUID uniqueidentifier -

Depending on:

  • Analysis

Function AnalysisHierarchyAll

Content of table Analysis including the hierarchy separated via “|” defined via the relation in column AnalysisParentID

Column DataType Description
AnalysisID int ID of the analysis (primary key)
AnalysisParentID int Analysis ID of the parent analysis, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (MAX) Description of the analysis
MeasurementUnit nvarchar (50) The measurement unit used for the analysis, e.g. mm, µmol, kg
Notes nvarchar (MAX) Notes on this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
HierarchyDisplayText varchar (900) -

Depending on:

  • Analysis

Function AnalysisList

Returns the content of table Analysis related to the given project and a taxonomic group

Parameter DataType Description
@ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
@TaxonomicGroup nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key)
Column DataType Description
AnalysisID int ID of the analysis (primary key)
AnalysisParentID int Analysis ID of the parent analysis, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (500) Description of the analysis
MeasurementUnit nvarchar (50) The measurement unit used for the analysis, e.g. mm, µmol, kg
Notes nvarchar (1000) Notes on this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
DisplayTextHierarchy nvarchar (255) -
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries

Depending on:

  • Analysis
  • AnalysisChildNodes
  • AnalysisTaxonomicGroup
  • ProjectAnalysis

Function AnalysisListForUnit

Returns the content of table Analysis available for a IdentificationUnit given by the IdentificationUnitID. The list depends upon the analysis types available for a taxonomic group and the projects available for an analysis

Parameter DataType Description
@IdentificationUnitID int ID of the IdentificationUnit (= part of primary key). Usually one of possibly several organisms present on the collected specimen. Example: parasite with hyperparasite on plant leaf = 3 units,
Column DataType Description
AnalysisID int ID of the analysis (primary key)
AnalysisParentID int Analysis ID of the parent analysis, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (1000) Description of the analysis
MeasurementUnit nvarchar (50) The measurement unit used for the analysis, e.g. mm, µmol, kg
Notes nvarchar (1000) Notes on this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
DisplayTextHierarchy nvarchar (255) -
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries

Depending on:

  • Analysis
  • AnalysisTaxonomicGroup
  • CollectionProject
  • IdentificationUnit
  • ProjectAnalysis

Function AnalysisProjectList

Returns content of table Analysis related to the given project

Parameter DataType Description
@ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
Column DataType Description
AnalysisID int ID of the analysis (primary key)
AnalysisParentID int Analysis ID of the parent analysis, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (500) Description of the analysis
MeasurementUnit nvarchar (50) The measurement unit used for the analysis, e.g. mm, µmol, kg
Notes nvarchar (1000) Notes on this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
RowGUID uniqueidentifier -

Depending on:

  • Analysis
  • AnalysisChildNodes
  • ProjectAnalysis

Function AnalysisTaxonomicGroupForProject

Returns the content of the table AnalysisTaxonomicGroup used in a project including the whole hierarchy

Parameter DataType Description
@ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
Column DataType Description
AnalysisID int ID of the analysis (primary key)
TaxonomicGroup nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key)
RowGUID uniqueidentifier -

Depending on:

  • Analysis
  • AnalysisList
  • AnalysisTaxonomicGroup
  • ProjectAnalysis

Function AverageAltitude

The average altitude for the points of a geography where the z value is given

DataType: float

Parameter DataType Description
@Geography geography (-1) The geography for which the average altitude should be extracted

Function BaseURL

Returns the basic URL for the database

DataType: varchar (255)


Function CollCharacterType_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) -
Description nvarchar (500) -
Abbreviation nvarchar (50) -

Function CollDateCategory_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code that uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollectionChildNodes

Returns a result set that lists all the items within a hierarchy starting at the topmost item related to the given item.

Parameter DataType Description
@ID int ID of the collection (= CollectionID, PK)
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection

Function CollectionEventSeriesHierarchy

Returns a table that lists all the Series related to the given Series.

Parameter DataType Description
@SeriesID int Primary key. The ID for this series of collection events (= primary key)
Column DataType Description
SeriesID int Primary key. The ID for this series of collection events (= primary key)
SeriesParentID int The ID of the superior series of collection events
DateStart datetime Point in time when the series of collection events started
DateEnd datetime Point in time when the series of collection events ended
DateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event series comprises a period. The time of the event, if necessary.
SeriesCode nvarchar (50) The user defined code for a series of collection events
Description nvarchar (500) The description of the series of collection events as it will be printed on e.g. the label
Notes nvarchar (500) Notes on this series of collection events
Geography geography (MAX) The geography of the series of collection events

Depending on:

  • CollectionEventSeries
  • EventSeriesChildNodes
  • EventSeriesTopID

Function CollectionHierarchy

Returns a table that lists all the analysis items related to the given analysis.

Parameter DataType Description
@CollectionID int Unique reference ID for the collection (= primary key)
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection
  • CollectionChildNodes

Function CollectionHierarchyAll

Returns a table that lists all the collections including a display text with the whole hierarchy

Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (500) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayText varchar (900) -
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection
  • UserCollectionList

Function CollectionHierarchyMulti

Returns a table that lists all the collections related to the given collection in the list.

Parameter DataType Description
@CollectionIDs varchar (255) Comma separated list of IDs of the collections that should be included.
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (50) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (500) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection

Function CollectionHierarchySuperior

Returns a table that lists the given and all the items superior to the given collection

Parameter DataType Description
@CollectionID int Unique reference ID for the collection (= primary key)
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
LocationGeometry geometry (MAX) Geometry of the collection within the floor plan
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection

Function CollectionLocation

Returns a table that lists all the collection items related to the given collection

Parameter DataType Description
@CollectionID int The ID of the collection for which the hierarchy should be listed
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection
  • CollectionLocationChildNodes

Function CollectionLocationAll

Returns a table that lists all the collections including a display text with the whole hierarchy

Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (500) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayText varchar (900) Hierarchy of the collection with acronym if present, otherwise name
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection
  • UserCollectionList

Function CollectionLocationChildNodes

Returns a result set that lists all the items within a hierarchy starting at the topmost item related to the given item

Parameter DataType Description
@ID int The ID of the collection for which the hierarchy should be listed
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection

Function CollectionLocationMulti

List of collections according to the given CollectionIDs

Parameter DataType Description
@CollectionIDs varchar (4000) Space separated list of CollectionIDs with a maximal length of 4000
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (50) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (500) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection

Function CollectionLocationSuperior

Returns a table that lists the given and all the items superior to the given collection

Parameter DataType Description
@CollectionID int The ID of the collection for which the hierarchy should be listed
Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (10) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (255) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
LocationPlan varchar (500) URI or file name including path of the floor plan of the collection
LocationPlanWidth float Width of location plan in meter for calculation of size by provided geometry
LocationPlanDate datetime The date when the plan for the collection has been created
LocationHeight float Height from ground level, e.g. for the position of sensors
LocationGeometry geometry (MAX) Geometry of the collection within the floor plan
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Type nvarchar (50) Type of the collection, e.g. cupboard, drawer etc.
LocationParentID int If the hierarchy of the location does not match the logical hierarchy, the ID of the parent location

Depending on:

  • Collection

Function CollectionSpecimenCoordinateList

Parameter DataType Description
@CollectionSpecimenIDList varchar (8000) -
Column DataType Description
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key)
Latitude float -
Longitude float -

Depending on:

  • CollectionSpecimenCoordinates

Function CollectionSpecimenCoordinates

Parameter DataType Description
@CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key)
Column DataType Description
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key)
Latitude float -
Longitude float -
LocationAccuracy nvarchar (50) The accuracy of the determination of this locality
DistanceToLocation nvarchar (50) Distance from the specified place to the real location of the collection site (m)
DirectionToLocation nvarchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north)

Depending on:

  • CollectionEventLocalisation
  • CollectionSpecimen

Function CollectionSpecimenRelationInversList

Listing all internal relations in reverse perspective

Column DataType Description
CollectionSpecimenID int Unique ID for the table CollectionSpecimen (primary key)
RelatedSpecimenCollectionSpecimenID int The CollectionSpecimenID of the dataset that refers to the current dataset
RelatedSpecimenAccessionNumber nvarchar (50) The AccessionNumber of the dataset that refers to the current dataset
RelationType nvarchar (50) Type of the relation between the specimen (= foreign key, see table CollRelationType_Enum)
RelatedSpecimenCollectionID int ID of the Collection as stored in table Collection (= foreign key, see table Collection)
Notes nvarchar (MAX) Notes on the relation to the specimen

Depending on:

  • BaseURL
  • CollectionSpecimen
  • CollectionSpecimenRelation

Function CollectionTaskChildNodes

Returns a result set that lists all children of a collection task within a hierarchy

Parameter DataType Description
@ID int The CollectionTaskID to which the inferior datasets are link to via column CollectionTaskParentID
Column DataType Description
CollectionTaskID int PK of the table
CollectionTaskParentID int Relation to PK for hierarchy within the data
CollectionID int Relation to table Collection. Every ColletionTask needs a relation to a collection
TaskID int Relation to table Task where details for the collection task are defined
DisplayOrder int Display order e.g. in a report. Data with value 0 will not be included
DisplayText nvarchar (400) The display text of the module related data as shown e.g. in a user interface
ModuleUri varchar (500) The URL of module related data
CollectionSpecimenID int Refers to the CollectionSpecimenID of CollectionSpecimenPart (= foreign key and part of primary key)
SpecimenPartID int Unique ID of the part of the collection specimen the task is related to.
TransactionID int ID of a transaction. Related to PK of table Transaction
TaskStart datetime The start date and or time of the collection tasks. The type is defined in table Task
TaskEnd datetime The end date and or time of the collection tasks. The type is defined in table Task
Result nvarchar (400) A text result either taken from a list or entered. The type is defined in table Task
URI varchar (500) The URI of the collection tasks. The type is defined in table Task
NumberValue real The numeric value of the collection tasks. The type is defined in table Task
BoolValue bit The boolean of the collection tasks. The type is defined in table Task
MetricDescription nvarchar (500) Description of the metric e.g. imported from a time series database like Prometheus
MetricSource varchar (4000) The source of the metric e.g. the PromQL statement for the import from a timeseries database Prometheus
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleAgent nvarchar (500) The name of the responsible person or institution
ResponsibleAgentURI varchar (500) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents.
Description nvarchar (MAX) The description of the collection tasks. The type is defined in table Task
Notes nvarchar (MAX) The notes of the collection tasks. The type is defined in table Task

Depending on:

  • CollectionTask

Function CollectionTaskCollectionHierarchyAll

Returns a result set that lists all the collection tasks including a display text with the related collection as leading part

Column DataType Description
CollectionTaskID int PK of the table
CollectionTaskParentID int Relation to PK for hierarchy within the data
CollectionID int Unique reference ID for the collection (= primary key)
TaskID int Relation to table Task where details for the collection task are defined
DisplayText nvarchar (400) The display text of the module related data as shown e.g. in a user interface
DisplayOrder int The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
ModuleUri varchar (500) The URL of module related data
CollectionSpecimenID int Refers to the CollectionSpecimenID of CollectionSpecimenPart (= foreign key and part of primary key)
SpecimenPartID int Unique ID of the part of the collection specimen the task is related to.
TransactionID int The ID of the transaction to which the collection task is linked
TaskStart datetime The start date and or time of the collection tasks. The type is defined in table Task
TaskEnd datetime The end date and or time of the collection tasks. The type is defined in table Task
Result nvarchar (400) A text result either taken from a list or entered. The type is defined in table Task
URI varchar (500) The URI of the collection tasks. The type is defined in table Task
NumberValue real The numeric value of the collection tasks. The type is defined in table Task
BoolValue bit The boolean of the collection tasks. The type is defined in table Task
MetricDescription nvarchar (500) Description of the metric e.g. imported from a time series database like Prometheus
MetricSource varchar (4000) The source of the metric e.g. the PromQL statement for the import from a timeseries database Prometheus
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleAgent nvarchar (500) The name of the responsible person or institution
ResponsibleAgentURI varchar (500) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents.
Description nvarchar (MAX) A short description of the collection
Notes nvarchar (MAX) The notes of the collection tasks. The type is defined in table Task
HierarchyDisplayText nvarchar (900) Display text including the hierarchy of the collection separated by the string defined in function TaskCollectionHierarchySeparator followed by the hierarchy of the collection task separated by the string defined in function TaskHierarchySeparator followed by optional information about start, end and result of the collection task

Depending on:

  • CollectionHierarchyAll
  • CollectionTask
  • Task
  • TaskCollectionHierarchySeparator
  • TaskHierarchySeparator

Function CollectionTaskHierarchy

Returns a result set that lists all the collection tasks within a hierarchy starting at the topmost collection task related to the given collection task

Parameter DataType Description
@ID int The CollectionTaskID for which the hierarchy should be retrieved
Column DataType Description
CollectionTaskID int PK of the table
CollectionTaskParentID int Relation to PK for hierarchy within the data
CollectionID int Relation to table Collection. Every ColletionTask needs a relation to a collection
TaskID int Relation to table Task where details for the collection task are defined
DisplayOrder int Display order e.g. in a report. Data with value 0 will not be included
DisplayText nvarchar (400) The display text of the module related data as shown e.g. in a user interface
ModuleUri varchar (500) The URL of module related data
CollectionSpecimenID int Refers to the CollectionSpecimenID of CollectionSpecimenPart (= foreign key and part of primary key)
SpecimenPartID int Unique ID of the part of the collection specimen the task is related to.
TransactionID int The ID of the transaction to which the collection task is linked
TaskStart datetime The start date and or time of the collection tasks. The type is defined in table Task
TaskEnd datetime The end date and or time of the collection tasks. The type is defined in table Task
Result nvarchar (400) A text result either taken from a list or entered. The type is defined in table Task
URI varchar (500) The URI of the collection tasks. The type is defined in table Task
NumberValue real The numeric value of the collection tasks. The type is defined in table Task
BoolValue bit The boolean of the collection tasks. The type is defined in table Task
MetricDescription nvarchar (500) Description of the metric e.g. imported from a time series database like Prometheus
MetricSource varchar (4000) The source of the metric e.g. the PromQL statement for the import from a timeseries database Prometheus
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleAgent nvarchar (500) The name of the responsible person or institution
ResponsibleAgentURI varchar (500) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents.
Description nvarchar (MAX) The description of the collection tasks. The type is defined in table Task
Notes nvarchar (MAX) The notes of the collection tasks. The type is defined in table Task

Depending on:

  • CollectionTask
  • CollectionTaskChildNodes

Function CollectionTaskHierarchyAll

All CollectionTasks including a column displaying the hierarchy of the CollectionTask

Column DataType Description
CollectionTaskID int PK of the table
CollectionTaskParentID int Relation to PK for hierarchy within the data
CollectionID int Unique reference ID for the collection (= primary key)
TaskID int Relation to table Task where details for the collection task are defined
DisplayOrder int The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
Task nvarchar (400) Display text of the task the collection task is linked to
DisplayText nvarchar (400) The display text of the module related data as shown e.g. in a user interface
ModuleUri varchar (500) The URL of module related data
CollectionSpecimenID int Refers to the CollectionSpecimenID of CollectionSpecimenPart (= foreign key and part of primary key)
SpecimenPartID int Unique ID of the part of the collection specimen the task is related to.
TransactionID int The ID of the transaction to which the collection task is linked
TaskStart datetime The start date and or time of the collection tasks. The type is defined in table Task
TaskEnd datetime The end date and or time of the collection tasks. The type is defined in table Task
Result nvarchar (400) A text result either taken from a list or entered. The type is defined in table Task
URI varchar (500) The URI of the collection tasks. The type is defined in table Task
NumberValue real The numeric value of the collection tasks. The type is defined in table Task
BoolValue bit The boolean of the collection tasks. The type is defined in table Task
MetricDescription nvarchar (500) Description of the metric e.g. imported from a time series database like Prometheus
MetricSource varchar (4000) The source of the metric e.g. the PromQL statement for the import from a timeseries database Prometheus
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleAgent nvarchar (500) The name of the responsible person or institution
ResponsibleAgentURI varchar (500) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents.
Description nvarchar (MAX) A short description of the collection
Notes nvarchar (MAX) The notes of the collection tasks. The type is defined in table Task
HierarchyDisplayText nvarchar (4000) Display text including the hierarchy of the collection task separated by the string defined in function TaskHierarchySeparator followed by the hierarchy of the collection separated by the string defined in function TaskCollectionHierarchySeparator
CollectionHierarchyDisplayText nvarchar (4000) Display text including the hierarchy of the collection separated by the string defined in function TaskCollectionHierarchySeparator followed by the hierarchy of the collection task separated by the string defined in function TaskHierarchySeparator
TaskHierarchyDisplayText nvarchar (4000) Deprecated
TaskDisplayText nvarchar (4000) Display text of the collection task based on diverse content in tables Task and CollectionTask

Depending on:

  • CollectionHierarchyAll
  • CollectionTask
  • Task
  • TaskCollectionHierarchySeparator
  • TaskHierarchySeparator

Function CollectionTaskParentNodes

Parent CollectionTasks for a given CollectionTask in the hierarchy

Parameter DataType Description
@ID int The CollectionTaskID for which the parent hierarchy should be retrieved
Column DataType Description
CollectionTaskID int PK of the table
CollectionTaskParentID int Relation to PK for hierarchy within the data
CollectionID int Relation to table Collection. Every ColletionTask needs a relation to a collection
TaskID int Relation to table Task where details for the collection task are defined
DisplayOrder int Display order e.g. in a report. Data with value 0 will not be included
DisplayText nvarchar (400) The display text of the module related data as shown e.g. in a user interface
ModuleUri varchar (500) The URL of module related data
CollectionSpecimenID int Refers to the CollectionSpecimenID of CollectionSpecimenPart (= foreign key and part of primary key)
SpecimenPartID int Unique ID of the part of the collection specimen the task is related to.
TransactionID int ID of a transaction. Related to PK of table Transaction
TaskStart datetime The start date and or time of the collection tasks. The type is defined in table Task
TaskEnd datetime The end date and or time of the collection tasks. The type is defined in table Task
Result nvarchar (400) A text result either taken from a list or entered. The type is defined in table Task
URI varchar (500) The URI of the collection tasks. The type is defined in table Task
NumberValue real The numeric value of the collection tasks. The type is defined in table Task
BoolValue bit The boolean of the collection tasks. The type is defined in table Task
MetricDescription nvarchar (500) Description of the metric e.g. imported from a time series database like Prometheus
MetricSource varchar (4000) The source of the metric e.g. the PromQL statement for the import from a timeseries database Prometheus
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleAgent nvarchar (500) The name of the responsible person or institution
ResponsibleAgentURI varchar (500) URI of the person or institution responsible for the determination (= foreign key) as stored in the module DiversityAgents.
Description nvarchar (MAX) The description of the collection tasks. The type is defined in table Task
Notes nvarchar (MAX) The notes of the collection tasks. The type is defined in table Task

Depending on:

  • CollectionTask

Function CollEventDateCategory_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollEventImageType_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollExchangeType_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) -
Description nvarchar (500) -
Abbreviation nvarchar (50) -

Function CollIdentificationCategory_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollIdentificationDateCategory_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollIdentificationQualifier_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollLabelType_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollMaterialCategory_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollSpecimenImageType_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CollTranscriptionState_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) -
Description nvarchar (500) -
Abbreviation nvarchar (50) -

Function CollTypeStatus_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function ColTaxonomicGroup_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
Code nvarchar (50) A text code which uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
Abbreviation nvarchar (50) -

Function CuratorCollectionHierarchyList

Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (50) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (500) A short description of the collection
Location nvarchar (1000) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.

Depending on:

  • Collection
  • CollectionHierarchy
  • CuratorCollectionList

Function CurrentUser

Returns the information for the current user

Column DataType Description
LoginName nvarchar (50) A login name which the user uses to access the DivesityWorkbench, Microsoft domains, etc.
CombinedNameCache nvarchar (255) The short name of the user, e.g. P. Smith
UserURI varchar (255) Deprecated. URI of a user in a remote module, e.g. refering to UserInfo.UserID in database DiversityUsers
AgentURI varchar (255) URI of a agent in the module DiversityAgents
UserName nvarchar (255) -

Depending on:

  • UserProxy

Function CurrentUserName

retrieval of the name of the current user

DataType: nvarchar (4000)

Depending on:

  • UserProxy

Function DefaultProjectID

Returns the ID of the current project used by the user

DataType: int

Depending on:

  • ProjectUser
  • UserProxy

Function DiversityCollectionCacheDatabaseName

returns the name of the cache database containing the exported data for e.g. publication on the web

DataType: nvarchar (50)


Function DiversityWorkbenchModule

Name of the module

DataType: nvarchar (50)


Function EntityInformation_2

Returns the information about an entity

Parameter DataType Description
@Entity varchar (500) The name of the entity, e.g. Table.Column.Content within the database or a unique string for e.g. a message within the DiversityWorkbench e.g. “DiversityWorkbench.Message.Connection.NoAccess”, PK
@Language nvarchar (50) The language to which the information should be restricted
@Context nvarchar (50) The context to which the information should be restricted
Column DataType Description
Entity varchar (500) The name of the entity, e.g. Table.Column.Content within the database or a unique string for e.g. a message within the DiversityWorkbench e.g. “DiversityWorkbench.Message.Connection.NoAccess”, PK
DisplayGroup nvarchar (50) If DiversityWorkbench entities should be displayed in a group, the name of the group
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
Abbreviation nvarchar (20) The abbreviation for the entity as shown e.g. in a user interface
Description nvarchar (MAX) Description of enumerated object, displayed in the user interface
Accessibility nvarchar (50) If the access of entity is resticted to e.g. read only or it can be edited without restrictions
Determination nvarchar (50) If a value is determined e.g. by the system or the user
Visibility nvarchar (50) If the entity is visible or hidden from e.g. a user interface
PresetValue nvarchar (500) If a value is preset, the value or SQL statement for the value, e.g. ‘determination’ for identifications when using a mobile device during an expedition
UsageNotes nvarchar (4000) Notes from table EntityUsage is present
DoesExist bit If an object does exist
DisplayTextOK bit If DisplayText is present
AbbreviationOK bit If Abbreviation is present
DescriptionOK bit If Description is present

Depending on:

  • Entity
  • EntityContext_Enum
  • EntityRepresentation
  • EntityUsage

Function EventDescription

retrieval of the description including all superior events

DataType: nvarchar (4000)

Parameter DataType Description
@CollectionEventID int Unique ID for the table CollectionEvent (= primary key)

Depending on:

  • CollectionEvent
  • EventDescription

Function EventDescriptionSuperior

retrieval of the description of all superior events

DataType: nvarchar (4000)

Parameter DataType Description
@CollectionEventID int Unique ID for the table CollectionEvent (= primary key)

Depending on:

  • CollectionEvent
  • EventDescription

Function EventSeriesChildNodes

Returns a result set that lists all the items within a hierarchy starting at the topmost item related to the given item

Parameter DataType Description
@ID int The SeriesID for which the children should be returned
Column DataType Description
SeriesID int Primary key. The ID for this series of collection events (= primary key)
SeriesParentID int The ID of the superior series of collection events
DateStart datetime Point in time when the series of collection events started
DateEnd datetime Point in time when the series of collection events ended
DateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event series comprises a period. The time of the event, if necessary.
SeriesCode nvarchar (50) The user defined code for a series of collection events
Description nvarchar (MAX) The description of the series of collection events as it will be printed on e.g. the label
Notes nvarchar (MAX) Notes on this series of collection events
Geography geography (MAX) The geography of the series of collection events

Depending on:

  • CollectionEventSeries

Function EventSeriesHierarchy

Returns a table that lists all the Series related to the given Series

Parameter DataType Description
@SeriesID int Primary key. The ID for this series of collection events (= primary key)
Column DataType Description
SeriesID int Primary key. The ID for this series of collection events (= primary key)
SeriesParentID int The ID of the superior series of collection events
DateStart datetime Point in time when the series of collection events started
DateEnd datetime Point in time when the series of collection events ended
DateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event series comprises a period. The time of the event, if necessary.
SeriesCode nvarchar (50) The user defined code for a series of collection events
Description nvarchar (MAX) The description of the series of collection events as it will be printed on e.g. the label
Notes nvarchar (MAX) Notes on this series of collection events
Geography geography (MAX) The geography of the series of collection events

Depending on:

  • CollectionEventSeries
  • EventSeriesChildNodes
  • EventSeriesTopID

Function EventSeriesSuperiorList

Returns a table that lists all the Series above the given Series.

Parameter DataType Description
@SeriesID int Primary key. The ID for this series of collection events (= primary key)
Column DataType Description
SeriesID int Primary key. The ID for this series of collection events (= primary key)
SeriesParentID int The ID of the superior series of collection events
DateStart datetime Point in time when the series of collection events started
DateEnd datetime Point in time when the series of collection events ended
DateSupplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event series comprises a period. The time of the event, if necessary.
SeriesCode nvarchar (50) The user defined code for a series of collection events
Description nvarchar (500) The description of the series of collection events as it will be printed on e.g. the label
Notes nvarchar (500) Notes on this series of collection events
Geography geography (MAX) The geography of the series of collection events

Depending on:

  • CollectionEventSeries

Function EventSeriesTopID

Returns the top ID within the hierarchy for a given ID from the table CollectionEventSeries

DataType: int

Parameter DataType Description
@SeriesID int Primary key. The ID for this series of collection events (= primary key)

Depending on:

  • CollectionEventSeries

Function EventSpecimenNumber

calculation of all specimen in the database that are assigned to this event, including the inferior events

DataType: int

Parameter DataType Description
@EventID int The CollectionEventID for which the count should be calculated

Depending on:

  • CollectionSpecimen

Function EventSuperiorList

Returns a result set that lists all the CollectionEventIDs superior to a given event

Parameter DataType Description
@EventID int -
Column DataType Description
CollectionEventID int Refers to the ID of table CollectionEvent (= foreign key and part of primary key)
EventParentID int -
Event nchar (500) -
SpecimenCount int -

Depending on:

  • EventSpecimenNumber

Function FirstLines_4

Returns a table that lists all the specimen with the first entries of related tables

Parameter DataType Description
@CollectionSpecimenIDs varchar (8000) Comma separated list of CollectionSpecimenIDs for which the data should be retrieved
Column DataType Description
CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key)
Accession_number nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752”
Data_withholding_reason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null
Data_withholding_reason_for_collection_event nvarchar (255) -
Data_withholding_reason_for_collector nvarchar (255) If the data of the collector are withhold, the reason for withholding the data, otherwise null
Collectors_event_number nvarchar (50) Number assigned to a collection event by the collector (= ‘field number’)
Collection_day tinyint The day of the date of the event or when the collection event started
Collection_month tinyint The month of the date of the event or when the collection event started
Collection_year smallint The year of the date of the event or when the collection event started
Collection_date_supplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event comprises a period. The time of the event, if necessary.
Collection_time varchar (50) The time of the event or when the collection event started
Collection_time_span varchar (50) The time span e.g. in seconds of the collection event
Country nvarchar (50) The country where the collection event took place. Cached value derived from an geographic entry
Locality_description nvarchar (MAX) Locality description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Habitat_description nvarchar (MAX) Geo-ecological description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Collecting_method nvarchar (MAX) Description of the method used for collecting the samples, e.g. traps, moist chambers, drag net
Collection_event_notes nvarchar (MAX) Notes about the collection event
Named_area nvarchar (255) Named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
NamedAreaLocation2 nvarchar (255) Link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Remove_link_to_gazetteer int Empty column reserved to remove a link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Distance_to_location varchar (50) Distance from the specified place to the real location of the collection site (m)
Direction_to_location varchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north)
Longitude nvarchar (255) Longitude derived from WGS84 corresponding to LocalisationSystemID = 8
Latitude nvarchar (255) Latitude derived from WGS84 corresponding to LocalisationSystemID = 8
Coordinates_accuracy nvarchar (50) Accuracy of coordinates derived from WGS84 corresponding to LocalisationSystemID = 8
Link_to_GoogleMaps int Empty column reserved for retrieval of WGS84 coordinates via e.g. GoogleMaps corresponding to LocalisationSystemID = 8
_CoordinatesLocationNotes nvarchar (MAX) Notes for coordinates derived from WGS84 corresponding to LocalisationSystemID = 8
Altitude_from nvarchar (255) Lower value of altitude range corresponding to LocalisationSystemID = 4
Altitude_to nvarchar (255) Upper value of altitude range corresponding to LocalisationSystemID = 4
Altitude_accuracy nvarchar (50) Accuracy of altitude range corresponding to LocalisationSystemID = 4
Notes_for_Altitude nvarchar (MAX) Notes for altitude range corresponding to LocalisationSystemID = 4
MTB nvarchar (255) TK25 corresponding to LocalisationSystemID = 3
Quadrant nvarchar (255) Quadrant of TK25 corresponding to LocalisationSystemID = 3
Notes_for_MTB nvarchar (MAX) Notes for TK25 corresponding to LocalisationSystemID = 3
Sampling_plot nvarchar (255) Name of the sampling plot corresponding to LocalisationSystemID = 13
Link_to_SamplingPlots nvarchar (255) Link to the sampling plot corresponding to LocalisationSystemID = 13
Remove_link_to_SamplingPlots int Empty column reserverd to remove link to the sampling plot corresponding to LocalisationSystemID = 13
Accuracy_of_sampling_plot nvarchar (50) Accuracy of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Latitude_of_sampling_plot real Latitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Longitude_of_sampling_plot real Longitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Geographic_region nvarchar (255) Geographic region corresponding to LocalisationSystemID = 10
Lithostratigraphy nvarchar (255) Lithostratigraphy corresponding to LocalisationSystemID = 30
Chronostratigraphy nvarchar (255) Chronostratigraphy corresponding to LocalisationSystemID = 20
Biostratigraphy nvarchar (255) Biostratigraphy corresponding to LocalisationSystemID = 60
Collectors_name nvarchar (255) Name of the Collector
Link_to_DiversityAgents varchar (255) Link for the first collector to DiversityAgents
Remove_link_for_collector int Empty column reserved for removal of ink for the first collector
Collectors_number nvarchar (50) Number assigned to a specimen or a batch of specimens by the collector during the collection event (= ‘field number’)
Notes_about_collector nvarchar (MAX) Notes about the first collector
Accession_day tinyint The day of the date when the specimen was acquired in the collection
Accession_month tinyint The month of the date when the specimen was acquired in the collection
Accession_year smallint The year of the date when the specimen was acquired in the collection
Accession_date_supplement nvarchar (255) Verbal or additional accession date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’
Depositors_name nvarchar (255) The name of the depositor(s) (person or organization responsible for deposition). Where entire collections are deposited, this should also contain the collection name (e.g. ‘Herbarium P. Döbbler’)
Depositors_link_to_DiversityAgents varchar (255) The link for the depositor e.g. to DiversityAgents
Remove_link_for_Depositor int Empty column reserved to remove the link for the depositor e.g. to DiversityAgents
Depositors_accession_number nvarchar (50) Accession number of the specimen within the previous or original collection, e.g. ‘D-23948’
Exsiccata_abbreviation nvarchar (255) If specimen is an exsiccata: Standard abbreviation of the exsiccata (not necessarily a unique identifier; editors or publication places may change over time)
Link_to_DiversityExsiccatae varchar (255) Link to DiversityExsiccatae
Remove_link_to_exsiccatae int Empty column reserved to remove the link to DiversityExsiccatae
Exsiccata_number nvarchar (50) If specimen is an exsiccata: Number of current specimen within the exsiccata series
Original_notes nvarchar (MAX) Notes found on the label of the specimen by the original collector or from a later revision
Additional_notes nvarchar (MAX) Additional notes made by the editor of the specimen record, e.g. ‘doubtful identification/locality’
Internal_notes nvarchar (MAX) Internal notes which should not be published e.g. on websites
Label_title nvarchar (255) The title of the label e.g. for printing labels.
Label_type nvarchar (50) Printed, typewritten, typewritten with handwriting added, entirely in handwriting, etc.
Label_transcription_state nvarchar (50) The state of the transcription of a label into the database: ‘Not started’, ‘incomplete’, ‘complete’
Label_transcription_notes nvarchar (255) User defined notes on the transcription of the label into the database
Problems nvarchar (255) Description of a problem which occurred during data editing. Typically these entries should be deleted after help has been obtained. Do not enter scientific problems here; use AdditionalNotes for such permanent problems!
External_datasource int External datasource ID
External_identifier nvarchar (100) The identifier of the external specimen as defined in the external data source
Taxonomic_group nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key)
Relation_type nvarchar (50) Type of the relation between the specimen (= foreign key, see table CollRelationType_Enum)
Colonised_substrate_part nvarchar (255) If a substrate association exists: part of the substrate which is affected in the interaction (e.g. ’leaves’, if a fungus is growing on the leaves of an infected plant)
Life_stage nvarchar (255) Examples: ‘II, III’ for spore generations of rusts or ‘seed’, ‘seedling’ etc. for higher plants
Gender nvarchar (50) The sex of the organism, e.g. ‘female’
Number_of_units smallint The number of units of this organism, e.g. 400 beetles in a bottle
Circumstances nvarchar (50) Circumstances of the occurence of the organism
Order_of_taxon nvarchar (255) Order of the first taxon
Family_of_taxon nvarchar (255) Family of the first taxon
Identifier_of_organism nvarchar (50) Identifier of the first organism
Description_of_organism nvarchar (50) Description of the first organism
Only_observed bit True, if the organism was only observed rather than collected. It is therefore not present on the preserved specimen. Example: Tree under which the collected mycorrhizal fungus grew.
Notes_for_organism nvarchar (MAX) Notes for the first organism
Taxonomic_name nvarchar (255) Valid name of the species (including the taxonomic author where available). Example: ‘Rosa canina L.’
Link_to_DiversityTaxonNames varchar (255) Link for first identification of first organism to DiversityTaxonNames
Remove_link_for_identification int Empty column to remove link for first identification of first organism to DiversityTaxonNames
Vernacular_term nvarchar (255) Name or term other than a taxonomic (= scientific) name, e.g. ‘pine’, ’limestone’, ‘conifer’, ‘hardwood’
Identification_day tinyint The day of the identification
Identification_month tinyint The month of the identification
Identification_year smallint The year of the identification. The year may be empty if only the day or month are known.
Identification_category nvarchar (50) Category of the identification e.g. ‘determination’, ‘confirmation’, ‘absence’ (= foreign key, see table CollIdentificationCategory_Enum)
Identification_qualifier nvarchar (50) Qualification of the identification e.g. “cf.”," aff.", “sp. nov.” (= foreign key, see table CollIdentificationQualifier_Enum)
Type_status nvarchar (50) If identification unit is type of a taxonomic name: holotype, syntype, etc. (= foreign key, see table CollTypeStatus_Enum)
Type_notes nvarchar (MAX) Notes on the typification of this specimen
Notes_for_identification nvarchar (MAX) Notes for first identification of first organism to DiversityTaxonNames
Determiner nvarchar (255) Agent responsible for first identification of first organism
Link_to_DiversityAgents_for_determiner varchar (255) Agent for responsible for first identification of first organism to e.g. DiversityAgents
Remove_link_for_determiner int Empty column reservet to remove link for agent for responsible for first identification of first organism to e.g. DiversityAgents
Analysis nvarchar (50) First analysis of first organism
AnalysisID int ID of the analysis (primary key)
Analysis_number nvarchar (50) Number of the analysis
Analysis_result nvarchar (MAX) The result of the analysis
Taxonomic_group_of_second_organism nvarchar (50) Taxonomic group of second organism
Life_stage_of_second_organism nvarchar (255) Life stage of second organism
Gender_of_second_organism nvarchar (50) Gender of second organism
Number_of_units_of_second_organism smallint Number of units of second organism
Circumstances_of_second_organism nvarchar (50) Circumstances of second organism
Identifier_of_second_organism nvarchar (50) Identifier for second organism
Description_of_second_organism nvarchar (50) UnitDescription of second organism
Only_observed_of_second_organism bit OnlyObserved of second organism
Notes_for_second_organism nvarchar (MAX) Notes for second organism
Taxonomic_name_of_second_organism nvarchar (255) Taxonomic name of second organism
Link_to_DiversityTaxonNames_of_second_organism varchar (255) Link to DiversityTaxonNames of second organism
Remove_link_for_second_organism int Remove link to DiversityTaxonNames for second organism
Vernacular_term_of_second_organism nvarchar (255) Vernacular term of second organism
Identification_day_of_second_organism tinyint Identification day of second organism
Identification_month_of_second_organism tinyint Identification month of second organism
Identification_year_of_second_organism smallint Identification year of second organism
Identification_category_of_second_organism nvarchar (50) -
Identification_qualifier_of_second_organism nvarchar (50) -
Type_status_of_second_organism nvarchar (50) -
Type_notes_of_second_organism nvarchar (MAX) -
Notes_for_identification_of_second_organism nvarchar (MAX) -
Determiner_of_second_organism nvarchar (255) -
Link_to_DiversityAgents_for_determiner_of_second_organism varchar (255) -
Remove_link_for_determiner_of_second_organism int -
Collection int -
Material_category nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum)
Storage_location nvarchar (255) A code identifying the place where the specimen is stored within the collection. Frequently the accepted scientific name is used as storage location code.
Stock float Number of stock units, if the specimen is stored in separated units e.g. several boxes or vessels (max. 255)
Part_accession_number nvarchar (50) -
Storage_container nvarchar (500) The container in which the part is stored
Preparation_method nvarchar (MAX) The method used for the preparation of the part of the specimen, e.g. the inoculation method for cultures
Preparation_date datetime Point in time when the part was preparated e.g when it was separated from the source object
Notes_for_part nvarchar (MAX) -
Related_specimen_URL varchar (255) -
Related_specimen_display_text varchar (255) The name of a related specimen as shown e.g. in a user interface
Link_to_DiversityCollection_for_relation varchar (255) -
Type_of_relation nvarchar (50) -
Related_specimen_description nvarchar (MAX) Description of the related specimen
Related_specimen_notes nvarchar (MAX) -
Relation_is_internal bit -
_TransactionID int Unique ID for the table Transaction (= foreign key and part of primary key)
_Transaction nvarchar (200) -
_CollectionEventID int Unique ID for the table CollectionEvent (= primary key)
_IdentificationUnitID int If relation refers to a certain organism within a specimen, the ID of an IdentificationUnit (= foreign key)
_IdentificationSequence smallint The sequence of the identifications. The last identification (having the highest sequence) is regarded as valid
_SecondUnitID int -
_SecondSequence smallint -
_SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key).
_CoordinatesAverageLatitudeCache real -
_CoordinatesAverageLongitudeCache real -
_GeographicRegionPropertyURI varchar (255) -
_LithostratigraphyPropertyURI varchar (255) -
_ChronostratigraphyPropertyURI varchar (255) -
_BiostratigraphyPropertyURI varchar (255) -
_NamedAverageLatitudeCache real -
_NamedAverageLongitudeCache real -
_LithostratigraphyPropertyHierarchyCache nvarchar (MAX) -
_ChronostratigraphyPropertyHierarchyCache nvarchar (MAX) -
_BiostratigraphyPropertyHierarchyCache nvarchar (MAX) -
_SecondUnitFamilyCache nvarchar (255) -
_SecondUnitOrderCache nvarchar (255) -
_AverageAltitudeCache real Calculated altitude as parsed from the location fields

Depending on:

  • Analysis
  • CollectionAgent
  • CollectionEvent
  • CollectionEventLocalisation
  • CollectionEventProperty
  • CollectionSpecimen
  • CollectionSpecimenID_UserAvailable
  • CollectionSpecimenPart
  • CollectionSpecimenRelation
  • CollectionSpecimenTransaction
  • Identification
  • IdentificationUnit
  • IdentificationUnitAnalysis
  • Transaction

Function FirstLinesEvent_2

Returns a table that lists all the collection event with the first entries of related tables

Parameter DataType Description
@CollectionSpecimenIDs varchar (8000) Comma separated list of CollectionSpecimenIDs for which the data should be retrieved
Column DataType Description
CollectionEventID int Unique ID for the table CollectionEvent (= primary key)
Data_withholding_reason_for_collection_event nvarchar (255) If the data of the collection event are withhold, the reason for withholding the data, otherwise null
Collectors_event_number nvarchar (50) Number assigned to a collection event by the collector (= ‘field number’)
Collection_day tinyint The day of the date of the event or when the collection event started
Collection_month tinyint The month of the date of the event or when the collection event started
Collection_year smallint The year of the date of the event or when the collection event started
Collection_date_supplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event comprises a period. The time of the event, if necessary.
Collection_time varchar (50) The time of the event or when the collection event started
Collection_time_span varchar (50) The time span e.g. in seconds of the collection event
Country nvarchar (50) The country where the collection event took place. Cached value derived from an geographic entry
Locality_description nvarchar (MAX) Locality description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Habitat_description nvarchar (MAX) Geo-ecological description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Collecting_method nvarchar (MAX) Description of the method used for collecting the samples, e.g. traps, moist chambers, drag net
Collection_event_notes nvarchar (MAX) Notes about the collection event
Named_area nvarchar (255) Named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
NamedAreaLocation2 nvarchar (255) Link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Remove_link_to_gazetteer int Empty column reserved to remove a link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Distance_to_location varchar (50) Distance from the specified place to the real location of the collection site (m)
Direction_to_location varchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north)
Longitude nvarchar (255) Longitude derived from WGS84 corresponding to LocalisationSystemID = 8
Latitude nvarchar (255) Latitude derived from WGS84 corresponding to LocalisationSystemID = 8
Coordinates_accuracy nvarchar (50) Accuracy of coordinates derived from WGS84 corresponding to LocalisationSystemID = 8
Link_to_GoogleMaps int Empty column reserved for retrieval of WGS84 coordinates via e.g. GoogleMaps corresponding to LocalisationSystemID = 8
Altitude_from nvarchar (255) Lower value of altitude range corresponding to LocalisationSystemID = 4
Altitude_to nvarchar (255) Upper value of altitude range corresponding to LocalisationSystemID = 4
Altitude_accuracy nvarchar (50) Accuracy of altitude range corresponding to LocalisationSystemID = 4
MTB nvarchar (255) TK25 corresponding to LocalisationSystemID = 3
Quadrant nvarchar (255) Quadrant of TK25 corresponding to LocalisationSystemID = 3
Notes_for_MTB nvarchar (MAX) Notes for TK25 corresponding to LocalisationSystemID = 3
MTB_accuracy nvarchar (50) -
Sampling_plot nvarchar (255) Name of the sampling plot corresponding to LocalisationSystemID = 13
Link_to_SamplingPlots nvarchar (255) Link to the sampling plot corresponding to LocalisationSystemID = 13
Remove_link_to_SamplingPlots int Empty column reserverd to remove link to the sampling plot corresponding to LocalisationSystemID = 13
Accuracy_of_sampling_plot nvarchar (50) Accuracy of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Latitude_of_sampling_plot real Latitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Longitude_of_sampling_plot real Longitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Geographic_region nvarchar (255) Geographic region corresponding to LocalisationSystemID = 10
Lithostratigraphy nvarchar (255) Lithostratigraphy corresponding to LocalisationSystemID = 30
Chronostratigraphy nvarchar (255) Chronostratigraphy corresponding to LocalisationSystemID = 20
_CollectionEventID int Unique ID for the table CollectionEvent (= primary key)
_CoordinatesAverageLatitudeCache real Average Latitude of WGS84 Coordinates
_CoordinatesAverageLongitudeCache real Average Longitude of WGS84 Coordinates
_CoordinatesLocationNotes nvarchar (MAX) Notes for WGS84 Coordinates
_GeographicRegionPropertyURI varchar (255) URI of Geographic Region
_LithostratigraphyPropertyURI varchar (255) URI for Lithostratigraphy
_ChronostratigraphyPropertyURI varchar (255) URI for Chronostratigraphy
_NamedAverageLatitudeCache real Average Latitude for Named Area
_NamedAverageLongitudeCache real Average Longitude for Named Area
_LithostratigraphyPropertyHierarchyCache nvarchar (MAX) Hierarchy for Lithostratigraphy
_ChronostratigraphyPropertyHierarchyCache nvarchar (MAX) Hierarchy for Chronostratigraphy
_AverageAltitudeCache real Average Altitude

Depending on:

  • CollectionEvent
  • CollectionEventLocalisation
  • CollectionEventProperty
  • CollectionSpecimen
  • CollectionSpecimenID_UserAvailable

Function FirstLinesPart_2

Returns a table that lists all the collection specimen part with the first entries of related tables

Parameter DataType Description
@CollectionSpecimenIDs varchar (8000) Comma separated list of CollectionSpecimenIDs for which the data should be retrieved
@AnalysisIDs varchar (8000) Comma separated list of AnalysisIDs for which the data should be retrieved
@AnalysisStartDate date The start date of the range for analysis
@AnalysisEndDate date The end date of the range for analysis
@ProcessingID int ID of the processing method. Refers to ProcessingID in table Processing (foreign key)
@ProcessingStartDate datetime The start date of the range for processing
@ProcessingEndDate datetime The end date of the range for processing
Column DataType Description
SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key).
CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key)
Accession_number nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752”
Data_withholding_reason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null
Data_withholding_reason_for_collection_event nvarchar (255) If the data of the collection event are withhold, the reason for withholding the data, otherwise null
Data_withholding_reason_for_collector nvarchar (255) If the data of the collector are withhold, the reason for withholding the data, otherwise null
Collectors_event_number nvarchar (50) Number assigned to a collection event by the collector (= ‘field number’)
Collection_day tinyint The day of the date of the event or when the collection event started
Collection_month tinyint The month of the date of the event or when the collection event started
Collection_year smallint The year of the date of the event or when the collection event started
Collection_date_supplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event comprises a period. The time of the event, if necessary.
Collection_time varchar (50) The time of the event or when the collection event started
Collection_time_span varchar (50) The time span e.g. in seconds of the collection event
Country nvarchar (50) The country where the collection event took place. Cached value derived from an geographic entry
Locality_description nvarchar (255) Locality description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Habitat_description nvarchar (255) Geo-ecological description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Collecting_method nvarchar (255) Description of the method used for collecting the samples, e.g. traps, moist chambers, drag net
Collection_event_notes nvarchar (255) Notes about the collection event
Named_area nvarchar (255) Named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
NamedAreaLocation2 nvarchar (255) Link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Remove_link_to_gazetteer int Empty column reserved to remove a link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Distance_to_location varchar (50) Distance from the specified place to the real location of the collection site (m)
Direction_to_location varchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north)
Longitude nvarchar (255) Longitude derived from WGS84 corresponding to LocalisationSystemID = 8
Latitude nvarchar (255) Latitude derived from WGS84 corresponding to LocalisationSystemID = 8
Coordinates_accuracy nvarchar (50) Accuracy of coordinates derived from WGS84 corresponding to LocalisationSystemID = 8
Link_to_GoogleMaps int Empty column reserved for retrieval of WGS84 coordinates via e.g. GoogleMaps corresponding to LocalisationSystemID = 8
Altitude_from nvarchar (255) Lower value of altitude range corresponding to LocalisationSystemID = 4
Altitude_to nvarchar (255) Upper value of altitude range corresponding to LocalisationSystemID = 4
Altitude_accuracy nvarchar (50) Accuracy of altitude range corresponding to LocalisationSystemID = 4
Notes_for_Altitude nvarchar (255) Notes for altitude range corresponding to LocalisationSystemID = 4
MTB nvarchar (255) TK25 corresponding to LocalisationSystemID = 3
Quadrant nvarchar (255) Quadrant of TK25 corresponding to LocalisationSystemID = 3
Notes_for_MTB nvarchar (255) Notes for TK25 corresponding to LocalisationSystemID = 3
Sampling_plot nvarchar (255) Name of the sampling plot corresponding to LocalisationSystemID = 13
Link_to_SamplingPlots nvarchar (255) Link to the sampling plot corresponding to LocalisationSystemID = 13
Remove_link_to_SamplingPlots int Empty column reserverd to remove link to the sampling plot corresponding to LocalisationSystemID = 13
Accuracy_of_sampling_plot nvarchar (50) Accuracy of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Latitude_of_sampling_plot real Latitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Longitude_of_sampling_plot real Longitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Geographic_region nvarchar (255) Geographic region corresponding to LocalisationSystemID = 10
Lithostratigraphy nvarchar (255) Lithostratigraphy corresponding to LocalisationSystemID = 30
Chronostratigraphy nvarchar (255) Chronostratigraphy corresponding to LocalisationSystemID = 20
Collectors_name nvarchar (255) Name of the Collector
Link_to_DiversityAgents varchar (255) Link for the first collector to DiversityAgents
Remove_link_for_collector int -
Collectors_number nvarchar (50) Number assigned to a specimen or a batch of specimens by the collector during the collection event (= ‘field number’)
Notes_about_collector nvarchar (MAX) Notes about the first collector
Accession_day tinyint The day of the date when the specimen was acquired in the collection
Accession_month tinyint The month of the date when the specimen was acquired in the collection
Accession_year smallint The year of the date when the specimen was acquired in the collection
Accession_date_supplement nvarchar (255) Verbal or additional accession date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’
Depositors_name nvarchar (255) The name of the depositor(s) (person or organization responsible for deposition). Where entire collections are deposited, this should also contain the collection name (e.g. ‘Herbarium P. Döbbler’)
Depositors_link_to_DiversityAgents varchar (255) The link for the depositor e.g. to DiversityAgents
Remove_link_for_Depositor int Empty column reserved to remove the link for the depositor e.g. to DiversityAgents
Depositors_accession_number nvarchar (50) Accession number of the specimen within the previous or original collection, e.g. ‘D-23948’
Exsiccata_abbreviation nvarchar (255) If specimen is an exsiccata: Standard abbreviation of the exsiccata (not necessarily a unique identifier; editors or publication places may change over time)
Link_to_DiversityExsiccatae varchar (255) Link to DiversityExsiccatae
Remove_link_to_exsiccatae int Empty column reserved to remove the link to DiversityExsiccatae
Exsiccata_number nvarchar (50) If specimen is an exsiccata: Number of current specimen within the exsiccata series
Original_notes nvarchar (MAX) Notes found on the label of the specimen by the original collector or from a later revision
Additional_notes nvarchar (MAX) Additional notes made by the editor of the specimen record, e.g. ‘doubtful identification/locality’
Internal_notes nvarchar (MAX) Internal notes which should not be published e.g. on websites
Label_title nvarchar (255) The title of the label e.g. for printing labels.
Label_type nvarchar (50) Printed, typewritten, typewritten with handwriting added, entirely in handwriting, etc.
Label_transcription_state nvarchar (50) The state of the transcription of a label into the database: ‘Not started’, ‘incomplete’, ‘complete’
Label_transcription_notes nvarchar (255) User defined notes on the transcription of the label into the database
Problems nvarchar (255) Description of a problem which occurred during data editing. Typically these entries should be deleted after help has been obtained. Do not enter scientific problems here; use AdditionalNotes for such permanent problems!
Taxonomic_group nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key)
Relation_type nvarchar (50) The relation of a unit to its substrate, e.g. parasitism, symbiosis etc. as stored in CollRelationType_Enum (= foreign key)
Colonised_substrate_part nvarchar (255) If a substrate association exists: part of the substrate which is affected in the interaction (e.g. ’leaves’, if a fungus is growing on the leaves of an infected plant)
Related_organism nvarchar (200) Last identification of the related organism
Life_stage nvarchar (255) Examples: ‘II, III’ for spore generations of rusts or ‘seed’, ‘seedling’ etc. for higher plants
Gender nvarchar (50) The sex of the organism, e.g. ‘female’
Number_of_units smallint The number of units of this organism, e.g. 400 beetles in a bottle
Circumstances nvarchar (50) Circumstances of the occurence of the organism
Order_of_taxon nvarchar (255) Order of the first taxon
Family_of_taxon nvarchar (255) Family of the first taxon
Identifier_of_organism nvarchar (50) Identifier of the first organism
Description_of_organism nvarchar (50) Description of the first organism
Only_observed bit True, if the organism was only observed rather than collected. It is therefore not present on the preserved specimen. Example: Tree under which the collected mycorrhizal fungus grew.
Notes_for_organism nvarchar (MAX) Notes for the first organism
Taxonomic_name nvarchar (255) Valid name of the species (including the taxonomic author where available). Example: ‘Rosa canina L.’
Link_to_DiversityTaxonNames varchar (255) Link for first identification of first organism to DiversityTaxonNames
Remove_link_for_identification int Empty column to remove link for first identification of first organism to DiversityTaxonNames
Vernacular_term nvarchar (255) Name or term other than a taxonomic (= scientific) name, e.g. ‘pine’, ’limestone’, ‘conifer’, ‘hardwood’
Identification_day tinyint The day of the identification
Identification_month tinyint The month of the identification
Identification_year smallint The year of the identification. The year may be empty if only the day or month are known.
Identification_category nvarchar (50) Category of the identification e.g. ‘determination’, ‘confirmation’, ‘absence’ (= foreign key, see table CollIdentificationCategory_Enum)
Identification_qualifier nvarchar (50) Qualification of the identification e.g. “cf.”," aff.", “sp. nov.” (= foreign key, see table CollIdentificationQualifier_Enum)
Type_status nvarchar (50) If identification unit is type of a taxonomic name: holotype, syntype, etc. (= foreign key, see table CollTypeStatus_Enum)
Type_notes nvarchar (MAX) Notes on the typification of this specimen
Notes_for_identification nvarchar (MAX) Notes for first identification of first organism to DiversityTaxonNames
Determiner nvarchar (255) Agent responsible for first identification of first organism
Link_to_DiversityAgents_for_determiner varchar (255) Agent for responsible for first identification of first organism to e.g. DiversityAgents
Remove_link_for_determiner int Empty column reservet to remove link for agent for responsible for first identification of first organism to e.g. DiversityAgents
Analysis_0 nvarchar (50) Name of analysis 0 according to list of AnalysisIDs
AnalysisID_0 int ID of analysis 0 according to list of AnalysisIDs
Analysis_number_0 nvarchar (50) Number of analysis 0 according to list of AnalysisIDs
Analysis_result_0 nvarchar (MAX) Result of analysis 0 according to list of AnalysisIDs
Analysis_1 nvarchar (50) Name of analysis_1 according to list of AnalysisIDs
AnalysisID_1 int ID of analysis_1 according to list of AnalysisIDs
Analysis_number_1 nvarchar (50) Number of analysis_1 according to list of AnalysisIDs
Analysis_result_1 nvarchar (MAX) Result of analysis_1 according to list of AnalysisIDs
Analysis_2 nvarchar (50) Name of analysis_2 according to list of AnalysisIDs
AnalysisID_2 int ID of analysis_2 according to list of AnalysisIDs
Analysis_number_2 nvarchar (50) Number of analysis_2 according to list of AnalysisIDs
Analysis_result_2 nvarchar (MAX) Result of analysis_2 according to list of AnalysisIDs
Analysis_3 nvarchar (50) Name of analysis_3 according to list of AnalysisIDs
AnalysisID_3 int ID of analysis_3 according to list of AnalysisIDs
Analysis_number_3 nvarchar (50) Number of analysis_3 according to list of AnalysisIDs
Analysis_result_3 nvarchar (MAX) Result of analysis_3 according to list of AnalysisIDs
Analysis_4 nvarchar (50) Name of analysis_4 according to list of AnalysisIDs
AnalysisID_4 int ID of analysis_4 according to list of AnalysisIDs
Analysis_number_4 nvarchar (50) Number of analysis_4 according to list of AnalysisIDs
Analysis_result_4 nvarchar (MAX) Result of analysis_4 according to list of AnalysisIDs
Analysis_5 nvarchar (50) Name of analysis_5 according to list of AnalysisIDs
AnalysisID_5 int ID of analysis_5 according to list of AnalysisIDs
Analysis_number_5 nvarchar (50) Number of analysis_5 according to list of AnalysisIDs
Analysis_result_5 nvarchar (MAX) Result of analysis_5 according to list of AnalysisIDs
Analysis_6 nvarchar (50) Name of analysis_6 according to list of AnalysisIDs
AnalysisID_6 int ID of analysis_6 according to list of AnalysisIDs
Analysis_number_6 nvarchar (50) Number of analysis_6 according to list of AnalysisIDs
Analysis_result_6 nvarchar (MAX) Result of analysis_6 according to list of AnalysisIDs
Analysis_7 nvarchar (50) Name of analysis_7 according to list of AnalysisIDs
AnalysisID_7 int ID of analysis_7 according to list of AnalysisIDs
Analysis_number_7 nvarchar (50) Number of analysis_7 according to list of AnalysisIDs
Analysis_result_7 nvarchar (MAX) Result of analysis_7 according to list of AnalysisIDs
Analysis_8 nvarchar (50) Name of analysis_8 according to list of AnalysisIDs
AnalysisID_8 int ID of analysis_8 according to list of AnalysisIDs
Analysis_number_8 nvarchar (50) Number of analysis_8 according to list of AnalysisIDs
Analysis_result_8 nvarchar (MAX) Result of analysis_8 according to list of AnalysisIDs
Analysis_9 nvarchar (50) Name of analysis_9 according to list of AnalysisIDs
AnalysisID_9 int ID of analysis_9 according to list of AnalysisIDs
Analysis_number_9 nvarchar (50) Number of analysis_9 according to list of AnalysisIDs
Analysis_result_9 nvarchar (MAX) Result of analysis_9 according to list of AnalysisIDs
Preparation_method nvarchar (MAX) The method used for the preparation of the part of the specimen, e.g. the inoculation method for cultures
Preparation_date datetime Point in time when the part was preparated e.g when it was separated from the source object
Part_accession_number nvarchar (50) Accession number of part
Part_sublabel nvarchar (50) The label for a part of a specimen, e.g. “cone”, or a number attached to a duplicate of a specimen
Collection int ID of the Collection
Material_category nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum)
Storage_location nvarchar (255) A code identifying the place where the specimen is stored within the collection. Frequently the accepted scientific name is used as storage location code.
Storage_container nvarchar (500) The container in which the part is stored
Stock float Number of stock units, if the specimen is stored in separated units e.g. several boxes or vessels (max. 255)
Stock_unit nvarchar (50) If empty, the stock is given as a count, else it contains the unit in which stock is expressed, e.g. µl, ml, kg etc.
Notes_for_part nvarchar (MAX) Notes for specimen part
Description_of_unit_in_part nvarchar (500) Description of identification unit in specimen part
Processing_date_1 datetime Date of Processing_1 according to list of ProcessingIDs
ProcessingID_1 int ID of Processing_1 according to list of ProcessingIDs
Processing_Protocoll_1 nvarchar (100) Protocoll of Processing_1 according to list of ProcessingIDs
Processing_duration_1 varchar (50) Duration of Processing_1 according to list of ProcessingIDs
Processing_notes_1 nvarchar (MAX) Notes of Processing_1 according to list of ProcessingIDs
Processing_date_2 datetime Date of Processing_2 according to list of ProcessingIDs
ProcessingID_2 int ID of Processing_2 according to list of ProcessingIDs
Processing_Protocoll_2 nvarchar (100) Protocoll of Processing_2 according to list of ProcessingIDs
Processing_duration_2 varchar (50) Duration of Processing_2 according to list of ProcessingIDs
Processing_notes_2 nvarchar (MAX) Notes of Processing_2 according to list of ProcessingIDs
Processing_date_3 datetime Date of Processing_3 according to list of ProcessingIDs
ProcessingID_3 int ID of Processing_3 according to list of ProcessingIDs
Processing_Protocoll_3 nvarchar (100) Protocoll of Processing_3 according to list of ProcessingIDs
Processing_duration_3 varchar (50) Duration of Processing_3 according to list of ProcessingIDs
Processing_notes_3 nvarchar (MAX) Notes of Processing_3 according to list of ProcessingIDs
Processing_date_4 datetime Date of Processing_4 according to list of ProcessingIDs
ProcessingID_4 int ID of Processing_4 according to list of ProcessingIDs
Processing_Protocoll_4 nvarchar (100) Protocoll of Processing_4 according to list of ProcessingIDs
Processing_duration_4 varchar (50) Duration of Processing_4 according to list of ProcessingIDs
Processing_notes_4 nvarchar (MAX) Notes of Processing_4 according to list of ProcessingIDs
Processing_date_5 datetime Date of Processing_5 according to list of ProcessingIDs
ProcessingID_5 int ID of Processing_5 according to list of ProcessingIDs
Processing_Protocoll_5 nvarchar (100) Protocoll of Processing_5 according to list of ProcessingIDs
Processing_duration_5 varchar (50) Duration of Processing_5 according to list of ProcessingIDs
Processing_notes_5 nvarchar (MAX) Notes of Processing_5 according to list of ProcessingIDs
_TransactionID int Unique ID for the table Transaction (= foreign key and part of primary key)
_Transaction nvarchar (200) Title of first transaction
On_loan int If part is on loan according to first transaction
_CollectionEventID int Unique ID for the table CollectionEvent (= primary key)
_IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key)
_IdentificationSequence smallint The sequence of the identifications. The last identification (having the highest sequence) is regarded as valid
_SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key).
_CoordinatesAverageLatitudeCache real Average Latitude of WGS84 Coordinates
_CoordinatesAverageLongitudeCache real Average Longitude of WGS84 Coordinates
_CoordinatesLocationNotes nvarchar (255) Notes for WGS84 Coordinates
_GeographicRegionPropertyURI varchar (255) URI of Geographic Region
_LithostratigraphyPropertyURI varchar (255) URI for Lithostratigraphy
_ChronostratigraphyPropertyURI varchar (255) URI for Chronostratigraphy
_NamedAverageLatitudeCache real Average Latitude for Named Area
_NamedAverageLongitudeCache real Average Longitude for Named Area
_LithostratigraphyPropertyHierarchyCache nvarchar (255) Hierarchy for Lithostratigraphy
_ChronostratigraphyPropertyHierarchyCache nvarchar (255) Hierarchy for Chronostratigraphy
_AverageAltitudeCache real Calculated average altitude as parsed from the location fields

Depending on:

  • Analysis
  • CollectionAgent
  • CollectionEvent
  • CollectionEventLocalisation
  • CollectionEventProperty
  • CollectionSpecimen
  • CollectionSpecimenID_UserAvailable
  • CollectionSpecimenPart
  • CollectionSpecimenProcessing
  • CollectionSpecimenTransaction
  • Identification
  • IdentificationUnit
  • IdentificationUnitAnalysis
  • IdentificationUnitInPart
  • Processing
  • Transaction

Function FirstLinesSeries

Returns a table that lists all the collection event series with the first entries of related tables

Parameter DataType Description
@CollectionSpecimenIDs varchar (8000) Comma separated list of CollectionSpecimenIDs for which the data should be retrieved
Column DataType Description
SeriesID int The ID of the related expedition. Relates to the PK of the table CollectionExpedition (foreign key).
SeriesParentID int The ID of the superior series of collection events
Description nvarchar (500) The description of the series of collection events as it will be printed on e.g. the label
SeriesCode nvarchar (50) The user defined code for a series of collection events
Geography geography (MAX) The geography of the series of collection events
Notes nvarchar (500) Notes on the collection event
DateStart datetime Point in time when the series of collection events started
DateEnd datetime Point in time when the series of collection events ended

Depending on:

  • CollectionEvent
  • CollectionEventSeries
  • CollectionSpecimen
  • CollectionSpecimenID_UserAvailable

Function FirstLinesUnit_4

Returns a table that lists all the identification unit with the first entries of related tables

Parameter DataType Description
@CollectionSpecimenIDs varchar (8000) Comma separated list of CollectionSpecimenIDs for which the data should be retrieved
@AnalysisIDs varchar (8000) Comma separated list of AnalysisIDs for which the data should be retrieved
@AnalysisStartDate date The start date of the range for analysis
@AnalysisEndDate date The end date of the range for analysis
Column DataType Description
IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key)
CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key)
Accession_number nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752”
Data_withholding_reason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null
Data_withholding_reason_for_collection_event nvarchar (255) If the data of the collection event are withhold, the reason for withholding the data, otherwise null
Data_withholding_reason_for_collector nvarchar (255) If the data of the collector are withhold, the reason for withholding the data, otherwise null
Collectors_event_number nvarchar (50) Number assigned to a collection event by the collector (= ‘field number’)
Collection_day tinyint The day of the date of the event or when the collection event started
Collection_month tinyint The month of the date of the event or when the collection event started
Collection_year smallint The year of the date of the event or when the collection event started
Collection_date_supplement nvarchar (100) Verbal or additional collection date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’. The end date, if the collection event comprises a period. The time of the event, if necessary.
Collection_time varchar (50) The time of the event or when the collection event started
Collection_time_span varchar (50) The time span e.g. in seconds of the collection event
Country nvarchar (50) -
Locality_description nvarchar (255) Locality description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Habitat_description nvarchar (255) Geo-ecological description of the locality exactly as written on the original label (i.e. without corrections during data entry)
Collecting_method nvarchar (255) Description of the method used for collecting the samples, e.g. traps, moist chambers, drag net
Collection_event_notes nvarchar (255) Notes about the collection event
Named_area nvarchar (255) Named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
NamedAreaLocation2 nvarchar (255) Link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Remove_link_to_gazetteer int Empty column reserved to remove a link to a named area as e.g. derived from DiversityGazetteer corresponding to LocalisationSystemID = 7
Distance_to_location varchar (50) Distance from the specified place to the real location of the collection site (m)
Direction_to_location varchar (50) Direction from the specified place to the real location of the collection site (Degrees rel. to north)
Longitude nvarchar (255) Longitude derived from WGS84 corresponding to LocalisationSystemID = 8
Latitude nvarchar (255) Latitude derived from WGS84 corresponding to LocalisationSystemID = 8
Coordinates_accuracy nvarchar (50) Accuracy of coordinates derived from WGS84 corresponding to LocalisationSystemID = 8
Link_to_GoogleMaps int Empty column reserved for retrieval of WGS84 coordinates via e.g. GoogleMaps corresponding to LocalisationSystemID = 8
Altitude_from nvarchar (255) Lower value of altitude range corresponding to LocalisationSystemID = 4
Altitude_to nvarchar (255) Upper value of altitude range corresponding to LocalisationSystemID = 4
Altitude_accuracy nvarchar (50) Accuracy of altitude range corresponding to LocalisationSystemID = 4
Notes_for_Altitude nvarchar (255) Notes for altitude range corresponding to LocalisationSystemID = 4
MTB nvarchar (255) TK25 corresponding to LocalisationSystemID = 3
Quadrant nvarchar (255) Quadrant of TK25 corresponding to LocalisationSystemID = 3
Notes_for_MTB nvarchar (255) Notes for TK25 corresponding to LocalisationSystemID = 3
Sampling_plot nvarchar (255) Name of the sampling plot corresponding to LocalisationSystemID = 13
Link_to_SamplingPlots nvarchar (255) Link to the sampling plot corresponding to LocalisationSystemID = 13
Remove_link_to_SamplingPlots int Empty column reserverd to remove link to the sampling plot corresponding to LocalisationSystemID = 13
Accuracy_of_sampling_plot nvarchar (50) Accuracy of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Latitude_of_sampling_plot real Latitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Longitude_of_sampling_plot real Longitude of the sampling plot coordinates corresponding to LocalisationSystemID = 13
Geographic_region nvarchar (255) Geographic region corresponding to LocalisationSystemID = 10
Lithostratigraphy nvarchar (255) Lithostratigraphy corresponding to LocalisationSystemID = 30
Chronostratigraphy nvarchar (255) Chronostratigraphy corresponding to LocalisationSystemID = 20
Collectors_name nvarchar (255) Name of the Collector
Link_to_DiversityAgents varchar (255) Link for the first collector to DiversityAgents
Remove_link_for_collector int Empty column reserved for removal of ink for the first collector
Collectors_number nvarchar (50) Number assigned to a specimen or a batch of specimens by the collector during the collection event (= ‘field number’)
Notes_about_collector nvarchar (MAX) Notes about the first collector
Accession_day tinyint The day of the date when the specimen was acquired in the collection
Accession_month tinyint The month of the date when the specimen was acquired in the collection
Accession_year smallint The year of the date when the specimen was acquired in the collection
Accession_date_supplement nvarchar (255) Verbal or additional accession date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’
Depositors_name nvarchar (255) The name of the depositor(s) (person or organization responsible for deposition). Where entire collections are deposited, this should also contain the collection name (e.g. ‘Herbarium P. Döbbler’)
Depositors_link_to_DiversityAgents varchar (255) The link for the depositor e.g. to DiversityAgents
Remove_link_for_Depositor int Empty column reserved to remove the link for the depositor e.g. to DiversityAgents
Depositors_accession_number nvarchar (50) Accession number of the specimen within the previous or original collection, e.g. ‘D-23948’
Exsiccata_abbreviation nvarchar (255) If specimen is an exsiccata: Standard abbreviation of the exsiccata (not necessarily a unique identifier; editors or publication places may change over time)
Link_to_DiversityExsiccatae varchar (255) Link to DiversityExsiccatae
Remove_link_to_exsiccatae int Empty column reserved to remove the link to DiversityExsiccatae
Exsiccata_number nvarchar (50) If specimen is an exsiccata: Number of current specimen within the exsiccata series
Original_notes nvarchar (MAX) Notes found on the label of the specimen by the original collector or from a later revision
Additional_notes nvarchar (MAX) Additional notes made by the editor of the specimen record, e.g. ‘doubtful identification/locality’
Internal_notes nvarchar (MAX) Internal notes which should not be published e.g. on websites
Label_title nvarchar (255) The title of the label e.g. for printing labels.
Label_type nvarchar (50) Printed, typewritten, typewritten with handwriting added, entirely in handwriting, etc.
Label_transcription_state nvarchar (50) The state of the transcription of a label into the database: ‘Not started’, ‘incomplete’, ‘complete’
Label_transcription_notes nvarchar (255) User defined notes on the transcription of the label into the database
Problems nvarchar (255) Description of a problem which occurred during data editing. Typically these entries should be deleted after help has been obtained. Do not enter scientific problems here; use AdditionalNotes for such permanent problems!
Taxonomic_group nvarchar (50) Taxonomic group the organism, identified by this unit, belongs to. Groups listed in table CollTaxonomicGroup_Enum (= foreign key)
Relation_type nvarchar (50) The relation of a unit to its substrate, e.g. parasitism, symbiosis etc. as stored in CollRelationType_Enum (= foreign key)
Colonised_substrate_part nvarchar (255) If a substrate association exists: part of the substrate which is affected in the interaction (e.g. ’leaves’, if a fungus is growing on the leaves of an infected plant)
Related_organism nvarchar (200) Last identification of the related organism
Life_stage nvarchar (255) Examples: ‘II, III’ for spore generations of rusts or ‘seed’, ‘seedling’ etc. for higher plants
Gender nvarchar (50) The sex of the organism, e.g. ‘female’
Number_of_units smallint The number of units of this organism, e.g. 400 beetles in a bottle
Circumstances nvarchar (50) Circumstances of the occurence of the organism
Order_of_taxon nvarchar (255) Order of the first taxon
Family_of_taxon nvarchar (255) Family of the first taxon
Identifier_of_organism nvarchar (50) Identifier of the first organism
Description_of_organism nvarchar (50) Description of the first organism
Only_observed bit True, if the organism was only observed rather than collected. It is therefore not present on the preserved specimen. Example: Tree under which the collected mycorrhizal fungus grew.
Notes_for_organism nvarchar (MAX) Notes for the first organism
Taxonomic_name nvarchar (255) Valid name of the species (including the taxonomic author where available). Example: ‘Rosa canina L.’
Link_to_DiversityTaxonNames varchar (255) Link for first identification of first organism to DiversityTaxonNames
Remove_link_for_identification int Empty column to remove link for first identification of first organism to DiversityTaxonNames
Vernacular_term nvarchar (255) Name or term other than a taxonomic (= scientific) name, e.g. ‘pine’, ’limestone’, ‘conifer’, ‘hardwood’
Identification_day tinyint The day of the identification
Identification_month tinyint The month of the identification
Identification_year smallint The year of the identification. The year may be empty if only the day or month are known.
Identification_category nvarchar (50) Category of the identification e.g. ‘determination’, ‘confirmation’, ‘absence’ (= foreign key, see table CollIdentificationCategory_Enum)
Identification_qualifier nvarchar (50) Qualification of the identification e.g. “cf.”," aff.", “sp. nov.” (= foreign key, see table CollIdentificationQualifier_Enum)
Type_status nvarchar (50) If identification unit is type of a taxonomic name: holotype, syntype, etc. (= foreign key, see table CollTypeStatus_Enum)
Type_notes nvarchar (MAX) Notes on the typification of this specimen
Notes_for_identification nvarchar (MAX) Notes for first identification of first organism to DiversityTaxonNames
Determiner nvarchar (255) Agent responsible for first identification of first organism
Link_to_DiversityAgents_for_determiner varchar (255) Agent for responsible for first identification of first organism to e.g. DiversityAgents
Remove_link_for_determiner int Empty column reservet to remove link for agent for responsible for first identification of first organism to e.g. DiversityAgents
Analysis_0 nvarchar (50) Name of analysis 0 according to list of AnalysisIDs
AnalysisID_0 int ID of analysis 0 according to list of AnalysisIDs
Analysis_number_0 nvarchar (50) Number of analysis 0 according to list of AnalysisIDs
Analysis_result_0 nvarchar (MAX) Result of analysis 0 according to list of AnalysisIDs
Analysis_1 nvarchar (50) Name of analysis_1 according to list of AnalysisIDs
AnalysisID_1 int ID of analysis_1 according to list of AnalysisIDs
Analysis_number_1 nvarchar (50) Number of analysis_1 according to list of AnalysisIDs
Analysis_result_1 nvarchar (MAX) Result of analysis_1 according to list of AnalysisIDs
Analysis_2 nvarchar (50) Name of analysis_2 according to list of AnalysisIDs
AnalysisID_2 int ID of analysis_2 according to list of AnalysisIDs
Analysis_number_2 nvarchar (50) Number of analysis_2 according to list of AnalysisIDs
Analysis_result_2 nvarchar (MAX) Result of analysis_2 according to list of AnalysisIDs
Analysis_3 nvarchar (50) Name of analysis_3 according to list of AnalysisIDs
AnalysisID_3 int ID of analysis_3 according to list of AnalysisIDs
Analysis_number_3 nvarchar (50) Number of analysis_3 according to list of AnalysisIDs
Analysis_result_3 nvarchar (MAX) Result of analysis_3 according to list of AnalysisIDs
Analysis_4 nvarchar (50) Name of analysis_4 according to list of AnalysisIDs
AnalysisID_4 int ID of analysis_4 according to list of AnalysisIDs
Analysis_number_4 nvarchar (50) Number of analysis_4 according to list of AnalysisIDs
Analysis_result_4 nvarchar (MAX) Result of analysis_4 according to list of AnalysisIDs
Analysis_5 nvarchar (50) Name of analysis_5 according to list of AnalysisIDs
AnalysisID_5 int ID of analysis_5 according to list of AnalysisIDs
Analysis_number_5 nvarchar (50) Number of analysis_5 according to list of AnalysisIDs
Analysis_result_5 nvarchar (MAX) Result of analysis_5 according to list of AnalysisIDs
Analysis_6 nvarchar (50) Name of analysis_6 according to list of AnalysisIDs
AnalysisID_6 int ID of analysis_6 according to list of AnalysisIDs
Analysis_number_6 nvarchar (50) Number of analysis_6 according to list of AnalysisIDs
Analysis_result_6 nvarchar (MAX) Result of analysis_6 according to list of AnalysisIDs
Analysis_7 nvarchar (50) Name of analysis_7 according to list of AnalysisIDs
AnalysisID_7 int ID of analysis_7 according to list of AnalysisIDs
Analysis_number_7 nvarchar (50) Number of analysis_7 according to list of AnalysisIDs
Analysis_result_7 nvarchar (MAX) Result of analysis_7 according to list of AnalysisIDs
Analysis_8 nvarchar (50) Name of analysis_8 according to list of AnalysisIDs
AnalysisID_8 int ID of analysis_8 according to list of AnalysisIDs
Analysis_number_8 nvarchar (50) Number of analysis_8 according to list of AnalysisIDs
Analysis_result_8 nvarchar (MAX) Result of analysis_8 according to list of AnalysisIDs
Analysis_9 nvarchar (50) Name of analysis_9 according to list of AnalysisIDs
AnalysisID_9 int ID of analysis_9 according to list of AnalysisIDs
Analysis_number_9 nvarchar (50) Number of analysis_9 according to list of AnalysisIDs
Analysis_result_9 nvarchar (MAX) Result of analysis_9 according to list of AnalysisIDs
Collection int -
Material_category nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc. (= foreign key, see table CollMaterialCategory_Enum)
Storage_location nvarchar (255) A code identifying the place where the specimen is stored within the collection. Frequently the accepted scientific name is used as storage location code.
Stock float Number of stock units, if the specimen is stored in separated units e.g. several boxes or vessels (max. 255)
Preparation_method nvarchar (MAX) The method used for the preparation of the part of the specimen, e.g. the inoculation method for cultures
Preparation_date datetime Point in time when the part was preparated e.g when it was separated from the source object
Notes_for_part nvarchar (MAX) Notes for specimen part
_TransactionID int Unique ID for the table Transaction (= foreign key and part of primary key)
_Transaction nvarchar (200) Title of first transaction
On_loan int If part is on loan according to first transaction
_CollectionEventID int Unique ID for the table CollectionEvent (= primary key)
_IdentificationUnitID int Refers to the ID of IdentficationUnit (= foreign key and part of primary key)
_IdentificationSequence smallint The sequence of the identifications. The last identification (having the highest sequence) is regarded as valid
_SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key).
_CoordinatesAverageLatitudeCache real Average Latitude of WGS84 Coordinates
_CoordinatesAverageLongitudeCache real Average Longitude of WGS84 Coordinates
_CoordinatesLocationNotes nvarchar (255) Notes for WGS84 Coordinates
_GeographicRegionPropertyURI varchar (255) URI of Geographic Region
_LithostratigraphyPropertyURI varchar (255) URI for Lithostratigraphy
_ChronostratigraphyPropertyURI varchar (255) URI for Chronostratigraphy
_NamedAverageLatitudeCache real Average Latitude for Named Area
_NamedAverageLongitudeCache real Average Longitude for Named Area
_LithostratigraphyPropertyHierarchyCache nvarchar (255) Hierarchy for Lithostratigraphy
_ChronostratigraphyPropertyHierarchyCache nvarchar (255) Hierarchy for Chronostratigraphy
_AverageAltitudeCache real Average Altitude

Depending on:

  • Analysis
  • CollectionAgent
  • CollectionEvent
  • CollectionEventLocalisation
  • CollectionEventProperty
  • CollectionSpecimen
  • CollectionSpecimenID_UserAvailable
  • CollectionSpecimenPart
  • CollectionSpecimenTransaction
  • Identification
  • IdentificationUnit
  • IdentificationUnitAnalysis
  • Transaction

Function LocalisationSystem_List

Parameter DataType Description
@LanguageCode char (2) -
Column DataType Description
LocalisationSystemID int Unique ID for the localisation system (= Primary key)
LocalisationSystemParentID int LocalisationSystemID of the superior LocalisationSystem
LocalisationSystemName nvarchar (50) Name of the system used for the determination of the place of the collection, e. g. Gauss-Krüger, MTB, GIS
MeasurementUnit nvarchar (100) -
DefaultAccuracyOfLocalisation nvarchar (100) The default for the accuracy of values which can be reached with this method
DiversityModule nvarchar (50) -
ParsingMethod nvarchar (500) -
LocalisationSystemType nvarchar (500) -
Description nvarchar (255) Description of the localisation method
Abbreviation nvarchar (50) -
DescriptionLocation1 nvarchar (255) Description of the attribute Location1 in the table CollectionGeography as displayed in the user interface
AbbreviationLocation1 nvarchar (50) -
DescriptionLocation2 nvarchar (255) Description of the attribute Location2 in the table CollectionGeography as displayed in the user interface
AbbreviationLocation2 nvarchar (50) -

Function ManagerCollectionList

Returns a table that lists all the collections a Manager has access to, including the child collections.

Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (4000) A short description of the collection
Location nvarchar (1000) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.

Depending on:

  • Collection
  • CollectionChildNodes
  • CollectionManager

Function MethodChildNodes

All child nodes of a given method related via the MethodParentID

Parameter DataType Description
@ID int MethodID for which the depending methods should be returned
Column DataType Description
MethodID int ID of the Method (Primary key)
MethodParentID int MethodID of the parent Method, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the Method as e.g. shown in user interface
Description nvarchar (500) Description of the Method
ForCollectionEvent bit If a method may be used during a collection event
Notes nvarchar (1000) Notes on this method
MethodURI varchar (255) URI referring to an external documentation of the Method
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
RowGUID uniqueidentifier -

Depending on:

  • Method
  • MethodChildNodes

Function MethodHierarchy

The hierarchy of a given method

Parameter DataType Description
@MethodID int ID of the Method (Primary key)
Column DataType Description
MethodID int ID of the Method (Primary key)
MethodParentID int MethodID of the parent Method, if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the Method as e.g. shown in user interface
Description nvarchar (500) Description of the Method
Notes nvarchar (1000) Notes on this method
MethodURI varchar (255) URI referring to an external documentation of the Method
ForCollectionEvent bit If a method may be used during a collection event
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries

Depending on:

  • Method
  • MethodChildNodes

Function MethodHierarchyAll

All methods including a column displaying the hierarchy of the method

Column DataType Description
MethodID int ID of the Method (Primary key)
MethodParentID int MethodID of the parent Method, if it belongs to a certain type documented in this table
DisplayText nvarchar (255) Name of the Method as e.g. shown in user interface
Description nvarchar (MAX) Description of the Method
Notes nvarchar (MAX) Notes on this method
MethodURI varchar (255) URI referring to an external documentation of the Method
ForCollectionEvent bit If a method may be used during a collection event
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
HierarchyDisplayText nvarchar (900) Hierarchy of the method separated by

Depending on:

  • Method

Function NameList

Parameter DataType Description
@NameID int -
@NameStart nvarchar (50) -
Column DataType Description
NameID int -
TaxonName nvarchar (255) -

Function NameListMyxomycetes

Parameter DataType Description
@NameID int -
@NameStart nvarchar (50) -
Column DataType Description
NameID int -
TaxonName nvarchar (200) -

Function NameListPlants

Parameter DataType Description
@NameID int -
@NameStart nvarchar (50) -
Column DataType Description
NameID int -
TaxonName nvarchar (200) -

Function NextFreeAccNr

returns next free accession number similar to given parameter. Assumes that accession numbers have a pattern like M-0023423 or HAL 25345 or GLM3453 with a leading string and a numeric end

DataType: nvarchar (50)

Parameter DataType Description
@AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752”

Depending on:

  • CollectionSpecimen

Function NextFreeAccNumber

The next free accession number starting like parameter 1, optional inclusion of specimen (parameter 2) and parts (parameter 3)

DataType: nvarchar (50)

Parameter DataType Description
@AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752”
@IncludeSpecimen bit If specimen should be included in search
@IncludePart bit If parts should be included in search

Depending on:

  • CollectionSpecimen
  • CollectionSpecimenPart

Function PrivacyConsentInfo

Provides a link to common information about the DiversityWorkbench

DataType: varchar (900)


Function ProcessingChildNodes

Returns a result set that lists all the processings within a hierarchy starting at the topmost processing related to the given item

Parameter DataType Description
@ID int ID of the parent processing
Column DataType Description
ProcessingID int ID of the processing (primary key)
ProcessingParentID int The ID of the superior type of the processing
DisplayText nvarchar (50) The display text of the processing as shown e.g. in a user interface
Description nvarchar (500) Description of the processing
Notes nvarchar (1000) Notes on the processing
ProcessingURI varchar (255) A URI for a processing as defined in an external data source
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
RowGUID uniqueidentifier -

Depending on:

  • Processing
  • ProcessingChildNodes

Function ProcessingHierarchy

Returns a table that lists all the analysis items related to the given processing.

Parameter DataType Description
@ID int ID of the parent processing
Column DataType Description
ProcessingID int ID of the processing (primary key)
ProcessingParentID int The ID of the superior type of the processing
DisplayText nvarchar (50) The display text of the processing as shown e.g. in a user interface
Description nvarchar (500) Description of the processing
Notes nvarchar (1000) Notes on the processing
ProcessingURI varchar (255) A URI for a processing as defined in an external data source
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
RowGUID uniqueidentifier -

Depending on:

  • Processing
  • ProcessingChildNodes

Function ProcessingHierarchyAll

Returns a table that lists all the Processings including their hierarchy

Column DataType Description
ProcessingID int ID of the processing (primary key)
ProcessingParentID int The ID of the superior type of the processing
DisplayText nvarchar (50) The display text of the processing as shown e.g. in a user interface
Description nvarchar (MAX) Description of the processing
Notes nvarchar (MAX) Notes on the processing
ProcessingURI varchar (255) A URI for a processing as defined in an external data source
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
HierarchyDisplayText varchar (900) Hierarchy of the processings as DisplayText separated by

Depending on:

  • Processing

Function ProcessingListForPart

Returns a table that lists all the processing items related to the given part.Tthe list depends upon the processing types available for a material category and the projects available for a processing

Parameter DataType Description
@CollectionSpecimenID int Refers to the ID of CollectionSpecimen (= foreign key and part of primary key)
@SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key).
Column DataType Description
ProcessingID int ID of the processing (primary key)
ProcessingParentID int The ID of the superior type of the processing
DisplayText nvarchar (50) The display text of the processing as shown e.g. in a user interface
Description nvarchar (MAX) Description of the processing
Notes nvarchar (MAX) Notes on the storage of the sample
ProcessingURI varchar (255) A URI for a processing as defined in an external data source
DisplayTextHierarchy nvarchar (255) Hierarchy of the processings as DisplayText separated by

Depending on:

  • CollectionProject
  • CollectionSpecimen
  • CollectionSpecimenPart
  • Processing
  • ProcessingChildNodes
  • ProcessingHierarchy
  • ProcessingMaterialCategory
  • ProjectProcessing

Function ProcessingProjectList

Returns a table that lists all the Processing items related to the given project.

Parameter DataType Description
@ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
Column DataType Description
ProcessingID int ID of the processing (primary key)
ProcessingParentID int The ID of the superior type of the processing
DisplayText nvarchar (50) The display text of the processing as shown e.g. in a user interface
Description nvarchar (500) Description of the processing
Notes nvarchar (1000) Notes on the processing
ProcessingURI varchar (255) A URI for a processing as defined in an external data source
OnlyHierarchy bit If the entry is only used for the hierarchical arrangement of the entries
RowGUID uniqueidentifier -

Depending on:

  • Processing
  • ProcessingChildNodes
  • ProjectProcessing

Function ProjectDataLastChanges

retrieval of the last update in data of a project

DataType: datetime

Parameter DataType Description
@ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)

Depending on:

  • CollectionEvent
  • CollectionProject
  • CollectionProject_log
  • CollectionSpecimen

Function RequesterCollectionList

Returns a table that lists all the collections a requester has access to, including the child collections if allowed

Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (50) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (500) A short description of the collection
Location nvarchar (1000) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder varchar (255) The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.

Depending on:

  • Collection
  • CollectionHierarchy
  • CollectionRequester

Function StableIdentifier

Returns a stable identfier for a dataset. Relies on an entry in ProjectProxy

DataType: varchar (500)

Parameter DataType Description
@ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
@CollectionSpecimenID int CollectionSpecimenID that should be included in the StableIdentifier
@IdentificationUnitID int IdentificationUnitID that should be included in the StableIdentifier
@SpecimenPartID int SpecimenPartID that should be included in the StableIdentifier

Depending on:

  • ProjectProxy

Function TaskChildNodes

All child nodes of a given Task related via the TaskParentID

Parameter DataType Description
@ID int TaskParentID for which all child nodes of a given Task should be returned
Column DataType Description
TaskID int ID of the Task (primary key)
TaskParentID int The ID of the superior type of the Task
DisplayText nvarchar (50) The display text of the Task as shown e.g. in a user interface
Description nvarchar (500) Description of the Task
Notes nvarchar (1000) Notes on the Task
TaskURI varchar (255) A URI for a Task as defined in an external data source
Type varchar (50) The type of the task as defined in table TaskType_Enum
ModuleTitle varchar (50) The title for module related data for collection tasks. Not available in depending collection task if empty
ModuleType varchar (50) The DiversityWorkbench module to which a task is related. Not available in depending collection task if empty
SpecimenPartType nvarchar (50) The description of the collection specimen part to which a task is related. Not available in depending collection task if empty
TransactionType nvarchar (50) The description of the transaction to which a task is related. Not available in depending collection task if empty
ResultType varchar (50) The display text for the results as shown in a user interface. Not available in depending collection task if empty
DateType varchar (50) The date and time details defined for a task. Not available in depending collection task if empty
DateBeginType nvarchar (50) The definition of the begin for date and time details defined for a task. Not available in depending collection task if empty
DateEndType nvarchar (50) The definition of the end for date and time details defined for a task. Not available in depending collection task if empty
NumberType varchar (50) The definition for the numeric value as shown in a user interface. Not available in depending collection task if empty
BoolType varchar (50) The definition for the boolean value as shown in a user interface. Not available in depending collection task if empty
MetricType nvarchar (50) The definition for the metric as shown in a user interface. Not available in depending collection task if empty
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleType nvarchar (50) The definition for the responsible agent as shown in a user interface. Not available in depending collection task if empty
DescriptionType varchar (50) The definition for the description as shown in a user interface. Not available in depending collection task if empty
NotesType varchar (50) The definition for the notes as shown in a user interface. Not available in depending collection task if empty
UriType varchar (50) The definition for the URI as shown in a user interface. Not available in depending collection task if empty
RowGUID uniqueidentifier -

Depending on:

  • Task

Function TaskCollectionHierarchySeparator

Returns a separator used between collection and task hierarchy

DataType: nchar (3)


Function TaskHierarchy

The hierarchy of a given Task

Parameter DataType Description
@TaskID int ID of the Task (primary key)
Column DataType Description
TaskID int ID of the Task (primary key)
TaskParentID int The ID of the superior type of the Task
DisplayText nvarchar (50) The display text of the Task as shown e.g. in a user interface
Description nvarchar (500) Description of the Task
Notes nvarchar (1000) Notes on the Task
TaskURI varchar (255) A URI for a Task as defined in an external data source
Type varchar (50) The type of the task as defined in table TaskType_Enum
ModuleTitle varchar (50) The title for module related data for collection tasks. Not available in depending collection task if empty
ModuleType varchar (50) The DiversityWorkbench module to which a task is related. Not available in depending collection task if empty
SpecimenPartType nvarchar (50) The description of the collection specimen part to which a task is related. Not available in depending collection task if empty
TransactionType nvarchar (50) The description of the transaction to which a task is related. Not available in depending collection task if empty
ResultType varchar (50) The display text for the results as shown in a user interface. Not available in depending collection task if empty
DateType varchar (50) The date and time details defined for a task. Not available in depending collection task if empty
DateBeginType nvarchar (50) The definition of the begin for date and time details defined for a task. Not available in depending collection task if empty
DateEndType nvarchar (50) The definition of the end for date and time details defined for a task. Not available in depending collection task if empty
NumberType varchar (50) The definition for the numeric value as shown in a user interface. Not available in depending collection task if empty
BoolType varchar (50) The definition for the boolean value as shown in a user interface. Not available in depending collection task if empty
MetricType nvarchar (50) The definition for the metric as shown in a user interface. Not available in depending collection task if empty
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleType nvarchar (50) The definition for the responsible agent as shown in a user interface. Not available in depending collection task if empty
DescriptionType varchar (50) The definition for the description as shown in a user interface. Not available in depending collection task if empty
NotesType varchar (50) The definition for the notes as shown in a user interface. Not available in depending collection task if empty
UriType varchar (50) The definition for the URI as shown in a user interface. Not available in depending collection task if empty

Depending on:

  • Task
  • TaskChildNodes

Function TaskHierarchyAll

All Tasks including a column displaying the hierarchy of the Task

Column DataType Description
TaskID int ID of the Task (primary key)
TaskParentID int The ID of the superior type of the Task
DisplayText nvarchar (50) The display text of the Task as shown e.g. in a user interface
Description nvarchar (MAX) Description of the Task
Notes nvarchar (MAX) Notes on the Task
TaskURI varchar (255) A URI for a Task as defined in an external data source
Type varchar (50) The type of the task as defined in table TaskType_Enum
ModuleTitle varchar (50) The title for module related data for collection tasks. Not available in depending collection task if empty
ModuleType varchar (50) The DiversityWorkbench module to which a task is related. Not available in depending collection task if empty
SpecimenPartType nvarchar (50) The description of the collection specimen part to which a task is related. Not available in depending collection task if empty
TransactionType nvarchar (50) The description of the transaction to which a task is related. Not available in depending collection task if empty
ResultType varchar (50) The display text for the results as shown in a user interface. Not available in depending collection task if empty
DateType varchar (50) The date and time details defined for a task. Not available in depending collection task if empty
DateBeginType nvarchar (50) The definition of the begin for date and time details defined for a task. Not available in depending collection task if empty
DateEndType nvarchar (50) The definition of the end for date and time details defined for a task. Not available in depending collection task if empty
NumberType varchar (50) The definition for the numeric value as shown in a user interface. Not available in depending collection task if empty
BoolType varchar (50) The definition for the boolean value as shown in a user interface. Not available in depending collection task if empty
MetricType nvarchar (50) The definition for the metric as shown in a user interface. Not available in depending collection task if empty
MetricUnit nvarchar (50) The unit of the metric, e.g. °C for temperature
ResponsibleType nvarchar (50) The definition for the responsible agent as shown in a user interface. Not available in depending collection task if empty
DescriptionType varchar (50) The definition for the description as shown in a user interface. Not available in depending collection task if empty
NotesType varchar (50) The definition for the notes as shown in a user interface. Not available in depending collection task if empty
UriType varchar (50) The definition for the URI as shown in a user interface. Not available in depending collection task if empty
HierarchyDisplayText nvarchar (900) Hierarchy of the task starting at top Task separated by string defined in dbo.TaskHierarchySeparator()
HierarchyDisplayTextInvers nvarchar (900) Hierarchy of the task ending at top Task separated by string defined in dbo.TaskHierarchySeparator()

Depending on:

  • Task
  • TaskHierarchySeparator

Function TaskHierarchySeparator

Returns a separator used within a task hierarchy

DataType: nchar (3)


Function TaxonWithQualifier

Generates a valid name for a taxon using the taxonomic name and the identification qualifier

DataType: nvarchar (500)

Parameter DataType Description
@Taxon nvarchar (500) Taxonomic name used as base for transformation
@Qualifier nvarchar (50) Qualifier used as base for transformation

Function TransactionChildNodes

Returns a result set that lists all the transactions within a hierarchy starting at the topmost transaction related to the given transaction.

Parameter DataType Description
@ID int TransactionID of the topmost transaction within the hierarchy that should be returned
Column DataType Description
TransactionID int Unique ID for the transaction (= primary key)
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction.
MaterialDescription nvarchar (MAX) Description of the material of this transaction
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.
MaterialCollectors nvarchar (MAX) The collectors of the material
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents
NumberOfUnits int The number of units which were (initially) included in the transaction
Investigator nvarchar (200) The investigator for whose study a transacted material was sent
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner
BeginDate datetime Date when the transaction started
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page
ResponsibleName nvarchar (255) The person responsible for this transaction
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents)
DateSupplement nvarchar (100) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’.

Depending on:

  • Transaction

Function TransactionChildNodesAccess

Returns a result set that lists all the items within a hierarchy starting at the topmost item related to the given item where the current user has no access according to the restriction in TransactionList.

Parameter DataType Description
@ID int TransactionID of the topmost transaction within the hierarchy that should be returned
Column DataType Description
TransactionID int Unique ID for the transaction (= primary key)
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction.
MaterialDescription nvarchar (MAX) Description of the material of this transaction
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.
MaterialCollectors nvarchar (MAX) The collectors of the material
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents
NumberOfUnits int The number of units which were (initially) included in the transaction
Investigator nvarchar (200) The investigator for whose study a transacted material was sent
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner
BeginDate datetime Date when the transaction started
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page
ResponsibleName nvarchar (255) The person responsible for this transaction
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents)
Accessible tinyint If a user has access to this dataset

Depending on:

  • Transaction
  • TransactionChildNodesAccess

Function TransactionCurrency

The default curreny for payments

DataType: nvarchar (50)


Function TransactionHierarchy

Returns a table that lists all the transactions related to the given transaction.

Parameter DataType Description
@TransactionID int Unique ID for the transaction (= primary key)
Column DataType Description
TransactionID int Unique ID for the transaction (= primary key)
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction.
MaterialDescription nvarchar (MAX) Description of the material of this transaction
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.
MaterialCollectors nvarchar (MAX) The collectors of the material
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents
NumberOfUnits int The number of units which were (initially) included in the transaction
Investigator nvarchar (200) The investigator for whose study a transacted material was sent
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner
BeginDate datetime Date when the transaction started
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page
ResponsibleName nvarchar (255) The person responsible for this transaction
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents)
DateSupplement nvarchar (100) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’.

Depending on:

  • TransactionChildNodes
  • TransactionList

Function TransactionHierarchyAccess

Returns a table that lists all the transactions related to the given transaction including the accessiblity.

Parameter DataType Description
@TransactionID int Unique ID for the transaction (= primary key)
Column DataType Description
TransactionID int Unique ID for the transaction (= primary key)
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction.
MaterialDescription nvarchar (MAX) Description of the material of this transaction
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.
MaterialCollectors nvarchar (MAX) The collectors of the material
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents
NumberOfUnits int The number of units which were (initially) included in the transaction
Investigator nvarchar (200) The investigator for whose study a transacted material was sent
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner
BeginDate datetime Date when the transaction started
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page
ResponsibleName nvarchar (255) The person responsible for this transaction
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents)
Accessible tinyint If a user has access to this dataset

Depending on:

  • Transaction
  • TransactionChildNodesAccess
  • TransactionList

Function TransactionHierarchyAll

Returns a table that lists all the transactions including their hierarchy

Column DataType Description
TransactionID int Unique ID for the transaction (= primary key)
ParentTransactionID int The ID of a preceeding transaction of a superior transaction, if transactions are organized in a hierarchy
TransactionType nvarchar (50) Type of the transaction, e.g. gift in or out, exchange in or out, purchase in or out
TransactionTitle nvarchar (200) The title of the transaction as e.g. shown in an user interface
ReportingCategory nvarchar (50) A group defined for the transaction, e.g. a taxonomic group as used for exchange balancing
AdministratingCollectionID int ID of the collection which is responsible for the administration of the transaction.
MaterialDescription nvarchar (MAX) Description of the material of this transaction
MaterialSource nvarchar (500) The source of the material within a transaction, e.g. a excavation
MaterialCategory nvarchar (50) Material category of specimen. Examples: ‘herbarium sheets’, ‘drawings’, ‘microscopic slides’ etc.
MaterialCollectors nvarchar (MAX) The collectors of the material
FromCollectionID int The ID of the collection from which the specimen were transfered, e.g. the donating collection of a gift
FromTransactionPartnerName nvarchar (255) Name of the person or institution from which the specimen were transfered, e.g. the donator of a gift
FromTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
FromTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the source of the specimen, e.g. the donating collection of a gift
ToCollectionID int The ID of the collection to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerName nvarchar (255) Name of the person or institution to which the specimen were transfered, e.g. the receiver of a gift
ToTransactionPartnerAgentURI varchar (255) The URI of the transaction partner (see e.g. module DiversityAgents)
ToTransactionNumber nvarchar (50) Number or code by which a transaction may be recorded by the administration of the destination of the specimen, e.g. the receiving collection of a gift
ToRecipient nvarchar (255) The recipient receiving the transaction e.g. if not derived from the link to DiversityAgents
NumberOfUnits smallint The number of units which were (initially) included in the transaction
Investigator nvarchar (200) The investigator for whose study a transacted material was sent
TransactionComment nvarchar (MAX) Comments on the exchanged material addressed to the transaction partner
BeginDate datetime Date when the transaction started
AgreedEndDate datetime End of the transaction period, e.g. if the time for borrowing the specimen is restricted
ActualEndDate datetime Actual end of the transaction after a prolonation when e.g. the date of return for a loan was prolonged by the owner
InternalNotes nvarchar (MAX) Internal notes on this transaction not to be published e.g. on a web page
ResponsibleName nvarchar (255) The person responsible for this transaction
ResponsibleAgentURI varchar (255) The URI of the person, team or organisation responsible for the data (see e.g. module DiversityAgents)
DisplayText nvarchar (500) Hierarchy of the transaction starting at top transaction separated by
HierarchyDisplayText nvarchar (500) Hierarchy of the transaction starting at top transaction separated by

Depending on:

  • Transaction

Function UserCollectionList

Returns a table that lists all the collections a User has access to, including the child collections.

Column DataType Description
CollectionID int Unique reference ID for the collection (= primary key)
CollectionParentID int For a subcollection within another collection: CollectionID of the collection to which the subcollection belongs. Empty for an independent collection
CollectionName nvarchar (255) Name of the collection (e.g. ‘Herbarium Kew’) or subcollection (e.g. ‘cone collection’, ‘alcohol preservations’). This text should be kept relatively short. You may use Description for additional information
CollectionAcronym nvarchar (50) A unique code for the collection, e.g. the herbarium code from Index Herbariorum
AdministrativeContactName nvarchar (500) The name of the person or organisation responsible for this collection
AdministrativeContactAgentURI nvarchar (255) The URI of the person or organisation responsible for the collection e.g. as provided by the module DiversityAgents
Description nvarchar (MAX) A short description of the collection
Location nvarchar (1000) Optional location of the collection, e.g. the number within a file system or a description of the room(s) housing the (sub)collection
CollectionOwner nvarchar (255) The owner of the collection as e.g. printed on a label. Should be given if CollectionParentID is null
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.

Depending on:

  • Collection
  • CollectionChildNodes
  • CollectionManager
  • CollectionUser
  • ManagerCollectionList

Function UserID

ID of the User as stored in table UserProxy

DataType: int

Depending on:

  • UserProxy

Function Version

Version of the database

DataType: nvarchar (8)


Function VersionClient

Minimal version of the client compatible with the database

DataType: nvarchar (11)


PROCEDURES


Procedure DeleteXmlAttribute

Deleting an attribute of an XML node in a column of datatype XML

Parameter DataType Description
@Table nvarchar (128) Name of the table containing the XML column
@Column nvarchar (128) Name of the XML column
@Path nvarchar (4000) Path of the XML node
@Attribute nvarchar (128) Attribute that should be removed
@WhereClause nvarchar (4000) Where clause to select the data within the table

Procedure DeleteXmlNode

Deleting a XML node in a column of datatype XML

Parameter DataType Description
@Table nvarchar (128) Name of the table containing the XML column
@Column nvarchar (128) Name of the XML column
@Path nvarchar (4000) Path of the XML node
@WhereClause nvarchar (4000) Where clause to select the data within the table

Procedure procCopyCollectionSpecimen2

Copy a collection specimen

Parameter DataType Description
@CollectionSpecimenID int Refers to ID of CollectionEvent (= foreign key and part of primary key)
@OriginalCollectionSpecimenID int The CollectionSpecimenID of the CollectionSpecimen that should be copied
@AccessionNumber nvarchar (50) Accession number of the specimen within the collection, e.g. “M-29834752”
@EventCopyMode int 3 Options: -1 = dont copy the event, leave the entry in table CollectionSpecimen empty; 0 = take same event as original specimen; 1 = create new event with the same data as the old specimen
@IncludedTables nvarchar (4000) Contains list of tables that are copied according to the users choice

Depending on:

  • Annotation
  • CollectionAgent
  • CollectionEvent
  • CollectionEventImage
  • CollectionEventLocalisation
  • CollectionEventMethod
  • CollectionEventParameterValue
  • CollectionEventProperty
  • CollectionProject
  • CollectionSpecimen
  • CollectionSpecimenImage
  • CollectionSpecimenImageProperty
  • CollectionSpecimenPart
  • CollectionSpecimenPartDescription
  • CollectionSpecimenProcessing
  • CollectionSpecimenProcessingMethod
  • CollectionSpecimenProcessingMethodParameter
  • CollectionSpecimenReference
  • CollectionSpecimenRelation
  • CollectionSpecimenTransaction
  • ExternalIdentifier
  • Identification
  • IdentificationUnit
  • IdentificationUnitAnalysis
  • IdentificationUnitAnalysisMethod
  • IdentificationUnitAnalysisMethodParameter
  • IdentificationUnitGeoAnalysis
  • IdentificationUnitInPart

Procedure procCopyCollectionSpecimenPart

Copy a collection specimen part

Parameter DataType Description
@SpecimenPartID int Unique ID of the part of the collection specimen (= part of primary key).
@OriginalSpecimenPartID int The SpecimenPartID of the CollectionSpecimenPart that should be copied
@AccessionNumber nvarchar (50) Accession number of the part of the specimen within the collection, if it is different from the accession number of the specimen as stored in the table CollectionSpecimen, e.g. “M-29834752”
@PartSublabel nvarchar (50) The label for a part of a specimen, e.g. “cone”, or a number attached to a duplicate of a specimen
@StorageLocation nvarchar (255) A code identifying the place where the specimen is stored within the collection. Frequently the accepted scientific name is used as storage location code.
@IncludedTables nvarchar (4000) Contains list of tables that are copied according to the users choice

Depending on:

  • Annotation
  • CollectionSpecimenPart
  • CollectionSpecimenPartDescription
  • CollectionSpecimenPartRegulation
  • CollectionSpecimenProcessing
  • CollectionSpecimenProcessingMethod
  • CollectionSpecimenProcessingMethodParameter
  • CollectionSpecimenReference
  • CollectionSpecimenRelation
  • CollectionSpecimenTransaction
  • ExternalIdentifier
  • IdentificationUnitInPart

Procedure procFillCacheDescription

Filling table CacheDescription

Depending on:

  • CacheDescription
  • EntityRepresentation

Procedure procInsertCollectionEventCopy

Copy a collection event

Parameter DataType Description
@CollectionEventID int Unique ID for the table CollectionEvent (= primary key)
@OriginalCollectionEventID int The CollectionEventID of the CollectionEvent that should be copied

Depending on:

  • CollectionEvent
  • CollectionEventImage
  • CollectionEventLocalisation
  • CollectionEventProperty

Procedure procSetVersionCollectionEvent

Setting the version of a dataset

Parameter DataType Description
@ID int CollectionEventID of the dataset

Depending on:

  • CollectionEvent
  • CollectionProject
  • CollectionSpecimen
  • ProjectProxy

Procedure procSetVersionCollectionSpecimen

Setting the version of a dataset

Parameter DataType Description
@ID int CollectionSpecimenID of the dataset

Depending on:

  • CollectionProject
  • CollectionSpecimen
  • ProjectProxy

Procedure SetXmlAttribute

Setting a value of an XML node

Parameter DataType Description
@Table nvarchar (128) Name of the table containing the XML column
@Column nvarchar (128) Name of the XML column
@Path nvarchar (4000) Path of the XML node
@Attribute nvarchar (128) Attribute that should be set
@Value nvarchar (4000) The value for the attribute that should be set
@WhereClause nvarchar (4000) Where clause to select the data within the table

Procedure SetXmlValue

Setting a value of an XML node

Parameter DataType Description
@Table nvarchar (128) Name of the table containing the XML column
@Column nvarchar (128) Name of the XML column
@Path nvarchar (4000) Path of the XML node
@Value nvarchar (4000) The value for the node that should be set
@WhereClause nvarchar (4000) Where clause to select the data within the table
May 3, 2024

Diversity Collection

Roles

Content of cell Permission
Not granted
Name of other role Inherited from other role
Granted

Role Administrator

Administrator of the database. Read/write access to all objects

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis Editor Data Manager Data Manager TABLE
Analysis_log Data Manager TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User Data Manager Data Manager TABLE
Annotation_log Editor Editor TABLE
AnnotationType_Enum User TABLE
AnonymCollector Cache User Cache Admin Cache Admin Cache Admin TABLE
CacheDatabase2 Cache User Cache Admin TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection Editor Editor TABLE
Collection_log Editor Editor TABLE
CollectionAgent User Editor Editor TABLE
CollectionAgent_log Editor Editor TABLE
CollectionEvent User Editor Editor TABLE
CollectionEvent_log Editor Editor TABLE
CollectionEventImage User Editor Editor TABLE
CollectionEventImage_log Editor Editor TABLE
CollectionEventLocalisation User Typist Typist Editor TABLE
CollectionEventLocalisation_log Typist Typist TABLE
CollectionEventMethod User Data Manager Data Manager Data Manager TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User Data Manager Data Manager Data Manager TABLE
CollectionEventParameterValue_log Editor Editor TABLE
CollectionEventProperty User Typist Typist Editor TABLE
CollectionEventProperty_log Typist Typist TABLE
CollectionEventRegulation User Editor Editor TABLE
CollectionEventRegulation_log Editor Editor TABLE
CollectionEventSeries User Editor Typist Editor TABLE
CollectionEventSeries_log Typist Typist TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User Editor Typist Editor TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager Collection Manager TABLE
CollectionProject User Editor Editor TABLE
CollectionProject_log Editor Editor TABLE
CollectionSpecimen Typist Editor Editor TABLE
CollectionSpecimen_log Editor Editor TABLE
CollectionSpecimenImage Typist Editor Editor TABLE
CollectionSpecimenImage_log Typist Typist TABLE
CollectionSpecimenImageProperty User Editor Editor Editor TABLE
CollectionSpecimenImageProperty_log Editor Editor TABLE
CollectionSpecimenPart User Typist Typist Editor TABLE
CollectionSpecimenPart_log Typist Typist TABLE
CollectionSpecimenPartDescription User Editor Editor Editor TABLE
CollectionSpecimenPartDescription_log Editor Editor TABLE
CollectionSpecimenProcessing User Editor Editor Editor TABLE
CollectionSpecimenProcessing_log Typist Typist TABLE
CollectionSpecimenProcessingMethod User Editor Editor Editor TABLE
CollectionSpecimenProcessingMethod_log Editor Editor TABLE
CollectionSpecimenProcessingMethodParameter User Editor Editor Editor TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User Editor Editor Editor TABLE
CollectionSpecimenReference_log Editor Editor TABLE
CollectionSpecimenRelation User Editor Editor TABLE
CollectionSpecimenRelation_log Editor Editor TABLE
CollectionSpecimenTransaction User Typist Typist Editor TABLE
CollectionSpecimenTransaction_log Typist Typist TABLE
CollectionTask User Collection Manager Collection Manager Collection Manager TABLE
CollectionTask_log Collection Manager Collection Manager TABLE
CollectionTaskImage User Collection Manager Collection Manager Collection Manager TABLE
CollectionTaskImage_log Collection Manager Collection Manager TABLE
CollectionTaskMetric User Collection Manager Collection Manager Collection Manager TABLE
CollectionTaskMetric_log Collection Manager Collection Manager TABLE
CollEventDateCategory_Enum Editor TABLE
CollEventImageType_Enum Editor TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum Editor TABLE
CollIdentificationCategory_Enum Editor TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum Editor TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User Editor Editor Editor TABLE
ExternalIdentifier_log Editor Editor TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User Typist Typist TABLE
Identification_log Editor Editor TABLE
IdentificationUnit User Editor Editor TABLE
IdentificationUnit_log Editor Editor TABLE
IdentificationUnitAnalysis User Editor Editor TABLE
IdentificationUnitAnalysis_log Typist Typist TABLE
IdentificationUnitAnalysisMethod User Editor Editor Editor TABLE
IdentificationUnitAnalysisMethod_log Editor Editor TABLE
IdentificationUnitAnalysisMethodParameter User Editor Editor Editor TABLE
IdentificationUnitAnalysisMethodParameter_log Editor Editor TABLE
IdentificationUnitGeoAnalysis User Editor Editor Editor TABLE
IdentificationUnitGeoAnalysis_log Editor TABLE
IdentificationUnitInPart User Typist Typist Editor TABLE
IdentificationUnitInPart_log Typist Typist TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User Data Manager Data Manager TABLE
Processing_log Editor Data Manager TABLE
ProcessingMaterialCategory User Data Manager Data Manager TABLE
ProjectAnalysis User Data Manager Data Manager TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User Data Manager Data Manager TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher Editor TABLE
Task User Collection Manager Collection Manager TABLE
Task_log Collection Manager Collection Manager TABLE
TaskDateType_Enum User TABLE
TaskModule User Collection Manager Collection Manager Collection Manager TABLE
TaskModule_log Collection Manager Collection Manager TABLE
TaskModuleType_Enum User TABLE
TaskResult User Collection Manager Collection Manager Collection Manager TABLE
TaskResult_log Collection Manager Collection Manager TABLE
TaskType_Enum User TABLE
Transaction User Collection Manager Collection Manager TABLE
Transaction_log Typist Typist TABLE
TransactionAgent Transaction User Collection Manager Collection Manager Collection Manager TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User Typist Typist TABLE
TransactionDocument_log Typist Typist TABLE
TransactionPayment Transaction User Collection Manager Collection Manager Collection Manager TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString Editor FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List Editor FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List Editor FUNCTION
CollEventImageType_List Editor FUNCTION
CollExchangeType_List Editor FUNCTION
CollIdentificationCategory_List Editor FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List Editor FUNCTION
CuratorCollectionHierarchyList Collection Manager FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList Collection Manager FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr Typist FUNCTION
NextFreeAccNumber Editor FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 Editor PROCEDURE
procCopyCollectionSpecimenPart Editor PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent Editor PROCEDURE
procSetVersionCollectionSpecimen Editor PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • Replicator
  • DataManager
  • CacheAdmin
  • CollectionManager
  • Editor

Role AdminNonProject

Permissions as Administrator without permission to change projects

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis Editor Data Manager Data Manager Administrator TABLE
Analysis_log Data Manager TABLE
AnalysisResult User Administrator Administrator Administrator TABLE
AnalysisTaxonomicGroup User Administrator Administrator Administrator TABLE
Annotation User User Data Manager Data Manager TABLE
Annotation_log Editor Editor TABLE
AnnotationType_Enum User TABLE
AnonymCollector Cache User Cache Admin Cache Admin Cache Admin TABLE
CacheDatabase2 Cache User Cache Admin TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User Administrator Administrator Administrator TABLE
CollCollectionType_Enum User Administrator Administrator Administrator TABLE
CollDateCategory_Enum User Administrator Administrator Administrator TABLE
Collection Editor Administrator Editor Administrator TABLE
Collection_log Editor Editor TABLE
CollectionAgent User Editor Editor Administrator TABLE
CollectionAgent_log Editor Editor TABLE
CollectionEvent User Editor Editor Administrator TABLE
CollectionEvent_log Editor Editor TABLE
CollectionEventImage User Editor Editor Administrator TABLE
CollectionEventImage_log Editor Editor TABLE
CollectionEventLocalisation User Typist Typist Editor TABLE
CollectionEventLocalisation_log Typist Typist TABLE
CollectionEventMethod User Data Manager Data Manager Data Manager TABLE
CollectionEventMethod_log Administrator TABLE
CollectionEventParameterValue User Data Manager Data Manager Data Manager TABLE
CollectionEventParameterValue_log Editor Editor TABLE
CollectionEventProperty User Typist Typist Editor TABLE
CollectionEventProperty_log Typist Typist TABLE
CollectionEventRegulation User Editor Editor Administrator TABLE
CollectionEventRegulation_log Editor Editor Administrator TABLE
CollectionEventSeries User Editor Typist Editor TABLE
CollectionEventSeries_log Typist Typist TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User Editor Typist Editor TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User Administrator Administrator Administrator TABLE
CollectionExternalDatasource_log TABLE
CollectionImage Administrator Administrator Administrator Administrator TABLE
CollectionImage_log Administrator Administrator TABLE
CollectionManager Collection Manager Administrator Administrator Administrator TABLE
CollectionProject User Editor Editor Administrator TABLE
CollectionProject_log Editor Editor TABLE
CollectionSpecimen Typist Editor Editor Administrator TABLE
CollectionSpecimen_log Editor Editor Administrator TABLE
CollectionSpecimenImage Typist Editor Editor Administrator TABLE
CollectionSpecimenImage_log Typist Typist TABLE
CollectionSpecimenImageProperty User Editor Editor Editor TABLE
CollectionSpecimenImageProperty_log Editor Editor TABLE
CollectionSpecimenPart User Typist Typist Editor TABLE
CollectionSpecimenPart_log Typist Typist TABLE
CollectionSpecimenPartDescription User Editor Editor Editor TABLE
CollectionSpecimenPartDescription_log Editor Editor TABLE
CollectionSpecimenProcessing User Editor Editor Editor TABLE
CollectionSpecimenProcessing_log Typist Typist TABLE
CollectionSpecimenProcessingMethod User Editor Editor Editor TABLE
CollectionSpecimenProcessingMethod_log Editor Editor Administrator TABLE
CollectionSpecimenProcessingMethodParameter User Editor Editor Editor TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User Editor Editor Editor TABLE
CollectionSpecimenReference_log Editor Editor TABLE
CollectionSpecimenRelation User Editor Editor Administrator TABLE
CollectionSpecimenRelation_log Editor Editor TABLE
CollectionSpecimenTransaction User Typist Typist Editor TABLE
CollectionSpecimenTransaction_log Typist Typist TABLE
CollectionTask User Collection Manager Collection Manager Collection Manager TABLE
CollectionTask_log Collection Manager Collection Manager TABLE
CollectionTaskImage User Collection Manager Collection Manager Collection Manager TABLE
CollectionTaskImage_log Collection Manager Collection Manager TABLE
CollectionTaskMetric User Collection Manager Collection Manager Collection Manager TABLE
CollectionTaskMetric_log Collection Manager Collection Manager TABLE
CollEventDateCategory_Enum Editor Administrator Administrator Administrator TABLE
CollEventImageType_Enum Editor Administrator Administrator Administrator TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum Editor Administrator Administrator Administrator TABLE
CollIdentificationCategory_Enum Editor Administrator Administrator Administrator TABLE
CollIdentificationDateCategory_Enum User Administrator Administrator Administrator TABLE
CollIdentificationQualifier_Enum User Administrator Administrator Administrator TABLE
CollLabelTranscriptionState_Enum User Administrator Administrator Administrator TABLE
CollLabelType_Enum Editor Administrator Administrator Administrator TABLE
CollMaterialCategory_Enum User Administrator Administrator Administrator TABLE
CollRetrievalType_Enum User Administrator Administrator Administrator TABLE
CollSpecimenImageType_Enum User Administrator Administrator Administrator TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User Administrator Administrator Administrator TABLE
CollTaxonomicGroup_Enum User Administrator Administrator Administrator TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User Administrator Administrator Administrator TABLE
CollUnitRelationType_Enum User TABLE
Entity User Administrator Administrator Administrator TABLE
EntityAccessibility_Enum Administrator TABLE
EntityContext_Enum User Administrator Administrator Administrator TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User Administrator Administrator Administrator TABLE
EntityRepresentation User Administrator Administrator Administrator TABLE
EntityUsage User Administrator Administrator Administrator TABLE
EntityUsage_Enum User Administrator Administrator Administrator TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User Editor Editor Editor TABLE
ExternalIdentifier_log Editor Editor TABLE
ExternalIdentifierType User Administrator Administrator Administrator TABLE
ExternalIdentifierType_log Administrator Administrator TABLE
Identification User Typist Typist Administrator TABLE
Identification_log Editor Editor TABLE
IdentificationUnit User Editor Editor Administrator TABLE
IdentificationUnit_log Editor Editor TABLE
IdentificationUnitAnalysis User Editor Editor Administrator TABLE
IdentificationUnitAnalysis_log Typist Typist TABLE
IdentificationUnitAnalysisMethod User Editor Editor Editor TABLE
IdentificationUnitAnalysisMethod_log Editor Editor Administrator TABLE
IdentificationUnitAnalysisMethodParameter User Editor Editor Editor TABLE
IdentificationUnitAnalysisMethodParameter_log Editor Editor Administrator TABLE
IdentificationUnitGeoAnalysis User Editor Editor Editor TABLE
IdentificationUnitGeoAnalysis_log Editor TABLE
IdentificationUnitInPart User Typist Typist Editor TABLE
IdentificationUnitInPart_log Typist Typist TABLE
LanguageCode_Enum TABLE
LocalisationSystem User Administrator Administrator Administrator TABLE
MeasurementUnit_Enum TABLE
Method User Administrator Administrator Administrator TABLE
Method_log Administrator TABLE
MethodForAnalysis User Administrator Administrator Administrator TABLE
MethodForProcessing User Administrator Administrator Administrator TABLE
Parameter User Administrator Administrator Administrator TABLE
Parameter_log TABLE
ParameterValue_Enum User Administrator Administrator Administrator TABLE
Processing User Data Manager Data Manager Administrator TABLE
Processing_log Editor Data Manager TABLE
ProcessingMaterialCategory User Data Manager Data Manager Administrator TABLE
ProjectAnalysis User Data Manager Data Manager Administrator TABLE
ProjectMaterialCategory User Administrator Administrator Administrator TABLE
ProjectProcessing User Data Manager Data Manager Administrator TABLE
ProjectTaxonomicGroup User Administrator Administrator Administrator TABLE
ProjectUser Administrator Administrator Administrator Administrator TABLE
Property User Administrator Administrator TABLE
PropertyType_Enum TABLE
RegulationType_Enum User Administrator Administrator TABLE
ReplicationPublisher Editor Administrator Administrator TABLE
Task User Collection Manager Collection Manager Administrator TABLE
Task_log Collection Manager Collection Manager TABLE
TaskDateType_Enum User TABLE
TaskModule User Collection Manager Collection Manager Collection Manager TABLE
TaskModule_log Collection Manager Collection Manager TABLE
TaskModuleType_Enum User TABLE
TaskResult User Collection Manager Collection Manager Collection Manager TABLE
TaskResult_log Collection Manager Collection Manager TABLE
TaskType_Enum User Administrator Administrator Administrator TABLE
Transaction User Collection Manager Collection Manager Administrator TABLE
Transaction_log Typist Typist TABLE
TransactionAgent Transaction User Collection Manager Collection Manager Collection Manager TABLE
TransactionAgent_log TABLE
TransactionComment User Administrator Administrator Administrator TABLE
TransactionDocument User Typist Typist Administrator TABLE
TransactionDocument_log Typist Typist TABLE
TransactionPayment Transaction User Collection Manager Collection Manager Collection Manager TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString Editor FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List Editor FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List Editor FUNCTION
CollEventImageType_List Editor FUNCTION
CollExchangeType_List Editor FUNCTION
CollIdentificationCategory_List Editor FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List Editor FUNCTION
CuratorCollectionHierarchyList Collection Manager FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList Collection Manager FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr Typist FUNCTION
NextFreeAccNumber Editor FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 Editor PROCEDURE
procCopyCollectionSpecimenPart Editor PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent Editor PROCEDURE
procSetVersionCollectionSpecimen Editor PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • Administrator

Role CacheAdmin

Read/write access to objects related to cache database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis User TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User User TABLE
Annotation_log TABLE
AnnotationType_Enum User TABLE
AnonymCollector Cache User TABLE
CacheDatabase2 Cache User TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection User TABLE
Collection_log TABLE
CollectionAgent User TABLE
CollectionAgent_log TABLE
CollectionEvent User TABLE
CollectionEvent_log TABLE
CollectionEventImage User TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation User TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty User TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation User TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries User TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage User TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User TABLE
CollectionProject_log TABLE
CollectionSpecimen User TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage User TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty User TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart User TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription User TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing User TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod User TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter User TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation User TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction User TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User TABLE
Identification_log TABLE
IdentificationUnit User TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis User TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod User TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter User TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis User TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart User TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction User TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List User FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List User FUNCTION
CollEventImageType_List User FUNCTION
CollExchangeType_List User FUNCTION
CollIdentificationCategory_List User FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List User FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • CacheUser

Role CacheUser

Reading access to objects related to the cache database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis User TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User User TABLE
Annotation_log TABLE
AnnotationType_Enum User TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection User TABLE
Collection_log TABLE
CollectionAgent User TABLE
CollectionAgent_log TABLE
CollectionEvent User TABLE
CollectionEvent_log TABLE
CollectionEventImage User TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation User TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty User TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation User TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries User TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage User TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User TABLE
CollectionProject_log TABLE
CollectionSpecimen User TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage User TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty User TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart User TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription User TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing User TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod User TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter User TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation User TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction User TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User TABLE
Identification_log TABLE
IdentificationUnit User TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis User TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod User TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter User TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis User TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart User TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction User TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List User FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List User FUNCTION
CollEventImageType_List User FUNCTION
CollExchangeType_List User FUNCTION
CollIdentificationCategory_List User FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List User FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • User

Role CollectionManager

Role for the administration of collections and References

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis User TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User User TABLE
Annotation_log TABLE
AnnotationType_Enum User TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent User TABLE
CollectionAgent_log TABLE
CollectionEvent User TABLE
CollectionEvent_log TABLE
CollectionEventImage User TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation User TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty User TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation User TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries User TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User TABLE
CollectionProject_log TABLE
CollectionSpecimen User TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage User TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty User TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart User Storage Manager Storage Manager Storage Manager TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription User TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing User Storage Manager Storage Manager Storage Manager TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod User TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter User TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation User TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User TABLE
Identification_log TABLE
IdentificationUnit User TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis User Storage Manager Storage Manager Storage Manager TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod User TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter User TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis User TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart User Storage Manager Storage Manager TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent Transaction User TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment Transaction User TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List User FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List User FUNCTION
CollEventImageType_List User FUNCTION
CollExchangeType_List User FUNCTION
CollIdentificationCategory_List User FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List User FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • StorageManager
  • TransactionUser
  • User

Role DataManager

Can insert, update and delete data from tables Analysis, Annotation, CollectionEvent, CollectionSpecimen, Method, MethodForAnalysis, MethodForProcessing, Processing, ProcessingMaterialCategory, ProjectAnalysis, ProjectProcessing

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis Editor TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User TABLE
Annotation_log Editor Editor TABLE
AnnotationType_Enum User TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection Editor Editor TABLE
Collection_log Editor Editor TABLE
CollectionAgent User Editor Editor Editor TABLE
CollectionAgent_log Editor Editor TABLE
CollectionEvent User Editor Editor TABLE
CollectionEvent_log Editor Editor TABLE
CollectionEventImage User Editor Editor Editor TABLE
CollectionEventImage_log Editor Editor TABLE
CollectionEventLocalisation User Typist Typist Editor TABLE
CollectionEventLocalisation_log Typist Typist TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log Editor Editor TABLE
CollectionEventProperty User Typist Typist Editor TABLE
CollectionEventProperty_log Typist Typist TABLE
CollectionEventRegulation User Editor Editor Editor TABLE
CollectionEventRegulation_log Editor Editor TABLE
CollectionEventSeries User Editor Typist Editor TABLE
CollectionEventSeries_log Typist Typist TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User Editor Typist Editor TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage User Editor Editor TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User Editor Editor Editor TABLE
CollectionProject_log Editor Editor TABLE
CollectionSpecimen Typist Editor Editor TABLE
CollectionSpecimen_log Editor Editor TABLE
CollectionSpecimenImage Typist Editor Editor Editor TABLE
CollectionSpecimenImage_log Typist Typist TABLE
CollectionSpecimenImageProperty User Editor Editor Editor TABLE
CollectionSpecimenImageProperty_log Editor Editor TABLE
CollectionSpecimenPart User Typist Typist Editor TABLE
CollectionSpecimenPart_log Typist Typist TABLE
CollectionSpecimenPartDescription User Editor Editor Editor TABLE
CollectionSpecimenPartDescription_log Editor Editor TABLE
CollectionSpecimenProcessing User Editor Editor Editor TABLE
CollectionSpecimenProcessing_log Typist Typist TABLE
CollectionSpecimenProcessingMethod User Editor Editor Editor TABLE
CollectionSpecimenProcessingMethod_log Editor Editor TABLE
CollectionSpecimenProcessingMethodParameter User Editor Editor Editor TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User Editor Editor Editor TABLE
CollectionSpecimenReference_log Editor Editor TABLE
CollectionSpecimenRelation User Editor Editor Editor TABLE
CollectionSpecimenRelation_log Editor Editor TABLE
CollectionSpecimenTransaction User Typist Typist Editor TABLE
CollectionSpecimenTransaction_log Typist Typist TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum Editor TABLE
CollEventImageType_Enum Editor TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum Editor TABLE
CollIdentificationCategory_Enum Editor TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum Editor TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User Editor Editor Editor TABLE
ExternalIdentifier_log Editor Editor TABLE
ExternalIdentifierType User Editor Editor Editor TABLE
ExternalIdentifierType_log Editor TABLE
Identification User Typist Typist Editor TABLE
Identification_log Editor Editor TABLE
IdentificationUnit User Editor Editor Editor TABLE
IdentificationUnit_log Editor Editor TABLE
IdentificationUnitAnalysis User Editor Editor Editor TABLE
IdentificationUnitAnalysis_log Typist Typist TABLE
IdentificationUnitAnalysisMethod User Editor Editor Editor TABLE
IdentificationUnitAnalysisMethod_log Editor Editor TABLE
IdentificationUnitAnalysisMethodParameter User Editor Editor Editor TABLE
IdentificationUnitAnalysisMethodParameter_log Editor Editor TABLE
IdentificationUnitGeoAnalysis User Editor Editor Editor TABLE
IdentificationUnitGeoAnalysis_log Editor TABLE
IdentificationUnitInPart User Typist Typist Editor TABLE
IdentificationUnitInPart_log Typist Typist TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log Editor TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher Editor TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction User TABLE
Transaction_log Typist Typist TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User Typist Typist TABLE
TransactionDocument_log Typist Typist TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString Editor FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List Editor FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List Editor FUNCTION
CollEventImageType_List Editor FUNCTION
CollExchangeType_List Editor FUNCTION
CollIdentificationCategory_List Editor FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List Editor FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr Typist FUNCTION
NextFreeAccNumber Editor FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 Editor PROCEDURE
procCopyCollectionSpecimenPart Editor PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent Editor PROCEDURE
procSetVersionCollectionSpecimen Editor PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • Editor

Role DescriptionEditor

Role with write access to the tables for the desprition of the database objects

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult TABLE
AnalysisTaxonomicGroup TABLE
Annotation TABLE
Annotation_log TABLE
AnnotationType_Enum TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription TABLE
CollCircumstances_Enum TABLE
CollCollectionImageType_Enum TABLE
CollCollectionType_Enum TABLE
CollDateCategory_Enum TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent TABLE
CollectionAgent_log TABLE
CollectionEvent TABLE
CollectionEvent_log TABLE
CollectionEventImage TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask TABLE
CollectionTask_log TABLE
CollectionTaskImage TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum TABLE
CollIdentificationQualifier_Enum TABLE
CollLabelTranscriptionState_Enum TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum TABLE
CollRetrievalType_Enum TABLE
CollSpecimenImageType_Enum TABLE
CollSpecimenRelationType_Enum TABLE
CollTaskMetricAggregation_Enum TABLE
CollTaxonomicGroup_Enum TABLE
CollTransactionType_Enum TABLE
CollTypeStatus_Enum TABLE
CollUnitRelationType_Enum TABLE
Entity TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum TABLE
EntityDetermination_Enum TABLE
EntityLanguageCode_Enum TABLE
EntityRepresentation TABLE
EntityUsage TABLE
EntityUsage_Enum TABLE
EntityVisibility_Enum TABLE
ExternalIdentifier TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType TABLE
ExternalIdentifierType_log TABLE
Identification TABLE
Identification_log TABLE
IdentificationUnit TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem TABLE
MeasurementUnit_Enum TABLE
Method TABLE
Method_log TABLE
MethodForAnalysis TABLE
MethodForProcessing TABLE
Parameter TABLE
Parameter_log TABLE
ParameterValue_Enum TABLE
Processing TABLE
Processing_log TABLE
ProcessingMaterialCategory TABLE
ProjectAnalysis TABLE
ProjectMaterialCategory TABLE
ProjectProcessing TABLE
ProjectTaxonomicGroup TABLE
ProjectUser TABLE
Property TABLE
PropertyType_Enum TABLE
RegulationType_Enum TABLE
ReplicationPublisher TABLE
Task TABLE
Task_log TABLE
TaskDateType_Enum TABLE
TaskModule TABLE
TaskModule_log TABLE
TaskModuleType_Enum TABLE
TaskResult TABLE
TaskResult_log TABLE
TaskType_Enum TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent VIEW
AnnotationPart VIEW
AnnotationSpecimen VIEW
AnnotationUnit VIEW
CollectionAgent_Core VIEW
CollectionEvent_Core2 VIEW
CollectionEventID_CanEdit VIEW
CollectionEventID_UserAvailable VIEW
CollectionEventLocalisation_Core VIEW
CollectionSpecimen_Core2 VIEW
CollectionSpecimenID_Available VIEW
CollectionSpecimenID_AvailableReadOnly VIEW
CollectionSpecimenID_CanEdit VIEW
CollectionSpecimenID_Locked VIEW
CollectionSpecimenID_ReadOnly VIEW
CollectionSpecimenID_UserAvailable VIEW
CollectionSpecimenPart_Core2 VIEW
CollectionSpecimenRelationInternal VIEW
CollectionSpecimenRelationInvers VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification VIEW
Identification_Core2 VIEW
IdentificationUnit_Core2 VIEW
IdentificationUnitDisplayOrder1 VIEW
ManagerSpecimenPartList VIEW
ProjectList VIEW
ProjectListNotReadOnly VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList VIEW
TransactionList_H7 VIEW
TransactionPermit VIEW
TransactionRegulation VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL VIEW
ViewCollectionEventImage VIEW
ViewCollectionEventSeriesImage VIEW
ViewCollectionImage VIEW
ViewCollectionSpecimenImage VIEW
ViewDiversityWorkbenchModule VIEW
ViewIdentificationUnitGeoAnalysis VIEW
AgentOneString FUNCTION
AnalysisChildNodes FUNCTION
AnalysisHierarchyAll FUNCTION
AnalysisList FUNCTION
AnalysisListForUnit FUNCTION
AnalysisProjectList FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List FUNCTION
CollectionChildNodes FUNCTION
CollectionEventSeriesHierarchy FUNCTION
CollectionHierarchy FUNCTION
CollectionHierarchyAll FUNCTION
CollectionHierarchyMulti FUNCTION
CollectionHierarchySuperior FUNCTION
CollectionLocation FUNCTION
CollectionLocationAll FUNCTION
CollectionLocationChildNodes FUNCTION
CollectionLocationMulti FUNCTION
CollectionLocationSuperior FUNCTION
CollectionSpecimenCoordinateList FUNCTION
CollectionSpecimenCoordinates FUNCTION
CollectionSpecimenRelationInversList FUNCTION
CollectionTaskChildNodes FUNCTION
CollectionTaskCollectionHierarchyAll FUNCTION
CollectionTaskHierarchy FUNCTION
CollectionTaskHierarchyAll FUNCTION
CollectionTaskParentNodes FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List FUNCTION
CollIdentificationQualifier_List FUNCTION
CollLabelType_List FUNCTION
CollMaterialCategory_List FUNCTION
CollSpecimenImageType_List FUNCTION
CollTranscriptionState_List FUNCTION
CollTypeStatus_List FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser FUNCTION
CurrentUserName FUNCTION
DefaultProjectID FUNCTION
DiversityCollectionCacheDatabaseName FUNCTION
DiversityWorkbenchModule FUNCTION
EntityInformation_2 FUNCTION
EventDescription FUNCTION
EventDescriptionSuperior FUNCTION
EventSeriesChildNodes FUNCTION
EventSeriesHierarchy FUNCTION
EventSeriesSuperiorList FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber FUNCTION
EventSuperiorList FUNCTION
FirstLines_4 FUNCTION
FirstLinesEvent_2 FUNCTION
FirstLinesPart_2 FUNCTION
FirstLinesSeries FUNCTION
FirstLinesUnit_4 FUNCTION
LocalisationSystem_List FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes FUNCTION
MethodHierarchy FUNCTION
MethodHierarchyAll FUNCTION
NameList FUNCTION
NameListMyxomycetes FUNCTION
NameListPlants FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo FUNCTION
ProcessingChildNodes FUNCTION
ProcessingHierarchy FUNCTION
ProcessingHierarchyAll FUNCTION
ProcessingListForPart FUNCTION
ProcessingProjectList FUNCTION
ProjectDataLastChanges FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier FUNCTION
TaskChildNodes FUNCTION
TaskCollectionHierarchySeparator FUNCTION
TaskHierarchy FUNCTION
TaskHierarchyAll FUNCTION
TaskHierarchySeparator FUNCTION
TaxonWithQualifier FUNCTION
TransactionChildNodes FUNCTION
TransactionChildNodesAccess FUNCTION
TransactionCurrency FUNCTION
TransactionHierarchy FUNCTION
TransactionHierarchyAccess FUNCTION
TransactionHierarchyAll FUNCTION
UserCollectionList FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
DeleteXmlAttribute PROCEDURE
DeleteXmlNode PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute PROCEDURE
SetXmlValue PROCEDURE

Role Editor

Standard role for most users. Write permissions for most tables but can not delete data from tables CollectionReference and CollectionReference

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User User TABLE
Annotation_log TABLE
AnnotationType_Enum User TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent User TABLE
CollectionAgent_log TABLE
CollectionEvent User TABLE
CollectionEvent_log TABLE
CollectionEventImage User TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation User Typist Typist TABLE
CollectionEventLocalisation_log Typist Typist TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty User Typist Typist TABLE
CollectionEventProperty_log Typist Typist TABLE
CollectionEventRegulation User TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries User Typist TABLE
CollectionEventSeries_log Typist Typist TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User Typist TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage User TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User TABLE
CollectionProject_log TABLE
CollectionSpecimen Typist TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage Typist TABLE
CollectionSpecimenImage_log Typist Typist TABLE
CollectionSpecimenImageProperty User TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart User Typist Typist TABLE
CollectionSpecimenPart_log Typist Typist TABLE
CollectionSpecimenPartDescription User TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing User TABLE
CollectionSpecimenProcessing_log Typist Typist TABLE
CollectionSpecimenProcessingMethod User TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter User TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation User TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction User Typist Typist TABLE
CollectionSpecimenTransaction_log Typist Typist TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User Typist Typist TABLE
Identification_log TABLE
IdentificationUnit User TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis User TABLE
IdentificationUnitAnalysis_log Typist Typist TABLE
IdentificationUnitAnalysisMethod User TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter User TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis User TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart User Typist Typist TABLE
IdentificationUnitInPart_log Typist Typist TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction User TABLE
Transaction_log Typist Typist TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User Typist Typist TABLE
TransactionDocument_log Typist Typist TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr Typist FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • Typist
  • User

Role RegulationManager

Full access for tables CollectionEventRegulation and Regulation

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult TABLE
AnalysisTaxonomicGroup TABLE
Annotation TABLE
Annotation_log TABLE
AnnotationType_Enum TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription TABLE
CollCircumstances_Enum TABLE
CollCollectionImageType_Enum TABLE
CollCollectionType_Enum TABLE
CollDateCategory_Enum TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent TABLE
CollectionAgent_log TABLE
CollectionEvent TABLE
CollectionEvent_log TABLE
CollectionEventImage TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask TABLE
CollectionTask_log TABLE
CollectionTaskImage TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum TABLE
CollIdentificationQualifier_Enum TABLE
CollLabelTranscriptionState_Enum TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum TABLE
CollRetrievalType_Enum TABLE
CollSpecimenImageType_Enum TABLE
CollSpecimenRelationType_Enum TABLE
CollTaskMetricAggregation_Enum TABLE
CollTaxonomicGroup_Enum TABLE
CollTransactionType_Enum TABLE
CollTypeStatus_Enum TABLE
CollUnitRelationType_Enum TABLE
Entity TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum TABLE
EntityDetermination_Enum TABLE
EntityLanguageCode_Enum TABLE
EntityRepresentation TABLE
EntityUsage TABLE
EntityUsage_Enum TABLE
EntityVisibility_Enum TABLE
ExternalIdentifier TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType TABLE
ExternalIdentifierType_log TABLE
Identification TABLE
Identification_log TABLE
IdentificationUnit TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem TABLE
MeasurementUnit_Enum TABLE
Method TABLE
Method_log TABLE
MethodForAnalysis TABLE
MethodForProcessing TABLE
Parameter TABLE
Parameter_log TABLE
ParameterValue_Enum TABLE
Processing TABLE
Processing_log TABLE
ProcessingMaterialCategory TABLE
ProjectAnalysis TABLE
ProjectMaterialCategory TABLE
ProjectProcessing TABLE
ProjectTaxonomicGroup TABLE
ProjectUser TABLE
Property TABLE
PropertyType_Enum TABLE
RegulationType_Enum TABLE
ReplicationPublisher TABLE
Task TABLE
Task_log TABLE
TaskDateType_Enum TABLE
TaskModule TABLE
TaskModule_log TABLE
TaskModuleType_Enum TABLE
TaskResult TABLE
TaskResult_log TABLE
TaskType_Enum TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent VIEW
AnnotationPart VIEW
AnnotationSpecimen VIEW
AnnotationUnit VIEW
CollectionAgent_Core VIEW
CollectionEvent_Core2 VIEW
CollectionEventID_CanEdit VIEW
CollectionEventID_UserAvailable VIEW
CollectionEventLocalisation_Core VIEW
CollectionSpecimen_Core2 VIEW
CollectionSpecimenID_Available VIEW
CollectionSpecimenID_AvailableReadOnly VIEW
CollectionSpecimenID_CanEdit VIEW
CollectionSpecimenID_Locked VIEW
CollectionSpecimenID_ReadOnly VIEW
CollectionSpecimenID_UserAvailable VIEW
CollectionSpecimenPart_Core2 VIEW
CollectionSpecimenRelationInternal VIEW
CollectionSpecimenRelationInvers VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification VIEW
Identification_Core2 VIEW
IdentificationUnit_Core2 VIEW
IdentificationUnitDisplayOrder1 VIEW
ManagerSpecimenPartList VIEW
ProjectList VIEW
ProjectListNotReadOnly VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList VIEW
TransactionList_H7 VIEW
TransactionPermit VIEW
TransactionRegulation VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL VIEW
ViewCollectionEventImage VIEW
ViewCollectionEventSeriesImage VIEW
ViewCollectionImage VIEW
ViewCollectionSpecimenImage VIEW
ViewDiversityWorkbenchModule VIEW
ViewIdentificationUnitGeoAnalysis VIEW
AgentOneString FUNCTION
AnalysisChildNodes FUNCTION
AnalysisHierarchyAll FUNCTION
AnalysisList FUNCTION
AnalysisListForUnit FUNCTION
AnalysisProjectList FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List FUNCTION
CollectionChildNodes FUNCTION
CollectionEventSeriesHierarchy FUNCTION
CollectionHierarchy FUNCTION
CollectionHierarchyAll FUNCTION
CollectionHierarchyMulti FUNCTION
CollectionHierarchySuperior FUNCTION
CollectionLocation FUNCTION
CollectionLocationAll FUNCTION
CollectionLocationChildNodes FUNCTION
CollectionLocationMulti FUNCTION
CollectionLocationSuperior FUNCTION
CollectionSpecimenCoordinateList FUNCTION
CollectionSpecimenCoordinates FUNCTION
CollectionSpecimenRelationInversList FUNCTION
CollectionTaskChildNodes FUNCTION
CollectionTaskCollectionHierarchyAll FUNCTION
CollectionTaskHierarchy FUNCTION
CollectionTaskHierarchyAll FUNCTION
CollectionTaskParentNodes FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List FUNCTION
CollIdentificationQualifier_List FUNCTION
CollLabelType_List FUNCTION
CollMaterialCategory_List FUNCTION
CollSpecimenImageType_List FUNCTION
CollTranscriptionState_List FUNCTION
CollTypeStatus_List FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser FUNCTION
CurrentUserName FUNCTION
DefaultProjectID FUNCTION
DiversityCollectionCacheDatabaseName FUNCTION
DiversityWorkbenchModule FUNCTION
EntityInformation_2 FUNCTION
EventDescription FUNCTION
EventDescriptionSuperior FUNCTION
EventSeriesChildNodes FUNCTION
EventSeriesHierarchy FUNCTION
EventSeriesSuperiorList FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber FUNCTION
EventSuperiorList FUNCTION
FirstLines_4 FUNCTION
FirstLinesEvent_2 FUNCTION
FirstLinesPart_2 FUNCTION
FirstLinesSeries FUNCTION
FirstLinesUnit_4 FUNCTION
LocalisationSystem_List FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes FUNCTION
MethodHierarchy FUNCTION
MethodHierarchyAll FUNCTION
NameList FUNCTION
NameListMyxomycetes FUNCTION
NameListPlants FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo FUNCTION
ProcessingChildNodes FUNCTION
ProcessingHierarchy FUNCTION
ProcessingHierarchyAll FUNCTION
ProcessingListForPart FUNCTION
ProcessingProjectList FUNCTION
ProjectDataLastChanges FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier FUNCTION
TaskChildNodes FUNCTION
TaskCollectionHierarchySeparator FUNCTION
TaskHierarchy FUNCTION
TaskHierarchyAll FUNCTION
TaskHierarchySeparator FUNCTION
TaxonWithQualifier FUNCTION
TransactionChildNodes FUNCTION
TransactionChildNodesAccess FUNCTION
TransactionCurrency FUNCTION
TransactionHierarchy FUNCTION
TransactionHierarchyAccess FUNCTION
TransactionHierarchyAll FUNCTION
UserCollectionList FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
DeleteXmlAttribute PROCEDURE
DeleteXmlNode PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute PROCEDURE
SetXmlValue PROCEDURE

Role Replicator

Role with special rights needed for replication

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult TABLE
AnalysisTaxonomicGroup TABLE
Annotation TABLE
Annotation_log TABLE
AnnotationType_Enum TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription TABLE
CollCircumstances_Enum TABLE
CollCollectionImageType_Enum TABLE
CollCollectionType_Enum TABLE
CollDateCategory_Enum TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent TABLE
CollectionAgent_log TABLE
CollectionEvent TABLE
CollectionEvent_log TABLE
CollectionEventImage TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask TABLE
CollectionTask_log TABLE
CollectionTaskImage TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum TABLE
CollIdentificationQualifier_Enum TABLE
CollLabelTranscriptionState_Enum TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum TABLE
CollRetrievalType_Enum TABLE
CollSpecimenImageType_Enum TABLE
CollSpecimenRelationType_Enum TABLE
CollTaskMetricAggregation_Enum TABLE
CollTaxonomicGroup_Enum TABLE
CollTransactionType_Enum TABLE
CollTypeStatus_Enum TABLE
CollUnitRelationType_Enum TABLE
Entity TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum TABLE
EntityDetermination_Enum TABLE
EntityLanguageCode_Enum TABLE
EntityRepresentation TABLE
EntityUsage TABLE
EntityUsage_Enum TABLE
EntityVisibility_Enum TABLE
ExternalIdentifier TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType TABLE
ExternalIdentifierType_log TABLE
Identification TABLE
Identification_log TABLE
IdentificationUnit TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem TABLE
MeasurementUnit_Enum TABLE
Method TABLE
Method_log TABLE
MethodForAnalysis TABLE
MethodForProcessing TABLE
Parameter TABLE
Parameter_log TABLE
ParameterValue_Enum TABLE
Processing TABLE
Processing_log TABLE
ProcessingMaterialCategory TABLE
ProjectAnalysis TABLE
ProjectMaterialCategory TABLE
ProjectProcessing TABLE
ProjectTaxonomicGroup TABLE
ProjectUser TABLE
Property TABLE
PropertyType_Enum TABLE
RegulationType_Enum TABLE
ReplicationPublisher TABLE
Task TABLE
Task_log TABLE
TaskDateType_Enum TABLE
TaskModule TABLE
TaskModule_log TABLE
TaskModuleType_Enum TABLE
TaskResult TABLE
TaskResult_log TABLE
TaskType_Enum TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent VIEW
AnnotationPart VIEW
AnnotationSpecimen VIEW
AnnotationUnit VIEW
CollectionAgent_Core VIEW
CollectionEvent_Core2 VIEW
CollectionEventID_CanEdit VIEW
CollectionEventID_UserAvailable VIEW
CollectionEventLocalisation_Core VIEW
CollectionSpecimen_Core2 VIEW
CollectionSpecimenID_Available VIEW
CollectionSpecimenID_AvailableReadOnly VIEW
CollectionSpecimenID_CanEdit VIEW
CollectionSpecimenID_Locked VIEW
CollectionSpecimenID_ReadOnly VIEW
CollectionSpecimenID_UserAvailable VIEW
CollectionSpecimenPart_Core2 VIEW
CollectionSpecimenRelationInternal VIEW
CollectionSpecimenRelationInvers VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification VIEW
Identification_Core2 VIEW
IdentificationUnit_Core2 VIEW
IdentificationUnitDisplayOrder1 VIEW
ManagerSpecimenPartList VIEW
ProjectList VIEW
ProjectListNotReadOnly VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList VIEW
TransactionList_H7 VIEW
TransactionPermit VIEW
TransactionRegulation VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL VIEW
ViewCollectionEventImage VIEW
ViewCollectionEventSeriesImage VIEW
ViewCollectionImage VIEW
ViewCollectionSpecimenImage VIEW
ViewDiversityWorkbenchModule VIEW
ViewIdentificationUnitGeoAnalysis VIEW
AgentOneString FUNCTION
AnalysisChildNodes FUNCTION
AnalysisHierarchyAll FUNCTION
AnalysisList FUNCTION
AnalysisListForUnit FUNCTION
AnalysisProjectList FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List FUNCTION
CollectionChildNodes FUNCTION
CollectionEventSeriesHierarchy FUNCTION
CollectionHierarchy FUNCTION
CollectionHierarchyAll FUNCTION
CollectionHierarchyMulti FUNCTION
CollectionHierarchySuperior FUNCTION
CollectionLocation FUNCTION
CollectionLocationAll FUNCTION
CollectionLocationChildNodes FUNCTION
CollectionLocationMulti FUNCTION
CollectionLocationSuperior FUNCTION
CollectionSpecimenCoordinateList FUNCTION
CollectionSpecimenCoordinates FUNCTION
CollectionSpecimenRelationInversList FUNCTION
CollectionTaskChildNodes FUNCTION
CollectionTaskCollectionHierarchyAll FUNCTION
CollectionTaskHierarchy FUNCTION
CollectionTaskHierarchyAll FUNCTION
CollectionTaskParentNodes FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List FUNCTION
CollIdentificationQualifier_List FUNCTION
CollLabelType_List FUNCTION
CollMaterialCategory_List FUNCTION
CollSpecimenImageType_List FUNCTION
CollTranscriptionState_List FUNCTION
CollTypeStatus_List FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser FUNCTION
CurrentUserName FUNCTION
DefaultProjectID FUNCTION
DiversityCollectionCacheDatabaseName FUNCTION
DiversityWorkbenchModule FUNCTION
EntityInformation_2 FUNCTION
EventDescription FUNCTION
EventDescriptionSuperior FUNCTION
EventSeriesChildNodes FUNCTION
EventSeriesHierarchy FUNCTION
EventSeriesSuperiorList FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber FUNCTION
EventSuperiorList FUNCTION
FirstLines_4 FUNCTION
FirstLinesEvent_2 FUNCTION
FirstLinesPart_2 FUNCTION
FirstLinesSeries FUNCTION
FirstLinesUnit_4 FUNCTION
LocalisationSystem_List FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes FUNCTION
MethodHierarchy FUNCTION
MethodHierarchyAll FUNCTION
NameList FUNCTION
NameListMyxomycetes FUNCTION
NameListPlants FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo FUNCTION
ProcessingChildNodes FUNCTION
ProcessingHierarchy FUNCTION
ProcessingHierarchyAll FUNCTION
ProcessingListForPart FUNCTION
ProcessingProjectList FUNCTION
ProjectDataLastChanges FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier FUNCTION
TaskChildNodes FUNCTION
TaskCollectionHierarchySeparator FUNCTION
TaskHierarchy FUNCTION
TaskHierarchyAll FUNCTION
TaskHierarchySeparator FUNCTION
TaxonWithQualifier FUNCTION
TransactionChildNodes FUNCTION
TransactionChildNodesAccess FUNCTION
TransactionCurrency FUNCTION
TransactionHierarchy FUNCTION
TransactionHierarchyAccess FUNCTION
TransactionHierarchyAll FUNCTION
UserCollectionList FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
DeleteXmlAttribute PROCEDURE
DeleteXmlNode PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute PROCEDURE
SetXmlValue PROCEDURE

Role Requester

Role with the permission to place requests for loans

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult TABLE
AnalysisTaxonomicGroup TABLE
Annotation TABLE
Annotation_log TABLE
AnnotationType_Enum TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription TABLE
CollCircumstances_Enum TABLE
CollCollectionImageType_Enum TABLE
CollCollectionType_Enum TABLE
CollDateCategory_Enum TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent TABLE
CollectionAgent_log TABLE
CollectionEvent TABLE
CollectionEvent_log TABLE
CollectionEventImage TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask TABLE
CollectionTask_log TABLE
CollectionTaskImage TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum TABLE
CollIdentificationQualifier_Enum TABLE
CollLabelTranscriptionState_Enum TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum TABLE
CollRetrievalType_Enum TABLE
CollSpecimenImageType_Enum TABLE
CollSpecimenRelationType_Enum TABLE
CollTaskMetricAggregation_Enum TABLE
CollTaxonomicGroup_Enum TABLE
CollTransactionType_Enum TABLE
CollTypeStatus_Enum TABLE
CollUnitRelationType_Enum TABLE
Entity TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum TABLE
EntityDetermination_Enum TABLE
EntityLanguageCode_Enum TABLE
EntityRepresentation TABLE
EntityUsage TABLE
EntityUsage_Enum TABLE
EntityVisibility_Enum TABLE
ExternalIdentifier TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType TABLE
ExternalIdentifierType_log TABLE
Identification TABLE
Identification_log TABLE
IdentificationUnit TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem TABLE
MeasurementUnit_Enum TABLE
Method TABLE
Method_log TABLE
MethodForAnalysis TABLE
MethodForProcessing TABLE
Parameter TABLE
Parameter_log TABLE
ParameterValue_Enum TABLE
Processing TABLE
Processing_log TABLE
ProcessingMaterialCategory TABLE
ProjectAnalysis TABLE
ProjectMaterialCategory TABLE
ProjectProcessing TABLE
ProjectTaxonomicGroup TABLE
ProjectUser TABLE
Property TABLE
PropertyType_Enum TABLE
RegulationType_Enum TABLE
ReplicationPublisher TABLE
Task TABLE
Task_log TABLE
TaskDateType_Enum TABLE
TaskModule TABLE
TaskModule_log TABLE
TaskModuleType_Enum TABLE
TaskResult TABLE
TaskResult_log TABLE
TaskType_Enum TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent VIEW
AnnotationPart VIEW
AnnotationSpecimen VIEW
AnnotationUnit VIEW
CollectionAgent_Core VIEW
CollectionEvent_Core2 VIEW
CollectionEventID_CanEdit VIEW
CollectionEventID_UserAvailable VIEW
CollectionEventLocalisation_Core VIEW
CollectionSpecimen_Core2 VIEW
CollectionSpecimenID_Available VIEW
CollectionSpecimenID_AvailableReadOnly VIEW
CollectionSpecimenID_CanEdit VIEW
CollectionSpecimenID_Locked VIEW
CollectionSpecimenID_ReadOnly VIEW
CollectionSpecimenID_UserAvailable VIEW
CollectionSpecimenPart_Core2 VIEW
CollectionSpecimenRelationInternal VIEW
CollectionSpecimenRelationInvers VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification VIEW
Identification_Core2 VIEW
IdentificationUnit_Core2 VIEW
IdentificationUnitDisplayOrder1 VIEW
ManagerSpecimenPartList VIEW
ProjectList VIEW
ProjectListNotReadOnly VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList VIEW
TransactionList_H7 VIEW
TransactionPermit VIEW
TransactionRegulation VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL VIEW
ViewCollectionEventImage VIEW
ViewCollectionEventSeriesImage VIEW
ViewCollectionImage VIEW
ViewCollectionSpecimenImage VIEW
ViewDiversityWorkbenchModule VIEW
ViewIdentificationUnitGeoAnalysis VIEW
AgentOneString FUNCTION
AnalysisChildNodes FUNCTION
AnalysisHierarchyAll FUNCTION
AnalysisList FUNCTION
AnalysisListForUnit FUNCTION
AnalysisProjectList FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List FUNCTION
CollectionChildNodes FUNCTION
CollectionEventSeriesHierarchy FUNCTION
CollectionHierarchy FUNCTION
CollectionHierarchyAll FUNCTION
CollectionHierarchyMulti FUNCTION
CollectionHierarchySuperior FUNCTION
CollectionLocation FUNCTION
CollectionLocationAll FUNCTION
CollectionLocationChildNodes FUNCTION
CollectionLocationMulti FUNCTION
CollectionLocationSuperior FUNCTION
CollectionSpecimenCoordinateList FUNCTION
CollectionSpecimenCoordinates FUNCTION
CollectionSpecimenRelationInversList FUNCTION
CollectionTaskChildNodes FUNCTION
CollectionTaskCollectionHierarchyAll FUNCTION
CollectionTaskHierarchy FUNCTION
CollectionTaskHierarchyAll FUNCTION
CollectionTaskParentNodes FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List FUNCTION
CollIdentificationQualifier_List FUNCTION
CollLabelType_List FUNCTION
CollMaterialCategory_List FUNCTION
CollSpecimenImageType_List FUNCTION
CollTranscriptionState_List FUNCTION
CollTypeStatus_List FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser FUNCTION
CurrentUserName FUNCTION
DefaultProjectID FUNCTION
DiversityCollectionCacheDatabaseName FUNCTION
DiversityWorkbenchModule FUNCTION
EntityInformation_2 FUNCTION
EventDescription FUNCTION
EventDescriptionSuperior FUNCTION
EventSeriesChildNodes FUNCTION
EventSeriesHierarchy FUNCTION
EventSeriesSuperiorList FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber FUNCTION
EventSuperiorList FUNCTION
FirstLines_4 FUNCTION
FirstLinesEvent_2 FUNCTION
FirstLinesPart_2 FUNCTION
FirstLinesSeries FUNCTION
FirstLinesUnit_4 FUNCTION
LocalisationSystem_List FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes FUNCTION
MethodHierarchy FUNCTION
MethodHierarchyAll FUNCTION
NameList FUNCTION
NameListMyxomycetes FUNCTION
NameListPlants FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo FUNCTION
ProcessingChildNodes FUNCTION
ProcessingHierarchy FUNCTION
ProcessingHierarchyAll FUNCTION
ProcessingListForPart FUNCTION
ProcessingProjectList FUNCTION
ProjectDataLastChanges FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier FUNCTION
TaskChildNodes FUNCTION
TaskCollectionHierarchySeparator FUNCTION
TaskHierarchy FUNCTION
TaskHierarchyAll FUNCTION
TaskHierarchySeparator FUNCTION
TaxonWithQualifier FUNCTION
TransactionChildNodes FUNCTION
TransactionChildNodesAccess FUNCTION
TransactionCurrency FUNCTION
TransactionHierarchy FUNCTION
TransactionHierarchyAccess FUNCTION
TransactionHierarchyAll FUNCTION
UserCollectionList FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
DeleteXmlAttribute PROCEDURE
DeleteXmlNode PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute PROCEDURE
SetXmlValue PROCEDURE

Role StorageManager

Role for handling Reference References and related information

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis User TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User User TABLE
Annotation_log TABLE
AnnotationType_Enum User TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection User TABLE
Collection_log TABLE
CollectionAgent User TABLE
CollectionAgent_log TABLE
CollectionEvent User TABLE
CollectionEvent_log TABLE
CollectionEventImage User TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation User TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty User TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation User TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries User TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage User TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User TABLE
CollectionProject_log TABLE
CollectionSpecimen User TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage User TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty User TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart User TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription User TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing User TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod User TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter User TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation User TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction User TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User TABLE
Identification_log TABLE
IdentificationUnit User TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis User TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod User TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter User TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis User TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart User TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction User TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List User FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List User FUNCTION
CollEventImageType_List User FUNCTION
CollExchangeType_List User FUNCTION
CollIdentificationCategory_List User FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List User FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • User

Role TransactionUser

Database Role with reading accesss to Transaction information.

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult TABLE
AnalysisTaxonomicGroup TABLE
Annotation TABLE
Annotation_log TABLE
AnnotationType_Enum TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription TABLE
CollCircumstances_Enum TABLE
CollCollectionImageType_Enum TABLE
CollCollectionType_Enum TABLE
CollDateCategory_Enum TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent TABLE
CollectionAgent_log TABLE
CollectionEvent TABLE
CollectionEvent_log TABLE
CollectionEventImage TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask TABLE
CollectionTask_log TABLE
CollectionTaskImage TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum TABLE
CollIdentificationQualifier_Enum TABLE
CollLabelTranscriptionState_Enum TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum TABLE
CollRetrievalType_Enum TABLE
CollSpecimenImageType_Enum TABLE
CollSpecimenRelationType_Enum TABLE
CollTaskMetricAggregation_Enum TABLE
CollTaxonomicGroup_Enum TABLE
CollTransactionType_Enum TABLE
CollTypeStatus_Enum TABLE
CollUnitRelationType_Enum TABLE
Entity TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum TABLE
EntityDetermination_Enum TABLE
EntityLanguageCode_Enum TABLE
EntityRepresentation TABLE
EntityUsage TABLE
EntityUsage_Enum TABLE
EntityVisibility_Enum TABLE
ExternalIdentifier TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType TABLE
ExternalIdentifierType_log TABLE
Identification TABLE
Identification_log TABLE
IdentificationUnit TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem TABLE
MeasurementUnit_Enum TABLE
Method TABLE
Method_log TABLE
MethodForAnalysis TABLE
MethodForProcessing TABLE
Parameter TABLE
Parameter_log TABLE
ParameterValue_Enum TABLE
Processing TABLE
Processing_log TABLE
ProcessingMaterialCategory TABLE
ProjectAnalysis TABLE
ProjectMaterialCategory TABLE
ProjectProcessing TABLE
ProjectTaxonomicGroup TABLE
ProjectUser TABLE
Property TABLE
PropertyType_Enum TABLE
RegulationType_Enum TABLE
ReplicationPublisher TABLE
Task TABLE
Task_log TABLE
TaskDateType_Enum TABLE
TaskModule TABLE
TaskModule_log TABLE
TaskModuleType_Enum TABLE
TaskResult TABLE
TaskResult_log TABLE
TaskType_Enum TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent VIEW
AnnotationPart VIEW
AnnotationSpecimen VIEW
AnnotationUnit VIEW
CollectionAgent_Core VIEW
CollectionEvent_Core2 VIEW
CollectionEventID_CanEdit VIEW
CollectionEventID_UserAvailable VIEW
CollectionEventLocalisation_Core VIEW
CollectionSpecimen_Core2 VIEW
CollectionSpecimenID_Available VIEW
CollectionSpecimenID_AvailableReadOnly VIEW
CollectionSpecimenID_CanEdit VIEW
CollectionSpecimenID_Locked VIEW
CollectionSpecimenID_ReadOnly VIEW
CollectionSpecimenID_UserAvailable VIEW
CollectionSpecimenPart_Core2 VIEW
CollectionSpecimenRelationInternal VIEW
CollectionSpecimenRelationInvers VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification VIEW
Identification_Core2 VIEW
IdentificationUnit_Core2 VIEW
IdentificationUnitDisplayOrder1 VIEW
ManagerSpecimenPartList VIEW
ProjectList VIEW
ProjectListNotReadOnly VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList VIEW
TransactionList_H7 VIEW
TransactionPermit VIEW
TransactionRegulation VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL VIEW
ViewCollectionEventImage VIEW
ViewCollectionEventSeriesImage VIEW
ViewCollectionImage VIEW
ViewCollectionSpecimenImage VIEW
ViewDiversityWorkbenchModule VIEW
ViewIdentificationUnitGeoAnalysis VIEW
AgentOneString FUNCTION
AnalysisChildNodes FUNCTION
AnalysisHierarchyAll FUNCTION
AnalysisList FUNCTION
AnalysisListForUnit FUNCTION
AnalysisProjectList FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List FUNCTION
CollectionChildNodes FUNCTION
CollectionEventSeriesHierarchy FUNCTION
CollectionHierarchy FUNCTION
CollectionHierarchyAll FUNCTION
CollectionHierarchyMulti FUNCTION
CollectionHierarchySuperior FUNCTION
CollectionLocation FUNCTION
CollectionLocationAll FUNCTION
CollectionLocationChildNodes FUNCTION
CollectionLocationMulti FUNCTION
CollectionLocationSuperior FUNCTION
CollectionSpecimenCoordinateList FUNCTION
CollectionSpecimenCoordinates FUNCTION
CollectionSpecimenRelationInversList FUNCTION
CollectionTaskChildNodes FUNCTION
CollectionTaskCollectionHierarchyAll FUNCTION
CollectionTaskHierarchy FUNCTION
CollectionTaskHierarchyAll FUNCTION
CollectionTaskParentNodes FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List FUNCTION
CollIdentificationQualifier_List FUNCTION
CollLabelType_List FUNCTION
CollMaterialCategory_List FUNCTION
CollSpecimenImageType_List FUNCTION
CollTranscriptionState_List FUNCTION
CollTypeStatus_List FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser FUNCTION
CurrentUserName FUNCTION
DefaultProjectID FUNCTION
DiversityCollectionCacheDatabaseName FUNCTION
DiversityWorkbenchModule FUNCTION
EntityInformation_2 FUNCTION
EventDescription FUNCTION
EventDescriptionSuperior FUNCTION
EventSeriesChildNodes FUNCTION
EventSeriesHierarchy FUNCTION
EventSeriesSuperiorList FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber FUNCTION
EventSuperiorList FUNCTION
FirstLines_4 FUNCTION
FirstLinesEvent_2 FUNCTION
FirstLinesPart_2 FUNCTION
FirstLinesSeries FUNCTION
FirstLinesUnit_4 FUNCTION
LocalisationSystem_List FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes FUNCTION
MethodHierarchy FUNCTION
MethodHierarchyAll FUNCTION
NameList FUNCTION
NameListMyxomycetes FUNCTION
NameListPlants FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo FUNCTION
ProcessingChildNodes FUNCTION
ProcessingHierarchy FUNCTION
ProcessingHierarchyAll FUNCTION
ProcessingListForPart FUNCTION
ProcessingProjectList FUNCTION
ProjectDataLastChanges FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier FUNCTION
TaskChildNodes FUNCTION
TaskCollectionHierarchySeparator FUNCTION
TaskHierarchy FUNCTION
TaskHierarchyAll FUNCTION
TaskHierarchySeparator FUNCTION
TaxonWithQualifier FUNCTION
TransactionChildNodes FUNCTION
TransactionChildNodesAccess FUNCTION
TransactionCurrency FUNCTION
TransactionHierarchy FUNCTION
TransactionHierarchyAccess FUNCTION
TransactionHierarchyAll FUNCTION
UserCollectionList FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
DeleteXmlAttribute PROCEDURE
DeleteXmlNode PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute PROCEDURE
SetXmlValue PROCEDURE

Role Typist

Write access to most objects. Can not delete data and not insert data into tables CollectionReference and CollectionReference

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis User TABLE
Analysis_log TABLE
AnalysisResult User TABLE
AnalysisTaxonomicGroup User TABLE
Annotation User User User TABLE
Annotation_log TABLE
AnnotationType_Enum User TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription User User User User TABLE
CollCircumstances_Enum User TABLE
CollCollectionImageType_Enum User TABLE
CollCollectionType_Enum User TABLE
CollDateCategory_Enum User TABLE
Collection User TABLE
Collection_log TABLE
CollectionAgent User TABLE
CollectionAgent_log TABLE
CollectionEvent User TABLE
CollectionEvent_log TABLE
CollectionEventImage User TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation User TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod User TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue User TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty User TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation User TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries User TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage User TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource User TABLE
CollectionExternalDatasource_log TABLE
CollectionImage User TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject User TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty User TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart User TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription User TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing User TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod User TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter User TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference User TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation User TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction User TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask User TABLE
CollectionTask_log TABLE
CollectionTaskImage User TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric User TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum User TABLE
CollEventImageType_Enum User TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum User TABLE
CollExchangeType_Enum User TABLE
CollIdentificationCategory_Enum User TABLE
CollIdentificationDateCategory_Enum User TABLE
CollIdentificationQualifier_Enum User TABLE
CollLabelTranscriptionState_Enum User TABLE
CollLabelType_Enum User TABLE
CollMaterialCategory_Enum User TABLE
CollRetrievalType_Enum User TABLE
CollSpecimenImageType_Enum User TABLE
CollSpecimenRelationType_Enum User TABLE
CollTaskMetricAggregation_Enum User TABLE
CollTaxonomicGroup_Enum User TABLE
CollTransactionType_Enum User TABLE
CollTypeStatus_Enum User TABLE
CollUnitRelationType_Enum User TABLE
Entity User TABLE
EntityAccessibility_Enum User TABLE
EntityContext_Enum User TABLE
EntityDetermination_Enum User TABLE
EntityLanguageCode_Enum User TABLE
EntityRepresentation User TABLE
EntityUsage User TABLE
EntityUsage_Enum User TABLE
EntityVisibility_Enum User TABLE
ExternalIdentifier User TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType User TABLE
ExternalIdentifierType_log TABLE
Identification User TABLE
Identification_log TABLE
IdentificationUnit User TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis User TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod User TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter User TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis User TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart User TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem User TABLE
MeasurementUnit_Enum TABLE
Method User TABLE
Method_log TABLE
MethodForAnalysis User TABLE
MethodForProcessing User TABLE
Parameter User TABLE
Parameter_log TABLE
ParameterValue_Enum User TABLE
Processing User TABLE
Processing_log TABLE
ProcessingMaterialCategory User TABLE
ProjectAnalysis User TABLE
ProjectMaterialCategory User TABLE
ProjectProcessing User TABLE
ProjectTaxonomicGroup User TABLE
ProjectUser User TABLE
Property User TABLE
PropertyType_Enum TABLE
RegulationType_Enum User TABLE
ReplicationPublisher TABLE
Task User TABLE
Task_log TABLE
TaskDateType_Enum User TABLE
TaskModule User TABLE
TaskModule_log TABLE
TaskModuleType_Enum User TABLE
TaskResult User TABLE
TaskResult_log TABLE
TaskType_Enum User TABLE
Transaction User TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment User TABLE
TransactionDocument User TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent User VIEW
AnnotationPart User VIEW
AnnotationSpecimen User VIEW
AnnotationUnit User VIEW
CollectionAgent_Core User VIEW
CollectionEvent_Core2 User VIEW
CollectionEventID_CanEdit User VIEW
CollectionEventID_UserAvailable User VIEW
CollectionEventLocalisation_Core User VIEW
CollectionSpecimen_Core2 User VIEW
CollectionSpecimenID_Available User VIEW
CollectionSpecimenID_AvailableReadOnly User VIEW
CollectionSpecimenID_CanEdit User VIEW
CollectionSpecimenID_Locked User VIEW
CollectionSpecimenID_ReadOnly User VIEW
CollectionSpecimenID_UserAvailable User VIEW
CollectionSpecimenPart_Core2 User VIEW
CollectionSpecimenRelationInternal User VIEW
CollectionSpecimenRelationInvers User VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification User VIEW
Identification_Core2 User VIEW
IdentificationUnit_Core2 User VIEW
IdentificationUnitDisplayOrder1 User VIEW
ManagerSpecimenPartList VIEW
ProjectList User VIEW
ProjectListNotReadOnly User VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList User VIEW
TransactionList_H7 User VIEW
TransactionPermit User VIEW
TransactionRegulation User VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL User VIEW
ViewCollectionEventImage User VIEW
ViewCollectionEventSeriesImage User VIEW
ViewCollectionImage User VIEW
ViewCollectionSpecimenImage User VIEW
ViewDiversityWorkbenchModule User VIEW
ViewIdentificationUnitGeoAnalysis User VIEW
AgentOneString FUNCTION
AnalysisChildNodes User FUNCTION
AnalysisHierarchyAll User FUNCTION
AnalysisList User FUNCTION
AnalysisListForUnit User FUNCTION
AnalysisProjectList User FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL User FUNCTION
CollCharacterType_List User FUNCTION
CollDateCategory_List User FUNCTION
CollectionChildNodes User FUNCTION
CollectionEventSeriesHierarchy User FUNCTION
CollectionHierarchy User FUNCTION
CollectionHierarchyAll User FUNCTION
CollectionHierarchyMulti User FUNCTION
CollectionHierarchySuperior User FUNCTION
CollectionLocation User FUNCTION
CollectionLocationAll User FUNCTION
CollectionLocationChildNodes User FUNCTION
CollectionLocationMulti User FUNCTION
CollectionLocationSuperior User FUNCTION
CollectionSpecimenCoordinateList User FUNCTION
CollectionSpecimenCoordinates User FUNCTION
CollectionSpecimenRelationInversList User FUNCTION
CollectionTaskChildNodes User FUNCTION
CollectionTaskCollectionHierarchyAll User FUNCTION
CollectionTaskHierarchy User FUNCTION
CollectionTaskHierarchyAll User FUNCTION
CollectionTaskParentNodes User FUNCTION
CollEventDateCategory_List User FUNCTION
CollEventImageType_List User FUNCTION
CollExchangeType_List User FUNCTION
CollIdentificationCategory_List User FUNCTION
CollIdentificationDateCategory_List User FUNCTION
CollIdentificationQualifier_List User FUNCTION
CollLabelType_List User FUNCTION
CollMaterialCategory_List User FUNCTION
CollSpecimenImageType_List User FUNCTION
CollTranscriptionState_List User FUNCTION
CollTypeStatus_List User FUNCTION
ColTaxonomicGroup_List User FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser User FUNCTION
CurrentUserName User FUNCTION
DefaultProjectID User FUNCTION
DiversityCollectionCacheDatabaseName User FUNCTION
DiversityWorkbenchModule User FUNCTION
EntityInformation_2 User FUNCTION
EventDescription User FUNCTION
EventDescriptionSuperior User FUNCTION
EventSeriesChildNodes User FUNCTION
EventSeriesHierarchy User FUNCTION
EventSeriesSuperiorList User FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber User FUNCTION
EventSuperiorList User FUNCTION
FirstLines_4 User FUNCTION
FirstLinesEvent_2 User FUNCTION
FirstLinesPart_2 User FUNCTION
FirstLinesSeries User FUNCTION
FirstLinesUnit_4 User FUNCTION
LocalisationSystem_List User FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes User FUNCTION
MethodHierarchy User FUNCTION
MethodHierarchyAll User FUNCTION
NameList User FUNCTION
NameListMyxomycetes User FUNCTION
NameListPlants User FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo User FUNCTION
ProcessingChildNodes User FUNCTION
ProcessingHierarchy User FUNCTION
ProcessingHierarchyAll User FUNCTION
ProcessingListForPart User FUNCTION
ProcessingProjectList User FUNCTION
ProjectDataLastChanges User FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier User FUNCTION
TaskChildNodes User FUNCTION
TaskCollectionHierarchySeparator User FUNCTION
TaskHierarchy User FUNCTION
TaskHierarchyAll User FUNCTION
TaskHierarchySeparator User FUNCTION
TaxonWithQualifier User FUNCTION
TransactionChildNodes User FUNCTION
TransactionChildNodesAccess User FUNCTION
TransactionCurrency User FUNCTION
TransactionHierarchy User FUNCTION
TransactionHierarchyAccess User FUNCTION
TransactionHierarchyAll User FUNCTION
UserCollectionList User FUNCTION
UserID User FUNCTION
Version User FUNCTION
VersionClient User FUNCTION
DeleteXmlAttribute User PROCEDURE
DeleteXmlNode User PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription User PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute User PROCEDURE
SetXmlValue User PROCEDURE
Inheriting from roles:
  • User

Role User

Restricted to read access to all tables. Can insert data into table Annotation

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Analysis TABLE
Analysis_log TABLE
AnalysisResult TABLE
AnalysisTaxonomicGroup TABLE
Annotation TABLE
Annotation_log TABLE
AnnotationType_Enum TABLE
AnonymCollector TABLE
CacheDatabase2 TABLE
CacheDescription TABLE
CollCircumstances_Enum TABLE
CollCollectionImageType_Enum TABLE
CollCollectionType_Enum TABLE
CollDateCategory_Enum TABLE
Collection TABLE
Collection_log TABLE
CollectionAgent TABLE
CollectionAgent_log TABLE
CollectionEvent TABLE
CollectionEvent_log TABLE
CollectionEventImage TABLE
CollectionEventImage_log TABLE
CollectionEventLocalisation TABLE
CollectionEventLocalisation_log TABLE
CollectionEventMethod TABLE
CollectionEventMethod_log TABLE
CollectionEventParameterValue TABLE
CollectionEventParameterValue_log TABLE
CollectionEventProperty TABLE
CollectionEventProperty_log TABLE
CollectionEventRegulation TABLE
CollectionEventRegulation_log TABLE
CollectionEventSeries TABLE
CollectionEventSeries_log TABLE
CollectionEventSeriesDescriptor TABLE
CollectionEventSeriesDescriptor_log TABLE
CollectionEventSeriesImage TABLE
CollectionEventSeriesImage_log TABLE
CollectionExternalDatasource TABLE
CollectionExternalDatasource_log TABLE
CollectionImage TABLE
CollectionImage_log TABLE
CollectionManager TABLE
CollectionProject TABLE
CollectionProject_log TABLE
CollectionSpecimen TABLE
CollectionSpecimen_log TABLE
CollectionSpecimenImage TABLE
CollectionSpecimenImage_log TABLE
CollectionSpecimenImageProperty TABLE
CollectionSpecimenImageProperty_log TABLE
CollectionSpecimenPart TABLE
CollectionSpecimenPart_log TABLE
CollectionSpecimenPartDescription TABLE
CollectionSpecimenPartDescription_log TABLE
CollectionSpecimenProcessing TABLE
CollectionSpecimenProcessing_log TABLE
CollectionSpecimenProcessingMethod TABLE
CollectionSpecimenProcessingMethod_log TABLE
CollectionSpecimenProcessingMethodParameter TABLE
CollectionSpecimenProcessingMethodParameter_log TABLE
CollectionSpecimenReference TABLE
CollectionSpecimenReference_log TABLE
CollectionSpecimenRelation TABLE
CollectionSpecimenRelation_log TABLE
CollectionSpecimenTransaction TABLE
CollectionSpecimenTransaction_log TABLE
CollectionTask TABLE
CollectionTask_log TABLE
CollectionTaskImage TABLE
CollectionTaskImage_log TABLE
CollectionTaskMetric TABLE
CollectionTaskMetric_log TABLE
CollEventDateCategory_Enum TABLE
CollEventImageType_Enum TABLE
CollEventSeriesDescriptorType_Enum TABLE
CollEventSeriesImageType_Enum TABLE
CollExchangeType_Enum TABLE
CollIdentificationCategory_Enum TABLE
CollIdentificationDateCategory_Enum TABLE
CollIdentificationQualifier_Enum TABLE
CollLabelTranscriptionState_Enum TABLE
CollLabelType_Enum TABLE
CollMaterialCategory_Enum TABLE
CollRetrievalType_Enum TABLE
CollSpecimenImageType_Enum TABLE
CollSpecimenRelationType_Enum TABLE
CollTaskMetricAggregation_Enum TABLE
CollTaxonomicGroup_Enum TABLE
CollTransactionType_Enum TABLE
CollTypeStatus_Enum TABLE
CollUnitRelationType_Enum TABLE
Entity TABLE
EntityAccessibility_Enum TABLE
EntityContext_Enum TABLE
EntityDetermination_Enum TABLE
EntityLanguageCode_Enum TABLE
EntityRepresentation TABLE
EntityUsage TABLE
EntityUsage_Enum TABLE
EntityVisibility_Enum TABLE
ExternalIdentifier TABLE
ExternalIdentifier_log TABLE
ExternalIdentifierType TABLE
ExternalIdentifierType_log TABLE
Identification TABLE
Identification_log TABLE
IdentificationUnit TABLE
IdentificationUnit_log TABLE
IdentificationUnitAnalysis TABLE
IdentificationUnitAnalysis_log TABLE
IdentificationUnitAnalysisMethod TABLE
IdentificationUnitAnalysisMethod_log TABLE
IdentificationUnitAnalysisMethodParameter TABLE
IdentificationUnitAnalysisMethodParameter_log TABLE
IdentificationUnitGeoAnalysis TABLE
IdentificationUnitGeoAnalysis_log TABLE
IdentificationUnitInPart TABLE
IdentificationUnitInPart_log TABLE
LanguageCode_Enum TABLE
LocalisationSystem TABLE
MeasurementUnit_Enum TABLE
Method TABLE
Method_log TABLE
MethodForAnalysis TABLE
MethodForProcessing TABLE
Parameter TABLE
Parameter_log TABLE
ParameterValue_Enum TABLE
Processing TABLE
Processing_log TABLE
ProcessingMaterialCategory TABLE
ProjectAnalysis TABLE
ProjectMaterialCategory TABLE
ProjectProcessing TABLE
ProjectTaxonomicGroup TABLE
ProjectUser TABLE
Property TABLE
PropertyType_Enum TABLE
RegulationType_Enum TABLE
ReplicationPublisher TABLE
Task TABLE
Task_log TABLE
TaskDateType_Enum TABLE
TaskModule TABLE
TaskModule_log TABLE
TaskModuleType_Enum TABLE
TaskResult TABLE
TaskResult_log TABLE
TaskType_Enum TABLE
Transaction TABLE
Transaction_log TABLE
TransactionAgent TABLE
TransactionAgent_log TABLE
TransactionComment TABLE
TransactionDocument TABLE
TransactionDocument_log TABLE
TransactionPayment TABLE
TransactionPayment_log TABLE
AnnotationEvent VIEW
AnnotationPart VIEW
AnnotationSpecimen VIEW
AnnotationUnit VIEW
CollectionAgent_Core VIEW
CollectionEvent_Core2 VIEW
CollectionEventID_CanEdit VIEW
CollectionEventID_UserAvailable VIEW
CollectionEventLocalisation_Core VIEW
CollectionSpecimen_Core2 VIEW
CollectionSpecimenID_Available VIEW
CollectionSpecimenID_AvailableReadOnly VIEW
CollectionSpecimenID_CanEdit VIEW
CollectionSpecimenID_Locked VIEW
CollectionSpecimenID_ReadOnly VIEW
CollectionSpecimenID_UserAvailable VIEW
CollectionSpecimenPart_Core2 VIEW
CollectionSpecimenRelationInternal VIEW
CollectionSpecimenRelationInvers VIEW
CollectionSpecimenTransactionRequest VIEW
FirstLinesIdentification VIEW
Identification_Core2 VIEW
IdentificationUnit_Core2 VIEW
IdentificationUnitDisplayOrder1 VIEW
ManagerSpecimenPartList VIEW
ProjectList VIEW
ProjectListNotReadOnly VIEW
RequesterSpecimenPartList VIEW
TransactionForeignRequest VIEW
TransactionList VIEW
TransactionList_H7 VIEW
TransactionPermit VIEW
TransactionRegulation VIEW
TransactionRequest VIEW
TransactionUserRequest VIEW
UserGroups VIEW
ViewBaseURL VIEW
ViewCollectionEventImage VIEW
ViewCollectionEventSeriesImage VIEW
ViewCollectionImage VIEW
ViewCollectionSpecimenImage VIEW
ViewDiversityWorkbenchModule VIEW
ViewIdentificationUnitGeoAnalysis VIEW
AgentOneString FUNCTION
AnalysisChildNodes FUNCTION
AnalysisHierarchyAll FUNCTION
AnalysisList FUNCTION
AnalysisListForUnit FUNCTION
AnalysisProjectList FUNCTION
AnalysisTaxonomicGroupForProject FUNCTION
AverageAltitude FUNCTION
BaseURL FUNCTION
CollCharacterType_List FUNCTION
CollDateCategory_List FUNCTION
CollectionChildNodes FUNCTION
CollectionEventSeriesHierarchy FUNCTION
CollectionHierarchy FUNCTION
CollectionHierarchyAll FUNCTION
CollectionHierarchyMulti FUNCTION
CollectionHierarchySuperior FUNCTION
CollectionLocation FUNCTION
CollectionLocationAll FUNCTION
CollectionLocationChildNodes FUNCTION
CollectionLocationMulti FUNCTION
CollectionLocationSuperior FUNCTION
CollectionSpecimenCoordinateList FUNCTION
CollectionSpecimenCoordinates FUNCTION
CollectionSpecimenRelationInversList FUNCTION
CollectionTaskChildNodes FUNCTION
CollectionTaskCollectionHierarchyAll FUNCTION
CollectionTaskHierarchy FUNCTION
CollectionTaskHierarchyAll FUNCTION
CollectionTaskParentNodes FUNCTION
CollEventDateCategory_List FUNCTION
CollEventImageType_List FUNCTION
CollExchangeType_List FUNCTION
CollIdentificationCategory_List FUNCTION
CollIdentificationDateCategory_List FUNCTION
CollIdentificationQualifier_List FUNCTION
CollLabelType_List FUNCTION
CollMaterialCategory_List FUNCTION
CollSpecimenImageType_List FUNCTION
CollTranscriptionState_List FUNCTION
CollTypeStatus_List FUNCTION
ColTaxonomicGroup_List FUNCTION
CuratorCollectionHierarchyList FUNCTION
CurrentUser FUNCTION
CurrentUserName FUNCTION
DefaultProjectID FUNCTION
DiversityCollectionCacheDatabaseName FUNCTION
DiversityWorkbenchModule FUNCTION
EntityInformation_2 FUNCTION
EventDescription FUNCTION
EventDescriptionSuperior FUNCTION
EventSeriesChildNodes FUNCTION
EventSeriesHierarchy FUNCTION
EventSeriesSuperiorList FUNCTION
EventSeriesTopID FUNCTION
EventSpecimenNumber FUNCTION
EventSuperiorList FUNCTION
FirstLines_4 FUNCTION
FirstLinesEvent_2 FUNCTION
FirstLinesPart_2 FUNCTION
FirstLinesSeries FUNCTION
FirstLinesUnit_4 FUNCTION
LocalisationSystem_List FUNCTION
ManagerCollectionList FUNCTION
MethodChildNodes FUNCTION
MethodHierarchy FUNCTION
MethodHierarchyAll FUNCTION
NameList FUNCTION
NameListMyxomycetes FUNCTION
NameListPlants FUNCTION
NextFreeAccNr FUNCTION
NextFreeAccNumber FUNCTION
PrivacyConsentInfo FUNCTION
ProcessingChildNodes FUNCTION
ProcessingHierarchy FUNCTION
ProcessingHierarchyAll FUNCTION
ProcessingListForPart FUNCTION
ProcessingProjectList FUNCTION
ProjectDataLastChanges FUNCTION
RequesterCollectionList FUNCTION
StableIdentifier FUNCTION
TaskChildNodes FUNCTION
TaskCollectionHierarchySeparator FUNCTION
TaskHierarchy FUNCTION
TaskHierarchyAll FUNCTION
TaskHierarchySeparator FUNCTION
TaxonWithQualifier FUNCTION
TransactionChildNodes FUNCTION
TransactionChildNodesAccess FUNCTION
TransactionCurrency FUNCTION
TransactionHierarchy FUNCTION
TransactionHierarchyAccess FUNCTION
TransactionHierarchyAll FUNCTION
UserCollectionList FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
DeleteXmlAttribute PROCEDURE
DeleteXmlNode PROCEDURE
procCopyCollectionSpecimen2 PROCEDURE
procCopyCollectionSpecimenPart PROCEDURE
procFillCacheDescription PROCEDURE
procInsertCollectionEventCopy PROCEDURE
procSetVersionCollectionEvent PROCEDURE
procSetVersionCollectionSpecimen PROCEDURE
SetXmlAttribute PROCEDURE
SetXmlValue PROCEDURE
Jun 5, 2024

Subsections of Details

Diversity Collection

Event Tables

The image below shows the tables related to collection event.

Dec 28, 2024

Diversity Collection

Regulation Tables

The image below shows the tables related to the regluation.

Dec 28, 2024

Diversity Collection

Method Tables

The image below shows the tables related to the method.

Dec 28, 2024

Diversity Collection

Collection Tables

The image below shows the tables related to the Collection.

Dec 28, 2024

Diversity Collection

Project Tables

The image below shows the tables related to the project.

Dec 28, 2024

Diversity Collection

Analysis Tables

The image below shows the tables related to the analysis and the methods used for the analysis and charaterized by parameters. The main focus of object data are the identification units (= organisms) with an optional restriction to a certain specimen part.

Jan 14, 2025

Diversity Collection

Processing Tables

The image below shows the tables related to the Processing.

Dec 28, 2024

Diversity Collection

Transaction Tables

The image below shows the tables related to the Transaction.

Dec 28, 2024

Diversity Collection

Task Tables

The image below shows the tables related to the task.

Dec 28, 2024

Diversity Collection

Entity Tables

The image below shows the tables related to the Entity.

Dec 28, 2024

Installation

Diversity Workbench modules use Microsoft SQL-Server 2014 or above as database engine. If you do not have a database server with DiversityAgents already available, you have to install the database engine first. Download the free version of Microsoft SQL Server Express 2016 or above from http://www.microsoft.com/downloads/.. Start the program and follow the instructions for the installation.

 

Server configuration

To configure your server for remote access, launch the SQL Server Configuration Manager (see image below).

If the tool is not available via the app menu but you have SqlServerManagmentStudio and SqlServer installed type [Win] + r to open the Run dialog, type the command SQLServerManager16.msc and press [Enter] to start the tool.

Then click on the "Protocols for SQLEXPRESS" node. Right click on "TCP/IP" in the list of Protocols and choose "enable" for TCP/IP.

Right click on the TCP/IP node and select, "Properties" to open a window as shown below.

In the part IPALL clear out the value for "TCP Dynamic Ports". Give a TCP-Port number to use when making remote connections, e.g. "4321" as shown above. You have to restart the SQL Server Express service before you can connect to your database. 

If you use a database on a server, make sure that the firewall of the server allows access via the port you set for the connections (see below). 

Start the Microsoft SQL Server Managment Studio and attach the database as shown below. Choose the node "databases" and right-click on it to open the context menu (see below). Then choose "attach" from the context menu. A window will open where you can choose the file DiversityAgents_Data.MDF from your database directory and attach it to the database engine.

 

After the installation make shure to get the latest updates from http://windowsupdate.microsoft.com/.

 

Database configuration

To configure your Database, use the Client as described in

Database configuration.

Mar 26, 2024

Creation

To create or add a database, you need a windows login on the server and sysadmin permissions.

New installation

If you start with a new installation of a DiversityWorkbench database connect with the database with a click on the button. Set server and port and as described in the chapter Database access. After connecting to the server, you will get a message, that no database is available and the button will appear. Click on the button to create a new database on the server. A window as shown below will open where you enter the name or the IP-address of the database server. 

127.0.0.1 is the IP-address of your local machine, so in case of a local installation you can keep this value. Next you have to enter the port of the database server. See the chapter Installation of the database for details. 1433 is the default port for SQL-Server. We do recommend to change this port for security reasons.

After server and port are set, the next step is the definition of the database as described below.

 

Adding database

If you are already connected to a database and want to add another database, select Connection - Create database... from the menu. A window will open as shown below where you have to enter the name of the database, starting with Diversity….

After creating the database a window with the script for the creation of the objects in the database (tables, views, functions, ...) as shown below will open.

Click on the button to start the script. After the application of the script you get a message as shown below.

Close the window and you will be connected to the new database. In case there are additional updates available, please start the update of the database to ensure the latest version.

Jun 5, 2024

Configuration

To configure your Database, choose Administration → Database → Rename database to change the name of the database according to your requirements. During this renaming all processes in the database will be terminated (you will get a warning if processes from other host are active).

Afterwards you should adapt the address that is published by the database for access by other modules. Choose Administration → Database → Set published address from the menu. This will change the published address to the name of the server where your database is located and an identifier for you database, e.g. http://xy.diversityworkbench.de/Collection/

 

Mar 26, 2024

Diversity Collection

Backup

If you want to create a backup of your database, there are 2 options. You may either export the data as csv files to your local computer or you may create a backup on the server.

Export data as csv

To export your data as csv files to your local computer, choose Data → Export → CSV(bcp) ... from the menu. A window will open as shown below, where you can select the tables that should be exported. Click on the Start Export button to export your data. If you choose the option as shown below 2 files will be created for every table. The first file (*.csv) contains the data while the second file (*.xml) contains the structure of the table.

Create backup on the server

To create a backup of your database on the server, choose Data → Backup database from the menu. This will create a SQL-Server backup on the server where the database is located. Ensure that there is enough space on the server.

Another option is to create a direct copy of the database files on the server. For this you have to use the functions provided by SQL-Server. However, you need administration rights for the database you want to create a backup of. Open the Enterprise Manager for SQL-Server, choose the database and detach it from the server as shown in the image below.

After detaching the database, you can save a copy of the ..._Data.MDF file to keep it as a backup.

After storing the backup you have to reattach the database.

A dialog will appear where you have to select the original database file in your directory.

Jan 8, 2025

Diversity Collection

History

To inspect the history of a dataset click on the button. A form will open, showing all former states of the data in the tables with the current dataset at the top. The version is shown in the header of the main.

The version will be set automatically. If a dataset is changed the version will be increased if the last changes where done by a different user or the last change is more than 24 hours ago (for further details see topic Logging ).

For analysis of the succession of changes the log tables contain additional columns:

  • Kind of change: This column is set by the trigger inserting data into the log table
    • current version: This is the current state of the data in the table
    • UPDATE: This is the state of the data before an update happened
    • DELETE: This is the state of the data when the data have been deleted
  • Date of change: The date and time of the changes. This column has the default value getdate() that means the current date an time is set when any data are inserted into the log table
  • Responsible: The user reponsible for the changes. This column has the default value suser_sname() that means the current user is set when any data are inserted into the log table
  • LogID: A unique ID of the logtable. This column is an identity that means it is set by the database when any data are inserted into the log table
Mar 24, 2025

Diversity Collection

Restore from log

If you want to restore a whole data set for a specimen including all dependent data, click on the Restore deleted button. This function is as well available from the menu Data - Restore from log .... In the upcoming dialogs choose the basic table to start for the search. Depending on your data you have to choose the correct table. There are 3 main possibilities as shown in the image below: CollectionEventSeries, CollectionEvent, CollectionSpecimen. If e.g. only the specimen have been deleted an the data of the collection events are still present, choose CollectionSpecimen as starting table. In the upcoming dialogs enter the date where the query should start and end, an optional filter for a column and the number of lines from the log table that should be displayed. Finally select the datarow(s) of the root table that should be restored. After that the program will try to recover the data with all depending information. The process is demonstrated in a short tutorial Video starten.

The image below outlines the data areas for restorage

Mar 24, 2025

Logging

Changes within the database will be documented for each dataset with the time and the responsible user in the columns shown in the image below.

All main tables have a corresponding logging table. If you change or delete a dataset the orignial dataset will be stored in this logging table together with informations about who has done the changes and when it happend. To see the data stored in the logging tables, click on the button to open the history of a dataset.

Mar 26, 2024

Login administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the timespan (From - To) and the number of data sets where any activity of the current login has been found.

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

 

Creation of login

To create a new login click on the button. A window will open as shown below.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has no access will be listed in gray while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

 

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below).

There are 4 states of accessibility for projects

  •     Full access: The user can edit the data
  •      Read only access: The user can only read the data
  •      Locked: The project is locked. Nobody can change the data
  •     No access: The user has no access via a project

Projects are related to the module DiversityProjects. To get additional information about a project select it in the the list and click on the button. 

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

 

 

Overview for a login

If you see an overview of all permissions and project for a login, click on the button. A window a shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user and roles in the database. 

To remove a user, select it in the list and click on the button. 

 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates, that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

Jun 4, 2024

Diversity Collection

Linked server

Databases not available on the local server may be accessible via a linked server. Provided the option for loading the connections is set, the program will automatically try to connect to these databases. Otherwise you can connect to these databases as described in chapter ModuleConnections. To administrate the linked servers, choose Administration - Linked servers ... from the menu. A form (see below) will open where you can add linked servers and inspect the content of the available databases.

Use the  resp. buttons to add or remove a linked server. To add a linked server, you need the name of the server and the port, e.g. tnt.diversityworkbench.de, 5432, the login associated with the connection of the linked server e.g. TNT and the password for this login. The available databases will be listed as shown above. To inspect the content, select among the tables or views listed in the right part as shown above. Linked servers have certain restrictions for the availability of data, e.g. XML and geography data are not available via a linked server. For a table or view containing incompatible content you may encounter a corresponding error mentioning the reason for the incompatibility.

An expample for a linked server as provided for central databases is shown below (using the management studio for SQL-Server) Linked servers

Jul 30, 2024

Tools

These are the tools to handle the basic parts of the database. These tools are only available for the owner of the database and should be handled with care as any changes in the database may disable the connection of your client to the database. Before changing any parts of the database it is recommended to backup the current state of the database. To use these tools, choose Administation → Database → Database tools ... from the menu. A window will open as shown below.

Description

The Description section (see above) shows the basic definitions of the objects in the database and enables you to enter a description for these objects including tables and their columns, functions and their parameter etc. With the buttons SQL for adding, update and both you can generate SQL statements for the creation of the descriptions in your database. Use the button both if you are not sure if a description is already present as it will generate a SQL statement working with existing and missing descriptions (see below).

The button  Fill Cache  fills the table CacheDescription where all descriptions are collected for easy access.

 

Log table and trigger

In the Log table and trigger section (see below) click on the List tables button to see all tables within the database. The Table section shows the basic definitions of a selected table. If columns for logging the date and responsible user for inserting and updating the data are missing, you can use the Attach ... button to attach these columns to the table. Furthermore you may add a RowGUID to the table as e.g. a preparation for a replication.

In the Log table section (see below) you can create a logging table for the selected table in a format as used within the Diversity Workbench. Click on the Show SQL ... button to show the SQL-statement that will create the logging table. If an old logging table should be kept, choose the Keep old log table option. If your table should support the version setting from a main table, choose the Add the column LogVersion option. To finally create the logging table click on the Create LogTable ... button.

The triggers for insert, update and delete are created in the according sections (see below). If an old trigger exists, its definition will be shown in the upper part of the window. Click on the Show SQL button to see the definition of the trigger according to the current definition of the table in a format as used in the Diversity Workbench. If a trigger should set the version in a main table, which the current table is related to, choose the Add version setting to trigger option. To enable this option you must select the version table first. To finally create the trigger click on the Create trigger button. The update and delete triggers will transfer the original version of the data into the logging tables as defined above, where you can inspect the history of the data sets.

If so far no procedure for setting the version in a main table is defined, you can create this procedure in the last section. Click on the Show SQL button to see the definition and on the Create Procedure button to create the procedure (see below).

 

Preparation for replication

If you want to use replication within you module, the tables need certain columns and a log table. These preparations can be performed by a script, generated in the section Replication (see below). Select the tables you want to include in the process and create the script. This script can than be included in an update of the database. Please ensure that these changes are only be done by expert staff.

 

Clear logtables

If for any reason you want to clear the log tables of the database, this can be done in the Clear log tab as shown below. Click on the List tables button to list the log tables. Then select those that should be cleared and click on the Clear log of selected tables button (see below). Please keep in mind that any restoration of data from the log is only possible as long as the data can be retrieved from the log.

 

Data protection

To implement the General Data Protection Regulation of the European Union several steps have to be performed in a database:

  • Generate a skript using this tool (see below) to convert all tables and insert objects according to the requirements:
    • Add columns ID, PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Grant update to PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Create update trigger for UserProxy setting the PrivacyConsentDate
    • Create the function providing the ID of the user from UserProxy
    • Create the function providing the name of the user from UserProxy
    • Create the function PrivacyConsentInfo providing common information
    • For every table:
      • Insert users from a table into UserProxy (if missing so far)
      • Insert users from the corresponding log table into UserProxy (if missing so far)
      • Change the constraints for the logging columns (User_Name() → UserID())
      • Replace user name with ID in logging columns
      • Replace user name with ID in logging columns of the log table
      • Adapt description of the logging columns
  • Include the skript in an update of the database
  • Check the database for update triggers, functions using e.g. CURRENT_USER, USER_NAME, SUSER_SNAME etc. where user names must be replaced with their IDs. Create a script performing these tasks and include it into an update for the database
  • Adapt the client to the now changed informations (e.g. query for responsible etc.)

After these changes the only place where the name of a user is stored is the table UserProxy together with the ID. Removing the name (see below) will remove any information about the user leaving only a number linked to the information within depending data.

To generate a script for the objects and changes needed to implement the General Data Protection Regulation use the Data protection tab as shown below. The generated script will handle the standard objects (logging columns) but not any additional circumstances within the database. For these you need to inspect the database in detail and create a script to handle them on your own.

To set the website where detailed information about the handling of the General Data Protection Regulation within the DiversityWorkbench resp. the current database is provided, click on the button on the Info site tab. If unchanged, the default site for the DiversityWorkbench is set (see below).

If for any reason a user wants his name to be removed from the database, select the users name from the list as shown below and click on the  button (see below).

Mar 26, 2024

Diversity Collection

No-SQL Interface

JSON Cache

Databases of the modules provid a No-SQL interface where the data of the main table and the depending tables are merged as JSON.

Table JsonCache

Content of table JsonCache restricted to public available data

Column Data type Description Nullable Relation
ID int Unique ID for the Dataset, Primary key NO ID of the source
URI varchar (500) The URL as combination of BaseURL and ID NO BaseURL and ID of the source
DisplayText nvarchar (500) Representation in the interface NO Main table of the source
LogUpdatedWhen datetime Date and time when the data were last updated NO -
Data json Data related to the current dataset NO -

procFillJsonCache is started by an update trigger trgUpd… of the main table in the database

Interface in clients

All modules provide data via a cache table. In the header of the clients you can inspect the content of the JsonCache with a click on the button. For modules with a difference between local and public data, you can inspect the content of the public data with a click of the right mouse button.

Update

Apart of the update via the Trigger (see below) you can update the JsonCache via the update button underneath the button.

To update the JsonCache for the whole database select Administration - JsonCache… from the menu. a window as shown below will open where you can update the JsonCache for single datasets or the whole database.

Summary

graph TD;
    TaxonName[Main table in database] 
    trgUpdTaxonName[trgUpd.. of main table in database]
    TaxonName --> |Update in table| trgUpdTaxonName
    proc[Procedure procFillJsonCache setting the content in table JsonCache]
    trgUpdTaxonName --> proc
graph TD;    
    Mainform[Main form]
    ButtonShow[Button show JsonCache of current dataset]
    Mainform --> ButtonShow
    Left[Show Data]
    ButtonShow --> |Left click| Left
graph TD;    
    Mainform[Main form]
    Admin[Administration menu]
    Mainform --> Admin
    Cache[JsonCache...]
    Admin --> Cache
    Adminform[Administration form]
    Cache --> Adminform
    AdminUpdateSingle[Update single dataset]
    Adminform --> AdminUpdateSingle
    AdminUpdateDB[Update for whole database] 
    Adminform --> AdminUpdateDB

Example

The JsonCache of the current dataset will be shown as in the example below:

[
    {
        "Server": "http://zsm.diversityworkbench.de/",
        "Database": "DiversityCollection_ZSM_Training",
        "URL": "http://zsm.diversityworkbench.de/Collection_ZSM_Training/399050",
        "Type": "CollectionSpecimen",
        "ID": 399050,
        "DisplayText": "JsonCacheDemo",
        "Project": [
            {
                "Project": "HYMIScoll",
                "ProjectID": 927
            }
        ],
        "CollectionEvent": [
            {
                "LocalityDescription": "Germany, Bavaria",
                "CollectionYear": 2024,
                "CollectionMonth": 7,
                "CollectionDay": 9,
                "CollectionEventLocalisation": [
                    {
                        "DisplayText": "Altitude (mNN)",
                        "Content Location 1": "Altitude from",
                        "Location1": "679",
                        "Content Location 2": "Altitude to"
                    },
                    {
                        "DisplayText": "Named area (DiversityGazetteers)",
                        "Content Location 1": "Location",
                        "Location1": "Holzleithen, Bavaria, Germany",
                        "Content Location 2": "Thesaurus code"
                    },
                    {
                        "DisplayText": "Coord. WGS84",
                        "Content Location 1": "Longitude (East-West)",
                        "Location1": "10.959893227",
                        "Content Location 2": "Latitude (North-South)",
                        "Location2": "47.753982544",
                        "Geography": "POINT (10.959893227 47.753982544)"
                    }
                ],
                "CollectionEventProperty": [
                    {
                        "PropertyName": "Geographic regions",
                        "PropertyType": "Vegetation",
                        "Property": "Eschen-Ahorn-Schluchtwald bzw. -Hangwald (feucht-kühle Standorte)",
                        "Hierarchy": "Eschen-Ahorn-Schluchtwald bzw. -Hangwald (feucht-kühle Standorte) | Schlucht-, Blockhalden- und Hangschuttwälder | Laub(misch)wälder und -forste (Laubbaumanteil > 50 %)"
                    }
                ],
                "CollectionEventMethod": [
                    {
                        "Method": "Fallen",
                        "Marker": "1",
                        "CCollectionEventParameterValue": [
                            {
                                "PropertyType": "Alkohol",
                                "Property": "70%"
                            },
                            {
                                "PropertyType": "Pheromon",
                                "Property": "-"
                            },
                            {
                                "PropertyType": "Licht",
                                "Property": "400 nm"
                            }
                        ]
                    }
                ],
                "CollectionEventRegulation": [
                    {
                        "Regulation": "DE_PER_20210801",
                        "TransactionTitle": "DE_PER_20210801"
                    }
                ],
                "CollectionEventSeries": [
                    {
                        "SeriesID": -1,
                        "Description": "Voralpen",
                        "SeriesCode": "B2024_02",
                        "DateStart": "2024-07-01T13:29:22",
                        "DateEnd": "2024-07-27T13:29:22",
                        "CollectionEventSeriesDescriptor": [
                            {
                                "Descriptor": "Schluchtwälder",
                                "DescriptorType": "Biotoperfassung"
                            }
                        ]
                    },
                    {
                        "SeriesID": -4,
                        "Description": "Ammerschlucht",
                        "Geography": "POINT (10.9668204567046 47.7016669695774)",
                        "DateStart": "2024-07-09T13:29:22",
                        "DateEnd": "2024-07-10T13:29:22",
                        "CollectionEventSeriesDescriptor": [
                            {
                                "Descriptor": "Schluchtwälder",
                                "DescriptorType": "Biotoperfassung"
                            }
                        ]
                    }
                ],
                "ExternalIdentifier": [
                    {
                        "Type": "LSID",
                        "Identifier": "Event01"
                    }
                ]
            }
        ],
        "Annotation": [
            {
                "Annotation": "Annotation for specimen"
            }
        ],
        "CollectorsName": [
            {
                "CollectorsName": "Huber, F.",
                "CollectorsNumber": "FH-654"
            },
            {
                "CollectorsName": "Pfeiffer, R."
            },
            {
                "CollectorsName": "Schmidt, H."
            }
        ],
        "CollectionSpecimenReference": [
            {
                "ReferenceTitle": "Reference for a part",
                "SpecimenPartID_Reference": 182805
            }
        ],
        "CollectionSpecimenRelation": [
            {
                "RelatedSpecimenDisplayText": "ext. Relation of specimen to something else",
                "RelationType": "Specimen part",
                "RelatedSpecimenURI": "ext. Relation of specimen to something else"
            }
        ],
        "CollectionSpecimenPart": [
            {
                "SpecimenPartID": 182807,
                "MaterialCategory": "DNA sample",
                "CollectionHierarchy": [
                    {
                        "CollectionName": "Entomologie",
                        "CollectionAcronym": "Ento",
                        "Type": "department"
                    },
                    {
                        "CollectionName": "Insecta varia",
                        "CollectionAcronym": "InVa",
                        "CollectionOwner": "SNSB - Zoologische Staatssammlung München",
                        "Type": "department"
                    },
                    {
                        "CollectionName": "Odonata",
                        "Type": "department"
                    },
                    {
                        "CollectionName": "SNSB - Zoologische Staatssammlung München",
                        "CollectionAcronym": "ZSM",
                        "Type": "institution"
                    }
                ],
                "CollectionSpecimenPartProcessing": [
                    {
                        "DisplayText": "DNA",
                        "ProcessingDate": "2024-07-10T10:47:53.050",
                        "ResponsibleName": ""
                    }
                ],
                "CollectionSpecimenTransaction": [
                    {
                        "TransactionType": "loan",
                        "TransactionTitle": "Ausleihe nach berlin",
                        "CollectionName": "SNSB - Zoologische Staatssammlung München",
                        "ActualEndDate": "2024-07-04T00:00:00"
                    }
                ],
                "CollectionSpecimenTask": [
                    {
                        "Task": "Exhibition ⁞ Part",
                        "Type": "Part",
                        "CollectionName": "Ebene 2",
                        "DisplayText": "JsonCacheDemo: Calopteryx virgo(Linnaeus, 1758) - DNA sample"
                    }
                ]
            },
            {
                "SpecimenPartID": 182805,
                "MaterialCategory": "pinned specimen",
                "CollectionHierarchy": [
                    {
                        "CollectionName": "ZSM-InVa-D1482",
                        "CollectionAcronym": "10",
                        "Type": "drawer",
                        "CollectionImage": [
                            {
                                "URI": "https://www.zsm.mwn.de/drawers/InVa/Odonata/ZSM-InVa-D1482-2020"
                            }
                        ]
                    }
                ],
                "CollectionSpecimenTask": [
                    {
                        "Task": "Exhibition ⁞ Part",
                        "Type": "Part",
                        "CollectionName": "Ebene 2",
                        "DisplayText": "JsonCacheDemo: Calopteryx virgo(Linnaeus, 1758) - pinned specimen"
                    }
                ]
            },
            {
                "SpecimenPartID": 182806,
                "MaterialCategory": "tissue sample",
                "CollectionHierarchy": [
                    {
                        "CollectionName": "ZSM-InVa-D1482",
                        "CollectionAcronym": "10",
                        "Type": "drawer",
                        "CollectionImage": [
                            {
                                "URI": "https://www.zsm.mwn.de/drawers/InVa/Odonata/ZSM-InVa-D1482-2020"
                            }
                        ]
                    }
                ],
                "CollectionSpecimenTransaction": [
                    {
                        "TransactionType": "regulation",
                        "TransactionTitle": "DE_PER_20210801",
                        "CollectionName": "SNSB - Zoologische Staatssammlung München"
                    }
                ],
                "CollectionSpecimenTask": [
                    {
                        "Task": "Exhibition ⁞ Part",
                        "Type": "Part",
                        "CollectionName": "Ebene 2",
                        "DisplayText": "JsonCacheDemo: Calopteryx virgo(Linnaeus, 1758) - tissue sample"
                    }
                ]
            }
        ],
        "IdentificationUnit": [
            {
                "IdentificationUnitID": 437340,
                "TaxonomicGroup": "fungus",
                "Identification": [
                    {
                        "TaxonomicName": "Metarhizium anisopliae",
                        "IdentificationSequence": 0
                    }
                ]
            },
            {
                "IdentificationUnitID": 437339,
                "HierarchyCache": "Odonata - Calopterygidae - Calopteryginae",
                "OrderCache": "Odonata",
                "FamilyCache": "Calopterygidae",
                "TaxonomicGroup": "insect",
                "NumberOfUnits": 22,
                "Identification": [
                    {
                        "TaxonomicName": "Calopteryx virgo(Linnaeus, 1758)",
                        "IdentificationSequence": 1
                    }
                ],
                "IdentificationUnitAnalysis": [
                    {
                        "DisplayText": "16S",
                        "AnalysisNumber": "1",
                        "AnalysisResult": "TGC",
                        "SpecimenPartID": 182805
                    },
                    {
                        "DisplayText": "DNA Analysis",
                        "AnalysisDate": "2024-06-24",
                        "AnalysisNumber": "1",
                        "AnalysisResult": "ATTGCAGC",
                        "ResponsibleName": "Meier, R.",
                        "IdentificationUnitAnalysisMethod": [
                            {
                                "DisplayText": "Ultraschall",
                                "MethodMarker": "1"
                            }
                        ]
                    }
                ],
                "IdentificationUnitGeoAnalysis": [
                    {
                        "AnalysisDate": "2024-07-08T14:39:21.300",
                        "Geography": "POINT (11.50062829 48.16385096)"
                    },
                    {
                        "AnalysisDate": "2024-07-08T14:45:28.007",
                        "Geography": "POLYGON ((11.5003972353666 48.1634295515789, 11.5005823309247 48.1634194298878, 11.5005903785577 48.1634788947945, 11.5004012591831 48.1635041989893, 11.5003972353666 48.1634295515789))"
                    }
                ]
            }
        ]
    }
]

Cache database

Table [Project].CacheJsonCache

Content of table JsonCache restricted to public available data in the Cache database

Column Data type Description
ID int Unique ID for the Dataset, Primary key
URI varchar (500) The URL as combination of BaseURL and ID
DisplayText nvarchar (500) Representation in the interface
LogUpdatedWhen datetime Date and time when the data were last updated
Data json Public available data related to the current dataset

The data are transferred via a stored procedure [Project].procPublishJsonCache where [Project] is the schema corresponding to the Project in the database. Restricted to public information e.g. not locked via DataWithholding, Internal…, etc. and further restrictions as defined in the cache database.

Postgres database

The table CacheJsonCache is a copy of the table in the SQL-Server database with the Data stored in JSONB Format (= binary).

Aug 7, 2024

Diversity Collection

Documentation

Tools for the database documentation

These are the tools to describe the parts of the database and create documentations of the structure. To use these tools, choose Administation - Database - Documentation… from the menu. A window will open as shown below.

Click on the List objects button to list the objects of the database. With the  button resp. button you can select resp. deselect the types in the type selection and the object in the list.

Select the objects that should be listed all button resp. none button you can select resp. deselect the types in the type selection and the object in the list.

Select the objects that should be included in the documentation:

  • Tables
    • Trigger
  • Views
  • Roles
  • Functions and procedures
  • Context

… and exclude the objects that should not be included in the documentation:

  • Logging tables
  • Enumeration tables
  • Old versions of objects
  • System objects
  • Deprecated objects

 

The button Set default seletion will select all items in the list without:

  • System objects
  • Older version of an object indicated by the number at the last position
  • Logging tables
  • Enumeration tables
  • Objects with a description starting with e.g. outdated, deprecated, obsolete etc.
  • HTML options:
    • include index for objects
    • include NULL / NOT NULL
    • include relations and dependencies
    • include Description
    • exclude standard trigger
    • exclude definition
    • include permissions for *_Enum etc.
    • exclude obsolete columns
    • exclude columns starting or ending with the given strings
    • include list of tables that are depending on a table

The buttons Add to seletion and  Remove from seletion  will use the given strings with * as wildcard to add resp. remove items from the selection.

With the Context  option you can show or hide the context area for the html and media wiki tab as shown above.

HTML, MediaWiki, JSP-Wiki

To create a documentation choose among the provided options and click on the button Create ... documentation to create the documentation in one of the available formats (HTML, MediaWiki, JSP-Wiki). 

Oct 19, 2024

Subsections of Documentation

Diversity Collection

Documentation

chm

With the chm tab you can generate index and keyword html files as well as markdown files for a website generated out of the hhc and hhk files of the HTML Help Workshop for the creation of chm manual as described in the video .

The button Generate keywords for HUGO creates a text file keywords.txt containing the keywords needed for the HUGO manual in a simple format. A pre- or postfix is set for every module to avoid conflicts. Use the Open button to open the file in a text editor.

Oct 19, 2024

Diversity Collection

Documentation

Github

ssh-key

To change the authentication mechanism to SSH keys in Visual Studio Code and GitHub, you need to follow these steps:

  • Open the command line and change in your homedirectory if not already done cd %USERPROFILE%
  • Generate an SSH key pair on your local machine using the command ssh-keygen -a3 -t ed25519 -C "your_email@example.com" -f .ssh/id_github.
    • In case you omit the -f option nameing the file where the key should be stored, you will be asked th enter the name of the file where the key should be stored e.g. id_github. Make shure not to overwrite existing keys.
  • Next enter a passphrase (twice)
    • When you generate an SSH key pair, you have the option to add a passphrase to the private key. A passphrase is an extra layer of security that helps protect your private key from unauthorized access. If someone gains access to your private key, they can use it to authenticate as you and perform actions on your behalf. By adding a passphrase, you make it more difficult for someone to use your private key without your permission.
    • When you use an SSH key with a passphrase, you will be prompted to enter the passphrase every time you use the key. This can be inconvenient, but it ensures that only you can use the key to authenticate with remote servers. You can also use an SSH agent to store your passphrase so that you don’t have to enter it every time you use your key .
    • The location of your keys will be shown (e.g. id_github for the private key and id_github.pub for the public key) next to a fingerprint and a randomart image like
+--[ED25519 256]--+
|     ..   .+=.o  |
|      .+ . o+*   |
|    . +.. ooo.o  |
|     +.B.+= =.o  |
|      =+S=o* = o |
|     . oo*= o o  |
|      .  .       |
|        . . o E  |
|           o .   |
+----[SHA256]-----+
  • Add the public key to your GitHub account by navigating to your account settings, selecting “SSH and GPG keys”, and clicking “New SSH key”.
  • Copy the contents of the public key file (usually ~/.ssh/id_rsa.pub) and paste it into the “Key” field on the GitHub website.
  • In Visual Studio Code, open the Command Palette (press Ctrl+Shift+P on Windows) and search for Remote-SSH: Open Configuration File.
  • Select the configuration file you want to edit and add the following lines:
    Host github.com
    HostName github.com
    User git
    IdentityFile ~/.ssh/id_rsa
  • Save the file and close it.
  • Open the Command Palette again and search for Remote-SSH: Connect to Host.
  • Select the configuration file you just edited and wait for the connection to be established.
  • You should now be able to use Git with SSH authentication in Visual Studio Code.
Oct 19, 2024

Diversity Collection

Documentation

HUGO

In the HUGO / HTML tab you generate markdown files according to HUGO and the relearn theme.

The conversion and adaptions are explained in a short tutorial: Video starten

For enumeration tables the content can be exported as explained in a short tutorial: Video starten

In the tab you can fix links in markdown files according to HUGO shortcodes.

The fixes for broken links are explained in a short tutorial: Video starten

The adaptions for links for HUGO as related references are explained in a short tutorial: Video starten

To map the files in the original links to new files in the documentation follow the steps shown in a short tutorial: Video starten

Installation of HUGO

Update des Themes

um das Theme auf die letzte Version zu bringen kann man den Befehl git submodule update --remote --merge themes/relearn verwenden

Übersetzung des Bestands an html

  • Übersetzung der *.html Seiten mit pandoc in *.md
  • Aufbau einer Ordnerstruktur die dem Index der chm Datei entspricht
  • Das Basisdokument der Ordner wird in die Ordner verschoben und in _index.md umbenannt
    • Dort im Frontmatter steht der Titel der im Menü angezeigt wird, e.g.:
      --- 
      title: Installation 
      ---  

Überarbeitung der md Dateien

  • Korrektur der Bildverweise
    • Ordner mit den Bildern in den Ordner static kopieren
    • von e.g. ![](img/...) in ![](img/...)
    • ACHTUNG - Case sensitiv. Namen müssen stimmen
    • Icons gegebenenfalls freistellen für Darkmode
  • Entfernung aller störenden Formatierungsangaben
  • Entfernung der Kopfzeile (Überschrift wird von HUGO automatisch erzeugt)
  • Korrektur der internen Verweise
    • ändern von [![](img/VideoDE.svg?class=inlineimg)](http://media.snsb.info/Tutorials/dwb/Editing/OeffentlicheKontaktdaten.webm) zu [![Video starten](img/VideoDE.svg?class=inlineimg)](http://media.snsb.info/Tutorials/dwb/Editing/OeffentlicheKontaktdaten.webm)
      • ansonsten wird das Bild gezeigt statt das Video zu starten
    • ändern von
      [Contact](Contact.htm)
      zu e.g.
      [Contact](editingdata/contact)
    • Wenn als Basisadresse in hugo.toml etwas angegeben wurde, e.g. baseURL = "http://www.diversityworkbench.de" dann muss diese auch für Verweise innerhalb der Files verwendet werden.
      • e.g. Bildverweise ![](img/IcoFeedback.gif?class=inlineimg)
      • Dateiverweise [Anmelden](database)
      • HUGO relearn erzeugt für Überschriften Anker die man ansteuern kann, e.g. kann man ### Table **AgentResource** über die Adresse database/database/#table-agentresource erreichen. Ein Index Eintrag dafür wäre e.g. [AgentResource](database/database/#table-agentresource). ACHTUNG - Case sensitiv: ### Table **AgentResource** wird in #table-agentresource übersetzt
    • Kommentare starten mit # ohne folgendes Leerzeichen

Frontmatter

You can change the frontmatter to a default using the documentation tool

  • Steht am Anfang der Datei und ist bei yaml durch --- oben und unten abgegrenzt, e.g.
    ---
    title: Login administration
    linktitle: Logins
    weight: 5
    menuPre: img/Documentation.svg
    alwaysopen: false
    ---
  • Seiten die noch in Entwicklung sind kann man mit draft: true im Frontmatter markieren. Diese werden dann nicht in die Ausgabe übernommen
  • Der Titel wird mit title: Login administration angegeben. Dieser erscheint dann auch in der Seite als Überschrift
  • Der Text im Menü kann abweichend definiert werden mit linktitle: Logins. Ansonsten erscheit der Titel im Menü
  • Die Reihenfolge im Menü kann mit weight: 5 angegeben werden. Ansonsten wird alphabetisch sortiert
  • Ein Logo kann man mit `menuPre: img/LinkedServer.svg
  • Wenn das Untermenue erst beim Anwählen geöffnet werden soll: alwaysopen: false

Template files

Starting with a Dash: If the first line of your Markdown file starts with a dash (-), Hugo might misinterpret it as a YAML delimiter, leading to an error

Bilder

You can adapt the images to a default using the documentation tool

  • Icons die e.g. in den Text integriert werden sollen, müssen folgedermassen eingebaut werden:
    • ![](img/Database.svg?class=inlineimg)
  • Die Bilder am Anfang der Seite werde wie folgt eingebaut:
    • ![](img/LinkedServer.svg?class=headerimg)

mit px wird das Bild mitgezoomt, bei vw bleibt es gleich gross

  • noch nicht zu svg konvertierte Bilder die im Fliesstest erscheinen sollen werden wie folgt eingebunden:
    • ![](img/Delete.svg?class=inlineimg)
  • sonstige Bilder mit
    • ![](img/Delete.svg)

mit der Angabe ...lightbox=false wird verhindert, dass ein Bild beim Anklicken mit der Maus geöffnet wird. Dies sollte bei Bildern die nicht nach svg konvertiert wurden und nicht im Fliesstext erscheinen nicht verwendet werden, damit der User bei kleinen Bildern diese in Originalauflösung betrachten kann. Unten 2 Beispiele

![](img/Delete.svg?class=inlineimg)

![](img/Delete.svg?class=inlineimg)

Für Bilder die aus der Quelle fontawesome kommen kann man hier suchen: fontawesome. Es funktionieren nicht alle die dort bereitstehen. Daher bitte testen!

Für Links innerhalb des Manuals kann man shortcodes verwenden. Dafür entweder auf den Namen der Datei oder auf Links von Überschriften (ab ##) verwenden. Diese müssen innerhalb des Manuals eindeutig sein. Für Header als erstes Zeichen # dann Überschrift und alles lower case und Leerzeichen werden durch - ersetzt. Beispiel:

## Main form of diversityexsiccatae

wird zu sofern es sich in der gleichen Datei befindet: 2 x { und % relref "#main-form-of-diversityexsiccatae" % und 2 x }

Für Links ausserhalb der Datei werden Verweise unter Einschluss des Dateinamens verwendet:

Verweis auf ein Kapitel innerhalb einer Datei 2 x { und % relref "diversityexsiccatae#main-form-of-diversityexsiccatae" % und 2 x }

bzw. nur auf die Datei 2 x { und % relref "diversityexsiccatae" % und 2 x }

Leerzeichen zwischen 2 x { und % und % und 2 x } entfernen

Von ausserhalb kann e.g. eine Überschrift mit https://www.diversityworkbench.demodules/diversityexsiccatae/index.html#main-form-of-diversityexsiccatae aufgerufen werden. Diese können direkt aus dem Manual kopiert werden.

  • hierfür das Logo in den Ordner static kopieren
  • im Ordner layouts einen Ordner partials anlegen
  • dort eine Datei logo.html anlegen
    • in dieser auf das Logo verweisen e.g.:
      <h4><b>DiversityAgents</b></h4>
      <img src="/DA_4D.svg">
  • in static - layouts - partials die Datei menu-footer.html anlegen und anpassen

favicon

Im Ordner static den Ordner images anlegen Datei favicon.ico in der Ordner static/images kopieren

Einschliessen von Dateien

Das Verzeichnis templates enthält Dateien die in andere Dateien über eine shortcode eingeschlossen werden können, e.g.:  2 x { und % include file="templates/template_workbench.md" % und 2 x } Diese Dateien dürfen kein frontmatter enthalten. Shortcodes müssen überprüft werden, da diese in der Regel nicht ausgewertet werden.

ER-Diagramm

dieses kann als Mermaid eingebaut werden, e.g.

 
graph LR;
    A[Agent] --> B[AgentContact<br/>Kontaktdaten der Agents]
    A --> C[AgentReference]
    A --> D[AgentIdentifier]
    A --> E[AgentResource]
    A --> F[AgentExternalID]
    G[AgentExternalDatabase] --> F[AgentExternalID]

soll das Diagramm zoombar sein wird die Version 5.23 des Themes benoetigt. Ausserdem kann der Parameter nur für die Shortcode Version angegeben werden, nicht für die Codefences:

2 x { und % mermaid align="center" zoom="true" % und 2 x }
... 
(remove space between 2 x { und  and < resp > and  und 2 x } in header and footer for correct code)
...
2 x { und % /mermaid % und 2 x }

Anpassung des Themes

  • es werden 2 eigene Themes bereitgestellt

    • im Verzeichnes
      • themes
        • relearn
          • static
            • css:
            • theme-dwb-dark.css
            • theme-dwb.css

    diese an DWB Anforderungen anpassen

    • in \themes\relearn\static\css\theme.css
      #body img.inline {
          display: inline !important;
          margin: 0 !important;
          vertical-align: middle;
          /* vertical-align: bottom; */
      }
    • in \themes\relearn\static\css\theme-dwb.css
      /*--MENU-HEADER-BG-color: rgba( 28, 144, 243, 1 );*/ /* Background color of menu header */
      --MENU-HEADER-BG-color: rgba( 220, 220, 220, 1 ); /* Background color of menu header */
      --MENU-HEADER-BORDER-color: rgba( 51, 161, 255, 1 ); /*Color of menu header border */
      

      –MENU-SEARCH-color: rgba( 255, 255, 255, 1 ); /* Color of search field text / /–MENU-SEARCH-BG-color: rgba( 22, 122, 208, 1 );/ / Search field background color (by default borders + icons) / –MENU-SEARCH-BG-color: rgba( 90, 90, 90, 1 ); / Search field background color (by default borders + icons) / /–MENU-SEARCH-BORDER-color: rgba( 51, 161, 255, 1 );/ / Override search field border color / –MENU-SEARCH-BORDER-color: rgba( 0, 0, 0, 1 ); / Override search field border color */

Konfiguration - in hugo.toml:

```native
baseURL = "http://www.diversityworkbench.de"
languageCode = "en-us"
title = "DiversityAgents"
theme = "relearn"

[outputs] home = ["HTML", "RSS", "SEARCH", "SEARCHPAGE"] section = ["HTML", "RSS", "PRINT"] page = ["HTML", "RSS", "PRINT"]

[params] themeVariant = [ "auto", "dwb", "dwb-dark" ]

</code></pre>
<h2 id="start-des-testservers">Start des Testservers:</h2>
<ul>
<li>mit einem Terminal in das Verzeichnis des Projekts wechseln</li>
<li>dort <code>hugo server </code> eingeben.</li>
<li>bei Problem mit Sonderzeichen: den Inhalt der Datei config.toml in hugo.toml kopieren und config.toml löschen (beide sollten wenn vorhanden UTF8 sein - werden manchmal als UTF16 angelegt - dieses dann nach UTF8 ändern)
<ul>
<li>Error: &ldquo;&hellip;\diversityworkbench\hugo.toml:1:1&rdquo;: unmarshal failed: toml: invalid character at start of key: ÿ</li>
</ul>
</li>
<li>Im Browser an die angegebene Adresse navigieren, e.g. <code>localhost:1313</code></li>
<li>Wenn als Basisadresse in hugo.toml etwas angegeben wurde, e.g. <code>baseURL = &quot;http://www.diversityworkbench.de&quot;</code> dann muss die passende Adresse eingeben werden also e.g. <code>localhost:1313</code></li>
</ul>
Oct 19, 2024

Diversity Collection

Documentation

MediaWiki

With the MediaWiki tab you can generate markdown files according to MediaWiki.

Oct 19, 2024

Diversity Collection

Database description

These are the tools to describe the parts of the database and create documentations of the structure. To use these tools, choose Administration -> Database -> Description ... from the menu. A window will open as shown below.

Description

The structure of the database is documented as Entities of the structure [Table].[Column].[Content] e.g. Analysis for the table Analysis or CollTransactionType_Enum.Code.loan for the entry loan in the table CollTransactionType_Enum. The descriptions are defined for contexts if e.g. a certain group of users need differing descriptions or translations of the database structures. In the Usage section you can define the Accessibility of tables and columns if e.g. for a mobile application like DiversityMobile certain parts of the database e.g. should not be used. With the Determination you can define if the contents are set by e.g. a program or by the user. With the Visibility you can define if certain parts should be visible of hidden. If for a certain context a preset value should be used, this value can be set here. In the Representation section you can enter a Display text, an Abbreviation and a Description for all contexts in any language. 

Entity

To insert missing tables choose Entity - Insert all missing tables from the menu. A window as shown below will open where you can select among the missing tables which of these should be added. Missing columns can be added with the menu Entity - Insert missing columns for ... either all tables or a selected table. If you want to insert descriptions for the content of a table, choose Insert PK for selected table. This is option is provided to enable the translation of enumerations contained in the database.

Representation

To insert entries for a language that is missing, choose Representation - Insert all language ... from the menu. In the window that will open, choose the language and click OK. Any missing language entry will be inserted to prepare the entry of the translations by a user. The database contains default descriptions of all tables and columns. These can either be used as a base for the description. Select a table and choose Representation - Update descriptions ... from the menu. To change the descriptions in the database according to the entries you made choose Representation - Update database ... from the menu.

 

Usage

With the Usage menu you can add a Usage for a table or for the columns of a table.

 

Context

To edit the context choose Administration - Context from the menu. A window as shown below will open with all contexts available in the database.

To enter a new context, just enter the values in the last line. As ParentCode enter General or one of the existing codes. The values of this parent context will be used if values for the new context are missing. As next step insert the parameters for the new context into the table for the representation. To do so select the table EntityContext_Enum and choose Insert PK for selected table (see below). This will add the value for the new context so far missing in the table Entity and EntityRepresentation.

In the upcoming dialog set the mapping as shown below.

Now the new context is available for selection in the main menu.

 

Mar 20, 2025

Diversity Collection

Version of data sets

The Version of a data set consists of two parts, e.g. 3 / 1 as shown in the header of the specimen in the main form. The first number refers to the version of the data set as stored in table CollectionSpecimen. The second number refers to the version as stored in table CollectionEvent. Both versions will be set to a higher number if the data in the tables themselves or in dependent tables are changed. Thus, if a new identification is inserted in the table Identification the specimen number of the version will increase from 3 to 4 resulting in a version 4 / 1 for the whole data set. The changes in the version will only occur if the last changes in the data were more than 24 hours ago or a different user is changing the data. This ensures that a user can change several parts in a data set within 24 hours and the version will only be increased by 1.

The data is stored in the tables CollectionSpecimen and CollectionEvent.

Mar 19, 2025

Version

For information about the version of the client application choose Help, Info…

The current version in the example above is 4.0.0 for the client and 2.1.13 for the database

 

 

Mar 26, 2024

Data Access

Access to the data

To get access to the data, you have to fulfill several requirements. In DiversityCollection, you must be a member of one of the usergroups. You can only access data, which is listed in the projects you have access to. For external users data may be blocked by entries in the data withholdingreasons or due to a data embargo.

   

Jan 14, 2025

Subsections of Data Access

Availability of data sets

The data of certain parts of the database can be blocked for remote access. If you want to prevent access for the whole dataset, enter your reason in the field Withholding reason in the header (see below).

If you want to block only the access to the data of the collection event or the collector, choose them in the tree and enter your reason for withholding the data in the corresponding fields. The data will only be published, if these fields are empty.

Within the database a user has only access to the data of those projects for which he has permission. If a data set belongs to a certain project, it is stored in the table CollectionProject.

To prevent the publication of the data these can be blocked for the whole data set (table CollectionSpecimen), for the locality as a whole and for the collection date (table CollectionEvent), for the collectors (table CollectionAgent) (for the collectors an anonymisation is available), the organisms (table IdentificationUnit) and the parts (table CollectionSpecimenPart) - see overview below - and for all image tables: CollectionSpecimenImage, CollectionEventImage, CollectionEventSeriesImage and CollectionImage. The transaction provide the possiblity of an embargo (see below).

To edit the withholding reasons for all specimen selected in the main window choose Administration  - Withhold data... from the menu. As an alternative choose Data - Cache database... from the menu. There in the projects part click on the button to edit the withholding reasons for a single project. A window will open as shown below, giving a summary of all withholding reasons set for the selected specimen and related data. Video starten

To edit the withholding reasons for certain entries choose the corresponding page where the details are listed as shown below.

To block all data enter a new reason for withholding the data and click on the Add withholding reason to all ...  button or the ... only to selected button, if only the selected entries should be blocked. To remove the withholding reason from all data sets click on the Remove withholding reasons for all ... button or the ... only from selected button, if only the selected entry should be published.

Data embargo

To mark data to be not published for a certain period you can define a data embargo and include the data in this data embargo.

Permissions for projects

The user's access to the data within the database is stored in the tables shown below. The tables UserProxy and ProjectProxy are related to the Diversity Workbench modules DiversityUsers and DiversityProjects respectively. See User administration for further details.

Mar 20, 2025

Diversity Collection

Projects

Every CollectionSpecimen may be assigned to any number of projects. To assign a specimen to a project click on the button. To add a project where you have no access to, use the button. To remove a specimen from a project select the project from the list and click on the button.

 

If there are projects, to which you have no access to, these will be listed in a separate list at the top as shown below.

 

Projects, to which you have Read only access will be listed in a separate list at the top as shown below.

Data from Read only projects can be seen but not edited. Only Annotations can be added (see image below).

To transfer all selected specimen into an additional project choose Data → Transfer → To project... from the menu. A window will open where you can select the project to which the specimen should be added.

To remove all selected specimen from an additional project choose Data → Remove from project... from the menu. A window will open where you can select the project from which the specimen should be removed. The last project in which a specimen is placed can not be removed.

The data are stored in the table CollectionProject.

Details of the projects within the DiversityWorkbench are stored in the database DiversityProjects. To access further information on a project click on the button. To edit details in projects you require the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you may use the synchronize function in the useradministration window as shown below. If DiversityProjects is not available, you may create a new project by clicking the button. If DiversityProjects is available, use the synchronize function .

To import new projects from the DiversityProjects, select Administration - Projects from the menu. A window as below will open where the available projects are restricted to the type "Collection" . (Short introduction: Video starten)

 

To select a project of a different type or missing type, deselect the restriction (see below).

The present project list details about the projects available in DiversityCollection.

the diagram below shows all tables with direct relations to the project tables. For more details see the sections Analysis, Processing and Image description.

 

Mar 24, 2025

Security

Security

A user may be in several groups with diverse rights in the database. Here certain higher groups have all rights of lower groups in addition to special rights for the higher group, e.g. the group User may only read data of certain tables while Typist has the rights of User and additionally may edit the data in certain tables - see overview below.

Summarized overview of some of the groups and their permissions

Role Permissions in addition to lower role and user group respectively Included rights
Administrator Delete data, edit user permissions DataManager
CollectionManager Administration of collections, handling loans etc. StorageManager
DataManager Delete data, edit image descripton templates Editor
Editor Create new entries and delete details (not entire data sets) Typist
Requester Has the right to place requests for specimen  
StorageManager Administration of stored parts, handling loans etc. User
Typist Edit data User
User See the data of the data tables, add annotations

To place a user in one of the groups, select Administration - Database - Logins... from the menu. In the window that will open select a login and a database. The roles available in the selected database will be listed as shown below. Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

 

If you are an Administrator you may add a user to one of these groups.

Any user may have access to several projects.

May 3, 2024

Project access for user

The accessibility of projects for users can have 4 different states:

  • No access
    • The current user has no access to the project
  • Accessible
    • The current user has access to the project
  • Read only
    • The current user has read only access to the project
  • Locked
    • The project is locked. Any user can either none or read only access to the project

To allow the current user access projects use the  >  button for the selected project resp. the  >>  button for all projects. To revoke access for the current user use the  <   button for the selected project resp. the  <<  button for all projects. To change the access for a project to read only use the button and the button to remove a project from the read only list.

 

 

Locking of a project

To lock a selected project use the button. For all users the project will be removed from the accessible or read only list and transferred to the locked list. This is only allowed for a database owner (dbo). Please make sure that you really want to lock a project. Any dataset related to this project will be set to read only for all users. For an introduction, please see the a short tutorial Video starten.

To remove the locked state of a project, select the project in the No access list and click on the  button. The selected project will be moved from the locked list into the read only list for those users that had access to the project.

 

Retrieval of projects from DiversityProjects

Details of the projects within the DiversityWorkbench are stored in the database DiversityProjects. To access further information on a project click on the  button. To edit details in projects you require the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you may use the synchronize function in the user administration window as shown below. If DiversityProjects is not available, you may create a new project by clicking the button. If DiversityProjects is available, use the synchronize function .

   

The diagram below shows all tables with direct relations to the project tables. For more details see the sections Analysis, Processing and Image description.

 

Jan 14, 2025

License

This manual is copyrighted work licensed under a Creative Commons License.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

 

For information about the license of the client software choose Help, Info…

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License (GPL) for more details.

Mar 26, 2024

Update

Update of database and client

If either the database or the client needs to be updated, the menu will show an additional entry: Update.

Database update

To update the database, choose Update Update database … from the menu. See chapter Database update for details.

Client update

To update the client, choose Update Update client … and download the lastest version of the client. ee chapter Update client for details.

Mar 26, 2024

Subsections of Update

Update Client

Replace the files and folders of your installation of DiversityCollection with the files you received by e-mail or downloaded from the DiversityWorkbench portal. The database will not be influenced by this replacement. After starting the new software you need to transfer the settings of the previous version. When you start the program and connect to a database, the program will check if it is compatible with the database or if the database needs an update. In any of these cases an update entry in the menu will appear. If a new version of the client is available, this menu will contain an update client … entry. Click on it to open the webpage where you may download the client as shown below.

 

Mar 26, 2024

Update Database

Update database to current version

If you are the owner of the database (Database role = dbo) and the database needs to be updated, the menu will contain an update database … entry. Select this entry to open a window as shown below to run the provided update scripts, delivered with the client software. These scripts need to run consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either have to run the script DiversityCollectionUpdate_020501_To_020504 or the scripts DiversityCollectionUpdate_020501_To_020502, DiversityCollectionUpdate_020502_To_020503 and DiversityCollectionUpdate_020503_To_020504. The program will guide you through these steps and check for the scripts. All you need to do is click the Start update button. 

Update of all databases on a server

If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:

DiversityCollection.exe UpdateDatabase 127.0.0.1 5432

The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.

Mar 26, 2024

Diversity Collection

Errorlog

If any error messages show up while working with the application, you can find further details concerning the part of the application where the error occurred and the parameters involved in the file e.g. DiversityCollectionError.log in the Module DiversityCollection located in your resources directory.

To open the errorlog, choose Help - ErrorLog from the menu. A window will open showing the content of the errolog. By default the errorlog will be reset at program start. You can keep the errorlog if needed by chossing Help - Errorlog - Keep error log from the menu. A button will appear that allows you to clear the error log manually: Help - Clear ErrorLog.

Mar 20, 2025

Modules

Modules

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain.

In the figure shown below the connections to other modules within DiversityCollection are indicated.

May 3, 2024

Subsections of Modules

Diversity Collection

Module connections

Connections between the modules of the Diversity Workbench

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. DiversityAgents is referred by several modules. To scan for references from these modules on data in DiversityAgents choose Data - Scan modules - from the menu (see image below).

With these options the program will scan all sources of the selected module as listed in the connections for references to the current agent. After selecting an agent in the tree, the sources of the selected modules together with the linked data will be listed as shown below.

Select a link to see a summary of the linked data (see below).

To get further information about an item click on the button. If so far the path to the respective application has not been set, you will get a corresponding message (see below).

Click on the button to set the path to the application (see below).

By default the path to the application is C:\Program Files (x86)\DiversityWorkbench\Diversity...\Diversity.…exe as shown.

Jan 23, 2025

Diversity Collection

Editing

Module Related Entry

The DiversityWorkbench is a set of components for building and managing biodiversity information. Each of which focuses on a particular domain and provides services for the other modules. For an introduction see a short tutorial Video starten.

To use the service of an external module you need access to the database of this module and optionally the module application placed in your application directory. Entries related to an external module have a standard interface in the main form.

Linking to a datasource or module

There are 4 options to link the content to a datasource (or module).

  • Local database
  • Remote database
  • Cache database
  • Webservice

There are two differnt approaches for providing content for the textbox. Either as a autocomplete list (, , ) or by searching values on base of the entered text in combination with a combobox ().

For the autocomplete lists just start to type and the corresponding entries will be listed where you can choose the entry you are looking for. To set the link including additional information provided by the original source (, ), you just have to leave the textbox. The program will then contact the database to which the entry corresponds and insert the additional information including the link to the source database.

The next paragaphs show how to uses this linking. The colours of the pins are automatically set when a datasource is set. The colour indicates if the current set datasource ist set to the local, remote or cache databse or to a webservice. To select one of the datasources, click on the  button and choose among the sources.

Local database

The values shown in the autocomplete list are taken from the entries in the local database.

This is the default. To refresh the content or slect the local databse as source, click on the pin button, choose the first empty entry of the list and click OK.

Remote database

To set the datasource on a remote database, choose a database from the list.

Either a database available via a linked server (e.g. [TNT.DIVERSITYWORKBENCH.DE,5432].DiversityTaxonNames_TaxaVaria see below) or a database on your local server, starting with e.g. DiversityTaxonNames for taxa in the identification

Next you will be asked to choose a project within the selected source. In case there are additional options you may be asked e.g. for taxa to restrict the content to a checklist provided by the datasource. The pin button and the textbox will change their color to orange to indicate the current source type. The autocomplete list is then generated based on the content in the remote database. When you leave the textbox the software will automatically add additional information from the selected source and set the link as shown below.

 

Cache database

To provide data via the cache database these data must be first imported as source as described in the link to cacheDB chapter.

This option provides faster access to remote data e.g. on linked servers . To choose a source from the cache database, click on the pin button and select the entry CacheDB from the list (see below) and click OK.

Next you will be asked to choose among the sources provided by the cache database. Choose your preferred source and click OK. The button and the textbox will change their color to to indicate the current source type. Now the values for the autocomplete list will be based on this datasource. Just start to type and the corresponding entries will be listed where you can choose the entry you are looking for. To set the link including additional information provided by the original source, you have to leave the textbox. The program will contact the database to which the entries in the cache database correspond and insert the additional information.

Webservice 

To set the datasource on a webservice, choose a webservice from the list as shown below. The pin button and the textbox will change their color to blue to indicate the current source type.

To get data from the webservice, you have to enter a search text in the textbox and click on the combobox button to search the webservice for matching entries. Choose among the provided results to fill the textfield and the set the link to the webservice.   

States and functions of the interface

There are several states and functions of this interface:

  • 1: the value is only set in the local database with no connection to the remote module. In this state you may either type the value or select it from the values which are already available in the database (see above).

  • 2: the value is related to the remote module.

If you wish to set a relation to the remote module you have 2 options:

Option 1

Click on the pin button to select a source as described above.

An overview for all settings can be found under Administration - Customize display - Settings.

Charts

After the source is set to a database of the DiversityWorkbench certain datasources provide also charts for the selection of taxa or terms. Click on the chart button to open a table where you can select one of the provided taxa resp. terms. Video starten

 

Option 2 Detailed linking with query option

Click on the amonite button. A window will open where you may select an entry from the foreign database. If the option for loading the connections is not set the connection to a database may not be established indicated by a button. Either requery all connections as described in chapter Connections or click on the button to open the database connections for the linked module. With this option you have the full range of query options as shown in the image below as well as access to additional webservices.

For DiversityScientificTerms you can use a hierarchy for the selection of the lists as shown below.

 

If the value has a relation to the remote module, the interface will appear as shown below with the content of textbox set to read only and a yellow background.

To release the connection to the remote module click on the button. If you require further information on the value, click on the button. This will open a form showing an overview of the related value.

If the client application of the module is available, you may inspect the details of the entry. To start the client application of the remote module click on the button. 

If the provided link does not correspond to a dataset in the source, you will get a message as shown below. Click Yes to remove the wrong link and replace it with a valid link. Video starten

 

Relation to a webservice

Some modules provide the possibility to link your data to an external webservice. For example, DiversityTaxonNames gives you access to the taxonomic names of IndexFungorum. To establish a connection to an external webservice click on the button. As with the link to modules within the DiversityWorkbench, a window will open where you are able to choose from either DiversityWorkbench modules or external Webservices. See chapter Webservice for further details

Dec 12, 2024

Webservices

Webservice - foreign sources

Some modules within the DiversityWorkbench provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of Index Fungorum. To establish a connection to an external webservice click on the button. A window will open where you may choose from either DiversityWorkbench modules or external Webservices. For an overview see a short tutorial . The currently provided webservices are:

Mar 26, 2024

Subsections of Webservices

Catalogue of Life

DiversityWorkbench provides the possibility to link your data to an external webservice. The webservice provided by the Catalogue of Life is possible through the module DiversityTaxonNames. To establish a connection to this external webservice click on the button. A window will open where you may choose this webservice (see below).

In the field Name in Query conditions enter your search string and click on the button to start the query. In the list of the left upper part the results of the query will be listed. In the right part of the window additional information is shown as provided by the webservice. To include the link from the webservice into your database choose one of the entries in the list and click OK. The entry will change as shown below.

If you double-click on the link area, a window will open providing you with the retrieval information of the webservice (e.g.:https://api.checklistbank.org/dataset/3LR/nameusage/8K9Y). 

To receive the information related to an entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed in the upper part. If available, additional information provided on a corresponding website will be shown in the lower part.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

 

 

 

 

 

May 3, 2024

Index Fungorum

Some modules within the DiversityWorkbench provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of Index Fungorum. To establish a connection to this webservice, click on the button. A window will open where you may choose Index Fungorum from the database list (see below). 

Enter the query restriction for the name in the Name field in Query conditions. The maximum number of records you receive may be set in the max. results field (choose a low number, if you have a slow connection to the internet). Click on the search button to start the query. In the list in the left upper part the results of the query will be listed. In the right part of the window additional information is shown as provided by the webservice. For certain entries buttons will appear, as e.g. shown above for the basionym and the current name of a scientific name. Click on these buttons, if you wish to change to one of these related data sets from the webservice. If available, the information provided on the corresponding website is shown in the lower part. To include the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the entire information related to this entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed. If available, the lower part will show the corresponding information of a website.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

Mar 26, 2024

Palaeontology Database

DiversityWorkbench provides the possibility to link your data to an external webservice. The webservice provided by the Palaeontology Database is possible through the module DiversityTaxonNames. To establish a connection to this external webservice click on the button. A window will open where you may choose this webservice (see below).

In the field Name in Query conditions enter you search string and click on the button to start the query. In the list of the left upper part the results of the query will be listed. In the right part of the window additional information is shown as provided by the webservice. The lower part of the window will show the webpage of the related information.

For synonyms the accepted name will be shown as well as shown above. To change to the accepted name click on the linked entry of the ID - in the example above ID: 57254. To include the link from the webservice into your database choose one of the entries in the list and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the information related to an entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed in the upper part. If available, additional information provided on a corresponding website will be shown in the lower part.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

 

 

 

 

 

May 3, 2024

Pan-European Species directories Infrastructure (PESI)

Some modules within the DiversityWorkbench provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of the Pan-European Species directories Infrastructure (PESI). To establish a connection to this webservice, click on the button. A window will open where you can choose PESI from the database list (see below). 

Enter the query restriction for the name in the Name field in Query conditions. Click on the search button to start the query. In the list in the left upper part the results of the query will be listed. On the right part of the window additional information is shown as provided by the webservice. If available, the information provided on the corresponding website is shown in the lower part. To include the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the entire information related to this entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed. If available, the lower part will show the corresponding information of a website.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

May 3, 2024

Recent Literature on Lichens

The module DiversityReferenes gives you access to the webservice Recent Literature on Lichens. To access this service click on the button. A window will open where you can search for entries in the database (see below). 

Enter the query restriction for the Authors, the Year and the Title in the query conditions. Click on the search button to start the query. In the list in the left upper part the results of the query will be listed. On the right part of the window additional information is shown as provided by the webservice. To include the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the entire information related to this entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

May 3, 2024

Diversity Collection

links from DiversityDescriptions

In the module DiversityDescriptions you can link data to DiversityCollection. To detect these links and list them in DiversityCollection, select the specimen in the tree and activate the checkbox Scan module DiversityDescriptions at the bottom of the details section. If there are links found in the available DiversityDescriptions databases, these will be listed as shown below. Select one of the items in the list to show some basic data stored in DiversityDescriptions (see below). 

To show the details in the module DiversityDescriptions set the path to the application (click on the button) and click on the button. The module DiversityDescriptions will start, showing the dataset with the link to DiversityCollection (see below).

Mar 20, 2025

Diversity Collection

Resources

The resources directory is set via the menu (Administration - Resources).

There are 3 possibilities for the resources directory:

  • Select any directory you have read/write access (User defined)
  • Select the "Home" directory of the user
  • Select the "My Documents" directory of the user

The default is set to Home. This directory will contain all files the user needs access to (see image below as an example for the module DiversityAgents).

Certain directories are hidden (Query) and are handled by the software i.e. the content should not be changed by the user. The other folders are generated by the software if missing, e.g. Export for any exports (see below).

Optional copy

By default all files the software needs from the application directory will be copied into the selected resources directory of the user. You can change this behaviour to one of the options listed below:

  • Copy files at program start
  • Add missing files at program start
  • Do not copy

With the next start of the program the software will act according to the selected behaviour. If you change from the Do not copy option to one of the other options the software will act at once according to the new option and e.g. copy missing directories and files into the user directory.

Aug 9, 2024

Diversity Collection

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024

Diversity Descriptions

DiversityDescriptions (version 4) is part of the database framework Diversity Workbench. Each DWB module is devoted to a specific data domain. The domain of DiversityDescriptions covers the knowledge about descriptions of organisms and descriptions of any other item/ element/ entity which are object of diversity research. It can be used to describe individual organisms, research items/ objects (e.g. specimens, observation and measurement events, plots) as well as taxa, syntaxonomic entities (e.g. species, plant-sociological entities, ecosystems).  

  • The descriptions are characterized by a triple structure, namely ‘item-descriptor-state’ or ‘item-descriptor-value’ or ‘item-character-character state’ or ’entity-attribute-value’ or ’element-property-value’.
  • The states or values, which build the item/description, can be generalized to one of the presently supported data types (categorical states, quantitative values and statistical measures, molecular sequence data and free-form text as a fall-back option).
  • The descriptors (= characters, attributes, properties) are not limited to morphological characters and functional traits, but could address physiological, ecological, behavioral and even interview parameter, some molecular descriptors and descriptors of data content schemes.

    

The image below gives a rough overview how the triple structure is represented in the data tables of DiversityDescriptions. A detailled database diagram including all tables and their data columns can be found here. At the right side you can see the descriptors and categorical states that build the “descriptive terminology”. Currently four descriptor types are supported:

  1. Categorical descriptor
    may be used for representing discrete enumerable categorical states, e.g. color: red - green - blue  
  2. Quantitative descriptor
    may be used for storing numeric values, e.g. minimum, maximum, mean  
  3. Text descriptor
    free-form text, applicable if no other descriptor type is suitable  
  4. Molecular sequence descriptor
    may be used for storing nucleotide or protein sequences  

While the first three descriptor types are most commonly known in the context of descriptive data, the molecular sequence descriptor is designed according the SDD standard of TDWG. (An alternate entry point to SDD can be found here.) In most cases molecular sequence data may be mapped to text descriptor data, e.g. for export to a DELTA file. 

    

At the left side of the image above there are the “descriptive data”, which consist of the single description or item and the associated summary data. In analogy to the four descriptor types there are categorical and quantitative summary data, text descriptor data and molecular sequence data that reference the corresponding descriptor and store the actual values for the item ( green lines).  For an item description scopes can be specified, e.g. taxon names or specimens, which may optionally be linked to the corresponding module of the Diversity Workbench (orange lines at the very left). Additionally for each descriptor a data status may be specified, e.g. to indicate that a certain descriptor/character should be specified but actually no data are available (Descriptor Status Data).  

To make this very abstact overview a little bit more tangible, find in the image below a tiny example taken from the tutorial. The “Example plant” is a “Tree” and has the “Leaf color” “green” (Categorical Summary Data). Its “Leaf length” is between 5 and 10 cm (Quantitative Summary Data) and for “Literature” (currently) no data are available. Additionaly the taxon name “Ulmus campetris” has been associated to the “Example plant” (Description Scope). 

    

DiversityDescriptions keeps only descriptive data. Data of other realms like e.g. taxonomy are handled in separate modules. For an overview of the available modules see Diversity Workbench. DiversityDescriptions might also be used as a stand-alone application.

Besides the descriptive data that represent the summarized data e.g. for a certain species, Diversity Descriptions provides the feature of appending Sample Data to each description.  

To each description or item several “sampling events” may be appended, which build the anchor for the “sampling units”. The sampling event holds additional data like the date and time or a time span when the data were collected, the geographic location and coordinates. The sampling unit represents a tuple of values that belong to an individual probe, e.g. an evaluated organism (see image above). The sample data may be exported together with the descriptive data to the SDD format, which provides full sample data support. Optionally sample data may be exported to the DELTA format, where each sampling unit is mapped to a separate item. 

DiversityDescriptions 4 is based on Microsoft SQL-Server (version 2012 or newer recommended) and the .Net Framework, Version 4.8.

For licence and copyright see the licence section.

Even if you are already familiar with other Diversity Workbench modules, it is strongly recommended to take a look into the Tutorial to get an overview of the main features of DiversityDescriptions.

 

Jan 14, 2025

Subsections of Descriptions

Diversity Descriptions

Download

Current version

4.7.4 (2024-04-18)

Download

Previous versions

4.7.3 (2023-12-14)

Download

4.7.2 (2023-09-05)

Download  

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Mar 26, 2024

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.
Mar 26, 2024

Database Access

Database - access

The database engine for DiversityDescriptions is Microsoft SQL-Server 2012 or higher.

If you are connected to a database this is indicated by the icon of the connection button in left upper corner. If you are not connected this will be indicated by the icon . To access any database, you must specify the server where the database is located. For the configuration of this connection choose Connection → Database… from the menu or click on the button.

If you want to use a database on a local or remote SQL-server, start the program DiversityDescriptions.exe and in the main window click on the button or choose Connection → Database … from the menu. A window as shown below will open. Here set the connection parameters as described below.

 

Database name, IP-address and Port

A dialog will open, to specify the name or IP-address and port number of the server and to select the authentication mode. The SQL-Server may be addressed by its IP-address, e.g. 127.0.0.1 or by its name, e.g. localhost. You can either choose Windows authentication (see left image below) or SQL-Server authentication (see below - central middle image).

The standard port number for SQL-Server is 1433 and will be set as a default. If the database server is configured using a port different from that port, you must give the port number in the field Port. Click on the button to connect to the server. If the connection informations are valid, you can choose a database from the server from the combobox at the base of the window (see right image above). To restart the connecting process click on the button. In menu you find a list of the latest login data (server and port) used.

If you access a database for the first time you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data ProtectionRegulation. Without your consent the access is not possible.

 

Password

If you are logged in with a SQL-Server account and are not restricted to the group DataUser or DataReader, you can change your password. Choose Administration → Change password... from the menu. In the window that will open, enter your current password and the new password (see below). The password must match the restrictions set by the database server.

 

Module connections

The program will automatically try to get connect to Diversity Workbench databases and webservices. For further details see the Connections section.

Jan 14, 2025

Subsections of Database Access

Data Availability

Availability of the data

In the description data descriptors may be marked with the data status Data withheld (see below). 

   

When you export data the export forms include the “Withheld data” options where you can decide how to handle those data (see below).  

 

  • The default setting Suppress whole description will exclude the whole description dataset from the export.  
  • The setting Hide withheld descriptor will include the description dataset in the export, but descriptor data that are marked as “Data withheld” will be suppressed.  
  • The setting Export withheld data will include all data in the export.  

The options mentioned above are also available for the cachedatabase. Additionally there are powerful filters to restrict the exported description items and dedicated descriptor and scope data may be excluded from export.  

Finally the document generation by default excludes all descriptions that have any descriptor with data status “Data withheld”. This is indicated by the button in the upper right corner of the form. By clicking this button the descriptions may be included, which is indicated with the inactive icon . Withheld descriptors will be skipped. For the document generators there is no option to include them.  

Jan 14, 2025

Login Administration

Login administration

To administrate the logins on the database server, their permissions resp. roles and access to projects choose Administration -> Database … → Logins … from the menu. A window as shown below will open.

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the timespan (From - To) and the number of data sets where any activity of the current login has been found.

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

 

Create a login

To create a new login, click on the button in the lower left corner. Another window will open.

Here you can enter the name of the new login and the password. To assign the user information click on the button to search for a name in the DiversityAgents database.

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit login data

To edit the access for a login on the server, select the login in the list. If a login should be disabled , uncheck the enabled checkbox.

All databases on the server will be listed, with the current database showing a yellow background. The databases where the login has no access will be listed in gray while the databases accessible for a login are black.

 

Access of a login to a database

To allow a login the access to a database, select the database from the list and choose the database as shown below.

 

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below). By clicking the button you get an overview of the access rights for the selected role.

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below). Next to the projects with full access a second list provides projects with Read Only access (see image below). Use the and buttons to move projects between Accessible and Read Only.  Projects are related to the module DiversityProjects. To get additional informations about a project, select it in the list and click on the button. 

If a project is not used within DiversityDescriptions (see cachedprojects) you may delete it by shifting it to No Access and clicking button Remove project . To load additional projects, click on the Load projects button. A window as shown below will open. Projects already in the database will be listed in green,
missing projects in red (see below). Check all projects you need in your database and click the Start download button.

 

Overview for a login

If you want to se see an overview of all permissions and project for a login, click on the button. A window as shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user and roles in the database. 

To remove a user, select it in the list and click on the button. 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates, that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

Jan 14, 2025

Projects

Projects

Within DeversityDescriptions you have to distinguish the local projects and linked projects, which are connected to an entry in DiversityProjects. Administration of both projects is done in editprojects mode. For linked projects data of DiversityProjects are inserted during data publishing, e.g. by the cache database.

To link an entry, first the project data must be downloaded from DiversityProjects. For logins with Administrator rights there are two ways available, the menu item Administration-> Projects … and the Login administration.

In the login administration you may only download projects that are not yet present in DiversityDescriptions. With the menu item Administration-> Projects … you can additionally update loaded projects, e. g. if their name has been changed in DiversityProjects. In both cases a window as shown below will open. 

Projects already in the database will be listed in green, missing projects in red. Check all projects you need in your database and click the Start download button. After downloading a new project it is not yet accessible within DiversityDescriptions. Therefore use the Login administration to grant access rights to the users.

Within the Get Projects window you may get an overwiew of the present project by opening the Present projects tab and clicking the button (see image below). You can distinguish local project from linked projects by their negative “ID” and a missing “ProjectURI”. 

 

 

Checking projects data 

With DiversityDescriptions version 3.5.0 a new project handling has been introduced. Now for each project there is an entry in table Project and ProjectProxy with identical name. Therefore each project appears in the Login administration and individual access rights may be administrated. During the database update of earlier versions to database version 03.03.00 the existing project entries are processed the following way:

  1. Projects that are uniquely assigned to a DiversityProjects entry and have the same name in DiversityDescriptions stay unchanged.
  2. Projects that are uniquely assignment to a DiversityProjects entry but have a different name, are renamed in DiversityDescriptions. The original project name is entered in field Wording of the project table.
  3. All other projects become local projects, i.e. they are not linked to an DiversityProjects entry. Usually they keep their name, unless it would collide with projects mentioned in the previous items. In case of a collision a numeric value is appended to the original name and the original name is inserted in the Wording field of the project table. 

With menu item Administration-> Database …-> Check projects … you may check the consistency of the Project and ProjectProxy table. It shows you required database commands according the rules mentioned above. If you are a system administrator, you will be asked if the suggested actions shall be performed.

   

Projects and descriptions 

Each description is uniquely assigned to a project that determines its “terminology”, i.e. the descriptors and categorical states (see picture below from Edit description). Usually only projects that are assigned to the user are displayed in the project tree. The example beloe shows two projects assigned to the user that have a parent that is not assigned to the user. Therefore the parent (“Vögel”) is displayed with grey text colour and icon to indicate missing access rights. The project “Vögel weltweit” is set to read-only for the current user, therefore the display text has a grey text colour and icon is grey, too.

 

 

Projects and descriptors 

A descriptor is not directly assigned to a project, instead “descriptor trees” are used. One descriptor may be included in several descriptor trees and therefore belong to several projects or it might be unassigned. The picture below (from Edit descriptor) shows that one descriptor belongs to several projects, since it is part of different descriptor trees. As in the description example, the picture shows a parent project (“Vögel”) that is not accessible for the actual user and therefore displayed in grey text colour. Contained in that parent project there are two parallel projects that include the same descriptor: “Vögel Deutschlands” and “Vögel weltweit”, which is read-only and therefore displayed in grey colour. 

The Edit project panel provides the panel to edit descriptor trees, too. Here all descriptors for the selected projects are displayed (see picture below). For special purposes, e.g. copy of descriptor trees, other projects and their trees may be included in this view.

 

Jan 14, 2025

Security

Security

A user can be in 6 groups with diverse rights in the database where certain higher groups have all rights of lower groups in addition to special rights for this group, e.g. the group DataReader can only read the data while DescriptionsEditor has the rights of DataReader and additionally can edit the data in descriptor tables - see overview below.

Summarzied overview of the permissions of the groups

Role Permissions in addition to lower role resp. user group Inculded rights
Administrator Edit own user permissions; use database maintenance functions ProjectManager, CacheAdmin
ProjectManager Create, edit and delete project data; import data with project information TerminologyEditor
TerminologyEditor Create, edit and delete descriptor data; import data without changing project information   DescriptionsEditor
DescriptionsEditor Create, edit and delete description data DataReader
DataReader View description, descriptor, project and cache mapping data; export data DataUser
DataUser View descriptions without “withheld” descriptors and without resource data  

Two additional roles have been introduced for the handling of the cachedatabase

Role Permissions in addition to lower role resp. user group Inculded rights
CacheAdmin Edit cache related table data CacheUser
CacheUser View cache database and project data DataReader

In addition to the mentioned roles a “System Aministrator” may use the Login administration to add other users to one of these groups and grant access to one ore more projects. If you are an “Administrator” you have the right to modify the projects assigned to your own login.

To place a user in one of the groups, go to the loginadministration. In the window that will open select a login and a database. The roles available in the selected database will be listed as shown below. Use the > and < buttons to add or remove roles for the login in the database (see below).  

 

To see the detailed permissions of a role, select it in the list of Available roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

 

 

Jan 14, 2025

Tutorial

Tutorial - first steps

This tutorial will guide you through the first basic steps in DiversityDescriptions. After the installation, make sure you have access to the database. To start the programm double click on the DiversityDescriptions.exe in the directory where you copied the files of DiversityDescriptions. The main window will open.

 

In this tutorial it is assumed that you installed a local database server and are running DiversityDescriptions with the DiversityDescriptions_Worshop database available at our training server. If you are running a private environment with sufficient rights, you may create an empty DiversityDescriptions database. If you open this window for the first time, you need to connect to the database. Click on the button or choose Connection → Database… from the menu. A window will open where you may enter your account information and choose the database (see image below, for further information see databaseaccess).

 

After connecting to the server and choosing a database click on the OK button to return to the main form. As indicated by the symbol in the right upper corner, you are now connected to the database. The tooltip of the button will show your current login information (see below). 

 

 

Tutorial files

For DiversityDescriptions a number of tutorial files are available that provide examples, e.g. for using the matrix import wizard. The whole example demonstrated in the following pages is available as an SDD file and can easily imported. To copy the tutorial files into your resources directory select Administration->  Tutorial files … from the menu. 

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Subsections of Tutorial

Tutorial Categorical Descriptor

Tutorial - Enter categorical descriptors

To create a new categorical descriptor, select edit mode descriptors from menu Edit->Descriptors. Now click on the button in the upper left panel (see point 1 in image below). 

The new descriptor is created with a numeric name. Change it to “Leaf length” (see point 2 in image above) and set the sequence number to “3” (see points 3 in image above). Now switch to the main tab and check that the descriptor type is “Categorical” (see points 4 and 5 in image above). Finally save the descriptor (see point 6 in image above) and the descriptor name will be updated in the header and the query panel at the left side of the window.

As for the other descriptors we want to attach a resource link to our new categorical descriptor, that symbolizes the descriptor’s duty (see image below, a link to Wikipedia was used).

 

Certainly the categorical descriptor shall be attached to the “Descriptor tree for tutorial” that was created in the last step. In the descriptor tree tab select “Descriptor tree for tutorial” and click button at the right tool bar (see image below).

 

For categorical descriptors we have to define categorical states, which define the possible character values. Select the “Categorical states” tab (see point 1 in image below) and enter the three categorical state names “green”, “yellow” and “red” in the table (see points 2 in image below). Finally save the descriptor (see point 3 in image below).

For each categorical state resources may be assigned. Therefore select the categorical state where you want to enter the resources (see point 1 in image below) and enter a resource name (see points 2 in image below). In this case we do not assign an URL to a picture but attach color values. Therefore click the color button in the task bar and select a color value (see points 3 to 5 in image below). Finally save the descriptor (see point 6 in image below).

For our tutorial we need a second each categorical descriptor. Create the categorical descriptor “Plant growth type” (see points 1 to 4 in image below). This descriptor shall always be used in the descriptions, therefor mark it as mandatory (see point 5 in image below). Finally save the descriptor (see point 6 in image below).

For descriptor “Plant growth type” enter the categorical states “Tree”, “Shrub”, “Herb”, “Succulent” and “Other” (see image below).

Finally append descriptor “Plant growth type” to the descriptor tree for tutorial (see image below).

A more detailled description of all editing options can be found in the Edit descriptors section of this manual.

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Tutorial Descriptions

Tutorial - Enter description data

Now that we have entered several descriptors and categorical states we have defined a “terminology” to enter descriptive data. To create a new description, select edit mode descriptions from menu Edit->Descriptions. Now click on the button in the upper left panel (see point 1 in image below). If you are asked for the project, select “Tutorial”.

The new description is created with a numeric name. Change it to “Example plant” (see point 2 in image above) and check that project “Tutorial” is assigned to the new description (see points 3 in image above). Finally save the description (see point 4 in image above) and the description name will be updated in the header and the query panel at the left side of the window.

 

Enter resources for the description

As described for the descriptors, for each description resources may be assigned. Therefore click on the “Resource links” tab, which looks exactly the same as described in chapter “Enter a textdescriptor” (see image below, a link to Wikipedia was used).

 

 

Enter descriptive data

Now let’s start entering the descriptive data. Open the “Descriptor view” tab (see point 1 in image below). In the left part of the window there is a list of the desriptors. Select descriptor “Plant growth type” (see point 2 in image below) and on the right side the associated categorical states are diplayed. Click on the square in columne “x” besides the state “Tree” to set the check mark (see point 3 in image below). Finally save the description (see point 4 in image above).

 

Next select the descriptor “Literature” tab (see point 1 in image below). In principle you could enter a text in the right area “Descriptive text”, but for this example two other things shall be demonstrated. In the first column of the descriptor list the sequence number (“Nr.”) is displayed. A small square behind the number indicates that resources have been attached to the descriptor (see point 2 - upper arrow - in image below). You can view the attached resources by a double-click on the sequence number (see point 2 - right arrow - in image below). In some cases you do not have data available for a certain descriptor but you want to express that data should be entered. Therefore you can sen one or more “Status data” values in the right lower part of the window  (see point 3 in image below). Finally save the descriptor (see point 4 in image below).

For each categorical state resources may be assigned. Therefore select the categorical state where you want to enter the resources (see point 1 in image below) and enter a resource name (see points 2 in image below). In this case we do not assign an URL to a picture but attach color values. Therefore click the button in the “…” column and select a color value (see points 3 and 4 in image below). Finally save the descriptor (see point 5 in image below).

The last descriptor not yet used is “Leaf color”. Select it from the descriptor list an chek the categorical state “gree” (see points 1 and 2 in image below). The square in column “Nr.” of the “Categorical states” indicates that resources are attached. Double-click it to view the resources (see point 3 in image below). Since we attached three different colors for that categorical state, you may scroll through the different resources by using the “right” and “left” arrow key on the keyboard (see point 4 in image below). Finally save the descriptor (see point 5 in image below).

 

An alternate description data view

If you have defined many descriptors and one specific description references only a small amount of the descriptors, the “Descriptor view” might be quite confusing. In this case an alternate representation, the “Continuous view” might be helpful (see image below). Here only the descriptors that have been referenced in the description data are shown and the values (categorical states, statistical measures or plain text data) are attached at the descriptors. Additionally some extra information is color coded, e.g. “Plant type” is displayed in light red text because it is a mandatory descriptor. For details check the Editdescriptions section of this manual.

 

Enter description scope

As last step in this section the insert of “Description scopes” shall be demonstrated. In our example we want to enter a taxon name and link it to a taxon name service in the internet.

First select the “Main attributes” tab and click button if visible (see points 1 and 2 in image above). When you now select the scope type “Taxon name” (see point 3 in image above) you could enter a taxon name, e.g. “Ulmus campestris”, in the text box that appears right from the scope type. But we want to create a link to the internet service “Catalogue Of Life”, therefore press button . Now a separate window opens (see image below). Select “CatalogueOfLife” as database (see point 1 in image below). Enter the search string “ulmus camp” in the query field and start a search (see points 2 and 3 in image below). When you select a search reult (see point 4 in image below), you can watch the stored data in the lower part of the window. Finally click “OK” to store the link (see point 5 in image below).  

For scope type “Taxon name” links to three different internet services may be set. If you use the DiversityWorkbench module DiversityTaxonNames, you can build an own taxon database and link entries to descriptions. Other scoe types that allow linking to DiversityWorkbench modules are “Geographic area” (DiversityGazzeteers), “Reference” (DiversityReferences), “Specimen” (DiversityCollection) and “Observation” (DiversityCollection also). Additionally there are the scope types “Sex”, “Stage”, “Part” and “Other scope”, which have certain values defined in the Edit projects section. Remember that in step Create a new project we inserted the sex values “Male” and “Female” and assigned them for the tutorial project. Try to insert the scope value “Female” for the example description!

A more detailled description of all editing options can be found in the Edit descriptions section of this manual.

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Tutorial Descriptor Dependencies

Tutorial - Enter descriptor dependencies 

In our final tutorial step we take a short look on the descriptor applicability rules. In out example we have two descriptors dealing with leaf properties, “Leaf color” and “Leaf length”. If you have chosen the categorical state “Cactus” for the descriptor “Plant growth type”, it usually does not make sense specifying leaf properties. You can enter such kind of descriptor dependencies in a formal way. 

Select edit mode projects from menu Edit->Projects , search for project “Tutorial” and open the “Descriptor applicabilities” tab (see points 1 to 3 in image above). Select the controlling descriptor “Plant type” (see point 4 in image above) and in the section “Controlling states” a list of the descriptor’s categorical states is displayed. Select the controlling state “Succulent” (see point 5 in image above) and then click on button to enter the first controlled descriptor (see point 6 in image above). This opens a selection window where you select descriptor “Leaf color”  (see point 7 in image above). Repeat the last step to insert descriptor “Leaf length” as second controlled descriptor. 

After that check that for the two dependent descriptors the applicability rule “inapplicable” is set (see point 1 in image below). Finally save all changes (see point 2 in image below). 

To try out the applicability rules,  select edit mode descriptions and search for the example plant (see points 1 and 2 in image below). Open the “Descriptor view” tab, expand the tree and select descriptor “Plant growth type” (see points 3 to 5 in image below). Click on button to show the “Categorial states”. Deselect state “Tree” and select state “Succulent” instead (see point 6 in image below). In the “Summary data” section the text color of the descriptors “Leaf color” and “Leaf length” changes to grey to indicate that the descriptor is not applicable. Since for that descriptors values have been specified, the backround color is changed to yellow to indicate that the applicability rules are broken (see point 7 in image below).

In the “Descriptor view” tab the “descriptor inapplicable” property is indicated by an “x” in column “!” of the descriptor list (see image below).

 

Jun 5, 2024

Tutorial Html

Tutorial - Generate an HTML document

Now that we have entered our first description data and learned how to find them in the database, we want to share that data. Search for the description of the example plant as described in the previous tutorial step (see image below).

      

From the menu choose Data →  Generate document … and a window will open as shown below. Select the “Example plant” (see point 1 in image below). Then set the options Include resources to show the images we have assigned and Include descriptors to generate the descriptor definitions in the same document (see point 2 in image below). Finally click on button Create HTML documentation and the data will be shown in the HTML window (see point 3 in image below). If you scroll down or click on a descriptor name in the description data you will find the descriptor data. In the working directory of Diversity Descriptions a HTML file has been generated that might be used to publish your data. 

 

  

This tutorial is continued in the sections listed below.

Jul 5, 2024

Tutorial Modifiers

Tutorial - Assign modifiers 

Modifiers may be used in the description data for an additional characterization of categorical or quantitative descriptor data. There are five different modifier categories: Certainty, Seasonal, Diurnal, Misinterpretation and Other. An additional modifier class, Frequency is only applicable for categorical descriptors. Although you are allowed to define own modifier values, there is a large number of commonly used predefined modifier and frequency values, which should be preferred. We now want to insert those predefined values into the database. 

Select edit mode projects from menu Edit->Projects and open the “Modifier/Frequency” tab (see point 1 in image above). The modifier and frequency tables should both be empty. A click on button in the modifier section (see point 2 in image above) opens a window with the predefined values (see impage below left). Click on button selects all values from the list. Click “OK” and all modifier values are now inserted in the modifier table. Proceed in the same way with the frequency values (see point 3 in image above and image below right). The values are now available for all projects in the database. 

   

To use certain modifiers in the descriptive data, the allowed values must be assigned to certain descriptors. This is done int the descriptor tree in almost the same way as the assignment of statistical measures to quantitative descriptors. Select the “Descriptor tree” tab (see point 1 in image below) and click button to dispay the recommended values. Then select descriptor “Leaf color” and select some modifier and frequency values (see point 3 in image below). Finally save all changes (see point 4 in image below). 

Now let’s try out the modifiers in our example description. Select edit mode descriptions and search for the example plant (see points 1 and 2 in image below). Open the “Descriptor view” tab and select descriptor “Leaf color” (see points 3 and 4 in image below). In the “Categorial states” section you can now find two additional columns “Modifier” and “Frequence” where you may select from the values you assigned in the previeous step (see point 5 in image below). Finally save all changes (see point 6 in image below).

 

This tutorial is continued in the section listed below. ow.

May 3, 2024

Tutorial New Project

Tutorial - Create a new project

To create a new project, select edit mode projects from menu Edit->Projects. Now click on the button in the upper left panel and confirm with “Yes” (see point 1 in image below). 

The new project is created with a numeric name. Click on button  to change it to “Tutorial” (see point 2 in image above). Then check that no other project is selected as a parent of the new one (see point 3 in image above). Finally save the project (see point 5 in image above) and the project name will be updated in the header and the query panel at the left side of the window (see image below).

If you like, you may now enter additional project data like a detailled project descripition (“Details”), a copyright text (“Rights”), the address of a license text in the internet (“License” - button opens a browser window to navigate to the license page) and you may select the project’s lanuage (see point 1 in image below).

 

If you want to use scope values for sex in your descriptive data, select the scope category “Sex” (see point 2 in image above). Now the “Add” button is enabled. When you click on the button (see point 3 in the image above) a drop-down menu offers predefined sex values. Select “Male”, then again click on the “Add” button and select value “Female”. The two values are now appended to item “sex”. To make them available for the tutorial project click on the boxes before the values to set them checked (see point 4 in image above). If you click on one of the scope values, additional options are available in the task bar at the right (see image below). Finally save the project (see point 5 in image above)

 

For the other scope categories no predefined values exit. When you click the “ Add” button, values with a numeric name will be appended that can be renamed by clicking on button “ Edit” and selecting menu item “ Edit scope name”.

When you create a new project, your user account automatically gets access rights for that project. If you are “Administrator” - which is the case for user “Workshop” in the training database, you may take a look to the login administration from menu Administration->Database …->Logins …. Select the entry “Workshop” from Login, then click on the database “DiversityDescriptions_Base” and open the Projects tab in the login administration (see below). You find the new project “Tutorial” in the Accessible projects list.

If you are working with a private database installation and are logged in with the same Windows accout that has been used for installation of the Microsof SQL-Server, you are the “database owner” (dbo), which has the highest database access rights. In this case select entry “dbo” from Logins. As “dbo” you can administrate access rights of any user and create or delete logins. 

A more detailled description of all editing options can be found in the Edit projects section of this manual.

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Tutorial Quantitative Descriptor

Tutorial - Enter a quantitative descriptor

To create a new quantitative descriptor, select edit mode descriptors from menu Edit->Descriptors. Now click on the button in the upper left panel (see point 1 in image below). 

The new descriptor is created with a numeric name. Change it to “Leaf length” (see point 2 in image above) and set the sequence number to “2” (see points 3 in image above). Now switch to the main tab and set the descriptor type to “Quantitative” (see points 4 and 5 in image above). For the quantitative descriptor we enter the measurement unit “cm”, a minimum and a maximum value (see points 6 and 7 in image above). Finally save the descriptor (see point 8 in image above) and the descriptor name will be updated in the header and the query panel at the left side of the window.

As for the text descriptor we want to attach a resource link to our new quantitative descriptor, that symbolizes the descriptor’s duty (see image below, a link to Wikipedia was used).

 

Certainly the quantitative descriptor shall be attached to the “Descriptor tree for tutorial” that was created in the last step. In the descriptor tree tab select “Descriptor tree for tutorial” and click button tab select “Descriptor tree for tutorial” and click button at the right tool bar (see image below).

 

For quantitative descriptors a number of statistical measures are defined, for which values can be entered in the descriptive data. In the descriptor tree fo each descriptor of descriptor tree node may be specified, which values shall be used in the descriptive data. A click on button opens the recommended statistical measures on the right side of the window (see image below). Select the quantitative descriptor in the descriptor tree and then check the statistical measures “Minimum value”, “Maximum value” and “Mean” (see image below).

A more detailled description of all editing options can be found in the Edit descriptors section of this manual.

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Tutorial Query

Tutorial - Searching the database

To search for data in the database use the query sector in the left part of the window. Depending on the actually chosen edit mode - Descriptions, Descriptors or Projects - the query searches for descriptions, descriptors or (local) drojects. The query conditions are changed depending on the edit mode, too (see images below).

      

To select the query conditions click on the button in the top panel. A window will open as shown below.

 

With the Maximum number of results you may limit the package size which should be retrieved from the server. For a slow connection to the database server choose a low value (e.g. 100 as set by default).

The Limit for drop-down lists restricts the maximum number of drop-down lists which should be created. For a slow connection to the database server choose a low value. The default is set to 0 which means no drop-down lists will be created.

Click on the Check none button to clear the previous selection or click Check all to select all conditions. Alternatively you may display or hide each single query condition by checking or unchecking the entry in the list.

After all query conditions are set, click on the button to start the query. In the result list you should find the description, descriptors or project created in this tutorial. To save your current query click on the button on the right of the button. A window will open as shown below. For more details see the section Savequery.

When you enter new descripors to the databas it may happen that you forgot to assign it to descriptor tree. That means, those desriptor cannot be used for entering description data. Another action that may generate such orphaned descriptors is to delete a project. With that action implicitely the associated descriptions and descriptor trees will be removed from the database, but the descriptors will not be deleted, because they might be assigned to a different descriptor tree (and project).

To find and delete orphaned descriptors, set mode “Edit descriptors” (see point 1 in image below). Then set query condition “Descriptor tree - Assignment” to “missing” (see point 2 in image below) and start the search (see point 3 in image below). If you want to deleted the found descriptors, you can select them in the resulg list (multiple selection is possible) and click button to delete them. 

  

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Tutorial Sort Descriptors

Tutorial - Sort the descriptors

In the tutorial steps when we created a new descriptor, we usually set the field “Nr.” (sequence number), which determines the sequence the descriptors are displayed in several lists, e.g. when you enter description data. If you like to change that display sequence, it is quite uncomfortable, to go through all descriptors and change the sequence numbers manually, but there is a much more comfortable way. Select edit mode projects from menu Edit->Projects or from the bottom control (see point 1 in image below). Now click on the button to find the project “Tutorial” (see points 2 and 3 in image below). Open the “Descriptor tree” tab and expand the trees (see points 4 and 5 in image below). 

The “Descriptor tree” tab in the “Edit projects” mode looks almost like that one in the “Edit descriptors” mode. But there are some important differences. If you are in the “Edit descriptor” mode, only the actually selected descriptor will be displayed in the tree. In the “Edit projects” mode all descriptors are diplayed! Therefore the descriptors may now be shifted up and down to change the order (see points 1 and 2 in image below). 

 

Now select the “Descriptor tree for tutorial” and click button (see image below left). With this action you indicate that this descriptor tree should be complete, i.e. it contains all descriptors for the project. Now the additional button is displayed that allows to take over of the descriptor tree order to the descriptor’s sequence numbers (see image below right).

   

When you click on button a window opens that displays the changed sequence numbers of the descriptors (see imabe above). After confirming the changes with “OK” the new order will be effective in the descriptor list of the “Edit descriptions” (see image below).

 

This tutorial is continued in the sections listed below.

May 3, 2024

Tutorial Text Descriptor

Tutorial - Enter a text descriptor

To create a new text descriptor, select edit mode descriptors from menu Edit->Descriptors. Now click on the button in the upper left panel (see point 1 in image below). 

The new descriptor is created with a numeric name. Change it to “Literature” (see point 2 in image above), because this descriptor shall allow insert of literature references or citations as free form text into the description data. Then set the descriptor type to “Text” (see points 3 in image above) and set the sequence number to “1” (see points 4 in image above). Finally save the descriptor (see point 5 in image above) and the descriptor name will be updated in the header and the query panel at the left side of the window.

If you like, you may now enter additional descriptor data like a detailled project descripition (“Details”) or “Notes”. But we want to attach a resource link to our new text descriptor, that symbolizes the descriptor’s duty. Therefore select the “Resource links” tab (see point 1 in image below) and enter the resource name “Literature” (see point 2 in image below). Now you can enter the URL of a picture that is reachable in the internet (see point 3 in image below, a link to Wikipedia was used). Alternatively you may double-click on the “URL” field to open a browser window, where you can navigate to the picture location. Finally, don’t forget to save your changes (see point 4 in image below).

 

Until now the descriptor is not assigned to any project, i.e. it cannot be used for entering descriptive data. Assignment of descriptors to projects is done by using “descriptor trees”. This allows on the one hand a thematical grouping of the descriptors, on the other hand the descriptors may be appended to several trees simultaniously. I.e. descriptors my be used in several distinct projects.

Since no descriptor tree has been created yet, select the “Descriptor tree” tab (see point 1 in image below), right-click the project “Tutorial” and select context menu entry “Add descriptor tree” (see point 2 in image below). A new descriptor tree is appended to the project “Tutorial” with a numeric name. Right-click the descriptor tree and select “Edit name” from the context menu to change the name to “Descriptor tree for tutorial” (see point 3 in image below). To append the actual descriptor to the tree, click button at the right tool bar (see point 4 in image below). In the “Descriptor tree” tab most functions are alternatively accessible by the tool bar at the right or by the context menu that opens when you right-click a tree node. Finally, don’t forget to save your changes (see point 5 in image below).

 

A more detailled description of all editing options can be found in the Edit descriptors section of this manual.

 

This tutorial is continued in the sections listed below.

Jan 14, 2025

Query Overview

Queries - overview

With the user defined queries, you can define any query condition - this is the default query mode.

Depending on the active edit mode you get one of three different query option panels as shown in the pictures below.

In the lower part you may adjust the Query conditions to restrict the Query results shown in the upper part of the panel. In search texts you may enter SQL wildcards to specify ambigious conditions to match the data. By default only the most importand query conditions are displayed. To modify the query settings, refer to the Query options. Finally section Save query describes how to save and restore a certain query.

Description query window is available from the menu Query Description query …, where you may select and accumulate descriptions in a list. The regular description query is not capable to select descriptions with specific descriptor data. Therefore the Extended query is accessible from the menu Query Extended query …

 

Jan 14, 2025

Subsections of Query Overview

Queries Saved

Save query

If you want to save a current query, click on the button. A window as shown below will open where you can specify the title and description of you query.

After you entered title and description of the query, click OK to specify the query group. A window as shown below will open.

Choose a group from the tree or create a new one an click OK. The new query will be included in the selected group.

 

Finally you can edit the titles and descriptions of the groups an queries. Click the button to store the changes. To delete items from the tree, select it and click on the button. Click OK to save the new query and close the window.

 

Load query

If you want to load a query that has been stored previously, click on the button. A window as shown below will open.

 

Choose a query from the tree and click OK to close the form and filter the datasets according to the selected query.

May 3, 2024

Query

Query conditions

Depending on the activated edit mode you get one of the three query options pannel below. The options for a fast search are displayed in the main window beneath the list of the items. You can change this arrangement using the / button to place the query options on the left side of the item list.

To search for an item enter the restrictions in the fields for the search conditions and click on the button. The entities found in the database will be shown in the result list. To add items with differing search conditions click on the button. To clear all entries in the query fields use the button. If the list of items is longer than your maximal number of returned items you can browse the next items with the button. To move back to the previous block of items click on the button.

With button you can select all entries in the result list. If you want to remove entries from the selected list, choose them and click on the button. If you want to keep the selected entries in the list and remove the rest, click on the button. This will not delete the data from the database, but remove them from your query result. With the resp. buttons you can change the order of the results between ascending and descending. To hide the area containing the search fields click on the  button. If the search area is hidden and you want to start a new search, just click on the  button.

To see the command generated by the program to retrieve the data right-click on the button to open the context menu (see below).

A window will open containing the command used to retrieve the data (see below).

With the button you may control auto-remember of the last submitted query parameter. If you re-start the application and connect to the same database, the last used query will automatically be submitted. If you prefer to switch off auto-remember, click the button and it will change to . In the main menu Query → Preferred project … you may select a project that will be used as a pre-selection for Description and Descriptor query, if no other query parameter have been restored. 

Within the query options you have several possibilities to specify your search restriction. Use the drop down button to change between the operator. The available operators are shown in the table below.

Operator Meaning Example
Text
search for an entry like … Pinus s[iy]lvestris % (you can use wildcards)
= search for an entry exactly equal to … Pinus silvestris L.
search for an entry not like … Pinus s[iy]lvestris % (you can use wildcards)
search for an entry where a value is missing …
search for an entry where a value is present …
- search for an entry between … and … 2000 - 2005
| search within a list of entries, separated by “|” 2000 | 2003 | 2005
Numeric
= search for an entry exactly equal to … 2006
< search for an entry lower than … 2006
> search for an entry bigger than … 2006
- search for an entry between … and … 2000 - 2005
| search within a list of entries, separated by “|” 2000 | 2003 | 2005
search for an entry where a value is missing …
search for an entry where a value is present …
Date
= search for an entry exactly equal to … 20.3.2006
< search for an entry lower than … 20.3.2006
> search for an entry bigger than … 20.3.2006
search for an entry where the date is missing …
search for an entry where the date is present and complete …
Hierachy
= search for an entry exactly equal to … M-Fungi
search for an entry that is not equal to … M-Fungi
search for missing entry …
search for present entry …
Δ search including childs in a hierarchy … M-Fungi
XML
/ Search for entries containing a given XML node settings
¬ Search for entries not containing a given XML node settings
search for missing entry …
search for present entry …

For yes/no fields you will get an checkbox with 3 options: = yes, = no, = undefined 

 

Query in modules

In the query for scopes linked to another module click on the button to open a window where you can search for values within the linked module. A click on the button will show a list of the selected items, button the related database (see image below).

Module related restriction
Operator Meaning Example
Search for entries with a list ... Rosa | Rosa caninia | ...
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269
Picea abies L.

 

Jan 14, 2025

Query Options

Query options

The maximal number of items shown in a query result can be set in the window for the query options. The default value is set to 100. If you have a fast connection to your database or need to see more or less results, you may change this value to any number you like.

To change the displayed search fields click on the  button. This opens a form where you can select and deselect the fields shown for searching specimens. You might also change the maximum number of items that will be shown in the result list.

The limit for the creation of drop down lists is by default set to 0, that means no dropdown lists will be created. If you set the limit to e.g. 1000 and connect to a database, the programm will create drop down list based on the entries in the database to ease the entry in the query. For slow connections you may set this to lower value to speed up the start of the program. If you set the value to 0 no drop down lists will be created.

The minimal numbers of characters for a selection from the drop down list is by default set to 3.

After having edited the query options click OK to store your selection. The new selection will become active for the next query. To ease the selection and deselection of query options you may use the buttons Check all, Check none, Expand and Collapse.

To search for a field within the database, use the search function that will check the names and descriptions of the fields and mark them as shown below.

After having edited the query options click OK to store you selection. The new selection will become active for the next query.

May 3, 2024

Query Window

Collect descriptions

With menu item Query Collect descriptions … you can open a query window for descriptions as shown below. This window will also open when you click a description selection button in several other forms. 

Start a query and select the entries you want to take over into the result list. By clicking the button Add you insert the selected entries. With button Delete all you can clear the result list. By clicking on button you may open an extended query window and take over the results in the query result window. 

You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. To export the checked results to a tab-separated text file, click the button and view the exported list by clicking . If you want to view a single entry of the result list, you may select it in the result list and press the button. When you close the window by a click on the OK button, the checked entries are passed to the main window of Diversity Descriptions. 

May 16, 2024

Result list

Result list

The result list displays the descriptions, descriptors or projects found in a query.

With combobox order by: you may adjust the sorting and presentation of the query results. For example the descriptors may be displayed with their sequence number, name or ID on as shown in the images above.

You can restrict the maximal number of results together with the queryoptions (click on the button), for example if you have a slow connection to the database. As a default the maximal number is set to 100. If the number of datasets according to your query is higher than the maximal value set in the query options this will be indicated in the header of the list.

To search for items, enter the restrictions in the fields for the search conditions and click on the button. The items found in the database will be shown in the result list. To add items that match differing search conditions click on the button. If the list of items is longer than your maximal number of returned items you can browse the next items with the button. With button you can select all entries in the result list. If you want to remove entries from the selected list, choose them in the list and click on the button. If you want to keep the selected entries in the list and remove the rest, click on the button. This will not delete the data from the database, but remove them from your query result.

Jan 14, 2025

Wildcards

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

%     any string consisting of no, one or many characters, e.g. Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.

*     any string consisting of no, one or many characters, e.g. Pinus * will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.

_      a single character, e.g. Pinus s**_lvestris will find Pinus sylvestris and Pinus si**lvestris etc.

[]     ** any character out of a given range like [abcde] or [a-e], e.g. Pinus s[iy]**lvestris will find Pinus sylvestris and Pinus silvestris.

[^]   any character not in a given range like [^abcde] or [^a-e], e.g. Pinus s**[^i]**lvestris will find Pinus sylvestris but not Pinus silvestris.

May 3, 2024

Extended Query

Extended query - introduction

With this form you can search description data from the database that match specific conditions of the description data, description scopes and descriptor values. Choose Query → Extended query … from the menu to open the extended query window (see image below). With the button  you can set the timeout for critical database queries, with button you can set the timeout for the web access to resource data. Feedbacks can be sent with the button .

 

First the Project must be selected from the combo box in the upper window area. If you want to include matches that are assigned to the selected project only in the additionalprojects field, check the Additional projects option. The Matches: field shows the number of available description datasets. If any matches are available, the Show matches button is active and by clicking it the datasets are listed in the Result list section (see image below).

 

If you want to view a single entry of the result list, you may select it by a single click on the entry and press the View in separate window button. You may check all entries by clicking the all button, uncheck all entries by clicking the none button or toggle the check marks by clicking the swap button. You may export the checked results to a tab-separated text file by clicking the button and view the exported list by clicking . When you close the window by a click on the OK button, the checked entries are passed to the parent form, e.g. the main window of Diversity Descriptions (see below). If you do not want to take over the query results to the parent form, close the extended query by pressing the Cancel button.

 

Continue with:

Jan 14, 2025

Subsections of Extended Query

Extended Query Parameter

Extended query parameter

As you have seen in the introduction the basic filter in the extended query are the selected Project and Additional projects. You may introduce additional query restrictions for description data, description scopes and descriptor conditions, which are shown in the Query parameter area. By clicking on button Add description, Add scope or Add descriptor in the Query parameter tool strip a query parameter control is inserted at the end of the query parameter list. When you enter query parameter, the field Matches: will be updated immediatly. To see the Result list, you will have to click on button Show matches (see picture below). 

If you have entered several parameter controls, you might wish to de-activate one of them temporarily, e.g. to check its effect on the result list. Remove the check mark in the beginning of the first line of the query parameter (see item 1 in image below) and the whole condition will be ignored. Below this check box you find by default the symbol (see item 2 in image below), which means “logical AND”. If you specify several query parameter controls, which are all adjusted to , a matching description must fulfill all entered query conditions simultaneously.

You may click on the symbol to change it to (see item 3 in image below), which means “logical OR”. In this case the result list will include all descriptions that fulfill the first descriptor condition and additionally all descriptions, which fulfill the second condition. I.e. each “AND” condition will reduce the list of matching descriptions and each “OR” condition will add its matching descriptions to the result list.  

By clicking on a parameter control it is selected as the active control (see above). The active parameter control is shown with light blue background. The resulting SQL query may be viewed with button . You can delete the current query control by clicking on button Remove or all query controls by clicking on button in the Query parameter tool strip.

 

Continue with:

Jan 14, 2025

Subsections of Extended Query Parameter

Extended Query Description

Extended query parameter - Description conditions

Press button Add description in the Query parameter tool strip to insert a new query parameter condition to search for specific values in the description data. A control representing a single description data filter will be added at the end of the query parameter list. You may enter filter criteria for the description ID, Title text, Details text and AID text (alternate id). To enable a certain item, select the check box before the parameter text (picture below). For the numeric parameter ID you may enter a number and select the comparer by clicking the  button . Available comparers are = (equal), (not equal), < (less), > (greater), (less or equal) and (greater or equal).   

 

For the text parameters (title, details and AID) you may enter a search text and select one the matching options Contains, Starts with, Ends with or Exact match. Capitalization is not taken into account. For option Contains the database text must contain the search text. The options Starts with and Ends with only check the database text begin rsp. end for a match. Finally option Exact match requires identical texts. For option Exact match you may enter an empty text, which will match if in the database an empty text or a NULL value (if a NULL value is allowed) is present. For the other matching options an empty search text does not make sense because it will allways match. By checking the Invert option you may invert the search criteria. E.g. the option Exact match with empty search text and Invert will search for “text present” (“not empty string”). You may use the wildcards _, [] and [^] in your search text, but not %. % is automatically inserted in the correct places by selecting the matching option.

If you entered more than one condition as shown in the image above (ID and Title text), the default adjustment is that all conditions must match. This is indicated by the symbol behind the text Description data in the header line, which means “logical AND”. If you want to get a match for any of the entered conditions, you may click on the symbol to change it to “logical OR” (see image below). 

The next example shows how two description conditions are used to exclude a certain number range of the ID from the result list. The first condition restricts the result list to all IDs smaller than 343. The second condition adds all results with IDs larger than 426, which is achieved by a logical OR of the condition operator (). In this example it does not matter which one of the two conditions is marked as “AND” rsp. “OR”. If both conditions would be marked as “OR”, there would not be any restriction left except the project.  

 

Continue with:

Jan 14, 2025

Extended Query Descriptor

Extended query parameter - Descriptor conditions

Press button Add descriptor in the Query parameter tool strip to insert a new query condition for the search of specific values in the description summary data. A control representing a single descriptor filter will be added at the end of the query parameter list. Now you have to select the descriptor that shall be included in the search filter. This can be done by selecting the descriptor’s sequence number with combo box No.:, from an alphabetical descriptor list with combo box Descriptor: or by selecting from the descriptor tree with button (see picture below). 

 

After selecting the descriptor the query control shows query parameters depending on the descriptor type (see below). You may search for descriptions that do not have any data for the selected descriptor by checking option absent. The currently marked parameter control is shown with light blue background. You can delete the current query control by clicking on button Remove or all query controls by clicking on button in the Query parameter tool strip.

In the parameter control the descriptor type is indicated by symbols in the beginning of the first line ( categorical, quantitive, text or sequence). If additional information for the descriptor are available in the database, you can show them as bubble help by moving the mouse cursor over the symbol. If resource data are available for a descriptor, the symbol is displayed with coloured background and you can view them by double-clicking it (see image below).

   

Each parameter control has two main sections:

  • At the left you find the section for the descriptor parameter, depending on its type (Categorical states, Statistical measures, Descriptive text or Molecular sequence). If this section is checked and no other data have been entered, the query filters for all descriptions that include any value for that descriptor, e.g. any descriptive text or any categorical state. You may search for descriptions without descriptor data by checking option no value. By entering additional query data, the filter becomes more restrictive.  
  • At the right you find the section for the descriptor Status data. If this section is checked and no status value has been selected, the query filters for all descriptions that include any status data value for that descriptor. At the end of the Status data check box by default the symbol indicates that all selected data status values must be present in the matching descriptions. By checking dedicated status data values, the filter becomes more restrictive (logical AND). If you click on the symbol you can change it to (logical OR) to find matches for any of the selected status data values.  

If both sections are selected, matching descriptors must fulfill both conditions, i.e. the value must be present and the status data value must be set.

 

Notes

In the descriptive data you may enter free text notes to all text and sequence data. Furthermore individual notes may be entered for every selected categorical state and statistical measure. You may include additional query contitions for each of those notes, therefore the symbol is included at the appropriate places. To enter a query condition, click the button and a window as shown below will be opened.

You may enter a Search text that shall be part of the notes text. Capitalization is not taken into account. For option Contains the notes text must contain the search text. The options Starts with and Ends with only check the descriptor text begin rsp. end for a match. Finally option Exact match requires identical texts. Check the option Invert to invert the search criteria. You may use the wildcards _, [] and [^] in your search text, but not %. % is automatically inserted in the correct places by selecting the matching option.When you click OK the additional query condition will be active and the icon background changes to red (). If you want to remove the query condition, open the notes form, uncheck the Enable notes filter option and click OK.

For text and molecular sequence data exactly one note is possible for each descriptor value, therefore you find exactly one symbol for entering a query condition. For categorical and quantitative data you may enter a note for each single state rsp. statistical measure. Here you may search for notes of the specific state rsp. measure by clicking on the symbol located at the element. Additionally you may search for notes entered at any state or measure of the descriptor. Therefore an additional symbol is located in the header section besides the no value check box (see image above). 

 

Modifier and frequency

In categorical and quantitative descriptive data you may select modifier values for every selected categorical state and statistical measure. For categorical data additionally a frequency value may be selected. You may include additional query contitions for each of those modifier and frequency values, therefore the symbols (modifier) and (frequency) are included at the appropriate places. To enter a query condition, click the button and a window as shown below will be opened.

You may select the modifier rsp. frequency values for filtering from the recommended values of the current descriptor. Check the option Invert to invert the search criteria. A hint text explaining the resulting filter will be displayed in the lower area of the window. When you click OK the additional query condition will be active and the icon background changes to red (, ). If you want to remove the query condition, open the form, uncheck the Enable filter option and click OK.

 

Continue with:

Jan 14, 2025

Subsections of Extended Query Descriptor

Extended Query Categorical

Extended query parameter - Categorical states

In this query control the categorical states are listed. If pictures or colours are assigned to the categorical states, they can be viewed by clicking on the state name (see picture below). You may switch off automatic loading of the resource view by clicking the button (“no web”), which will be indicated by a yellow symbol background. If this “no web” option is activated, only local resources, e.g. colours, will be shown. If during loading of remote resources an error occurs, e.g. due to a timeout, the “no web” option will automatically be activated. 

You may change the display order of the states between the standard numeric order , alphabetical order and reverse alphabetical order by clicking the appropriate button. If the state list exceeds the standard height of the control, a scroll bar will show at the right side of the state list. You can enlarge the control by clicking the button at the lower left side (see picture above). To return to the standard size, click on button  (see picture below).

Categorical states that are not checked are not relevant for the filter. If you want to search for a categorical state that is NOT present, check the option invert behind the categorical state name (see picture below). You may search for descriptions that do not have selected any of the categorical states by checking option no value.

By default all categorical states of a descriptor that are selected must be present in the matching descriptions. You may change this logical AND to a logical OR by clicking on the symbol behind the no value check box, which will change to symbol (see picture below). Now all descriptions will match, which include one of the selected states. 

 

Continue with:

Jan 14, 2025

Extended Query Quantitative

Extended query parameter - Statistical measures

In this query control the recommended statistical measures are listed. You may enter a single value for an exact match in the from: field or a value range in from: and to: (see picture below). If you enter no numeric values (or only a value in to:), a search for value presence will be performed. Remark: If you modify a value in a from: or to: field, you must leave the field to update the Matches: count. If you want to exclude the specified value range from the query, check the invert option. If you do not enter a value, the statistical measure is checked for presence.

If the statistical measure list exceeds the standard height of the control, a scroll bar will show at the right side of the statistical measure list. You can enlarge the control by clicking the button at the lower left side (see picture above). To return to the standard size, click on button  (see picture below).

Statistical measures that are not checked are not relevant for the filter. If you want to search for a statistical measure that is NOT present, check the option invert and do not enter any values (see picture below). You may search for descriptions that do not have specified any statsistical measure by checking option no value.

By default all statistical measure conditions of a descriptor that are selected must be fulfilled in the matching descriptions. You may change this logical AND to a logical OR by clicking on the symbol behind the no value check box, which will change to symbol (see picture below). Now all descriptions will match, which include one of the selected measure conditions. 

 

Continue with:

Jan 14, 2025

Extended Query Sequence

Extended query parameter - Molecular sequence

In this query control you may enter a Sequence that shall be part of the molecular sequence data. Capitalization is not taken into account. For option Contains the sequence text must contain the search string (see image below). The options Starts with and Ends with only check the descriptor text begin rsp. end for a match. Finally option Exact match requires identical texts. You may use the wildcards _, [] and [^] in your sequence text, but not %. % is automatically inserted in the correct places by selecting the matching option.

Check the option Invert to invert the search criteria (see picture below), i.e. there is a match if the molecular sequence does NOT contain, start or end with the specified Sequence. The query condition Invert with Exact match and empty Sequence is the query for molecular sequence present. A molecual sequence can only be absent if notes are present, because otherwise the descriptor had no value. You may search for descriptions that do not have specified any descriptor data by checking option no value

 

Continue with:

Jan 14, 2025

Extended Query Text

Extended query parameter - Descriptive text

In this query control you may enter a Search text that shall be part of the text descriptor data. Capitalization is not taken into account. For option Contains the descriptor text must contain the search string (see image below). The options Starts with and Ends with only check the descriptor text begin rsp. end for a match. Finally option Exact match requires identical texts. You may use the wildcards _, [] and [^] in your search text, but not %. % is automatically inserted in the correct places by selecting the matching option.

Check the option Invert to invert the search criteria (see picture below), i.e. there is a match if the descriptive text does NOT contain, start or end with the specified Search text. The query condition Invert with Exact match and empty Search text is the query for descriptive text present. A descriptive text can only be absent if notes are present, because otherwise the descriptor had no value. You may search for descriptions that do not have specified any descriptor data by checking option no value.   

 

Continue with:

Jan 14, 2025

Extended Query Scope

Extended query parameter - Scope conditions

Press button Add scope in the Query parameter tool strip to insert a new query parameter condition to search for specific description scope data. A control representing a single description scope filter will be added at the end of the query parameter list. Now you have to select the Scope type that shall be included in the search filter. You have the choice between the general scope types ( Geographic area, Sampling plot, Reference, Observation, Specimen and Taxon name) and the project specific scope types (Other scope, Sex, Stage and Part). The project specific scope types are only shown if values have been entered in the database (see Editing the project). 

 

General scopes

After selecting the scope type a query control as shown in the image below is available. You may search for descriptions that do not have any scope of the selected type by checking option no value. Otherwise the two text search fields Scope text and Scope URI are available, which can be activated by checking the box before the text. 

 

You may enter a search text and select one the matching options Contains, Starts with, Ends with or Exact match. Capitalization is not taken into account. For option Contains the database text must contain the search text. The options Starts with and Ends with only check the database text begin rsp. end for a match. Finally option Exact match requires identical texts. For option Exact match you may enter an empty text, which will match if in the database an empty text or a NULL value (if a NULL value is allowed) is present. For the other matching options an empty search text does not make sense because it will allways match. By checking the Invert option you may invert the search criteria. E.g. the option Exact match with empty search text and Invert will search for “text present” (“not empty string”). 

With the query option Module filter you may build a item list from a linked database using a remore query. You may search for scopes that match one of the entries (operator ) or do not link any of the entries (operator ). You may select the operator by clicking the drop down button . To build the list click on the button to open a window where you can search for values within the linked module. A click on the button will show a list of the selected items, button the related database (see image below).

 

A click on the button switches the filter mode between link search and text search. For some scope types, e.g. Taxon names, additional operations are available (see image below). While for the standard operations all elements of the query result are entered into the item list, they will take the selected value as starting value and add synonym/hierarchy values.

Operator Meaning Example
Search for entries with a list ... Rosa | Rosa caninia | ...
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269
Picea abies L.

If you entered more than one condition, the default adjustment is that all conditions must match. This is indicated by the symbol behind the text Description scopes and the no value check box, which means “logical AND”. If you want to get a match for any of the entered conditions, you may click on the symbol to change it to “logical OR”. 

 

Project scopes

After selecting a project specific scope all available values inserted in the database will be listed (see image below). You may select one ore more of the avalable values. Furthermore you may check the invert option to search for description entries that do not include the specified scope value. 

If you entered more than one condition, the default adjustment is that all conditions must match. This is indicated by the symbol behind the text Description scopes and the no value check box, which means “logical AND”. If you want to get a match for any of the entered conditions, you may click on the symbol to change it to “logical OR” (see image below). 

The project specific scope values must be marked as “recommended” for each project. In the query control you will be shown every value, but the not recommended ones will be listed with an appropriate text shown in the image below. 

 

Continue with:

Jan 14, 2025

Extended Query Save

Save and load extended query

The complete query schema may be saved into an XML file using the button , which opens a dialog window to enter the file name and location. By default the schema file name is generated as:

     <working directory>\ExtendedQuery\DescriptionQuery_<Database name>_<Project>.xml 

The XML schema file includes information concerning the database, the project and the query parameter. By pressing the button in the Query parameter section, a query schema file can be opened. If the schema does not meet the active database you will be informed by a message box. In the query file all relevant parameter are identified by the database internal numeric IDs. If no matching values are found, it is tried to get them by their names. Since the names might be ambigious, the corresponding element are displayed with a yellow background colour (see image below).

 

If the parameter could not even be assigned by their names, this is indicated by a red background color (see picture below).   

May 3, 2024

Data Editing

Editing the data

The database of DiversityDescriptions consists of three major areas:  

  • The descriptive data (descriptions) reference elements of the descriptive terminology and add specific data, e.g. numeric values.
  • The descriptive terminology, consisting of descriptors, categorical states, statistical measures and modifiers. 
  • The project data build the administrative frame for terminology and descriptions. Each description belongs to exactly one project. By additional entities (descriptor tress) it is possible to restrict the descriptors, statistical measures and modifier that shall be used in a certain project.  

In almost all forms an Extended text editor can be opened for single text fields that provides additional editing features.  

Corresponding with that three major sections of the data model, the DiversityDewscriptions application provide three edit modes. The edit mode is diplayed at the bottom of the main window (see picture below). After the first start the edit mode is preselected to “Edit descriptions”. You can switch the edit mode using the menu Edit-> DescriptionsEdit→ Descriptors or Edit-> Projects. Alternatively you may switch the edit mode by click the mode button in the upper left corner of the header area (item 3 in picture below) or on the tiny triangle besides the edit mode display in the status line at the bottom (see item 4 in picture below).

The main window of the DiversityDescriptions client contains two main areas. At the left you find the query and the results of this query. In the right part the data of the dataset selected in the result list is shown.

 

Basic operations

In each edit mode there are some common functions for storing and reloading data, to create a new dataset or delete or copy the actual dataset. On top of the query results (item 1 in image above) there is button to store the actual dataset, button to delete the actual dataset and button to create a new dataset. By pressing button  the actual dataset is reloaded, i.e. changes that have been made will be dropped. Finally, button copies the data of the actual dataset to a new one.

Some of those buttons can be found in the tool bar at the right side of the edit window (item 2), too.

Additionally to explicit saving by pressing the button, an automatic saving of the dataset is done, if an entry in the query result list is selected or a new query is performed. If a dataset has been modified without saving, a message window will appear and ask if changes shall be saved for several actions, e.g. change of edit mode, connetion to a database or if the application is closed. 

 

Translations

For many database tables the text columns may be translated into different languages. To enter, modify or view the translated texts, use the translations editor. For an overview on multilingualism in Diversity Descriptions see chapter translations.  

 

Description HTML form

When you have started a query and selected a description, you may open an HTML form to view and edit the data (button marked as item 5 in image above). It provides a simplified user interface for access to a subset of the description data. 

 

Description grid view

An alternate form for editing or viewing the data of several descriptions in a grid is provided by the description gridview. It provides a simplified user interface for access to a subset of the description data. 

 

Sample data grid view

An alternate form for editing or viewing the sample data of several descriptions in a grid is provided by the sample data gridview

 

Table editors

For a selected set of database tables a direct data editing in a grid is provided by the table editors

 

Jan 14, 2025

Subsections of Editing

Edit Description

Editing the description

After starting a database query and selecting an entry in the result list the dataset is diplayed in the edit window. In the header area the dataset name, the default project language and the URI of the current dataset are show (see picture below). Below the header area the description name may be edited in a text box. Changes of the description data, e.g. the name, will be visible in the header after saving the dataset. To check dataset changes, click on the button to open the history. By clicking button you may open a simplified HTML form to view and edit the description data.

The main description data may be accessed in the first Mainattributes tab, which is described below. Click on one of the other tabs in the picture below to go directly to the appropriate manual chapter.

img/DD_Description_Main

 

Main attributes tab

The main attributes tab provides in the upper area a field to enter additional description details and a wording for natural language support. The optional filed AID may keep an alpha-numeric alternate ID of the dataset. If used, it should be unambigious within the project, but this is not checked by the program. Click on to get an overview of the used keys. 

 

Scopes

The next section Description scopes allows specification of description scopes. This sections consists of the scope table with scope type and value and a edit section to modify a seleted scope entry or to enter e new scope. The scope types Geographic ares, Reference, Specimen, Observation and Taxon name allow input of a free-form text or reference to the corresponding DiversityWorkbench module or a web service. The connection to to a module or web service is done using the button . After selecting the entry in the referenced database the text will be taken over and the backround colour of the scope value field changes to yellow. A further editing of the text will not be possible (see below).

 

Additionally the edit section now shows the buttons to view the database link and  to remove the database link. In the latter case editing of the scope value will be possible again.

If a scope entry has been selected in the scope table, it can be modified in the edit section. If you want to enter a new scope value instead, press the button at the end of the edit line. The scope entry in the scope table will be deselected and a selection box for the scope type appears in the edit section (see below).

You may insert mutiple scope values with links to a DiversityWorkbench module or a webservice. Therfore enter a new scope value with scope type Geographic ares, Reference, Specimen, Observation and Taxon name (or select one, which is not yet linked). Besides the scope type dropdown box the button is shown, which allows insert of multiple scopes (see image below).

You may insert mutiple scope values with links to a DiversityWorkbench module or a webservice. Therfore enter a new scope value with scope type Geographic ares, Reference, Specimen, Observation and Taxon name (or select one, which is not yet linked). Besides the scope type dropdown box the button is shown, which allows insert of multiple scopes (see image below).

In the remote query panel you find the section Unit list, where you may add the currently selected query result by clicking the button. When you select an entry in the Unit list, you may remove it by clicking or view the data in a separate window by clicking . When you have collected all query results click the OK button and the scopes are inserted for the description (see below).

 

Project scopes

Besides the already mentioned scope types that allow input of a free text or reference to a database entry, the scope types Sex, Stage, Part and Other scope provide pre-defined scope values. The values can be administrated as described in the Editing theProject chapter. For each project a different set of values can be selected as “recommended” values. If for the current description project scope values are defined/assigned, they are shown in the right part of the description scopes as Project scopes (see below).

Selecting or deleting of a scope entry can be easily done by selecting clickin on the check box before the scope value. You may select rsp. deselect all scope values of a certain scope type (Sex, State, Part or Other scope) by clicking the check box of the category. If for a scope value a detailled description text has been stored, you may view it as bubble help by moving the mous cursor over the values.

If for a description a scope value is selected, that is not assigned to its project, the value ist show with yellow background (see below). Such a situation can occur, if the scope value has been removed for the project or if a description has been moved to a different project. 

 

Project

The section Project allows the selection of the project the description is assigned to. This adjustment has influence of the available values of scope types Sex, Stage and Other scope, the available descriptors and recommended modifier/frequency values and statistical measures of the description. Therefore this unambiguous adjustment might be seen as the “terminology project” of the description item. The access rights for a certain user to the projects are controlled with the login settings (see chapter Loginadministration). When you click on a project name, you may view some additional project data (see image below middle). 

     

If access to a certain project is restricted to “read only”, it is displayed with grey colour and symbol in the Project section (see pictures above). A “read only” project cannot be selected for the actual description. If the selected description has already been assigned to a “read only” project by another user with appropriate rights, this is indicated at the right bottom corner of the application window (see above below right).

 

Additional projects

In section Additional projects you may make the description accessible for additional projects. To assign a description to a project click on the  button. To remove it from a project, select the project from the list and click on the  button. Additional projects without write access are shown in the upper part of the window, projects with full access in the lower (or only) part (see image below). If you do not have any access to a project, it is shown as red text. Be aware that by entering additional projects you may grant editing rights for single descriptions to users that have no write access to the current project!

     

Be aware that by entering additional projects you may grant editing rights for dedicated descriptions to users that have no write access to the current project! If you have write access to the terminologyproject of a description item and granted access to another project, where you have read-only access, you nevertheless may withdraw these rights by removing it from the Additional projects.

   

 

Continue with:

Jan 14, 2025

Subsections of Edit Description

Edit Description Continuous View

Editing the description - Continuous view tab

The continuous view tab provides an alternate view on the descriptive data. In the Summary data only the descriptors are included where data have been entered. At the right side there is a tool strip. The displayed buttons will change depending on the selected entry. The descriptor types categorical, quantitive, text and sequence are indicated by different colours and icons as shown in the example at the bottom. By pressing the button on the tool strip this example may be hidden. Descriptors that are marked as mandatory are displayed with light red text, descriptors that are inapplicable are greyed out. Additionally coloured background indicated possible problems, e.g. if an inapplicability rule has been ignored or a not allowed descriptor has been used. A tool tip text shows the error or warning reason when the mouse curser is moved over the element.

By pressing the button the tree view may be expanded to display the contained categorical states, quantitative measures or texts. By pressing the button the tree will be collapsed to descriptor level.

To insert a descriptor press , to delete a descriptor select the entry and press . If only a single value shall be removed, select the entry and use the button. All these functions can alternatively be accessed by the context menu by a right-click on the tree node.

If for a descriptor resources, e.g. pictures, are avaialble, this is indicated by the background color of the descriptor icon. Categorical states with resources are marked with icon (see first entries in picture above). The resources may be accessed by a right-click on the tree node and selecting context menu item View resources (see picture above).

 

Structured descriptor view

If for the project a structured descriptor tree is defined, i.e. a descriptor tree that contains at least one descriptor tree node, the Descriptor tree: drop-down list is shown below the descriptor tree (see image below left). If a descriptor tree is selected, the descriptor tree node hierarchy will be included in the output and the descriptors will be arranged accordingly. The names of the descriptor tree nodes and the descriptors will be reduced by parts contained in the supriour hierarchy nodes (see image below right).  

If for a descriptor tree node resources are available, this is indicated by the grey background color of the descriptor tree icon. The resources may be accessed by a right-click on the tree node and selecting context menu item View resources. Additional descriptor tree node information, e.g. an optional abbreviation or details text can be viewed as bubble help by placing the mouse cursor over the item.  

 

Editing summary data

A click on opens an edit window at the right part of the tab. This window provides the same functions as available in the descriptor view tab. The picture below shows the resource linked to a categorical state that can be opened by doule-clicking the state ID in the Categorical states section. 

 

Continue with:

Jan 14, 2025

Edit Description Descriptor View

Editing the description - Descriptor view tab

The left part of the descriptor view tab shows all descriptors available for the description’s project. The entries in column “!” indicate some additional information about the descriptor:

  • Descriptor is referenced in the summary data (●)
  • Descriptor is referenced in the status data (○)
  • Descriptor is mandatory, values must be specified (!)
  • Descriptor is inapplicable because of other specified descriptors/categorical states (x)
  • Descriptor is exclusive, only one categorical states shall be selected (e)

If resources are linked to a descriptor, the entry is marked by a square (□) behind its sequency number and a tool tip appears when the mouse cursor is moved over the “No.” column (see below). By double-clicking the sequence number a “Media view” window can be opened to view the resources.

 

If for the project descriptor trees are defined, the Descriptor tree: drop-down list and Restricted check box are shown below the descriptor list (see image below left). If a descriptor tree is selected, the names of the descriptor tree node hierarchy is included in the descriptor names (see image below right). This feature is useful, if several descriptors with ambigious names exist the can now be distinguished. E.g. two descriptors “colour”, one at descriptor tree node “Leaf”, the other at descriptor tree node “Blossom” will become “Leaf colour” and “Blossom colour”. If the descriptor name already includes the hierarchy, the duplicate parts will be filtered. In the mentioned example the descriptor names “Leaf colour” and “Blossom colour” will not be changed, if the descriptor tree is selected.

If additionally the Restricted option is set, only the descriptors included in the selected descriptor tree are displayed (see image below right, missing descriptor number 14). So you have the option to create several descriptor trees that include only special aspects of the description’s property (e.g. morphology, molecular biology and so on) to get a clearly arranged descriptor list. 

 

Editing summary data

The right part of the descriptor view tab shows at the bottom the Status data values of the selected descriptor. It is possible to select several values for each descriptor. In the “Notes” column additional information concerning the selected data status may be entered. By a double click on the “Notes” entry a separate edit window can be opened.

Depending on the descriptor type you can find at the top either Categorical states (see large picture above), Statistical measures, Descriptive text or Molecular sequence (see pictures below). In the “Notes” columns additional information concerning the specific categorical state rsp. statistical measure may be entered. By a double click on the “Notes” entry a separate edit window can be opened.

  

To enter a statistical measure value click in the “Value” field and enter the value, the check mark in field “x” will be set automatically. If recommended modifier values are defined (see “Editing the Descriptor” and “Editing the Project”), a value may be selected from the drop down list “Modifier”. If no modifier values are available, the appropriate table column may be hidden. In the “Notes” field an additional text may be added. By double-clicking the “Notes” field the Extended texteditor can be opened.

The descriptive text may be edited diretly in the window, which shows the pure text without any formatting. In the notes field an additional text may be entered. By double-clicking the text fields the Extended text editor can be opened. 

The molecular sequence window displays in the status line below the edit area the sequence type (“Nucleotide” or “Protein”), the symbol length (“Len:”) in case of proteine sequences, the gap symbol (“Gap:”) if defined, the long text of the actual element and the position (“Pos:”) (see image below). In case of three-letter proteine symbols the position is the number of the amino acid symbol, not the character position. By pressing the TAB key the cursor jumps to the next symbol. 

When characters are entered in the edit area that are recognized as valid symbols, they will automatically be formatted. One-letter symbols are converted to upper case characters, three-letter symbols are converted according the “Xxx” schema, e.g. “Ala” for “Alanine”. The sybols for the nucleotide bases "Adenine", "Cytosine", “Guanine”, "Thymine" and "Uracil" are dispayed with different colors. Ambiguity symbols and gap symbols are shown in grey color. If the ambiguity symbols have not been enabled in the descriptor data, they will be displayed with yellow background. Symbols that have not been recognized are displayed with red background. 

The molecular sequence window offers some additional functions available in the sequence menu. It may be opened by moving the mouse cursor over the control header (“Molecular sequence”, see window below left) or from the context menu (right-click on the sequence edit area, see windows below right). With menu item Import you may read the seqeunce data from a file and insert them to the description. With menu item Export you may export the actual sequence data to a file.  

   

By double-clicking the molecular sequence area or from sequence menu Open → Sequence a separate edit window may be opened (see image below). On the top of the window there is the drop-down menu Insert symbol: where a value may be selected from a list. After selecting the value press the [ENTER] key or click on to insert the selected symbol at the cursor position. 

To select a categorical state set a check mark in field “x” with a mouse click. If recommended modifier or frequency values are defined (see Editing the Descriptor and Editing the Project), values may be selected from the drop down lists “Modifier” rsp. “Frequency”. If no modifier or frequency values are available, the appropriate table column may be hidden. In the “Notes” field an additional text may be added. By double-clicking the “Notes” field the Extended text editor can be opened. 

If a “Modifier” or “Frequency” value is selected, the multiple specification of a dedicated categorical state is possible. A tool tip offers to add a row by doouble-click, if mouse cursor is moved over the “State” field (left picture below, picture in the midddle after double click). Multiple specifications of one categorical state are only allowed if they have been assigned different modifier and frequency values. Inputs offending these restrictions will be ignored an a cell error will indicate the problem (right picture below).

   

If resources are linked to a categorical state a tool tip appears when the mouse cursor is moved over the ID (left picture below). By double-clicking the ID a “Media view” window can be opened to view the resources (right picture below).

 

If more than one resources have been assigned to one entry, a slider will be visible at the bottom of the “Media view” window. To switch through the available resources the slider can be moved using the mouse or the right and left arrow keys (see below).

 

 

Continue with:

Jan 14, 2025

Edit Description HTML

Edit description in HTML form

With this form you can easily edit the description data in an HTML form. After starting a description query and selecting an entry choose Edit -> Edit as HTML form … from the menu or click on the button at the right side of the main Diversity Descriptions window. A window as shown below will be opened.

 

When you move the mouse cursor over embedded pictures, they are slightly magnified, by clicking on the resource, you may show it in full size (see below). Use button  Home to return to the HTML form. 

 

With drop down button Options you may insert some additional input fields in the form, e.g. item details or notes. With drop down button Scope you may insert input fields for the vasiour scope types and drop down button Color lets you select the background color. All that changes come into affect, when you reopen the form or redraw the HTML form using the Reload button.

After clicking the Reload button you will be asked if you want to discard all changes. By selecting No the HTML form data will be written into the local data store, otherwise all inputs will be reset. To exit the form and save all changes in the local data store, click the OK button. To ignore your changes, click the Cancel button and you will be asked if you want to discard all changes. The HTML form utility works completely on the local data store. I.e. if you edited the description data in the main form of Diversity Descriptions and start the HTLM form editor without saving the data, all changes are only present in the application dataset. To store the data in the database, click the save button of the main form!

 

 

May 3, 2024

Edit Description Molecular Sequences

Editing the description - Molecular sequence symbols

The editor for sequence data recognizes predefined symbols for nucleotide and protein sequences according the IUPAC definitions.

 

Nucleic acid symbols

Symbol Name
A Adenine
C Cytosine
G Guanine
T Thymine
U Uracile
W Weak (A or T) 
S Strong (G or C)
M aMino (A or C)
K Keto (G or T)
R puRine (G or A)
Y pYrimidine (C or T) 
B not A (B comes after A) 
D not C (D comes after C)
H not G (H comes after G)
V not T (V comes after T and U)
N No idea (not a gap)

The symbols with grey background are ambiguity symbols. The difference between “N” and a gap symbol (usually “-”, but any other symbol may be defined in the descriptor) is that a gap symbol represents an unspecified number of unknown symbols but “N” stands for exatly one nucleic acid. 

 

Amino acid symbols

Name 1-letter sybmol 3-letter sybmol
Alanine A Ala
Arginine R Arg
Asparagine N Asn
Aspartic acid S Asp
Cysteine C Cys
Glutamic acid E Glu
Glutamine Q Gln
Glycine G Gly
Histidine H His
Isoleucine I Ile
Leucine Leu
Lysine K Lys
Methionine M Met
Phenylalanine F Phe
Proline P Pro
Serine S Ser
Threonine T Thr
Tryptophan W Trp
Tyrosine Y Tyr
Valine V Val
Selenocysteine U Sec
Pyrrolysine O Pyl
Asparagine or aspartic acid B Asx
Glutamine or glutamic acid Z Glx
Leucine or Isoleucine J Xle
Unspecified or unknown amino acid X Xaa

The symbols with grey background are ambiguity symbols. The difference between “X” rsp. “Xaa” and a gap symbol (e.g. “—”, but any other symbol may be defined in the descriptor) is that a gap symbol represents an unspecified number of unknown symbols but “X” rsp. “Xaa” stand for exatly one amino acid. The amino acids “Selenocysteine” and Pyrrolysine" are non-standard amino acids that only occur in certain species. 

 

Continue with:

Jan 14, 2025

Edit Description Resources

The resouce links tab allows assigment and inspection of resource links for the description. In the lower Resources part of the tab there are two tables. Ar the left the “Resource” table specifies the single resources, at the right the “Resource variant” table contains the associated URLs to images, video or sound resources.

To enter a new resource select the empty line at the end of the “Resource” table and click on the “Resource name” field. After entering the “Resource name” (leave the cell by pressing the TAB key) automatically a new value for the sequence number (“No.”) is initialized. The sequence number determines the display order in tables and may be changed manually. You may order the resource entries by clicking on the column header or by using the arrow buttons in the left tool strip ( and for up and down, and to shift the selected entry to top or bottom). After ordering the resources click button to renumber the entries starting with “1” and make the changes effective. In field “Ranking” you may enter a numeric value in range 0 … 10 expressing the suitability of the resource. In field “Role” you may select one of the offered values.

If you want to delete a resource, you have three choices:

  1. Select the resource and press the button in the left tool strip.
  2. Select the resource and press the Delete key on the keyboard.
  3. Enter the sequence number column (“No.”) and remove the value. After leaving the cell the entry will be deleted.

In any case you will be asked if you want to delete the data row, if resource links are present. 

To view or edit the additional resource data and copyright information press on the button besides the resource table. In field License: and a link to the license text in the web may be entered, in field Rights: you may enter a copyright text. By pressing the button a browser window can be opened to navigate to the license page in the web. Furthermore you may enter a detailled text (field Details:), the resource language (field Language:) and set the Display embedded flag (see picture below). If any additional resource data have been entered, this will be indicated by a square (□) behind the resource name’s sequence number (see picture above).

 

To enter a resource link, first select the entry in the “Resource” table, then select the empty line at the end of the “Resource variant table”. By clicking on the “URL” field a web address may be entered. By double-clicking the “URL” field a browser window opens to navigate to the resource. For each resource several URLs to resource variants with different quality levels, e.g. different resolution, may be inserted. For each entry in the URL table a different value of “Variant” must be selected.

As an alternative to a resource URL a colour may be spcified in the format “color://#rrggbb” where “rrggbb” specifies a hexadecimal colour code. The colour can simply be seleced by clicking the button besides the resource variant table.

To remove a resource variant, select the entry and press the button in the right tool strip or the Delete key on the keyboard. Alternatively you may delete the “URL” entry in the resource variant table. 

The button besides the resource variant table allows you to view a resource URL in the system browser.

The upper part of the resource links tab consists of a preview window on the left side and the complete list of resource links. By selecting one of the links the preview is shown on the preview window. If you press button in the preview window, the resource is opened in a separate viewer window.

At the bottom of the resource links tab the media data of a selected URL are displayed. These data can be edited by double-clicking the “Type” entry in the resource variant table, by clicking at one of the media data value fields or the button. The edit dialog provides the possibility to access the URL to get available data. Additionally the values may be edited manually.   

 

Copy description resources to a descriptor

If you have write access to descriptors of the currently selected description’s project, you may copy a selected resource URL to a descriptor. After clicking the button a window will open to select one of the accessible descriptors (see image below). Remark: To see the copied resources in the Descriptorview or the Continuous view, you will have to reconnect to the database. 

 

Continue with::

Jan 14, 2025

Edit Description Samples

Editing the description - Sample data tab

The sample data tab allows assigment and inspection of sampling events and associated sampling units for the description. In the upper left Sampling events part of the tab there is a list of the sampling events stored for the description. By selecting a sampling event entry the Event data are shown in the upper right part of the tab. Here you may edit the event name, a detailled description, the date and time rsp. a date and time span and geographic data. To insert a new sampling event click on the button in the Sampling events section, to delete the selected sampling event and all stored sampling unit data press the button (see image above). 

The geographic area may be linked to an entry of a DiversityGazetteers database (see section Module related entry). If latitiude and longituede have not yet been entered, the coordinates of the selected DiversityGazetteers entry will be inserted. By pressing the button a window to select the coordinates by Google maps will be opened. Field Geo. datum allows entering short text concerning the geodetic datum. If coordinates are entered using Google maps a remark that WGS84 coordinates are used will be inserted.

 

Editing sampling unit data

For each sampling events one or several Sampling units may be entered. A sampling unit represents a tuple of values that belong together, e.g. because they represent a single specimen. For each descriptor, which is represented by the table column, a value may be entered in a sampling unit, which builds a single table line. The background colour of each table column indicates the type of sample data: categorical, quantitative, text or sequence . If the number of sampling units is displayed in field Units of the Sampling units section in the lower part of the tab. If sampling units are present, the number is displayed with yellow background (see image below).

To view the unit data, select a Descriptor tree and choose the descriptor sequence range (From descriptorto descriptor) to restrict the number of columns displayed in the unit table. Finally press button and the sampling untis will be displayed (see image below). If you prefer to display the present sampling units automatically whenever you select a sampling event, click on the number behind Units. The background changes from yellow to red to indicate this mode. When you select a cell and resources are available for the selected descriptor column, the button will be shown. You may click it to view the descriptor resources. 

To insert a new sampling unit press button . By clicking on the free space at the beginning of a table line you mark the whole sampling unit (see picture below). Now you have the additional options to delete the unit by pressing button or to copy the data to a new sampling unit by pressing the button. Keep in mind that all unit data will be copied, even if you do not see all descriptor columns due to the display restrictions.

 

When you select the Sampling unit ID cell you may enter a collection specimen in the Unit specimen control below the units table. By clicking the button (see section Module related entry) you can link it to an entry in a DiversityCollection database. If the sampling unit is linked to a database entry in DiversityCollection, the text of the Unit specimen: control is shown with light yellow background. You may view the linked data by clicking the button or double clicking the Sampling unit ID cell.

To modify categorical sampling data enter the table cell and press the button within the cell. A control will be opened where you can select the categorical states and enter notes or modifier values (if defined) for each single state (see image below).

 

For all other sampling data the value can be entered directly in the table cell. Notes for the selected table cell are entered in the Notes: text box directly below the units table. For categorical, text and molecular sequence sample data a separate edit window can be opened by double-clicking the table cell. For molecular sequence data the tool strip buttons (import) and  (export) allow import and export from rsp. to dedicated file formats as described in sections Import sequencedata and Export sequence data.

 

Continue with:

Jan 14, 2025

Export Sequence

Editing the description - Export sequence data

With this form you can export data from the database to a file. Choose Export from the sequence menu to open the window for the export. Format specifies the file format, currently FASTA and FASTQ are supported.

 

In the Header settings you may specify if a new header shall be generated or if the notes shall be searched for a FASTA rsp. FASTQ header. In case of FASTA export you may specify in the Comments settings section if FASTA comment lines from the notes (starting with “;”) shall be inserted after the header, the whole notes shall be inserted as FASTA comments or if the notes shall be ignored. If Insert description comments is checked, two comment linsed wit the description and descriptor title will be generated.

In the Header preview section you may check and edit the resulting header, in the Sequence preview section the converted sequence in one-letter notation is displayed.

In case of FASTQ export the Comments settings are irrelevant. If the notes include a QUALITY STRING sections, it is inserted in the FASTQ output (see image below). If no quality string can be found or the Find FASTQ quality from notes has been unchecked, the lowest quaality value “!” is inserted.

 

Click on the button to select the file where the data shall be exported. By default the data are appended at the end of the selected file, check the Overwrite existing file option to overwrite it. Finally click the Save file button to write the data.

 

Continue with:

Jan 14, 2025

Edit Description Grid

Description grid view

After starting a database query for descriptions select Grid → Description grid view … from the menu. The query result list is passed to the description grid view form and a window as shown below opens (click the button Display description table to build the table output). In the first line the database name is displayed. If you move the mouse cursor over the database name, a tooltip shows the actual connection paramter. 

img/DD_Description_Main

The table in the lower part of the window shows the description titles in the first column and the summary data in the other columns. Each summary column holds the data of a certain descriptor. If a cell with summary data is selected, the summary details and the descriptor status data are displayed in the upper right part of the window. The upper left part of the window shows the selection parameters that are used for building the description table. You may change the table colors by clicking the button . A form as shown below will be opened. 

Click on buttons categorical, quanitative, text or sequence to select the corresponding table colors. By clicking the Reset button below the color, the corresponding default value will be selected. After changing the table colors by a click on the OK button, you must re-draw the table.

 

Selection parameters

In the upper left part of the parameters for the description table can be adjusted. If in the query list passed to the form descriptions of different projects are present, the displayed project can be selected with the Project: drop-down box. The entries in the drow-down list include the project name, followed by the number of descriptions for that project in brackets and an asterisk (*) if the user has only read access for that project.

The Descriptor tree drop-down box restricts the descriptor columns to the descriptors contained in the selected tree. Furthermore the tree hierarchy is included in the descriptor names if a structured descriptor tree is selected (see images below).

  

The values From descriptor and to descriptor limit the range of descriptor sequence numbers that is included in the discription tabe. Be aware that this restiction is additionally effective to a selected desriptor tree! If you want to de-activate this restriction, select “from” value 0 “to” value 999999 by a double-click on the labels From descriptor rsp. to descriptor. The limitation of the number of descriptor columns makes speeds up the description table generation, especally if many descriptor (e.g. some hundrets) are present.

If you select option Separate statistical measures, separate columns will be insterted in the data grid for each quantitative descriptor and its recommended statistical measures. This option may be useful for editing quantitative summary data that use other statistical measures than Min, UMethLower, Mean, UMethUpper and Max (see section Data editing for details.

Finally click the button Display description table to build a new description table according to your settings. During output of the description table the icon of the button changes to  and you may abort processing by clicking the button. 

 

Continue with:

Jan 14, 2025

Subsections of Edit Description Grid

Edit Description Grid Copy

Description grid view - Copy or create descriptions

To copy one or more descriptions select the whole data rows by clicking in the area left from the “Description title” column. In the tool strip the copy button appears (see image below).

img/DD_Description_Main

After clicking the button you may be asked if you want to copy description resources, too. Be aware that the copy operation is directly performed within the database. I.e. that local changes that have been done in the sources desrcriptions will not be included in the targets unless you save your data before copy (see image below, second and last line in descriptors 28 and 29). 

img/DD_Description_Main

 

New description

To enter a new description, click on button and a new row will be appended (see image below). Same as for copy the new description is created directly within the database.

  

 

Continue with:

Jan 14, 2025

Edit Description Grid Editing

Description grid view - Data editing

The first column of the description table shows the description titles, which are fixed. I.e. if you scroll the summary data to the right, the titles are still visible at the left. The other columns show the summary data, where the descriptor type is indicated by the background colour: categorical, quantitative, text or sequence. The column titles include the descriptor name, the mesurement unit in square bracket for quantitative descriptors and the descriptor’s sequence number (see image below).

When a summary cell in the description table is selected, the field Description: shows the description title and field Descriptor: shows the symbols according the descriptor type ( for categorical, for quantitative, for text and for sequence) and the descriptor title. If for a descriptor resources are available, this fact is indicated by a coloured symbol background. You may view them by a double-click on the descriptor title. If for a description resources are available, the symbol is displayed before the title. Double click in that symbol to view the resources. 

For the selected cell the summary data and the descriptor status data are displayed in the upper right area of the window (see image above). You may edit the data within these controls as described in section Editing the description - Descriptor view tab of this manual. For modified summary cells the text colour changes to blue and the description titles will be shown with yellow background in the table.

 

Changing the description title

To change the description title, double-click on it in field Description: to open a separate edit window. After comitting the changes with “OK” the description will be marked as modified (see images below).

  

 

Changing the summary data in the table

Categorical summary data

Categorical, states are specified by their sequence number. Multiples are separated by a forward slash ("/", see image below). Existing “notes” will be removed, if the corresponding categorical state is not specified in the input.

  

 

Quantitative summary data

If you did not check the option Separate quantitative measures, for quantitative summary data only the five quantitative measures  

Min Minimum value
UMethLower Lower range limit (legacy data stat. meth. unknown)
Mean Mean (= average)
UMethUpper Upper range limit (legacy data stat. meth. unknown)
Max Maximum value

can be specified within the summary table. The values must be specified in theis given order and separated by a forward slash ("/"). E.g. 1////100 means “Min=1, Max = 100”. If only one value without any slashes is entered, it is assumed than only the “Mean” value is specified. To indicate that values for other than the five mentioned statistical measures are present in the data, an asterisk ("*") is appended in the summary table (see image below, cell value 1////100 *).

  

 

If you checked the option Separate quantitative measures, for each statistical measure in the quantitative summary data a separate column will be allocated in the data grid view. I.e. you can direcly enter your values into the table (see image below).

  

 

Text descriptor and Molecular sequence data

For Text and sequence data the texts may be edited directly within the table. The corresponding “notes” will not be affected.

 

Changing values in a table column

It is possible to modify several values of a single table column. Therefore select the table entries that shall be edited - by selecting an entry and clicking the button in section Column action you may select the whole table column (see image below). Then select the required operation: “Insert”, “Append”, “Replace” or “Clear” and enter the new rsp. new and old value. After clicking the action button - depending on the selected Column action this is (Insert), (Append), (Replace) or (Clear). Be aware that this feature performs a pure text operation in the table columns. Especially for quantitative and categorical data columns the resulting data will be interpreted according to the rules described above an might lead to unsexpected results, if not designed ver carefully. 

 

Continue with:

Jan 14, 2025

Edit Description Grid Save

Description grid view - Save or discard changes

When you click in button “OK” the description grid view is closed and all changes are automatically saved in the database. If you did some changes and want to save them without leaving the form, simply click on (see image below). If you close the window, e.g. by clicking the “Cancel” button, and still have unsaved changes, you will be asked to save or discard the changes.

img/DD_Description_Main

 

Undo all changes

You may discard all unsaved changes without leaving the form by clicking the button and the data will be reloaded form the database (see image below).

  

 

May 3, 2024

Edit Descriptor

Editing the descriptor

After starting a database query and selecting an entry in the result list the dataset is diplayed in the edit window. In the header area the dataset name is shown (see picture below). Below the header area the descriptor name may be edited in a text box and the sequence number (No.) can be set, which determines the display order in descriptor lists. Changes of the descriptor name will be visible in the header after saving the dataset. To check dataset changes, click on the button to open the history.

The main descriptor data may be accessed in the first Main attributestab, which is described below. Click on one of the other tabs in the picture below to go directly to the appropriate manual chapter.

img/DD_Descriptor_Main

 

Main attributes tab

The main attributes tab provides access to an abbreviation, a detailled descriptor text, notes and wording information for natural laguage descriptions. In the bottom area the Descriptor type, Descriptor settings, Measurement data (only for quantitative descriptors) and Molecular sequence data (only for sequence descriptors) can be adjusted. The descriptor type can only be modified, if the descriptor is not referenced by any description. If the descriptor type “Categorical” is changed, already entered categoricalstates will be deleted.

The check box Exclusive (only for categorical descriptors) indicates that only one state shall be specified in a description. Check box Mandatory indicates that for this descriptor always data shall be specified. Statistical measurement scale specifies for categorical descriptors, if the states are unordered (e.g. red/green/blue) of ordered (e.g. bad/medium/good). For quantitative descriptors it specifies if intervals or ratios are measured. Repeatability and Availability specify how reliable (different measurements or scorings by different observers) and accessible the descriptor is, e.g. for identification.

For quantitative descriptors the Unit of the measurement values my be specified either by directly entering the string or alternatively by selecting a Prefix (e.g. “k” for “kilo” = 1000) and the Base unit (e.g. “g” for “gramm”). Unit is prefix indicates that the measurement unit preceeds the measurement value. Minimum and Maximum specify the absolute range limits expected for the measurement values. If in a description specific values, e.g. “Mean”, exceed these limits, a warning will be shown. Values are integer indicates that dedicated values, e.g. “Min” or “Max”, are expected to be integer values. Take care that statisical measures like “Mean” certainly may be real numbers. If this condition is violated in the description data, a warning will be displayed.

For sequence descriptors the sequence type Nucleodide sequence or Proteine sequence must be selected. Enable ambiguity symbols determines if in the sequence data ambiguity symbols like “S” for “C or G” in nucleotide sequences, are allowed. In case of protein sequences the Symbol length may be chosen from one letter sybols (e.g. “A” for “Alanine”) and three letter symbols (e.g. “Ala” for “Alanine). The Gap symbol is a symbol that indicates gaps of unspecified length and must meet the selected symbol length.

 

Project assignement

Descriptors are not directly assigned to a project, instead descriptortrees are used. One descriptor may be included in several descriptor trees and therefore belong to several projects or it might be unassigned. In both cases dedicated hints will be displayed at the bottom of the application window (see pictures above and below).

You can easily find descriptors that are not included in any descriptor tree by setting “Descriptor tree” → “Assignment” to “Ø” in the search criteria. By opening the Descriptor treetab these descriptors may be easily inserted into a tree by selecting the tree (node) and clicking

If the actually selected descriptor is referenced by more than ony project and not all of the projects can be modified by the actual user, the descriptor data cannot be changed, which will be indicated at the lower right corner of the application window (see above).

 

Continue with:

Jan 14, 2025

Subsections of Edit Descriptor

Edit Descriptor Modifier

Editing the descriptor - Modifier/Frequency tab

The Modifier/Frequency tab allows definition of modifier and frequency values. The sequence number column (“No.”) determines the display sequence in selection lists. You may order the entries by clicking on a column header. With the arrow buttons ( ) you can move the selected entries up or down within the table, clicking button or shifts the selected entries to the top respective bottom of the table. After ordering the entries click button to renumber the table entries (starting with “1” for the first table entry) and make the changes effective. After pressing button column “Use” shows the number of references in the database for each modifier rsp. frequency value.

To enter a new modifier or frequency value, select the empty line on the end of the table and click on the “Modifier” rsp. “Frequency” field to enter the new values. After entering the new entry name automatically a new value for “No.” is initialized. To delete an entry, select the entry and press the tool strip button, the Delete key or remove the value in the sequence number column (“No.”).

There is a number of predefined modifier and frequency values commonly used. These values can be accessed by pressing the  button, which opens one of the windows shown below.

 

 By checking of uncecking the values, they can easily be inserted or deleted from the modifier rsp. frequency list. Values that are already used in the database are marked by a grey text colour. When these values are marked to be removed from the list, you will be asked for each single value if it really shall be deleted after pressing OK. New values are inserted at the end of the list (see below).

  

You may order the modifier and frequency values according the sequence of the predefined values by pressing the  button, which opens one of the windows shown below. Values that are not in the predefined lists will be shifted to the end of the list.

 

 

Continue with:

Jan 14, 2025

Edit Descriptor Resources

The resouce links tab allows assigment and inspection of resource links for the descriptor. In the lower Resources part of the tab there are two tables. Ar the left the “Resource” table specifies the single resources, at the right the “Resource variant” table contains the associated URLs to images, video or sound resources.

To enter a new resource select the empty line at the end of the “Resource” table and click on the “Resource name” field. After entering the “Resource name” (leave the cell by pressing the TAB key) automatically a new value for the sequence number (“No.”) is initialized. The sequence number determines the display order in tables and may be changed manually. You may order the resource entries by clicking on the column header or by using the arrow buttons in the left tool strip ( and for up and down, and to shift the selected entry to top or bottom). After ordering the resources click button to renumber the entries starting with “1” and make the changes effective. In field “Ranking” you may enter a numeric value in range 0 … 10 expressing the suitability of the resource. In field “Role” you may select one of the offered values.

If you want to delete a resource, you have three choices:

  1. Select the resource and press the button in the left tool strip.
  2. Select the resource and press the Delete key on the keyboard.
  3. Enter the sequence number column (“No.”) and remove the value. After leaving the cell the entry will be deleted.

In any case you will be asked if you want to delete the data row, if resource links are present. 

To view or edit the additional resource data and copyright information press on the button besides the resource table. In field License: and a link to the license text in the web may be entered, in field Rights: you may enter a copyright text. By pressing the button a browser window can be opened to navigate to the license page in the web. Furthermore you may enter a detailled text (field Details:), the resource language (field Language:) and set the Display embedded flag (see picture below). If any additional resource data have been entered, this will be indicated by a square (□) behind the resource name’s sequence number.

 

To enter a resource link, first select the entry in the “Resource” table, then select the empty line at the end of the “Resource variant table”. By clicking on the “URL” field a web address may be entered. By double-clicking the “URL” field a browser window opens to navigate to the resource. For each resource several URLs to resource variants with different quality levels, e.g. different resolution, may be inserted. For each entry in the URL table a different value of “Variant” must be selected.

As an alternative to a resource URL a colour may be spcified in the format “color://#rrggbb” where “rrggbb” specifies a hexadecimal colour code. The colour can simply be seleced by clicking the button besides the resource variant table.

To remove a resource variant, select the entry and press the button in the right tool strip or the Delete key on the keyboard. Alternatively you may delete the “URL” entry in the resource variant table. 

The button besides the resource variant table allows you to view a resource URL in the system browser.

The upper part of the resource links tab consists of a preview window on the left side and the complete list of resource links. By selecting one of the links the preview is shown on the preview window. If you press button in the preview window, the resource is opened in a separate viewer window.

At the bottom of the resource links tab the media data of a selected URL are displayed. These data can be edited by double-clicking the “Type” entry in the resource variant table, by clicking at one of the media data value fields or the button. The edit dialog provides the possibility to access the URL to get available data. Alternatively the values may be edited manually.   

 

Continue with:

Jan 14, 2025

Edit Descriptor States

Editing the descriptor - Categorical states tab

The Categorical states tab is only enabled, if the descriptor type has been set to “Categorical”. The upper part of the state tab shows the table of categorical states. To enter a new state select the empty line at the end of the table and click on the “Categorical state” field. After entering the “Categorical state” name (leave the cell by pressing the TAB key) automatically a new value for the sequence number (“No.”) is initialized. The sequence number determines the display order in tables and may be changed manually. You may order the state entries by clicking on the column header or by using the arrow buttons in the tool strip right besides the states ( and for up and down, and to shift the selected entry to top or bottom). After ordering the states click button to renumber the entries starting with “1” and make the changes effective.

If you want to delete a categorical state, you have three choices:

  1. Select the state and press the button in the tool strip right besides the states.
  2. Select the state and press the Delete key on the keyboard.
  3. Enter the sequence number column (“No.”) and remove the value. After leaving the cell the entry will be deleted.

In any case you will be asked if you want to delete the data row. If the categorical state is already used in any description items, the number of affected entries will be shown and you have the option to abort the action. 

If for a state at least one assigned resource is present, the state is marked by a square (□) behind its sequence number (see image above). After selecting the categorical state its assigned resources ar displayed in the lower part of the state tab, the State resource links. It allows management of resources linked to a categorical state marked in the upper table. For a detailled description take a look at the Resource links tab section.

 

Continue with:

Jan 14, 2025

Edit Descriptor Trees

Editing the descriptor - Descriptor tree tab

The Descriptor tree tab provides the possibility for a structured assignment of the descriptors to the projects. The Descriptor tree consists of three node types, which show the administered projects, descriptor trees, descriptor tree nodes and descriptors. The tree parts’ colours are shown in the example at the bottom. By pressing the button on the tool strip at the right side the example may be hidden. The buttons displayed on the too strip will change depending on the selected entry.

The descriptor trees support three main functions:

  • Assignment of descriptors to a certain project
  • Selection of recommended Frequency/Modifier values and Statistical measures for a certain descriptor
  • Structured arragement of the descriptors, e.g. for hierarchical selection lists and definition of descriptor subsets for description editing and export

 

Descriptor trees are the root of a tree and may only be appended at a project. To insert a new descriptor tree select a project and press . Descriptor tree nodes may be appended at a descriptor tree or another descriptor tree node. To insert a new descriptor tree node, select the parent and press . Descriptors may be appended to a descriptor tree or a descriptor tree node. To append a descriptor select the parent and press , to remove it select the descriptor and press . All these functions can alternatively be accessed by the context menu by a right click on the entry. The descriptor type is indicated by different icons. Categorical descriptors are marked as , quantitative descriptors as , text descriptors as and sequence descriptors as .

You may change the name of a Descriptor tree or a Descriptor tree node in three different ways:

  1. Select the tree element (single click) and then click once on it.
  2. Select the tree element (single click) and click on button in the tool bar on the right.
  3. Right-click the tree element and select item Edit name from the context menu.

You may edit the name of the selected node within the tree. The Descriptor tree must be globally unique. The Descriptor tree node names must be unique with respect to their tree position, i.e. all nodes with the same parent within a descriptor tree must have distinguished names.

If a Descriptor tree or a Descriptor tree node does not contain any other element, it may be deleted by pressing  (delete descriptor tree) rsp. (delete descriptor tree node). Please be aware that in edit mode “Descriptor” the descriptor tree shows only the descriptor that as actually selected in the query panel! To get a complete overview of all descriptors assigned to a certain descriptor tree and to delete trees or nodes with all included objects, select edit mode “Project” (see Editprojects).

If projects and their associated descriptor trees cannot be changed, because the project has been set to “read-only” state, these parts are displayed with grey text color (see project “Schmetterlinge” in picture above).

Descriptor trees can be marked as “tree complete”, to indicate that they should contain all descriptors of the project. In this case the symbol of the descriptor tree changes from to . Setting and resetting the “tree complete” flag is described in the Edit projects section, where additional edit options are availabe.

When a new descriptor tree or descriptor tree node is inserted it gets a numeric name, which may be changed by clicking on the node or selecting from the context menu. Take care that the names of the discriptor trees must be unambiguous within the whole database! The names of the descriptor tree nodes must only be unambiguous within one parent.

If no descriptor tree is installed for a certain project, all descriptors, modifier/frequency values and statistical measures will be usable in the project’s descriptions. Anyway, if you export data or generate documents an do not have an appropriate descriptor tree, you might have missing data! If a project contains several descriptor trees, the available descriptors are the superset of the descriptors assigned to all contained trees.

 

Sorting of descriptor tree elements 

By pressing the button you can expand the tree view to display all elements, by pressing the tree will be collapsed to descriptor tree level. With the arrow buttons ( rsp. ) you can move descriptor tree nodes up or down rsp. to the top or the bottom. An additional ordering option is to select the descriptor tree node you want to move and click the button. The button’s back color changes to red and you may now select the new position in the tree.

In operation mode Edit projects you may take over the descriptor order from a descriptor tree to the descriptor sequence numbers of all project’s descriptors. This will affect the descriptor presentation for description data editing or document generation.  

 

Descriptor tree node details  

For Descriptor tree nodes you may enter an abbreviation a details text and assign resource data. Select the Descriptor tree node (single click) and click on button in the tool bar on the right. Alternatively you may right-click the Descriptor tree node and select Edit details from the context menu. An edit window as shown below will be opened.

If resources are assigned to a Descriptor tree node, its symbol is shown with grey background in the descriptor tree. You may view the resources by right-clicking it and selecting View resources from the context menu.  

 

Recommended statistical measures, modifiers and frequency values 

Click on in the tool bar to close the edit window in the right part of the tab or on  to reopen it. In the edit window you can select recommended modifier/frequency values and statistical measures. The recommended values can be administered for a selected descriptor or for a selected descriptor tree node. In the latter case selected values are inherited by all subordinate nodes, which will be indicated by the background colour if a subordinate node is selected in the descriptor tree. 

To define the available modifier and frequency values and their display sequence, please refer to the Modifier/Frequency tab. The statistical measure values are predefined, nevertheless their display sequence may be modified using the  button (see image above). A form as shown below will appear. With the arrow buttons ( ) you can move the selected entries up or down within the table, clicking button or shifts the selected entries to the top respective bottom of the table. After ordering the entries click button to renumber the table entries (starting with “1” for the first table entry) and make the changes effective.  

The picture below shows an example for a descriptor where the recommended statistical measures Minimum value, Maximum value and Mean are inherited by the superior node.  

For the contained descriptor only additional values may be selected, but the inherited values cannot be de-selected.

 

Continue with:

Jan 14, 2025

Edit Project

Editing the project

After starting a database query and selecting an entry in the result list the dataset is diplayed in the edit window. In the header area the dataset name and the project language are shown (see picture below). To check dataset changes, click on the button to open the history.

The main project data may be accessed in the first Main attributestab, which is described below. Click on one of the other tabs in the picture below to go directly to the appropriate manual chapter.

img/DD_Project_Main

In DiversityDescriptions a project may be a pure local project or it can be linked with DiversityProjects. By clicking the button above the query window, a new local project is created. For a local project the name can be set freely - as long as it is unambigious within the database - by clicking the  button behind the project name (see image below). By clicking the button you may view the login names that have access to the project.  

If a project is linked with DiversityProjects, the name is fixed to the value set in DiversityProjects. If the name is modified in DiversityProjects, it will change in DiversityDescriptions, too, when the project data are downloaded. The linking of a local project to DiversityProjects is described below in the Cachedprojects section.  

For a linked project some additional buttons are available (see above): With URI you may view the symbolic address of the referred DiversityProjects entry and with you may view the data in DiversityProjects. By clicking the button you may view the login names that have access to the project. With the button you may release the connection to DiversityProjects. I.e. the current project will become a local project.  

  

Main attributes tab

The main attributes tab provides access to a license URI, a short rights text and a detailled project text. The project language can be selected from a list. In field Rights you may enter a copyright text, in field License and a link to the license text in the web may be entered. By pressing the button a browser window can be opened to navigate in the web.

In the Wording field you may enter an alternative project name, which is used for the cache database. When a project has been published in a cache database and it is renamed, this field offers the opportunity to keep the published name. If a project published in the cache database and is renamed, the original project name will be automatically be inserted in the Wording field, if it is empty. Therefore publishing with the old project name will still be possible. To modify the published project name, too, update or remove the Wording entry and re-create the project in the cache database.

With combo box Language you can select the project’s default language. You man change the display and sorting of the entries in the Language combo box from “<code> - <description>” to “<description> - <code>” (and back) by clicking the button . If you need language codes that are not included in the list, click the button. For more details see Edit language codes.

 

Parent project

In the bottom area at the left side the Parent project can be adjusted. If the project has no parent, select “Root” (symbol ). The Parent project adjustment has an influence on the available descriptors, recommended modifier and frequency values and recommended statistical measures, because these adjustments are inherited by the subordinate project. If for a project in the Parent project tree no write access is possible, this is indicated by grey text colour and symbol . The missing write rights for a parent project has no influence on accessability of the actually selected project, except that the parent project adjustment cannot be changed. 

 

Cached projects

The Cached projects section shows entries that are downloaded fromDiversityProjects and not yet used within DiversityDescriptions (see image below, left). Accessible projects are shown with symbol , read-only projects as and projects wihout any access rights as . When you click on the project name, additional buttons are displayed (see image below, right). You may view the database link by clicking on URI or view the data stored in DiversityProjects by clicking on symbol . By clicking the button you may view the login names that have access to the project. With button you may link the current project to the selected DiversityProjects entry.

            

 

Scope values

In the Scope values section at the right the values for scope types “Sex”, “Stage” and “Other scope” may defined. When you mark one of the entries, a tool strip with the available operations is shown at the right border of the control. To insert a new value, select the scope type and press button . In case of “Sex” one of the predefined “sex status” values derived from the SDD standard has to be selected. In all other cases a new value with a numeric key is appended, that can be renamed by pressing the button and selecting Edit scope name or by clicking at the name. 

In case of “Sex” scope the “Edit” menu offers the additional menu items Reset scope name, which appears if the name differs from the original “sex status”. Further the “sex status” value may be changed with menu item Set sex status. For the other scope types you may enter a details text by pressing the button and selecting Edit scope details.

To remove a scope value, select it and press the button. To make a value available for the project, the check box must be checked. If the selected project has a parent and a value has already been checked in the parent project, this is indicated by the background colour (see image below).

 

Continue with:

Jan 14, 2025

Subsections of Edit Project

Edit Project Dependencies

Editing the project - Descriptor applicability tab

The Descriptor applicability tab serves the administration of dependencies between categorical states and dependent descriptors. First a descriptor has to be selected either by its name in the alphabetically ordered drop down list or its sequence number (“No.”) in the first line of the descriptor dependencies tab. If for the selected project a descriptor tree is present, the  button allows selecting the descriptor form the descriptor tree (see picture below). 

The table Controlling states in the upper left part of the tab shows the categorical states if a categorical descriptor has been selected. When you have adusted the restrichted descriptor view, visible by the button in the toolbar of the Dependent descriptor section, only the actually set dependent descriptors are displayed here. You can switch to an alternate Full descriptorview as described below. For each categorical state Dependent descriptors can be inserted by pressing the button. A dialog window opens to select the descriptor either by its name, sequence number or using the descriptor tree (see picture below).

 

In column “Rule” the symbol indicates that the dependent descriptor is inapplicable if the controlling state is present in a description. The symbol indicates that the controlling state must be present in a description if the controlled descriptor shall be applicable. The rule can be toggled by clicking the symbol in the table or by pressing the corresponding button ( rsp. ) at the right. To remove a dependent descriptor select it and press the button.

In the lower part of the tab you find the States controlling this descriptor. You may double-click on the item to select navigate to it for editing. Alternatively you may edit the controlling descriptor states using the control buttons of the tool strip at the right. By double-clicking an entry in Dependent descriptors or in States controlling this descriptor you may navigate forwards and backwards in the chain of dependent descriptors.

If you want to get an overview of all the project’s descriptor dependencies or want to delete all dependencies, take a look at the Applicability tree section below.

 

 

Calculation of the descriptor applicability

To decide if a descriptor is applicable in a description, the following conditions are evaluated:

  • Inapplicable-if rule: If only controlling states are present in a description, these make the controlled descriptor inapplicable. The character remains applicable if either no state at all, or any non-controlling states are present.
  • Applicable-if rule: If any controlling state is present in a description, these make the controlled descriptor applicable. It is inapplicable if only non-controlling states are present.
  • Special condition 1: If the controlling descriptor is inapplicable (through another applicability rule, or through an explicit “Not applicable” data status value), the controlled descriptor is always inapplicable as well.
  • Special condition 2: If no data for the controlling descriptor are present in a description (data completely missing or only status is “Missing data” or “Not to be recorded”), the controlled descriptor always remains applicable.

 

 

Full descriptor view

By clicking the button in the toolbar of the Dependent descriptor section, you can chenge to the full descriptor view (see image below). In section Dependent descriptors all available project descriptors are shown. You may set a dependency by selecting the descriptor and clicking the button rsp. . To remove the dependency, click on button . Alternatively you may click on they symbol in the table column “Rule” to change the values in the sequence -> .

If you select a values for the Descriptor tree, the descriptor list is restricted to the values included in that descriptor tree. Please be aware that existing dependencies might be hidden by such a selection! 

You can return to the restricted descriptor view by clicking on button .

 

 

Applicability tree

Instead of the States controlling this descriptor you may display a complete overview of the descriptor applicability rules by pressing the button in the Dependent descriptors section (see image below). By double-clicking an item in the Applicability tree you can open it for editing.

By pressing the button in the Applicability tree section you can delete all dependencies shown in the tree.

 

Continue with::

Jan 14, 2025

Edit Project Modifier

Editing the project - Modifier/Frequency tab

The Modifier/Frequency tab allows definition of modifier and frequency values. The sequence number column (“No.”) determines the display sequence in selection lists. You may order the entries by clicking on a column header. With the arrow buttons ( ) you can move the selected entries up or down within the table, clicking button or shifts the selected entries to the top respective bottom of the table. After ordering the entries click button to renumber the table entries (starting with “1” for the first table entry) and make the changes effective. After pressing button column “Use” shows the number of references in the database for each modifier rsp. frequency value.

To enter a new modifier or frequency value, select the empty line on the end of the table and click on the “Modifier” rsp. “Frequency” field to enter the new values. After entering the new entry name automatically a new value for “No.” is initialized. To delete an entry, select the entry and press the tool strip button, the Delete key or remove the value in the sequence number column (“No.”).

There is a number of predefined modifier and frequency values commonly used. These values can be accessed by pressing the  button, which opens one of the windows shown below.

 

 By checking of uncecking the values, they can easily be inserted or deleted from the modifier rsp. frequency list. Values that are already used in the database are marked by a grey text colour. When these values are marked to be removed from the list, you will be asked for each single value if it really shall be deleted after pressing OK. New values are inserted at the end of the list (see below).

 

You may order the modifier and frequency values according the sequence of the predefined values by pressing the  button, which opens one of the windows shown below. Values that are not in the predefined lists will be shifted to the end of the list.

 

 

Continue with:

Jan 14, 2025

Edit Project Move Trees

Editing the project - Move or copy descriptor trees

Using the context menue, you may move or copy parts of a descriptor tree to other branches. Please note that for the move and copy operations the selected project, marked by its background colour in the descriptor tree, is assumed as the target project. You may copy descriptor trees or parts of projects with read-only access to your selected project. The move operation is certainly not possible in those cases. Note that by the copy operations only the tree structures will be copied, associated recommended statistical measures, modifiers and frequencies will not be copied! The move operations preserve those adjustments.

Remark: If you want to move or copy element from an other than the selected project, activate the “Show all projects” option by clicking the button in the tool strip. The icon background will be changed to red color to indicate that this option is active.

1. Move or copy a descriptor tree

Right click on the descriptor tree you want to move/copy. A context menu opens, that offers the options Copy ‘<tree name>’ to ‘<project name>’ rsp. Move ‘<tree name>’ to ‘project name’ (see picture below left). If you selected “Move”, the descriptor tree is removed from the original project and appended to your selected project. If you selected “Copy”, a copy of the tree will be appended to the selected project. In this case numeric IDs are appended to generate unique tree and tree node names (see picture below right). The copy function can be used to generate a clone of a descriptor tree in the selected project.

  

Additionally you may copy the contents of a descriptor tree to a descriptor tree node by clicking selecting the option Copy descriptor tree to descriptor tree node … rsp. Move descriptor tree to descriptor tree node … (see picture above left). A separate window opens to select the target node (see picture below left). Find the move result in the right picture below. Since the tree has been moved, the tree node names have not been changed. One duplicate descriptor has not been moved to the target node. 

   

2. Move or copy a descriptor tree node

Right click on the descriptor tree node you want to move/copy. A context menu opens, that offers the options Copy descriptor tree node … rsp. Move descriptor tree node … (see picture below left). After selecting one of there items a dialog windows opens where you may select the target descriptor tree or descriptor tree node (see picture below right).

   

If you selected “Move”, the descriptor tree node is removed from the original position and appended to the selected tree position. If you selected “Copy”, a copy of the tree node will be appended to the selected tree position. In this case numeric IDs are appended to generate unique tree node names (see picture below). The copy function can also be used to generate a clone of a descriptor tree node in the selected project.

3. Move or copy a descriptor

Right click on the descriptor you want to move/copy. A context menu opens, that offers the options Copy descriptor … rsp. Move descriptor … (see picture below left). After selecting one of there items a dialog windows opens where you may select the target descriptor tree or descriptor tree node (see picture below right).

 

If you selected “Move”, the descriptor is removed from the original position and appended to the selected tree position. If you selected “Copy”, a new descriptor node will be appended to the selected tree position (see picture below).

 

Continue with:

Jan 14, 2025

Edit Project Trees

Editing the project - Descriptor tree tab

The Descriptor tree tab provides the possibility for a structured assignment of the descriptors to the projects. The Descriptor tree consists of three node types, which show the administered projects, descriptor trees, descriptor tree nodes and descriptors. The tree parts’ colours are shown in the example at the bottom. By pressing the button on the tool strip at the right side the example may be hidden. The buttons displayed on the too strip will change depending on the selected entry.

By default only the selected project. its subordinated projects and their descriptor trees are displayed. You may select the “Show all projects” option by clicking the button in the tool strip to show alle projects. To indicate that this option is active, the icon background will be changed to red color (see images below). Be aware that this option might slow down data loading.

The descriptor trees support three main functions:

  • Assignment of descriptors to a certain project
  • Selection of recommended Frequency/Modifier values and Statistical measures for a certain descriptor
  • Structured arragement of the descriptors, e.g. for hierarchical selection lists and definition of descriptor subsets for description editing and export

Descriptor trees are the root of a tree and may only be appended at a project. To insert a new descriptor tree select a project and press , to delete it select the descriptor tree and press . Descriptor tree nodes may be appended at a descriptor tree or another descriptor tree node. To insert a new descriptor tree node, select the parent and press , to remove it select the descriptor tree node and press . Descriptors may be appended to a descriptor tree or a descriptor tree node. To append a descriptor select the parent and press , to remove it select the descriptor and press . All these functions can alternatively be accessed by the context menu by a right click on the entry. The descriptor type is indicated by different icons. Categorical descriptors are marked as , quantitative descriptors as , text descriptors as and sequence descriptors as .

You may change the name of a Descriptor tree or a Descriptor tree node in three different ways:

  1. Select the tree element (single click) and then click once on it.
  2. Select the tree element (single click) and click on button in the tool bar on the right.
  3. Right-click the tree element and select item Edit name from the context menu.

You may edit the name of the selected node within the tree. The Descriptor tree must be globally unique. The Descriptor tree node names must be unique with respect to their tree position, i.e. all nodes with the same parent within a descriptor tree must have distinguished names.

If projects and their associated descriptor trees cannot be changed, because the project has been set to “read-only” state, these parts are displayed with grey text color (see project “Schmetterlinge” in picture above).

When a new descriptor tree or descriptor tree node is inserted it gets a numeric name, which may be changed by clicking on the node or selecting from the context menu. Take care that the names of the discriptor trees must be unambiguous within the whole database! The names of the descriptor tree nodes must only be unambiguous within one parent.

If no descriptor tree is installed for a certain project, all descriptors, modifier/frequency values and statistical measures will be usable in the project’s descriptions. Anyway, if you export data or generate documents an do not have an appropriate descriptor tree, you might have missing data! If a project contains several descriptor trees, the available descriptors are the superset of the descriptors assigned to all contained trees.

 

Editing the project descriptor assignemnts for a tree node 

When you use button to append a descriptor to a tree node, you will be offered all accessible descriptors in the database. In many cases, when you have already assigned all required descriptors to the project, you may wish to build some additional structured descriptor trees. If you select a descriptor tree or a descriptor tree node, the button is shown (see image below left). After clicking this button you will get a selection list with all descriptors assigned to the project. Descriptors that are included in the tree node are selected in the list (see image below right). You may easily change the selection and click “OK” to make the changes effective.

 

Sorting of descriptor tree elements 

By pressing the button you can expand the tree view to display all elements, by pressing the tree will be collapsed to descriptor tree level. With the arrow buttons ( rsp. ) you can move descriptors or descriptor tree nodes up or down rsp. to the top or the bottom. An additional ordering option is to select the descriptor tree node you want to move and click the button. The button’s back color changes to red and you may now select the new position in the tree. If you select a descriptor tree or a descriptor tree node, you may arrange the contained descriptors in alphabedical order by clicking the buttons (ascending) or (descending).

A descriptor tree may be marked as “tree complete” to indicate that this tree shall contain all descriptors for the project. This is done by selecting the descriptor tree node and clicking the button . To indicate that the tree is marked as complete the tree icon changes to (see picture below). 

The “tree complete” flag may be removed by clicking the button and the tree icon will be changed back to (see picture below).

  

If a descriptor tree is marked as “tree complete”, it can be used to take over the sorting of the descriptor nodes to the sequence number of the descriptors. But you must be aware that the descriptor’s sequence number (field “No.” in “Edit descriptor” main panel) is not project or tree dependent, i.e. that this operations will have influence on the dispolay sequence of all descriptions using these descriptors. Click on button (see picture above) to open the descriptor sorting window below.

The first column shows the descriptor names as sorted in the descriptor tree, the second column shows the current sequence number int the database and the last column shows the new sequence number. If the sequence number stays unchanged, the new sequence number is displayed with green background, otherewise with yellow background. You may click on a new sequence number and change its value manually. By clicking on the table headers, you may sort the table display according descriptor names, old or new sequence numbers. If a descriptor may not be changed, because it is assigned to a project where the user has no write access, the whole line is displayed with grey backgound and cannot be changed. Finally click on OK to accept or Cancel to reject the changes. 

An additional option available for complete trees is to copy missing descriptors with button . The descriptors available for a certain project include all descriptors assigned to all descriptor trees of the project and its sub-projects. In our example a new descriptor tree has been assigned to the upmost project (see image below left). After clicking the button all valid descriptors are inserted to the descriptor tree (see image below right). 

 

 

Descriptor tree node details  

For Descriptor tree nodes you may enter an abbreviation a details text and assign resource data. Select the Descriptor tree node (single click) and click on button in the tool bar on the right. Alternatively you may right-click the Descriptor tree node and select Edit details from the context menu. An edit window as shown below will be opened.

If resources are assigned to a Descriptor tree node, its symbol is shown with grey background in the descriptor tree. You may view the resources by right-clicking it and selecting View resources from the context menu.  

 

Click on in the tool bar to close the edit window in the right part of the tab or on  to reopen it. In the edit window you can select recommended modifier/frequency values and statistical measures. The recommended values can be administered for a selected descriptor or for a selected descriptor tree node. In the latter case selected values are inherited by all subordinate nodes, which will be indicated by the background colour if a subordinate node is selected in the descriptor tree.  

To define the available modifier and frequency values and their display sequence, refer to the Modifier/Frequency tab. The statistical measure values are predefined, nevertheless their display sequence may be modified using the  button (see image above). A form as shown below will appear. With the arrow buttons ( ) you can move the selected entries up or down within the table, clicking button or shifts the selected entries to the top respective bottom of the table. After ordering the entries click button to renumber the table entries (starting with “1” for the first table entry) and make the changes effective.  

The picture below shows an example for a descriptor where the recommended statistical measures Mini mum value, Maximum value and Mean are inherited by the superior node. 

For the contained descriptor only additional values may be selected, but the inherited values cannot be de-selected.

 

Continue with:

Jan 14, 2025

Edit Sample Data Grid

Sample data grid view

After starting a database query for descriptions select Grid → Sample data grid view … from the menu. The query result list is passed to the description grid view form and a window as shown below opens. In the first line the database name is displayed. If you move the mouse cursor over the database name, a tooltip shows the actual connection paramter.

img/DD_Description_Main

The table in the lower parThe table in the lower part of the window shows the sampling unit IDs in the first column and the sample data in the other columns. Each sample column holds the data of a certain descriptor. The upper part of the window shows the selection parameters that are used for building the sampling unit table. You may change the table colors by clicking the button . A form as shown below will be opened. 

Click on buttons categorical, quanitative, text or sequence to select the corresponding table colors. By clicking the Reset button below the color, the corresponding default value will be selected. After changing the table colors by a click on the OK button, you must re-draw the table.

 

Selection parameters

In the upper left part of the parameters for the samping unit table can be adjusted. If in the query list passed to the form descriptions of different projects are present, the displayed project can be selected with the Project drop-down box. The entries in the drow-down list include the project name, followed by the number of descriptions for that project in brackets and an asterisk (*) if the user has only read access for that project.

After selecing a project in section Descriptions and sampling events (right upper part of the window) the descriptions and their sampling events are listed. Here you may select the descriptions and sampling events that shall be used for building the sampling unit table. The buttons all, none and swap can be used to change the selection of all tree elements. By pressing the button the tree view may be expanded to display the contained sampling events, by pressing the button only the descriptions will be shown. In the bottom of the section the currently selected number of sampling events and sampling units is displayed.

When you click on a single sampling event and more than one description is in the list, the button appears in the tool strip. By clicking this button you can open a description selection window and thus shift the sampling event to a different parent description. 

The Descriptor tree drop-down box restricts the descriptor columns to the descriptors contained in the selected tree. Furthermore the tree hierarchy is included in the descriptor names if a structured descriptor tree is selected (see images below).

  

The values From descriptor and to descriptor limit the range of descriptor sequence numbers that is included in the discription tabe. Be aware that this restiction is additionally effective to a selected desriptor tree! If you want to de-activate this restriction, select “from” value 0 “to” value 999999 by a double-click on the labels From descriptor rsp. to descriptor. The limitation of the number of descriptor columns makes speeds up the description table generation, especally if many descriptor (e.g. some hundrets) are present.

Finally click the button Display sampling units table to build a new sampling unit table according to your settings. During output of the sampling unit table the icon of the button changes to  and you may abort processing by clicking the button.

 

Continue with:

Jan 14, 2025

Subsections of Edit Sample Data Grid

Edit Sample Data Grid Editing

Sample data grid view - Data editing

The first column of the sampling unit table shows the sampling unit IDs titles, which are fixed. I.e. if you scroll the sample data to the right, the IDs are still visible at the left. The other columns show the sample data, where the descriptor type is indicated by the background colour: categorical, quantitative, text or sequence. The column titles include the descriptor name, the mesurement unit in square bracket for quantitative descriptors and the descriptor’s sequence number (see image below).

When a sample cell in the sampling unit table is selected, the field Sampl. event: shows the sampling event titles, field Description: shows the description title and field Descriptor: shows the symbols according the descriptor type ( for categorical, for quantitative, for text and for sequence) and the descriptor title. If for a descriptor resources are available, this fact is indicated by a coloured symbol background. You may view them by a double-click on the descriptor title. If for a description resources are available, the symbol is displayed before the title. Double click in that symbol to view the resources.

For the selected cell the sample data may be edited as described in section Editing the description - Sample data tab of this manual. For modified sample cells the text colour changes to blue and the sample unit IDs will be shown with yellow background in the table.

 

Changing the sampling event

To shift samling units to a different sampling event, select the whole data rows by clicking in the area left from the “Sampling unit ID” column. In the tool strip the set event button appears. After clicking the button a window for selecting the new parent sampling event will be opened (see image below).

 

Copy sampling units

To copy one or more sampling units select the whole data rows by clicking in the area left from the “Sampling unit ID” column. In the tool strip the copy button appears (see image below).

  

After clicking the button the copied line are inserte at the end of the tabel (see image below). 

  

 

Delete sampling units

To delete one or more sampling units select the whole data rows by clicking in the area left from the “Sampling unit ID” column. In the tool strip the copy button appears.

 

New sampling unit

To enter a new sampling, click on button and a new row will be appended. After clicking the button a window for selecting the sampling event will be opened.

  

 

Continue with:

Jan 14, 2025

Edit Sample Data Grid Save

Sample data grid view - Save or discard changes

When you click in button “OK” the sample data grig view is closed and all changes are automatically saved in the database. If you did some changes and want to save them without leaving the form, simply click on (see image below). If you close the window, e.g. by clicking the “Cancel” button, and still have unsaved changes, you will be asked to save or discard the changes.

img/DD_Description_Main

 

Undo all changes

You may discard all unsaved changes without leaving the form by clicking the button and the data will be reloaded form the database (see image below). 

  

 

May 3, 2024

Table Editors

Table editors

For the data selected in the main window the table editors offer a direct access to the tables of the database. Underneath the menu Grid  select one of the Table editors. A window with the content of the table will open. Columns with a gray background can not be edited here. Columns with a light gray background are linked to the contents of lookup tables where you can change according to the contents of these tables. The following tables are included for direct access:

Depending on the edit mode the following options are available in the Table editors menue:

  • Edit descriptions
    • Sampling events to edit the sampling events of the descriptions in the query result list
    • Descriptions to edit the descriptions in the query result list
    • Description resources to edit the resource entries for the descriptions in the query result list
    • Resource variants to edit the resource variant entries for the descriptions in the query result list
    • Translations to edit the translation entries for the descriptions in the query result list
  • Edit descriptors:
    • Descriptors to edit the descriptors in the query result list
    • Descriptor resources to edit the resource entries for the descriptors in the query result list
    • Categorical states to edit the categorical states of the descriptors in the query result list
    • Categorical state resources to edit the resource entries for the categorical states of the descriptors in the query result list
    • Resource variants to edit the resource variant entries for the descriptors and categorical states in the query result list
    • Translations to edit the translation entries for the descriptors and categorical states in the query result list
  • Edit projects
    • Project to edit the projects in the query result list
    • Descriptor tree node resources to edit the resource entries for the descriptor tree nodes of the projects in the query result list
    • Resource variants to edit the resource variant entries for the descriptor tree nodes of the projects in the query result list
    • Translations to edit the translation entries for the projects in the query result list

 

As an example see below the table editor window for projects.

 

Read-only

If for parts of the query result no write access exists, the table editor will be opened in read-only mode. Especially for descriptors you should keep in mind that they may belong to more than one project. Therefore the table editors for descriptors, categorical states and their resources or resource variants may be opened for read-only, if you have not write permissions for all projects in the database. 

 

Editing

You can either edit the contents of the table directly or perform changes to any number of marked fields. To mark a whole column use the  button. Once you have selected the contents to change, select one of the modes of change that appear in the upper left corner. The modes of change are:

  • Insert: Insert the given value at the beginning of the content
  • Append: Append the given value at the end of the content
  • Replace: Replace a string in the content with the given value
  • Clear: Remove the content

After selecting the change mode, enter the text in the field where necessary and click on the corresponding button to perform the changes.

If you want to delete a line in the database, select it by clicking in the space before the line and press the button. Take care that an undo of that action is not possible.

 

Filtering

To filter the content of the table, click in the column that should be used for filtering. Then choose the mode of comparision:

  • = : The content must be exactly like the given value
  • ~ : The content must contain the given value
  • ≠ : The content must be different to the given value

If you want the filtering to be case sensitive, choose the a<>A option. After all parameters are set, click on the button. To undo the filtering, click on the button. This will reset the data to the last saved version. If you want your changes to be saved, click the button before you reset the filtering. If you close the window all changes so far will be saved automatically. If you do not want to save your changes, click on the button to close the window without saving.

 

Export

To export the data as a tab separated text file, click on the button. The file will be automatically saved in the client-folder.  

Jan 14, 2025

Text Editing

Extended text editor

In the most text fields you can open an extended text editor by double-clicking the text field, which provides the following features:

  • Perform basic text formatting
  • Show and convert RTF-like text formatting
  • Insert and view links to HTML pages or Diversity Workbench database entries

 

Text formatting

In the text fields you may use some HTML mark-ups <b>bold</b> <i>italic</i> and <u>underline</u> for text formatting (see image below left). Additionally the tags <br>, <br/> or <br /> may be inserted to indicate a new text line, but the most common way is to press the ENTER key instead. The format tags will have an effect if documents are generated from the database.

   

By double-clicking the text field you can open a separate edit window that shows the text formatting (see image above right). You can easily change the formatting by selecting a text and clicking the buttons B, I or U.

To reload the original text into the edit window click the button. By clicking OK the changes are taken over to the text field, to ignore the changes, click the cancel button.

 

RTF-like text formatting

In some projects RTF-like mark-ups are used to indicate text formatting, e.g. \iitalics\i0{} for italics. If you double-click on the text field you can open the separate edit window and button indicates that RTF-like format mark-ups have been detected (see image below).

<

By clicking the button the edit window will show you the formatted text (see image below left). After clicking OK the text will be stored using the HTML mark-ups, which is the standard for DiversityDescriptions (see image below right).

  

 

You may open an internet browser by clicking the button . After navigating to your target page, click OK to insert the link at the current cursor position. By clicking the drop-down button you can select a Diversity Workbench database and search for a certain database entry (see image below).

After selecting a found entry and clicking OK the database link is inserted at the current cursor position (see image below). 

When the link is clicked either the web browser opens (for regular HTML links) or the Diversity Workbench application to display the databease entry (see image below).

Jun 5, 2024

Import Export

Import / Export

An overview of some options for the import, export and additional file based operations is given in the image below. The import wizard provides a very flexible tool to import data from tab-separated text files, e.g. generated from a foreighn tool or database. With the list export you may generate tab-separated text files from the database. The export and re-import of tab-separated list allows external editing of the data in e.g. spread sheet programs. For this purpose especially the Matrix wizard is very suitable. As an alternative the questionnaires allow editing of data in an HTML form, which can be done with any internet browser. The modified data can be “downloaded” as text files and re-imported into the database. Even new description data may be collected using the questionnaires without the need of a direct database access.

The CSV export provides a direct copy of selected database tables by means of the Microsoft SQL Server. These copies might be used for archiving purposes or if a foreighn application shall be supplied with data.

The most popular genuine formats for storing and exchanging descriptive data are DELTA and SDD, which are both supported for import and export. The structured export additionally allows generation of EML files, that provide metadata as XML and descriptive data as text table. A spin-off of the import and export functions for structured data is the file conversion, which may even be used without any database access. Additionally the SDD and EML structured XML files may be checked for conformance to their XML schemas. 

Finally the cache database is providing descriptive data to external partners, e.g. a webportal. 

Jan 14, 2025

Subsections of Import Export

Cache Database

Cache database

The cache databases for DiversityDescriptions are designed as sources for preformatted data for publication in e.g. public user portals like GBIF. The cache database by default has a name corresponding to the main source database, e.g. DiversityDescriptionsCache and is located on the same server. By itself it is the source for the data in Postgres (Version 10 or above) cache databases located on any Windows or Linux server (see image below). An overview for the basic steps is provided in chapter Basic steps for publication of data via the cachedatabase.

 

 

Generating the cache database

To create a cache database you need to be a system administrator (s. Login administration). The creation of the cache database is described in the chapter Creation of the cachedatabase.

 

Projects

The publication and transfer of the data is always related to a project . Every project has its own database schema containing the data tables etc. The metadata are defined via settings in a DiversityProjects database. The Projects module provides a stable identifier for each Project. The basic address has to be set in the Project module (choose Administration - Stable identifier … in the menu). Please turn to the module DiverisityProjects for further information. The metadata will be transferred into a table in the cache database. For further details see chapter Projects in the cache database.

 

Collections, references, taxonomy and other sources

As well as data from DiversityDescriptions, data from other modules like DiversityCollection containing specimen or observations, DiversityReferences containing citations and DiversityTaxonNames containing the taxonomy, including accepted names and synonyms are transferred into the cache database and may be retrieved from the local server or a linked server. The data of these sources are stored and transferred independent from the project data. For further details see chapter Sources from other modules

 

Jan 14, 2025

Subsections of Cache Database

Cache Database Basic steps

Basic steps for publication of data via the cache database

1 - Create the cache database

To create a cache database as shown in the chapter Creation of thecache databasee you need to be a system administrator (s. Login administration). After this step the cache database should be available and you can create a Postgres database as final target of your data. To grant access to the cache database for other users, see chapter Login administrationof the cache databases.

2 - Create a Postgres database

The final formatting of the data e.g. for publication via webservice are performed in a Postgres database. If no server providing Postgres is available, you may install Postgres on your local machine (see https://www.postgresql.org/ for further information). The creation and administration of a Postgres database is described in chapter Administration of the Postgres cache databasess. To grant access to the Postgres cache database for other users, see chapter Login administration of thecache databases.  

3 - Insert sources for taxonomic names, collection specimen, references etc.

This step is optional and depends upon the availability of a source for e.g. taxonomic names. You may either use sources from your local server or the public available sources provided by tnt.diversityworkbench.de (turn to http://www.snsb.info for further information). The needed settings are described in chapter Sources from othermodules.  

4 - Insert a project

The data published in the cache database are organized according to the projects. Add a project as shown in chapter Projects in the cache database. Check the Mapping of IDs in the source database and make sure that the data within this project are not withheld from publication and that the ranges you want to publish are set properly (see chapter Restrictions for the datatransfer into the cache database).  

5 - Transfer the data

The final transfer of the data is described in chapter Sources forother modules and chapter Transfer of the data.

6 - Publish or export the data

To export the data or prepare them for publication according to the specifications of webservices etc. the data frequently need to be formatted. This is done with packages as described in chapter Administration of the Packages.

 

 

Jan 14, 2025

Cache Database Create

Create the cache database

To create a cache database you need to be a system administrator (s. Login administration). To create the cache database, choose Data → Cache database … from the menu. If so far no cache database exists, you will be asked if a new one should be generated. After the generation of the cache database a window as shown below will open.

Click on the Update button to update the database to the latest version. A window as shown below will open. Click on Start update to execute all the scripts needed for the latest version of the database.

To grant access to the cache database for other users, see chapter Login administration of the cache databases.  

You should now close an re-open the cache database window. During transfer to the cache database the project metadata are read from a local Diversity Projects database, if in DiversityDescriptions the project is linked to it. By default the name of this “project definitions” database is assumed to be “DiversityProjects” and the same postfix as the DiversityDescriptions database. If this assumption is not fulfilled, you will find the button Please check function ProjectsDatabase (see image below).

   

After clicking the button, a message window might inform you about Projects databases you cannot access due to insufficient access rights (see image below).

   

After closing the message window you find all accessible projects database located on the same database server as your DiversityDescriptions database (see image below). In columns “Fitting projects” and “Non fitting projects” you see the number of projects with fitting rsp. not fitting links to the lsited DiversityProjects database. Click on the database you want ti use for the cache transfer. If not fitting projects are present, the button  may be used to see more details.

   

After selecting a database click on button OK.

If there are non fitting links in your projects database, you will find the button Check missing links for ProjectsDatabase (see image below). Click this button to view the details. Afterward you will have get the projects selection window as shown above.

   

You may now continue with the Administration of the Postgres cachedatabases or insert Sources from other modules. Anyway, close and re-open the cache database window before you insert Projects in the cachedatabase.

 

Jan 14, 2025

Cache Database Id Mapping

Mapping of IDs for the data transfer into the cache database

In the Diversity Descriptions database the main tables Description, Descriptor and CategoricalState have a numeric “id” as key, which is set by the MS SQL server when the dataset ist crated. All relations between the tables are set by using these unique values. For various reasons those internal IDs are not seen as suitable for all purposes of the cache database. Therefore a mapping of the internal IDs is performed before the transfer of data to the cache database.

 

Default mapping

The default mapping of the IDs is mainly oriented on the way the states and characters are identified in the widely spread DELTA standard:

  • Descriptors are numbered starting with “1” in ascending order and transferred into the cache database table CacheCharacter. The order is determined by the descriptor parameter “display_order” and the alphabetical order. The original “id” is stored as “CharID” in the target table, the descriptor number as “CID”.
  • CategoricalStates are numbered for each character starting with “1” in ascending order and transferred into the cache database table CacheState. The order is determined by the categorical state parameter “display_order” and the alphabetical order. The original “id” is stored as “StateID” in the target table, the categorical state number as “CS”.
  • Since the categorical state numbers (“CS”) are not unique, each state is identified, e.g. in a description item, by the character and state number (“CID”, “CS”).
  • Descriptions are numbered starting with “1” in ascending order and transferred into the cache database table CacheItem. The order is determined by the alphabetical order. The original “id” is stored as “ItemID” in the target table, the description number as “IID”. As an alternative the “IID” may be derived from the field “alternate_id” of the “Description” table (see following section.

The mapping data are stored related to the project in the tables CacheMappingDescriptor, CacheMappingState and CacheMappingDescription of the original database.  

 

Mapping adjustment

To set the mapping adjustments, click on the  button (see below).

A window as shown below will open.

If no option is selected, the default mapping algorithm described above will be performed for every transfer to the cache database. Any changes, e.g. insertion of a descriptor or re-arrangement of categorical states, will affect the “CID”, “CS” and “IID” of the cache database.

If option Keep fixed IDs after first export is selected, the default mapping algorithm described above will be performed only for the first transfer to the cache database. Any changes, e.g. insertion of a descriptor or re-arrangement of categorical states, will NOT affect the “CID”, “CS” and “IID” of the cache database. New elements will get a number higher than the last one present. If an element is deleted, this will result in “missing” numbers in the cache database. Pure re-arrangements will have no effect.

The last option Take “IID” from “AID” field only affects the description mapping. By default the descriptions are numbered in alphabetical order. If this option is chosen, it is tried to use the field “alternate_id” (“AID” in the GUI) as item number. Preconditions are that the “AID” is a pure number and that the values are unique. If the “AID” is not supplied or an alpha-numeric string or if the number is already occupied, a new ascending value will be set. By using this option a foreign numbering scheme may be used for the cache database. When selecting this option you might want select Re-initialize “IID” fields to build the description mapping at the next cache transfer. 

Jan 14, 2025

Cache Database Infrastructure

Infrastructure for the cache database

For the administration of the data that are published via the cache database, certain tables as shown below are used. These are either placed in the schema dbo or a schema named according to the published project, e.g. Project_Test for a project with the name “Test”. Additionally some basic data are stored in dedicated tables of the main DiversityDescriptions database.

 

Tables in the main database

In the main DiversityDescriptions database there is a number of tables holding the cache database name, information about datawithholding and mapping information of the IDs. This information is needed to restore the cache database in case of loss. For the database diagram take a look at the database section of this manual.  

 

Central tables in the cache database

There are a number of tables placed in the schema dbo that are accessible by all projects.

 

Published project tables

The central published project tables contain the information about the projects that are published together with the target (Postgres) databases and the packages including optional add-ons into which they had been transferred. This information is used to ensure a recovery in case of a loss of the targets.

 

 

Source tables

To access sources from other modules (e.g. DiversityReferences) there are tables for the storage of the principal access to the modules and a number of tables containing the data (depending on the module).

Access tables

These tables contain the principal access like the name of the view defined to access the data. The example below lists the tables defined for the module DiversityReferences, but there are corresponding tables for every module accessed by the cache database. 

Data tables

These tables contain the data provided by the module and therefore depend on the module. The example below lists the tables defined for the module DiversityReferences, but there are corresponding tables for every module accessed by the cache database. Since data from various source databases may be acumulated in the cache database, in general all the data tables include the BaseURL as part of their keys to ensure unambiguousness.  

To access the data in the source database for the module views are generated by the client. The name of these views are composed according to the name of the database and the project to ensure a unique name. Furthermore letters are appended to identify subordinated tables. These are stored in the table “<module>Source” and are used by the client for a transfer of the data from the module database into the tables in the cache database. The example below lists the view names for the module DiversityReferences. In this example the source database “DiversityReferences_Test” and project “DALI” result in the main table name. By appending “_R” the view name for subordinated table “ReferenceRelator” is built. This gives the views References_Test_DALI and References_Test_DALI_R.

 

Project tables in the cache database

These tables contain the data of the projects with every project having its own schema. The tables correspond to the tables in the main database of the module with according the following assignment. In the third columns the views of the cache database are listed to access the DiversityDescriptions data. The view access besides the main tables listed in the second table column and the ID mapping tables. For the summary data (CacheDescription) additionally subordinated tables, e.g. Modifier, are accessed to resolve relations in DiversityDescriptions as simple character strings.

Table in cache database Tables in DiversityDescriptions Views in cache database
CacheCharacter Descriptor ViewCacheCharacter
CacheCharacterTree DescriptorTree ViewCacheCharacterTree
CacheCharacterTreeNode DescriptorTreeNode ViewCacheCharacterTreeNode
CacheDescription CategoricalSummaryData,
QuantitativeSummaryData,
TextDescriptorData,
MolecularSequenceData,
DescriptorStatusData
ViewCacheCategorical,
ViewCacheQuantitative,
ViewCacheText,
ViewCacheSequence,
ViewCacheStatusData
CacheItem Description ViewCacheItem
CacheResource Resource,
ResourceVariant
ViewCacheResourceCharacter,
ViewCacheResourceCharacterTreeNode,
ViewCacheResourceItem,
ViewCacheResourceState
CacheScope DescriptionScope ViewCacheScope
CacheState CategoricalState ViewCacheState,
ViewCacheMeasure
CacheTranslation Translation ViewCacheTranslationCharacter,
ViewCacheTranslationState,
ViewCacheTranslationItem

 

Besides the tables mentioned above, the auxilliary tables ProjectLockedDescriptor and ProjectLockedScope contain the descriptor IDs and scope types that shall be excluded from the transfer to the cache database. The auxilliary tables ProjectPublishedTranslation and ProjectPublishedDescriptorTree contain language codes of translations (columns label, wording and detail of source tables Descriptor, CategoricalState and Description) and the descriptor tree IDs that shall be included in the cache database transfer. Together with the extended query parameter, which are stored in the columns FilterCommand and FilterParameter of the table ProjectPublished, they build the transferrestrictions of the cache database. Finally, in table CacheMetadata some data from the DiversityProjects database are stored.

The main tables CacheItem, CacheCharacter and CacheState have a numeric key (ItemID, CharID and StateID), which is identical to the unique key in the main database. However, in the cache database the main adress attributes are IID, CID and CS. CID and SD are in principle the descriptor and categorical state sequence numbers, where the mapping algorith guarantees unique ascending values. In this adressing schema a single state is identified by the combination of CID and CS.

Additionally in table CacheState the recommended statistical measures of quantitative descriptors are inclueded, where the measure code (e.g. “Min”, “Max” or “Mean”) is inserted in CS. In table CacheDescription, which holds the single descriptor or data status values, the CID and CS are specified for a specific categorical state. For quantitative data in CS the measurement type is identified by the measure code. For text and molecular sequence data CS is supplied with the fixed texts “TE” and “MS”. In case of descriptor status data CS is set NULL. Instead the data status code is inserted in column Status.  

 

Project procedures for the data transfer into the project tables

For every project table there is a set of procedures that transfers the data from the main database into the cache table. The names of these procedures are procPublish + the name of the target table without “Cache” e.g. procPublishCharacter for the transfer of the data into the table CacheCharacter. The first steps of the data transfer perform an update the ID mapping tables in the main database. This is done in the procedures procPublishMappingItem, procPublishCharacter and procPublishState, which call dedicated procedures in the DiversityDescriptions database. As mentioned above, the original IDs (ItemID, CharID and StateID) are stored together resulting mapped IDs (IID, CID and CS) in the cache database tables. To view the mapping information, the views CacheMappingItem, CacheMappingCharacter and CacheMappingState select the appropriate values from the cache tables.

 

List of tables mentioned above

Table ProjectPublished

The projects published via the cache database (Details about the projects are defined in DiversityProjects)

Column Data type Description Nullable
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO
Project nvarchar (255) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects) YES
ProjectURI varchar (255) The URI of the project, e.g. as provided by the module DiversityProjects. YES
FilterCommand varchar (MAX) The SQL command to select description IDs to be transferred to the cache database. YES
FilterDescription nvarchar (MAX) The XML description of the filter command to transferred description IDs. YES
CoordinatePrecision tinyint Optional reduction of the precision of the coordinates within the project YES
LastUpdatedWhen datetime The date of the last update of the project data
Default value: getdate()
YES
LastUpdatedBy nvarchar (50) The user reponsible for the last update.
Default value: suser_sname()
YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES
IncludeInTransfer bit If the project should be included in a schedule based data transfer YES
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferred
Default value: (0)
YES
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6
Default value: '0'
YES
TransferTime time The time when the transfer should be executed
Default value: '00:00:00.00'
YES
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES
TranslationDescription bit If the description item translation should be included in the data transfer
Default value: (1)
NO
TranslationDescriptor bit If the descriptor translation should be included in the data transfer
Default value: (1)
NO
TranslationCategoricalState bit If the categorical state translation should be included in the data transfer
Default value: (1)
NO
OmitLockedDescriptors bit If the locked descriptors and their states shall be omitted in the data transfer
Default value: (0)
NO
ResourceDescription bit If the description item resources should be included in the data transfer
Default value: (0)
NO
ResourceDescriptorTreeNode bit If the descriptor tree node resources should be included in the data transfer
Default value: (0)
NO
ResourceDescriptor bit If the descriptor resources should be included in the data transfer
Default value: (0)
NO
ResourceCategoricalState bit If the categorical state resources should be included in the data transfer
Default value: (0)
NO
ResourceTypeAll bit If all resource types should be included in the data transfer
Default value: (0)
NO
ResourceTypeImage bit If the resource type "image" should be included in the data transfer
Default value: (0)
NO
ResourceTypeColor bit If the resource type "color" should be included in the data transfer
Default value: (0)
NO
ResourceRankingRestriction tinyint The minimum resource ranking (0-10) that should be included in the data transfer
Default value: (0)
NO
ResourceRoleRestriction varchar (255) The resource roles that should be included in the data transfer
Default value: NULL
YES

Table ProjectTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO
LastUpdatedWhen datetime The date of the last update of the project data YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES
IncludeInTransfer bit If the project should be included in a schedule based data transfer
Default value: (1)
YES
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferred
Default value: (0)
YES
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6
Default value: (0)
YES
TransferTime time The time when the transfer should be executed
Default value: '00:00:00.00'
YES
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES
TargetID int The ID of the server, relates to table Target NO

Table ProjectTargetPackage

Packages for projects as documented in the table Package in the Postgres database

Column Data type Description Nullable
ProjectID int Refers to ProjectID in table ProjectTarget NO
TargetID int Referes to TargetID in table ProjectTarget NO
Package nvarchar (50) Package installed for this project target NO

Table ProjectTransfer

The transfers of data of a project

Column Data type Description Nullable
ProjectID int ID of the project, part of PK NO
TransferDate datetime Date of the transfer. Part of PK
Default value: getdate()
NO
ResponsibleUserID int The ID of the user as stored in table UserProxy of the source database, responsible for the transfer
Default value: (-1)
YES
TargetID int If the transfer regards a postgres database, the ID of the target (= Postgres database) as stored in table Target YES
Package nvarchar (50) If the transfer regards a package, the name of the package, otherwise empty YES
Settings nvarchar (MAX) The versions, number of transfered data etc. of the objects concerned by the transfer [format: JSON] YES

Table ReferenceRelator

Column Data type Description Nullable
BaseURL varchar (500) - NO
RefID int - NO
Role nvarchar (3) - NO
Sequence int - NO
Name nvarchar (255) - NO
AgentURI varchar (255) - YES
SortLabel nvarchar (255) - YES
Address nvarchar (1000) - YES
SourceView nvarchar (128) - NO

Table ReferenceTitle

Column Data type Description Nullable
BaseURL varchar (500) - NO
RefType nvarchar (10) - NO
RefID int - NO
ProjectID int - YES
RefDescription_Cache nvarchar (255) - NO
Title nvarchar (4000) - NO
DateYear smallint - YES
DateMonth smallint - YES
DateDay smallint - YES
DateSuppl nvarchar (255) - NO
SourceTitle nvarchar (4000) - NO
SeriesTitle nvarchar (255) - NO
Periodical nvarchar (255) - NO
Volume nvarchar (255) - NO
Issue nvarchar (255) - NO
Pages nvarchar (255) - NO
Publisher nvarchar (255) - NO
PublPlace nvarchar (255) - NO
Edition smallint - YES
DateYear2 smallint - YES
DateMonth2 smallint - YES
DateDay2 smallint - YES
DateSuppl2 nvarchar (255) - NO
ISSN_ISBN nvarchar (18) - NO
Miscellaneous1 nvarchar (255) - NO
Miscellaneous2 nvarchar (255) - NO
Miscellaneous3 nvarchar (255) - NO
UserDef1 nvarchar (4000) - NO
UserDef2 nvarchar (4000) - NO
UserDef3 nvarchar (4000) - NO
UserDef4 nvarchar (4000) - NO
UserDef5 nvarchar (4000) - NO
WebLinks nvarchar (4000) - NO
LinkToPDF nvarchar (4000) - NO
LinkToFullText nvarchar (4000) - NO
RelatedLinks nvarchar (4000) - NO
LinkToImages nvarchar (4000) - NO
SourceRefID int - YES
Language nvarchar (25) - NO
ReplaceWithRefID int - YES
CitationText nvarchar (1000) - NO
CitationFrom nvarchar (255) - NO
LogInsertedWhen smalldatetime -
Default value: getdate()
YES
SourceView nvarchar (128) - NO
ReferenceURI varchar (500) - YES
AuthorsCache varchar (1000) - YES

Table ReferenceTitleSource

Column Data type Description Nullable
SourceView nvarchar (128) the name of the view retrieving the data from the database NO
Source nvarchar (500) - YES
SourceID int - YES
LinkedServerName nvarchar (500) If the source is located on a linked server, the name of the linked server YES
DatabaseName nvarchar (50) The name of the database where the data are taken from YES
Subsets nvarchar (500) Subsets of a source: The names of the tables included in the transfer separted by "|" YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES
IncludeInTransfer bit If the source should be included in a schedule based data transfer YES
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferred
Default value: (0)
YES
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6
Default value: '0'
YES
TransferTime time The time when the transfer should be executed
Default value: '00:00:00.00'
YES
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES
LastUpdatedWhen datetime The date of the last update of the data
Default value: getdate()
YES
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES
Version int -
Default value: (0)
YES

Table ReferenceTitleSourceTarget

The targets of the projects, i.e. the Postgres databases

Column Data type Description Nullable
SourceView nvarchar (128) SourceView as defined in table ReferenceSource NO
Target nvarchar (255) The targets of the projects, i.e. the Postgres databases where the data should be transferred to NO
LastUpdatedWhen datetime The date of the last update of the project data
Default value: getdate()
YES
TransferProtocol nvarchar (MAX) The protocol created during the transfer of the data YES
IncludeInTransfer bit If the project should be included in a schedule based data transfer
Default value: (1)
YES
CompareLogDate bit If the log dates of the transferred data should be compared to decide if data are transferred
Default value: (0)
YES
TransferDays varchar (7) The days the transfer should be done, coded as integer values with Sunday = 0 up to Saturday = 6
Default value: (0)
YES
TransferTime time The time when the transfer should be executed
Default value: '00:00:00.00'
YES
TransferIsExecutedBy nvarchar (500) If any transfer of the data is active YES
TransferErrors nvarchar (MAX) Errors that occurred during the data transfers YES
LastCheckedWhen datetime The date and time when the last check for the need of an update of the content occurred YES

Table ReferenceTitleSourceView

Column Data type Description Nullable
BaseURL varchar (500) - NO
RefID int - NO
SourceView nvarchar (128) The name of the source view of the data NO
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.
Default value: getdate()
YES

Table Target

The postgres databases as targets for the data

Column Data type Description Nullable
TargetID int ID of the target on a postgres server, PK NO
Server nvarchar (255) Name of IP of the Server NO
Port smallint Port for accessing the server NO
DatabaseName nvarchar (255) The name of the database NO

Table CacheCharacter

Character (= descriptors, features) define variables

Column Data type Description Nullable
CharID int Database-internal ID of this record (primary key) NO
CID smallint A positive number defining the sequence in which characters are displayed NO
CharName nvarchar (255) Short label (or name) of character NO
Notes nvarchar (MAX) Additional detail text explaining or commenting on the character definition YES
CharWording nvarchar (255) Optional separate wording for natural language generation (CharName will be used if this is missing)
Default value: NULL
YES
Unit nvarchar (255) A measurement unit (mm, inch, kg, °C, m/s etc.) or dimensionless scaling factor
Default value: NULL
YES
UnitIsPrefix tinyint Set to 1 if the measurement unit precedes the value
Default value: '0'
NO
Subclass nvarchar (255) The four character subclasses of SDD are all combined here in one entity and distinguished by this attribute ("categorical", "quantitative", "text" or "sequence")
Default value: 'categorical'
NO
Mandatory tinyint Is the scoring of this descriptor mandatory (required) in each item?
Default value: '0'
NO
Exclusive tinyint Applicable to categorical charactors only. If usually exclusive = 1, then by default the user interface allows only entering one state. Nevertheless, multiple states in the data are valid.
Default value: '0'
NO
ValuesAreInteger tinyint Set to 1 if the values are integer
Default value: '0'
NO
Reliability tinyint How reliable and consistent are repeated measurements or scorings of the character by different observers and on different objects? (0-10)
Default value: '5'
NO
Availability tinyint How available is the character or concept for identification? (0-10)
Default value: '5'
NO
SequenceType nvarchar (255) Type of molecular sequence, "Nucleotide" or "Protein". The value "Nucleotide" covers RNA and DNA sequences
Default value: 'Nucleotide'
NO
SymbolLength tinyint The number of letters in each symbol. Nucleotides are always codes with 1-letter symbols, but proteins may use 1 or 3-letter codes (e.g. A or Ala for alanine)
Default value: '1'
NO
GapSymbol nvarchar (3) A string identifying the "gap" symbol used in aligned sequences. The gap symbol must always be symbol_length long
Default value: NULL
YES
NumStates smallint A positive number specifying the number of states for this character
Default value: '0'
NO
StateCollection nvarchar (255) Handling of multiple values: OrSet/AndSet: unordered set combined with or/and, OrSeq/AndSeq: ordered sequence combined with or/and, WithSeq: example is “green with brown”, Between: an example is “oval to elliptic”
Default value: 'OrSet'
NO
Order int Display order
Default value: (0)
NO

Table CacheCharacterTree

The descriptor trees

Column Data type Description Nullable
CharTreeID int Database-internal ID of this record (primary key) NO
CharTreeName nvarchar (255) Descriptor tree name NO

Table CacheCharacterTreeNode

The character tree nodes

Column Data type Description Nullable
CharTreeNodeID int Database-internal ID of this record (primary key) NO
CharTreeID int Reference to the character tree to which the node belongs (foreign key) NO
ParentTreeNodeID int Reference to the superior character tree node - NULL if the tree node is on top level (foreign key)
Default value: NULL
YES
CharTreeNodeName nvarchar (255) Character tree node name - NULL if node references a character
Default value: NULL
YES
CID smallint Reference to the character to which the node belongs - NULL if the tree node is no leaf (foreign key)
Default value: NULL
YES
Order int Display order
Default value: (0)
NO

Table CacheDescription

The description data in the database

Column Data type Description Nullable
DescrID int Database-internal ID of this record (primary key) NO
IID int Reference to the description item to which the data belong NO
CID smallint Reference to the character to which the data belong NO
CS varchar (18) Reference to the state to which the data belong. Null if data status is specified
Default value: NULL
YES
Status varchar (16) Data status of the character as 16 letter code. Null if CS is specified
Default value: NULL
YES
Modifier nvarchar (255) Modifier value of description item. Relevant for categorical and quantitative charaters
Default value: NULL
YES
Frequency nvarchar (255) Frequency value of description item. Relevant for categorical charaters
Default value: NULL
YES
X float Numeric value of description item. Relevant for quantitative charaters YES
TXT nvarchar (MAX) Text value of description item. Relevant for text and molecular sequence charaters YES
Notes nvarchar (MAX) Additional text explaining or commenting on the description item. Relevant for all charaters YES

Table CacheItem

The description item in the database

Column Data type Description Nullable
ItemID int Database-internal ID of this record (primary key) NO
IID int A positive number defining the sequence in which items are displayed NO
ItemName nvarchar (255) Short label (or name) of description item NO
Notes nvarchar (MAX) Additional detail text explaining or commenting on the description item definition YES
ItemWording nvarchar (255) Optional separate wording for natural language generation (ItemName will be used if this is missing)
Default value: NULL
YES

Table CacheMetadata

Column Data type Description Nullable
ProjectID int - NO
ProjectTitle nvarchar (400) - YES
ProjectTitleCode nvarchar (254) - YES
StableIdentifier nvarchar (500) - YES
TechnicalContactName nvarchar (254) - YES
TechnicalContactEmail nvarchar (254) - YES
TechnicalContactPhone nvarchar (254) - YES
TechnicalContactAddress nvarchar (254) - YES
ContentContactName nvarchar (254) - YES
ContentContactEmail nvarchar (254) - YES
ContentContactPhone nvarchar (254) - YES
ContentContactAddress nvarchar (254) - YES
OtherProviderUDDI nvarchar (254) - YES
DatasetTitle nvarchar (254) - YES
DatasetDetails nvarchar (MAX) - YES
DatasetCoverage nvarchar (254) - YES
DatasetURI nvarchar (254) - YES
DatasetIconURI nvarchar (254) - YES
DatasetVersionMajor nvarchar (254) - YES
DatasetCreators nvarchar (254) - YES
DatasetContributors nvarchar (254) - YES
DatasetGUID nvarchar (254) - YES
DateCreated nvarchar (254) - YES
DateModified nvarchar (254) - YES
SourceID nvarchar (254) - YES
SourceInstitutionID nvarchar (254) - YES
OwnerOrganizationName nvarchar (254) - YES
OwnerOrganizationAbbrev nvarchar (254) - YES
OwnerContactPerson nvarchar (254) - YES
OwnerContactRole nvarchar (254) - YES
OwnerAddress nvarchar (254) - YES
OwnerTelephone nvarchar (254) - YES
OwnerEmail nvarchar (254) - YES
OwnerURI nvarchar (254) - YES
OwnerLogoURI nvarchar (254) - YES
IPRText nvarchar (254) - YES
IPRDetails nvarchar (254) - YES
IPRURI nvarchar (254) - YES
CopyrightText nvarchar (254) - YES
CopyrightDetails nvarchar (254) - YES
CopyrightURI nvarchar (254) - YES
TermsOfUseText nvarchar (500) - YES
TermsOfUseDetails nvarchar (254) - YES
TermsOfUseURI nvarchar (254) - YES
DisclaimersText nvarchar (254) - YES
DisclaimersDetails nvarchar (254) - YES
DisclaimersURI nvarchar (254) - YES
LicenseText nvarchar (254) - YES
LicensesDetails nvarchar (254) - YES
LicenseURI nvarchar (254) - YES
AcknowledgementsText nvarchar (254) - YES
AcknowledgementsDetails nvarchar (254) - YES
AcknowledgementsURI nvarchar (254) - YES
CitationsText nvarchar (254) - YES
CitationsDetails nvarchar (254) - YES
CitationsURI nvarchar (254) - YES
RecordBasis nvarchar (254) - YES
KindOfUnit nvarchar (254) - YES
HigherTaxonRank nvarchar (254) - YES
TaxonomicGroup nvarchar (254) - YES
BaseURL varchar (254) - YES
RecordURI nvarchar (500) - YES
ProjectLanguageCode nvarchar (3) - YES

Table CacheResource

The available resources

Column Data type Description Nullable
ResourceID int Database-internal ID of this record (primary key) NO
EntityID int Database-internal ID of the referenced record NO
TargetTable nvarchar (255) Name of the target table: "State", "Chararcter", "CharacterTreeNode" or "Item" (primary key) NO
ResourceName nvarchar (255) Short label (or name) of resource NO
Ranking smallint Ranking of the resource; range: 0 to 10
Default value: NULL
YES
Role nvarchar (255) Role of the resource ("unknown"=role not known or not specified; "diagnostic"=optimized for identification; "iconic"=icon/thumbnail, needs text; "normative"=defines a resource object; "primary"=display always, informative without text; "secondary"=display only on request) NO
IPRText nvarchar (255) The license text of the resource
Default value: NULL
YES
IPRURI nvarchar (255) The license URI of the resource
Default value: NULL
YES
MimeType nvarchar (255) The type of the resource as MIME type like "image/jpeg"; color as "color/hexrgb"
Default value: NULL
YES
URL nvarchar (500) The URL of the resource
Default value: NULL
YES
Order int Display order
Default value: (0)
NO

Table CacheScope

The scope of the description

Column Data type Description Nullable
ScopeId int Database-internal ID of this record (primary key) NO
IID int Reference to the description item to which these data belong NO
ScopeType nvarchar (255) Scope type ("GeographicArea", "Citation", "Observation", "Specimen", "TaxonName", "OtherConcept", "Stage", "Part" or "Sex") NO
ScopeName nvarchar (255) Short label (or name) of scope NO
DwbURI nvarchar (500) Reference to DiversityWorkbench component
Default value: NULL
YES

Table CacheState

The states available for characters

Column Data type Description Nullable
StateID int Database-internal ID of this record (primary key) NO
CID smallint Reference to the character to which the state belongs (foreign key) NO
CS varchar (18) A short string identifying the states in relation to its character NO
StateName nvarchar (255) Short label (or name) of state NO
Notes nvarchar (MAX) Additional detail text explaining or commenting on the state definition YES
StateWording nvarchar (255) Optional separate wording for natural language generation (StateName will be used if this is missing)
Default value: NULL
YES
MinValue float Applicable to quantitative characters only; in support of a plausibility check for values. Example: for tree height this could be 0, i.e. only positive values allowed
Default value: '-1e308'
NO
MaxValue float Applicable to quantitative characters only; in support of a plausibility check for values. Example: for tree height this could be 99
Default value: '1e308'
NO
Order int Display order
Default value: (0)
NO

Table CacheTranslation

The available translations

Column Data type Description Nullable
TranslationID int Database-internal ID of this record (primary key) NO
EntityID int Database-internal ID of the referenced record NO
LanguageCode nvarchar (3) Three-character language code of the translation NO
SourceColumn nvarchar (255) Name of the original table column NO
TargetTable nvarchar (255) Name of the target table: “State”, “Character” or “Item” NO
Text nvarchar (MAX) Translated text YES

Table ProjectLockedDescriptor

The descriptors (=characters) that shall not be published

Column Data type Description Nullable
DescriptorID int Database-internal descriptor ID of descriptive data that shall no be published (primary key) NO

Table ProjectLockedScope

The scope types that shall not be published

Column Data type Description Nullable
ScopeType nvarchar (255) Scope types that shall not be pulished (primary key) NO

Table ProjectPublishedDescriptorTree

The descriptor tree IDs that shall be published

Column Data type Description Nullable
DescriptorTreeID int IDs of descriptor trees that shall be published (primary key) NO

Table ProjectPublishedTranslation

The translation languages that shall be published

Column Data type Description Nullable
LanguageCode nvarchar (3) Three-letter language codes of translations that shall be published (primary key) NO
Jan 14, 2025

Cache Database Logins

Cache database - User administration

There are two roles in the cache database with a general access to the data: CacheAdmin (for the administration and transfer of the data) and CacheUser (with read only access). The data in the cache databases are organized in projects. Therefore for every project you find one additional role: CacheAdmin_Project_… with the right to transfer of the corresponding project to the SQL-Server cache database. You find the project specific roles in the SQL-Server cache database, in the Postgres database only CachAdmin and CacheUser are available.

To administrate the logins in the SQL-Server database, go to the Update and Sources tab and click on the button of the cache database to open a window as shown below. To administrate the access for other logins, you have to be a System administator. For further details please see the chapter about the login administration for the main database.

To view the access rights of a selected role click on the button to open a window as shown below.

 

Postgres database

To handle the logins and user groups on the Postgres database server, go to the Update and Sources tab and click on the button of the postgres database. A window as shown below will open, where you can create and delete logins and groups. For the logins you can change their membership in groups and their properties (see below). On the left you find 2 lists, with the upper list containing the logins and the list below with the groups resp. roles. For the logins you can set the general properties as shown below. The login postgres is created with the installation of the database and is the login for the administration of the database including the updates etc. For details about predefined properties like “Is superuser”, please turn to the Postgresdocumentation

In the Membership in groups area you can define the groups in which the login is a member (see below). 

For the groups you can change their membership in other groups and their permissions (see below). 

May 3, 2024

Cache Database Packages

Administration of the Packages

The formatting of the data according to the specifications of webservices etc. is done with packages. There is a growing list of packages provided with the software. For new packages either turn to the developers or create a package of your own. The packages are realised as tables, view, functions etc. reading the data in the tables without any changes to the data. They therefore can be inserted and removed without any effects on the original data. The naming of the objects within a package follow the schema [Name of the package]_… as shown in the images below.

To administrate the packages installed within one project, click on the button (see above). A window as shown below will open listing all available packages.

Click on the button to establish the selected package. To ensure the current version of the package, click on the Update to vers. … button (see below).

A window will open where all the needed scripts will be listed. For packages keeping the data in their own tables like NaviKey it may be necessary to adapt the timeout for database commands. Click on the button and enter an appropriate value. For large amounts of data the value 0 is recommended, which means infinite.

With button you may select locked characters to restrict the exported data for the current package. This option might be useful, if for a certain target, some characters make no sense. E.g. for the NaviKey application information like the “data record revision” is irrelevant. For other targets it may be published, because it is no secret information.    

To remove a package use the button and the button to get information about the package. For some packages the button indicates that modified data may be published by using an Add-On (see below).

A package (e.g. NaviKey) may contain e.g. tables or materialized views. These need an update after the data have been transferred to the Postgres database. Click on the Transfer button to update the package data. A window as shown below will open, listing the transfer steps for the package. Choose the steps that should be transferred and click on the Start transfer button to transfer the data.

After closing the transfer window you may inspect the data provided by the package by click on the button of the package. Some packages or add-ons may install depend schemas in the database. In this case you will get a window to select the schema for display.

A window as shown below will open listing all package related objects. For every object (table, view, column, … ) the description is shown in the lower part of the window.

To export the contents of a package, click on the button. A window as shown below will open listing the main views of the package. You can export the data as XML (creating a directory with one xml file for every view) or as SQLite database (creating a SQLite database containing the tables).

Jan 14, 2025

Cache Database Packages Add On

Administration of the Add-Ons for Packages

For certain packages there are add-ons available to adapt a package to the special specifications of e.g. a project. To add an add-on, click on the button as shown below. A window as shown below will open listing all available add-ons.

A window as shown below will open listing all available add-ons.

Certain add-ons require the selection of an add-on parameter. E.g. the Navikey_Language add-on requires the selection of the published translation language code. In this cases an additional selection window will be shown (see image below). Remark: Selecting the add-on parameter and therefore the installation of the add-on might require that data have been trasferred to the Postgres database before! 

After the add-on has been added, you need to update it to the current version of the add on with a click on the Upd. to vers. … button (see below). A window will open where all the needed scripts will be listed. Some add-ons are exclusive, meaning that no further add-ons can be added and further updates of the package are organized via the add-on as shown below. To remove an add-on you have to remove the package with a click on the button. 

An Add-on defines a version of the package it is compatible with. Add-ons can not be removed as they perform changes in the package. To remove an add-on, remove the package and reinstall it. If a package containing an Add-on needs an update you have to remove the package as well and reinstall it.

With a click on the first button besides the package you can generate a description of all objects in the package (see below).

With a click on the second button besides the add-on you can view its description (see below).

May 3, 2024

Cache Database Postgres

Administration of the Postgres cache databases

To create a Postgres cache database, you must be connected with a server running Postgres  (Version 10 or above). To connect to a server, click on the button and enter the connection parameters. If no cache database has been created so far, you will get a message that no database is available, otherwise you may select the database as shown below.



After entering valid login data to the Postgres server, at least the button will be available (see image below). Click on the button to create a new cache database (see below). You will be asked for the name of the database and a short description.



After the database was created, you have to update the database to the current version. Click on the Update button to open a window listing all needed scripts. To run these scripts just click on the Start update button. After the update the database is ready to take your data. Subsequent updates may become necessary with new versions of the database. To remove the current database from the server, just click on the button.

In the image on the right you see a screenshot from the tool pgAdmin 4 . You may use this tool to inspect your data and administrate the database independent from DiversityDescriptions. Please keep in mind, that any changes you insert on this level may disable your database from being used by DiversityDescriptions as a sink for your cache data. The data are organized in schemas, with public as the default schema. Here you find functions for marking the database as a module of the Diversity Workbench and the version of the database. The tables in this schema are e.g. TaxonSynonymy where the data derived from DiversityTaxonNames are stored and ReferenceTitle where the data derived from DiversityReferences are stored. For every project a separate schema is created (here Project_LIASlight). The project schemas contain 2 functions for the ID of the project and the version. The data are stored in the tables while the packages in their greater part are realized as views and functions extracting and converting the data from the tables according to their requirements. 

If you connect to a Postgres database for the very first time, you must use an account with sufficient rights to create databases, e.g. "postgres". After performing the first database update the role "CacheAdmin" is available, which has sufficient rights for any cache database operation. To create new logins and grant access to the Postgres cache database for other users, see chapter Login administration of the cache databases .
May 3, 2024

Cache Database Postgres Database

Infrastructure for the postgres database

At the PostgreSQL server the tables are either placed in the schema public or a schema named according to the published project. In general the tables in postgres have the same strucure as in the Microsoft SQL cache database, so the transfer to postgres is mainly a pure copy of their contents. Only some data types are subtituted by their equivalents in postgres. Therefore you may refer to the cachedatabase documentation concerning these tables. Some additional tables, views or even schemas and appropriate transfer functions may be introduced by the packages and their add-ons.

In schema public the support functions diversityworkbenchmodule and version provide the module name “DiversityDescriptionsCache” and the postgres database version (e.g. “01.00.01”) as strings to support processing and the database update. In the published project schemas the support functions projectid and version provide the corresponding integer values.   

All schemas, functions, tables and views are owned by role CacheAdmin. The additional role CacheUser grants read access to all elements rsp. execution rights to the support functions.

 

Source tables

The data tables of the source modules (e.g. DiversityReferences) are transfered as copies to the schema public. I.e. the access tables ending with “Source”, “SourceTarget” and “SourceView”, which serve administrative purposes, are omitted. In the example for the module DiversityReferences, shown in the databaseinfrastructure page, only the tables ReferenceTitle and ReferenceRelator are tranferred to postgres.

 

Project tables

The project tables in postgres are simple copies of the cache database tables. They are placed in a schema named according to the published project, e.g. Project_Test for a project with the name “Test”. For details refer to the cache database documentation:

The view ProjectLanguage provides access to the ProjectLanguageCode stored in table CacheMetadata. The view TranlationLanguage provides access to the LanguageCode of available translations stored in table CacheTranslation.  

 

Packages and Add-Ons

The formatting of the data according to the specifications of webservices etc. is done with packages. The packages are realized as tables, views, functions etc. reading the data in the tables without any changes to the data. They therefore can be inserted and removed without any effects on the original data. The naming of the objects within a package follow the schema [Name of the package]_… . Each package provides a database command file to create the required objects. Transfer of data is done by calling dedicated transfer functions.

For certain packages there are add-ons available to adapt a package to the special specifications of e.g. a project. Each add-on provides a database command file to create the required objects. The traditional way of realizing an add-on is to modify some transfer functions of the package. Therefore only one of those add-ons can be installed for a package. A more flexible approach of handling add-ons is to build a dedicated add-on transfer function and store its name in the administration table. For package transfer there a transger step is defined that reads all associated add-ons from the database and calls their transfer functions in a defined order. With this approach insertion of multiple compatible add-ons may be realized.   

 For the administration of packages and add-ons four tables are used in the postgres database:

In table Package each installed package, its version and description are stored. After data transfer to a package transfer date and time are stored there, too. Add-on data like its version are stored in table PackageAddOn. Some add-ons may require a parameter that has to be selected during installation and ist stored in table column Parameter. If the “non-traditional” approach of realizing add-ons using dedicated transfer functions is used, this table provides optional support columns.

The table PackagePublicTable offers support, if a package or add-on needs to provide data in the schema public. A traditional way to realize this feature is to mark the package as “using schema public”. As a consequence the package can only be created in one project of the whole database. When the package is removed, all objects in schemad public with the prefix “[Name of the package]_” are dropped.

An alternative is that a package or add-on inserts the public table name in PackagePublicTable. Furthermore the public table must have a column where the source schema name is included. If the package is removed, all entries of the public table with matching package name and source schema will be deleted. If the public table is empty, the table itself will be dropped. An example is package NaviKey that enters all published schemas in the table NaviKey_Schema. This table is used by the REST service to provide data to the application DiversityNaviKey.  

The table PackageSchema offers support, if a package or add-on needs to provide data in dependent schemas. For example the add-on NaviKey_Translations provides access to all available translated data of the package NaviKey. Therefore for each available language code a dependent schema named [language code]_Project_[Name of the project] (e.g. de_Project_LIASlight for the german translation) is created with views to the data in the master schema. Each dependent schema is inserted in table PackageSchema (and the public table NaviKey_Schema for the REST service). When the package is removed, all dependent schemas will be dropped, too.

 

Available Packages and Add-Ons

Currently the following packages and add-ons are available:

Package Add-On Description
LiasGtm - Tables and views on the data for geographic visualization of LIAS trait data (https://liasgtm.lias.net/gtm.php)
NaviKey - Tables and views on the data for use with identification tool DiversityNaviKey (https://diversityworkbench.net/Portal/DiversityNaviKey)
NaviKey NaviKey_Wording Add on for package NaviKey that provides data for the DiversityNaviKey application (https://diversityworkbench.net/Portal/DiversityNaviKey):
(1) For characters/descriptors, categorical states and description items the wording text is provided instead of the original names.
NaviKey NaviKey_Language Add on for package NaviKey that provides data for the DiversityNaviKey application (https://diversityworkbench.net/Portal/DiversityNaviKey):
(1) For characters/descriptors, categorical states and description items the tranlated texts are provided instead of the original names and notes.
(2) During installation of the add on the target language is selected from the available translations.
(3) For published translations and available tables observe the cache database restrictions.
NaviKey NaviKey_Translations Add on for package NaviKey that provides data for the DiversityNaviKey application (https://diversityworkbench.net/Portal/DiversityNaviKey):
(1) For characters/descriptors, categorical states and description items the tranlated texts are provided instead of the original names.
(2) For each available language a schema is created where the data can be accessed.
(3) The dependent schemas are registered in tables PackageSchema and the public NaviKey_Schema.
(4) For published translations and available tables observethe cache database restrictions.

 

Tables for Packages and Add-Ons

Table Package

Column Data type Description Nullable
Package character varying(50) The name of the package NO
Version integer The version of the package YES
Description text Description of the package YES
URL character varying(500) A link to a website with further informations about the package YES
LogLastTransfer timestamp without time zone - YES

Table PackageAddOn

Column Data type Description Nullable
Package character varying(50) The name of the package NO
AddOn character varying(50) The name of the package add-on NO
Parameter character varying(50) An optional parameter to configure the package add-on YES
Version integer The version of the package add-on YES
TransferFunction character varying(50) An optional transfer function the package add-on; NULL for exclusive packages YES
TransferPriority integer The transfer priority of the package add-on; 0 for exclusive packages YES

Table PackageLockedCharacter

Stores for each schema the CIDs that shall not included in the package.

Column Data type Description Nullable
Package character varying(50) The name of the package NO
CID smallint The CID that shall not be included in the package NO

Table PackagePublicTable

Stores tables in schema public where data of the package are inserted. Data in this table are inserted by the package and/or Add-Ons.

Column Data type Description Nullable
Package character varying(50) The name of the package NO
Table character varying(128) The dependent table name in schema public of the package where data of the package are inserted NO
ControllingSchemaColumn character varying(128) The column name of dependent table where the controling schema name is stored YES

Table PackageSchema

Stores dependent schemas where data of the package are inserted. Data in this table are inserted by the package and/or Add-Ons.

Column Data type Description Nullable
Package character varying(50) The name of the package NO
Schema character varying(128) The dependent schema name of the package where data of the package are inserted NO
Jan 14, 2025

Cache Database Projects

Projects in the cache database

The data transferred into the cache database are always transferred according to a project they belong to. Choose Data → Cache database … from the menu and select the tab Projects. If no projects were added so far the window will appear like shown below.

To add a new project for the transfer into the cache database, click on the Add project button. In the area below a new entry as shown below will appear. The area on the right shows the number of datasets in the project in the source database together with the date of the last update. To ensure the separation of the data between the projects, DiversityDescriptions creates a separate schema for every project named Project_[name of the project] together with needed roles, tables etc..

Before transferring data you have to update the project schema to the latest version, indicated by the appearance of an update button . Click on the button to open a window as shown below. Click on the Start update button to update the schema to the latest version. For adding a project and performing the database update you need to be a system administrator (s. Login administration). 

After the update the database is ready to transfer data into. 

But before starting the cache transfer you should take a look on the ID mapping, data withholding and data restrictions. The first two items are stored in the descriptions database, the latter in the cache database.

With the ID mapping you can determine how description items, descriptors and categorical states shall be identified in the cach database and how changes are handled in subsequent cache transfers. Click on the button to edit the ID mapping behaviour for the data of the project (see below).

If any descriptors are marked with the data status Data withheld, you have the options to exclude the whole description the export, to hide only the marked descriptor data or to export the whole dataset. Click on the button to edit the data withholding behaviour for the data of the project (see below).

Besides the restrictions in the source database, you can set further data restrictions for this transfer. Click on the button and choose the data restrictions for the cache transfer (see below).

To transfer the data you have 3 options as described in the Transfer chapter.

Afterwards the number and date of the transferred data are visible as shown below.

To inspect the transferred data use the View content button. A window as shown below will open where all tables containing the data of the project are listed.

Click on the button to filter the content. A window as shown below will open. Choose the column for the filter, the operator (e.g. = ) and the filter value (see below).

Now click on the button to add the filter criteria to the table filter. You may add as many criteria as needed (see below). With the button you can clear the filter..

Before you can transfer the data into the Postgresdatabase, you have to connect to the Postgres database and click on the button to establish the project and run necessary updates . After the project is established and up to date, use the button to transfer the data in the Postgres area (see below).

If a project is exported into another Postgres database on the same server, these databases will be listed underneath the Postgres block (see image below). For an overview of all target Postgres databases click on the button.

If the target is placed on the current server, the text will appear in black instead of grey (see below). Packages, if administered, will be listed in the table as well.

In some cases, when a cache database has been deleted on the current Postgres server, there might still be some administrative information left. In this case the target is shown in red and you have the option to delete the administrative data for that target (see below).

In the Postgres database you can install packages to adapt the data to any needed format.

 

 

 

 

 

Jan 14, 2025

Cache Database Restrictions

Restrictions for the data transfer into the cache database

The restrictions of the published data are defined in the main database via projects and data withholding . In the cache database further restrictions can be set for every project. You may set a filter on description data to restrict the Descriptions, select the Descriptors, the Scopes and the Translations that are transferred.

To set the restrictions, click on the  button (see below).

A window as shown in the following sections will open.

 

Descriptions tab

The Descriptions filter works the same way as the Extended query. Use buttons Add description, Add scope or Add descriptor to insert filter items for description, scope or descriptor criteria and set the filter conditions. With button Remove filter item you may remove the currently selected filter item. In the lower right corner Matches: shows you the current count of description items that match the adjusted filter criteria. In the lower center part the resulting SQL filter is shown.

 

Descriptors tab

With the Descriptors filter you can select the descriptors for which summary data shall be transferred. Use button the arrow buttons  << ,   <  ,   >   and  >>  for moving the entries between the Not published and Published list. Click button Transfer existing to move all descriptors that are used within the database to the Published list. With button Transfer from tree you may move all descriptors connected to the selected Descriptor tree to the Published list. Option Show sequence numbers includes the descriptor sequence numbers in the lists. If you do not only want to suppress the descriptive data but also want to hide the descriptors and their state from the cache database, select the option Omit descriptors.

Note: With this option you may keep the selected descriptors completely away from the cache database. If you want to suppress certain descriptors only for selected targets, there is an additional possibility to control the export based on the Packages (refer to “locked characters”).

 

Scopes tab

With the Scope filter you can select the scope type for description scopes that shall be transferred. Use button the arrow buttons  << ,   <  ,   >   and  >>  for moving the entries between the Not published and Published list. Click button Transfer existing to move all scope types that are used within the database to the Published list.

 

Translations tab

With the Translation filter you can select the translation languages for description items, descriptors and categorical states that shall be transferred. Use button the arrow buttons  << ,   <  ,   >   and  >>  for moving the entries between the Not published and Published list. Click button Transfer existing to move all translation languages that are present within the database to the Published list. Use the check boxes Descriptions, Descriptors and States to select the tables where translations shall be published. By default, i.e. without explicit adjustment no tranlations will be transferred to the cache database.

 

Descriptor trees tab

With the Descriptor tee filter you can select the descriptor trees that shall be transferred. Use button the arrow buttons  << ,   <  ,   >   and  >>  for moving the entries between the Not published and Published list. By default, i.e. without explicit adjustment no descriptor trees will be transferred to the cache database.

 

Resources tab

With the Resources filter you can select the resource links that shall be transferred. You have to select at least the Entity types and the Resource types that shall be published. By default, i.e. without explicit adjustment no resources will be transferred to the cache database.

If you select Publish all from section Resource types, all available resources that either are URLs (starting with “http://” or “https://”) or color codes (starting with “color://#”) are included in the transfer. This general restriction ignores resources that are located on your local machine and therefore not generally reachable. If you select the explicit types Images or Colors, the resource variant types must be set correctly, e.g. “image/jpeg”. This can be done for an individual resource in the corresponding edit panel by retrieving the media data from the source. A more comfortable way to get those data for a large amount of resources is to use the database maintenance tool.

With the check boxes Restrict role you may select role values that shall be transferred. With Restrict ranking you may select the minimum ranking value of published resources. If you select the value “0”, the ranking values will be ignored, i.e. even unranked resources will be published.   

Jan 14, 2025

Cache Database Sources

Sources from other modules

To provide details from other modules like DiversityTaxonNames, DiversityCollection, DiversityReferences etc. in the cached data, this information is transferred into the cache database together with the data from DiversityDescriptions database. Use the button to add a source for the data you need. You may include data from a local or a linked database. The data for the cache database are provided via views that will be created for you. With the button you can list the sources used in the projects to get a hint of what may be needed. The tables and view for the sources are placed in the schema dbo in the SQL-Server cache database and public in the Postgres cache databases. In case a new version for the source is available you get a notation like  Needs recreation to version 2 . In this case you must remove the source with a click on the button and use the button to recreate the source. For the inclusion of sources from services like Catalogue of Life see the chapter Sources from webservices.

 

Subsets

The sources of some module provide additional subsets to the main data. To select the subsets that should be transferred to the cache database, click on the button. In the upcoming dialog (see the example for DiversityTaxonNames below) select those subsets you want to transfer in addition to the basic name list.

 

Transfer

Single manual transfer

To transfer the data of a single source into the ** ** cache database use the button and the buttons to inspect the content.

To transfer the data into the Postgres database, you have to connect with a database first. Use the button to transfer the data from the ** ** cache database into the  Postgres database. The button will transfer the data of all sources in the list into the cache database (see below).

 

Scheduled transfer

To transfer the data of all sources into the ** ** cache database and all available Postgres databases, use the scheduled transfer as backgroundprocess. With this transfer all available Postgres databases will be included in the data transfer. These targets are indicated underneath the Postgres block (see image below).

If the target is placed on the current server, the text will appear in black as shown below.

 

Removal

With the button you can remove the sources together with the views (see above).

 

Orphaned data

In some cases, e.g. if a datasource is removed from the ** ** cache database and there is no active connection to the Postgres database, the corresponding data will stay in the postgres database. These orphaned data might disturb subsequent data transfers, if they overlap with the remaining data. Their source view and number of datasets are shown in section “Source views not present in the SQL-Server database” (see below). Click on button to delete the orphaned data. 

 

 

 

Jan 14, 2025

Cache Database Transfer

Transfer of the data

To transfer the data you have 3 options:

  • Single transfer : Transfer data of a single project
  • Bulk transfer : Transfer data of all projects and sources selected for the schedule based transfer

With the resp. button you can decide if the data should be checked for updates. If this option is active ( ) the program will compare the contents and decide if a transfer is needed. If a transfer is needed, this will be indicated with a red border of the transfer button . If you transferred only a part of the data this will be indicated by a thin red border for the current session . The context menu of the button View differences will show the accession numbers of the datasets with changes after the last transfer (see below).

Competing transfer

If a competing transfer is active for the same step, this will be indicated as shown below. While this transfer is active, any further transfer for this step will be blocked.

If this competing transfer is due to e.g. a crash and is not active any more, you have to get rid of the block to preceed with the transfer of the date. To do so you have to reset the status of the transfer. Check the scheduler as shown below. This will activate the button.

Now click on the button to open the window for setting the scheduler options as shown below.

To finally remove the block by the Active transfer, click on the button. This will remove the block and you can preceed with the transfer of the data.

 

Single transfer

To transfer the data for a certain project, click on the button in the Cache- or Postgres data range (see below).

A window as shown below will open, where all data ranges for the transfer will be listed. With the  button you can set the timeout for the transfer of the data where 0 means infinite and is recommended for large amounts of data. With the button you can switch on resp. of the generation of a report. Click on the Start transfer button to start the transfer.

After the data are transferred, the number and data are visible as shown below.

After the data are transferred successful transfers as indicated by an error by . The reason for the failure is shown if you click on the button. For the transfer to the Postgres database the number in the source and the target will be listed as shown below indicating deviating numbers of the data. For the detection of certain errors it may help to activate the logging as described in the chapter TransferSettings. To inspect the first 100 lines of the transferred data click on the button.

 

Bulk transfer

To transfer the data for all projects selected for the schedule based transfer, click on the button in the cache- or Postgres data range (see below).  

 DiversityDescriptions_local  DiversityDescriptionsCache_local DiversityDescriptionsCache_2 on 127.0.0.1, 5555 as postgres

Together with the transfer of the data, reports will be generated and stored in the reports directory. Click on the button in the Timer area to open this directory. To inspect data in the default schemas (dbo for SQL-Server and public for Postgres ) outside the project schemata, use the buttons shown in the image above.

 

Transfer as background process

Transfer data from database to cache database and all Postgres databases

To transfer the data as a background process use the following arguments:

  • CacheTransfer
  • Server of the SQL-server database
  • Port of SQL-server
  • Database with the source data
  • Server for Postgres cache database
  • Port for Postgres server
  • Name of the Postgres cache database
  • Name of Postgres user
  • Password of Postgres user

For example:

C:\DiversityWorkbench\DiversityDescriptions> DiversityDescriptions.exe CacheTransfer snsb.diversityworkbench.de 5432 DiversityDescriptions 127.0.0.1 5555 DiversityDescriptionsCache PostgresUser myPostgresPassword

The application will transfer the data according to the settings, generate a protocol as described above and quit automatically after the transfer of the data. The user starting the process needs a Windows authentication with access to the SQL-Server database and proper rights to transfer the data. The sources and projects within DiversityCollection will be transferred according to the settings (inclusion, filter, days and time). The transfer will be documented in report files. Click on the button to access these files. For a simulation of this transfer click on the Transfer all data according to the settings  button at the top of the form. This will ignore the time restrictions as defined in the settings and will start an immediate transfer of all selected data.

To generate transfer reports and document every step performed by the software during the transfer of the data use a different first argument:

  • CacheTransferWithLogging

C:\DiversityWorkbench\DiversityDescriptions> DiversityDescriptions.exe CacheTransferWithLogging snsb.diversityworkbench.de 5432 DiversityDescriptions 127.0.0.1 5555 DiversityDescriptionsCache PostgresUser myPostgresPassword

To transfer only the data from the main database into the cache database use a different first argument:

  • CacheTransferCacheDB

To transfer only the data from the cache database into the postgres database use a different first argument:

  • CacheTransferPostgres

The remaining arguments correspond to the list above. The generated report files are located in the directory …/ReportsCacheDB and the single steps are witten into the file DiversityCollectionError.log.

History

For every transfer of the data along the pipeline, the settings (e.g. version of the databases) the number of transferred data and additional information are stored. Click on the  button in the respective part to get a list of all previous transfers together with these data (see below).

 

Jan 14, 2025

Cache Database Transfer Protocol

Protocol of the transfers in the cache database

The protocol of any transfer is written into the error log of the application. To examine the messages of the transfers within the cache database you may for every single step click on the button in the transfer window in case an error occurred. In the main window the protocol for all transfers is shown in the   Protocol  part. Choose Data -> Cache database … from the menu and select the tab Protocol. A window will appear like shown below.

A click on the button Requery protocol (error log) requeries resp. shows the protocol. The option Show lines will show the line numbers of the protocol and the option Restrict to Failure will restrict the output to failures and errors stored in the protocol. By default both options are seleted and the number of lines is restricted to 1000. In case of longer protocols change the number of lines for the output. The button Open as textfile will show the protocol in the default editor of your computer. The button Clear protocol (error log) will clear the protocol.

 

 

 

 

 

May 3, 2024

Cache Database Transfer Settings

Settings for the transfer of the projects in the cache database

To edit the general settings for the transfer, click on the button in the main form. A window as shown below will open. Here you can set the timeout for the transfer in minutes. The value 0 means that no time limit is set and the program should try infinite to transfer the data. Furthermore you can set the parameters for the transfer of the data in chunks. If the amount of data is above a certain threshold, it is faster to divide the data into smaller chunks. The threshold for transfer into the cache database and into the Postgres database can be set as shown below, together with the maximal size of the chunks. To return to the default vales click the button Set default values.

Logging

For the detection of certain errors it may help to log the events of the transfer by activating the logging: . The logging is set per application, not per database. So to detect errors in a transfer started by a scheduler on a server, you have to activate the logging in the application started by the server.

Scheduled transfer

The scheduled transfer is meant to be launched on a server on a regular basis, e.g. once a week, once a day, every hour etc.. The transfer of the data via the scheduled transfer will take place according to the settings. This means the program will check if the next planned time for a data transfer is passed and only than start to transfer the data. To include a source in the schedule, check the selector for the scheduler. To set the time and days scheduled for a transfer, click on the button. A window as shown below will open where you can select the time and the day(s) of the week when the transfer should be executed.

The planned points in time are shown in the form as shown below.

The protocol of the last transfer can be seen as in the window above or if you click on the button. If an error occurred this can be inspected with a click no the button.

If another transfer on the same source has been started, no further transfer will be started. In the program this competing transfer is shown as below.

You can remove this block with a click on the < button. In opening window (see below) click on the button. This will as well remove error messages from previous transfers.

A further option for restriction of the transfers is the comparison of the date when the last transfer has been executed. Click on the button to change it to . In this state the program will compare the dates of the transfers and execute the transfer only if new data are available.

 

 

 

 

 

May 3, 2024

Cache Database Webservices

Sources from webservices

To provide details for datasets linked to webservices like Catalogueof Life etc. in the cached data, this information can be transferred into the cache database together with the data from the DiversityCollection database. Use the button to add the webservice you need.

 

Transfer

To transfer the data of a webservice into the ** ** cache database use the button. A window a shown below will open where you must select all projects related to the webservice you selected. **You must transfer the projects into the  ** cache database before transferring the webservice data! Only entries found within these projects will be transferred.

Use the buttons to inspect the content. Names that are already present will not be transferred again. So if you need these values to be updated you have to remove it (see below) and add it again. Links that refer to lists of names instead of single names will not be inserted. These links will be stored in the Errorlog to enable their inspection.

To transfer the data into the Postgres database, you have to connect with a database first. Use the button to transfer the data from the ** ** cache database into the  Postgres database and the buttons to inspect the content.

 

Removal

With the button you can remove the sources together with the views (see above).

 

Jan 14, 2025

Export

Export

There are several export mechanisms:

Matrix wizard: Export descriptor and description data as tabulator separated text file generate an import schema for the matrix importwizard.

List export: Export data as tabulator-separated text file.

Structured export: Export data as structued data file, e.g. XML according to the SDD schema 1.1 rev 5 or DELTA text file.

Export questionaires: Export description data of a project or from a quey list as HTML forms.

CSV export: Export data in a tab separated format for external analysis.

 

Byte order mark BOM

Exported documents are in general generated with UTF-8 encoding. An option for UTF-8 encoded documents is to include a three-byte long Byte Order Mark (BOM) at the beginning of the document (“magic number”). An advantage of the BOM is that a program that evaluates it, automatically detects UTF-8 as the correct encoding. Especially the import tools of DiversityDescriptions recognize the BOM and are able to adjust the correct encoding.

Unfortunately some older tools and Java do not automatically recognize the BOM, which results in “strange” characters at the beginning of such documents. In DiversityDescriptions generally the export functions for structured documents (e.g. XML and HTML) do not generate a BOM, since those documents include an explicit encoding information field. For the tabulator-separated data document provided with EML, the encoding is specified in the XML-based metadata document, therefore no BOM is inserted here.

For all tabulator-separated text file exports you have the option to omit the BOM. In the upper right corner of the window, besides the button to set the output file, you can find the check button . Keep it checked to generate the output file with BOM (see image below left) or uncheck it to suppress the BOM (image at the right).  

        

Jan 14, 2025

Subsections of Export

Export CSV

Export CSV

Notes:

  • The Export CSV function provides a direct copy of selected database table as tabulator separated text file. If you want to generate flles that give a strutured overview of descriptors or description data, you should prefer the Export … Lists or the Export Wizard (coming soon).
  • The Export CSV function requires the “Bulk Copy” tool, which is part of a local Microsoft SQL Server installation. If it is not available on your computer, you will get an error message after opening the window. Search for the “bcp-utility” to get information about a free download and installation of the “Bulk Copy” tool.

To export the tables of the database in the a tabulator, comma or semicolon separated format, choose Data → Export → Export CSV … from the menu. A window as shown below will open where you can select the tables to be exported in sections Selection criteria and in the Tables for export.

To start the export click on the Start export button. By default the data will be exported into a directory <resources directory>\Export\<database_name>. Click on the button to select a different target directory before starting export.

After export the tables are marked with green backgound, if table schema and data were exported successfully. If only the data were exported, this is marked with yellow background, if nothing was exported, the background is red. A detailled export report can be viewd by a click on the export result file name.  

May 16, 2024

Export Questionnaires

Export questionnaires

With this form you can export description data from the database to HTML forms. You can open the generated HTML files, edit the data in the form and re-import the changes by using the import questionairedata function. Choose Data -> Export → Export questionnaires … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked. You may pass a description list to the form by starting a query in mode “Edit descriptions”. If all descriptions in the list belong to the same project, you have the option to select single descriptions for export. In this case the Export project section shows the button  to switch to the list view (see below).

 

In the Expot descriptions section you find all description titles that have been passed to the export form (see below). You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. By clicking the button you will return to the Export project view.

The Withheld data section allows control over export of datasets that contain entries with data status “Data withheld”. Option Supress whole description (default) excludes all descriptions form export where at least on descriptor is marked with “Data withheld”. Option Hide withheld descriptor excludes only the corresponding descriptor data from the description. Option Export withheld data does not exclude any data from export.

 

Options 

The Options section allows the selection of a Descriptor tree to determine the sequence and selection of descriptors for output. If a structured descriptor tree is selected, the first level descriptor tree nodes will be inserted as headers to structure the document. If option Adapt descriptor names is checked, the descriptor names will be prefixed with the headers from the derscriptor tree. In this case you may specify a string to connect the names in the texrt box at the right of the option. If Generate index page is checked, an alphabetically sorted index with links to the individual description pages will be generated.

You may Hide descriptor status data in the generated forms. Furthermore output of the ordinal numbers for descriptors rsp. categorical states may be suppressed by using the options Hide descriptor numbers rsp. Hide state numbers.  With options Include notes and Include modifier/frequency you can control if notes and modifier or frequency values shall be included in the generated questionaires. With Include details a text field for editing the item details will be inserted.

By default a font type with serifes is used for the HTML output, select Sans serif font for an alternative. The colors of several HTML elements may be adapted to the personal preferences by clicking on button . With Text rows you can adjust the size of text boxex used for text and molecular sequence descriptors. Option Scrollable states generates an alternative layout for categorical descriptors, where the state values are arranged in scroll boxes. 

Check Include resources to include images for descriptions, descriptors, categorical states and descriptor tree nodes in the questionnaire. In the generated HTML questionnaire the images will be zoomed by a dedicated factor, when the mouse cursor is moved over it. The zoom factors may be adjusted by clicking on button . If you check the option Insert fields for new resources, the specified number of input fields for entering new description resources (name and URL) will be inserted in the forms (see image below on the left). 

Check Include scopes to include a section for scope data in the questionnare. The scope values of the types “Sex”, “Stage”, “Part” and “Other scopes”, which may be administered in the Edit project section, are included as check boxes. For the other (general) scope types input boxes will be generated, where new values may be entered or existing values can be edited. If a scope value is linked to a database entry, e.g. of a DiversityTaxonNames database, it cannot be modified. In this case only a fixed text with the reference to the target database will be inserted in the questionnaire.

By clicking on button you may open an option window where you can change this default behaviour. You may adjust for which scope types an input box for a new scope value shall be inserted or if scopes that cannot be modified shall be displayed (see image above on the right).

See below an example of a questionnaire where imput fields for a new description resource and all general scope types are present..

 

If for the selected projects translations are stored in the database, you may chose the Export language. If for any element no translation in the chosen export language is present, automatically the original text will be used. With field Language settings you can control the presentation of floating point values in the output, in field Send answer to you may enter the mail address to return the results. 

 

Test

To check the export, click on the Test export button. In the Output preview section an empty form for entering a new item will be displayed (see picture below). The file name is generated as <resources directory>\Questionnaires\<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. Button opens the form in an external web browser.

Since the generated form can be opened with any modern web broswer, you may distribute it to easily collect item data by people that do not have access to the Diversity Descriptions database. Even if the form is published as a web page, the collected data stay completele local in the user’s web browser and are not uploaded to any server. To get the  data into the database, they must be “downloaded” form the form and sent back to a database editor for import (see item Send reply below).

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Questionaires\<Database name>_<Project>.html. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name text box. During export a number of HTML files will be generated. The document for entering a new item has the specified file name. For entries present in the database the description id is appended. Furthermore an index file with postfix “_Index” will be generated, where you may navigated to each exported questionnaire.

To generate the HTML files press the Start export button. During export the icon of the button changes to  and you may abort processing by clicking the button. Button opens the form visible in the Output preview section in an external web browser (see image above).

 

Send reply

When you opened a HTML form in the web browser and modified data, you may download them as a text file for databaseimport. At the bottom of the HTML form click the button Download revised description (see image below). Data collection is completely done in the user’s local web browser, nothing is uploaded to a server. Since data collection is done using javascript, please take care that the script is not blocked by the web browser.

 

Jan 14, 2025

List Export

List export

There are several exports for tabulator-separated text files:

Export descriptors list: Export descriptor data as tabulator separated text file.

Export descriptions list: Export description data as tabulator separated text file.

Export sample data list: Export sample data as tabulator separated text file.

Export resource data list: Export resource data as tabulator separated text file for data review and possible re-import of modified data.

Export translations list: Export translations as tabulator separated text file for data review and possible re-import of modified data.

 

May 3, 2024

Subsections of List Export

Export Descriptions List

Export Descriptions List

With this form you can export description data from the database to a tabulator separated text file. Choose Data → Export → Export lists -> Descriptions list … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked. You may pass a description list to the form by starting a query in mode “Edit descriptions”. If all descriptions in the list belong to the same project, you have the option to select single descriptions for export. In this case the Export project section shows the button  to switch to the list view (see below).

 

In the Export descriptions section you find all description titles that have been passed to the export form (see below). You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. By clicking the button you will return to the Export project view.

The Withheld data section allows control over export of datasets that contain entries with data status “Data withheld”. Option Supress whole description (default) excludes all descriptions form export where at least on descriptor is marked with “Data withheld”. Option Hide withheld descriptor excludes only the corresponding descriptor data from the description. Option Export withheld data does not exclude any data from export.

The Export settings allows the inclusion of a header line in the output by checking the option Generate headers in output. Additionally the lines displayed in the Test output section may be selected by specifying the first and last line number in Test lines [start] to [end]. For the generated output you may adjust the lines that shall be exported in Exp. lines [start] to [end]. For the end line a maximum value of 99999 may be entered, which means export of the whole data beginning from the start line.

 

Columns

To generate a list output, you have to determine the data columns that shall be present in the descriptions list. To include a new column press the Add button in the tool strip of the Columns section. A control representing a single output column will be added at the end of the column list (see picture below). 

 

The Columns control shows the column number, a text box for the column header (title) and the source selector (see below).

As source you may select one of the following values:

**Line number ** Number of the data line in the output file
Description   Description data, e.g. name of the description entry
Description scope  Description scope data, e.g. taxon, specimen or sex 
Descriptor value  Value(s) of a certain descriptor
Descriptor status   Data status of a certain descriptor 

Depending on the selected data source one or more additional selection boxes will appear in the description column control. The target (see picture below left) selects the field from the database that shall be inserted. If you select “Description scope” as data source, a selection box for filtering will be inserted to determine the scope category (see picture below right).  

 

If you select “Descriptor value” or “Descriptor status” as data source, a selection box for the descriptor will be inserted (see picture below). The descriptor can be selected from an alphabetical list or from the descriptor tree by clicking . In case of “Descriptor value” the target selection box entries depend on the descriptor type. For categorical descriptors you may select “Name”, “Abbreviation”, “Detail”, “Wording”, “ID” or “Notes” of the categorical ssummary data. For quantitative descriptors you may select the “Value” or “Notes” of a specific statistical measure (separate selection box). For text and sequence descriptors you may select the “Text” or “Notes”. 

Categorical descriptors offer an additional special target type called “<Binary columns>”. If you select this value, an additional selection window will appear, where you can select either “<all>” or a specific categorical state. If a specific categorical state is selected, a column will be inserted in the outptu, that contains either “1” if the state is present or “0” otherwise. If you select “<all>”, a column for each categorical state will be inserted that contains the binary presence sign. An examble is shown in the picture below (column 6).  

As long as you did not enter a value for the column header, a reasonable suggestion depending on the selected values will be inserted. You may enter a different column header, then the background color changes to light yellow to indicate that it will not be updated automatically anymore (see picture below, column 3). Double-click on the header to open a separate edit window. 

Output formatting is controlled with check box “quotes” that includes the whole output text in quotes and text boxes Pre: and Post:, which allow inclusion of the values in prefix and postfix strings (default is “). By selecting the check box Skip empty a blank output will be inserted  instead of the specified prefix and postfix strings, if no value is present. If for a column multiple values may be present, e.g. in case of categorical descriptors several categorical states might be present, there is the choice of insterting additional lines for multiple values (Separate line), selecting a single value (Select) or merging the values to a single output string (Merge). For option Select you have specify if the first, second or other values shall be selected. For option Merge you may specify a separator string that shall be inserted between two values (default is ; ). To open a separate edit window for the Pre:, Post: or Merge strings, e.g. because a longer value shall be entered, double-click on the correspondent text box. 

Any selected column may be shifted to another position using the Up and Down buttons or deleted with the Remove button of the tool strip. With button you may delete all columns. The complete export schema may be saved into an XML file using the button , which opens a dialog window to enter the file name and location. By default the schema file name is generated as:

     <resources directory>\ExportSchema\DescriptionList_<Database name>_<Project>.xml 

The XML schema file includes information concerning the database, the project, handling of withheld data and the output columns. By pressing the button in the Columns section, a schema file can be opened. If the schema does not meet the active database, especially descriptor dependent columns might be erroneous because of unknown values. This is indicated by a red background color (see picture below).   

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Export\DescriptionList_<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. If you uncheck the option Generate preview, no output preview will be generated for the export. To generate an output without BOM, release the button. 

To check the export, click on the Test export button. By changing the selected Language settings: you may adapt the output of floating point numbers or date and time fields to your needs. In the Output preview grid view the lines specified in the Export settings (Test lines [start] to [end]) will be displayed (see picture above). To generate the table file press the Start export button. During test and export the icon of the button changes to  and you may abort processing by clicking the button. 

May 16, 2024

Export Descriptors List

Export Descriptors List

With this form you can export descriptor data from the database to an tabulator separated text file. Choose Data → Export → Export lists -> Descriptors list … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked.

The Export settings allows the inclusion of a header line in the output by checking the option Generate headers in output. Additionally the lines displayed in the Test output section may be selected by specifying the first and last line number in Test lines [start] to [end]. For the generated output you may adjust the lines that shall be exported in Exp. lines [start] to [end]. For the end line a maximum value of 99999 may be entered, which means export of the whole data beginning from the start line.

 

Columns

To generate a list output, you have to determine the data columns that shall be present in the descriptors list. To include a new column press the Add button in the tool strip of the Columns section. A control representing a single output column will be added at the end of the column list (see picture below). 

 

The Columns control shows the column number, a text box for the column header (title) and the source selector (see below).

As source you may select one of the following values:

**Line number ** Number of the data line in the output file
Descriptor   Descriptor data, e.g. name of the descriptor
Descriptor tree  Assigned descriptor tree(s)
Categorical state   Categorical state(s) of a certain descriptor 

Depending on the selected data source one or more additional selection boxes will appear in the descriptor column control. The target (see picture below) selects the filed from the database that shall be inserted.  

   

As long as you did not enter a value for the column header, a reasonable suggestion depending on the selected values will be inserted. You may enter a different column header, then the background color changes to light yellow to indicate that it will not be updated automatically anymore (see picture below, column 4). Double-click on the header to open a separate edit window. 

Output formatting is controlled with check box “quotes” that includes the whole output text in quotes and text boxes Pre: and Post:, which allow inclusion of the values in prefix and postfix strings. By selecting the check box Skip empty a blank output will be inserted  instead of the specified prefix and postfix strings or quotes, if no value is present. If for a column multiple values may be present, e.g. in case of categorical descriptors where several categorical states might be present, there is the choice of inserting additional lines for multiple values (Separate line), selecting a single value (Select) or merging the values to a single output string (Merge). For option Select you have specify if the first, second or other values shall be selected. For option Merge you may specify a separator string that shall be inserted between two values (default is ; ). To open a separate edit window for the Pre, Post or Merge values strings, e.g. because a longer value shall be entered, double-click on the correspondent text box. 

Any selected column may be shifted to another position using the Up and Down buttons or deleted with the Remove button of the tool strip. With button you may delete all columns. The complete export schema may be saved into an XML file using the button , which opens a dialog window to enter the file name and location. By default the schema file name is generated as:

     <resources directory>\ExportSchema\DescriptiorList_<Database name>_<Project>.xml 

The XML schema file includes information concerning the database, the project and the output columns. By pressing the button in the Columns section, a schema file can be opened. 

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Export\DescriptorList_<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. If you uncheck the option Generate preview, no output preview will be generated for the export. To generate an output without BOM, release the button. 

To check the export, click on the Test export button. By changing the selected Language settings: you may adapt the output of floating point numbers or date and time fields to your needs. In the Output preview grid view the lines specified in the Export settings (Test lines [start] to [end]) will be displayed (see picture above). To generate the table file press the Start export button. During test and export the icon of the button changes to  and you may abort processing by clicking the button. 

May 16, 2024

Export Resource List

Export resource data list

With this form you can export the resource data (see tables Resource and ResourceVariant) from the database to a tabulator separated text file. Since the output includes the database keys, you may correct the data, e.g. by using a spreadsheet program and re-import the changes by using the importwizard. Choose Data → Export → Export lists -> Resource data list … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked.

The Withheld data section allows control over export of datasets that contain entries with data status “Data withheld”. Option Supress whole description (default) excludes all descriptions form export where at least on descriptor is marked with “Data withheld”. Option Hide withheld descriptor excludes only the corresponding descriptor data from the description. Option Export withheld data does not exclude any data from export.

The Options section allows the selection of the Entity types for output (“Description”, “Descriptor”, “Categorical state” and “Descriptor tree node”). To include all export data in quotes, check option “quotes”. If option Fill all columns is checked, resource variant data that are inherited from the row above will be explicitely repeated in the actual row. To include all data rows that do not have resources select option Show empty entities. If you select Show descriptors, the descriptor titles will be inserted for categorical states. By checking option Show duplicates only you may list resource links that are referenced by more than one entity of the same type.

You may restrict the resource data list to resource links that include a specified substring by selecting the URL filter option and entering the required string in the text field below. 

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Export\ResourceDataList_<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. To generate an output without BOM, release the button. 

To check the export, click on the Test export button. In the Output preview data grid the first few lines will be displayed (see picture above). To generate the table file press the Start export button. During test and export the icon of the button changes to  and you may abort processing by clicking the button. 

 

Re-import

The review output includes all database keys that can be sufficiently used to identify the affected data row. When the modified data shall be re-imported, the internal keys must be available to the import wizard. This can easily be done by creating a new import session and using the option  Generate mapping … in form Import sessions.

Jan 14, 2025

Export Samples List

Export Sample Data List

With this form you can export sample data from the database to a tabulator separated text file. Choose Data → Export → Export lists -> Sample data list … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked.

The Export settings allows the inclusion of a header line in the output by checking the option Generate headers in output. Additionally the lines displayed in the Test output section may be selected by specifying the first and last line number in Test lines [start] to [end]. For the generated output you may adjust the lines that shall be exported in Exp. lines [start] to [end]. For the end line a maximum value of 99999 may be entered, which means export of the whole data beginning from the start line.

 

Columns

To generate a list output, you have to determine the data columns that shall be present in the descriptions list. To include a new column press the Add button in the tool strip of the Columns section. A control representing a single output column will be added at the end of the column list (see picture below). 

 

The Columns control shows the column number, a text box for the column header (title) and the source selector (see below).

As source you may select one of the following values:

**Line number ** Number of the data line in the output file
Description   Description data, e.g. name of the description entry
Sampling event  Sampling event data, e.g. name, detail or start date 
Sampling unit  Sampling unit data, e.g. ID, specimen or specimen URI 
Descriptor value  Sample value(s) of a certain descriptor

Depending on the selected data source one or more additional selection boxes will appear in the description column control. The target (see pictures below) selects the field from the database that shall be inserted..  

 

If you select “Descriptor value” as data source, a selection box for the descriptor will be inserted (see picture below). The descriptor can be selected from an alphabetical list or from the descriptor tree by clicking . The target selection box entries depend on the descriptor type. For categroical descriptors you may select “Name”, “Abbreviation”, “Detail” or “ID” of the categorical sampling data, for quantitative descriptors you may select the “Value” or “Notes”, for text and sequence descriptors you may select the “Text” or “Notes”.   

As long as you did not enter a value for the column header, a reasonable suggestion depending on the selected values will be inserted. You may enter a different column header, then the background color changes to light yellow to indicate that it will not be updated automatically anymore (see picture below, column 3). Double-click on the header to open a separate edit window. 

Output formatting is controlled with check box “quotes” that includes the whole output text in quotes and text boxes Pre: and Post:, which allow inclusion of the values in prefix and postfix strings (default is “). By selecting the check box Skip empty a blank output will be inserted  instead of the specified prefix and postfix strings, if no value is present. If for a column multiple values may be present, e.g. in case of categorical descriptors several categorical states might be present, there is the choice of inserting additional lines for multiple values (Separate line), selecting a single value (Select) or merging the values to a single output string (Merge). For option Select you have specify if the first, second or other values shall be selected. For option Merge you may specify a separator string that shall be inserted between two values (default is ; ). To open a separate edit window for the Pre:, Post: or Merge strings, e.g. because a longer value shall be entered, double-click on the correspondent text box. 

Any selected column may be shifted to another position using the Up and Down buttons or deleted with the Remove button of the tool strip. With button you may delete all columns. The complete export schema may be saved into an XML file using the button and a dialog window will be opened. By default the schema file name is generated as:

     <resources directory>\ExportSchema\SampleDataList_<Database name>_<Project>.xml 

The XML schema file includes information concerning the database, the project, handling of withheld data and the output columns. By pressing the button in the Columns section, a schema file can be opened. If the schema does not meet the active database, especially descriptor dependent columns might be erroneous because of unknown values. This is indicated by a red background color (see picture below).   

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Export\SampleDataList_<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. If you uncheck the option Generate preview, no output preview will be generated for the export. To generate an output without BOM, release the button. 

To check the export, click on the Test export button. By changing the selected Language settings: you may adapt the output of floating point numbers or date and time fields to your needs. In the Output preview grid view the lines specified in the Export settings (Test lines [start] to [end]) will be displayed (see picture above). To generate the table file press the Start export button. During test and export the icon of the button changes to  and you may abort processing by clicking the button. 

May 16, 2024

Export Translation List

Export translations list

With this form you can export the translations (see table Translation) from the database to a tabulator separated text file. Since the output includes the database keys, you may correct the data, e.g. by using a spreadsheet program and re-import the changes by using the importwizard. Choose Data → Export → Export lists -> Translations list … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked.

The Withheld data section allows control over export of datasets that contain entries with data status “Data withheld”. Option Supress whole description (default) excludes all descriptions form export where at least on descriptor is marked with “Data withheld”. Option Hide withheld descriptor excludes only the corresponding descriptor data from the description. Option Export withheld data does not exclude any data from export.

The Options section allows the selection of the Entity types for output (“Description”, “Descriptor” and “Categorical state”). To include all export data in quotes, check option “quotes”. To include all data rows that do not have translations select option Show empty entities. If you select Show descriptors, the descriptor titles will be inserted for categorical states. 

You may restrict the translations list to a certain Language or to a certain data Column by selecting a value in the mentioned combo boxes. The column value “wording” will output the translations of the wording columns for descriptions, descriptors and categorical states. Additionally translations of the columns “wording_before” and “wording_after” for descriptors will be exported. 

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Export\TranslationsList_<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. To generate an output without BOM, release the button. 

To check the export, click on the Test export button. In the Output preview data grid the first few lines will be displayed (see picture above). To generate the table file press the Start export button. During test and export the icon of the button changes to  and you may abort processing by clicking the button. 

 

Re-import

The review output includes all database keys that can be sufficiently used to identify the affected data row. When the modified data shall be re-imported, the internal keys must be available to the import wizard. This can easily be done by creating a new import session and using the option  Generate mapping … in form Import sessions.

Please be aware that table Translation has a numeric key that is not directly accessible for the import wizard. If you want to update an exsisting translation, the correct entry must be identified by the alternate key consisting of “object_id”, “language_code” and “column_id”, which correspond to the generated output table columns “Entity ID”, “Language” and “Column” (see image above). In the import wizard these three columns must therefore be marked as “key columns” (see image below).

If you generate an output for several entity types, e.g. “Descriptor” and “Categorical states” as shown in the example above, you will have to insert a filter condition in the import wizard. E.g. if you want to re-import descriptor translations, select the outptut column “Contents” for the “contents” table column and mark it as decisive column. Insert a filter to output column “State name” for equal “empty” (see image below) to ignore lines with a categorical state.

Jan 14, 2025

Matrix Export Wizard

Matrix export wizard for tab separated lists

With this form you can export the descriptor and description data from the database to a tabulator separated text file. The output includes the database keys. Furthermore you have the option to create rsp. update import mapping data and generate an matrix import schema. Therefore you may correct the data, e.g. by using a spreadsheet program and re-import the changes by using the matrix import wizard. Choose Data → Export -> Matrix wizard … from the menu to open the window for the export.

 

In the Export project section all projects of the database are shown as a tree. Select here the project that shall be exported. In case of hierarchically organized projects the subordinated projects will be included for export, if the Include child projects option is checked. You may pass a description list to the form by starting a query in mode “Edit descriptions”. Now you have the option to select single descriptions for export. In this case the Export project section shows the button  to switch to the list view (see below).

 

In the Export descriptions section you find all description titles that have been passed to the export form (see below). You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. By clicking the button you will return to the Export project view.

The Withheld data section allows control over export of datasets that contain entries with data status “Data withheld”. Option Supress whole description (default) excludes all descriptions form export where at least on descriptor is marked with “Data withheld”. Option Hide withheld descriptor excludes only the corresponding descriptor data from the description. Option Export withheld data does not exclude any data from export.

The Options section allows the selection of the Descriptor tree: and descriptor sequence number bounds (From descriptor: and to descriptor:) for restriction of output table columns.

If you select option Use sequence, the descriptor state sequence numbers will be inserted into the output table instead of the state names. These sequence numbers will be inserted into the selected import session (see below) for a later re-import of the data. If you export the descriptive data to edit them with a spreadsheet tool, e.g. Microsoft Excel, you have to identify the active categorical states by their sequence number. 

To include all exported data in quotes, check option “quotes”. Select Trim end to remove white characters (e.g. blank or word wrap) at the end of texts. By specifying the State separator: (default , ) you determine how multiple categorical state values will be concatenated in the table cells. By changing the selected Lang. settings: you may adapt the output of floating point numbers or date and time fields to your needs.

 

Import session

The section Import session: is relevant if you want to edit the description data in a separate spreadsheet programme and re-import the edited data using the Matrix Import Wizard. To select an import session cick on button Select and a window as shown below will be opened. You may either select an existing import session, which will be updated with the exported data, or create a new one.  

 

During generation of the matrix data file the relevant data for re-import will be stored in the selected import session. Additionally an xml import schema file will be generated as  <resources directory>\Export\Matrix_<Database name>_<Project>_Schema.xml. If you do not require the data for re-import, simply do not select an import session or click on button to cancel an existing selection. 

 

Export

Before starting the export, the export file name should be checked. The file name is generated as <resources directory>\Export\Matrix_<Database name>_<Project>.txt. This default setting may be changed by editing the File name or by navigating at the target location by pressing the button besides the file name. To generate an output without BOM, release the button.  

To check the export, click on the Test export button. In the Output preview data grid the first few lines will be displayed (see picture above). To generate the table file press the Start export button. During test and export the icon of the button changes to  and you may abort processing by clicking the button.

 

Jan 14, 2025

File Operations

File operations

Without any database access data files may be converted in the following directions:

Convert SDD file: Read an XML file according to the SDD schema 1.1 rev 5 and generate DELTA or EML files.

Convert DELTA file: Read DELTA text file(s) and generate SDD or EML files.

Additionally XML file check tools are available:

Check SDD file: Check if a text file is an XML file according to the SDD schema 1.1 rev 5.

Check EML file: Check if a text file is an XML file according to the EML schema 2.1.1.

Jan 14, 2025

Subsections of File Operations

Check EML

Check EML file

With this form you can check if an XML file is compliant to the EML2.1.1 or EML 2.2.0 schema. Choose Data -> File operations -> Check EML file … from the menu. After opening the window shown below the schema files will be automatically loaded. You may select the schema that shall be used with combo box Schema version (see image below). Starting with DiversityDescriptions v. 4.3.5 the EML export will be done using EML 2.2.0.

 

In the window click on the button to select the file you want to check. The check results will be diplayed in the center part of the window. By clicking the reload button  you can start a new check (see image below).  

 

May 3, 2024

Check SDD

Check SDD file

With this form you can check if an XML file is compliant to the SDD 1.1rev 5 schema. Choose Data -> File operations -> Check SDD file … from the menu. After opening the window shown below the schema files will be automatically loaded.

 

In the window click on the button to select the file you want to check. The check results will be diplayed in the center part of the window. If you generated a SDD file using Diversity Descriptions with deactivated Comptible option, the check result may show warnings for elements with missing schema information. You may check the option Include specific schema extensions, then the Diversity Descriptions specific schema definitions will be included. By clicking the reload button  or selecting another file you can start a new check (see image below).  

 

May 3, 2024

Convert DELTA

Convert DELTA file to SDD or EML

With this form you can directly convert data from a file in DELTA format into an XML file according schema SDD 1.1 rev5. No connection to a database is needed for the conversion. Choose Data -> File operations -> Convert data file → DELTA to SDD … from the menu to open the window. In the window click on the button to select the file with the data you want to convert. If the Multi-file option is selected before pressing the button, a folder selection window opens to select the folder where the DELTA files are located. For muti-file processing currently the files “chars”, “items”, “specs” and “extra” are evaluated. If during analysis any problem occurs, you may click on the button to reload the file and re-initialize the window.

 

The contents of the file will be shown in the upper part of the File tree tab page. If special characters are not displayed corretly, try a different Encoding setting, e.g. “ANSI”, and reload the document using the button.

The Insert “variable” state controls the handling of the DELTA state “V” for categorical summary data. If possible, a categorical state “variable” is inserted to the descriptor data and set in the summary data, when the state “V” is present in the description data.

If the Check strings for illegal characters  option is checked, all string literals that shall be exported from database are scanned for illegal non-printable characters and matches are replaced by a double exclamation mark ("‼"). Activating this option may increase the analysis processing time.

In the file tree you may deselect entries that shall not be converted. Use that option very carefully, because if you deselect entries that are being referenced by other parts of the input tree, e.g. descriptors referenced by descriptions, the analysis step might become erronous!

If during reading of the files expressions cannot be interpreted, suspicious entries are maked with yellow background (warning) in the file tree. When you move the mouse curser over the marked entries, you get additional information as tool tip or the tree node text itself tells the problem (see example below).  

 

 

Analysis

To analyse the data in the file click on the Analyse data button. During the analysis the program checks the dependencies between the different parts of the data and builds up an analysis tree in the lower part of the window. The analysis tree contains all data in a suitable format for the final step. During data analysis the icon of the button changes to  and you may abort processing by clicking the button. 

In the Analysis settings section (see image below) you set the document’s Language. You man change the display and sorting of the entries in the Language combo box from “<code> - <description>” to “<description> - <code>” (and back) by clicking the button . If you need language codes that are not included in the list, click the button. For more details see Edit language codes.

The Insert “variable” state controls the handling of the DELTA state “V” for categorical summary data. If possible, a categorical state “variable” is inserted to the descriptor data and set in the summary data, when the state “V” is present in the description data.

If the Check strings for illegal characters  option is checked, all string literals that shall be exported from database are scanned for illegal non-printable characters and matches are replaced by a double exclamation mark ("‼"). Activating this option may increase the analysis processing time.

In DELTA text in angle bracket (<text>) usually denotes comments, which are by default imported into the “Details” fields of the database. In the lower parts of the Analysis settings you may adjust a different handling for description, descriptor and categorical state items. 

  • For DELTA comments in descriptions you may Move comments to details (default) or Keep comments in description titles.
  • For DELTA comments in descriptors you may Move comments to details (default), Move comments to notes or Keep comments in descriptor titles
  • For DELTA comments in categorical states you may Move comments to details (default) or Keep comments in categorical state titles.

After changing one of these settings click on the Analyse data button to make the changes effective.

After analysis a message window informs you if any warnings or errors occured. You can find detailled error and warning information at the file and/or analysis trees by entries with red text (error) or yellow background (warning). When you move the mouse curser over the marked entries, you get additional information as bubble help or the tree node text itself tells the problem (see example below). By clicking on the status text besides the progress bar, you can open an analysis protocol (see below, right). 

 

If an analysis error occured, you are not able to proceed. You will first have to correct the problem, e.g. by excluding the erronous descriptor in the example above (after reloading the file). If a warning occured, it might not cause further problems, but you should take a closer look if the converted data will be correct.

 

Write data

Pressing the Generate file button in the Write SDD group box opens a window to select the target XML file. By default the target file has the same name as the DELTA file, followed by the extension “.xml”. The Comptible option controls generation of files with most possible compatibility to the SDD standard. On the other hand some data might not be present in the generated file, if this option is activated.

As an additional option you may generate file according the EMLschema, which consists of a data table (tabulator separated text file) and an XML file that contains the metadata including column descriptions. Click on the Generate file button in the Write EML group box. The generated file names will have the endings "_EML_DataTable.txt" and "_EML_Metadata.xml".

Pressing the drop down button EML settings in the Write EML group box opens the EML writer options. You can chose to include a special sign for empty column values or set the columns values in quotes (see left image below). Furthermore you may shose the column separator (tab stop rsp. comma) an decide if multiple categorical states shall be inserted as separate data columns. If you already generated EML files, the used settings will be automatically saved and you may restore them using the option Load last write settings. Finally click button EML settings to close the option panel. 

 

 

Handling of special DELTA states

In the DELTA format the special states “-” (not applicable), “U” (unknown) and “V” (variable) are available for categorical and quantitative characters. These states are treated in the folloging manner during import:

  • -” (not applicable)
    The data status “Not applicable” is set.
  • U” (unknown)
    The data status “Data unavailable” is set.
  • V” (variable)
    The data status “Not interpreterable” is set.

 

Jan 14, 2025

Convert SDD

Convert SDD file to DELTA or EML

With this form you can directly convert data from a file in XML file according schema SDD 1.1 rev5 into a DELTA file. No connection to a database is needed for the conversion. Choose Data → File operations -> Convert data file → SDD to DELTA … from the menu to open the window. In the window click on the button to select the file with the data you want to convert. If during analysis any problem occurs, you may click on the button to reload the file and re-initialize the window.

 

The contents of the file will be shown in the upper part of the File tree tab page. In the Analysis settings part you find the documents’ default language. If additional laguages are contained in the document, you may select one of them as the new language of the DELTA file. By checking Import translations you select all additional document languages for the analysis step. This option is automatically pre-selected if more than one language has been found in the file. In the bottom part of the window you find the actual processing state.

In the file tree you may deselect entries that shall not be imported into the database. Use that option very carefully, because if you deselect entries that are being referenced by other parts of the input tree, e.g. descriptors referenced by descriptions, the analysis step might become erronous!

 

Analysis

To analyse the data in the file click on the Analyse data button. During the analysis the program checks the dependencies between the different parts of the data and builds up an analysis tree in the lower part of the window. The analysis tree contains all data in a suitable format for the final step. During data analysis the icon of the button changes to  and you may abort processing by clicking the button. 

 

After analysis a message window informs you if any warnings or errors occured. You can find detailled error and warning information at the file and/or analysis trees by entries with red text (error) or yellow background (warning). When you move the mouse curser over the marked entries, you get additional information as tool tip or the tree node text itself tells the problem (see examples below). By clicking on the status text besides the progress bar, you can open an analysis protocol (see below, right). 

  

If an analysis error occured, you are not able to proceed. You will first have to correct the problem, e.g. by excluding the erronous descriptor in the example above (after reloading the file). If a warning occured, it might not cause further problems, but you should take a closer look if the converted data will be correct.

 

Write data

Pressing the Generate file button in the Write Delta group box opens a window to select the target delta file. By default the target file has the same name as the SDD file, followed by the extension “.dat”. The Comptible option controls generation of files with most possible compatibility to the DELTA standard. On the other hand some data might not be present in the generated file, if this option is activated.

As an additional option you may generate file according the EMLschema, which consists of a data table (tabulator separated text file) and an XML file that contains the metadata including column descriptions. Click on the Generate file button in the Write EML group box. The generated file names will have the endings "_EML_DataTable.txt" and "_EML_Metadata.xml".

Pressing the drop down button DELTA settings in the Write DELTA group box opens the DELTA writer options. You can chose to include some detail text and notes in the DELTA output (see left image below). For descriptions, descriptors or categorical states the details will be appended as DELTA comments (included in angle brackets “< … >”) to the respective titles. The notes will be appended as DELTA comments of the corresponding summary data. If you already generated DELTA files, the used settings will be automatically saved and you may restore them using the option Load last write settings. Finally click button DELTA settings to close the option panel. 

Pressing the drop down button EML settings in the Write EML group box opens the EML writer options. You can chose to include a special sign for empty column values or set the columns values in quotes (see right image above). Furthermore you may shose the column separator (tab stop rsp. comma) an decide if multiple categorical states shall be inserted as separate data columns. If you already generated EML files, the used settings will be automatically saved and you may restore them using the option Load last write settings. Finally click button EML settings to close the option panel. 

 

Handling of special sequence data

While SDD can handle molecular sequence data, for DELTA export these data will be exported as text data. To preserve the sequence specific descriptor data, they will be inserted into the text character as a special comment with the format, e.g. “#6. Sequence descriptor <[SequenceCharacter][ST:N][SL:1][GS:-][/SequenceCharacter]>/”.

If the analysis tree includes sample data, they will be included as items at the end of the DELTA file. The naming of those spetial items will be <description name> - <event name> - Unit <number>. Sampling event data will not be included in the DELTA file.

May 16, 2024

Import

Import

There are several import mechanisms:

Matrix wizard: Import descriptors, descriptions and sample data from tabulator separated text file(s) organized as a matrix.

Import wizard: Import descriptive data from tabulator separated text file(s).

SDD import: Import descriptive data from an XML file according to the SDD schema 1.1 rev 5.

DELTA import: Import descriptive data from DELTA text file(s).

Import questionaires: Import revised data received from HTML forms.

Jan 14, 2025

Subsections of Import

Matrix Wizard

Matrix import wizard for tab separated lists

The table oriented import wizard works fine if you have separate lists for descriptor and description data. Usually this type of tables is generated by an export of data from a database. A typical example for that cases is described in the import wizardtutorial. If no dedicated application for collecting description data is available, most commonly a spreadsheet program like MS Excel or Open Office Calc is used to collect the description data. Typically the table columns represent a single character (=descriptor) and the table rows represent the items (=description or sample data). Importing data from such a “matrix” into Diversity Descriptions with the table oriented import wizard usually requires a lot of manual adaptions. Therefore the specialized “Matrix Wizard” was designed to import the most important descriptor and description data in a single import step. 

As usual you should create a new project and install a descriptor tree to collect the dedicated descriptors. Then choose Data → Import → Import wizard → Matrix wizard … from the menu. As know from the import wizard, a window to create or select a import session will be shown.

 

After selecting or creating an import session a window as shown below will open that will lead you through the import of the data. 

With the selection box Target: you may select which data shall be imported: 

Remark: Example files and XML schemas to import summary or sample data using the matrix wizard are provided in the tutorialfiles or may be downloaded from the Diversity Descriptions example file repository. Find the example data in folders “Biomass as description” and “Biomass as sample” 

Jan 14, 2025

Subsections of Matrix Wizard

Matrix Wizard Description

Matrix import wizard for description data

After selecting Target: Description a window as shown below will be displayed. The window is separated in three areas. On the left side you see the descriptor settings for the actual file column (presently not visible). On the right side you see the list of available import steps. In the middle part the details of the selected import steps are shown.

 

Choosing the File

As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Then choose the Encoding of the file, e.g. Unicode.  The Header lines specifies the number of header lines, usually at least the first line which typically contains the descriptor names (see image below). The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines, i.e. the descriptions/items that shall be imported. The not imported parts in the file are indicated with a gray background. If your data contains e.g. date information or floating point values where notations differ between countries (e.g. 3.14 - 3,13), choose the Language / Country to ensure a correct interpretation of your data. Finally you can select a prepared Schema (see sections Testing and Import below) for the import.

 

Choosing the descriptor types

In the first line of the file section the descriptor type of the file columns are displayed. The value Ignore indicates that the column shall not be imported. To adjust the descriptor type, select a cell in the file column and chose a Descriptor type in the left section of the panel (see image below). Available descriptor types are Categorical, Quantitative, Text and Sequence.

For categorical descriptors you may specify State splitters, if one item has more than one categorical state. To add a splitter click on the button, to remove it use the button. By clicking the Test states button you get a list of categorical states found in the file between start line and end line and the number of occurrences (field Count, see image above). With this function you may test the effect of the state splitters.

For quantitative descriptors you have to specify the Statistical measure that shall be used for the imported values. By clicking the Test values button you get a list of values in the file between start line and the line number in the file (see image above).

If a value cannot be interpreted as a number, it is marked with a light red background colour. You may edit the erroneous values in the test result panel (see below).

For text and sequence descriptors no additional adjustments are possible. As long as no descriptor columns have been defined, a reminder is visible on top of the left section:

  • Please select a descriptor type   = At least for one file column a descriptor type is needed.

In our example column 1 (date) will be adjusted as text descriptor and columns 2 (functional group) and 3 (sublocation) as categorical descriptors.

 

Table data

To set the source for the data columns, select the step of a table listed underneath the File step. Be aware that for the Descriptor table not the file columns will be selected but the file rows in the header lines. In the image below you see an example of the descriptor data columns, where the values for id and label are taken from the first line in the file. Additionally the descriptors will be assigned to the descriptor tree “Descriptor tree for matrix”.  

Remark: Although descriptortree_id is a numeric value in the database, the externally visible descriptor tree name is expected here. Since this name is unambigious, the corresponding id will be determined during import.

The option Address index allows the selection of the column number (for descriptor) rsp. the line number (for description) as value. See below an example for the Description table data columns. For id the line number has been selected to get an unambigious address value. The label has been composed of the line number, three data columns and some fixed text parts. Finally all description data are assigned to the project “Matrix text”.

Remark: Although project_id is a numeric value in the database, the externally visible project name is expected here. Since this name is unambigious, the corresponding id will be determined during import.

A reminder in the header line will show you what actions are still needed to import the data into the table:

  • Please select at least one decisive column   = If data will be imported depends on the content of decisive colums, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list

The handling of the columns is almost the same as described in the chapter columns of the table oriented import wizard.

 

Testing

To test if all requirements for the import are met use the Testing step. You can navigate to a certain data cell by using the Column: and Line: controls. As an alternative select the data cell ent click on button . Finally click on the Test data button. If there are still unmet requirements, these will be listed in a window as shown below. In the window below you can see the following test actions:

  1. Insert of a quantitative descriptor “biomass”
  2. Insert of a descriptor tree node (assignemnt to tree “Matrix test tree”)
  3. Insert of a recommended statistical measure (measure “Mean”) for the descriptor tree node
  4. Insert of description “Biomass 3 [CSP01 woody NW_c]” for project “Matrix test”
  5. Insert of a statistical measure for “Mean” with value 28.2020000…

You may save the schema file by a click on button Save schema. If you click on button Generate flat files according to your adjustments data and matching schema files for the table oriented import wizards will be generated. This option may be used, if you want to import additional data, e.g. a descriptor’s measurement unit, that are not supported by the matrix wizard. Since all mapping relevant data are stored in the selected import session, you may import the basic descriptor and description data using the matrix wizard and append additional data with the table oriented import wizards. In this case the generated flat data and schema files might be useful to have a defined starting point.    

 

Import

With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

Schedule for matrix import of tab-separated text files into DiversityDescriptions
Target within DiversityDescriptions: Description
Schedule version: 1 Database version: 03.00.17
Lines: 2 - 757 Header lines: 1
Encoding: ANSI Language: US

Tables

Descriptor (Descriptor)
Merge handling: Merge

Column in table ? Copy Pre Post File pos. Value Source
id ? 1 File
label 1 File
descriptortree_id Descriptor tree for matrix Interface

Description (Description)
Merge handling: Merge

Column in table ? Copy Pre Post File pos. Value Source
id ? Index
label Biomass Index
+ [ 0 File
+ 2 File
+ ] 3 File
project_id Matrix test Interface

Descriptor columns

File pos.

Descriptor type

Additional data

0

Categorical

Splitters

1

Text

2

Categorical

Splitters

3

Categorical

Splitters

4

Quantitative

Statistical measure
Mean (= average)

File cells that could not be imported will be marked with a red background while imported lines are marked green. If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

Protocol

Responsible: Link (DB-User: Workshop)
Date: Donnerstag, 20. April 2017, 15:53:24
Server: training.diversityworkbench.de
Database: DiversityDescriptions_Workshop
Descriptor columns total: 5
Descriptors imported: 5
Import lines total: 756
Descriptions imported: 756
Cells imported: 3780
Jan 14, 2025

Matrix Wizard Sample

Matrix import wizard for sample data

After selecting Target: Sampling event a window as shown below will be displayed. The window is separated in 3 areas. On the left side you see the descriptor settings for the actual file column (presently not visible). On the right side you see the list of available import steps. In the middle part the details of the selected import steps are shown.

 

Choosing the File

As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Then choose the Encoding of the file, e.g. Unicode.  The Header lines specifies the number of header lines, usually at least the first line which typically contains the descriptor names (see image below). The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines, i.e. the descriptions/items that shall be imported. The not imported parts in the file are indicated with a gray background. If your data contains e.g. date information or floating point values where notations differ between countries (e.g. 3.14 - 3,13), choose the Language / Country to ensure a correct interpretation of your data. Finally you can select a prepared Schema (see sections Testing and Import below) for the import.

 

Choosing the descriptor types

Choosing of the descriptor types is done in exactly the same way as described in section Matrix wizard for descriptiondata.

 

Table data

To set the source for the data columns, select the step of a table listed underneath the File step. Be aware that for the Descriptor table not the file columns will be selected but the file rows in the header lines. In the image below you see an example of the descriptor data columns, where the values for id and label are taken from the first line in the file. Additionally the descriptors will be assigned to the descriptor tree “Descriptor tree for matrix”.  

Remark: Although descriptortree_id is a numeric value in the database, the externally visible descriptor tree name is expected here. Since this name is unambigious, the corresponding id will be determined during import.

The option Address index allows the selection of the column number (for descriptor) rsp. the line number (for description or sampling event) as value. See below an example for the Description table data columns. For id and label the For all:  alue “++ New description ++” was selected to create a single description entry where all sample data are attached. Finally the description is assigned to the project “Matrix text sample”.

Remark: Although project_id is a numeric value in the database, the externally visible project name is expected here. Since this name is unambigious, the corresponding id will be determined during import.

Finally the source for the Sampling event table data columns must be selected. For id and label the file column 0 has been selected (see image below).

A reminder in the header line will show you what actions are still needed to import the data into the table:

  • Please select at least one decisive column   = If data will be imported depends on the content of decisive colums, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list

The handling of the columns is almost the same as described in the chapter columns of the table oriented import wizard.

 

Testing

To test if all requirements for the import are met use the Testing step. You can navigate to a certain data cell by using the Column: and Line: controls. As an alternative select the data cell ent click on button . Finally click on the Test data button. If there are still unmet requirements, these will be listed in a window as shown below. In the window below you can see the following test actions:

  1. Insert of a quantitative descriptor “Channel 2 VLT Us1G”
  2. Insert of a descriptor tree node (assignemnt to tree “Tree for matrix test sample”)
  3. Insert of a recommended statistical measure (measure “Mean”) for the descriptor tree node
  4. Insert of description “++ New description ++” for project “Matrix test sample”
  5. Insert of a sampling event “30.01.2014 22:00” for description “++ New description ++”
  6. Insert of a sampling unit with id 199 for sampling event “30.01.2014 22:00”
  7. Insert of a quantitative value -22.72 to sampling unit 199

You may save the schema file by a click on button Save schema. If you click on button Generate flat files according to your adjustments data and matching schema files for the table oriented import wizards will be generated. This option may be used, if you want to import additional data, e.g. a descriptor’s measurement unit, that are not supported by the matrix wizard. Since all mapping relevant data are stored in the selected import session, you may import the basic descriptor and description data using the matrix wizard and append additional data with the table oriented import wizards. In this case the generated flat data and schema files might be useful to have a defined starting point.    

 

Import

With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

Schedule for matrix import of tab-separated text files into DiversityDescriptions
Target within DiversityDescriptions: SamplingEvent
Schedule version: 1 Database version: 03.00.17
Lines: 5 - 151 Header lines: 4
Encoding: ANSI Language: US

Tables

Descriptor (Descriptor)
Merge handling: Merge

Column in table ? Copy Pre Post File pos. Value Source
id ? 1 File
label Channel 1 File
+ 2 File
+ 3 File
descriptortree_id Tree for matrix test sample Interface

Description (Description)
Merge handling: Merge

Column in table ? Copy Pre Post File pos. Value Source
id ? ++ New description ++ Interface
label ++ New description ++ Interface
project_id Matrix test sample Interface

SamplingEvent (SamplingEvent)
Merge handling: Merge

Column in table ? Copy Pre Post File pos. Value Source
id ? 0 File
label 0 File

Descriptor columns

File pos. Descriptor type Additional data
2 Quantitative
Statistical measure
Mean (= average)
3 Quantitative
Statistical measure
Mean (= average)
4 Quantitative
Statistical measure
Mean (= average)
5 Quantitative
Statistical measure
Mean (= average)
6 Quantitative
Statistical measure
Mean (= average)
7 Quantitative
Statistical measure
Mean (= average)
8 Quantitative
Statistical measure
Mean (= average)
9 Quantitative
Statistical measure
Mean (= average)
10 Quantitative
Statistical measure
Mean (= average)
11 Quantitative
Statistical measure
Mean (= average)
12 Quantitative
Statistical measure
Mean (= average)
13 Quantitative
Statistical measure
Mean (= average)
14 Quantitative
Statistical measure
Mean (= average)
15 Quantitative
Statistical measure
Mean (= average)
16 Quantitative
Statistical measure
Mean (= average)
17 Quantitative
Statistical measure
Mean (= average)
18 Quantitative
Statistical measure
Mean (= average)
19 Quantitative
Statistical measure
Mean (= average)
20 Quantitative
Statistical measure
Mean (= average)
21 Quantitative
Statistical measure
Mean (= average)
22 Quantitative
Statistical measure
Mean (= average)
23 Quantitative
Statistical measure
Mean (= average)
24 Quantitative
Statistical measure
Mean (= average)
25 Quantitative
Statistical measure
Mean (= average)
26 Quantitative
Statistical measure
Mean (= average)
27 Quantitative
Statistical measure
Mean (= average)
28 Quantitative
Statistical measure
Mean (= average)
29 Quantitative
Statistical measure
Mean (= average)
30 Quantitative
Statistical measure
Mean (= average)
31 Quantitative
Statistical measure
Mean (= average)
32 Quantitative
Statistical measure
Mean (= average)
33 Quantitative
Statistical measure
Mean (= average)
34 Quantitative
Statistical measure
Mean (= average)
35 Quantitative
Statistical measure
Mean (= average)
36 Quantitative
Statistical measure
Mean (= average)
37 Quantitative
Statistical measure
Mean (= average)
38 Quantitative
Statistical measure
Mean (= average)
39 Quantitative
Statistical measure
Mean (= average)
40 Quantitative
Statistical measure
Mean (= average)
41 Quantitative
Statistical measure
Mean (= average)
42 Quantitative
Statistical measure
Mean (= average)
43 Quantitative
Statistical measure
Mean (= average)
44 Quantitative
Statistical measure
Mean (= average)
45 Quantitative
Statistical measure
Mean (= average)

File cells that could not be imported will be marked with a red background while imported lines are marked green. If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

Protocol

Responsible: Link (DB-User: Workshop)
Date: Donnerstag, 20. April 2017, 16:17:42
Server: training.diversityworkbench.de
Database: DiversityDescriptions_Workshop
Descriptor columns total: 44
Descriptors imported: 44
Import lines total: 147
Descriptions imported: 1
Samples imported: 147
Cells imported: 6348
Cells failed: 120
Jan 14, 2025

Wizard

Import wizard for tab separated lists

With this import routines, you can import data from text files (as tab-separated lists) into the database. For a comprehensive real-life example that shows many features of the import wizard take a look at the import wizard tutorial

Choose Data → Import -> Import wizard and then the type of data that should be imported, e.g. Import descriptors … from the menu. If you did not use the import wizard before, the following window is shown to create a new import session.

 

In section Session project the projects with write access are listed for selection. In section Session description you should enter a detailled text description. If already an import session is present in the database, the window below will be shown where you may select the session. You may select one of the offered sessions or create a new one by selecting Create new import session

After selecting or creating an import session a window as shown below will open that will lead you through the import of the data. The window is separated in 3 areas. On the left side you see a list of possible data related import steps according to the type of data you choosed for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

 

Choosing the File

As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Then choose the Encoding of the file, e.g. Unicode. The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the First line contains the column definition this line will not be imported as well. If your data contains e.g. date information or floating point values, where notations differ between countries (e.g. 3.14 - 3,14), choose the Language / Country to ensure a correct interpretation of your data. Finally you can select a prepared Schema (see chapter Schema below) for the import.

 

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

Certain tables can be imported in parallel. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import information of logging columns like who created and changed the data, click on button in the header line. This will include an additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

 

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like “id” in the table “Descriptor” in the example below.

If you select a column for attachment, this column will be marked with a blue backgroud (see below and chapter Table data).

 

Merging data

You can either import your data as new data or Merge them wih data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported, otherwise the data will be updated..

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

 

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. Some columns may be grouped below the table name as shown for the Descriptor table. 

Click on one of the subordinated column groups and in the central part of the window the data columns avaialble for importing will be listed in the central part of the window. In the example shown below the column is used to attach the new data to data in the database.

All columns that have not been grouped beneath the table may be accessed by selecting the table ste itself. In the example shown below table Descriptor was selected to supply the “data_entry_note” column for import.

A reminder in the header line will show you what actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive colums, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparision   = For all merge types other than insert columns for comparision with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for you test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display you any errors that occurred as shown below. All datasets marked with a red backgroud, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets: INSERT, MERGE, UPDATE, No difference. Attach, No data. The colors of the table colums indicate whether a colums is decisive , a key column or an attachment column.  

If you suspect, that the import file contains data allready present in the database, you may test this an extract only the missing lines in a new file. Choose the attachment column (see chapter Attaching data) and click on the button Check for allready present data. The data allready present in the database will be marked red (see below). Click on the button Save missing data a text file to store the data not present in the database in a new file for the import. 

If you happen to get a file with a content as shown below, you may have seleted the wrong encoding or the encoding is incompatible. Please try to save the original file as UTF8 and select this encoding for the import. 

 

Import

With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

Schedule for import of tab-separated text files into DiversityCollection
Target within DiversityCollection: Specimen
Schedule version: 1 Database version: 02.05.41
Lines: 2 - 3215 First line contains column definition: ?
Encoding: Unicode Language: de

Tables

CollectionSpecimen (CollectionSpecimen)
Parent: CollectionEvent
Merge handling: Insert

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
CollectionSpecimenID Database
AccessionNumber ? ? 0 File

IdentificationUnit_1 (IdentificationUnit)
Parent: CollectionSpecimen
Merge handling: Merge

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
CollectionSpecimenID Database
IdentificationUnitID Database
LastIdentificationCache ? 2 File
+ 3 File
+ 4 File
+ 5 File
TaxonomicGroup ? fish Interface

IdentificationUnitAnalysis_1_1 (IdentificationUnitAnalysis)
Parent: IdentificationUnit_1
Merge handling: Update

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
CollectionSpecimenID Database
IdentificationUnitID Database
AnalysisID 94 Interface
AnalysisNumber 1 Interface
AnalysisResult ? ? 39 File

 Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

 

Description

A description of the schema may be included in the schema itself or with a click on the button generated as a separate file. This file will be located in a separate directory Description to avoid confusion with import schemas. An example for a description file is shown below, containing common settings, the treatment of the file columns and interface settings as defined in the schema.

Schedule for import of tab-separated text files into DiversityCollection
Target within DiversityCollection: Specimen
Schedule version: 1 Database version: 02.05.52
Lines: 2 - 5 First line contains column definition: ?
Encoding: Unicode Language: de
Description: Import Schema fuer Literaturdaten (Bayernflora) aus Dörr & Lippert mit MTB Daten und max. 4 Sammlern

File columns

Merge handling of table Column usage
Insert Merge Update Attach Decisive Key
Pos. Name Table Column Example Transformed
0 ID
CollectionSpecimen. ExternalIdentifier 1
1 originalname
Identification_1_2. TaxonomicName Ophioglossum vulgatum
2 nameautor
Identification_1_1. TaxonomicName Ophioglossum vulgatum L.
3 taxnr
Identification_1_1. NameURI 3949
Prefix: http://tnt.diversityworkbench.de/TaxonNames_Plants/
4 mtb
CollectionEventLocalisation_6. Location1 8423
5 qu
CollectionEventLocalisation_6. Location2 2
6 unschärfe
CollectionEventLocalisation_6. LocationAccuracy
7 jahr_von
CollectionEvent. CollectionYear 1902
8 jahr_bis
CollectionEvent. CollectionDateSupplement
Prefix: bis?
9 status
IdentificationUnitAnalysis_1_1. AnalysisResult
10 verwaltungseinheit not imported
11 fundort not imported
12 finder not imported
13 ID_collector1
CollectionAgent_1. CollectorsAgentURI 43708
Prefix: http://snsb.diversityworkbench.de/Agents_BayernFlora/
14 ID_collector2
CollectionAgent_2. CollectorsAgentURI
Prefix: http://snsb.diversityworkbench.de/Agents_BayernFlora/
15 ID_collector3
CollectionAgent_3. CollectorsAgentURI
Prefix: http://snsb.diversityworkbench.de/Agents_BayernFlora/
16 ID_collector4
CollectionAgent_4. CollectorsAgentURI
Prefix: http://snsb.diversityworkbench.de/Agents_BayernFlora/
17 primärquelle not imported
18 ID_primärquelle
Annotation_1. ReferenceURI
Prefix: http://id.snsb.info/references/
19 primärquelle_seiten not imported
20 bestand
IdentificationUnitAnalysis_1_2. AnalysisResult
21 sonstiges
CollectionSpecimen. OriginalNotes
22 höhe
CollectionEventLocalisation_7. Location1
23 herbar1 not imported
24 herbar2 not imported
25 herbar3 not imported
26 ID_herbar1
CollectionSpecimenRelation_1. RelatedSpecimenCollectionID
27 ID_herbar2 not imported
28 ID_herbar3 not imported
29 det not imported
30 ID_det not imported
31 rev not imported
32 ID_rev not imported
33 datenquelle not imported
34 ID_datenquelle
CollectionSpecimen. ReferenceURI 135
Prefix: http://id.snsb.info/references/
35 project1 not imported
36 project2
CollectionSpecimen. AdditionalNotes O Beobachtung
Transformations:
Reglar express.:
O ? Beobachtung
Reglar express.:
H ? Herbarauswertung
Reglar express.:
L ? Literaturauswertung

Interface settings

Table Table alias Column Value
Annotation Annotation_1 AnnotationType Reference
Annotation_1 Annotation Literaturauswertung: nach Dörr & Lippert (2004)
Annotation_1 ReferenceDisplayText Annotation
CollectionAgent CollectionAgent_1 CollectorsName Collector1
CollectionAgent_2 CollectorsName Collector2
CollectionAgent_3 CollectorsName Collector3
CollectionAgent_4 CollectorsName Collector4
CollectionEvent CountryCache Germany
CollectionProject CollectionProject_1 ProjectID 37
CollectionProject_2 ProjectID 149
CollectionSpecimen ReferenceTitle Reference
CollectionSpecimenRelation CollectionSpecimenRelation_1 RelatedSpecimenURI
CollectionSpecimenRelation_1 RelatedSpecimenDisplayText
CollectionSpecimenRelation_1 Notes Herbarauswertung: nach Dörr & Lippert (2004)
Identification Identification_1_1 IdentificationSequence 2
Identification_1_2 IdentificationSequence 1
Identification_1_2 Notes Originalname aus Dörr & Lippert (2004)
IdentificationUnit IdentificationUnit_1 LastIdentificationCache plant
IdentificationUnit_1 TaxonomicGroup plant
IdentificationUnitAnalysis IdentificationUnitAnalysis_1_1 AnalysisID 2
IdentificationUnitAnalysis_1_1 AnalysisNumber 1
IdentificationUnitAnalysis_1_2 AnalysisID 4
IdentificationUnitAnalysis_1_2 AnalysisNumber 2

 

 

Jan 14, 2025

Subsections of Wizard

Import DELTA

Import DELTA file

Remark:

  • To import data from a DELTA file at least TerminologyEditor rights are neccessary.

With this form you can import data from a file in DELTA format into the database. Choose Data → Import -> Import DELTA … from the menu to open the window for the import. In the window click on the button to select the file with the data you want to import. If the Multi-file option is selected before pressing the button, a folder selection window opens to select the folder where the DELTA files are located. For muti-file processing currently the files “chars”, “items”, “specs” and “extra” are evaluated. If during analysis or import any problems occur, you may click on the button to reload the file and re-initialize the window.

 

The contents of the file will be shown in the upper part of the File tree section. If special characters are not displayed corretly, try a different Encoding setting, e.g. “ANSI”, and reload the document using the button. In the bottom part of the window you find the import database and the actual processing state.

In the file tree you may deselect entries that shall not be imported into the database. Use that option very carefully, because if you deselect entries that are being referenced by other parts of the input tree, e.g. descriptors referenced by descriptions, the analysis or import step might become erronous!

If during reading of the files expressions cannot be interpreted, suspicious entries are maked with yellow background (warning) in the file tree. When you move the mouse curser over the marked entries, you get additional information as tool tip or the tree node text itself tells the problem (see example below).  

 

 

Analysis

To analyse the data in the file click on the Analyse data button. During the analysis the program checks the dependencies between the different parts of the data and builds up an analysis tree in the lower part of the window. The analysis tree contains all data in a suitable format for the final import step. During data analysis the icon of the button changes to  and you may abort processing by clicking the button. 

In the Analysis settings section (see image below) you set the document’s Language. You man change the display and sorting of the entries in the Language combo box from “<code> - <description>” to “<description> - <code>” (and back) by clicking the button . If you need language codes that are not included in the list, click the button. For more details see Edit language codes.

The Insert “variable” state controls the handling of the DELTA state “V” for categorical summary data. If possible, a categorical state “variable” is inserted to the descriptor data and set in the summary data, when the state “V” is present in the description data.

If the Check strings for illegal characters  option is checked, all string literals that shall be exported from database are scanned for illegal non-printable characters and matches are replaced by a double exclamation mark ("‼"). Activating this option may increase the analysis processing time.

In DELTA text in angle bracket (<text>) usually denotes comments, which are by default imported into the “Details” fields of the database. In the lower parts of the Analysis settings you may adjust a different handling for description, descriptor and categorical state items. 

  • For DELTA comments in descriptions you may Move comments to details (default) or Keep comments in description titles.
  • For DELTA comments in descriptors you may Move comments to details (default), Move comments to notes or Keep comments in descriptor titles
  • For DELTA comments in categorical states you may Move comments to details (default) or Keep comments in categorical state titles.

After changing one of these settings click on the Analyse data button to make the changes effective.

 

After analysis a message window informs you if any warnings or errors occured. You can find detailled error and warning information at the file and/or analysis trees by entries with red text (error) or yellow background (warning). When you move the mouse curser over the marked entries, you get additional information as bubble help or the tree node text itself tells the problem (see example below). By clicking on the status text besides the progress bar, you can open an analysis protocol (see below, right). 

 

If an analysis error occured, you are not able to proceed. You will first have to correct the problem, e.g. by excluding the erronous descriptor in the example above (after reloading the file). If a warning occured, it might not cause problems during import, but you should take a closer look if the imported data will be correct.

 

Import

If you want to import new data to a project you have two import options:

  • New import - import new data and save mapping information to an import session.
    For descriptors, categorical states and descriptions the mapping information from the DELTA import will be storen in an import session. Therefore by a subsequent import run updated information, e.g. a modified label or detail information can be done (see section “Update” below).
  • No update - import new data without saving of mapping information.
    This option might be faster, but you will not be able to update the titles or to import additional translations from a DELTA file.

Before starting the import, you should take a look at the import settings:

  • New project - import data to a new project.
    The project name is specified in the text box right from this radio button.
    This option is only available if at least ProjectManager rights are available.
  • To project - import data to an existing project.
    The combo box at the right shows all projects where write access is possible.
    If only TerminologyEditor rights are availabe, no changes in the existing project (e.g. detail or copyright) will be done.
  • Accept comma as decimal separator shall help to overcome problems with localization of some programs that create DELTA files.
    If this option is checked, a floating point value like “1,0” (e.g. used in german localizations) instead of “1.0” will be accepted as “1”.
  • Create default descriptor tree creates a default descriptor tree and assigns all imported descriptors to that tree.
    Additionally the statistical measures “Minimum”, “Lower limit”, “Mean”, “Upper limit” and “Maximum” are set as recommended for all quantitative descriptors.
    This option is useful to avoid unassigned descriptors if the import file does not specify any descriptor tree assignments.

To start the import click on the Start import button. Now the data from the analysis tree are written into a local database cache and finally stored into the database.

 

After import a message window inform you if any warnings or errors occured. You can find detailled error and warning information at the file and/or analysis trees by entries with red text (error) or yellow background (warning). When you move the mouse curser over the marked entries, you get additional information as bubble help or the tree node text itself tells the problem. By clicking on the status text besides the progress bar, you can open an import protocol (see below). 

 

 

Handling of special DELTA states

In the DELTA format the special states “-” (not applicable), “U” (unknown) and “V” (variable) are available for categorical and quantitative characters. These states are treated in the folloging manner during import:

  • -” (not applicable)
    The data status “Not applicable” is set.
  • U” (unknown)
    The data status “Data unavailable” is set.
  • V” (variable)
    The data status “Not interpreterable” is set.

 

Update

If you imported new data using option New import, a new import session with the following data will be created:

  • Descriptor keys - the “character number” that is used in DELTA to identify a dedicated character.
  • Categorical state keys - the “state number” that is used in DELTA, together with the “character number”, to identify a dedicated chategorical state.
  • Description keys - the item position in the item list. Since in DELTA there are no explicit item numbers, the position within the item list is taken for this key. If you want to update the items using the DELTA import, you must be sure that the item list has exactly the same sequence as for the first import!

For those entities you may update the columns “label”, “detail” and “data_entry_notes” (only for descriptors). To achive this, you must specify the same Language in the Analysis settings as adjusted as project language. If you specify a different Default language, the data will be imported as translations for the columns “label” rsp. “detail” (see image below). For descriptor column “data_entry_notes” translations are not supported.

 

Preparation

By changing the Analysis settings and a clicking the Analyse data button you may modify the handling of DELTA comments. E.g. if you used the default settings during a past import, a DELTA character “data record <type>” was imported as descriptor “data record” and “type” was written into the columns “detail”. In the Analysis settings you may now select option Keep comments in descriptor titles to update the descriptor title to “data record <type>". 

 

Import settings

Before starting the import, you should take a look at the import options:

  • Update - perform an update import.
  • Import session - click on button  Select to select the correct import session.
    In the text box below that option the automatically generated descriptive text of the import session is displayed.
  • Remove optional columns - clear optional columns if no contents is present.
    If during update import for an optional column (“detail” rsp. “data_entry_note”) no data are present, by default an existing entry in the database will not be removed. Check this option to clear the data.

Start the import click on the Start import button. Now the data from the analysis tree are written into a local database cache and finally stored into the database.

 

 

 

Jan 14, 2025

Import Questionnaires

Import questionnaire data

With this form you can import response data generated by an HTML questionnaire (see Export questionnaires). Choose Data → Import -> Import questionnaire data … from the menu to open the window for the import. In the window click on the button to select the text file with the data you want to import. If during analysis or import any problem occurs, you may click on the button to reload the file and re-initialize the window.

 

The contents of the file will be shown in the upper part of the Import contents section. You may edit the contents or even enter the whole data by copy - paste. In the Import data part you find the basic dataset parameters Export server, Export database, Import project and Import description (see image below). If there is a mismatch, e.g. because the questionnaire was generated from a different database than your import database, an appropriate error will be reported.

 

Analysis

To analyse the data in the file click on the Analyse data button. During the analysis the program compares the reported data to the entries in the database and presents the planned database operations in the lower part of the window (see image below). By checking Accept comma as decimal separator in the Import options section you can overcome problems with localization of the computer where the questionnaire was filled in. If this option is checked, a floating point value like “1,0” (e.g. used in german localizations) instead of “1.0” will be accepted as “1”.

 

After analysis a message window informs you about errors or ignored input lines. By clicking on the status text besides the progress bar, you can open an analysis protocol (see below). 

  

If an analysis error occured, you are not able to proceed. If ignored lines are reported, this fact is usually uncritical. Most of them concern “modifier” or “frequency” values (prefix CM, CF or QM) where the questionnaire reports the actual values, not only the differences.

 

Import

Before starting the import, you should take a look at the remaining Import options:

  • Update description after backup
    Create a backup of the original description data and then update the original description in the database. If this option is chosen, you may enter a Postfix that will be appended at the backup description name. Additionally you may select the option Include data and time to append these data at the backup name, too (see image below).
  • Create a new description (only option for new descriptions)
    Make a copy of the original description data and then updatde the copy in the database.
  • Update description in database
    The original description in the database will be updated.

If the description entries in your database are referenced by other applications, you should update the original database entry, i.e. use the first or third option. The reason is that references from other databases usually use the description id, which will be different for the copied description. To ensure that the questionnaire data are correct, you can import them useing the option Create a new description, verify the imported data and finally import them to the original description using option Update description in database.

Before performing the import you may include or exclude single database operations by setting or removing the check mark in column “OK”. You may select or deselect all operations by clicking the buttons Select all rsp. Select none. Please be aware that deselecting single operation might lead to unexpected results.

To start the import click on the Start import button (see image below). 

 

After import a message window inform you if any occured. Sucessful database operations are shown with green background, unsuccessful operations with red background. When you move the mouse curser over the red entries, you get additional information as bubble help. By clicking on the status text besides the progress bar, you can open an import protocol (see below).  

  

 

Batch import

If you want to import several questionaire result files, there is the comfortable option to do a batch import. When you select the option Multi-file, the window changes as shown below. For batch import you only have the option to create a new description that will be updated with the questionnaire data.

Click on the button and select all text files you want to import. In the lower part of the window the selected files will belisted (see image below). 

After checking the remaining Import options click on the Start import button to start the import. In the lower part of the window you find the processing result for each selected file (see image below). 

 

 

Jan 14, 2025

Import SDD

Import SDD file

Remarks:

  • To import data from an SDD file at least TerminologyEditor rights are neccessary.
  • Currently SDD statements concerning natural laguage descriptions and identification keys are not evaluated.

With this form you can import data from an XML file according schema SDD 1.1 rev 5 into the database. You may download an example SDD file with from the Diversity Descriptions example file repository. Choose Data → Import → Import SDD … from the menu to open the window for the import. In the window click on the button to select the file with the data you want to import. If during analysis or import any problems occur, you may click on the button to reload the file and re-initialize the window.

 

The contents of the file will be shown in the upper part of the File tree tab page. In the Analysis settings part you find the document’s Default language. If additional laguages are contained in the document, you may select one of them as the new default language of the database. By checking Import translations you select all additional document languages for the import. This option is automatically pre-selected if more than one language has been found in the file. In the bottom part of the window you find the import database and the actual processing state.

If the Check strings for illegal characters  option is checked, all string literals that shall be exported from database are scanned for illegal non-printable characters and matches are replaced by a double exclamation mark ("‼"). Activating this option may increase the analysis processing time.

In the file tree you may deselect entries that shall not be imported into the database. Use that option very carefully, because if you deselect entries that are being referenced by other parts of the input tree, e.g. descriptors referenced by descriptions, the analysis or import step might become erronous!

 

Analysis

To analyse the data in the file click on the Analyse data button. During the analysis the program checks the dependencies between the different parts of the data and builds up an analysis tree in the lower part of the window. The analysis tree contains all data in a suitable format for the final import step. During data analysis the icon of the button changes to  and you may abort processing by clicking the button. 

 

After analysis a message window informs you if any warnings or errors occured. You can find detailled error and warning information at the file and/or analysis trees by entries with red text (error) or yellow background (warning). When you move the mouse curser over the marked entries, you get additional information as tool tip or the tree node text itself tells the problem (see examples below). By clicking on the status text besides the progress bar, you can open an analysis protocol (see below, right). 

  

If an analysis error occured, you are not able to proceed. You will first have to correct the problem, e.g. by excluding the erronous descriptor in the example above (after reloading the file). If a warning occured, it might not cause problems during import, but you should take a closer look if the imported data will be correct.

 

Import

Before starting the import, you should take a look at the import options:

  • New project - import data to a new project.
    The project name is specified in the text box right from this radio button.
    This option is only available if at least ProjectManager rights are available.
  • To project - import data to an existing project.
    The combo box at the right shows all projects where write access is possible.
    If only TerminologyEditor rights are availabe, no changes in the existing project (e.g. detail or copyright) will be done.
  • Accept comma as decimal separator shall help to overcome problems with localization of some programs that create SDD files.
    If this option is checked, a floating point value like “1,0” (e.g. used in german localizations) instead of “1.0” will be accepted as “1”.
  • Create default descriptor tree creates a default descriptor tree and assigns all imported descriptors to that tree.
    Additionally the statistical measures “Minimum”, “Lower limit”, “Mean”, “Upper limit” and “Maximum” are set as recommended for all quantitative descriptors.
    This option is useful to avoid unassigned descriptors if the import file does not specify any descriptor tree assignments.
  • Import trees for natural language descriptions - currently natural language descriptions are ignored.
  • Import trees without “role” - usually those trees only contain descriptor dependency information.

To start the import click on the Start import button. Now the data from the analysis tree are written into a local database cache and finally stored into the database.

 

After import a message window inform you if any warnings or errors occured. You can find detailled error and warning information at the file and/or analysis trees by entries with red text (error) or yellow background (warning). When you move the mouse curser over the marked entries, you get additional information as bubble help or the tree node text itself tells the problem. By clicking on the status text besides the progress bar, you can open an import protocol (see below).  

 

May 16, 2024

Import Sessions

Import sessions

Usually the information required for an import into DiversityDescriptions is spread over at least two files, e.g. “terminology” (descriptors/categorical states) and “items” (descriptions data), where the elements of the terminology are referenced to build the item descriptions. Between these files references are usually built using e.g. a descriptor number and/or the categorical state name. Within the DiversityDescriptions database relations are built using automatically generated numbers (“id”). To allow a mapping between the internally generated keys and the external keys, the “Import sessions” are used.

When you start the import wizard you are asked to select rsp. create a new import session. To ge an overview of the present import session or to create, edit and delete import sessiong select Data -> Import -> Wizard -> Organize sessions … and a window as shown below will be shown.

Click buttoem New and a window as shown below will be shown. Select the project of the import session and enter a description text. So save the new import session click Save ,to ignore the changes click button Don’t save. A similar window can be opened by selecting an existing import session and clicking Edit

To delete an import session, select it and click the Delete button. If import mapping data are present for the import session, an additional window will be shown that informs you about the number of mappings that will be implicitelx deleted and you have the chance to cancel the delete process (see below).

 

 

Import mapping

To view the mapping information that has been stored for an import session, select it and click the Mapping button. If import mapping data are present for the import session, a table with the database “Table name”, an optional “Parent key”, e.g. the descriptor id in case of categorical states, the “External key” used for import and the database interal key, the “Object ID”, is displayed (see below). To go back to the session overview, click the Session button. 

You may search for specific strings in the mapping table by entering the search string in the upper right text box and clicking the  button. Menu item Clear mapping allows clearing of mapping information for selected tables or all tables. With menu item Import mapping an import wizard can be opened to read the mapping information from tab-separated files. A detailled example for using the mapping import is shown in Import wizard - tutorial for advanced functions.  

If you want to import list data that include the internal database keys, you can generate mapping data that make these internal keys available for import by klicking menu item Generate mapping …. All mappings of the selected import session will be deleted and the internal keys (“Object ID”) of descriptors, categorical states, descriptions and their resources will be inserted as external keys. By using this function you can re-import rsp. update data that have been generated with the form Export resource data list and modified with an external program. 

May 3, 2024

Wizard Advanced Tutorial

Import wizard - tutorial for advanced functions

The second part of the import wizard tutorial is dedicated to some advanced functions of the import wizard. When data are imported from the file formats DELTA or SDD, no import mapping information is stored, because all logical references are completely satisfied within the data files. The starting point of this tutorial, which was taken from a real life example, is a database imported from a DELTA file. For the datasets a lot of pictures are available on a web server. A web application reads the data from the original database (where the DELTA file was generated) and gets the information about available pictures from a second database to display both in a browser. From the original databases several tables were extracted and now the pictures shall be appended to the imported data.

 

Overview of the data tables and necessary import steps  

Step 1 - Preparations: Data import from DELTA file and new import session  

Step 2 - Import of categorical state mapping 

Step 3 - Import of descriptor mapping 

Step 4 - Import of description mapping 

Step 5 - Import of resouces for descriptors 

Step 6 - Import of resouces for categorical states 

Step 7 - Import of resouces for descriptions 

Step 8 - Import of resouce variant 

 

May 3, 2024

Subsections of Wizard Advanced Tutorial

Wizard Advanced Tutorial Step 1

Step 1 - Preparations: Data import from DELTA file and new import session

Choose Data → Import -> Import DELTA … (see Import DELTA file) from the menu and import the DELTA file to project “Deemy” (see below). If the original database contains special characters, e.g. the German letters “ä”, “ö” or “ü”, it is recommended to specify the export character set “Unicode” or “UTF” if the application allows that. If the character set “ANSI” or “ASCII” was used, you may try the corresponding encoding setting to get a satifactory import result. The option “Accept comma as decimal separator” was checked, because the export has been done on a German computer system, where a value like “3.14” is exported as “3,14”.

Close the window above and choose Data → Import -> Wizard → Organize session … from the menu. A window as shown below will open, click the New button to create a new import session. Select project “Deemy” and enter a session description. Finally click button Save to store the data (see below).

 

When you now click on button Mapping you can see that no mapping data are available (see below).

 

 

Next: Step 2 - Import of categorical state mapping 

Jan 14, 2025

Wizard Advanced Tutorial Step 2

Step 2 - Import categorical state mapping

In the Import session form choose Import mapping → Descriptor … from the menu. A window as shown below opens that will lead you through the import of the descriptor mapping data. 

The only available import step Descriptor Mapping is already selected at the left side of the window. Now choose the File from where the data should be imported. Open file “Deemy_CHAR.txt”. The chosen encoding ANSI of the file is sufficient. The file column “CharName” contains the descriptor names and file column “CID” the external ID needed for the import of the categorical state mapping import (see below).

In the step table at the right side you find the import step Descriptor Mapping. Click on it and in the center window the assignemt data for the internal “object_id” and the “external_key” are displayed. In column “object_id” click on to make this the decisive column, further click on From file to select the column “CharName” as data source. Now click on the  In column “external_key” click on From file to select the column “CID” as data source. After that the columns should look as shown below.  

Remark: In the import wizards for the import mapping “object_id” allways represents the internal ID of the database. The matching database entry is searched by comparing the label of the database entry to the selected file column. If there are several descriptors (or descriptions) with identical names, the import will generate errors. For categorical states a special handling is available if the state names are not unique.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window. In our example no error occured and the test for the first data line is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

 

 

Append categorical state mapping

Close the import form for descriptors. In the Import session form choose Import mapping -> Categorical state … from the menu and open file “Deemy_CS.txt” (see below). 

The only available import step CategoricalState Mapping is already selected at the left side of the window. In the step table at the right side you find the import step CategoricalState Mapping, too. Click on it and in the center window the assignemt data for the internal “object_id”, the “parent_key” and the “external_key” are displayed. In column “object_id” click on to make this the decisive column, further click on From file to select the column “CharStateName” as data source. In column “parent_key” you have to specify the parent of the categorical state, i.e. the external descriptor ID. Therefore click on From file to select the column “CID” as data source. In column “external_key” click on From file to select the column “StateID” as data source. After that the columns should look as shown below.  

In the source database of this example not only the categorical states as known in DiversityDescriptions are present, but also some “pseudo states” that represent statistical measures of quantitative descriptors or the data status value “not applicable”. The real categorical states can be recognized by a numeric value in file column “CS”. In any case the import wizard check if a categorical state with the label specified in file column “CharStateName” exists in the database. Therefore let’s do a first test for some selected file lines.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window. Perform the import test for file lines 2, 13 and 12 (see below).

 

The file line 2 refers to parent “CID=1”, which belongs to a text descriptor. The pseudo state “(internal)” was not found as a categorical state in the database, therefore not import is performend for the file line.

 

The file line 13 refers to parent “CID=3”, which belongs to a categorical descriptor. The categorical state “monopodial-pinnate” was found exactly once in the database, therefore the import test was successful.

 

The file line 12 refers to parent “CID=3”, which belongs to a categorical descriptor. But the categorical state “absent” was found 152 time in the database. Therefore it was not possible to find the correct categorical state. But the error message already gives a hint how to solve the problem: To get an unambigious match, additionally the (external) descriptor ID must be specified.

Select the import step CategoricalState Mapping and click on the button at the end of line “object_id”. Select file column “CID”, which contains the reference to the descriptor and enter the separator character | (pipe symbol) in field Pre.: of the new line. Additionally click on button in the first line of “object_id”. In the transformation window insert one replacement (button ): Replace <br> by <br /> . This transformation is neccessary, because the formatting tag “<br>” will be converted to the standardized format “<br /> during export from the original database and import from DELTA. You can check that transformation by the test functions for lines 1860 and 3555. After that the column should look as shown below.

The import test with file line 12 now gives a positive result as shown below..

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. The imported data lines are marked green (see below).

 

Next: Step 3 - Import of descriptor mapping 

May 16, 2024

Wizard Advanced Tutorial Step 3

Step 3 - Import of descriptor mapping

Close the import form for the categorical state mapping. In the Import session form choose Clear mapping -> Descriptor from the menu (see below) and answer the followind question with “Yes”. This mapping is based on data column “CID” and was needed in the previous step to append the categorical state mapping data. For the picture import the descriptor mapping based on data column “CharID” is required.

In the Import session form choose Import mapping → Descriptor … from the menu and open file “Deemy_CHAR.txt”. The file column “CharName” contains the descriptor names and file column “CharID” the foreign ID (see below).

In the step table at the right side you find the import step Descriptor Mapping. Click on it and in the center window the assignemt data for the internal “object_id” and the “external_key” are displayed. In column “object_id” click on to make this the decisive column, further click on From file to select the column “CharName” as data source. Now click on the  In column “external_key” click on From file to select the column “CharID” as data source. After that the columns should look as shown below.  

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window. In our example no error occured and the test for the first data line is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

 

Next: Step 4 - Import of description mapping 

May 16, 2024

Wizard Advanced Tutorial Step 4

Step 4 - Import description mapping

Close the import form for descriptors. In the Import session form choose Import mapping → Description … from the menu and open file “Deemy_ITEM.txt” (see below). 

The only available import step Description Mapping is already selected at the left side of the window. In the step table at the right side you find the import step Description Mapping, too. Click on it and in the center window the assignemt data for the internal “object_id” and the “external_key” are displayed. In column “object_id” click on to make this the decisive column, further click on From file to select the column “ItemName” as data source. In column “external_key” click on From file to select the column “ItemID” as data source. After that the columns should look as shown below.  

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and then click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window. In our example no error occured and the test for the first data line is shown below.

 

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. The imported data lines are marked green (see below).

The failed lines are in this example caused by duplicate item names twice in the database. This problem can be fixed by renaming the ambigious entries in the database and the import file, e.g. to “Alnirhiza cystidiobrunnea + Alnus 1” and “Alnirhiza cystidiobrunnea + Alnus 2” rsp. “Lactarius omphaliformis Romagn. + Alnus 1” and “Lactarius omphaliformis Romagn. + Alnus 2”. 

 

Next: Step 5 - Import of resources for descriptors 

May 16, 2024

Wizard Advanced Tutorial Step 5

Step 5 - Import of resources for descriptors

Close the import wizard for the mapping data and the import session window. Now choose Data → Import -> Wizard -> Import resources → Descriptor resources … from the menu. A window as shown below will open to select an import session. Select the session for project “Deemy”.

After clicking [OK] the following window opens that will lead you through the import of the descriptor resource data. Open file “Deemy_RSC.txt” (see below).

 

Selecting the data ranges

In the selection list on the left side of the window all possible import steps for the data are listed according to the type of data you want to import. The step Descriptor is already selected, additionally check the step Descriptor resource (see below).

We attach the descriptor resource values to the descriptors, therefore we will not change anything in the descriptor but will attach data. In import step Attachment at the right side select Descriptor id (see below). 

Select the import step Merge from the list. For Descriptor we select the Attach option because this tables shall not be changed, for the other step Insert should already be selected, because a new entry has to be inserted (see below).

In the step table at the right side you find the import steps Descriptor and Descriptor resource and below them the data groups of the import steps. Deselect every column from import step Descriptor except “id”. Mark the “id” column as Key column for comparison during attachment and click on From file to select the column “CharID” as data source. The “id” column of import step Descriptor now looks as shown below.

In the import step Descriptor resource click on Resource ID and in the center window the assignemt data for the resource id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “Resource” as data source. After that the column should look as shown below.  

Click on Resource name. The center window shows the data column “label”. Click on From file in the “label” line to select file column “Resource”. After the resource number the value in data column “Caption” shall be inserted, included in brackets, if it is present. Click on the button at the end of line “label” and select column “Caption”. Enter  ( (blank and opening bracket) in field Pre.: and ) in field Post.: of the new line. After that the column should look as shown below.

Finally click on Sequence number. In the center window select the data column “display_order”, click on From file and select file column “DisplayOrder” (see below).

 

Testing

To test if all requirements for the import are met use the Testing step. The test for the first data line is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. There are 86 lines that were not imported due to duplicate entries (see below).

The failed lines are caused by duplicate entries, i.e. the resource was already imported for the descriptor.

 

Next: Step 6 - Import of resources for categorical states 

May 16, 2024

Wizard Advanced Tutorial Step 6

Step 6 - Import of resources for categorical states

Close the import wizard for the descriptor resources. Now choose Data -> Import -> Wizard → Import resources → State resources … from the menu, select the session for project “Deemy”. The following window opens that will lead you through the import of the categorical state resource data. Open file “Deemy_RSC.txt” (see below).

 

Selecting the data ranges

In the selection list on the left side of the window all possible import steps for the data are listed according to the type of data you want to import. Deselect the step Descriptor, it is not needed since the categorical states have been assigned unambiguous external IDs in step 3. Check the steps Categorical state and State resource (see below).

We attach the state resource values to the categorical states, therefore we will not change anything in the categorical state but will attach data. In import step Attachment at the right side select Categorial state id (see below). 

Select the import step Merge from the list. For Categorical state we select the Attach option because this tables shall not be changed, for the other step Insert should already be selected, because a new entry has to be inserted (see below).

In the step table at the right side you find the import steps Categorical state and State resource and below them the data groups of the import steps. Deselect every column from import step Categorical state except “id”. Mark the “id” column as Key column for comparison during attachment and click on From file to select the column “StateID” as data source. The “id” column of import step Categorical state now looks as shown below.

In the import step State resource click on Resource ID and in the center window the assignemt data for the resource id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “Resource” as data source. After that the column should look as shown below.  

Click on Resource name. The center window shows the data column “label”. Click on From file in the “label” line to select file column “Resource”. After the resource number the value in data column “Caption” shall be inserted, included in brackets, if it is present. Click on the button at the end of line “label” and select column “Caption”. Enter  ( (blank and opening bracket) in field Pre.: and ) in field Post.: of the new line. After that the column should look as shown below.

Finally click on Sequence number. In the center window select the data column “display_order”, click on From file and select file column “DisplayOrder” (see below).

 

Testing

To test if all requirements for the import are met use the Testing step. The test for the second data line is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. There are 561 lines that were not imported due to duplicate entries (see below).

The failed lines are caused by duplicate entries, i.e. the resource was already imported for the categorical state.

 

Next: Step 7 - Import of resources for descriptions 

Jan 14, 2025

Wizard Advanced Tutorial Step 7

Step 7 - Import of resources for descriptions

Close the import wizard for the state resources. Now choose Data -> Import -> Wizard → Import resources → Description resources … from the menu, select the session for project “Deemy”. The following window opens that will lead you through the import of the categorical state resource data. Open file “Deemy_RSC.txt” (see below).

 

Selecting the data ranges

In the selection list on the left side of the window all possible import steps for the data are listed according to the type of data you want to import. Step Description is already selected. Aditionally check step  Description resource (see below).

We attach the description resource values to the descriptions, therefore we will not change anything in the description but will attach data. In import step Attachment at the right side select Description id (see below). 

Select the import step Merge from the list. For Description we select the Attach option because this tables shall not be changed, for the other step Insert should already be selected, because a new entry has to be inserted (see below).

In the step table at the right side you find the import steps Description and Description resource and below them the data groups of the import steps. Deselect every column from import step Description except “id”. Mark the “id” column as Key column for comparison during attachment and click on From file to select the column “ItemID” as data source. The “id” column of import step Description now looks as shown below.

In the import step Description resource clickon Resource ID and in the center window the assignment data for the resource id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “Resource” as data source. After that the column should look as shown below.  

Click on Resource name. The center window shows the data column “label”. Click on From file in the “label” line to select file column “Resource”. After the resource number the value in data column “Caption” shall be inserted, included in brackets, if it is present. Click on the button at the end of line “label” and select column “Caption”. Enter  ( (blank and opening bracket) in field Pre.: and ) in field Post.: of the new line. After that the column should look as shown below.

Finally click on Sequence number. In the center window select the data column “display_order”, click on From file and select file column “DisplayOrder” (see below).

 

Testing

To test if all requirements for the import are met use the Testing step. The test for the data line 717 is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. There are 177 lines that were not imported due to duplicate entries (see below).

The failed lines are caused by duplicate entries, i.e. the resource was already imported for the description.

 

Next: Step 8 - Import of resource variants 

May 16, 2024

Wizard Advanced Tutorial Step 8

Step 8 - Import of resource variants

The import wizards used in step 5 up to step 7 allow appending a resource variant to one resource. Those wizards can be used most efficiently if the data that are needed for the resource table and the resource variant are located at the same file. In our example there is the complication that the direction of the resource reference is in the opposite direction than in the original database. In DiversityDescription a resource references e.g. a descriptor and one or more resource variants reference the resource. In the original database several entities, e.g. descriptors or states, may reference the same picture.

During the import of the resources we used the picture number as the external key of the resources. Together with their parent key, e.g. a descriptor ID, this gives unambiguous entries although the external resource ID alone is ambiguous. Now we want to create a resource variant, containing the URL of the picture, for each resource entry with the same external resource ID.

Since this “multiple” import is no standard feature of the import wizard, the following description shows a work-around: During the import the first resource entry with a matching “Resource ID” that is not referenced by any Resource variant will be available for data update and appending of a new resource variant. A repeated import with the same setting will find the next resource entry and so on until all ambigious resource entries are processed. 

Close the import wizard for the description resources. Now choose Data -> Import -> Wizard → Import resources → Resource variants … from the menu, select the session for project “Deemy”. The following window opens that will lead you through the import of the categorical state resource data. Open file “Deemy_IMG.txt” (see below).

 

Selecting the data ranges

In the selection list on the left side of the window all possible import steps for the data are listed according to the type of data you want to import. The available steps Update resource and Resource variant are already selected.

We want to update some fields of the resource table with values form the data file attach the resource variant to the resource. In import step Attachment at the right side select Update resource id (see below). Note: With this import wizard only update of resources is supported. 

Select the import step Merge from the list. For Update resource we keep the Merge option because this table shall be updated, for the other step Insert should already be selected, because a new entry has to be inserted (see below).

In the import step Update resource click on Resource ID and in the center window the assignment data for the resource id (“id”) are displayed. Click on to make this the decisive column. Mark the “id” column as Key column for comparison during attachment and click on From file to select the column “PID” as data source. After that the column should look as shown below.

Click on Resource name. The center window shows the data column “label” and “detail”. Deselect the “label” entry and select “detail”. Click on From file to select the column “SourceTitle” as data source and enter Source:  in field Pre.: (double-click in the field to open a separate edit window). Now click on the button at the end of line “detail”, select file column “Volume” and enter , vol.  in field Pre.:. Repeat the last step for file columns “Pages” (, p. ) and “ReferenceNotes” (, notes: ). After that the column should look as shown below. 

Click on Resource rights and in the center window the assignment data for the resource rights are displayed. Select “rights_text”. Click on From file to select the column “Author” as data source and enter ©  (Alt+0169 and a blank) in field Pre.:. Now click on the button at the end of line “rights_text”, select file column “DateYear” and enter ,  in field Pre.:. After that the column should look as shown below. 

In the import step Resource variant click on Resource link. The center window shows the data column “url”. Click on to make this the decisive column and on From file in the “url” line to select file column “FileName”. Double-click on the text box after Pre.: to open a separate edit window. Here enter the web address of the picture server where the files are located and confirm with “OK”. After that the column should look as shown below.

Click on Variant type. In the center window select the data column “variant_id”, click on For all: and select the value “good quality” (see below).

Click on the import step Resource variant to find some ungrouped fields. In the center window select the data column “pixel_width”, click on From file and select the value “WidthD”. Now select the data column “pixel_height”, click on From file and select the value “HeightD”. Finally select the data column “mime_type”, click on From file and select the value “FileName”. Click on button to define a transformation. In the transformation window click on the cut transformation, enter Position: 2, click on to enter splitter character . (period) to extract the file extension. Now click on to insert a translation table and to insert the values contained in the file column. “gif” shall be converted to image/gif, “jpg”  will become image/jpeg (see below).

After that the columns should look as shown below.

 

Testing

To test if all requirements for the import are met use the Testing step. The test for the first data line is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. As mentioned in the introduction, the import step has to be repeated until no more resource variant is imported. At the first run 789 lines were imported (see below).

At the second run, started by another click on Start import, 152 lines were imported (see below).

Finally, at the seventh run no further line is imported (see below).

 

May 16, 2024

Wizard Advanced Tutorial Step Overview

Overview of the data tables and necessary import steps

From the original database several tables have been extracted that contain the descriptor names, categorical state names and description names, together with their internal IDs in the foreign database. Additionally there is a table that assigns picture IDs to the IDs of descriptors, categorical states and descriptions. The last table connects the picture IDs to file names. In DiversityDescriptions resources are represented by the tablese “Resource”, which holds some general information and is linked to descriptors, categorical states or descriptions. Table “Resource variant” holds the URL of the resources and each table row is assigned to one entry in table “Resource”.

Find below a part of the table “Deemy_RSC.txt”, which corresponds quite well to the table “Resource” in DiversityDescriptions. It references either to a description (“ItemID”), a descriptor (“CharID”) or a categorical state (“StateID”). 

The value in column “Resource” corresponds to column “PID” of the table “Deemy_IMG.txt” (see below), where the picture file name is specified. Since all pictures are accessible over a URL containing that file name, this table can be used for import to data table “Resource variant” in DiversityDescriptions. 

To import the picture data, first the data in table “Deemy_RSC.txt” must be appended to the existing descriptors, categorical states and descriptions. Then the data from table “Deemy_IMG.txt” must be appended to the resource entries. Since the basic data are imported from a DELTA file, no mapping information have been stored, which are needed to append the resource data. Therefore at first the mapping information must be imported from three additional tables. 

 

Mapping data

To allow appending of resource data to the existing database objects, we first must create the mapping information of the external IDs of the foreign database to the actual IDs in DiversityDescriptions. Find below the table “Deemy_Char.txt”, which contains the descriptor name (“CharName”), the internal “CharID” and an external “CID”. 

For the picture import each descriptor must be mapped to its “CharID”, which can be done by a special mapping import available in the Import session form. When we now take a look at the “Deemy_CS.txt” (see below), which contains the categorical state data, we discover a problem: The categorical states contain the required “StateID”, but they are connected to their descriptors by the value “CID”, not “CharID”.

This problem can be solved by importing the descriptor mapping twice: First the descriptor mapping is imported by using the “CID” and the categorical states are appended to the descriptors. Then the descriptor mapping is cleared and imported again, this time using the final value from column “CharID”.

The last table is “Deemy_Item.txt”, which contains the mapping information for the descriptions. Here the data column “ItemID” must be mapped to the descriptions (see below).

 

Next: Step 1 - Preparations: Data import from DELTA file and new import session 

May 3, 2024

Wizard Columns

Import wizard - Columns

If the content of a file should be imported into a certain column of a table, mark it with the checkbox.

 

Decisive columns

The import depends upon the data found in the file where certain columns can be choosed as decisive, that means only those lines will be imported where data are found in any of these columns. To mark a column as decisive, click on the icon at the beginning of the line (see below).

In the example shown below, the file column Organims 2 was marked as decisive. Therefore only the two lines containing content in this column will be imported.

 

Key columns

For the options Merge, Update and Attach the import compares the data from the file with those already present in the database. This comparision is done via key columns. To make a column a key column, click on the icon at the beginning of the line. You can define as many key columns as you need to ensure a valid comparision of the data.

 

Source

The data imported into the database can either be taken From file or the same value that you enter into the window or select from a list can be used For all datasets. If you choose the From file option, a window as shown below will pop up. Just click in the column where the data for the column should be taken from and click OK (see below).

If you choose the For all option, you can either enter text, select a value from a list or use a checkbox for YES or NO.

 

Transformation

The data imported may be transformed e.g. to adapt them to a format demanded by the database. For further details please see the chapter Transformation.

 

Copy

If data in the source file are missing in subsequent lines as shown below,

you can use the Copy line option to fill in missing data as shown below where the blue values are copied into empty fields during the import. Click on the button to ensure that missing values are filled in from previous lines.

 

 

Prefix and Postfix

In addition to the transformation of the values from the file, you may add a pre- and a postfix. These will be added after the transfromation of the text. Double-click in the field to see or edit the content. The pre- and a postfix values will only be used, if the file contains data for the current position.

For the datatype geography the pre- and postfixes will be automatically set to enable the import. The preset values by default are set for points as geographical units. You may change this to predefined types like lines or areas. Click on the button at the end of the line to open the information window. Here you can choose among the types mentioned above (see below).  

 

Column selection

If for any reason, a column that should take its content from the imported file misses the position of the file or you want to change the position click on the button. In case a position ist present, this button will show the number of the column. A window as shown below will pop up where you can select resp. change the position in the file.

 

Multi column

The content of a column can be composed from the content of several columns in the file. To add additional file columns, click on the button. A window as shown below will pop up, showing you the column selected so far, where the sequence is indicated in the header line. The first colum is marked with a blue background while the added columns are marked with a green background (see below).

To remove a added column, use the button (see below).

 

Information

The button opens a window displaying the informations about the column. For certain datatypes additional options are included (see Pre- and Postfix).

Jan 14, 2025

Wizard Transformation

Import wizard - transformation

The data imported may be transformed e.g. to adapt them to a format demanded by the database. Click on the button to open a window as shown below.

Here you can enter 4 types of transformation that should be applied to your data. Cut out parts,  Translate contents from the file, RegEx apply regular expressions or Replace text in the data from the file. All transformations will be applied in the sequence they had been entered. Finally, if a prefix and/or a postfix are defined, these will be added after the transformation. To remove a transformation, select it and click on the button.

 

Cut

With the cut transformation you can restrict the data taken from the file to a part of the text in the file. This is done by splitters and the position after splitting. In the example below, the month of a date should be extracted from the information. To achieve this, the splitter ‘.’ is added and than the position set to 2. You can change the direction of the sequence with the button Seq starting at the first position and starting at the last position. Click on the button Test the transformation to see the result of your transformation.

 

Translate

The translate transformation translates values from the file into values entered by the user. In the example above, the values of the month cut out from the date string should be translated from roman into numeric notation. To do this click on the button to add a translation transformation (see below). To list all different values present in the data, click on the button. A list as shown below will be created. You may as well use the and buttons to add or remove values from the list or the button to clear the list. Than enter the translations as shown below. Use the save button to save entries and the Test the transformation button to see the result. 

To load a predefined list for the transformation use the button. A window as shown below will open. Choose the encoding of the data in you translation source, if the first line contains the column definition and click on the  button to open a file. Click OK to use the values from the file for the translation.

To load a database table for the transformation use the button (see main translation window above). A window as shown below will open, where you may select a database table for the translation. Choose the table and the columns for the translation. Click OK to use the values from the table for the translation. Only unique values from the table will be used to ensure an unequivocal translation.

The values of the database table will be listed underneath as shown below. For the translation will only be regarded if the manual list does not contain the corresponding table. That means that content in the manual table will overwrite corresponding content in the database table. To remove the database table use the button.

 

Regular expression

The transformation using regular expressions will transform the values according to the entered Regular expression and Replace by vales. For more details please see documentations about regular expressions.

 

Replacement

The replacement transformation replaces any text in the data by a text specified by the user. In the example shown below, the text “.” is replaced by “-". 

 

Calculation 

The calculation transformation performs a calculation on numeric value, dependent on an optional condition. In the example below, 2 calculations were applied to convert 2-digit values into 4 digit years.

 

Filter 

The filter transformation compares the values from the file with a value entered by the user. As a result you can either Import content of column in file or Import a fixed value. To select another column that should be compared, click on the button and choose a column from the file in the window that will open. If the column that should be compared is not the column of the transformation, the number of the column will be shown instead of the symbol. To add further filter conditions use the button. For the combination of the conditions you can choose among AND and OR. 

 

Color 

The color transformation offers the transformation of color values between the three formats HEX values (#rrggbb), decimal value triples (rrr, ggg, bbb) and (negative) integer numbers. 

 

May 3, 2024

Wizard Tutorial

Import wizard - tutorial

This tutorial demostrates the import of descriptors and descriptions from two tabulator separated files into the database. The original data were stored in an MS-Excel sheet with data from an agricultural survey. The first table contains a list of questions and data like expected type of the answer, possible values and the measurement unit in case of numeric values (see image below).

The second table contains the answers of three individuals that are identified by a numeric value (see image below).

By using the option “Save as unicode text” the tables can easily be exported as tabulator separated text files (“Survey_Questions.txt” and “Survey_Answers.txt”). The import is done in seven steps and demonstrates various features of the import wizard. The tabulator separated text files and import schemas are available in the tutorialfiles in folder “Agricultural survey” or may be downloaded from the Diversity Descriptions example filerepository

 

Step 1 - Preparations: New project and descriptor tree 

Step 2 - Import of descriptors 

Step 3 - Insert recommended values of descriptors 

Step 4 - Import of categorical states for boolean data 

Step 5 - Import of categorical states and update of descriptor 

Step 6 - Import of descriptions 

Step 7 - Import of description data 

Epilogue 

 

See the second part of the import wizard tutorial to learn more about some advanced functions of the import wizard. 

 

Jan 14, 2025

Subsections of Wizard Tutorial

Wizard Tutorial Step 1

Step 1 - Preparations: New project and descriptor tree

Choose Edit → Projects from the menu and create a new project by clicking the button. Now click on button to enter the project name “Agricultural survey”. After entering the name the project will automatically be saved and the display will be updated (see below).

Change to tab “Descriptor tree”, mark project “Agricultural survey” in section “Descriptor tree” and press button to insert a new tree. Change the tree name to “Main tree for Agricultural survey” and click button to save all changes (see below).

 

 

Next: Step 2 - Import of descriptors 

May 16, 2024

Wizard Tutorial Step 2

Step 2 - Import of descriptors

Choose Data → Import -> Import wizard -> Import descriptors … from the menu. A window as shown below will open to create a new import session. Select project “MycoPhylogenyNet” and enter a session description.

After clicking [OK] the following window opens that will lead you through the import of the descriptor data. The window is separated in three areas. On the left side, you see a list of possible data related import steps according to the type of data you choosed for the import. On the right side you see the list of currently selected import steps. In the center part the details of the selected import step are shown.

 

Choosing the File

As a first step, choose the File from where the data should be imported. Open file “Survey_Questions.txt”. The preselected encoding ANSI should be sufficient for our test file. The file column “QuestionText” contains the descriptor names that shall be imported. In file column “QuestionNumber” there is a unique number assigned to each descriptor that will be used by other data tables to reference a certain descriptor. “Type” might give a hint for the descriptor type (categorical, quantitative or text) and “DisplayOrder” may be used to determine the sequence number of the descriptor.

 

Selecting the data ranges

In the selection list on the left side of the window all possible import steps for the data are listed according to the type of data you want to import.

The step Descriptor is already selected and cannot be de-selected, additionally we select Descriptor node, because we want to assign each imported descriptor to a descriptor tree (see above). In the step table at the right side you find the import step Descriptor and below the most important data groups of the import step. Click on Descriptor ID and in the center window the assignemt data for the descriptor id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “QuestionNumber” as data source. After that the column should look as shown below.  

Remark: The Descriptor ID is a number that is generated automatically from the database when a new descriptor is created. Anyway in the data file there is a field “QuestionNumber” that is linked to a certein descriptor and used in other tables to reference a certain descriptor. The mapping from the “QuestionNumber” values to the internally generated Descriptor ID values will be stored in a separate import mapping table for the actual import session. In the later import steps this mapping table will allow to find the correct descriptor assigned to a certain “QuestionNumber”.

Now the descriptor name must be selected, therefore click on Descriptor name. The center window shows three data columns: “label”, “abbreviation” and “detail”. Click on From file in the “label” line to select file column “QuestionText” (see below).

Next click on Sequence number. In the center window select the data column “display_order”, click on From file and select file column “QuestionNumber”. (see below).

As already mentioned before the file column “Type” contains information that can be used to determine the descriptor type. Therefore click on Subclass, select the “subclass” line, click on From file and select the file column “Type”. Now click on button to open the transformation window. As only transformation step select to insert a translation table and to list the values contained in the file column. “Bool” shall be converted to “Categorical descriptor”, “Integer” and “Real” will become “Quantitative descriptor” and the rest “Text descriptor” (see below).

The file rows that contain entries in column “Values” seem to specify categorical descriptors but are simply inserted as text characters. We will correct those values when we import the categorical states in a later step. The “subclass” data column now looks as shown below.

The descriptor step at the right displays the most important data columns grouped in separate steps. Anyway, there are several additional data columns available that can be accessed by clicking on the Descriptor step itself. Here we select data column “measurement_unit”, choose file column “Unit” (see below).

To do the assignment of the imported descriptors to the descriptor tree that was created in the preparation step, select Descriptor node ID from step Descriptor node and supply it exactly the samy way as the Descriptor ID. (Don’t forget to click on to make it the decision column.) Furthermore supply the Sequence number in the same way as described above.

Finally select import step Descriptor tree, select data column “descriptortree_id”, choose For all:  and select entry “Main tree for Agricultural survey” from the drop down (see below). With this adjustment every imported descriptor will automatically be assigned to that descriptor tree.

Remark: Although descriptortree_id is a numeric value in the database, the externally visible descriptor tree name is expected here. Since this name is unambigious, the corresponding id will be determined during import.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window. In our example no error occured and the test for the first data line is shown below.

You can see that in table “Descriptor” for data column “id” a new value 325050 is generated - remember that from file column “ParamID” the value 1 was selected. The mapping of the external value (1) to the internal value (325050) in table “Descriptor” will be stored in the “ImportMapping” table of the actual import session. I.e. if in a subsequent import step for the same session a “Descriptor.id=1” is specified in the import schema, it will automatically be translated to the internal “Descriptor.id=325050”. Anyway, usually you do not have to take care about this automatic translation. This example shall only demonstrate the meaning of the import sessions.

Remark: Since testing works with transaction rollback, the “id” values shown in the test window are different from the values resulting from a real import.

As a second example data line 4 with “DataType=Integer” was selected to demonstrate that the descriptor subtype is correctly set to “quantitative” (see below).    

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

Schedule for import of tab-separated text files into DiversityDescriptions
Target within DiversityDescriptions: Descriptor
Schedule version: 1 Database version: 03.00.17
Lines: 2 - 10 First line contains column definition:
Encoding: ANSI Language: US

Tables

Descriptor (Descriptor)
Merge handling: Insert

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
id ? 0 File
label 1 File
display_order 0 File
subclass 2
Translate Into
Bool categorical
Integer quantitative
Real quantitative
Text text
File
measurement_unit 4 File

DescriptorTreeNode (DescriptorTreeNode)
Parent: Descriptor
Merge handling: Insert

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
id ? 0 File
display_order 0 File
descriptortree_id Main tree for Agricultural survey Interface
descriptor_id ParentTable

Lines that could not be imported will be marked with a red background while imported lines are marked green.

If you want to save lines that produce errors during the import in a separate file, use the “Save failed lines” option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

 

Next: Step 3 - Insert recommended values of descriptors 

May 16, 2024

Wizard Tutorial Step 3

Now we have imported the descriptors and assigned them to a descriptor tree. Since we have several quantitative descriptors, we should at least assign one recommended statistical measure to these descriptors. In this step we will additionally insert recommended modifier and frequency vales. If your database does not yet include modifier and frequency values, you might like to interrupt here and insert them according chapter  Edit projects - Modifier/Frequencytab of this manual. 

Finally we want to set the “values_are_integer” flag for the descriptor, that is specified as “Integer” in the file column “Type”. We could have done this during the previous import step, but here we can demonstrate the update existing data sets with the import wizard. 

In the selection list on the left side of the window select Rec. stat. measure 1 Rec. modifier 1 and Rec. frequency 1 (see below).

In this step we attach the recommended values to all descriptor nodes, therefore we will not change anything in the descriptor or descriptor node but will attach data. In import step Attachment at the right side select id (see below). 

Select the import step Merge from the list. For Descriptor we select the Update option because the “values_are_integer” column shall be updated. For Descriptor node we select the Attach option because this tables shall not be changed. For all other steps Insert should already be selected, because new entries have to be inserted (see below).

Deselect every column from import steps Descriptor and Descriptor node except “id”. Mark the “id” columns as Key column for comparison during attachment. The “id” column of import step Descriptor now looks as shown below.

The “id” column of import step Descriptor node now looks as shown below.

 

Selecting the values

In the step table at the right side click on the import step Rec. stat. measure 1 and in the center window the assignemt data for the statistical measure (“measure_id”) are displayed. Click on to make this the decisive column, further click on For all: and select entry “Central or typical value (human estimate)” from the drop down (see below).  

Select values for Rec. modifier 1 and Rec. frequency 1 in the same way, the actually selected modifier and frequency values do not matter for this tutorial (see below). 

Remark: Although measure_id, modifier_id and frequency_id are numeric values in the database, the externally visible names are expected here. Since this names are unambigious, the corresponding ids will be determined during import.

If you want to insert more than one recommended value of a type, click on button of the import step at the left side of the window. Select the new inserted step and supply the “measure_id”, “modifier_id” or “frequency_id” as described above.

Now we will enter the update of the “values_are_integer” data column. Select the import step Descriptor and select the “values_are_integer” line. Click on From file and select the file column “Type”. Now click on button to open the transformation window. As only transformation step select to insert a translation table and to insert the values contained in the file column. For “Integer” the data column value shall be set to “yes” as shown below.

The “values_are_integer” column of import step Descriptor now looks as show below.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window. In our example no error occured and the test for the fifth data line is shown below. 

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. The imported data lines are marked green (see below).

 

Next: Step 4 - Import of categorical states for boolean data 

Jan 14, 2025

Wizard Tutorial Step 4

Step 4 - Import of categorical states for boolean data

Now we want to import categorical states for the descriptors specified as “Bool” in the table. In the selection list on the left side of the window deselect Descriptor node, Rec. stat. measure 1 Rec. modifier 1 and Rec. frequency 1. Select Categorical state 1, click on the button to insert a second categorical state and select it, too (see below).

In this step we attach two categorical states named “Yes” and “No” at those descriptors that are marked as “Bool” in file column “Type”. The state values are not present in the “Survey_Questions.txt” file, but in the “Survey_answers.txt” files we can see the values. In import step Attach at the right side we select id (see below). It indicates that we do not want to insert new descriptors but attach data to an existing descriptor.

Select the import step Merge from the list. For Descriptor we select the Attach option because this table shall not be changed, for Categorical state 1 we select Insert, because a new entry shall be inserted (see below).

Deselect every column from import step Descriptor except “id”. Mark the “id” column as Key column for comparison during attachment (see below).

 

Inserting the categorical states

In the import step Categorical state 1 click on Categorical state ID and in the center window the assignemt data for the categorical state id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “Type” as data source. Now click on button to define a transformation. In the tranformation window click on to select a filter, then select Import fixed value and enter the value Yes. Now click on the button choose column “Type” from the file and enter compare value Bool (see below).

This filter has the following effect: If file column “Type” contains value “Bool”, the value Yes is provided for import, otherwise the file row will be ignored. The column now looks as shown below.  

Remark: The Categorical state ID is a number that is generated automatically from the database when a new categorical state is created. At first sight it seems confusing that we select a string for this numeric key. The point is that in the file with the description data the corresponding catogorical state is idenified by exactly this categorical state name. Since we select this categorical state name for the Categorical state ID, the mapping between these two values will be stored in a separate import mapping table for the actual import session. In the later import steps this mapping table will allow to find the correct categorical state.

In the import step Categorical state 1 click on Categorical state name and in the center window the assignemt data for the categorical state name (“label”), its abbreviation and detailled description (“abbreviation” and “details”) are displayed. Select “label” and click on For all: and enter the value Yes. The column now looks as shown below.

Finally we supply the Sequence number. Select For all: with 1 (see below).

 

In the import step Categorical state 2 click on Categorical state ID and in the center window the assignemt data for the categorical state id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “Type” as data source. Now click on button to define a transformation. In the tranformation window click on to select a filter, then select Import fixed value and enter the value No. Now click on the button choose column “Type” from the file and enter compare value Bool (see below).

This filter has the following effect: If file column “DataType” contains value “Bool”, the value No is provided for import, otherwise the file row will be ignored. The column now looks as shown below.  

In the import step Categorical state 1 click on Categorical state name and in the center window the assignemt data for the categorical state name (“label”), its abbreviation and detailled description (“abbreviation” and “details”) are displayed. Select “label” and click on For all: and enter the value Yes. The column now looks as shown below.

Finally we supply the Sequence number. Select For all: with “2” (see below).

 

Testing

To test if all requirements for the import are met use the Testing step. First the test for data line 2 is shown below, which is an example for a non “Bool” descriptor.

No data shall be inserted. Below the test result for data line 8, a “Bool” descriptor, is shown.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. The imported data lines are marked green, the ignored data lines grey (see below).

 

Next: Step 5 - Import of categorical states and update of descriptor 

May 3, 2024

Wizard Tutorial Step 5

Step 5 - Import of categorical states and update of descriptor data

Now we want to import the categorical states that are specified in file column “Values” and set the subclass for those descriptors from “text” to “categorical”. In the selection list on the left side of the window Descriptor, Categorical state 1 and Categorical state 2 are still selected and Descriptor node 1 is deselected (see below). Furthermore the descriptor id is selected for attachment.

Since we want to change the descriptor data, we have to change the import step Merge from the list. For Descriptor we select the Update option (see below).

In the import step Descriptor click on Subclass, select file column “Values” and click on button to open the transformations. By clicking the button the transformations of previous steps are removed. In the tranformation window click on to select a filter, then select Import a fixed value and enter the value categorical. Now click on the button choose column “Values” from the file and select <not equal> blank (see below).

This filter will provide the value “categorical” for database column “subclass” if file column “Values” is not empty. If “Value” is empty, no value is provided and the “subclass” stays unchanged. The column now looks as shown below.

 

Inserting the categorical states

A closer look on the “Values” file column shows that the states are provided as a list of values separated by the pipe symbol and blanks (" | “). To get the single state values, we have to split off a value at the string " | “. This value will then be used for the Categorical state ID and the Categorical state name.

In the import step Categorical state 1 click on Categorical state ID and in the center window the assignemt data for the categorical state id (“id”) are displayed. Click on to make this the decisive column, further click on From file to select the column “Values” as data source. Now click on button to define a transformation.

In the tranformation window click on the cut transformation, enter Position: 1, click on to enter splitter character  |  (blank, pipe, blank). By clicking on button [Test the tranformation] you can check the transformation results (see below).

The column now looks as shown below.  

Remark: The Categorical state ID is a number that is generated automatically from the database when a new categorical state is created. At first sight it seems confusing that we select a string - the catigorical state name - for this numeric key. The point is that in the file with the description data the corresponding catogorical state is idenified by exactly this categorical state name. Since we select this categorical state name for the Categorical state ID, the mapping between these two values will be stored in a separate import mapping table for the actual import session. In the later import steps this mapping table will allow to find the correct categorical state.

Now supply exactly the same filter settings for Categorical state name but do not mark it as decisive column (see below).

Finally we supply the Sequence number. Select For all: with 1 (see below).

And now there is some “fun”:

The longest entry in column “Values” contains four entries separated by pipes and blanks. Therefore click two more times on the button of step Categorical state 1 on the left side and select the new steps Categorical state 3 and Categorical state 4. For each of the remaining steps supply the columns in the same way as for Categorical state 1, but increase the Position: value in the cut transformations and the For all: value in  Sequence number.  

 

Testing

To test if all requirements for the import are met use the Testing step. The test for data line 9, where all eleven descriptor states are present, is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. There were 4 lines that contained descriptors (see below).

 

Next: Step 6 - Import of descriptions 

May 3, 2024

Wizard Tutorial Step 6

Step 6 - Import of descriptions

Choose Data → Import -> Wizard -> Import descriptions … from the menu. A window as shown below will open to select an import session. Select session for project “MycoPhylogenyNet”.

After clicking [OK] the following window opens that will lead you through the import of the description data.

 

Choosing the File

Choose step File an open file “Survey_Answers.txt”. The chosen encoding ANSI of the file should be sufficiend. The file column “ClientNumber” contains the description names that shall be imported. Since there are no other description specific data, the same column will be used for the as unique ID to identify each description. 

 

Selecting the data ranges

In the selection list on the left side of the window all possible import steps for the data are listed according to the type of data you want to import.

Since each description name rsp. ID occurs in several lines of the file, subsequent tries to import the same description would cause errors, if the standard merge handling Insert was used.  We have to change the import step Merge from the list. For Description we select the Merge option (see below).

The step Description is already selected and cannot be de-selected (see above). In the step table at the right side you find the import step Descriptor and below the data groups of the import step. Click on Description ID and in the center window the assignemt data for the description id (“id”) are displayed. Click on to make this the decisive column and on to allow the merge comparison, further click on From file to select the column “ClientNumber” as data source. After that the column should look as shown below.  

Now the description name must be selected, therefore click on Description name. The center window shows two data columns: “label” and “detail”. Click on From file in the “label” line to select file column “ClientNumber”. After that the columns should look as shown below.

Finally select import step Project, select data column “project_id”, choose For all:  and select entry “Agricultural survey” from the drop down (see below). With this adjustment every imported description will automatically be assigned to that project.

Remark: Although project_id is a numeric value in the database, the externally visible project name is expected here. Since this name is unambigious, the corresponding id will be determined during import.

 

Testing

To test if all requirements for the import are met use the Testing step. The test for the first data line is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. There were three different descriptions (see below).

 

Next: Step 7 - Import of description data 

May 16, 2024

Wizard Tutorial Step 7

Step 7 - Import of description data

In this step we attach categorical, quantitative and text data to the descriptions. In import step Attach at the right side we select id (see below). It indicates that we do not want to attach data to an existing description.

Select the import step Merging from the list. For Description we select the Attach option because this table shall not be changed (see below).

Deselect every column from import step Description except “id”. The “id” column was already marked as Key column for comparison in the previous step. Now the column looks as shown below.

 

Inserting text descriptor data

We will now include the text, quantitative, categorical and status data step by step. First we will attach the text descriptor data. Select the Text descriptor 1 step at the left (see below).

At the right side you find the import step Text descriptor 1 and below the data groups of the import step. Click on Descriptor ID and in the center window the assignemt data for the referenced descriptor’s id (“descriptor_id”) are displayed. Click on From file to select the file column “QuestionNumber” as data source. After that the column should look as shown below.  

Now the description text must be selected, therefore click on Text. The center window shows two data columns: “content” and “notes”. In line “content” click on to make it the decisive column, further on From file to select file column “Answer”. In line “notes” click on From file to select file column “Notes”. After that the columns should look as shown below.

 

Testing the text descriptor data import

To test if all requirements for the import are met use the Testing step. The test for the first data line is shown below.

An additional test is done for the next data line. This line contains no text data but a categorical state. You can see below that this line will not be imported as text descriptor data, because the descriptor (given by Descriptor ID) is automatically checked for the correct type.

 

Inserting quantitative summary data

We will now include the quantitative summary data. Select the Quantitative data 1 step (see below).

At the right side you find the import step Quantitative data 1 and below the data groups of the import step. Click on Descriptor ID and select the file column “QuestionNumber” as data source.

Now the value must be selected, therefore click on Value. The center window shows two data columns: “value” and “notes”. In line “value” click on to make it the decisive column, further on From file to select file column “Answer”. In line “notes” click on From file to select file column “Notes”. After that the columns should look as shown below.

For quantitavie measures you must specify which statistical measure is given by the value. We assume all imported values are mean values, therefore click on the import step Statistical measure and in the center window the assignemt data for the statistical measure (“measure_id”) are displayed. Click on For all: and select entry “Central or typical value (human estimate)” from the drop down (see below).  

 

Testing the quantitative summary data import

To test if all requirements for the import are met use the Testing step. The test for data line 25 with integer data is shown below.

The test for data line 25, which contains real number fails (see below).

A closer look on the data in column “Answer” shows that the decimal separator is a comma, because the table has been generated by a progam using the German localization. The database expects a decimal point as separator. To interpret the localized file values correctly, select the step File and choose Language / Country: de (see below).

With this settings the test now works fine (see below).

 

Inserting categorical summary data

Now we will include the categorical summary data. Select the Categorical data 1 step at the left (see below).

At the right side you find the import step Categorical data 1 and below the data groups of the import step. Click on Categorical state ID. The center window shows the data column “state_id”. Click on to make it the decisive column, further on From file to select file column “Answer”. If you perform a quick import test you will see that this setting works perfectly for data file lines 3, 4 and 6, but fails for line 8 (see below).

The reason is that we used the state name as external key for the categorical state. For the descriptors 6 and 8, which both represent boolean values, the states names are ambigious (“Yes” and “No” for both descriptors), therefore the import wizard does not know which descriptor shall be used. To overcome this ambiguity the Categorical state ID step allows the additional specification of the descriptor id. Select import step Categorical state ID. In the center click on the button at the end of line “state_id”. Select file column “QuestionNumber”, which contains the reference to the descriptor and enter the separator character | (pipe symbol) in field Pre.: of the new line. After that the column should look as shown below.

If you repeat the quick import test for line 8, it will now work.

Now click on Notes. The center window shows the data column “notes”. Click on From file to select file column “Notes”. After that the columns should look as shown below.

 

Testing the categorical summary data import

To test if all requirements for the import are met use the Testing step. The test for data line 15 with categorical data and notes is shown below.

 

Inserting the descriptor status data

There is an empty lines in the file. For this line we want to set the descriptor status “Data unavailable” to indicate that the descriptor should be present in the description. Select the Descriptor status 1 step at the left (see below).

At the right side you find the import step Descriptor status 1 and below the data groups of the import step. Click on Descriptor ID and select the file column “QuestionNumber” as data source. Furthermore click on Notes and select the file column “Notes”. 

Now click on Data status. The center window shows the data column “statusdata_id”. Click on to make it the decisive column, further on From file to select file column “Answer”. Now click on button to define a transformation. In the tranformation window click on to select translation. In the translation window click the button to list the values contained in the file column. For the empty entry in the first line select the translation value “Data unavailable” (see below). All data entries will therefore be mapped to “empty”, i.e. no data status will be set. Only if the data file line ist empty, the selected data status will be inserted.

 

Testing the descriptor status data import

To test if all requirements for the import are met use the Testing step. The test for data line 16 is shown below.

 

Import

With the last step you can start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings. There were 26 lines imported and one failed line (see below).

The erroneous lines are stored into separate text file (e.g. “Survey_AnswersError.txt”) for a detailled analysis and a separate import after error corrections. In our example the error is caused by the undefined value “Cereals” in the “Answer” column of file line 24.  

 

Next: Epilogue 

Jan 14, 2025

Wizard Tutorial Step Epilogue

Epilogue

When you close the import wizard and start a query for descriptions of project “Agricultural survey” you will find the three datasets and the imported descriptor data (see image below). 

Finnally two more aspects of the imports wizard shall be discussed from a retrospective view. The first one concerns the mapping of external and internal keys and the role of the import session. The second one takes a closer look on the role of the “ID” columns during import. 

 

Mapping of external and internal keys

When opening the import wizard you have to select rsp. create an import session. Imports into Diversity Descriptions usually require at least two import operations, e.g. for descriptors and descriptions. The description data reference descriptors or categorical states. Within the database those relations are built based on numeric values that are provided by the database during creation of the corresponding objects. In the external data files the relations are usually built by numbers coordinated by the user (“QuestionNumber”) or by the entity names.

The import session stores the external and internal key values in separate database tables and therefore builds a bracket around the different import operations. Each import session is assigned to one project, but for each project several import sessions may be created. The mapping data may be viewed by opening the menu item Data -> Import -> Wizard -> Organize sessions …, selecting the session and clicking the button Mapping (see image below).

 

 

Selecting import columns for the “ID” fields

As an addition to the tutorial steps a closer look on the role of the “ID” fields shall be taken. In principle the most important IDs during import concern the Descriptor ID and the Categorical state ID during descriptor import. To decide which file column shall be used for that values during import, it is important to know how these elements are referenced in the other files.    

For the descriptor import, you should take a look at the description data table (see above), which is part of the tutorial example. The descriptor is referenced by column “QestionNumber”, which matches homonymous column of the descriptor data table (see below). Therefore the natural approach is to use this column as input for the Descriptor ID during the descriptor import. Since in most practical cases the descriptors will have a numbering column, which is used in the referencing table. Surely more variety exists in the way the categorical states are listed in the descriptor data file and the way they are referenced by the description data file.  

In the tutorial the first complication is that the possible states are all concatenated, separated by a semicolon, into a single column of the descriptor data file. This causes some effort in the transformation, because the states have to be splitted into the single values. The question is, what is the Categorical state ID? The answer can be found in the upper table, because the state name is explicitely mentioned in the description data file as reference. I.e. for the descriptor import the state name must be used for the Categorical state ID, too.

In Diversity Descriptions the categorical state names must be unique in relation to their descriptor. But different descriptors may have states with the same names. In our example this situation occures with the two boolean descriptors (states “Yes” and “No”) and the state value “Others”, wich is used by two descriptors. Therefore it is generally recommended to specify the descriptor for the import of categorical summary data as demonstrated in the tutorial. 

 

 

May 3, 2024

Translations

Translations

For each project a default language is selected in the Edit project panel. In Diversity Descriptions for most database entries additionally translated expressions can be stored in the Translation table. Even for the default language adjusted for the project alternate expressions may be entered. In several export and document generation forms it is possible to select an alternate output language, if translations are available. Translatable entities are listed in the following table.

Database table Database columns
CategoricalState label, detail, abbreviation, wording
DataStatus_Enum label, detail, abbreviation
Description label, detail, wording
Descriptor label, detail, abbreviation, wording_before, wording_after, wording
DescriptorTree label
DescriptorTreeNode label, detail, abbreviation
Frequency label
Modifier label
OtherScope label, detail
Project label, detail
Resource label, detail
ResourceVariant_Enum label, detail
SamplingEvent label, detail
SexStatus_Enum label, detail, abbreviation
StatisticalMeasure_Enum label, abbreviation

All mentioned entities may be edited using the translationseditor. If for an output a translation language is specified, a situation may occur that for a certain entity not translation is stored in the database. In those cases automatically the original database values will be used. 

As you can see in the table above, no translations are supported for the descriptive data, i.e. summary or sampling data. Concerning categorical data, there is a tranlsation support, because the terminology parts (Descriptor and CategoricalState) my be translated. Quatitative data mainly include numeric values and their statistical measure, where the measure texts themselves can be translated. The same is valid for descriptor status data. Molecular sequence data naturally do not contain any translatable texts. Finally only the contents of text descriptor data and notes, that can be included in any summary or sampling data, are not supported for translation.

 

Data export

The export format SDD is XML based and offers multilingual support. By default the document language ist set to the project default language and the original database entries (labels, detail texts and so on) are included without explicit language tag. If translations are stored in the database, they are included in the SDD output with their specific language tag. As an option translations may be completely excluded from export or the SDD document language may even be switched to one of the available translation languages. Please be aware, that the enumerated values (DataStatus_Enum, StatisticalMeasures_Enum and SexStatus_Enum) are identified by specific tags within SDD. Therefore the translations for these are not included in the SDD file! 

The export format DELTA is text based and does not support multilinguality. By default the original database entries are used in the DELTA output. If translations are stored in the database, you may select one of the available languages for the DELTA output.

In both cases the general rule applies that if for a certain term no translated value is present, the original value will be used. For details concerning the data export see here.

 

Data import

In the SDD import form the available languages are displayed. You have the options to omit translations during import or select a different language as the project’s default language. 

The DELTA import form offers the option to import translations for descriptors, categorical states and description items from separate DELTA files with identical structure. In a first step the complete data are imported form a main DELTA file. In subsequent steps the identifier for additional languages may be imported from additional language specific DELTA files. 

 

Document generators

The is a number of document generators to generate HTML or Media Wiki output. In this form an “Export language” field is shown if any translations are available in the database. In those cases you have the choice to adjust the default language or one of the offered tranlsations languages. Anyway, there may be some fixed expressions in the generated documents, where currently no mutilingual support is available.  

 

 

Jan 14, 2025

Subsections of Translations

Edit Language Codes

Edit language codes

In the Diversity Descriptions database language codes are used for two purposes: The first one is to indicate the project’s default language. Furthermore for the most important parts of the data translations may be entered, which carry a laguage code, too.

By all means the language codes consists of an at most three-letter string. In the application you may select the language code from a drop-down box, which shows the language code - in most cases a two-letter ISO 639-1 code - and the corresponding long name. By clicking the button you may change the display sequence (see images below).      

Most of the values are provided by the operating system. Anyway there might be the need to include additional values, e.g. “eo” for Esperanto. For those cases as a second source additional language codes may be stored in the application’s settings. Finally, language codes that are present in the database but neither included in the operating system’s list nor the application settings will be included at the end of the selection list with red background, if neccessary. 

To edit the language codes, click the button and a new window will open (see image below). The operating system’s entries are shown with a light blue background and cannot be modified. The language codes that are stored in the application settings are shown with white background and may be edited. To enter a new value, use the empty line at the end of the table. To delete an entry, mark the whole line by clicking on the row header and press the delete key on the keyboard. 

   

By clicking OK the changes will be stored in the settings.

Jan 14, 2025

Edit Translations

Editing translations

After connecting a database select Edit -> Translations … from the menu (see image below). You have to select the mandatory parameter Project and the Table. If you want to enter a new translation text, the Column and the target Language must be selected. If you omit one of those parameters, only existing tranlation texts from the database will be shown. Anyway the number of translations that match the currently selected criteria will be shown in field Translations in the upper right area of the form.

You man change the display and sorting of the entries in the Language combo box from “<code> - <description>” to “<description> - <code>” (and back) by clicking the button . If you need language codes that are not included in the list, click the button. For more details see Edit language codes.

With the numeric control Items you may adjust how many database items shall be selected for display. After clicking the button the query results are displayed. By clicking the buttons and you can load the next rsp. previous matches. 

When you select a Column, an additional text box Filter is activated, where you may restrict the displayed datasets to matching entries in the Original text (see image below). In field Start ID the first ID of the current output is shown. You may enter a dedicated value to be used for the next output. 

The table lists the internal ID of the data entry (“ID”), the table column (“Column”), the project language (“PL”), the “Original text”, the translation language (“TL”) and the “Translated text” (see image below). In table column “x” lines without write access will be marked as  x . If you have write access, you may enter the tranlated text directly in the table. 

   

You may copy the original text of selected lines to the translated text by clicking the button or delete the translated text with button . To select all translated texts click on button . In modified lines the background color of the first two columns will be change to yellow (see image below). With button you can save the modified data, with button you can reload the table, i.e. discard the changes. 

If you selected any Translated text entries, it is possible to modify several values simultaneously. Therefore select the table entries that shall be edited - by clicking the button you may select the whole table column. Then select the required operation in the Edit section: “Insert”, “Append” or “Replace” and enter the new rsp. new and old value. After clicking the action button - depending on the selected operation this is (Insert), (Append) or (Replace).

By double-clicking the table line or clicking the button you can open a separate edit window (see image below). This form works almost in the same way as the Extended text editor.

  

 

Jan 14, 2025

Summarize Data

Summarize data

Currently the following functions for summarizing data are available:

Summarize descriptions : Summarize the data of selected descriptions and create a new one or update an existing description.

Summarize sample data : Summarize the sample data of selected descriptions and update their summary data.

 

Summarizing methods

Depending on the selected summarizing function either the descriptor data of selected descriptions or the sampling data of the selected descriptions build the data source. Summarization of the data is done according their data type.

 

Categorical summary data

For building of categorical summary data the single categorical states of the data sources are accumulated. In general for each states test notes can be entered. To summarize the text notes, the different notes are accumulated (append in a new line), if they are not yet included in the summary note.

If modifier have to be processed, each combination of a categerical state and a modifier will be treated as separate values. Summarization of notes text will be done separately for each of these tuples. Only modifiers that are assigned to a descriptor as recommended modifier (see Editing the descriptor - Descriptor tree tab ) are evaluated, otherwise the modifier values are ignored.

Categorical descriptors may be marked as “exclusive”, which means that only on state may be selected. If the approptiate option is set for the summarization, the categorical states that is most often selected in the source data will be used in the target. 

 

Quantitative summary data

For building of quantitative summary data from the numeric values of the data sources all recommended statistical measures (see Editing thedescriptor - Descriptor tree tab ) for the processed descriptor are calculated. Text notes are accumulated for each statistical measure the same way as described for categorical summary data.

If modifier have to be processed, all the modifier are accumulated for eache statistical measure. Since in the resulting quantitative summary data only one modifier value is allowed for each statistical measure, the most often used modfier is inserted.

 

Text descriptor data

To summarize the text descriptor data, the different texts are accumulated (append in a new line), if they are note yet included in the summary text. Text notes are accumulated in the same way.

 

Molecular sequence data

To summarize the molecular sequence data, the different sequences are accumulated (append in a new line), if they are note yet included in the target sequence. Text notes are accumulated in the same way.

 

 

Jan 14, 2025

Subsections of Summarize Data

Statistical Measures

Statistical measures

The following table gives an overview of the available statistical measures. In column Calculation a hint is given, how the measuere is calculated from the basic data rows.

Name Abbr. Calculation
Lower range limit (human estimate) - x1..xn sorted list: x1
Upper range limit (human estimate) + x1..xn sorted list: xn
Central or typical value (human estimate) centr. x1..xn sorted list: xn/2
Lower range limit (legacy data stat. meth. unknown) -(?) x1..xn sorted list: x1
Upper range limit (legacy data stat. meth. unknown) +(?) x1..xn sorted list: xn
Central or typical value (legacy data stat. meth. unknown) centr.(?) x1..xn sorted list: xn/2
Minimum value Min Absolute smallest value
Maximum value Max Absolute largest value
Mean (= average) μ μ=(1/n)∑(n)xi
Harmonic mean hμ=n/(∑(n)(1/xi))
hμ=0 if any xi=0
Geometric mean gμ=n√∏(n)xi
Mode mode Value that appears most often (ambigious!)
Median med. x1..xn sorted list
n odd: med=x(n+1)/2
n even: med=(xn/2+x(n/2+1))/2
Interquartile mean (= average) IQM x1..xn sorted list
IQM=μ(x0.25n+1..x0.75n+1)
Variance (sample df = n-1) Var. Sn-1=(1/n-1)∑(n)(xi-μ)2
Variance (population; df = n; rarely applicable!) Var. (pop.) Sn=(1/n)∑(n)(xi-μ)2
Standard deviation (sample) s.d. σn-1=√Sn-1
Standard deviation (population; df = n; rarely applicable!) s.d. (pop.) σn=√Sn
Mean deviation m.d. md=(1/n)∑(n)|xi-μ|
Mean deviation from median m.d.m. mdm=(1/n)∑(n)|xi-med|
Coefficient of variation (sample) CV CV=σn
Corrected coefficient of variation (sample) CVC CVC=σn-1
Total range TR x1..xn sorted list
TR=xn-x1
Interquartile range IQR x1..xn sorted list
IQR=x0.75n+1-x0.25n+1
Standard error of mean s.e. σxn-1/√n
Standard error of variance (of multiple samples) s.e.(var.) Sx=Sn-1/n
Skewness Skw. ϒ1=(1/n)∑(n)((xi-μ)/σ)3
Kurtosis Kurt. Kurt=(1/n)∑(n)((xi-μ)/σ)4
Sample size n Number of values

 

Adjust display sequence

You may adjust the display sequence of the statistical measures for the whole database. Choose Administation -> Database -> Statistical measures … from the menu. A window will open as shown below.

  

The sequence number column (“No.”) determines the display sequence in various forms. You may order the entries by clicking on a column header. With the arrow buttons ( ) you can move the selected entries up or down within the table, clicking button or shifts the selected entries to the top respective bottom of the table. After ordering the entries click button to renumber the table entries (starting with “1” for the first table entry) and make the changes effective. To save the changes in the database, leave the form with the OK button, to discard all changes click the Abort button. 

 

May 3, 2024

Summarize Descriptions

Summarize description data

With this form you can summarize the information of selected descriptions and store the summarized data in a new description or update an existing one. After connecting a database select Edit -> Summarize descriptions … from the menu.

 

Description selection

 In the first tab Description selection you search for the source descriptions that shall be summarized into a new or an existing target description (see image below).

You have to select at least the mandatory parameter Project and start a query with button . From the result list superfluous entries may be removed with the button. For a detailled description of the query control please refer to section Query.

 

Descriptor selection

In tab Descriptor selection select the descriptors that shall be summarized in table column OK (see image below). You can select rsp. deselect all descriptors with buttons and . Button inverts all selections. To select all categorical, quantitative, text or sequence descriptors the buttons , , and are avaiable. With button you may select a descriptor tree rsp. descriptor tree node to select all descriptors assigned to the selected element.

   

For quantitative descriptors a statistical measure must be specified where the values for summarization are available. When the descriptor table is filled, for each quantitative descriptor the available recommended measures are checked if one of the measures “Mean (= average)”, “Central or typical value (human estimate)”, “Central or typical value (legacy data stat. meth. unknown)”, “Mode” or “Sample size” is available (priority in this sequence), it is pre-selected in colum Measure. You may modify this adjustment for each single descriptor or use button to change the setting for all selected descriptors. 

 

Generator options

In section Summarize options you may specify to Ignore notes and to Ignore modfier values of the source descriptions. If you select Restrict exclusive descriptors, the most often selected categorical state of a “exclusive” descriptor will be set instead of accumulating all source values. Accumulate scopes will collect all scope values, Accumulate resources all resources of the source descriptions to the target. Write item count will enter notes containing information about the number of collected items in the summary data. If you additionally select Write detailled notes, the source description IDs will be listed in the notes. Finally, Write summary infomation inserts a summary about summarized descriptions into the target description details (see image below).

In section Target description you may select the Target project (usually the same as the source description’s). You may either create a New description and enter the description name or Update a description selected form a drop-down list.  

In section Status data you may control the summarization behaviour for every descriptor data status value:

  • Ignore    
    If in a summarized description the corresponding data status is present for a descriptor value, it will be summarized but the descriptor data status will not be set in the target description.
  • Summarize
    As for Ignore the descriptor values will be summarized. Additionally the descriptor data status will be set in the target description.
  • Omit data
    If in a summarized description the corresponding data status is present for a descriptor value, it will not be summarized and the descriptor data status will not be set in the target description.

After checking the settings click in button Start generator . During processing the icon of the button changes to  and you may abort by clicking the button. In the Preview area a table with the generated rsp. updated target description (coloured background, may be change with button ) and the summarized source descriptions (grey background) is shown. If the target description has been modified, this is indicated ba a yellow background of the description title (see image above). Updated values are shown as blue text. By double-clicking on a field in the preview table you may view the contents in a separate browser window. To save the updated values and close the window click the OK button. To exit without saving click Abort. In this case you will be asked if you want to save modified data.

Since building the preview table may take some time, especially if a lot of descriptors have been selected, you may use the button Recalculate for restarting the summary process. In this case the descriptor columns will not be re-built, only the summary data will be calculated and actualized. This feature may be useful, if you change some settings an want to update the data. If you use the Recalculate button with an empty preview table, only the description titles will be displayed. Anyway you can view the summarized data using the button (see below).

You may store all changed entries by clicking the button or omit all changes and reload the data by clicking the button. To view the description details of the currently selected entry click the button and a separate browser window opens (see image below). 

  

 

Jan 14, 2025

Summarize Sampling Data

Summarize sample data

With this form you can summarize the information of selected descriptions and store the summarized data in a new description or update an existing one. After connecting a database select Edit -> Summarize sample data … from the menu.

 

Description selection

 In the first tab Description selection you search for the desriptions that shall be updated by their summarized sample data (see image below).

You have to select at least the mandatory parameter Project and start a query with button . From the result list superfluous entries may be removed with the button. For a detailled description of the query control please refer to section Query.

 

Descriptor selection

In tab Descriptor selection select the descriptors that shall be summarized in table column OK (see image below). You can select rsp. deselect all descriptors with buttons and . Button inverts all selections. To select all categorical, quantitative, text or sequence descriptors the buttons , , and are avaiable. With button you may select a descriptor tree rsp. descriptor tree node to select all descriptors assigned to the selected element.

   

 

Generator options

In section Summarize options you may specify to Ignore notes and to Ignore modfier values of the description’s sample data. If you select Restrict exclusive descriptors, the most often selected categorical state of a “exclusive” descriptor will be set instead of accumulating all source values. Accumulate scopes will collect all scope values of the sampling events (geographic areas) and sampling units (specimen) in the description summary. Write item count will enter notes containing information about the number of collected items in the summary data. If you additionally select Write detailled notes, the source description IDs will be listed in the notes. Finally, Write summary infomation inserts a summary about summarized sampling events into the target description details (see image below).

In section Descriptions and sampling events you find the descriptions from the query result list in tab Description selection and their sampling events. You may exclude single sampling events or even the whole description form the summarization. In the latter case the description data will not be changed.  

After checking the settings click in button Start generator . During processing the icon of the button changes to  and you may abort by clicking the button. In the Preview area a table with the updated target descriptions (coloured background, may be change with button ) and the summarized sampling units (grey background) is shown. If the target description has been modified, this is indicated ba a yellow background of the description title (see image above). Updated values are shown as blue text. By double-clicking on a field in the preview table you may view the contents in a separate browser window. To save the updated values and close the window click the OK button. To exit without saving click Abort. In this case you will be asked if you want to save modified data.

Since building the preview table may take some time, especially if a lot of descriptors have been selected, you may use the button Recalculate for restarting the summary process. In this case the descriptor columns will not be re-built, only the summary data will be calculated and actualized. This feature may be useful, if you change some settings an want to update the data. If you use the Recalculate button with an empty preview table, only the description titles will be displayed. Anyway you can view the summarized data using the button (see below).

You may store all changed entries by clicking the button or omit all changes and reload the data by clicking the button. To view the description details of the currently selected entry click the button and a separate browser window opens (see image below). 

  

 

Jan 14, 2025

Generate Document

Generate document

This tool is used to generate a structured documentation of database contents. To use this tool, start a query and choose Data →  Generate Document … from the menu. The entries of the query result will be passed to the form and depending on the query type (description, descriptor or project) different output options will be provided.

For details check the following pages:

    Generate a description data document

    Generate a descriptor data document

    Generate a project data document

 

Translations and wording

In most of the forms for document generation a control for adjusting the Export language as shown below is included. The drop down box always offers an item “(default)” and language codes for all translation languages available in the database. If you select the default value, the original labels, details a.s.o. is used in the generated document. If you select a specific language code, the corresponding tranlated values are exported. If no tranlation is stored in the database for a specific value, the original value is used instead. 

  

If you select the option Use wording, for descriptions, descriptors and categorical states the values of the fields “wording” are exported instead of the names. For summary data additionally the values “wording before” and “wording after”, which may be specified for each descriptor, are inserted before and after the values. If no wording is specified, the original name is used.    

Jan 14, 2025

Subsections of Generate Document

Generate Descriptions

Generate a description data document

This tool is used to generate a structured documentation of description data stored in the database. To use this tool, start a query for descriptions and choose Data ->  Generate document … from the menu. A window with will open as shown below.

You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. Choose among the provided options and click on the button Create … documentation to create a document in one of the available formats.

By default no descriptions will be exported that include any descriptor with data status “Data withheld”. This is indicated by the button in the upper right corner of the window. You may click on this button to include those descriptions. The button will change to and only the marked descriptor summary data will be excluded from the document. 

 

HTML

If you create a HTML documentation, a local file named <Database name>_Description.htm is generated in the application directory, that might be copied and edited for own purposes. If you select option Include descriptors, the used descriptors are included at the end of the documents and links to that empedded descriptors are set in the description section. Otherwise the links are set to the entries specified in the Descriptor file: text box. By clicking button Select colors you may open a dialog window where you can select the colors of different elements (see window below).

If all descriptions in the selection box belong to the same project and a descriptor tree is defined, the Descriptor tree: drop-down list is shown in the options (see image below left). If a descriptor tree is selected and the Structured output keeps activated, the description data are arranged according the selected descriptor trees. Additionally leading descriptor name parts are omitted, if they are contained in the descriptor tree hierachy. Therefore “literature references” becomes to “references” contained in node “Literature” as shown below. If the selected descriptor tree contains only a subset of descriptors, only this subset will be displayed in the output. 

If the Structured output option is deactivated, all descriptors will be included in the output in the standard sequence order. Leading name parts will be reduced if they are already contained in the tree hierarchy as described in the Editing the description - Continuous viewtab section. With check box Include data titles the output of the titles “State”, “Text” and “Sequence” in the descriptor data can be controlled. If you select Resolve scopes, for each scope that is linked to a database entry a table with the foreighn database values will be inserted. To check and adjust the module connections click on button

If in the datasets RTF-like formatting tags like \i or \sub{} are included, use option Accept RTF mark-ups as shown in the picture below. 

 

MediaWiki

If you create a MediaWiki documentation, you may copy the generated text from the output window and insert it in the MediaWiki page. With the Layout option you may determine if all data shall be included in a large table or if several tables with additional header lines shall be generated (see image below). 

If all descriptions in the selection box belong to the same project and a descriptor tree is defined, the Descriptor tree: drop-down list is shown in the options (see image below left). If a descriptor tree is selected and the Restricted option is activated, the description data are restricted to the descriptors contained in the selected descriptor tree. 

If the Restriced option is deactivated, all descriptor data will be included in the output in the standard sequence order. Only name parts of the descriptor tree hierarchy will be included in the descriptor names as described in the Editing the description - Descriptor viewtab section. 

 

Pensoft content

If you like to publish description data in some online media, e.g. the Pensoft “Biodiversity Data Journal”, the description data are expected in a dedicated Microsoft Excel format. A template fille as shown below, that includes several tables, is available. DiversityDescriptions allows generating tabulator separated files for tables “Taxa” and “SpeciesDescriptionMatrix” of that template. 

If all descriptions in the selection box belong to the same project and a descriptor tree is defined, the Descriptor tree: drop-down list is shown in the options (see image below). If a descriptor tree is selected, the description data are arranged with heading according the selected descriptor trees. Additionally leading descriptor name parts are omitted, if they are contained in the descriptor tree hierachy.

When Ignore data status ist selected, it will not be included in the “CharacterValue” column. Option Ignore RTF mark-ups will remove RTF-like formatting tags like \i or \sub{}. If option Ignore notes is de-selected, notes will be inserted in the “Remarks” column of the “SpeciesDescriptionMatrix”.

If you select Resolve scopes and a scope entry for a taxon name is linked to an entry in DiversityTaxonNames, the corresponding fields of the “Taxa” table will be filled with that data. To check and adjust the module connections click on button . If scope data for a geographic area is available, it will be inserted in the “Distribution” column of the “Taxa” table.  

The results are stored in local files named <Database name>_Taxa.txt and <Database name>_SpeciesDescriptionMatrix.txt

 

 

Jan 14, 2025

Generate Descriptors

Generate a descriptor data document

This tool is used to generate a structured documentation of descriptors stored in the database. To use this tool, start a query for descriptors and choose Data ->  Generate Document … from the menu. A window will open as shown below.

You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. Choose among the provided options and click on the button Create … documentation to create a document in one of the available formats.

 

HTML

If you create a HTML documentation, a local file named <Database name>_Descriptor.htm is generated in the application directory, that might be copied and edited for own purposes. By clicking button Select colors you may open a dialog window where you can select the colors of different elements (see window below).

If in the datasets RTF-like formatting tags like \i or \sub{} are included, use option Accept RTF mark-ups as shown in the picture below. 

 

MediaWiki

If you create a MediaWiki documentation, you may copy the generated text from the output window and insert it in the MediaWiki page. With the Layout option you may determine if all data shall be included in a large table or if several tables with additional header lines shall be generated (see image below). 

 

May 3, 2024

Generate Projects

Generate a project data document

This tool is used to generate a structured documentation of project related data stored in the database. To use this tool, start a query for projects and choose Data ->  Generate Document … from the menu. A window will open as shown below.

You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. Choose among the provided options and click on the button Create … documentation to create a document in one of the available formats.

 

HTML

If you create a HTML documentation, a local file named <Database name>_Project.htm is generated in the application directory, that might be copied and edited for own purposes. By clicking button Select colors you may open a dialog window where you can select the colors of different elements (see window below).

You have the choice to output additional information besides the basic project data by selection the options Include descriptor trees, Include descriptor data or Include applicabilities (see window below).

 

MediaWiki

If you create a MediaWiki documentation, you may copy the generated text from the output window and insert it in the MediaWiki page. With the Layout option you may determine if all data shall be included in a large table or if several tables with additional header lines shall be generated (see image below). 

If you specify values in text fields Replace: and by: you can perform text replacements for Descriptor or Categorical state names in the generated output. By specifying a Prefix: for a Semantic MediaWiki (see next section) you can generate lokal links to this kind of Wiki pages. Additionally, you may insert the absolute link adresses by entering the base Wiki address in the URI: filed.  

 

Semantic MediaWiki

If you create a Semantic MediaWiki documentation, the descriptors, categorical states, descriptor trees and descriptor applicability information are generated in a format that fits to terminology platforms as used e.g by TDWG. In this scheme the most important entities are “Concept” and “Collection”. Each “Concept” represents a single descriptor or categorical state value, which is shown on an own page. Each “Collection” represents a single descriptor tree or descriptor tree node, which is shown on an own page. The pages are named according the schema <prefix>:<entity label> [(<number>)], where the <number> parts may be optional, depending on the Naming: setting (see image below):

  • If Opt. order (Optional order) is selected the <number> part is omitted if the name is unambigious. Otherwise it starts with 1 for the first duplicate and is increased for each subsequent one to avoid duplicate page names. 
  • If Order is selected the <number> starts with 1 and is increased for each subsequent duplicate to guarantee unambigious page names.
  • If Entity ID is selected the <number> contains the database internal ID of each entry to guarantee unambigious page names.

The Cardinality option includes information about multiple occurance and the mandatory property in the descriptor concepts. By selecting the Include trees option the descriptor trees and the tree structure will be included as collections where subordinated tree nodes are represented by concatenated node names, e.g. <prefix>:<Tree name>.<Node 1 name>.<Node 2 name>. If you specify values in text fields Replace: and by: you can perform text replacements for Descriptor or Categorical state names in the generated output.

If Generate: XML for Wiki import is selected, the output is generated in an XML format that may be imported to a semantic media wiki. To show all generated data, the two templates “dwb_Descriptor” and “dwb_CategoricalState” must be inserted in the wiki.

If Generate: XSD/XML document is selected, an XML schema (XSD) is generated in the main window. If schema generation was ended without problems, a selection list will be shown where description items for the XML document may be selected. For the selected descriptions an XML document structured according the XSD will be shown in a separate window. By default no descriptions will be exported that include any descriptor with data status “Data withheld”. This is indicated by the button in the upper right corner of the window. You may click on this button to include those descriptions. The button will change to and only the marked descriptor summary data will be excluded from the document.

 

Descriptor applicability

The descriptor applicability tree shows the selected projects and as subordinated nodes the categorical descriptors that control the applicability of dependent descriptors. Contained in the controlling descriptor are their categorical states and the dependent descriptors with the applicability rule “applicable-if” or “inapplicable-if” . The descriptor names are prefixed with their sequence number in square brackets, the states with the descriptor’s sequence number and their own.

If you create a applicability tree documentation, two local tabulator-separated text files are generated. The first file named <Database name>_ApplicabilityNodes.txt contains the node list with columns “Id”, “Label” and “Modularity class” (“Project”, “Descriptor” or “State”). The second file named <Database name>_ApplicabilityEdges.txt contains the edges list with columns “Source”, “Target” and “Label” (“Includes” for project-descriptor relations, “Contains” for descriptor-state relations or “Applicable” rsp. “Inapplicable” for state-descriptor relations). You may import those files to a graphic program like “Gephi”  to visualize the descriptor applicabilities. 

By selecting the option Convert to applicable rule or Convert to inapplicable rule the applicability settings stored in the database can be converted to the required complatible format (see image below).

 

May 3, 2024

Generate Diagram

Generate diagram

This tool allows you to generate charts that show the categorical state or descriptor usage for one or more sets of descriptions. To use this tool, choose Data →  Generate diagram … from the menu. A window with will open as shown below.

There are the following diagram Types available:

 

Selecting diagram sources 

By default at least one control Diagram source is present in the area Data sources at the left of the window. Here you select the descriptions that shall be used as data source for a diagram series. In text box Series name you can enter a label for the data source that will appear in the diagram legend. After selecting the Project in the main window (see image above) click on the button Edit item list to open a description query form (see window below). 

Start a query and select the entries you want to take over into the result list. By clicking the button Add you insert the selected entries. With button Delete all you can clear the result list. You may select all entries by clicking the all button, deselect all entries by clicking the none button or toggle your selection by clicking the swap button. Finally, click OK to close the query window (see image below). 

 

 

 

Jan 14, 2025

Subsections of Generate Diagram

Generate Diagram Cross Match

Generate diagram - categorical state cross-match

This tool allows you to generate a chart that shows the used categorical states of two specific descriptors for one set of descriptions as a cross-match. Select the Project and the two descriptors that shall be compared in Descriptor and Descriptor 2. By selecting the option Use names you will insert the categorical state names into the diagram. By checking the option Use wording, the wording values will be used if available. With the numeric control letters you can control the length of the state labels. If you select option Numbers, the sequence numbers of descriptors and categorical states will be inserted. Furthermore after the Series name the item count will be shown in the diagram.

After selecting entries for the Diagram source and entering a Series name click on button to draw the diagram (see image below). 

With button  you may switch between a 2D and 3D view. In the Diagram area there is a drop down box, where you may select a different color palette, buttons to rotate the 3D diagram in different directions, change the perspective and the scaling. With button you may save the diagram as an image file, with button you may store the data rows as tabulator separated text file. 

 

 

 

May 3, 2024

Generate Diagram Multi Source

Generate diagram - categorical state usage

This tool allows you to generate a chart that shows the used categorical states of a specific descriptor for one or more sets of descriptions. Select the Project and the Descriptor. You may restrict the categorical states that shall be included into the diagram by clicking the Select states button. By selecting the option Use names you will insert the categorical state names and the descriptor name into the diagram. By checking the option Use wording, the wording values will be used if available. With the numeric control letters you can control the length of the state labels. If you select option Numbers, the sequence numbers of descriptors and categorical states will be inserted. Furthermore after the Series name the item count will be shown in the diagram.  

After selecting entries for the Diagram source and entering a Series name click on button to draw the diagram (see image below). 

With button  you may switch between a 2D and 3D view. In the Diagram area there is a drop down box, where you may select a different color palette, buttons to rotate the 3D diagram in different directions, change the perspective and the scaling. With button you may save the diagram as an image file, with button you may store the data rows as tabulator separated text file. 

In the Data sources area the button  Add source may be used to add additional data sources (see image below). Use buttons and to move the Diagram source to the top or bottom of the list and button to delete the data source. By selecting Hide you may temporarily ignore the data source for the diagram. With drop down button you may select the display of Relative values, i.e. values scaled to the number of items in the Diagram source or Absolute values in the diagram.

 

 

 

May 3, 2024

Generate Diagram Usage

Generate diagram - descriptor usage

This tool allows you to generate a chart that shows the used desriptors for one or more sets of descriptions. After selecting the Project chose the first and the last descriptor in Descriptor and Descriptor 2. By selecting the option Use names you will insert the descriptor names into the diagram. By checking the option Use wording, the wording values will be used if available. With the numeric control letters you can control the length of the descriptor labels in the chart. If you select option Numbers, the sequence numbers of descriptors and categorical states will be inserted. Furthermore after the Series name the item count will be shown in the diagram.

After selecting entries for the Diagram source and entering a Series name click on button to draw the diagram (see image below). 

With button  you may switch between a 2D and 3D view. In the Diagram area there is a drop down box, where you may select a different color palette, buttons to rotate the 3D diagram in different directions, change the perspective and the scaling. With button you may save the diagram as an image file, with button you may store the data rows as tabulator separated text file. 

In the Data sources area the button  Add source may be used to add additional data sources (see image below). Use buttons and to move the Diagram source to the top or bottom of the list and button to delete the data source. By selecting Hide you may temporarily ignore the data source for the diagram. With drop down button you may select the display of Relative values, i.e. values scaled to the number of items in the Diagram source or Absolute values in the diagram.

 

 

 

May 3, 2024

Generate State Statisctics

Generate state statistics

This tool allows you to generate a table that shows the used categorical state of two or three descriptors for a sets of descriptions. To use this tool, choose Data →  Generate state statistics … from the menu. A window with will open as shown below.

First select the Project. With the option Include and Exclude you may select descriptions that shall be included rsp. excluded from the evaluation. To use the option, select the check box. With buttons you can now open an query window to select the description items. If none of these options is selected, all descriptions of the selected Project will be the base of the statistics evaluation. 

In section Categorical states select the DescriptorsDescriptor 1 and Descriptor 2 are inserted in the first columns of the Output table, the states of Descriptor 3 are inserted as separate columns. You may restrict the categorical states that shall be included for a descriptor by clicking the Select states button besides it. If you only want to evaluate the cross-match of two descriptors, you may de-select the check box before Descriptor 2

In section Legens you may control the appearance of descriptor and state names. By selecting the option Use names you will insert the categorical state names and the descriptor name into the outptu table. By checking the option Use wording, the wording values will be used if available. With the numeric control letters you can control the length of the labels. If you select option Numbers, the sequence numbers of descriptors and categorical states will be inserted. 

Click on button Fill table in section Output to build the cross-reference table (see image below). During calculation the icon changes to and you have the option to abort the process by clicking this button. 

By clicking Save table to file you may store the data as tabulator-separated text file. After saving you may open the text file with an external editor by clicking View saved file (see image below). 

Click on button Show data as diagram to view the generated cross-reference data as diagram (see image below). 

 

Next page: Generate categorical state statisctics - Three descriptor cross-match

Jul 5, 2024

Subsections of Generate State Statisctics

Generate Three Descriptor Statisctics

Generate state statistics - Three descriptor cross-match

In the examples shown so far only a two descriptor cross-match between Descriptor 1 and Descriptor 3 has been shown. When you set the check mark before Descriptor 2, its categorical states will be included in the statsitical evaluation. The second descriptor will then be inserted in the second table column at the Output area. If you do not perform further settings, each combination of the selected states from Descriptor 1 and Descriptor 2 will be listet in the output table as shown below.

You may further restrict the output by clicking on button right besides Descriptor 2. For each categorical state of Descriptor 1 the number of assigned categorical states of Descriptor 2 is shown (see image below left). When you click on a button in column “Assigned states” you may select the categorical states of Descriptor 2 that shall belisted for the corresponding “First state” (see image below middle). If no “Assigned state” is selected, only the “First state” will be evaluated. 

     

After setting the state cross-reference (see image above right) click “OK”. In the state statistics form an active state selection is indicated by the icon (see image below).

 

 

May 3, 2024

Maintenance

Maintenance

To open the maintenance form choose Administration → Database … → Maintenance … from the menu. The maintenance form offers functions for evaluation and update of multiple datasets that can hardly be achieved by the regular editing options, which focus on a single dataset. Currently the functions Synchronize databases, Update description scopes, Update resource data, Maintain descriptor trees, Maintain descriptors and Maintain descriptive data are available.

With the button  you can set the timeout for critical database queries, with the button  you can set the timeout for web requests used within maintenance. Feedbacks can be sent with the button .

Jan 14, 2025

Subsections of Maintenance

Maintenance Descriptions

Maintenance - Maintain descriptive data

To open the maintenance form choose Administration → Database … → Maintenance … from the menu and select the Maintain descriptive data tab. In the Descriptor status data tab you may set or reset the descriptor status of a categorical descriptor depending on its summary data. In the Categorical summary data tab you may shift and copy categorical summary data to a different descriptor or delete values for selected categorical states. In the Quantitative summary data tab you may perform such operations concerning statistical measures. With tab  Description project you may manage the additional projects of your description items. To find and delete corrupted descriptive data choose the Clean descriptive data tab. The tab  Find violation of rules offers query functions to find description items where rules concerning the descriptor usage are violated.

 

Commonly used description selection options

In the sub-panels you may set a descriptor status and move or copy categorical rsp. quantitative summary data. By default all descriptions from the selected project will be searched that fulfill the specified conditions, i.e. a certain categorical state or statistical measure. In certain cases it is neccessary to restrict the possibly affected descriptions by some additional conditions. For this purpose there is the option to define a restriction and/or an exclusion list (see example below).

By opening a query window (button ) you can generate a list of descriptions (see image below) that shall be included in the search (Description restriction) or excluded from the search (Description exclusion).  

The resulting numbers of restricted and excluded descriptions will be displayed in the controls. You may check the selected items by double-clicking the numbers (see images below).

 

Jan 14, 2025

Subsections of Descriptions

Maintenance Clean Descriptions

Maintenance - Clean descriptive data

Descriptive data, which can be summary or sampling data, are stored in the database in several tables, that reference the corresponding descriptor rsp. categorical state and hold some additional data. Depending on the descriptor type - categorical, quantitative, text or sequence - different tables are used to represent the descriptive data. Although Diversity Descriptions does not allow to change the type of a descriptor if descriptive data are present, in some cases it cannot be assured that such an action is rejected. The resulting data are then meaningless and will not be displayed within Diversity Descriptions. To find, check and delete such kinds of corrupted descriptive data, select the Maintain descriptive data tab and choose the tab Clean descriptive data.

Select the Data type (“Summary data” or “Sampling data”), the Entity type (i.e. the type of descriptive data in database: “categorical”, “quantitative”, “text” or “sequence”) and the Project. Click on Check for invalid data and all invalid data will be listed (see image below).

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To delete the selected entries from the database click on the button. Instead of deleting the selecting entries you may click Close form and check list in database to return to the main program with the affected descriptions.

You may open a table editor for the selected entries by clicking the Open table editor button (see image below). Here you may check the corrupted data to decide if further measures are required. 

 

May 3, 2024

Maintenance Description Projects

Maintenance - Description project

Description items belong to one basic projects, that determines the terminology. Additionally they may be assigned to additionalprojects to make them accessible within other contexts. To set or remove additional projects, select the Maintain descriptive data tab and choose the tab Description project.

Select the Project, Addtitional project and the requested operation Set additional project, Remove additional project or Swap projects to exchange the project and additional project. Click on Check for project data and the matching descriptions will be listed (see image below). The Description restriction and Description exclusion lists may be used for refinement of the description selection (see Maintain descriptivedata). 

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To delete the selected entries from the database click on the button. Instead of deleting the selecting entries you may click Close form and check list in database to return to the main program with the affected descriptions.

 

Jan 14, 2025

Maintenance Violations

Maintenance - Find violations of rules

With this form you ma easily search description items, that do not fulfill certain requirements. With the Mandatory descriptors tab you may find descriptions where data for mandatory descriptors are missing. With the Exclusive descriptors tab you may find descriptions that contain multiple states for exclusive descriptors. In the Applicability rules tab you may descriptions that violate rules administered in the Descriptorapplicability data. In the Ambigious descriptions tab you may search for ambigious description titles.  

 

Jan 14, 2025

Subsections of Maintenance Violations

Maintenance Ambiguous

Maintenance - Ambiguous description titles

In DiversityDescriptions the description titles may be ambiguous, even within one project. It depends on the informal project strategies if duplicate description titels shall be accepted, therefore there is no kind of highlighting. With this form you can easily find all descriptions with ambigious titles within a project.

After selecting the Project click on Check for violations and all found description items are listed in the table (see image above). If you select the option Ignore same state, mutiple occurances of the same state, e.g. when modifier of frequency values have been selected, will be ignored. By selecting an entry and clicking the button Inspect dataset you may view that dataset in a separate window.

You may select or deselect all entries of the result list by clicking the buttons Select all rsp. Select none. To save the selected table entries in a tab-separated text file click on the Export data button. Click Close form and check list in database to return to the main program with the affected descriptions.

 

May 3, 2024

Maintenance Exclusive

Maintenance - Exclusive descriptors

If a descriptor is marked as “exclusive”, in each description item only one categorical state value for this descriptor should be present. When you are editing a description in the Contiuousview violations of this rule are usually highlighted by a yellow background color. With this form you can easily find all descriptions violating the exclusivity condition.

After selecting the Project click on Check for violations and all found description items are listed in the table (see image above). If you select the option Ignore same state, mutiple occurances of the same state, e.g. when modifier of frequency values have been selected, will be ignored. By selecting an entry and clicking the button Inspect dataset you may view that dataset in a separate window.

You may select or deselect all entries of the result list by clicking the buttons Select all rsp. Select none. To save the selected table entries in a tab-separated text file click on the Export data button. Click Close form and check list in database to return to the main program with the affected descriptions.

 

Jan 14, 2025

Maintenance Mandatory

Maintenance - Mandatory descriptors

If a descriptor is marked as “mandatory”, in each description item a value for this descriptor should be present. When you are editing a description in the Contiuous view those missing data as usually highlighted by a yellow background color. With this form you can easily find all descriptions with missing mandatory descriptor data.

After selecting the Project click on Check for violations and all found description items are listed in the table (see image above). You may restrict the query to selected Descriptor types. If you select the option Evaluate status data, any present descriptor status, e.g. “To be checked” or “Data missing”, will be treated as if descriptor data were present. By selecting an entry and clicking the button Inspect dataset you may view that dataset in a separate window.

You may select or deselect all entries of the result list by clicking the buttons Select all rsp. Select none. To save the selected table entries in a tab-separated text file click on the Export data button. Click Close form and check list in database to return to the main program with the affected descriptions.

 

Jan 14, 2025

Maintenance Summary Categorical

Maintenance - Categorical summary data

To shift and copy categorical summary data to a different descriptor or delete values for selected categorical states, select the Maintain descriptive data tab and choose the tab Categorical summary data. In this panel you operate on the categorical summary data of the descriptions. If you want to shift or copy categorical states between descriptors, please use Maintenance - Categoricalstates

Select the Project and the Source descriptor. If you want to select a Target descriptor that is different than the Source descriptor, check the box before the Target descriptor and select a value. Click on Show categorical state mapping and all categorical state values of the selected Source descriptor will be listed in the upper table (see image below). Select the categorical states for which you want to modify the summary data in column >>.

The following operations are available:

  • Delete the summary data by leaving the Target state empty
  • Move the summary data by selecting the Target state
  • Copy the summary data by selecting the Target state and selecting the New column

In case the summary data are moved or copied, all relevant data including modifier and frequency values and notes will be processed. 

After adjusting the required operations for the selected categorical states click on Check for categorical states and all affected summary data will be listed in the lower table (see image above). The Description restriction and Description exclusion lists may be used for refinement of the description selection (see Maintain descriptivedata). For each affected Description and State of the categorical summary data the Action (DELETE, MOVE or INSERT) and New state are specified. If you check the option No state selected, you may search for descriptions that do not reference any state of the Source descriptor and set a state of the selected Target descriptor (see image below). 

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To perform the selected operations click on the button. Instead of updating the database you may click Close form and check list in database to return to the main program with the affected descriptions.

 

Jan 14, 2025

Maintenance Summary Quantitative

Maintenance - Quantitative summary data

To shift and copy quantitative summary data to a different descriptor or delete values for selected statistical measures, select the Maintain descriptive data tab and choose the tab Quantitative summary data

Select the Project and the Source descriptor. If you want to select a Target descriptor that is different than the Source descriptor, check the box before the Target descriptor and select a value. Click on Show statistical measure mapping and the assigned statistical measures of the selected Source descriptor will be listed in the upper table (see image below). If you want so process all available statistical measures, not only that ones assigned to the descriptors in the descriptor tree, check Show all source measures rsp. Show all target measures. Select the statistical measures for which you want to modify the summary data in column >>.

The following operations are available:

  • Delete the summary data by leaving the Target statistical measure empty
  • Move the summary data by selecting the Target statistical measure
  • Copy the summary data by selecting the Target statistical measure and selecting the New column

In case the summary data are moved or copied, all relevant data including modifier values and notes will be processed. 

After adjusting the required operations for the selected categorical states click on Check for statistical measures and all affected summary data will be listed in the lower table (see image above). The Description restriction and Description exclusion lists may be used for refinement of the description selection (see Maintain descriptivedata). For each affected Description and Measure of the quantitative summary data the Action (DELETE, MOVE or INSERT) an New measure are specified. You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To perform the selected operations click on the button. Instead of updating the database you may click Close form and check list in database to return to the main program with the affected descriptions.

 

Jan 14, 2025

Maintenance Summary Status

Maintenance - Descriptor status data

To set or reset a certain descriptor status for dedicated categorical summary data, select the Maintain descriptive data tab and choose the tab Descriptor status data

Select the Project, the Source descriptor and the Target descriptor status. Depending on the Source descriptor type you have different basic options to select the descriptions for which the descriptor data status shall be modified. For quantitative, text and molecular sequence descriptors, you may decide if the selected Descriptor value shall be present (option Value is present) or absent (option No value is present, see image below). This basic restriction may further be refined by selecting Description restriction and Description exclusion lists (see Maintaindescriptive data). Further select the data status and if it shall be set or reset using Action options.

After adjusting the required operations click on Check for descriptor status and all affected summary data will be listed in the lower table (see image above). For each affected Description the Action (DELETE or INSERT) and the Status are specified.

If you select a categorical Source descriptor, you have the basic selection options to modify the descriptor data status for specific Categorical state (option Specific state selected, see image below). In this case use the combobox to adjust the selected state. If you uncheck Specific state selected, you may search for descriptions where any State is present or No state is present. In any case the Description restriction and Description exclusion lists may again be used for further refinement of the description selection (see Maintain descriptive data).

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To perform the selected operations click on the button. Instead of updating the database you may click Close form and check list in database to return to the main program with the selected descriptions.

 

Jan 14, 2025

Maintenance Descriptors

Maintenance - Maintain descriptors

To open the maintenance form choose Administration → Database … → Maintenance … from the menu and select the Maintain descriptors tab. In the Categorical states tab you may shift and copy categorical states to a different descriptor or delete selected categorical states.  

 

 

Jul 5, 2024

Subsections of Descriptors

Maintenance Categorical States

Maintenance - Categorical states

To shift and copy categorical states to a different descriptor or delete selected categorical states, select the Maintain descriptors tab and choose the tab Categorical states. In this panel you operate on the categorical states of the descriptors. If you want to shift or copy categorical summary data in descriptions, please use Maintenance - Categoricalsummary data

Select the Project, the Source descriptor and the Target descriptor. Click on Show categorical state mapping and all categorical state values of the selected Source descriptor will be listed in the upper table (see image below). Select the categorical states you want to modify in column >>.

The following operations are available:

  • Delete the categorical state by leaving the Target state empty
  • Move the categorical state by entering the Target state
  • Copy the categorical state by entering the Target state and selecting the New column

In case the categorical states are moved or copied, associated fields as abbreviation and detail will be processed. State resources will not be copied. 

After adjusting the required operations for the selected categorical states click on Check for categorical states and the number of affected summary and sampling data will be listed in the lower table (see image above). For each State the Action (DELETE, MOVE or INSERT) and New state are specified. You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To perform the selected operations click on the button. If  Instead updating the database you may click Close form and check list in database to return to the main program with the affected descriptions.

 

Jan 14, 2025

Maintenance Resources

Maintenance - Update resource data

To open the maintenance form choose Administration → Database … → Maintenance … from the menu and select the Update resource data tab. In the resource edit forms the resource data, e.g. the file size, of a single resource can be obtained from the remote server addressed by the resource link. If for a large number of resouces the data shall be updated it is much easier to select the Get resource data tab. To find and delete empty resources choose the Clean empty resources tab. 

Jan 14, 2025

Subsections of Resources

Maintenance Clean Resources

Maintenance - Clean resources

In the database the “Resource” table holds the general resource data, e.g. copyright information, and links the resource to the target entity. The “ResourceVariant” table holds the link to the resource and allows to associate several links with distinguished quality levels to a single resource. To find resource entries that are not associated with any resource variant (“empty resources”), select the Update resource data tab and choose the tab Clean empty resources.

Select the Resource target (“Description”, “Descriptor”, “Categorical state” or “Descriptor tree node”) and the Project. Click on Check for empty resources and all resource links of the specified type will be listed where no resource variants are present in the database (see image below).

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To delete the selected resource entries from the database click on the button. Instead of updating the selecting entries you may click Close form and check list in database to return to the main program with the corresponding data sets.

You may open a table editor for the selected resources by clicking the Open table editor button (see image below).

 

May 3, 2024

Maintenance Get Resources

Maintenance - Get resource data

In the resource edit forms the resource data, e.g. the file size, of a single resource can be obtained from the remote server addressed by the resource link. If for a large number of resouces the data shall be updated it is much easier to select the Update resource data tab and choose the tab Get resource data.

Select the Resource target, (“Description”, “Descriptor”, “Categorical state” or “Descriptor tree node”), the Resource type (“image”, “audio”, “video”, “text”, “application” or “other”) and the Project. Click on Check resource data and all resource links of the specified type will be listed where the remote data of (“Mime type”, “File size”, “Width”, “Height” or “Duration”) differ from the database values (see image below). If the acces to a URL was not successfull, this is indicated by a red background color. To see the failure reason, move the mouse cursor over the entry.

The size of the query result list may be adapted by changing the value Number of results or unchecking this option to get the complete list. Usually only database links are checked that do not have any entry for “File size”, “Width”, “Height” and “Duration”. Select Check links with data to check entries with data, e.g. to update manually entered values. Since with this option allways all resources will be processed, the numeric control Skip first rows is available (see image below). So you may adjust Number of results to 200 and Skip first rows to 100 to check only the resource entries 101 to 200. 

When you select the option Update URL with response value, the URL returned by the web server will be compared with the requested URL. If there is a difference, re returned URL will be entered in the table and marked in column URL change (see image above). This option might be useful, if you have resource links stored with protocol type “http://” and the web server was updated to use encryption. In this case the URL changes to “htttps://”.

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To update the database click on the button.

You may open a table editor for the selected resource variants by clicking the Open table editor button (see image below).

Some resources, especially for resource types like “text” or “application”, do not even provide a file size. Therefore you might not get any new matches for subsequent check and update sequences if the number of results is limited. In those cases you should try to increase the number of results or deactivate the Number of results option.

 

 

 

May 3, 2024

Maintenance Scopes

Maintenance - Update description scopes

To open the maintenance form choose Administration → Database … → Maintenance … from the menu and select the Update description scopes tab. If you want to generate scope entries from description data, select the Generate scopes tab. With the Link entries  tab you may insert scope links to another database of the DiversityWorkbench. If you have linked descriptions to entries in DiversityCollection, you may import links of the referenced specimen rsp. observations to other databases by using the Import scopes tab. To find and delete empty scopes choose the Clean empty scopes tab. 

Jan 14, 2025

Subsections of Scopes

Maintenance Clean Scopes

Maintenance - Clean empty scopes

If you want to find and delete scope entries that do not contain any data, select the Update description scopes tab and choose the tab Clean empty scopes.

Select the Scope type, e.g. “Taxon name” and the Project. Click on Check for empty scopes and all descriptions will be listed where no scope of the specified type is present and source data are available (see image below).

The size of the query result list may be adapted by changing the value Number of results or unchecking this option to get the complete list. You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none

If you select the option Include description IDs and start a new query (button Check for empty scopes) the result list will include the column DescriptionID. By selecting an entry and clicking the button Inspect dataset you may directly navigate to that dataset. If you click on button Close form and check list in database , you will return to the main form and find the selected entries in the description result list.

To update the database click on the button.

 

 

 

May 3, 2024

Maintenance Generate Scopes

Maintenance - Generate scopes

Especially if data are imported, e.g. from a DELTA file, data that can be stored as scope of a description are often contained in dedicated text or categorical descriptor data. For taxonomic descriptions often the item/description names reflect the taxonomic names. To generate formal scopes from such “embedded” data select the Update description scopes tab and choose the tab Generate scopes.

Select the Scope type, e.g. “Taxon name” and the Project. You may generate the Scope from description name or select a Source descriptor and the type Text or Categorical. Furthermore the whole source text (description name or text descriptor data) may be selected (option Copy whole text) or only the first parts (option Copy first parts). Click on Check for missing scopes and all descriptions will be listed where no scope of the specified type is present and source data are available (see image below).

The size of the query result list may be adapted by changing the value Number of results or unchecking this option to get the complete list (see image below). You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none

If you select the option Include description IDs the button Inspect dataset will be shown (see image below). By starting a new query (button Check for missing scopes) the result list will now include the column DescriptionID. By selecting an entry and clicking the button Inspect dataset you may directly navigate to that dataset. To update the database click on the button. 

 

 

 

May 3, 2024

Maintenance Import Scopes

Maintenance - Import scopes

If you have linked description items to DiversityCollection, either by as scope type “Specimen” or “Observation”, you have the option to import links to other databases e.g. to a taxon entry that is present in DiversityCollection. Select the Update description scopes tab and choose the tab Import scopes.

Select the Scope type that shall be imported, e.g. “Sampling plot” and the Project. The Link to collection may be “Specimen” or “Observation”. You have three options to search for descriptions that are liked to DiversityCollection:

  • Insert missing scopes searches any description item that is linked to DiversityCollection and you may import the specified links as new scope values.
  • Insert if no scope is present searches only description items that are linked to DiversityCollection and do not yet have an entry of the selected Scope type.
  • Delete not matching scopes offers the option to remove scope entries from description items of the selected Scope type that are not present in the references collection entry.   

For the latter two options you may decide to Ignore unlinked scopes. Click on Search for descriptions and all descriptions will be listed where the selected conditions match (see image below). You may select or deselect all entries of the description list for the database query by clicking the buttons Select all descriptions rsp. Select no description . If you want to view a single description item, click on it in the result list and then click button Inspect dataset .

In a second step you can now check the linked collection entries for matching links to the selected scope type. The size of the query result list may be adapted by changing the value Number of results. Click on button to open the connections administration form where you may connect missing collection databases.

Start a query for links in DiversityCollection with button Check for matching entries. Description entries with found links are marked with green background, without links with yellow background. If Number of results is selected, only the specified number of entries in the descriptions list will be processed. Depending on the selected options the modified entries will be shown and the “Action” will be “INSERT” or “DELETE” (see image below). After updatig the database, you may process the next package in the description list by a further click on Check for matching entries

In case of new entries the “Scope text” will be taken over from DiversityCollection if possible, otherwise it will be set to the selected scope type. After updating the database, you may use Synchronize databases to update the display text in DiversityDescriptions.  

You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none. To update the database click on the button. 

 

 

 

Jan 14, 2025

Maintenance Link Scopes

If you have entries in DiversityDescriptions that shall be linked with data in other DiversityWorkbench databases that have a partly equal name, this may generally be done with two subsequent maintenance tasks. An example are taxonomic descriptions in that shall be linked with their corresponding entries in DiversityTaxonNames. In a first step taxon scopes must be generates, e.g. from the first two parts of the description names with Generate scopes. With a second step the generated scope may be linked to the target database using Synchroniuze databases. For descriptions without matching entries in the target database unlinked scopes will be remaining.

To generate the links with one step and avoid generating unlinked scopes select the Update description scopes tab and choose the tab Link entries. Select the Scope type, the Project and the Target database. Option Only if no scope present filters for description items that do not have a scope entry of the selected scope type. Furthermore the whole description name may be selected (option Compare whole text) or only the first parts (option Compare first parts). Click on Check for missing scopes and all descriptions will be listed where no scope of the specified type is present and source data are available (see image below).

The size of the query result list may be adapted by changing the value Number of results or unchecking this option to get the complete list (see image below). You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none

If you select the option Include description IDs the button Inspect dataset will be shown (see image above). By starting a new query (button Check for missing scopes) the result list will now include the column DescriptionID. By selecting an entry and clicking the button Inspect dataset you may directly navigate to that dataset. To update the database click on the button. 

If more than one matching entry is available in the Target database the entry is marked with blue background in the result list (see image above). With button Select value   you may view the available alternatives and select the correct entry (see image below). 

 

 

 

Jan 14, 2025

Maintenance Synchronize

Maintenance - Synchronize databases

To open the maintenance form choose Administration → Database … → Maintenance … from the menu and select the Synchronize databases tab. With the maintenance functions you can update values cached from other modules or external webservices. Entries in Diversity Descriptions can be linked with several other modules of the Diversity Workbench, e.g. by the Description scopes. If you link a data source to another module, the URI of the data set in the other module together with one or several cached values will be stored in Diversity Descriptions. Due to changes in the source modules these cached values may differ from the original values. To get the actual values you can use the  synchronize functions for taxonomic names, specimen and observations geographical names, sampling plots, and references. Additionally broken links can be searched an repaired.

 

Commonly used database synchronization options

In the sub-panels several commonly used options and controls are available. First the source database must be selected, where the referenced data are stored. In the example shown below this is the Taxonomy database. Click on button to open the connections administration form where you may connect missing databases. The second parameter that has to be specified is the Descriptions project that contains the datasets which have to be checked or updated. If datasets of Diversity Descriptions are not yet linked to another module, the project of the source database may be specified (Taxonomy project in example below).

By starting a query (button Check for differences, Check for identical names or Start check) you will get a result list of database entries that can be updated (see image below). In this example the first result entry represents two datasets in Diversity Descriptions (column Number). In column DescriptionIds the range of the affected database internal IDs is shown. You may select or deselect single entries of the result list for the database update in column OK.

The size of the query result list may be adapted by changing the value Number of results or unchecking this option to get the complete list (see image below). If datasets of Diversity Descriptions are not yet linked to another module, the query in Diversity Descriptions may be restricted by specifying a value in the field Restrict to names starting with. You may select or deselect all entries of the result list for the database update by clicking the buttons Select all rsp. Select none

If you select the option Include description IDs the buttons Inspect dataset and Close and view will be shown. By starting a new query (button ) the result list will now include the columns Description and DescriptionID instead of DescriptionIds and Number (see image below). Furthermore each dataset entry will now be shown in an own result line.  

By selecting an entry in the result table and clicking the button Inspect dataset you may view the dataset in a sepate window. With button Close and view you can close the maintenance form without changing the database and view or edit all enteries that are checked in column “OK” of the result table in the main program window. 

Jan 14, 2025

Subsections of Synchronize

Maintenance Broken Links

Broken links to other databases occur when the database’s name has been change or if it was moved to a different server. To find and repair broken links to the modules of the Diversity Workbench select the Synchronize databases tab and choose the tab Broken links. The meaning of some generally used controls is explained in the introduction page of database synchronization

Select the Link type, e.g. “Taxon name” to search broken links to DiversityTaxonNames and the Descriptions project. Select the Search for broken links option and start the query with a click on the Search for broken links button. If the link type “Geographic area” or “Specimen” has been selected, an additional selection box for the Descriptions table appears, where you may select from “Description scope” or " Sampling event" rsp. " Sampling unit". Each link of the selected type and project will checked if it can be connected to the referenced database and unsuccessful connection attemts will be listed in the data grid view (see image below).

Keep in mind that the connection check might be unsuccessful for remote databases, if the database connection was not set up before! 

If you prefer to remove some broken links, you may now select them and then click button . If you want to connect the links to a database, chose the new target in combo box Database and click the Check matches in database button. The check is successful, if the new databese contains an entry with the same ID and display text and the results will be selected and shown with white background (see image below).

If in the new database a matching link was found but the display text differs, the entries are marked  with yellow background. For these lines you should check the “New name” column and if the found entry is applicable you may select the entry for update. If no matching entry in the database was found, it is marked with grey background (see image above). To update the database click on the button.

 

Delete unlinked scope entries

As an additional option you may search for unlinked scope entries and remove them completely from the database. Select the option Search for unlinked entries and then click on the Search for broken links button. Select the entries you want to delete and click button (see image below).

 

The webservice “Catalogue of Life” was changed several times. Links to old versions are not readable anymore, therefore new matching entries have to be found. Select the option Search for old Catalogue of Life links and then click on the Search for broken links button. If you only want to remove the invalid links and keep the unlinked scope entry, click on button (see image below).

To find matching entries in the current webservice, select a option Check full name or Compare first parts and click on the Check matches in the database button. If the name in your data does not match the name in the webservice perfectly, it will be marked with a yellow background. If no name matches exactly and there are several entries, the line is marked with blue background (see image below). 

You have the option to select the best match by a click on button Select name (see image below).

Finally, click on the button to enter the results in the database.

 

May 3, 2024

Maintenance Collection

Maintenance - Collection

To synchronize the entries for the specimen or observations derived from the module DiversityCollection select the Synchronize databases tab and choose the tab Collection. There are two ways to synchronize specimen and observations. You may either Synchronize entities with a link to DiversityCollection for entries where the link to a taxonomic database is already established or you may Synchronize entities missing a link to DiversityCollection where no link is established and you can query for identical names in one of the databases. The meaning of some generally used controls is explained in the introduction page of database synchronization.

Synchronize entities with a link to DiversityCollection

The specimen and observations are stored as field “label” of table DescriptionScope, where the scope type Specimen or Observation specified. Alternatively the field collection_specimen of table SamplingUnit can be updated. Select a collection database, the descriptions project and the scope type that shall be synchronized. Start the query with a click on the  button.

 

The form will list all differences found. To update the database click on the button.

 

Synchronize entities missing a link to DiversityCollection

Select the collection database, optionally a project within this database, a project in the descriptions database, the descriptions teble and the scope type Specimen or Observation to search for identical names. Start the query with a click on the button. To use these similar names check them in the OK column. 

 

The form will list all matches found. To insert the links to the database click on the button.

 

Jan 14, 2025

Maintenance Gazetteer

Maintenance - Gazetteers

To synchronize the entries for the geographic places derived from the module DiversityGazetteers select the Synchronize databases tab and choose the tab Gazetteers. There are two ways to synchronize geographic names. You may either Synchronize places linked to DiversityGazetteers for entries where the link to a gazetteers database is already established or you may Synchronize places missing a link to DiversityGazetteers where no link is established and you can query for identical names in one of the databases. The meaning of some generally used controls is explained in the introduction page of database synchronization.

Synchronize places linked to DiversityGazetteers

The geographic names are stored as field “label” of table Descriptionscope with the scope type GeographicArea or in field “geographic_area” of table SamplingEvent. Select a gazetteers database, the descriptions project and the descriptions table that shall be synchronized. Start the query with a click on the  button.

 

The form will list all differences found. To update the database click on the button.

 

Synchronize places missing a link to DiversityGazetteers

Select the gazetteers database, optionally a project within this databas, a project in the descriptions database and the descriptions table to search for identical names. Start the query with a click on the  Start check button. To use these similar names check them in the OK column. 

Many places have identical names in different regions. Names where several results were found are marked in blue. To choose the correct name among the list of results, click on the  Select name button and select the correct name from the list as shown below.

Finally, click on the button to enter the results in the database.

 

 

 

Jan 14, 2025

Maintenance References

Maintenance - References

To synchronize the titles of the references which are linked to the module DiversityReferences select the Synchronize databases tab and choose the tab References. Select the references database and the project for which the reference titles should be synchronized. The references are stored as field “label” of table DescriptionScope, where the scope type Citation is specified. The meaning of some generally used controls is explained in the introduction page of database synchronization.

Start the query with a click on the  button.

The form will list all differences found. To update the database click on the button.

 

 

Jan 14, 2025

Maintenance Sampling Plots

Maintenance - Sampling plots

To synchronize the titles of the references which are linked to the module DiversityReferences select the Synchronize databases tab and choose the tab Sampling plots. Select the references database and the project for which the reference titles should be synchronized. The references are stored as field “label” of table DescriptionScope, where the scope type Citation is specified. The meaning of some generally used controls is explained in the introduction page of database synchronization.

Start the query with a click on the  button.

The form will list all differences found. To update the database click on the button.

 

 

Jan 14, 2025

Maintenance Taxon Names

Maintenance - Taxonomic names

To synchronize the entries for the taxonomic names derived from the module DiversityTaxonNames select the Synchronize databases tab and choose the tab Taxon names. There are two ways to synchronize taxonomic names. You may either Synchronize taxonomic names linked to an external data source for entries where the link to a taxonomic database is already established or you may Synchronize taxonomic names missing a connection where no link is established and you can query for identical names in one of the databases. The meaning of some generally used controls is explained in the introduction page of database synchronization.

Synchronize taxonomic names linked to an external data source

The taxonomic names are stored as field “label” of table DescriptionScope, where the scope type TaxonName is specified. Select a taxonomy database and the descriptions project that shall be synchronized. Start the query with a click on the  button.

 

The form will list all differences found. To update the database click on the button.

 

Synchronize taxonomic names missing a connection

Select a taxonomic database, optionally a project within this database and a project in the descriptions database to search for identical names. Start the query with a click on the  button. You may either restrict the search to an exact match (= Compare whole name) or to the first parts of the name (= Compare first parts) as shown below. If the names do not match exactly, you may either update the name (= Update similar name) in the descriptions database or import the name from the DiversityTaxonNames as a new scope (= Insert as new name - see options in the window depicted below). In the result list only matching names will be checked (column OK). The other results will be marked indicating the difference. Yellow indicates a difference in the authors while red indicates differences in main parts of the name. To use these similar names check them in the OK column.

 

The form will list all matches found. To insert the links to the database click on the button.

 

Synchronize taxonomic names missing a connection with a websrvice

To synchronize the taxonomic names with a webservice select it as Taxonomy database. You may either compare the entire name or the first parts of the name (see image below and description above). If the name in your data does not match the name in the webservice perfectly, the name will be marked with a yellow background.

If several similar names were found, these lines will be marked with a blue background (see image above). To select one of the similar names click on the Select name button. A window will open as shown below listing all similar names found in the webservice. Select one name and click OK to use it.

 

Jan 14, 2025

Maintenance Trees

Maintenance - Maintain descriptor trees

To open the maintenance form choose Administration → Database … → Maintenance … from the menu and select the Maintain descriptor trees tab. With the descriptor trees the assignment of descriptors to certain projects is done. Furthermore it is possible to administer the recommended statistical measures and modifiers for quantitive descriptors and the recommended modifier and frequency values for categorical descriptors. If a description item references entities that are not correctly assigned in the descriptor trees, this can be seen in the continious view. In the tab Missing description entities you can easily find and fix such kind of inconsistencies. Furthermore a centralized function to administer Statistical measures Modifier values and Frequency values is provided. Finally superfluous entries may be deleted by using the Clean descriptor trees tab.

Jan 14, 2025

Subsections of Trees

Maintenance Trees Clean

Maintenance - Clean descriptor trees

To administer the recommended modifier values select the Maintain descriptor trees tab and choose the tab Clean decriptor trees. Select the Project, the Descriptor tree and the Entity type (“Statistical measure”, “Modifier” or “Frequency”) that shall be cleaned. Currently three cleaning options are supported:

  • Unsuitable recommended values - Clear recommended values the do not match the descriptor type, e.g. statistical measures for a categorical descriptor.
  • Recommended values for tree nodes - Clear recommended values that are not directly assigned to a descriptor, but a tree node. You should only perform this operation if you are sure that the neccessary values have been directly assigned to the approriate descriptors.  
  • All values in the descriptor tree - Delete all recommended values. Only descriptor trees can be selected for this option, that are not marked as “complete”. You should only perform this operation if you are sure that the neccessary values have been assigned to a complete descriptor tree of the project.  

To start the search click on the Check for values to clean button. 

 

To start the update of the selected descriptor tree click on the button. 

 

May 3, 2024

Maintenance Trees Frequency

Maintenance - Frequency values

To administer the recommended frequency values select the Maintain descriptor trees tab and choose the tab Frequency values. Select the Project and the Descriptor tree that shall be checked and click on the Check for frequency values button. Behind the “Descriptor” column all used frequency values are shown in the output table. Values that are not assigned for the selected descriptor tree but anyway available in the project, e.g. due to a different descriptor tree or inherited by a superior tree node, are diplayed with blue background (see image below).

 

New values may be inserted in the table by selecting them in the check list on the left and clicking the Add >> button. The check list shows the frequency values available in your database. Additional values can be inserted in the Modifier/Frequency tabs of Edit descriptor or Edit project. By clicking the button All >> rsp. None >> may check or uncheck all checked values from the list box in the table. The buttons All project >> and No project >> check or uncheck the project specific entries with blue background in the table. If one or more lines in the output tables are selected (click on the fields before the “OK” column), the mentioned functions operate only for the selected lines, otherways for the whole table. With option Fix descriptor columns you may fix the first data grid columns to scroll horizontally thru the value list.  

To store the modifications to the selected descriptor tree click on the button. Instead of updating the selected entries you may click Close form and check list in database to return to the main program with the corresponding data sets.

 

Jan 14, 2025

Maintenance Trees Measure

Maintenance - Statistical measures

To administer the recommended statistical measures select the Maintain descriptor trees tab and choose the tab Statistical measures. Select the Project and the Descriptor tree that shall be checked and click on the Check for statistical measures button. Behind the “Descriptor” column all used statistical measures are shown in the output table. Descriptors that have not assigned any statistical measures are marked with yellow background. Values that are not assigned for the selected descriptor tree but anyway available in the project, e.g. due to a different descriptor tree or inherited by a superior tree node, are diplayed with blue background (see image below).

 

New values may be inserted in the table by selecting them in the check list on the left and clicking the Add >> button. By clicking the button All >> rsp. None >> may check or uncheck all checked values from the list box in the table. The buttons All project >> and No project >> check or uncheck the project specific entries with blue background in the table. If one or more lines in the output tables are selected (click on the fields before the “OK” column), the mentioned functions operate only for the selected lines, otherways for the whole table. With option Fix descriptor columns you may fix the first data grid columns to scroll horizontally thru the value list.  

To store the modifications to the selected descriptor tree click on the button. Instead of updating the selected entries you may click Close form and check list in database to return to the main program with the corresponding data sets. 

 

May 3, 2024

Maintenance Trees Missing

Maintenance - Missing description entities

To find description entities that are not correctly assigned to the project’s descriptor trees, select the Maintain descriptor trees tab and choose the tab Missing description entities. Select the Project and the Entity type that shall be checked. Currently the following entity types are supported:

  • Descriptor - Search for descriptors that are referenced in the description data but not assigned to the project’s descriptor tree
  • Statistical measure - Search for statistical measures that are referenced in the description data but not assigned to the quantitative descriptor
  • Modifier - Search for modifier values that are referenced in the description data but not assigned to the quantitative rsp. categorical descriptor
  • Frequency - Search for frequency values that are referenced in the description data but not assigned to the categorical descriptor

By default the option Ignore inherited entities is checked, therefore only descriptors of the own project and recommended values directly assigned to the project descriptor are evaluated. If option Include description IDs is checked you will have the option to inspect the found data sets after the query. Start the query with a click on the Check for missing entities button.

 

If you selected the option Include description IDs the button Inspect dataset will be shown. By selecting an entry and clicking the button Inspect dataset you may directly navigate to that dataset.

Before database update select the Target descriptor tree where missing entities shall be inserted. By default only descriptor trees that are marked as “complete” are shown. You may uncheck option Show only complete trees to display all present descriptor trees.

To update the database click on the button. Instead of updating the selected entries you may click Close form and check list in database to return to the main program with the corresponding data sets.

 

May 3, 2024

Maintenance Trees Modifier

Maintenance - Modifier values

To administer the recommended modifier values select the Maintain descriptor trees tab and choose the tab Modifier values. Select the Project and the Descriptor tree that shall be checked and click on the Check for modifier values button. Behind the “Descriptor” column all used modifier values are shown in the output table. Values that are not assigned for the selected descriptor tree but anyway available in the project, e.g. due to a different descriptor tree or inherited by a superior tree node, are diplayed with blue background (see image below).

 

New values may be inserted in the table by selecting them in the check list on the left and clicking the Add >> button. The check list shows the modifier values available in your database. Additional values can be inserted in the Modifier/Frequency tabs of Edit descriptor or Edit project. By clicking the button All >> rsp. None >> may check or uncheck all checked values from the list box in the table. The buttons All project >> and No project >> check or uncheck the project specific entries with blue background in the table. If one or more lines in the output tables are selected (click on the fields before the “OK” column), the mentioned functions operate only for the selected lines, otherways for the whole table. With option Fix descriptor columns you may fix the first data grid columns to scroll horizontally thru the value list. 

To store the modifications to the selected descriptor tree click on the button. Instead of updating the selected entries you may click Close form and check list in database to return to the main program with the corresponding data sets. 

 

Jan 14, 2025

Fequently Asked Questions

Database

  • How to connect to a database.
    • See chapter Connect
    • and the video Video starten: Anmeldung an die Datenbank
  • How to create a documentation of the database
    • see chapter Documentation of database
    • and the video Video starten: Erzeugung am Beispiel einer Tabelle, Inhalt des Ordners, Standardeinstellung zur Erzeugnung des Dokuments, Vorstellung der Details, Erzeugung eines Dokuments mit Standardeinstungen, Inhalt des Ordners mit css Dateien, Darkmode im Browser, CSS-Datei.

Documentation

  • How to adapt the chm manuals for Hugo
  • and the video: Anpassungen für HUGO Video starten: Umzug von chm nach html. Anleitung für Umstellung auf html. Übersetzung von html nach markdown. Auswahl der Dateien im Programm. Pandoc als Voraussetzung für Konvertierung. Ansicht der markdown Dateien. Ersetzen des headers (Frontmatter). Anpassungen für Bilder, Ersatz der Icons durch Vektorgrafiken. Beispiel für Vektorgrafik. Bearbeitung der Liste für Ersetzungen über Tabelle. Laden einer Datei mit Ersetungen. Ansicht der Datei und Laden der Datei. Durchfürung der Ersetzungen.
  • How to export the content of enum tables for inclusion in the manual for HUGO
  • and the video Ausgabe des Inhalts von Aufzählungstabellen Video starten: Auswahl der Aufzählungstabellen, Anwählen der Ausgabeoption, Auswahl der Spalten, Export und Ansicht im Formular und im Browser.
  • How to fix broken links for Hugo
  • and the video: Video starten

  • How to related reference links for Hugo

  • and the video: Video starten

Administration

  • How to set the access to projects
    • see chapter Zugriff auf Projekte
    • and the video Video starten: Einstellungen des Zugriffs auf Projekte, Zugriff auf Daten innerhalb von Projekten

Editing

  • How to set the language of a dataset
    • see chapter Sprache
    • and the video Video starten: Festlegen der Sprache des Inhalts eines Datensatzes.
    • How are addresses retrieved from the hierarchy
      • see chapter Hierarchien
      • and the video Video starten: Haupthierarchie mit Ermittlung der Adresse und zusätzliche Hierarchien.
        • How to remove loops from a hierarchy
          • see chapter Schleifen entfernen
          • and the video Video starten: Entfernen von Schleifen in der Hierarchie anhand von Beispieldaten.
    • How to remove loops in the synonymy
    • How to see the public contanct infos
      • see chapter Öffentliche Kontaktdaten
      • and the video Video starten: Ermittlung der öffentlichen Kontaktdaten anhand zugänglichen Kontaktdaten des aktuellen Eintrags sowie der in der Haupthierarchie verfügbaren Kontaktdaten.
    • How to set the icons of descriptors
      • see chapter Descriptoren - Icons einstellen
      • and the video Video starten: 2 prinzipielle Typen von Deskriptor: Modul zugeordnet oder ohne Modul. 4 Möglichkeiten für die Einstellung der Icons - OHNE ICON: Modul zugeordnet: Default Icon des Moduls. ohne Modul: Default Icon für Deskriptor. MIT ICON: ohne Modul: Ausgabe des gesetzten Icons. Modul zugeordnet: Ausgabe des gesetzten Icons. Default Icon des Moduls wird ersetzt.
    • How to propagate changes to linked data
      • see chapter Änderungen verlinkter Datensätze weiterleiten
      • and the video Video starten: DiversityAgents als Modul in der DWB. Darstellung der Beispieldaten in DiversityCollection und DiversityAgents. Änderung in DiversityAgents, Eintrag des geänderten Datensatzes in Update Liste. Auswahl der zu aktualsierenden Datenbanken. Display types in DiversityAgents. Eintrag von aktuellem Datensatz, Eintrag aller Datensätze, Ansicht der Liste, Löschen der Liste. Aktualisieren des Datensatzes. Kontrolle der Änderungen in DiversityCollection.
    • Spreadsheet

  • How to include column RowGUID to enable changes in the PK of a table
  • see chapter …
  • and the video RowGUID einschliessen Video starten: Erläuterung der RowGUID. Beispieldaten im TableEditor. Laden der Daten im Spreadsheet. Versuch der Änderung einer Spalte die Teil des Primärschlüssels ist. Einschliessen der RowGUID. Versuch der Änderung mit eingeschlossener RowGUID. Ablehnung der Änderung bei Kollision mit Primärschlüssel. Änderung der Daten ohne Kollision. Ergebnis der Bearbeitung.

Import

  • How to import data
    • see chapter Überblick
    • and the video Video starten: Import von Daten anhand des Beispiels im Tutorial.
    • How to check for duplicates
      • see chapter Duplikate
      • and the video Video starten: Prüfung auf in der Datenbank bereits vorhandene Duplikate während des Imports.
    • How to transform data during the import
      • see chapter Transformation
      • and the video Video starten. Transformation von Daten für den Import am Beispiel eines Datums.

Archive

  • How to create an achive including the log tables
  • see chapter Archiv inclusive des Logs
  • and the video Video starten.
    (Aufbau von Logtabellen, Vorstellung der Beispieldaten, Erstellung eines Archivs: Einschliessen der Logtabellen, Suche nach Daten, Anlegen des Archivs. Wechsel in leere Datenbank. Einlesen der Archivdaten: Auswahl des Archivs, Log einschliessen, Einlesen der Daten, Archivdaten einspielen, Meldung zu vorhandenem Projekt. Anmeldebestätigung. Ansicht der Daten einschliesslich der Daten in den Logtabellen)
  • How to create an archive
  • see chapter Archiv erstellen
  • and the video Video starten.
    (Automatisierte Erstellung durch Server, Manuelle Erstellung, Suche nach Daten, Erstellung, Inhalt einer xml-Datei, Protokoll).

General

Mar 26, 2024

Subsections of General

High Resolution

High-resolution displays

More and more computers are nowadays delivered with high-resolution displays. Since Diversity Descriptions is a Windows forms application, which works pixel-oriented, the program window would become smaller and smaller with increasing display resolution.

To face this problem, Windows uses a scaling mechanism, which zooms pixel-oriented applications, which may lead to a burry picture. To avoid this, an alternative is to increase the font sizes within the application and magnify elements like buttons, data grids and so on, which is called “DPI-awareness” of the application. Since the icons within the application are not zoomed automatically, this mechanism usually only works satisfactory with moderate scaling factors of some 125% or 150%. For higher factors the icons within the application will become too small. You can check the scaling factor fo your system in the Windows settings → System → Display, section “Scale and layout”  

If you have problems with DiversityDescriptions with a high-resolution display, please try out if you get better results with the Windows scaling. Therefore right-click the program icon (usually on your desktop), select “Properties” and go to the “Compatibility” tab (see image below).

Please click on button Change high DPI setting and another window as shown below will appear.

Check the option “High DPI caling override” and you will be able to select a different value than the default “Application”. Please try out if “System” or “System (Enhanced)” gives better results. After confirming with OK start the application and check the adjustment.

 

May 16, 2024

Menu

Overview of the menu in DiversityDescriptions:

Connection
    Create database ... Create a new database. This option is only applicable if you have system administrator rights for the database.
    Database ... Choose one of the databases available on the server. Only those databases will be listed to which the user has access permission.
    Reconnect to database Reconnect to the actual database and reload basic data.
         Auto connect   Automatically connect to database (only with windows login).
    Module connections ... Edit the connections to the other modules within the Diversity Workbench.
    Timeout for database ... Set the timeout for database queries.
    Timeout for web requests ... Set the timeout for web requests.
    Transfer previous settings ... Transfer the settings for IP-Address and port of the server, name of the database, login etc. of a previous version of the client to the current version.
    Current server activity ... View current activities on the database server.
    Quit Quit the application and stop all processes started by the application.

Edit
        Descriptions Select edit mode for descriptions.
        Descriptors Select edit mode for descriptors.
        Projects Select edit mode for projects.
    Tranlsations ... Edit or view translations.
    Summarize descriptions ... Summarize description data.
    Summarize sampling data ... Summarize sampling data.
    Edit as HTML form ... Edit the current description in an HTML form.

Grid
    Description grid ... Edit or view descriptions in a grid.
    Sample data grid ... Edit or view sample data in a grid.
    Table editor  
       Projects ... Edit the projects in the query result list. 
       Sampling events ... Edit the sampling events for the descriptions in the query result list. 
       Descriptions ... Edit the descriptions in the query result list. 
       Description scopes ... Edit the scopes of the descriptions in the query result list. 
       Description resources ... Edit the resources for descriptions in the query result list. 
       Descriptors ... Edit the descriptors in the query result list.
       Descriptor resources ... Edit the resources for descriptors in the query result list. 
       Categorical states ... Edit the categorical states of the descriptors in the query result list. 
       Categorical state resources ... Edit the resources for the categorical states of the descriptors in the query result list. 
       Descriptor tree node resources ... Edit the resources for the descriptor tree nodes of the projects in the query result list. 
       Resource variants ... Edit the resources for entities in the query result list. 
       Translations ... Edit the translations for entities in the query result list. 

Query
        Show query Show the query window.  
        Project preference ... Set or view the project preference for query windows.  
    Extended query ... Extended query for description data.  
    Collect descriptions ... Collect descriptions with a separate query form.  

Data
     Save dataset Save the actual dataset in the database.  
     Restore from log ... Restore deleted datasets from the log tables in the database (only for administrator).   
    Generate document ... Generate a document with descriptions, descriptors or projects from the query list.  
    Generate diagram ... Generate a diagram of categorical state usage, cross-match or descriptor usage for a set of description items.  
    Generate state statistics ... Generate statistics for categorical state usage (two or three descriptors cross-match) for a set of description items.  
    Import
       Import wizard Import wizard.  
          Matrix wizard ... Import descriptor, description and sample data from a tabulator separated text file.
          Sample data ... Import sample data for descriptions from a tabulator separated text file.  
          Descriptions ... Import descriptions from a tabulator separated text file.
          Descriptors ... Import descriptors from a tabulator separated text file.
          Import resources Import resources.
             Description resources ... Import description resources from a tabulator separated text file.  
             Descriptor resources ... Import descriptor resources from a tabulator separated text file.
             Categorical state resources ... Import categorical state resources from a tabulator separated text file.
             Descriptor tree node resources ... Import descriptor tree node resources from a tabulator separated text file. 
             Resource variants ... Import resource variants from a tabulator separated text file -special import to append resource variants.
          Import translations Import translations.
             Description translations ... Import description translations from a tabulator separated text file.  
             Descriptor translations ... Import descriptor translations from a tabulator separated text file.
             Categorical state translations ... Import categorical state translations from a tabulator separated text file.
       Organize sessions ... Organize import sessions.  
       Import SDD ... Import SDD files.
      Import DELTA ... Import DELTA files.
       Import questionnaire data ... Import revised data received from HTML forms.  
    Export
       Matrix wizard ... Export descriptor and description data as tabulator separated list and generate an import schema for the Matrix Import Wizard.  
      Export data ... Export data in a structured data file format (SDD, DELTA, EML).  
       Export questionnaires ... Export description data of a project or from a query list as HTML forms.  
       Export lists   Export tabulator separated lists.  
          Sample data list ... Export sample data list.
          Descriptions list ... Export descriptions list.
          Descriptors list ... Export descriptors list.  
         Resource data list ... Export resource data list document for review and possible re-import of modified data.  
         Translations list ... Export translations list document for review and possible re-import of modified data.  
       Export CSV ... Export database tables in CSV format.  
    Cache database ... Export data of selected projects into a cache database.  
    Backup database ... Create a backup of the database.  
    File operations File operations (no database connection needed).  
       Convert SDD file ... Convert a SDD file to DELTA or EML without database access.  
       Convert DELTA file ... Convert an DELTA file to SDD or EML without database access.  
       Check SDD file ...   Check if an SDD file is compliant to the XML schema SDD 1.1 rev 5.  
       Check EML file ...   Check if an EML file is compliant to the XML schema EML 2.1.1.  

Administration
   Change password ... Changing the password of a user.  
   Database  
       Database tools ... Tools for the administration of the objects in the database.
For experts only!
       Documentation ... Generate documentation of the information model.  
       Statistical measures ... Adjust display sequence of statistical measures.  
       Logins ... Administration of the logins of the server their permissions in the databases.  
       Maintenance ... Maintenance of database entries, especially, if connected to other modules.
       Rename database ... Rename the current database.  
       Set published address ... Setting the address published for links by other modules.  
       Check projects ... Check the consistency of the project data.  
    Linked server ... Administration of the linked servers.  
     Projects ... Administration of the projects.  
   Resources directory ... Change the resources directory.  
   Tutorial files ... Copy tutorial files to the resources directory.

Help
    Manual Opens the user manual.  
    Feedback ... Opens a window for sending feedback.  
    Feedback history ... Opens a window for browsing former feedback.  
    Edit feedback ... Opens a window for feedback editing - only for special users possible.  
    Statistics ... Overview of statistical data for the database contents.  
    Info ... Show the version of the program and corresponding information.  
    Websites Websites related to Diversity Descriptions.  
        Download application ... Download Diversity Descriptions from the website of the Diversity Workbench project.  
        Information model ... Inspect the information model on the website of the Diversity Workbench project.  
        SDD homepage ... Visit the TDWG homepage for the SDD standard.  
        EML homepage ... Visit the KNB homepage for the EML standard.  
        DELTA homepage ... Visit the DELTA homepage for the DELTA standard.  
        Example files ... Visit the repository of DiversityDescriptions example files.
    Error log View the actual error log file.  
            Keep error log Change the error log settings to "Keep error log".
            Clear error log at program start Change the error log settings to "Clear error log at program start".  
    Clear error log Clear the actual error log file.  

Update
     Update database ... Update the database to the current version.  
     Update client ... Download the current version of the client.  

 

 

 

 

 

May 3, 2024

Statistics

Statistics

For statistical information about the database contents choose Help -> Statistics ….

The Users tab shows information about the users with access to the database. This output may be restrictied to your own data if you do not have sufficient acces rights (see image below).

The Projects tab shows information about the projects in the database and the entered data (see image below). The colums marked with “(total)” include entries that refer to the specified project as an additional project (see Editdescription).

The Descriptor trees tab shows information about the projects in the database, their descriptor trees and nodes and the number of assigned descriptors (see image below).

Jan 14, 2025

Feedback

If you have suggestions for improvement, need any changes in the programm or encouter an error you can give a feedback to the administrator. Click on the ALT and PRINT buttons to get a screen shot of your current form. After creating the screen shot choose Help - Feedback from the menu to open the feedback form as shown below.

 

Click on the Insert image button to insert the screen shot and give a comment about your problem. In the field Topic enter the topic of your feedback (will appear in response e-mail). The Priority can either be empty or set to 3 levels:

  • urgent
  • as soon as possible
  • nice to have

If necessary, enter a date in the field ToDo until when you would like to have the task described in you feedback be solved. Then click on the  Send feedback button to send your feedback to the administrator. If you would like to receive a message when the problem you described is solved, please enter you e-mail address in the field below the description.

To inspect your former feedbacks choose Feedback history from the menu. A window will open where you can browse your past feedback together with the state of progress.

Mar 26, 2024

Internals

For users that need more detailed information about the software including database design etc.

May 3, 2024

Subsections of Internals

Database

Database

The database for DiversityDescriptions is based on Microsoft SQL-Server 2012 and higher.

Organisation of the data

The database consits of three major parts:

1. The “Descriptive terminology” with the main tables “Descriptor” and “CategoricalState” provides the means to express the description details. The two fixed enumeration tables “DataStatus_Enum” and “StatisticalMeasure_Enum” provide values defined in the SDD standard 1.1 rev 5.

2. The “Descriptions” part with the main table “Description” reflects the items themselves. Each description must be assigned to a project (see part 3) and references entries from the descriptive terminology. These references are reflected by the tables “CategoricalSummaryData”, “QuantitativeSummaryData” and “TextDescriptorData”, where additional item specific data are stored.

3. The “Projects” part with the main tables “Project”, “DescriptorTree” and “DescriptorTreeNode” build the anchor for the descriptions, which must be assigned to a project. Further functions are a hierarchical organization of the descriptors and restriction of the descriptive terminology to certain projects. Additionally it is possible, to define recommended values of statistical measure, modifier and frequency associated to certain branches of a descriptor tree or single descriptors. If for a certain project no descriptor tree is created, there is no restriction, i. e. all descriptors are allowed.

The image below shows the main tables of the database.

 

In the graphic the tables of the database are marked according to their logical groups. Additionally the database group “Resources” provides the option to assign links to resource files (pictures, audio, video) to certain descriptors, categorical states or descriptions. The “Auxilliary” group with the main table “BaseEntity” provides unique keys for the most of the other tables for building of relations. Furthermore it allowes a centralized realization of some features, e.g. support of translations supply imports and export to a cache database.

Further details: tables, projects.

Jan 14, 2025

Subsections of Database

Backup

Backup

Database copy

If you need to backup your database, you have to use the functionality provided by SQL-Server. To do this, you need administration rights in the database you want to create a backup. Open the Management Studio for SQL-Server, choose the database and detach it from the server as shown in the image below.

After detaching the database, you can store a copy of the …_Data.MDF File to keep it as a backup.

After storing the backup you have to attach the database.

A dialog will appear where you have to select the original database file in your directory.

Note: A database copy can only be attached to an SQL server with the same or a higher version. For example if a database that was attached to an SQL-Server 2008 R2 (internal version 10.50) is copied, it is not possible to attach the copy to an SQL-Server 2008 (internal version 10.00).

 

Database backup

If you are logged in to a database with administrator rights, you can start a backup within DiversityDescriptions with menu item Data-> Backup database. In this case the name of the backup is automaticallly generated from the SQL-server version, the database name and data/time of backup. In case of backup success the resulting file path at the SQL server disk will be displayed as in the example below.

To restore the backup to a new database, right-click at “Database” in the Managment Studion for SQ-Server and select “Restore database…”.

In the following panel specify the database name, select “Restore from medium” to specify your backup file and select the backup source (see below). You can overwrite an existing databse by selecting it in that panel instead of specifying a new database name.

Note: The same limitations concerning the SQL-Server versions as mentioned in section “Database copy” are valid for backup handling, too. A backup can only be restored at the same or a higher version of SQL-Server.

May 3, 2024

Connections

Connections to the databases and services

The program will automatically try to connect to all the modules within the Diversity Workbench. To edit these connections choose Connection -> Module connections … from the menu. A form as shown below will open, where you can edit these connections.

To requery the connections use the button. If you want to add a connection to a different server click on the  button and connect to the database you want to add to the list. Added databases will be displayed in green. To remove a connection from the list select it and click on the button. If you have added connections in a former program run, click on button to insert them into the available connections (see right image). If an added connection misses a password, this will be indicated by a red backcolor. Click on the button to enter the missing password. 

Webservices like IndexFungorum will be displayed in blue.

May 3, 2024

Create Database

Create a new database

If you have database system administrator rights, the menue item Connection → Create database … is available, where you may create a new database for your client. A similar option is available if you connect to a database server that does not have any fitting databases and you are using a windows login with sufficient rights. In this case the button will be shown after clicking Connect to server in the connection window (see image below).

After clicking the button, you will be asked to enter the database name (see image below).

The database files will be created in the default database directory of the Microsoft SQL Server. Afterwards the database update form will be opened to install all required database objects (see image below).

Click on button Start update to complete the installation. After creating the new database you should check the login administration to make it it accessible to other users.

 

Jan 14, 2025

Data Project

Information concerning the project access and related tables are stored in the tables shown in the diagram below. The table “Project” relates the table “ProjectProxy”, which holds an optional link to DiversityProjects, with attribute “ProjectProxyID”. The tables “UserProxy”, “ProjectUser” and “ProjectProxy” allow a independent administration of the access functions related to projects and users and are required for the centralized DiversityWorkbench components.

 

 

Index

Table ProjectProxy

The projects as stored in the module DiversityProjects

Column Data type Description
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
Project nvarchar (255) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects)
ProjectURI nvarchar (255) URI of a project in a remote module, e.g. refering to database DiversityProjects

Table ProjectUser

The projects that a user can access

Column Data type Description
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc..
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
ReadOnly bit If the user has only read access to data of this project
Default value: (0)

Table UserProxy

The user as stored in the module DiversityAgents

Column Data type Description
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc..
CombinedNameCache nvarchar (255) The short name of the user, e.g. P. Smith
AgentURI nvarchar (255) URI of a user in a remote module, e.g. refering to database DiversityAgents
Queries xml (MAX) Queries created by the user
ID int ID of the user
PrivacyConsent bit If the user consents the storage of his user name in the database
PrivacyConsentDate datetime The time and date when the user consented or refused the storage of his user name in the database
May 3, 2024

Database Configuratation

Configuration of the database

To configure your Database, choose Administration -> Database → Rename database … to change the name of the database according to your requirements. During this renaming all processes in the database will be terminated (you will get a warning if processes from other host are active).

Afterwards you should adapt the address that is published by the database for access by other modules. Choose Administration -> Database → Set published address … from the menu. This will change the published address to the name of the server where your database is located and an identifier for you database, e.g. http://xy.diversityworkbench.de/Descriptions/

Renaming of the database and adapting of the published address should be done before you start to use the database and name and address should not be changed afterwards as datasets from other modules linked to data in the database would point to outdated addresses otherwise.

 

 

May 16, 2024

Database Documentation

Database documentation

This tool is used to generate a structured documentation of database parts. To use this tool, choose Administration -> Database ->  Documentation … from the menu. A window will open as shown below.

Select the tables that should be included in the documentation, choose among the provided options and click on the button Create … documentation to create a documentation in one of the available formats (HTML, MediaWiki, JSP-Wiki, Semantic Media Wiki). If you create a HTML documentation, a local file named <Database name>.htm is generated in the application directory, that might be copied and edited for own purposes. For MediaWiki and JSP-Wiki you may simply copy and paste the needed parts from the output window.

If you select format “Semantic Media Wiki” an output is generated that fits to terminology platforms as used e.g by TDWG. In this scheme the most important entities are “Concept” and “Collection”. Each “Concept” represents a single table column, which is shown on an own page named <prefix>:<table>.<column>. Each “Collection” represents a single table, which is shown on an own page named <prefix>:<table> (see image below). The “Semantic Media Wiki” option currently only supports output of Tables. Views, Functions and Roles will be ignored. 

If “Generate: XML” is selected, the output is generated in an XML format that may be imported to a semantic media wiki. To show all generated data, the two templates “dwb_concept” and “dwb_relation” must be inserted in the wiki.

 

May 3, 2024

Database Tools

Database tools

These are the tools to handle the basic parts of the database. The most of the functions support developers in introducing and maintining database features. These tools are only available for the owner of the database and should be handled with care as any changes in the database may disable the connection of your client to the database. Before changing any parts of the database it is recommended to backup the current state of the database. To use these tools, choose Administation → Database → Database tools … from the menu. A window will open as shown below.

 

Description

The Description section (see above) shows the basic definitions of the objects in the database and enables you to enter a description for these objects including tables and their columns, functions and their parameter etc. With the buttons SQL for adding, update and both you can generate SQL statements for the creation of the descriptions in your database. Use the button both if you are not sure if a description is already present as it will generate a SQL statement working with existing and missing descriptions (see below).

 

Log table and trigger

In the Log table and trigger section (see below) click on the List tables button to see all tables within the database. The Table section shows the basic definitions of a selected table. If columns for logging the date and responsible user for inserting and updating the data are missing, you can use the Attach … button to attach these columns to the table. Furthermore you may add a RowGUID to the table as e.g. a preparation for a replication.

In the Log table section (see below) you can create a logging table for the selected table in a format as used within the Diversity Workbench. Click on the Show SQL … button to show the SQL-statement that will create the logging table. If an old logging table should be kept, choose the Keep old log table option. If your table should support the version setting from a main table, choose the Add the column LogVersion option. To finally create the logging table click on the Create LogTable … button.

The triggers for insert, update and delete are created in the according sections (see below). If an old trigger exists, its definition will be shown in the upper part of the window. Click on the Show SQL button to see the definition of the trigger according to the current definition of the table in a format as used in the Diversity Workbench. If a trigger should set the version in a main table, which the current table is related to, choose the Add version setting to trigger option. To enable this option you must select the version table first. To finally create the trigger click on the Create trigger button. The update and delete triggers will transfer the original version of the data into the logging tables as defined above, where you can inspect the history of the data sets.

 

Preparation for replication

If you want to use replication within you module, the tables need certain columns and a log table. These preparations can be performed by a script, generated in the section Replication (see below). Select the tables you want to include in the process and create the script. This script can than be included in an update of the database. Please ensure that these changes are only be done by expert staff.

 

Clear logtables

If for any reason you want to clear the log tables of the database, this can be done in the Clear log tab as shown below. Click on the List tables button to list the log tables. Then select those that should be cleared and click on the Clear log of selected tables button (see below). Please keep in mind that any restoration of data from the log is only possible as long as the data can be retrieved from the log.

 

Data protection

To implement the General Data Protection Regulation of the European Union several steps have to be performed in a database:

  • Generate a skript using this tool (see below) to convert all tables and insert objects according to the requirements:
    • Add columns ID, PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Grant update to PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Create update trigger for UserProxy setting the PrivacyConsentDate
    • Create the function providing the ID of the user from UserProxy
    • Create the function providing the name of the user from UserProxy
    • Create the function PrivacyConsentInfo providing common information
    • For every table:
      • Insert users from a table into UserProxy (if missing so far)
      • Insert users from the corresponding log table into UserProxy (if missing so far)
      • Change the constraints for the logging columns (User_Name() ? UserID())
      • Replace user name with ID in logging columns
      • Replace user name with ID in logging columns of the log table
      • Adapt description of the logging columns
  • Include the skript in an update of the database
  • Check the database for update triggers, functions using e.g. CURRENT_USER, USER_NAME, SUSER_SNAME etc. where user names must be replaced with their IDs. Create a script performing these tasks and include it into an update for the database
  • Adapt the client to the now changed informations (e.g. query for responsible etc.)

After these changes the only place where the name of a user is stored is the table UserProxy together with the ID. Removing the name (see below) will remove any information about the user leaving only a number linked to the information within depending data.

To generate a script for the objects and changes needed to implement the General Data Protection Regulation use the Data protection tab as shown below. The generated script will handle the standard objects (logging columns) but not any additional circumstances within the database. For these you need to inspect the database in detail and create a script to handle them on your own.

To set the website where detailed information about the handling of the General Data Protection Regulation within the DiversityWorkbench resp. the current database is provided, click on the button on the Info site tab. If unchanged, the default site for the DiversityWorkbench is set (see below).

If for any reason a user wants his name to be removed from the database, select the users name from the list as shown below and click on the  button (see below).

 

May 16, 2024

Diversity Descriptions Workshop

Index

Table BaseEntity

The BaseEntity is used within the database to provide unique keys

Column Data type Description Nullable
id int Database-internal object ID, unique across all tables in database (primary key) NO
table_id int References the table name of table entries associated with the BaseEntity; NULL indicates orphaned entries and may be used for garbage collection of otherwise deleted object ids
Default value: NULL
YES
specific_rights_text nvarchar (255) To be used where the licence for an object differs from the default project licence
Default value: NULL
YES
specific_licence_uri nvarchar (255) URI of licence, where different from project licence
Default value: NULL
YES

Table BaseEntityTable_Enum

The BaseEntityTable_Enum contains the names of tables that reference the BaseEntity table

Column Data type Description Nullable
id int Database-internal object ID of this record (primary key) NO
table nvarchar (255) Name of table that references the BaseEntity table NO

Table CacheDatabase

Table holding the cache databases connected to the database

Column Data type Description Nullable
Server varchar (50) The name or IP of the server where the cache database is located NO
DatabaseName varchar (50) The name of the cache database NO
Port smallint The port of the server where the cache database is located NO
Version varchar (50) The version of the cache database YES

Table CacheMappingDescription

Table holding the description key mappings for the cache database

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
project_id int Reference to the description project (foreign key) NO
description_id int Reference to the description to which these data belong (foreign key) NO
target_key int Mapped key value for the target of the cache database. NO

Table CacheMappingDescriptor

Table holding the descriptor key mappings for the cache database

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
project_id int Reference to the descriptor project (foreign key) NO
descriptor_id int Reference to the descriptor to which these data belong (foreign key) NO
target_key int Mapped key value for the target of the cache database. NO
last_state_key int Highest value of state key. Relevant for key_mapping_level > 0
Default value: (0)
YES

Table CacheMappingState

Table holding the categorical state key mappings for the cache database

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
project_id int Reference to the state project (foreign key) NO
state_id int Reference to the categorical state to which these data belong (foreign key) NO
target_key int Mapped key value for the target of the cache database. NO

Table CacheProject

Table holding the project settings for the cache database

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
project_id int Reference to the description project (foreign key) NO
withheld_data_level tinyint Flag for handling of withheld descriptor data. 0=withhold description; 1=withhold descriptor; 2=do not withhold data
Default value: (0)
YES
key_mapping_level tinyint Flag for handling of key mapping. 0=re-build mapping for each update; 1=keep first mapping; 2=additionally take numeric values of alternate ID for items; >2 as 2 but re-initialize table
Default value: (1)
YES
last_char_key int Highest value of character key. Relevant for key_mapping_level > 0
Default value: (0)
YES
last_item_key int Highest value of item key. Relevant for key_mapping_level > 0
Default value: (0)
YES
last_changes datetime The recent date when data within the project had been changed
Default value: getdate()
YES

Table CategoricalSamplingData

The categorical data recorded for a sampling event

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
sampling_unit_id int Reference to the sampling unit (foreign key) NO
state_id int Reference to the state (descriptor is implicit in state_id) (foreign key) NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES
modifier_id int Optional reference to a modifier definition (e.g. "strongly", "at the base", "in autumn") (foreign key)
Default value: NULL
YES
frequency_value int Number of times this category was observed within a single sampling unit
Default value: NULL
YES

Table CategoricalState

The categorical states available for categorical descriptors

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
descriptor_id int Reference to the descriptor to which the state belongs (foreign key) NO
label nvarchar (255) Short label (or name) of descriptor state NO
abbreviation nvarchar (255) Abbreviated label of descriptor state
Default value: NULL
YES
detail nvarchar (MAX) Additional detail text explaining or commenting on the descriptor state definition YES
wording nvarchar (255) Optional separate wording for natural language generation (label will be used if this is missing)
Default value: NULL
YES
display_order int A positive number defining the sequence in which descriptor states are displayed
Default value: '0'
NO

Table CategoricalSummaryData

The categorical data of a description

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int Reference to the description to which these data belong (foreign key) NO
state_id int Reference to the state (the descriptor is implicit in state_id) (foreign key) NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES
modifier_id int Optional reference to a modifier definition (e.g. "strongly", "at the base", "in autumn") (foreign key)
Default value: NULL
YES
frequency_id int Optional reference to a frequency modifier definition (e.g. "rarely", "usually", "mostly") (foreign key)
Default value: NULL
YES

Table DataStatus_Enum

Values of data status used for descriptions according to SDD 1.1 rev 5

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of data status NO
code nvarchar (255) Code of data status NO
abbreviation char (1) Single (intuitive) character NO
detail nvarchar (MAX) Additional detail text explaining or commenting on the data status definition YES

Table Description

The description in the database

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of description
Default value: NULL
YES
detail nvarchar (MAX) Additional detail text explaining or commenting on the description definition YES
project_id int Each description belongs to exactly one project that determines its terminology (required, foreign key) NO
alternate_id nvarchar (30) Optional alternate id of a description item - should be unique within one project, but not checked by database
Default value: NULL
YES
wording nvarchar (255) Optional separate wording for natural language generation (label will be used if this is missing)
Default value: NULL
YES

Table DescriptionProject

The projects where descriptions are accessible

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int ID of the description that belongs to the project (required, foreign key) NO
project_id int ID of the project to which the description belongs (required, foreign key) NO

Table DescriptionScope

The scope of the description

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int Reference to the description to which these data belong (foreign key) NO
label nvarchar (255) Short label (or name) of scope
Default value: NULL
YES
dwbURI nvarchar (500) Reference to DiversityWorkbench component
Default value: NULL
YES
type nvarchar (255) Scope type ("GeographicArea", "SamplingPlot", "Citation", "Observation", "Specimen", "TaxonName", "OtherConcept", "Stage", "Part" or "Sex")
Default value: NULL
YES
other_scope_id int Reference to further scopes, e.g. stage, sex etc. (foreign key)
Default value: NULL
YES

Table Descriptor

Descriptor (= characters, features) define variables

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of descriptor NO
abbreviation nvarchar (255) Abbreviated label of descriptor
Default value: NULL
YES
detail nvarchar (MAX) Additional detail text explaining or commenting on the descriptor definition YES
display_order int A positive number defining the sequence in which descriptors are displayed
Default value: '0'
NO
subclass nvarchar (255) The four character subclasses of SDD are all combined here in one entity and distinguished by this attribute ("categorical", "quantitative", "text" or "sequence")
Default value: 'categorical'
NO
statistical_measurement_scale nvarchar (255) Scale of descriptor: Categorical may be nominal (unordered, “red/green/blue”) or ordinal (ordered, “bad/medium/good”); Quantitative may be interval (°C) or ratio (mass, length, time, K)
Default value: 'nominal'
NO
usually_exclusive tinyint Applicable to categorical (nominal/ordinal) descriptors only. If usually exclusive = 1, then by default the user interface allows only entering one state. Nevertheless, multiple states in the data are valid.
Default value: '0'
NO
state_collection_model nvarchar (255) Handling of multiple values: OrSet/AndSet: unordered set combined with or/and, OrSeq/AndSeq: ordered sequence combined with or/and, WithSeq: example is “green with brown”, Between: an example is “oval to elliptic”
Default value: 'OrSet'
NO
mandatory tinyint Is the scoring of this descriptor mandatory (required) in each item?
Default value: '0'
NO
repeatability nvarchar (255) How reliable and consistent are repeated measurements or scorings of the descriptor by different observers and on different objects? ("ignore", "very low", "low", "below average", "slightly below average", "standard", "slightly above average", "above average", "high" or "very high")
Default value: 'standard'
NO
availability nvarchar (255) How available is the descriptor or concept for identification? ("ignore", "very low", "low", "below average", "slightly below average", "standard", "slightly above average", "above average", "high" or "very high")
Default value: 'standard'
NO
measurement_unit nvarchar (255) A measurement unit (mm, inch, kg, °C, m/s etc.) or dimensionless scaling factor
Default value: NULL
YES
measurement_unit_precedes_value tinyint Set to 1 if the measurement unit precedes the value
Default value: '0'
NO
values_are_integer tinyint Set to 1 if the values are integer
Default value: '0'
NO
min_plausible_value float Applicable to quantitative descriptors only; in support of a plausibility check for values. Example: for tree height this could be 0, i.e. only positive values allowed
Default value: '-1.79e308'
NO
max_plausible_value float Applicable to quantitative descriptors only; in support of a plausibility check for values. Example: for tree height this could be 99
Default value: '1.79e308'
NO
sequence_type nvarchar (255) Type of molecular sequence, "Nucleotide" or "Protein". The value "Nucleotide" covers RNA and DNA sequences
Default value: 'Nucleotide'
NO
symbol_length tinyint The number of letters in each symbol. Nucleotides are always codes with 1-letter symbols, but proteins may use 1 or 3-letter codes (e.g. A or Ala for alanine)
Default value: '1'
NO
enable_ambiguity_symbols tinyint Set to 1 if ambiguity symbols are supported in the sequence string, e.g. R, Y, S, W for nucleotides or B, Z for proteins
Default value: '1'
NO
gap_symbol nvarchar (3) A string identifying the "gap" symbol used in aligned sequences. The gap symbol must always be symbol_length long
Default value: NULL
YES
wording_before nvarchar (255) Representation for natural language output, inserted before the states/value
Default value: NULL
YES
wording_after nvarchar (255) Representation for natural language output, inserted after the states/value
Default value: NULL
YES
data_entry_note nvarchar (MAX) A note or prompt when entering or dealing with data YES
wording nvarchar (255) Optional separate wording for natural language generation (label will be used if this is missing)
Default value: NULL
YES

Table DescriptorInapplicability

The descriptor dependency rules

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
controlled_descriptor_id int Reference to the descriptor to which the rule will apply, e.g. which will be inapplicable if controlling state applies to the same description (foreign key) NO
controlling_state_id int Reference to the controlling categorical state; if present in a description, controlled descriptor is affected according to rule NO
rule nvarchar (255) The kind of rule creating a descriptor inapplicability ("inapplicable-if", "applicable-if", "inapplicable-computed-from-applicable")
Default value: 'inapplicable-if'
NO

Table DescriptorStatusData

The status data of a descriptor for a certain description

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int Reference to the description to which these data belong (foreign key) NO
descriptor_id int Reference to the descriptor to which the status value belongs (foreign key) NO
datastatus_id int Reference to a status definition. Status is like a marker why data is missing or in need of revision (examples: “unknown”, “not applicable”, “to be checked”, “data withheld” etc.) (foreign key) NO
notes nvarchar (MAX) Free-form text detailing additional information (rarely used, not multilingual) YES

Table DescriptorTree

The root and definition of a descriptor tree

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
is_complete tinyint Set to 1 if this tree includes the largest possible set of descriptors for the taxon set associated with a project (i.e. the "master-descriptor tree", other trees being subsets)
Default value: '0'
NO
label nvarchar (255) Short label (or name) of descriptor tree NO
type nvarchar (255) "mixed", "part-of", "property" or "generalization" NO
project_id int Each tree belongs to exactly one project (required, foreign key) NO

Table DescriptorTreeNode

The descriptor tree nodes representing either nodes of the tree or descriptors (“leafes” of the tree)

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
parent_node_id int Reference to a parent node, creating a true tree; NULL for a root node (foreign key)
Default value: NULL
YES
label nvarchar (255) Short label (or name) of internal node associated with a concept; NULL for a descriptor node
Default value: NULL
YES
abbreviation nvarchar (255) Abbreviated label of node
Default value: NULL
YES
display_order int A positive number defining the sequence in which child nodes are displayed
Default value: '0'
NO
descriptortree_id int Reference to a descriptor tree; all nodes must have a direct link to the tree definition (foreign key) NO
descriptor_id int Reference to a descriptor; NULL if the present node is an inner concept node defining a hierarchy of nodes or descriptors (foreign key)
Default value: NULL
YES
detail nvarchar (MAX) Additional detail text explaining or commenting on the node definition YES

Table DescriptorTreeNodeRecFrequency

Selection of recommended frequency values for descriptor tree parts or single descriptors

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
node_id int Reference to the descriptor tree node (foreign key) NO
frequency_id int Reference to the recommended frequency modifier (foreign key) NO

Table DescriptorTreeNodeRecModifier

Selection of recommended modifier values for descriptor tree parts or single descriptors

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
node_id int Reference to the descriptor tree node (foreign key) NO
modifier_id int Reference to the recommended modifier (foreign key) NO

Table DescriptorTreeNodeRecStatMeasure

Selection of recommended statistical measures for descriptor tree parts or single descriptors

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
node_id int Reference to the descriptor tree node (foreign key) NO
measure_id int Reference to the recommended measure (foreign key) NO

Table Frequency

Definition of frequency modifier values

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of frequency modifier (e.g. "very rare", "rare", "usually" etc.) NO
lower_estimate float Each frequency modifier defines a frequency range, this is the estimated lowest frequency
Default value: '0'
NO
upper_estimate float As above, estimate of upper range for the border; note: ranges may overlap!
Default value: '1'
NO
display_order int A positive number defining the sequence in which frequency modifiers are to be displayed
Default value: '0'
NO

Table ImportMapping

The import mappings to support mapping of external file keys to database keys

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
object_id int Reference to the object to which the mapping belongs, references BaseEntity (foreign key) NO
session_id int Reference to the import session to which the mapping belongs, references ImportMapping (foreign key) NO
table_name varchar (50) Name of the import table NO
parent_key varchar (255) Symbolic key of the parent table NO
external_key nvarchar (255) External key in the import file NO

Table ImportSession

The import sessions to support import of data spread over several files

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
project_id int Each import session belongs to exactly one project (required, foreign key) NO
detail nvarchar (MAX) Detail text explaining the import session definition YES
create_timestamp datetime Date and time when the import session was created
Default value: getdate()
NO
update_timestamp datetime Date and time when the import session was updated
Default value: getdate()
NO

Table Modifier

Definition of modifier values

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
class nvarchar (255) Grouping of modifiers into classes ("Certainty", "Seasonal", "Diurnal", "TreatAsMisinterpretation" or "OtherModifierClass") NO
label nvarchar (255) Short label (or name) of modifier (e.g. "strong", "probably" etc.) NO
display_order int A positive number defining the sequence in which modifiers are to be displayed
Default value: '0'
NO

Table MolecularSequenceData

The molecular sequence data of a description

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int Reference to description to which these data belong (foreign key) NO
descriptor_id int Reference to a molecular sequence descriptor to which the sequence text belongs (foreign key) NO
sequence nvarchar (MAX) Molecular sequence text referring to information on one descriptor NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES

Table MolecularSequenceSamplingData

The molecular sequence data recorded for a sampling event

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
sampling_unit_id int Reference to a sampling unit (foreign key) NO
descriptor_id int Reference to a molecular sequence descriptor to which the sequence text belongs (foreign key) NO
sequence nvarchar (MAX) Molecular sequence text referring to information on one descriptor NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES

Table OtherScope

Scope values for description scope values for scope types “Other scope”, “Part”, “Stage” and “Sex”

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of scope (e.g. "male", "female", "adult", "juvenile" etc.) NO
detail nvarchar (MAX) Additional detail text explaining or commenting on the scope and delimitation of the present description YES
type nvarchar (255) Describes the scope type ("sex", "stage", "part" or "other") NO
sex_status_id int Reference to sex status value according SDD V5.1 (foreign key)
Default value: NULL
YES

Table Project

Projects define separated workareas in a single database

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
parent_project_id int Reference to a parent project, creating a subproject; NULL for a root project (foreign key)
Default value: NULL
YES
label nvarchar (255) Short label (or name) of project (or subproject); each project defines a separate work environment within a shared database by means of defining sets of descriptors (through DescriptorTree) NO
rights_text nvarchar (255) The default rights and licence statement for the entire project; BaseEntity provides means to override this for individual objects
Default value: NULL
YES
licence_uri nvarchar (255) URI of licence for the project; BaseEntity provides means to override this for individual objects
Default value: NULL
YES
detail nvarchar (MAX) Additional detail text explaining or commenting on the project (or subproject) YES
primary_language_code nvarchar (3) Language of primary text version (fields directly in tables, may be translated in table Translation); Examples: "de", "en" etc. (ISO 639 language code) NO
ProjectProxyID int Reference to a project definition of DiversityProjects that allows control of access rights
Default value: (0)
NO
wording nvarchar (255) Optional separate wording for natural language generation and cache database (label will be used if this is missing)
Default value: NULL
YES

Table Project_AvailableScope

Scope values available for a certain project

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
project_id int Reference to the project for which a shall be available (foreign key) NO
scope_id int Reference to a scope definition in OtherScope (foreign key) NO

Table QuantitativeSamplingData

The quantitative data recorded for a sampling event

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
measure_id int Optional statistical measure (minimum, mean, maximum, ranges, sample size, variance etc.) recorded in value; if NULL, value is a direct measurement (foreign key)
Default value: NULL
YES
sampling_unit_id int Reference to a sampling unit (foreign key) NO
descriptor_id int Reference to descriptor which the values record (foreign key) NO
value float The value for the statistical measure or single measurement/recording NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES
modifier_id int Optional reference to a modifier definition (e.g. "strongly", "at the base", "in autumn") (foreign key)
Default value: NULL
YES

Table QuantitativeSummaryData

The quantitative data of a description

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
measure_id int Reference to the statistical measure (minimum, mean, maximum, ranges, sample size, variance etc.) recorded in value (foreign key) NO
description_id int Reference to the description to which these data belong (foreign key) NO
descriptor_id int Reference to the descriptor which the values record (foreign key) NO
value float The value of the statistical measure NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES
modifier_id int Optional reference to a modifier definition (e.g. "strongly", "at the base", "in autumn") (foreign key)
Default value: NULL
YES

Table Resource

Hyperlinks to separate rich text/media objects

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
terminology_role nvarchar (255) Role in relation to descriptors or states ("unknown"=role not known or not specified; "diagnostic"=optimized for identification; "iconic"=icon/thumbnail, needs text; "normative"=defines a resource object; "primary"=display always, informative without text; "secondary"=display only on request)
Default value: 'unknown'
NO
ranking_for_terminology tinyint Ranking of the resource with respect to terminology; range: 0 to 10
Default value: NULL
YES
descriptor_id int Optional reference to a descriptor (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)
Default value: NULL
YES
state_id int Optional reference to a categorical state (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)
Default value: NULL
YES
taxon_role nvarchar (255) Role in relation to taxa or descriptions ("unknown"=role not known or not specified; "diagnostic"=optimized for identification; "iconic"=icon/thumbnail, needs text; "normative"=defines a resource object; "primary"=display always, informative without text; "secondary"=display only on request)
Default value: 'unknown'
NO
ranking_for_taxon_use tinyint Ranking of the resource with respect to taxa or descriptions; range: 0 to 10
Default value: NULL
YES
taxon_id int Optional reference to a taxon (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)
Default value: NULL
YES
description_id int Optional reference to a description (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)
Default value: NULL
YES
scope_id int Reference to the scope of the resource (e.g. "sex", "stage", "season" etc.)
Default value: NULL
YES
display_embedded tinyint false/0: display as link, true/1: display as embedded media object
Default value: '0'
NO
label nvarchar (255) Short label of (or caption for) the resource, e.g. a text displayed below an image or instead of the link NO
detail nvarchar (MAX) Additional detail text explaining or commenting on the resource definition YES
language_code nvarchar (3) Language of the resource itself, use zxx for language neutral/no linguistic content (ISO 639-1)
Default value: NULL
YES
rights_text nvarchar (255) The rights and licence statement for the resource
Default value: NULL
YES
licence_uri nvarchar (255) URI of licence for the resource
Default value: NULL
YES
display_order int A positive number defining the sequence in which multiple resources are displayed
Default value: '0'
NO
node_id int Optional reference to a descriptor tree node (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)
Default value: NULL
YES

Table ResourceVariant

Different resource variants/instances/service access points

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
resource_id int Reference to the resource to which these variants provide access points (foreign key) NO
variant_id int Reference to the definition of a variant class e.g. "tiny sample", "small sample", "lower quality", "medium quality", "good quality" or "best quality" (foreign key) NO
url nvarchar (255) URL of the resource variant NO
pixel_width int Where applicable (still- or moving image): the width in pixel
Default value: NULL
YES
pixel_height int Where applicable (still- or moving image): the height in pixel
Default value: NULL
YES
duration int Where applicable (sound or moving image): the duration in seconds
Default value: NULL
YES
size int The size of the resource in bytes
Default value: NULL
YES
mime_type nvarchar (255) Type of the resource as MIME type like image/jpeg; color as color/hexrgb
Default value: NULL
YES

Table ResourceVariant_Enum

Classes for resource variants, values are predefined in the database

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of resource variant class ("tiny sample", "small sample", "lower quality", "medium quality", "good quality" or "best quality") NO
code nvarchar (255) Brief code equivalent to the (longer) label NO
detail nvarchar (MAX) Additional detail text explaining the resource variant class YES
quality_order int A positive number providing a filter mechanism for "tiny sample" to "best quality"; the smaller the number, the less quality a resource has
Default value: '0'
NO

Table SamplingEvent

A sampling event may contain many sampling units

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int Reference to the description to which these sampling data belong (foreign key) NO
label nvarchar (255) Free-form text identifying a sampling event to humans. Sampling events have time, location, perhaps purpose and act as a container for multiple sampling units.
Default value: NULL
YES
detail nvarchar (MAX) Free-form text giving detail or description of sampling event YES
date_time datetime Date and time when the event occurred; single point or start of duration
Default value: NULL
YES
datetimespan_end datetime Optional end of a time span or duration within which or during which the event occurred
Default value: NULL
YES
geographic_area nvarchar (255) A geographic area at which the event occurred
Default value: NULL
YES
geographic_area_uri nvarchar (255) Reference to a geographic area in DiversityGazetteers
Default value: NULL
YES
coord_dec_latitude float Latitude of geographical coordinates in signed decimal degrees
Default value: NULL
YES
coord_dec_longitude float Longitude of geographical coordinates in decimal degrees
Default value: NULL
YES
coord_literal nvarchar (255) Free-form string, either in addition to or instead of code (a mapping to the controlled vocabulary may be unavailable or considered ambiguous)
Default value: NULL
YES
coord_geodeticdatum nvarchar (50) Optional, only where knowledge of the geodetic datum is readily available; defaults to WGS84 used in GPS
Default value: NULL
YES

Table SamplingUnit

Sampling unit data

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
sampling_event_id int Reference to a sampling event; keeps paired measurements together (several categorical or quantitative observations at the same time on the same object or object part) (foreign key) NO
collection_specimen nvarchar (255) A collection specimen that is represented by the sampling unit
Default value: NULL
YES
collection_specimen_uri nvarchar (500) Reference to a collection specimen in DiversityCollection
Default value: NULL
YES

Table SexStatus_Enum

Values of sex status predefined according to SDD 1.1 rev 5

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of sex status NO
code nvarchar (255) Code of sex status NO
abbreviation nvarchar (255) One or two (intuitive) characters NO
detail nvarchar (MAX) Additional detail text explaining or commenting on the sex status definition YES
display_order int A positive number defining the sequence in which sex status values are displayed
Default value: '0'
NO

Table StatisticalMeasure_Enum

The statistical measures predefined according SDD 1.1 rev 5

Column Data type Description Nullable
id int Database-internal ID of this record, references BaseEntity (primary key) NO
label nvarchar (255) Short label (or name) of statistical measure NO
code nvarchar (255) Code of statistical measure according SDD 1.1 rev 5 NO
abbreviation nvarchar (255) Abbreviation of statistical measure NO
display_order int A positive number defining the sequence in which statistical measures are displayed
Default value: '0'
NO

Table TextDescriptorData

The text data of a description

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
description_id int Reference to description to which these data belong (foreign key) NO
descriptor_id int Reference to a text descriptor to which the free-form text belongs (foreign key) NO
content nvarchar (MAX) Free-form text referring to information on one descriptor NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES

Table TextSamplingData

Free-form text data recorded for a sampling event

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
sampling_unit_id int Reference to a sampling unit (foreign key) NO
descriptor_id int Reference to descriptor to which the free-form text belongs (foreign key) NO
content nvarchar (MAX) Free-form text referring to information on one descriptor NO
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the data YES

Table Translation

The translations of entries related to BaseEntity

Column Data type Description Nullable
id int Database-internal ID of this record (primary key) NO
object_id int Reference to the object to which the translation belongs, references BaseEntity (foreign key) NO
language_code nvarchar (3) Language of representation translation (ISO 639 language code) NO
column_id int References the translated column name NO
contents nvarchar (MAX) Translated contents YES

Table TranslationColumn_Enum

The TranslationColumn_Enum contains the column names that are translated in the Translation table

Column Data type Description Nullable
id int Database-internal object ID of this record (primary key) NO
column nvarchar (255) Name of column that is translated in the Translation table NO
May 3, 2024

History

History

To inspect the history of a data set click on the button. A window will open showing all former states of the data in tables with the current data set at the top. 

 

If you have sufficient access rights for the database (role administrator), the buttons Restore deleted and Restore data as in selected line are available (see image below). If you want to restore an old version of a data set, choose the corresponding line in the table and click on the Restore data as in selected line button.

 

If you want to restore a whole data set including the dependent data, click on the Restore deleted button. This function is as well available from the menu Data → Restore from log …. In the upcoming dialogs choose the basic table to start for the search. In the upcoming dialogs enter the date where the query should start and the number of lines from the log table that should be displayed. Finally select the datarow(s) of the root table that should be restored. After that the program will try to recover the data with all depending information.

Depending on selected edit mode (“Descriptions”, “Descriptors” or “Projects”) the marked tables in the overview below may be selected as basic tables for restorage. With “->” dependent tables are marked that will be restored automatically, if the parent has been successfully restored.

  • Edit mode “Descriptions”:
    Translation
    Description -> SamplingEvent -> SamplingUnit
    -> DescriptionScope -> CategoricalSamplingData
    -> CategoricalSummaryData -> QuantitativeSamplingData
    -> QuantitativeSummaryData -> TextSamplingData
    -> TextDescriptorData -> MolecularSequenceSamplingData
    -> MolecularSequenceData
    -> Resource * -> ResourceVariant
  • Edit mode “Descriptors”:
    Translation
    Descriptor -> CategorialState    
    -> Resource * -> ResourceVariant
  • Edit mode “Projects”:
    Translation
    Project -> OtherScope    
    DescriptorTree -> DescriptorTreeNode  
      -> DescriptorTreeNodeRecFrequency  
      -> DescriptorTreeNodeRecModifier
      -> DescriptorTreeNodeRecStatMeasure
    -> Resource * -> ResourceVariant

* Remark: If you restore an object that assigns resources, be aware that during delete processing in many cases the link from the resource to the deleted object was set to null before deleting the resource itself. In those cases after restoring the target object you have take a look in the history to restore the resource link using the button Restore data as in selected line.

After successful restorage a message will give you an overview of the performed actions.

May 16, 2024

Installation Database

Installation of the database

DiversityDescriptions uses Microsoft SQL-Server 2012 or higher as database engine. When you have a database file from an older version of Microsoft SQL-Server, they can be attached to the newer version, since it will be updated automatically. You may use a centralized SQL-Server that is accessible by several users, e.g. over a local area network or run a local database server on your own PC.

If you do not have a database server with DiversityDescriptions already available, you have to install the database engine first. Download the free version of Microsoft SQL Server Express (e.g. SQLEXPRADV_x86_DEU.exe ) from http://www.microsoft.com/downloads/. Start the program and follow the instructions for the installation. After the installation make shure to get the latest updates using Windows Update.

When you have installed and configured your database server, you need an empty database to be used with your client applications. In principle two different procedings are available:

  • Attach a database file
    Download the database files DiversityDescriptions_Base.MDF  and DiversityDescriptions_Base_log.LDF  from http://www.diversityworkbench.net/Portal/ provided as a zip archive (DiversityDescriptions.zip) and copy them into your database directory. Then follow the steps described below.

    or
     

  • Create a new database
    The new application versions provide the option to create a new database and install all required elements. To use this option you have to connect to the database with a login that has system administation rights in the database. This option requires Microsoft SQL Server 2012 or higher.

The first alternative is also feasable, if you get database files from a different server or if you want to relocate the database files to a different disk directory. In the latter case you first have to “Detach” (“Trennen”) your database, move the files to the target directory and then “Attach” (“Anfügen”) it. 

 

Server configuration

To configure your server, launch the SQL Server Configuration Manager (see image below, please consider that in this example the two SQL-Servers “SQLEXPRESS” and “MSSQLSERVER” are installed).

Then click on the “Protocols for SQLEXPRESS” node. Right click on “TCP/IP” in the list of Protocols and choose “enable” for TCP/IP.

Right click on the TCP/IP node and select “Properties” to open a window as shown below.

In the part IPALL clear out the value for “TCP Dynamic Ports”. Give a TCP-Port number to use when making remote connections, e.g. “5432” as shown above. You have to restart the SQL Server Express service before you can connect to your database. 

If you use a database on a centralized server that shall be reachable over a computer network, make sure that the firewall of the server allows access via the port you set for the connections (see below). 

Attach a database file

Start the Microsoft SQL Server Managment Studio and connect to the database server with a system administrator login. Attach the database as shown below: Choose the node “Databases” (“Datenbanken”) and right-click on it to open the context menu (see below). Then choose “Attach” (“Anfügen”) from the context menu. A window will open where you can choose the file DiversityDescriptions_Base.MDF from your database directory and attach it to the database engine. The database files you attach must be created by a database server of the same or a lower version. Usually the Mircosoft SQL Server supports three predecessor versions. E.g. if you are using Microsof SQL Sever 2014, you should be able to attach database files for SQL Server 2014, 2012 and 2008 R2. 

 

Connect to database

Start the program DiversityDescriptions.exe and in the main window click on the button or choose Connection -> Database … from the menu. A window as shown below will open. Here enter the server name or the IP address (here “localhost” for a local database on the own PC) and its IP port (5432 in example below) to connect to your SQL-server and select the database file in your directory.

 

Database configuration

To configure your database, use the client as described in Database configuration.

Jan 14, 2025

Linked server

Linked server

Databases not available on the local server may be accessible via a linked server. To administrate the linked servers, choose Administration → Linked servers … from the menu. A form (see below) will open where you can add linked servers and inspect the content of the available databases.

Use the  resp. buttons to add or remove a linked server. To add a linked server, you need the name of the server and the port, e.g. tnt.diversityworkbench.de, 5432, the login associated with the connection of the linked server e.g. TNT and the password for this login. The available databases will be listed as shown above. To inspect the content, select among the tables or views listed in the right part as shown above. Linked servers have certain restrictions for the availability of data, e.g. XML and geography data are not available via a linked server. For a table or view containing incompatible content you may encounter a corresponding error mentioning the reason for the incompatibility.

May 16, 2024

Logging

Logging

Changes within the database will be documented for each data set together with the time and the responsible user in the columns shown in the image below.

All main tables have a corresponding logging table. If you change or delete a data set, the original data set will be stored in this logging table together with information about by whom and when changes were made last.

May 3, 2024

Diversity Descriptions

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES


Table Annotation

One record per annotated object (Char, State, Descr. etc.)

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
object_id int Reference to object to which the annotation belongs, references BaseEntity (foreign key) NO Refers to table BaseEntity
language_code nvarchar (3) Language of annotation text (ISO 639 language code) NO -
contributor_id int Contributors of annotations may be different from contributors of the object that is being annotated. Each annotation has only a single contributor. NO Refers to table Contributor
timestamp datetime Date and time when the annotation was entered. Annotations are never changed and only the most recent annotation is valid/current.Default value: getdate() NO -
content nvarchar (MAX) Free-form text annotating an object in the database, e.g. a descriptor, state, modifier, description etc. NO -
is_internal tinyint Set to 1 if text is a project internal note that should not normally be present on public pages. Goal is reduction of “annotation noise”, not confidentiality. At least project contributors will be able to read internals.Default value: ‘0’ NO -
is_latest_revision tinyint Set to 1 if this annotation is the latest by a given contributor. Annotations can never be changed, but each revision creates a new version. Only the latest version is valid.Default value: ‘0’ NO -
MEMO_WhichVersionsInheritIsNotSolved int - NO -

Depending on:

  • BaseEntity
  • Contributor

Table BaseEntity

The BaseEntity is used within the database to provide unique keys

Column Data type Description Nullable Relation
id int Database-internal object ID, unique across all tables in database (primary key) NO -
table_id int References the table name of table entries associated with the BaseEntity; NULL indicates orphaned entries and may be used for garbage collection of otherwise deleted object idsDefault value: NULL YES Refers to table BaseEntityTable_Enum
specific_rights_text nvarchar (255) To be used where the licence for an object differs from the default project licenceDefault value: NULL YES -
specific_licence_uri nvarchar (255) URI of licence, where different from project licenceDefault value: NULL YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntityTable_Enum

Table CacheDatabase

Table holding the cache databases connected to the database

Column Data type Description Nullable Relation
Server varchar (50) The name or IP of the server where the cache database is located NO -
DatabaseName varchar (50) The name of the cache database NO -
Port smallint The port of the server where the cache database is located NO -
Version varchar (50) The version of the cache database YES -

Table CacheMappingDescription

Table holding the description key mappings for the cache database

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
project_id int Reference to the description project (foreign key) NO Refers to table Project
description_id int Reference to the description to which these data belong (foreign key) NO Refers to table Description
target_key int Mapped key value for the target of the cache database. NO -

Depending on:

  • Description
  • Project

Table CacheMappingDescriptor

Table holding the descriptor key mappings for the cache database

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
project_id int Reference to the descriptor project (foreign key) NO Refers to table Project
descriptor_id int Reference to the descriptor to which these data belong (foreign key) NO Refers to table Descriptor
target_key int Mapped key value for the target of the cache database. NO -
last_state_key int Highest value of state key. Relevant for key_mapping_level > 0Default value: (0) YES -

Depending on:

  • Descriptor
  • Project

Table CacheMappingState

Table holding the categorical state key mappings for the cache database

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
project_id int Reference to the state project (foreign key) NO Refers to table Project
state_id int Reference to the categorical state to which these data belong (foreign key) NO Refers to table CategoricalState
target_key int Mapped key value for the target of the cache database. NO -

Depending on:

  • CategoricalState
  • Project

Table CacheProject

Table holding the project settings for the cache database

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
project_id int Reference to the description project (foreign key) NO Refers to table Project
withheld_data_level tinyint Flag for handling of withheld descriptor data. 0=withhold description; 1=withhold descriptor; 2=do not withhold dataDefault value: (0) YES -
key_mapping_level tinyint Flag for handling of key mapping. 0=re-build mapping for each update; 1=keep first mapping; 2=additionally take numeric values of alternate ID for items; >2 as 2 but re-initialize tableDefault value: (1) YES -
last_char_key int Highest value of character key. Relevant for key_mapping_level > 0Default value: (0) YES -
last_item_key int Highest value of item key. Relevant for key_mapping_level > 0Default value: (0) YES -
last_changes datetime The recent date when data within the project had been changedDefault value: getdate() YES -

Depending on:

  • Project

Table CategoricalSamplingData

The categorical data recorded for a sampling event

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO -
sampling_unit_id int Reference to the sampling unit (foreign key) NO Refers to table SamplingUnit
state_id int Reference to the state (descriptor is implicit in state_id) (foreign key) NO Refers to table CategoricalState
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
modifier_id int Optional reference to a modifier definition (e.g. “strongly”, “at the base”, “in autumn”) (foreign key)Default value: NULL YES Refers to table Modifier
frequency_value int Number of times this category was observed within a single sampling unitDefault value: NULL YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • CategoricalState
  • Modifier
  • SamplingUnit

Table CategoricalState

The categorical states available for categorical descriptors

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
descriptor_id int Reference to the descriptor to which the state belongs (foreign key) NO Refers to table Descriptor
label nvarchar (255) Short label (or name) of descriptor state NO -
abbreviation nvarchar (255) Abbreviated label of descriptor stateDefault value: NULL YES -
detail nvarchar (MAX) Additional detail text explaining or commenting on the descriptor state definition YES -
wording nvarchar (255) Optional separate wording for natural language generation (label will be used if this is missing)Default value: NULL YES -
display_order int A positive number defining the sequence in which descriptor states are displayedDefault value: ‘0’ NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • Descriptor

afterDeleteCategoricalState

afterInsertCategoricalState

trgCrCategoricalState


Table CategoricalSummaryData

The categorical data of a description

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
description_id int Reference to the description to which these data belong (foreign key) NO Refers to table Description
state_id int Reference to the state (the descriptor is implicit in state_id) (foreign key) NO Refers to table CategoricalState
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
modifier_id int Optional reference to a modifier definition (e.g. “strongly”, “at the base”, “in autumn”) (foreign key)Default value: NULL YES Refers to table Modifier
frequency_id int Optional reference to a frequency modifier definition (e.g. “rarely”, “usually”, “mostly”) (foreign key)Default value: NULL YES Refers to table Frequency
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • CategoricalState
  • Description
  • Frequency
  • Modifier

trgCrCategoricalSummaryData


Table Contribution

Multiple contributors may contribute in different roles

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
object_id int Reference to an object which the contributor has created or contributed to, references BaseEntity (foreign key) NO Refers to table BaseEntity
contributor_id int Reference to a contributor (foreign key) NO Refers to table Contributor
role nvarchar (255) TODO: expand enumeration, perhaps rather as linked vocabulary?Default value: ‘contributor’ NO -
timestamp datetime Date and time of a contributionDefault value: getdate() NO -

Depending on:

  • BaseEntity
  • Contributor

Table Contributor

People contibuting to a work. Roles are recorded in Contribution

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
email nvarchar (255) User’s email addressDefault value: NULL YES -
web_pseudonym nvarchar (255) Optional alternative name to display publicly on the webDefault value: NULL YES -
avatar_uri nvarchar (255) Optional URI to an image representing the userDefault value: NULL YES -
real_name nvarchar (255) Optional name the user gave (full name)Default value: NULL YES -
linked_agent_uri nvarchar (255) Linking to agents managed in an external componentDefault value: NULL YES -

Table Description

The description in the database

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
label nvarchar (255) Short label (or name) of descriptionDefault value: NULL YES -
detail nvarchar (MAX) Additional detail text explaining or commenting on the description definition YES -
project_id int Each description belongs to exactly one project that determines its terminology (required, foreign key) NO Refers to table Project
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
alternate_id nvarchar (30) Optional alternate id of a description item - should be unique within one project, but not checked by databaseDefault value: NULL YES -
wording nvarchar (255) Optional separate wording for natural language generation (label will be used if this is missing)Default value: NULL YES -

Depending on:

  • BaseEntity
  • Project

afterDeleteDescription

afterInsertDescription


Table DescriptionProject

The projects where descriptions are accessible

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
description_id int ID of the description that belongs to the project (required, foreign key) NO Refers to table Description
project_id int ID of the project to which the description belongs (required, foreign key) NO Refers to table Project
LogInsertedBy nvarchar (50) ID of the creator of this data set YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database. YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set last YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES -

Depending on:

  • Description
  • Project

trgCrDescriptionProject


Table DescriptionScope

The scope of the description

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
description_id int Reference to the description to which these data belong (foreign key) NO Refers to table Description
label nvarchar (255) Short label (or name) of scopeDefault value: NULL YES -
dwbURI nvarchar (500) Reference to DiversityWorkbench componentDefault value: NULL YES -
type nvarchar (255) Scope type (“GeographicArea”, “SamplingPlot”, “Citation”, “Observation”, “Specimen”, “TaxonName”, “OtherConcept”, “Stage”, “Part” or “Sex”)Default value: NULL YES -
other_scope_id int Reference to further scopes, e.g. stage, sex etc. (foreign key)Default value: NULL YES Refers to table OtherScope
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Description
  • OtherScope

trgCrDescriptionScope


Table Descriptor

Descriptor (= characters, features) define variables

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
label nvarchar (255) Short label (or name) of descriptor NO -
abbreviation nvarchar (255) Abbreviated label of descriptorDefault value: NULL YES -
detail nvarchar (MAX) Additional detail text explaining or commenting on the descriptor definition YES -
display_order int A positive number defining the sequence in which descriptors are displayedDefault value: ‘0’ NO -
subclass nvarchar (255) The four character subclasses of SDD are all combined here in one entity and distinguished by this attribute (“categorical”, “quantitative”, “text” or “sequence”)Default value: ‘categorical’ NO -
statistical_measurement_scale nvarchar (255) Scale of descriptor: Categorical may be nominal (unordered, “red/green/blue”) or ordinal (ordered, “bad/medium/good”); Quantitative may be interval (°C) or ratio (mass, length, time, K)Default value: ’nominal' NO -
usually_exclusive tinyint Applicable to categorical (nominal/ordinal) descriptors only. If usually exclusive = 1, then by default the user interface allows only entering one state. Nevertheless, multiple states in the data are valid.Default value: ‘0’ NO -
state_collection_model nvarchar (255) Handling of multiple values: OrSet/AndSet: unordered set combined with or/and, OrSeq/AndSeq: ordered sequence combined with or/and, WithSeq: example is “green with brown”, Between: an example is “oval to elliptic”Default value: ‘OrSet’ NO -
mandatory tinyint Is the scoring of this descriptor mandatory (required) in each item?Default value: ‘0’ NO -
repeatability nvarchar (255) How reliable and consistent are repeated measurements or scorings of the descriptor by different observers and on different objects? (“ignore”, “very low”, “low”, “below average”, “slightly below average”, “standard”, “slightly above average”, “above average”, “high” or “very high”)Default value: ‘standard’ NO -
availability nvarchar (255) How available is the descriptor or concept for identification? (“ignore”, “very low”, “low”, “below average”, “slightly below average”, “standard”, “slightly above average”, “above average”, “high” or “very high”)Default value: ‘standard’ NO -
measurement_unit nvarchar (255) A measurement unit (mm, inch, kg, °C, m/s etc.) or dimensionless scaling factorDefault value: NULL YES -
measurement_unit_precedes_value tinyint Set to 1 if the measurement unit precedes the valueDefault value: ‘0’ NO -
values_are_integer tinyint Set to 1 if the values are integerDefault value: ‘0’ NO -
min_plausible_value float Applicable to quantitative descriptors only; in support of a plausibility check for values. Example: for tree height this could be 0, i.e. only positive values allowedDefault value: ‘-1.79e308’ NO -
max_plausible_value float Applicable to quantitative descriptors only; in support of a plausibility check for values. Example: for tree height this could be 99Default value: ‘1.79e308’ NO -
sequence_type nvarchar (255) Type of molecular sequence, “Nucleotide” or “Protein”. The value “Nucleotide” covers RNA and DNA sequencesDefault value: ‘Nucleotide’ NO -
symbol_length tinyint The number of letters in each symbol. Nucleotides are always codes with 1-letter symbols, but proteins may use 1 or 3-letter codes (e.g. A or Ala for alanine)Default value: ‘1’ NO -
enable_ambiguity_symbols tinyint Set to 1 if ambiguity symbols are supported in the sequence string, e.g. R, Y, S, W for nucleotides or B, Z for proteinsDefault value: ‘1’ NO -
gap_symbol nvarchar (3) A string identifying the “gap” symbol used in aligned sequences. The gap symbol must always be symbol_length longDefault value: NULL YES -
wording_before nvarchar (255) Representation for natural language output, inserted before the states/valueDefault value: NULL YES -
wording_after nvarchar (255) Representation for natural language output, inserted after the states/valueDefault value: NULL YES -
data_entry_note nvarchar (MAX) A note or prompt when entering or dealing with data YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
wording nvarchar (255) Optional separate wording for natural language generation (label will be used if this is missing)Default value: NULL YES -

Depending on:

  • BaseEntity

afterDeleteDescriptor

afterInsertDescriptor


Table DescriptorInapplicability

The descriptor dependency rules

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
controlled_descriptor_id int Reference to the descriptor to which the rule will apply, e.g. which will be inapplicable if controlling state applies to the same description (foreign key) NO Refers to table Descriptor
controlling_state_id int Reference to the controlling categorical state; if present in a description, controlled descriptor is affected according to rule NO Refers to table CategoricalState
rule nvarchar (255) The kind of rule creating a descriptor inapplicability (“inapplicable-if”, “applicable-if”, “inapplicable-computed-from-applicable”)Default value: ‘inapplicable-if’ NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • CategoricalState
  • Descriptor

Table DescriptorMapping_C2C

Mapping of a categorical state to another categorical state

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
from_state_id int Reference to a categorical state that shall be mapped to target state NO Refers to table CategoricalState
to_state_id int Reference to a categorical state that shall be the target state NO -

Depending on:

  • CategoricalState

Table DescriptorMapping_Q2C

Mapping of a quantitative descriptor to a categorical state

Column Data type Description Nullable Relation
id int Database-internal ID of this record (foreign key) NO -
from_descr_id int Reference to quantitative descriptor that shall be mapped NO Refers to table Descriptor
from_lowerbound float - NO -
from_upperbound float - NO -
from_statistical_measure_id int - NO Refers to table StatisticalMeasure_Enum
from_statmeas_class_TO_CONSIDER int - NO -
to_state_id int Reference to a categorical state that shall be the target state NO Refers to table CategoricalState

Depending on:

  • CategoricalState
  • Descriptor
  • StatisticalMeasure_Enum

Table DescriptorStatusData

The status data of a descriptor for a certain description

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
description_id int Reference to the description to which these data belong (foreign key) NO Refers to table Description
descriptor_id int Reference to the descriptor to which the status value belongs (foreign key) NO Refers to table Descriptor
datastatus_id int Reference to a status definition. Status is like a marker why data is missing or in need of revision (examples: “unknown”, “not applicable”, “to be checked”, “data withheld” etc.) (foreign key) NO Refers to table DataStatus_Enum
notes nvarchar (MAX) Free-form text detailing additional information (rarely used, not multilingual) YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • DataStatus_Enum
  • Description
  • Descriptor

trgCrDescriptorStatusData


Table DescriptorTree

The root and definition of a descriptor tree

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
is_complete tinyint Set to 1 if this tree includes the largest possible set of descriptors for the taxon set associated with a project (i.e. the “master-descriptor tree”, other trees being subsets)Default value: ‘0’ NO -
label nvarchar (255) Short label (or name) of descriptor tree NO -
type nvarchar (255) “mixed”, “part-of”, “property” or “generalization” NO -
project_id int Each tree belongs to exactly one project (required, foreign key) NO Refers to table Project
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • Project

afterDeleteDescriptorTree

afterInsertDescriptorTree


Table DescriptorTreeNode

The descriptor tree nodes representing either nodes of the tree or descriptors (“leafes” of the tree)

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
parent_node_id int Reference to a parent node, creating a true tree; NULL for a root node (foreign key)Default value: NULL YES Refers to table DescriptorTreeNode
label nvarchar (255) Short label (or name) of internal node associated with a concept; NULL for a descriptor nodeDefault value: NULL YES -
abbreviation nvarchar (255) Abbreviated label of nodeDefault value: NULL YES -
display_order int A positive number defining the sequence in which child nodes are displayedDefault value: ‘0’ NO -
descriptortree_id int Reference to a descriptor tree; all nodes must have a direct link to the tree definition (foreign key) NO Refers to table DescriptorTree
descriptor_id int Reference to a descriptor; NULL if the present node is an inner concept node defining a hierarchy of nodes or descriptors (foreign key)Default value: NULL YES Refers to table Descriptor
detail nvarchar (MAX) Additional detail text explaining or commenting on the node definition YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • Descriptor
  • DescriptorTree

afterDeleteDescriptorTreeNode

afterInsertDescriptorTreeNode

trgCrDescriptorTreeNode


Table DescriptorTreeNodeRecFrequency

Selection of recommended frequency values for descriptor tree parts or single descriptors

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
node_id int Reference to the descriptor tree node (foreign key) NO Refers to table DescriptorTreeNode
frequency_id int Reference to the recommended frequency modifier (foreign key) NO Refers to table Frequency
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • DescriptorTreeNode
  • Frequency

Table DescriptorTreeNodeRecModifier

Selection of recommended modifier values for descriptor tree parts or single descriptors

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
node_id int Reference to the descriptor tree node (foreign key) NO Refers to table DescriptorTreeNode
modifier_id int Reference to the recommended modifier (foreign key) NO Refers to table Modifier
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • DescriptorTreeNode
  • Modifier

Table DescriptorTreeNodeRecStatMeasure

Selection of recommended statistical measures for descriptor tree parts or single descriptors

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
node_id int Reference to the descriptor tree node (foreign key) NO Refers to table DescriptorTreeNode
measure_id int Reference to the recommended measure (foreign key) NO Refers to table StatisticalMeasure_Enum
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • DescriptorTreeNode
  • StatisticalMeasure_Enum

Table Frequency

Definition of frequency modifier values

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
label nvarchar (255) Short label (or name) of frequency modifier (e.g. “very rare”, “rare”, “usually” etc.) NO -
lower_estimate float Each frequency modifier defines a frequency range, this is the estimated lowest frequencyDefault value: ‘0’ NO -
upper_estimate float As above, estimate of upper range for the border; note: ranges may overlap!Default value: ‘1’ NO -
display_order int A positive number defining the sequence in which frequency modifiers are to be displayedDefault value: ‘0’ NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity

afterDeleteFrequency

afterInsertFrequency


Table Identifier

Objects may have multiple external identifiers

Column Data type Description Nullable Relation
object_id int Reference to object that is identified by the uri, references BaseEntity (foreign key) NO Refers to table BaseEntity
uri nvarchar (255) URI (globally unique identifier, including IRIs) for the object (descriptor/character, taxon, etc.). Local IDs should be entered using a consistent method (e.g. if organisation x uses local id “char 123” create “x.org:EXTERNAL_LINK:char:123”) NO -
match nvarchar (255) Match of URI to linked object, see definitions according to skos:exactMatch etc.Default value: ’exact' NO -

Depending on:

  • BaseEntity

Table ImportMapping

The import mappings to support mapping of external file keys to database keys

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
object_id int Reference to the object to which the mapping belongs, references BaseEntity (foreign key) NO Refers to table BaseEntity
session_id int Reference to the import session to which the mapping belongs, references ImportMapping (foreign key) NO Refers to table ImportSession
table_name varchar (50) Name of the import table NO -
parent_key varchar (255) Symbolic key of the parent table NO -
external_key nvarchar (255) External key in the import file NO -

Depending on:

  • BaseEntity
  • ImportSession

afterInsertImportMapping


Table ImportSession

The import sessions to support import of data spread over several files

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
project_id int Each import session belongs to exactly one project (required, foreign key) NO Refers to table Project
detail nvarchar (MAX) Detail text explaining the import session definition YES -
create_timestamp datetime Date and time when the import session was createdDefault value: getdate() NO -
update_timestamp datetime Date and time when the import session was updatedDefault value: getdate() NO -

Depending on:

  • Project

Table Modifier

Definition of modifier values

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
class nvarchar (255) Grouping of modifiers into classes (“Certainty”, “Seasonal”, “Diurnal”, “TreatAsMisinterpretation” or “OtherModifierClass”) NO -
label nvarchar (255) Short label (or name) of modifier (e.g. “strong”, “probably” etc.) NO -
display_order int A positive number defining the sequence in which modifiers are to be displayedDefault value: ‘0’ NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity

afterDeleteModifier

afterInsertModifier


Table MolecularSequenceData

The molecular sequence data of a description

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
description_id int Reference to description to which these data belong (foreign key) NO Refers to table Description
descriptor_id int Reference to a molecular sequence descriptor to which the sequence text belongs (foreign key) NO Refers to table Descriptor
sequence nvarchar (MAX) Molecular sequence text referring to information on one descriptor NO -
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Description
  • Descriptor

trgCrMolecularSequenceData


Table MolecularSequenceSamplingData

The molecular sequence data recorded for a sampling event

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
sampling_unit_id int Reference to a sampling unit (foreign key) NO Refers to table SamplingUnit
descriptor_id int Reference to a molecular sequence descriptor to which the sequence text belongs (foreign key) NO Refers to table Descriptor
sequence nvarchar (MAX) Molecular sequence text referring to information on one descriptor NO -
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Descriptor
  • SamplingUnit

Table OtherScope

Scope values for description scope values for scope types “Other scope”, “Part”, “Stage” and “Sex”

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
label nvarchar (255) Short label (or name) of scope (e.g. “male”, “female”, “adult”, “juvenile” etc.) NO -
detail nvarchar (MAX) Additional detail text explaining or commenting on the scope and delimitation of the present description YES -
type nvarchar (255) Describes the scope type (“sex”, “stage”, “part” or “other”) NO -
sex_status_id int Reference to sex status value according SDD V5.1 (foreign key)Default value: NULL YES Refers to table SexStatus_Enum
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • SexStatus_Enum

afterDeleteOtherScope

afterInsertOtherScope


Table Project

Projects define separated workareas in a single database

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
parent_project_id int Reference to a parent project, creating a subproject; NULL for a root project (foreign key)Default value: NULL YES Refers to table Project
label nvarchar (255) Short label (or name) of project (or subproject); each project defines a separate work environment within a shared database by means of defining sets of descriptors (through DescriptorTree) NO -
rights_text nvarchar (255) The default rights and licence statement for the entire project; BaseEntity provides means to override this for individual objectsDefault value: NULL YES -
licence_uri nvarchar (255) URI of licence for the project; BaseEntity provides means to override this for individual objectsDefault value: NULL YES -
detail nvarchar (MAX) Additional detail text explaining or commenting on the project (or subproject) YES -
primary_language_code nvarchar (3) Language of primary text version (fields directly in tables, may be translated in table Translation); Examples: “de”, “en” etc. (ISO 639 language code) NO -
ProjectProxyID int Reference to a project definition of DiversityProjects that allows control of access rightsDefault value: (0) NO Refers to table ProjectProxy
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
wording nvarchar (255) Optional separate wording for natural language generation and cache database (label will be used if this is missing) YES -

Depending on:

  • BaseEntity
  • ProjectProxy

afterDeleteProject

afterInsertProject


Table Project_AvailableScope

Scope values available for a certain project

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
project_id int Reference to the project for which a shall be available (foreign key) NO Refers to table Project
scope_id int Reference to a scope definition in OtherScope (foreign key) NO Refers to table OtherScope
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • OtherScope
  • Project

Table ProjectUser

The projects that a user can access

Column Data type Description Nullable Relation
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc.. NO Refers to table UserProxy
ProjectID int ID of the project defined in DiversityProjects - negative value for local project NO Refers to table ProjectProxy
ReadOnly bit If the user has only read access to data of this projectDefault value: (0) YES -

Depending on:

  • ProjectProxy
  • UserProxy

Table QuantitativeSamplingData

The quantitative data recorded for a sampling event

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
measure_id int Optional statistical measure (minimum, mean, maximum, ranges, sample size, variance etc.) recorded in value; if NULL, value is a direct measurement (foreign key)Default value: NULL YES Refers to table StatisticalMeasure_Enum
sampling_unit_id int Reference to a sampling unit (foreign key) NO Refers to table SamplingUnit
descriptor_id int Reference to descriptor which the values record (foreign key) NO Refers to table Descriptor
value float The value for the statistical measure or single measurement/recording NO -
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
modifier_id int Optional reference to a modifier definition (e.g. “strongly”, “at the base”, “in autumn”) (foreign key)Default value: NULL YES Refers to table Modifier
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Descriptor
  • Modifier
  • SamplingUnit
  • StatisticalMeasure_Enum

Table QuantitativeSummaryData

The quantitative data of a description

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
measure_id int Reference to the statistical measure (minimum, mean, maximum, ranges, sample size, variance etc.) recorded in value (foreign key) NO Refers to table StatisticalMeasure_Enum
description_id int Reference to the description to which these data belong (foreign key) NO Refers to table Description
descriptor_id int Reference to the descriptor which the values record (foreign key) NO Refers to table Descriptor
value float The value of the statistical measure NO -
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
modifier_id int Optional reference to a modifier definition (e.g. “strongly”, “at the base”, “in autumn”) (foreign key)Default value: NULL YES Refers to table Modifier
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Description
  • Descriptor
  • Modifier
  • StatisticalMeasure_Enum

trgCrQuantitativeSummaryData


Table Resource

Hyperlinks to separate rich text/media objects

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO Refers to table BaseEntity
terminology_role nvarchar (255) Role in relation to descriptors or states (“unknown”=role not known or not specified; “diagnostic”=optimized for identification; “iconic”=icon/thumbnail, needs text; “normative”=defines a resource object; “primary”=display always, informative without text; “secondary”=display only on request)Default value: ‘unknown’ NO -
ranking_for_terminology tinyint Ranking of the resource with respect to terminology; range: 0 to 10Default value: NULL YES -
descriptor_id int Optional reference to a descriptor (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)Default value: NULL YES Refers to table Descriptor
state_id int Optional reference to a categorical state (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)Default value: NULL YES Refers to table CategoricalState
taxon_role nvarchar (255) Role in relation to taxa or descriptions (“unknown”=role not known or not specified; “diagnostic”=optimized for identification; “iconic”=icon/thumbnail, needs text; “normative”=defines a resource object; “primary”=display always, informative without text; “secondary”=display only on request)Default value: ‘unknown’ NO -
ranking_for_taxon_use tinyint Ranking of the resource with respect to taxa or descriptions; range: 0 to 10Default value: NULL YES -
taxon_id int Optional reference to a taxon (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)Default value: NULL YES -
description_id int Optional reference to a description (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)Default value: NULL YES Refers to table Description
scope_id int Reference to the scope of the resource (e.g. “sex”, “stage”, “season” etc.)Default value: NULL YES -
display_embedded tinyint false/0: display as link, true/1: display as embedded media objectDefault value: ‘0’ NO -
label nvarchar (255) Short label of (or caption for) the resource, e.g. a text displayed below an image or instead of the link NO -
detail nvarchar (MAX) Additional detail text explaining or commenting on the resource definition YES -
language_code nvarchar (3) Language of the resource itself, use zxx for language neutral/no linguistic content (ISO 639-1)Default value: NULL YES -
rights_text nvarchar (255) The rights and licence statement for the resourceDefault value: NULL YES -
licence_uri nvarchar (255) URI of licence for the resourceDefault value: NULL YES -
display_order int A positive number defining the sequence in which multiple resources are displayedDefault value: ‘0’ NO -
node_id int Optional reference to a descriptor tree node (at least 1 of description_id, node_id, descriptor_id, state_id or taxon_id must be present) (foreign key)Default value: NULL YES Refers to table DescriptorTreeNode
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • CategoricalState
  • Description
  • Descriptor
  • DescriptorTreeNode

afterDeleteResource

afterInsertResource


Table ResourceVariant

Different resource variants/instances/service access points

Column Data type Description Nullable Relation
id int Database-internal ID of this record, references BaseEntity (primary key) NO -
resource_id int Reference to the resource to which these variants provide access points (foreign key) NO Refers to table Resource
variant_id int Reference to the definition of a variant class e.g. “tiny sample”, “small sample”, “lower quality”, “medium quality”, “good quality” or “best quality” (foreign key) NO Refers to table ResourceVariant_Enum
url nvarchar (255) URL of the resource variant NO -
pixel_width int Where applicable (still- or moving image): the width in pixelDefault value: NULL YES -
pixel_height int Where applicable (still- or moving image): the height in pixelDefault value: NULL YES -
duration int Where applicable (sound or moving image): the duration in secondsDefault value: NULL YES -
size int The size of the resource in bytesDefault value: NULL YES -
mime_type nvarchar (255) Type of the resource as MIME type like image/jpeg; color as color/hexrgbDefault value: NULL YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Resource
  • ResourceVariant_Enum

Table SamplingEvent

A sampling event may contain many sampling units

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO Refers to table BaseEntity
description_id int Reference to the description to which these sampling data belong (foreign key) NO Refers to table Description
label nvarchar (255) Free-form text identifying a sampling event to humans. Sampling events have time, location, perhaps purpose and act as a container for multiple sampling units.Default value: NULL YES -
detail nvarchar (MAX) Free-form text giving detail or description of sampling event YES -
date_time datetime Date and time when the event occurred; single point or start of durationDefault value: NULL YES -
datetimespan_end datetime Optional end of a time span or duration within which or during which the event occurredDefault value: NULL YES -
geographic_area nvarchar (255) A geographic area at which the event occurredDefault value: NULL YES -
geographic_area_uri nvarchar (255) Reference to a geographic area in DiversityGazetteersDefault value: NULL YES -
coord_dec_latitude float Latitude of geographical coordinates in signed decimal degreesDefault value: NULL YES -
coord_dec_longitude float Longitude of geographical coordinates in decimal degreesDefault value: NULL YES -
coord_literal nvarchar (255) Free-form string, either in addition to or instead of code (a mapping to the controlled vocabulary may be unavailable or considered ambiguous)Default value: NULL YES -
coord_geodeticdatum nvarchar (50) Optional, only where knowledge of the geodetic datum is readily available; defaults to WGS84 used in GPSDefault value: NULL YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • Description

afterDeleteSamplingEvent

afterInsertSamplingEvent


Table SamplingUnit

Sampling unit data

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
sampling_event_id int Reference to a sampling event; keeps paired measurements together (several categorical or quantitative observations at the same time on the same object or object part) (foreign key) NO Refers to table SamplingEvent
collection_specimen nvarchar (255) A collection specimen that is represented by the sampling unitDefault value: NULL YES -
collection_specimen_uri nvarchar (500) Reference to a collection specimen in DiversityCollectionDefault value: NULL YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • SamplingEvent

Table Tag

Objects may have multiple tags (= keywords)

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
tag nvarchar (255) Tag (= keyword) to categorize objects like descriptors, states, descriptions NO -
object_id int Reference to object to which the tag belongs, references BaseEntity (foreign key) NO Refers to table BaseEntity

Depending on:

  • BaseEntity

Table TextDescriptorData

The text data of a description

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
description_id int Reference to description to which these data belong (foreign key) NO Refers to table Description
descriptor_id int Reference to a text descriptor to which the free-form text belongs (foreign key) NO Refers to table Descriptor
content nvarchar (MAX) Free-form text referring to information on one descriptor NO -
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the values YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Description
  • Descriptor

trgCrTextDescriptorData


Table TextSamplingData

Free-form text data recorded for a sampling event

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
sampling_unit_id int Reference to a sampling unit (foreign key) NO Refers to table SamplingUnit
descriptor_id int Reference to descriptor to which the free-form text belongs (foreign key) NO Refers to table Descriptor
content nvarchar (MAX) Free-form text referring to information on one descriptor NO -
notes nvarchar (MAX) Free-form text detailing special cases or additional data beyond the data YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Descriptor
  • SamplingUnit

Table TODO_MultilingualCharDataNotes

Column Data type Description Nullable Relation
table_is_just_a_note-Work_needs_to_be_done int - NO -
memo_char_and_taxon_notes_is_already_redundant_due_to_annotation int - NO -
memo_char_data_are_not_an_object_thus_not_annotated int - NO -

Table Translation

The translations of entries related to BaseEntity

Column Data type Description Nullable Relation
id int Database-internal ID of this record (primary key) NO -
object_id int Reference to the object to which the translation belongs, references BaseEntity (foreign key) NO Refers to table BaseEntity
language_code nvarchar (3) Language of representation translation (ISO 639 language code) NO -
column_id int References the translated column name NO Refers to table TranslationColumn_Enum
contents nvarchar (MAX) Translated contents YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • BaseEntity
  • TranslationColumn_Enum
May 3, 2024

Diversity Descriptions enumeration tables

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table


Table BaseEntityTable_Enum

The BaseEntityTable_Enum contains the names of tables that reference the BaseEntity table

Dependent tables:

  • BaseEntity

Table DataStatus_Enum

Values of data status used for descriptions according to SDD 1.1 rev 5

Depending on:

  • BaseEntity

Dependent tables:

  • DescriptorStatusData

afterDeleteDataStatus_Enum

afterInsertDataStatus_Enum


Table ResourceVariant_Enum

Classes for resource variants, values are predefined in the database

Depending on:

  • BaseEntity

Dependent tables:

  • ResourceVariant

afterDeleteResourceVariant_Enum

afterInsertResourceVariant_Enum


Table SexStatus_Enum

Values of sex status predefined according to SDD 1.1 rev 5

Depending on:

  • BaseEntity

Dependent tables:

  • OtherScope

afterDeleteSexStatus_Enum

afterInsertSexStatus_Enum


Table StatisticalMeasure_Enum

The statistical measures predefined according SDD 1.1 rev 5

Depending on:

  • BaseEntity

Dependent tables:

  • DescriptorMapping_Q2C
  • DescriptorTreeNodeRecStatMeasure
  • QuantitativeSamplingData
  • QuantitativeSummaryData

afterDeleteStatisticalMeasure_Enum

afterInsertStatisticalMeasure_Enum


Table TranslationColumn_Enum

The TranslationColumn_Enum contains the column names that are translated in the Translation table

Dependent tables:

  • Translation
May 3, 2024

License

License

This manual is copyrighted work licensed under a Creative CommonsLicense.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

 For information about the license of the client software choose Help -> Info …

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNUGeneral Public License (GPL) for more details.

May 3, 2024

Resources directory

Resources directory

In the resources directory all files are stored that have been generated by Diversity Descriptions, e.g. due to export. Furthermore you may store files here that shall be used for data import into the Diversity Descriptions database and the error log file. The resources directory may be set via the menu Administration-> Resources directory … (see image below).

There are 3 possibilities for the resources directory:

  • Select the “Home directory” of the user (may  be definded via %HOMEDRIVE%%HOMEPATH%)
  •   Select the “My Documents” directory of the user
  • Select any directory you have read/write access (User defined)

The default is set to Home. Below this node the directories “DiversityWorkbench” will be created and below that “DiversityDescriptions”, which will contain all files that a Diversity Descripiton user needs user need access to. If you install additional Diversity Workbench applikations and use resources directory option “Home directory”, they will all get dedicated directories under “..<user>\DiversityWorkbench\”.

Certain directories are hidden (Query, Settings, Spreadsheet) and are handled by the software i.e. the content should not be changed by the user. The other folders (Export, Import and so on) are a copy of folders placed in the program directory (see below).

 

Tutorial files  

For DiversityDescriptions a number of tutorial files are available that provide examples, e.g. for using the matrix import wizard. To copy the tutorial files into your resources directory select Administration->  Tutorial files … from the menu. 

Jan 14, 2025

Version

Version

For information about the version of the client application and the database choose Help-> Info …

The current version in the example above is 4.6.0. The required database version is 3.3.7.

 

May 3, 2024

Update

Update of database and client

If either the database or the client needs to be updated, the menu will show an additional entry: Update.

Database update

To update the database, choose Update Update database … from the menu. See chapter Database update for details.

Client update

To update the client, choose Update Update client … and download the lastest version of the client. ee chapter Update client for details.

Mar 26, 2024

Subsections of Update

Update Client

Replace the files and folders of your installation of DiversityCollection with the files you received by e-mail or downloaded from the DiversityWorkbench portal. The database will not be influenced by this replacement. After starting the new software you need to transfer the settings of the previous version. When you start the program and connect to a database, the program will check if it is compatible with the database or if the database needs an update. In any of these cases an update entry in the menu will appear. If a new version of the client is available, this menu will contain an update client … entry. Click on it to open the webpage where you may download the client as shown below.

 

Mar 26, 2024

Update Database

Update database to current version

If you are the owner of the database (Database role = dbo) and the database needs to be updated, the menu will contain an update database … entry. Select this entry to open a window as shown below to run the provided update scripts, delivered with the client software. These scripts need to run consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either have to run the script DiversityCollectionUpdate_020501_To_020504 or the scripts DiversityCollectionUpdate_020501_To_020502, DiversityCollectionUpdate_020502_To_020503 and DiversityCollectionUpdate_020503_To_020504. The program will guide you through these steps and check for the scripts. All you need to do is click the Start update button. 

Update of all databases on a server

If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:

DiversityCollection.exe UpdateDatabase 127.0.0.1 5432

The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.

Mar 26, 2024

Errorlog

If any error messages show up while working with the application, you can find further details concerning the part of the application where the error occurred and the parameters involved in the file e.g. DiversityCollectionError.log in the Module DiversityCollection located in your resources directory.

To open the errorlog, choose Help - ErrorLog from the menu. A window will open showing the content of the errolog. By default the errorlog will be reset at program start. You can keep the errorlog if needed by chossing Help - Errorlog - Keep error log from the menu. A button will appear that allows you to clear the error log manually: Help - Clear ErrorLog.

Mar 26, 2024

Workbench

Diversity Workbench

The Diversity Workbench is composed of components for building and managing biodiversity information, each of which focuses on a particular domain. Each component can provide services to the other components. DiversityDescriptions can link data to the modules DiversityCollection, DiversityTaxonNames, DiversityGazetteers and DiversityReferences as illustrated in the image below. DiversityProjects together with DiversityAgents provide support for administration of data access rights.

 

The modules communicate with each other to provide their services for the other modules.

May 3, 2024

Subsections of Workbench

Module Related Entry

Module related entry

The Diversity Workbench  is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. Each module provides services for the other modules. To use the service of a module, you need access to the database of the module and optionally the module application placed in your application directory. Entries related to an external module have a standard interface in the main form. There are 2 states of this interface:

1 - the value is only set in the local database with no connection to the remote module

In this state, you can either type the value or select it from the values that are already available in the database. To get a list of the available values type the beginning of the value (you may use wildcards) and click on the  button. If you want to set a relation to the remote module, click on the  button. A window will open where you may select an entry from the foreign database.

 

2 - the value is related to the remote module

If the value has a relation to the remote module, the interface will appear as shown above. To release the connection to the remote module click on the button. If you need further information about the value, click on the  button. This will open a form, showing an overview of the related value.

If the client application of the module is available you can inspect the details of the entry.  

 

3 - relation to a webservice

Some modules provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of IndexFungorum. To establish a connection to an external webservice, click on the  button. As with the link to modules within the Diversity Workbench a window will open where you can choose from either Diversity Workbench modules or external Webservices. See Webservice for further details.

Jan 14, 2025

Modules

Modules

The Diversity Workbench  is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. 

DiversityAgents Administration of the agents, i.e. people and institutions which should be documented with e.g. their addresses
<img src=“img/IcoDiversityCollection.gif” data-align=“left”
height=“16” /> DiversityCollection Administration of the scientific collections, specimens within these collections and observations
<img src=“img/IcoDiversityDescriptions.gif” data-align=“left”
height=“16” /> DiversityDescriptions Administration of the descriptive data
<img src=“img/IcoDiversityGazetteer.gif” data-align=“left”
height=“16” /> DiversityGazetteers A data collection to enable the linking of geographical records with the Getty Thesaurus of Geographical Names (TGN), the German GN250 database and other sources of geographical names
DiversityProjects Administration of projects
<img src=“img/IcoDiversityReferences.gif” data-align=“left”
height=“16” /> DiversityReferences Administration of litarature references
<img src=“img/IcoDiversityTaxonNames.gif” data-align=“left”
height=“16” /> DiversityTaxonNames   Administration of taxonomic names, their synonyms and hierarchical position

Each module provides services for the other modules. To use the service of a module, you need access to the database of the module and optionally the module application placed in your application directory. 

May 3, 2024

Webservice

Webservice - foreign sources

Some modules within the Diversity Workbench provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of IndexFungorum. To establish a connection to an external webservice, click on the  button. A window will open where you can choose from either Diversity Workbench modules or external Webservices. Some currently provided webservices are:

The Catalogue of Life

Index Fungorum

Pan-European Species directories Infrastructure

Recent Literature on Lichens

 

Jan 14, 2025

Subsections of Webservice

Webservice Catalogue Of Life

Catalogue of Life - webservice

Diversity Workbench provides the possibility to link your data to an external webservice. The webservice provided by the Catalogue ofLife allows linkage of taxon names. To establish a connection to this external webservice, click on the  button. A window will open where you can choose this webservice (see below). Remark: By selecting “CatalogueOfLife” you can search in the 2014 annual check list, by selecting “CatalogueOfLife_2” you can search in a newed, updated edition, which includes higher taxa.

In the field Name in Query conditions enter you search string and click on the button to start the query. In the list of the left upper part the results of the query will be listed. In the right part of the window additional information is shown as provided by the webservice. If available, the lower part of the window will show the webpage of the related information.

Higher taxa and for synonyms the accepted name will be shown as e.g. shown above. To inspect one of these entries, click on the linked entry of the ID. To take the link from the webservice into your database choose one of the entries in the list and click OK. The entry will change as shown below.

If you double-click on the link area a window will open, providing you with the retrieval information of the webservice. 

To get the information related to an entry as provided by the webservice, click on the  button. A window will open as shown below where the informations of the webservice are listed in the upper part. If available, additional informations provided on a corresponding website will be shown in the lower part.

If you want to remove the link to the webservice, click on the  button. This will only remove the relation to the webservice, not the cached name.

 

 

 

 

 

May 3, 2024

Webservice Index Fungorum

Index Fungorum - webservice

Diversity Workbench provides the possibility to link your data to an external webservice. The webservice provided by the IndexFungorum allows linkage of taxon names. To establish a connection to this external webservice, click on the  button. A window will open where you can choose this webservice (see below). 

Enter the query restriction for the name in the Name field in Query conditions. The maximal number of records you get can be set in the max. results field (choose a low number if you have a slow connection to the internet). Then click on the search button to start the query. In the list of the left upper part the results of the query will be listed. In the right part of the window additional information is shown as provided by the webservice. For certain entries buttons will appear, as e.g. shown above for the basionym and the current name of a scientific name. Click on these buttons if you want to change to one of these related datasets from the webservice. If available, the informations provided on the corresponding website is shown in the lower part. To take the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area a window will open, providing you with the retrieval information of the webservice. 

To get the whole information related to this entry as provided by the webservice, click on the  button. A window will open as shown below where the informations of the webservice are listed, If available, the lower part will show the corresponding informations of a website.

If you want to remove the link to the webservice, click on the the  button. This will only remove the relation to the webservice, not the cached name.

May 3, 2024

Webservice Myco Bank

MycoBank Database - webservice

Some modules within the DiversityWorkbench provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of the MycoBank database. To establish a connection to this webservice, click on the button. A window will open where you can choose MycoBank from the database list (see below). 

Enter the query restriction for the name in the Name field in Query conditions. Click on the search button to start the query. In the list in the left upper part the results of the query will be listed. On the right part of the window additional information is shown as provided by the webservice. If available, the information provided on the corresponding website is shown in the lower part. To include the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the entire information related to this entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed. If available, the lower part will show the corresponding information of a website.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

May 3, 2024

Webservice Palaeo DB

The Palaeontolgy Database - webservice

Diversity Workbench provides the possibility to link your data to an external webservice. The webservice provided by the PalaeontologyDatabase allows linkage of taxon names. To establish a connection to this external webservice, click on the  button. A window will open where you can choose this webservice (see below).

In the field Name in Query conditions enter you search string and click on the button to start the query. In the list of the left upper part the results of the query will be listed. In the right part of the window additional information is shown as provided by the webservice. The lower part of the window will show the webpage of the related information.

For synonyms, the accepted name will be shown as well as e.g. shown above. To change to the accepted name, click on the linked entry of the ID - in the example above id: 57254. To take the link from the webservice into your database choose one of the entries in the list and click OK. The entry will change as shown below.

If you double-click on the link area a window will open, providing you with the retrieval information of the webservice. 

To get the information related to an entry as provided by the webservice, click on the  button. A window will open as shown below where the informations of the webservice are listed in the upper part. If available, additional informations provided on a corresponding website will be shown in the lower part.

If you want to remove the link to the webservice, click on the  button. This will only remove the relation to the webservice, not the cached name.

 

 

 

 

 

May 3, 2024

Webservice PESI

Pan-European Species directories Infrastructure - webservice

Some modules within the DiversityWorkbench provide the possibility to link your data to an external webservice. For example DiversityTaxonNames gives you access to the taxonomic names of the Pan-European Species directories Infrastructure (PESI). To establish a connection to this webservice, click on the button. A window will open where you can choose PESI from the database list (see below). 

Enter the query restriction for the name in the Name field in Query conditions. Click on the search button to start the query. In the list in the left upper part the results of the query will be listed. On the right part of the window additional information is shown as provided by the webservice. If available, the information provided on the corresponding website is shown in the lower part. To include the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the entire information related to this entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed. If available, the lower part will show the corresponding information of a website.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

May 3, 2024

Webservice RLL

Recent Literature on Lichens - webservice

Some modules within the DiversityWorkbench provide the possibility to link your data to an external webservice. For example DiversityReferences gives you access to the webservice RecentLiterature on Lichens. To establish a connection to this webservice, click on the button. A window will open where you can choose RLL from the database list (see below). 

Enter the query restriction for the name in the Name field in Query conditions. Click on the search button to start the query. In the list in the left upper part the results of the query will be listed. On the right part of the window additional information is shown as provided by the webservice. If available, the information provided on the corresponding website is shown in the lower part. To include the link from the webservice into your database choose one of the entries and click OK. The entry will change as shown below.

If you double-click on the link area , a window will open providing you with the retrieval information of the webservice. 

To receive the entire information related to this entry as provided by the webservice click on the button. A window will open as shown below where information on the webservice is listed. If available, the lower part will show the corresponding information of a website.

If you wish to remove the link to the webservice, click on the button. This will only remove the relation to the webservice, not the cached name.

May 3, 2024

Diversity Exsiccatae

Clients for DiversityExsiccatae

There is 1 Client and 1 website available for editing resp. searching data in DiversityExsiccatae:

Scope of DiversityExsiccatae within the Diversity Workbench

DiversityExsiccatae is the module for administration of exsiccatal series within the Diversity Workbench. The DiversityExsiccatae is requiered by the module DiversityCollection and on the other hand uses services provided by the modules like DiversityReferences and DiversityAgents.

The modules communicate with each other to provide their services for the other modules.

Data managment sectors of the application

Sector Description
Evaluation The evaluation of an exsiccatal series
Editors The editors of an exsiccatal series
Publication span The publication span of an exsiccatal series
References The references related to an exsiccatal series
Examples The examples for an exsiccatal series

Usage example

An exsiccatal series is administrated or published by several agents using a list of references and examples.

Main form of DiversityExsiccatae

To start the application double click on DiversityExsiccatae.exe.

The first time you start the application you have to configure the connection to the database (Connection, Server … ) you want to work with. The header of your form allways shows you, with which database you are working, the version of the client, the database server and your login.

To see the descriptions for the fields of the database, simply move your mouse over it. A tooltip will appear with an explanation of the field.

Where you have to choose items from lists, type the beginning of the item name in the field and then click on the drop down button . This will start a query in the database and list the result in the combobox. If contents can be linked to an other module, click on the  button to start a query in this module.

Jan 14, 2025

Subsections of Exsiccatae

Diversity exsiccatae

Download

Upcoming version

4.0.5 (2024-??-??)

  • Bugfix - Using new verion for database update

Current version

4.0.4 (2023-03-02)

Download

  • Several bugfixes
  • Several new order columns
  • Multicolumn resultlist enabled

Previous versions

4.0.3

  • Bugfix removing images of examples
  • Update for current Workbench
  • Optimized query enabled
  • Rember of Query enabled

 

Datebase updates

  • 02.00.07: Adding PrivacyConsent columns in UserProxy;
  • 02.00.08: Missing decriptions; Adding View_Coverage;

 

Diversity exsiccatae

Menu

Overview of the menu in DiversityExsiccatae

  • Connection
    • Database: Choose one of the databases available on the server. Only databases to which the user has access permission will be listed.
    • Module connections: Edit the connections to the other modules within the DiversityWorkbench.
    •  Transfer previous settings: Transfer the settings for IP-Address and port of the server, name of the database, login etc. of a previous version of the client to the current version.
    •  Current acivity on server …: List the processes on the database server.
    •  Quit: Quit the application and stop all processes started by the application.
  • Query
    • Show query: Show or hide the query list.
    • Predefined queries: All predefined queries will be listed.
  • Data
  • Administration
    •   Database: Administration of the database.
      •  Descritption: Administration of the descriptions and messages within the application.
      • Database tools: Tools for the administration of the objects in the database - for experts only!.
      •  Documentation …: Documentation of the structure of the database.
      •   Logins: Administration of the logins of the server and their permissions in the databases.
      •   Queries: Creating and editing predefined queries.
      •   Rename database: Rename the current database.
      •   Set published address: Setting the address published for links by other modules.
  • Help
    •   Manual: Opens the online manual.
    •   Feedback: Opens a window for sending feedback.
    •   Feedback history …: Opens a window for browsing former feedback.
    •   Edit feedback …: Opens a window for editing the feedbacks sent to the administrator (for admins only).
    • Info: Show the version of the program and corresponding information.
    •   Websites: Websites related to DiversityCollection.
  •   ErrorLog: Open the errorlog of the appliaction.
  • Update
    •   Update database …: Update the database to the current version.
    •   Update client: Download the current version of the client.
Jan 14, 2025

Diversity exsiccatae

Editing the data

The main forms of all modules have a design as shown below

Main form

Status

In the status area you find

  • The name of the module,
  • The name of the database if different fron the module
  • The version of the software

The menu contains the options provided by the module

Commands

The commands area contains buttons for e.g. handling the data:

  • - To connect to a database click on the button.
  • - To save the changes in a dataset click on the button.
  • - To propagate the changes in a dataset to linked modules click on the button.
  • - To undo the changes a dataset click the button. This will recover the original data unless the changes had been saved or changes were done in certain tables or hierarchies were the data must be stored to display the hierarchy.
  • - To create a new entry in the database, click on the  button below the search result listbox. This will create a entry with the specimen and show it in the list.
  • - To copy a specimen, choose it from the list and click on the button .
  • - To options a dataset click on the button .
  • - To change the arrangement of the query click on the button.

Create new exssicate

To create a new exssicate, click on the  button above the search result listbox. You will be asked, if you are sure

Jul 22, 2024

Subsections of Editing

Diversity exsiccatae

Editors

To add a new editor to the list click on the  Button. To delete an selected editor from the list click on the  Button.

To open the module DiversityAgents to get more infomation about an editor, click on the  Button.

Jul 22, 2024

Diversity exsiccatae

Evaluation

In the evaluation part, further informations on the exsiccatal series are entered like the taxonomic coverage or the purpose of the exsiccatal series.

    

The geographcal regions covered in the exsiccatal series are in the corresponding area. To insert a new region, click on the  Button and select a region offered by the module DiversityGazetteer. To delete a region, select it in the list and click on the  button.

Jul 22, 2024

Diversity exsiccatae

Examples

The list of the examples is shown with their images in the list. If an example misses an image, this will be indicated with an  entry in the list.

To add a new example to the list click on the  Button. An window will open, where you can search for an image file. If you want to create an example without an image, just click OK without selecting any image. If you later want to add an image to you example click on the   button and select an image file. A form will open, where you can search for an image.

Click OK to take the image in your example.

To delete an selected example from the list click on the  Button. If you want to link to a collection specimen from the module DiversityCollection , click on the  Button.To zoom a sector of the image, just drag the mouse over the image. A red square will indicate the zoomed area. To adapt the size of the image to the available space in the form click on the  button. To change the orientation of the image use the appropriate buttons (  flip horizontal,  flip vertical,  rotate right,  rotate left).

Only the file names are stored in the database. The directory for the file must be set in the menu under Adminstraton - Image folder … .

Jul 22, 2024

Diversity exsiccatae

Publication span

Details about the Publication span are entered in the area Publication span. The span of the numbers will be shown in the sequence overview.

 

Jul 22, 2024

Diversity exsiccatae

References

To add a new reference to the list click on the  Button. To delete an selected reference from the list click on the  Button.

To open the module DiversityReferences to get more infomation about an reference, click on the  Button.

Jul 22, 2024

Diversity exsiccatae

Sequence

Details about the sequence are entered in the area “Title or author / editor changes”.

To enter a preceding exsiccatal series, click on the  button. This will open a form where you can search for an exsiccatal series. If you want to remove the relation to a preceding exsiccatal series, click on the   button. To change to a different exsiccatal series shown in the hierarchy, select it and click on the  button.

If there happens to be a loop or a selfreference in the sequence the client will show you this by highlighting the hierarchy as shown below.

The  button will be activated. You can change to the exsiccatal series that should be to topmost one in a sequence by using the  button. Than click the   button to remove the reference to the predecessor of this series.

Jan 7, 2025

Diversity exsiccatae

Table editors

For the data selected in the main window the table editors offer a direct access to the tables of the database. The menu Data - Table editors provide an editor for Exsiccata…, Editor… and Example…

A window with the content of the table will open. Columns with a gray background can not be edited here. Columns with a light gray background are linked to the contents of lookup tables that can be changed according to the contents of these tables. Columns containing an ID related to a lookuptable show the related value from the lookup table. To see the ID behind, click on the ID button.

Select Set timeout … from the menu to increase the default timeout from 5 seconds to a higher value, e.g. for greater amounts of data.  

Editing

You can either edit the contents of the table directly or perform changes to any number of marked fields. To mark a whole column use the  button. Once you have selected the contents to change, select one of the modes of change that appear in the upper left corner. The modes of change are:

  • Insert: Insert the given value at the beginning of the content
  • Append: Append the given value at the end of the content
  • Replace: Replace a string in the content with the given value
  • Clear: Remove the content

After selecting the change mode, enter the text in the field where necessary and click on the corresponding button to perform the changes

Filtering

To filter the content of the table, click in the column that should be used for filtering. Then choose the mode of comparision:

  • = : The content must be exactly like the given value
  • ~ : The content must contain the given value
  • ≠ : The content must be different to the given value

If you want the filtering to be case sensitive, choose the a<>A option. After all parameters are set, click on the button. To undo the filtering, click on the button. This will reset the data to the last saved version. If you want your changes to be saved, click the button before you reset the filtering. If you close the window all changes so far will be saved automatically. So if you do not want to save your changes, click on the button before closing the window.

Export

To export the data as a tab separated text file, click on the button. The file will be automatically saved in the client-folder.  

Log data

To see the log data of the table, you can click on the button. The content of the log table can not be changed, but is read only.  

Jan 6, 2025

Diversity exsiccatae

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Jul 22, 2024

Diversity exsiccatae

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.
Jul 22, 2024

Diversity exsiccatae

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many colunns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Jan 4, 2025

Diversity exsiccatae

Internals

For users that need more detailed information about the software including database design etc.

Jul 22, 2024

Subsections of Internals

Diversity exsiccatae

Database

Organisation of the data

The main data are kept in the table Exsiccata. Editors are listed in the table ExsiccataEditor, examples in the table ExsiccataExample and geographicla regions in the table ExsiccataRegion.

Descriptions of tables and columns

Jul 22, 2024

Diversity Exsiccatae

TABLES, VIEWS, FUNCTIONS, PROCEDURES, ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES


Table Exsiccata

An Exsiccata is a series of specimen issued in a publication like form.

Column Data type Description Nullable Relation
ExsiccataID int ID of the exsiccata (primary key) NO -
Version int The version of the datasetDefault value: (1) YES -
ExsAbbreviation nvarchar (255) Std. abbreviation (authors/editors, std. abbrev. of title) NO -
ExsTitle nvarchar (255) Exact title (create a new entry if title spelling changed considerably, link entries using PrecededBy/SupersededBy) NO -
EditingInstitution nvarchar (255) Issuing/Editing institution (If no editors are known, at least this must be entered) YES -
EditingLocationOri nvarchar (255) Original spelling of city/country where the exsiccata has been issued YES -
EditingLocationCurrent nvarchar (255) Current spelling of city/country where the exsiccata has been issued YES -
EditingLocationEnglish nvarchar (255) Current English spelling of city/country where the exsiccata has been issued YES -
PrecededBy int An earlier exsiccata publication appeared under different title or editors (Reference to entry in this database) YES Refers to table Exsiccata
ExsNumberFirst nvarchar (20) If known: number of the first exsiccata that was issued by the current editors under the current title YES -
ExsNumberLast nvarchar (20) If known: number of the last exssiccata that was issued by the current editors under the current title YES -
ExsPublYearFirst nvarchar (20) If known: publication year of the first exsiccata that was issued by the current editors under the current title YES -
ExsPublYearLast nvarchar (80) If known: publication year of the last exsiccata that was issued by the current editors under the current title YES -
Notes nvarchar (2000) Annotation, please add your name and a date for each annotation YES -
Problems nvarchar (MAX) Please explain here if you have a problem, this field will later be checked YES -
Fungi smallint check if exsiccata covers fungal species (default) 1 or -1= Yes it does, 0=No it does not, Null/empty = don’t know YES -
Algae smallint check if exsiccata covers Algae/Cyanophyta YES -
Bryophytes smallint check if exsiccata covers mosses/bryophytes YES -
Pteridophytes smallint check if exsiccata covers pteridophytes YES -
HigherPlants smallint check if exsiccata covers higher plants YES -
Zoocecidia smallint check if exsiccata covers galls on plants caused by animals YES -
Educational smallint Educational purpose of the exsiccata, 1 or -1= Yes, 0=No, Null/empty = don’t know YES -
Scientific smallint Scientific purpose of the exsiccata, 1 or -1= Yes, 0=No, Null/empty = don’t know YES -
GroupSpecific smallint Exsiccata is restricted to a taxonomic entity or ecologically delimited group, e.g. family or lichens on leaves, 1 or -1= Yes, 0=No, Null/empty = don’t know YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
Bacteria smallint check if exsiccata covers pteridophytes YES -

trgInsExsiccata

set last changes in ProjectProxy


Table ExsiccataEditor

The editors that published an exsiccatal series.

Column Data type Description Nullable Relation
ExsiccataID int Reference to ExsiccataID in Exsiccata (foreign Key) NO Refers to table Exsiccata
Name nvarchar (255) Enter as last name, comma, first names, use blanks after comma and period NO -
EditorAgentURI varchar (255) The URI of the Agent, e.g. as stored within the module DiversityAgents YES -
Sequence datetime (automatically set during entry, to maintain the sequence of editors)Default value: getdate() NO -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -

Depending on:

  • Exsiccata

trgInsExsiccataEditor

setting the version in the main table


Table ExsiccataExamples

Examples for an exsiccatal series.

Column Data type Description Nullable Relation
ExsiccataID int Reference to ExsiccataID in Exsiccata (foreign Key) NO Refers to table Exsiccata
ExampleID int A number that defines the sequence in which the examples have been added. NO -
ImageFile nvarchar (255) Example: Path and file name for an image of the label of the exsiccata example issue YES -
ResourceURI varchar (255) Optionally: The URI under which the image is recoded in e.g. DiversityResources. YES -
PublishedName nvarchar (255) Example: Published taxon name of example issue YES -
CollectionName nvarchar (255) Example: Name or Acronym of collection where the example issue is available. Default is M for München YES -
Number nvarchar (50) Example: Number of example issue within the exsiccata series YES -
StorageLocation nvarchar (255) Example: Deposited under (scientific name indicating a storage location) YES -
CollectionSpecimen varchar (255) Optionally: The Display text of the example specimen as recorded in e.g. DiversityCollection YES -
CollectionSpecimenURI varchar (255) Optionally: The URI under which the example specimen is recorded in e.g. DiversityCollection YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -

Depending on:

  • Exsiccata

trgInsExsiccataExamples

setting the version in the main table


Table ExsiccataReference

The references where an exsiccatal series is listed.

Column Data type Description Nullable Relation
ExsiccataID int Reference to ExsiccataID in Exsiccata (foreign Key) NO Refers to table Exsiccata
ReferenceTitle nvarchar (255) The title of the publication where information on the exiccata was published. Note this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (255) URI (e.g. LSID) of reference where information on the exsiccata was published, e.g. referring to the module DiversityReferences YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -

Depending on:

  • Exsiccata

trgInsExsiccataReference

setting the version in the main table


Table ExsiccataRegion

The geographic regions that are covered by the specimen within an exsiccatal series.

Column Data type Description Nullable Relation
ExsiccataID int Reference to ExsiccataID in Exsiccata (foreign Key) NO Refers to table Exsiccata
Region nvarchar (50) A region where the specimens within the exsiccata were collected. NO -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -

Depending on:

  • Exsiccata

trgInsExsiccataRegion

setting the version in the main table


VIEWS


View View_Coverage

Coverage and purpose columns of table Exsiccata

Column Data type Description Nullable
ExsiccataID int ID of the exsiccata (primary key) NO
Coverage varchar (27) Combined coverage columns of table Exsiccata NO
Purpose varchar (11) Combined Purpose columns of table Exsiccata NO

Depending on:

  • Exsiccata

View ViewBaseURL

Content of function BaseURL() for linked server

Column Data type Description Nullable
BaseURL varchar (255) Content of function BaseURL() YES

Depending on:

  • BaseURL

View ViewDiversityWorkbenchModule

Content of function DiversityWorkbenchModule() for linked server

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) Content of function DiversityWorkbenchModule() YES

Depending on:

  • DiversityWorkbenchModule

FUNCTIONS


Function BaseURL

Returns the basic URL for the database

DataType: varchar (255)


Function DiversityWorkbenchModule

Name of the module

DataType: nvarchar (50)


Function PrivacyConsentInfo

Provides a link to common information about the DiversityWorkbench

DataType: varchar (900)


Function StableIdentifier

The stable identifier published for a exsiccata

DataType: varchar (500)

Parameter DataType Description
@ExsiccataID int ID of the exsiccata

Depending on:

  • Exsiccata
  • StableIdentifierBase

Function StableIdentifierBase

DataType: varchar (255)


Function UserID

ID of the User as stored in table UserProxy

DataType: int

Depending on:

  • UserProxy

Function UserName

Name of the User as stored in table UserProxy

DataType: nvarchar (50)

Parameter DataType Description
@ID varchar (10) The ID of the user, Primary key

Depending on:

  • UserProxy

Function Version

Version of the database

DataType: nvarchar (8)


Function VersionClient

Minimal version of the client compatible with the database

DataType: nvarchar (11)


PROCEDURES


Procedure procCopyExsiccata

Copy a exsiccata

Parameter DataType Description
@ExsiccataID int ID of the new exsiccata
@OriginalExsiccataID int ID of the original exsiccata
@ExsTitle nvarchar (255) Title of the new exsiccata
@ExsAbbreviation nvarchar (255) Abbreviation of the new exsiccata

Depending on:

  • Exsiccata
  • ExsiccataEditor
  • ExsiccataExamples
  • ExsiccataReference
  • ExsiccataRegion

Procedure procSetVersionExsiccata

Setting the version of a dataset

Parameter DataType Description
@ID int ID of the exsiccata

Depending on:

  • Exsiccata
  • ProjectProxy
  • UserProxy

ROLES


Role DiversityWorkbenchEditor

Role with permission to edit the data

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Exsiccata TABLE
Exsiccata_log TABLE
ExsiccataEditor TABLE
ExsiccataEditor_log TABLE
ExsiccataExamples TABLE
ExsiccataExamples_log TABLE
ExsiccataReference TABLE
ExsiccataReference_log TABLE
ExsiccataRegion TABLE
ExsiccataRegion_log TABLE
View_Coverage VIEW
ViewBaseURL VIEW
ViewDiversityWorkbenchModule VIEW
BaseURL FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo FUNCTION
StableIdentifier FUNCTION
StableIdentifierBase FUNCTION
UserID FUNCTION
UserName FUNCTION
Version FUNCTION
VersionClient FUNCTION
procCopyExsiccata PROCEDURE
procSetVersionExsiccata PROCEDURE

Role DiversityWorkbenchUser

Role restricted to ReadOnly

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Exsiccata TABLE
Exsiccata_log TABLE
ExsiccataEditor TABLE
ExsiccataEditor_log TABLE
ExsiccataExamples TABLE
ExsiccataExamples_log TABLE
ExsiccataReference TABLE
ExsiccataReference_log TABLE
ExsiccataRegion TABLE
ExsiccataRegion_log TABLE
View_Coverage VIEW
ViewBaseURL VIEW
ViewDiversityWorkbenchModule VIEW
BaseURL FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo FUNCTION
StableIdentifier FUNCTION
StableIdentifierBase FUNCTION
UserID FUNCTION
UserName FUNCTION
Version FUNCTION
VersionClient FUNCTION
procCopyExsiccata PROCEDURE
procSetVersionExsiccata PROCEDURE
Jun 20, 2024

Diversity exsiccatae

Version

For information about the version of the client application choose Help, Info…

The current version in the example above is 4.0.0 for the client and 2.1.13 for the database

 

 

Jul 22, 2024

Diversity exsiccatae

License

This manual is copyrighted work licensed under a Creative Commons License.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

 

For information about the license of the client software choose Help, Info…

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License (GPL) for more details.

Jul 22, 2024

Diversity exsiccatae

Data Access

Access to the data

To get access to the data, you have to fulfill several requirements. In DiversityCollection, you must be a member of one of the user groups. You can only access data, which is listed in the projects you have access to. For external users data may be blocked by entries in the data withholding reasons or due to a data embargo.

   

Jul 22, 2024

Subsections of Access

Diversity exsiccatae

Login Administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

To set the website where information about details concerning the General Data Protection Regulation are shown, click on the button.   

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

To administrate the  linked servers, click on the button.   

To send a feedback click on the button.   

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the time span (From - To) and the number of data sets where any activity of the current login has been found.

 

Creation of login

To create a new login click on the button. A window will open as shown below. A login that should be able to create new logins must to be a System administrator.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has [no access] will be listed in [gray] while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

The state and date of the privacy consent according to the General Data Protection Regulation is shown in dependence of the selected database.

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

As a database owner you can edit the permissions and role memberships with the and buttons. Please keep in mind that any change of the permissions may cause serious troubles and should only be used for testing and bug fixing. The final setting of the permissions should be performed by a proper update script of the database. For every action you will get the code that is to be included in an update script (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below). Projects are related to the module DiversityProjects. To get additional information about a project select it in the list and click on the button. 

Starting with database version 02.05.35 next to the projects with full access, a second list provides projects with [Read Only] access (see image below). Use the and buttons to move projects between Accessible and Read Only. If a project is set on [Read Only] a user can still add annotations. Starting with version 4.3.219 a project as a whole can be locked with the restriction of access to read only. For more details see chapter Project administration.

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

To see an overview of the users within a project select one of the project in either list and click on the corresponding button . A window as shown below will open listing all users and their roles with access to the selected project.

To add or remove a role for a login, select the corresponding field and choose or from the context menu (see below).

 

Settings of a login in a database

Depending on the database you can edit the settings of a login as shown below.

If you wish to use settings already defined for another login, click on the Search template button. A window (see below) will open where you can choose among the settings defined for logins in the database.

 

Overview for a login

If you want to see an overview of all permissions and project for a login, click on the button. A window as shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user, roles and projects in the database. 

To remove a user, select it in the list and click on the button. 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

To find users within the database that have no valid login, click on the button. A window as shown below will open, listing the users without a login. Select those that should be removed and click OK. This will include a removal from the collection managers.

 

Jul 22, 2024

Diversity exsiccatae

History

To inspect the history of a dataset click on the button. A form will open, showing all former states of the data in the tables with the current dataset at the top. The version is shown in the header of the main.

The version will be set automatically. If a dataset is changed the version will be increased if the last changes where done by a different user or the last change is more than 24 hours ago (for further details see topic Logging ).

For analysis of the succession of changes the log tables contain additional columns:

  • Kind of change: This column is set by the trigger inserting data into the log table
    • current version: This is the current state of the data in the table
    • UPDATE: This is the state of the data before an update happened
    • DELETE: This is the state of the data when the data have been deleted
  • Date of change: The date and time of the changes. This column has the default value getdate() that means the current date an time is set when any data are inserted into the log table
  • Responsible: The user reponsible for the changes. This column has the default value suser_sname() that means the current user is set when any data are inserted into the log table
  • LogID: A unique ID of the logtable. This column is an identity that means it is set by the database when any data are inserted into the log table
Jan 4, 2025

Diversity exsiccatae

Update

Update of database and client

If either the database or the client needs to be updated, the menu will show an additional entry: Update.

Database update

To update the database, choose Update Update database … from the menu. See chapter Database update for details.

Client update

To update the client, choose Update Update client … and download the lastest version of the client. ee chapter Update client for details.

Jul 22, 2024

Subsections of Update

Diversity exsiccatae

Update Client

Replace the files and folders of your installation of DiversityCollection with the files you received by e-mail or downloaded from the DiversityWorkbench portal. The database will not be influenced by this replacement. After starting the new software you need to transfer the settings of the previous version. When you start the program and connect to a database, the program will check if it is compatible with the database or if the database needs an update. In any of these cases an update entry in the menu will appear. If a new version of the client is available, this menu will contain an update client … entry. Click on it to open the webpage where you may download the client as shown below.

 

Jul 22, 2024

Diversity exsiccatae

Update Database

Update database to current version

If you are the owner of the database (Database role = dbo) and the database needs to be updated, the menu will contain an update database … entry. Select this entry to open a window as shown below to run the provided update scripts, delivered with the client software. These scripts need to run consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either have to run the script DiversityCollectionUpdate_020501_To_020504 or the scripts DiversityCollectionUpdate_020501_To_020502, DiversityCollectionUpdate_020502_To_020503 and DiversityCollectionUpdate_020503_To_020504. The program will guide you through these steps and check for the scripts. All you need to do is click the Start update button. 

Update of all databases on a server

If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:

DiversityCollection.exe UpdateDatabase 127.0.0.1 5432

The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.

Jul 22, 2024

Diversity exsiccatae

Errorlog

If any error messages show up while working with the application, you can find further details concerning the part of the application where the error occurred and the parameters involved in the file e.g. DiversityCollectionError.log in the Module DiversityCollection located in your resources directory.

To open the errorlog, choose Help - ErrorLog from the menu. A window will open showing the content of the errolog. By default the errorlog will be reset at program start. You can keep the errorlog if needed by chossing Help - Errorlog - Keep error log from the menu. A button will appear that allows you to clear the error log manually: Help - Clear ErrorLog.

Jan 4, 2025

Diversity exsiccatae

Module connections

Connections between the modules of the Diversity Workbench

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. DiversityAgents is referred by several modules. To scan for references from these modules on data in DiversityAgents choose Data - Scan modules - from the menu (see image below).

With these options the program will scan all sources of the selected module as listed in the connections for references to the current agent. After selecting an agent in the tree, the sources of the selected modules together with the linked data will be listed as shown below.

Select a link to see a summary of the linked data (see below).

To get further information about an item click on the button. If so far the path to the respective application has not been set, you will get a corresponding message (see below).

Click on the button to set the path to the application (see below).

By default the path to the application is C:\Program Files (x86)\DiversityWorkbench\Diversity...\Diversity.…exe as shown.

Jul 22, 2024

Diversity exsiccatae

Resources

The resources directory is set via the menu (Administration - Resources).

There are 3 possibilities for the resources directory:

  • Select any directory you have read/write access (User defined)
  • Select the "Home" directory of the user
  • Select the "My Documents" directory of the user

The default is set to Home. This directory will contain all files the user needs access to (see image below as an example for the module DiversityAgents).

Certain directories are hidden (Query) and are handled by the software i.e. the content should not be changed by the user. The other folders are generated by the software if missing, e.g. Export for any exports (see below).

Optional copy

By default all files the software needs from the application directory will be copied into the selected resources directory of the user. You can change this behaviour to one of the options listed below:

  • Copy files at program start
  • Add missing files at program start
  • Do not copy

With the next start of the program the software will act according to the selected behaviour. If you change from the Do not copy option to one of the other options the software will act at once according to the new option and e.g. copy missing directories and files into the user directory.

Jan 4, 2025

Diversity exsiccatae

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024

Diversity Gazetteer

Scope of DiversityGazetteer within the Diversity Workbench

DiversityGazetteer is part of the database framework Diversity Workbench. Within this framework the application DiversityGazetteer is confined to the display of geographic places. Any module within the Diversity Workbench is focused on a specific data domain. DiversityGazetteer keeps only data regarding geographic names and places. Data of other realms like e.g. taxonomy are handled in separate modules.

DiversityGazetteer is based on Microsoft SQL-Server 2016 or above and the .Net Framework, Version 8.

For licence and copyright see the licence section.

Diversity Workbench modules

Jan 30, 2025

Subsections of Gazetteer

Diversity Gazetteer

Download

Upcoming version

4.5.1 (2024-??-??)

Current version

4.5

Download

  • Bugfixes in Workbench.dll

Previous versions

4.4.3

  • Database tools included and layout improved
  • Bugfix database tools
  • Adaption of documentation tools to help projects configuration
  • Documentation: Bugfix setting deprecated roles

Database updates

  • 02.05.37: Missing descriptions; TaxonOrder: Adding column IgnoreButKeepForReference for query; TaxonFamily: Adding column IgnoreButKeepForReference for query; New table SynonymyListCache to store results of function SynonymyList; New procedure procFillSynonymyListCache to fill table SynonymyListCache; SynonymyList - Try to get data from cache;

4.4.2

  • Optional inclusion of continents in hierarchy 

Database updates

  • 01.00.34: New function HierarchyIncludeContinents for decision if continents should be included in hierarchy; Inclusion of HierarchyIncludeContinents in SetHierarchyCacheAll; Inclusion of HierarchyIncludeContinents in RefreshGeoCache;

Subsections of Download

Diversity Gazetteer

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Apr 16, 2025

Diversity Gazetteer

Tutorial

Tutorial - first steps

This tutorial will guide you through the first basic steps in DiversityGazetteers. After the installation, make sure that you have access to the database. To start the program, double click on the DiversityGazetteers.exe in the directory where you placed the files of DiversityGazetteers. The main window will open.

Start page 

If you open this window for the first time, you have to connect to the database. A window will open automatically where you can enter your account information and choose the database (see image below, for further informations see database access). If not, click on the button or choose Connection → Database… from the menu to open the Connection window.

Connect page 

After having connected to the server and having chosen a database click on the OK button to return to the main window. As indicated by the  symbol in the tool bar, you are now connected to the database. The tooltip of the button will show your current login informations.

 

Apr 16, 2025

Subsections of Tutorial

Diversity Gazetteer

Tutorial Query

To search for data in the database, use the query section in the left part of the window. To select the query conditions, click on the button in the top panel. A window as shown below will open.

 

With the Maximal number of results you can limit the packet size that should be retrieved from the server. For a slow connection to the database server choose a low value (e.g. 100 as set by default).

Select the desired entries of

  • Name
  • Longitude / Latitude / Distance (km)
  • Place type
  • Project
  • Language
  • Place ID
  • Name ID

Click OK to close the window. According to the example above your query conditions will look like this:

Operators: Press the button to open the operator dropdown list and choose an appropriate operator for your query:

  • “~”: Like - The search string is part of the item.
  • “=”: Equal - The search string matches the item exactly.
  • “<”: Less than - All results less than the search string.
  • “>”: Greater than - All results greater than the search string.

Name: Enter the name of the place you are searching for in the adjacent text box. The results are depending on the operator.

Longitude: Enter the longitude for the desired places. Only numerical input allowed.

Latitude: Enter the latitude for the desired places. Only numerical input allowed.

Distance: Enter the distance regarding longitude and latitude. Depending on the operator all items will be displayed which are inside or outside the distance. Only numerical input allowed.

Place type: Choose from a list of possible entries. Select the type of place you are looking for. “—” means all kind of types.

Language: Choose from a list of possible entries. Select the language which is assigned to the place. If there are no results, set the language to “—” (all languages or no language assigned).

Project: Choose from a list of possible entries. Select your current project. “—” means all projects.

Place ID: Enter the place ID for the desired places. Only integer numbers allowed.

Name ID: Enter the name ID for the desired places. Only integer numbers allowed.

After all query conditions are set, click on the button to start the query. In the resultlist all places will be displayed which matches your query and the selected maximal number of results.

Jan 14, 2025

Diversity Gazetteer

Tutorial - query results

Pressing the Filter button will display all places in the list box which matches the query conditions and the selected maximal number of results:

Query results

The entries consist of name ID, name, place type and coordinates (if any). If no coordinates are available, the entry is shown in gray. In case the entry describes a complex geography (e.g. a country polygon, a river line string etc.), the coordinates represent the “envelope center” of the shape.

The indices of the currently displayed database entries are shown in the header of the list box, as well as the total number of entries. The first line in the list box also contains the indices and may be used to display all entries in total.

Pressing the Filter button will display the next set of entries (according to maximal number of results). The indices will change accordingly.

Pressing the Filter button will display the previous set of entries (according to maximal number of results). The indices will change accordingly.

Pressing the Filter button will add the next set of entries (according to maximal number of results) to the ones already displayed in the list. The indices will change accordingly.

Pressing the Filter button will clear the list box and the query conditions.

The Filter button is designed as a toggle button, which has 2 states. Pressing the button will switch the GISEditor display mode between “View” and “Edit”. If the mode is set to “Edit”, the button will appear as Filter and the map window will be extended by its control panel.

Query results

Jul 22, 2024

Diversity Gazetteer

Tutorial - show places

Tutorial - show places

The results list box displays the current set of places found by the database query. To show a certain place on the map, just double click at the entry. Due to the coordinates of the place the map will be adjusted to this area and build up. Depending on the internet connection and the map server this can take some seconds. A message box will pop up to advice the user to wait, until the map is complete:

Message box

When all tiles of the background map are drawn, press OK to continue. Then the online map will be scanned and the place will be shown on the map. If the coordinates are single positions, markers will be set. If the coordinates describe areas or line strings, the appropriate geometrical objects are drawn. The information area above the map lists the details of the place (name ID, name, place ID, place type, coordinates as well as more names and hierarchy, if available).

Map with marker

A double click at the first line shows all places currently listed in the results box. The information area will not show specific details, but moving the mouse over a place on the map displays the details in a tool tip.

Map with all places

If a place hierachy has been defined, it is shown in the hierarchy list box. Due to historical reasons there might also be a hierarchy text entry for the place, which is displayed beneath the hierarchy, if it is available. Below the place names are displayed, which are one level under the current place in the hierarchy tree, if there are any. By clicking on an entry of the upper or lower hierarchy list the current place can can be switched to that one. If you have administrator permissions, the hierarchy and the hierarchy text entry can be modified.

Map with all places

Since version 1.4.2.0 multiple languages and place types are supported for a place name. If there is more than one language or place types entry assigned, the additional ones are diplayed beneath the preferred entry.

Multiple languages and places

Press the Show Name Parameters button button to display all parameters for a place name stored in the database at a glance in a separate window.

Show name parameters

Jul 22, 2024

Diversity Gazetteer

Tutorial - edit places

If the user has administrator rights for the dataset, the Newbutton, Delete button and Savebutton items are displayed in the toolbar. Additionally the Add name button, Set parentbutton and Remove parentbutton buttons will appear in the info area.

The user then may edit the name of the place using the text box. The Save button item turns to red Redbutton to notify the user that the changes need to be saved by pressing this item before going to another place. The assigned geographical objects may also be edited or changed using the Edit mode of the GIS Editor and saved by pressing the Save button item. To add a new place to the gazetteer, create a geo object within the GISEditor, enter a description and subsequently press the New button item to put it into the database. The user may delete a name entry by pressing the Deletebutton item. To add a new name for the current place just type it into the Name text box and press the Add namebutton button aside. This button is only enabled, if the name has been edited.

To create or change the places hierarchy select an entry and switch ON the Set parent button toggle button. Search and select an entry using the query results list box to assign it as the parent place for the one which is displayed in the info area. The tool tip of the list box will change accordingly. As soon it has been assigned the toggle button will switch OFF again. If no entry should be assigned the button may be released by pressing it again. If the place is part of the hierarchy the Remove parent button button is enabled and may be pressed to remove the assignment of the parent for the current place. This will cut off the upper part of the place’s hierarchy tree.

Appropriate message boxes will pop up for changing or editing the name and hierarchy of a place to prevent changes by mistake. If there are multiple places selected, these buttons will not be functional.

Admin View

If there are more than one name entries for the current place, all names are shown in a list box right of the selected name. The user may switch to another name of the list by double clicking it. One of the name entries may be assigned as the preferred name for the current place. This can be done by left clicking it. A message box will be shown to ensure that the assignment should be made. The preferred name then will appear in red color in the list.

At the right side of the information area there are 2 list boxes. The first shows the projects which are assigned to the current name, the second shows the other projects which are not assigned. The administrator may assign or remove projects to the name by selecting a project and clicking on an appropriate arrow button to shift it to the opposite box. Alternatively he may easily shift the project by double clicking on it.

If the assignment of the projects has been changed, the Savebutton button turns to red Redbutton to notify the user that the changes need to be saved before going to another place. Otherwise the changes will be lost.

Admin View

Jul 22, 2024

Diversity Gazetteer

Tutorial - add places

If the user has administrator rights for the database, the New icon symbol is shown in the tool bar. Then the user may add new place entries to the database using the GISEditor. A background map and geographical objects may be created or imported, e.g. from ArcView shape files. These shapes are often very big and do not match the restrictions of MS SQL Geography Objects as used in the database, so there are several save options, which can help to avoid problems for the import:

Message box

One major restriction of MS SQL Geography Objects is, that polygon lines must not overlap. This is frequently the case on multiple polygons within one geographical object, e.g. the outlines of neighbouring countries. To avoid this, multiple polygons may be split up to single polygons, which can be saved either as separate place entries (with the drawback that the collection will be disbanded) or as one geographical collection (which keeps the togetherness of the elements).

Big ArcView shapes often contain millions of coordinates, which may cause out of memory errors when they are converted to a geographical data object. This can be avoided by successively saving the samples of the GIS editor to the database. Precondition for that is, that a big shape file is split into single geographical objects (samples) already when reading it by the GIS Editor. To do this the appropriate check box of the GIS Editor Settings has to be checked:

Message box

If you create a new place using the GIS Editor, be sure to enter a description in the “Text” field before you add it to the sample list. Clicking the New icon symbol of the tool bar will save the samples of the GIS Editor according to the save options and will use the sample descriptions as the place names. If the samples are split into multiple entries, an index is appended to the name.

Message box

Jul 22, 2024

Diversity Gazetteer

Import Export

  • Export

    Exporting data to text files

  • Import

    Importing data from text files

Apr 16, 2025

Subsections of Import Export

Diversity Gazetteer

Import

Apr 16, 2025

Subsections of Import

Diversity Gazetteer

Import wizard

The examples below are from the module DiversityAgents, but are valid for any other module as well.

With the current solution please ensure that there are no concurrent imports in the same database.

For some imports like e.g. for Collections in DiversityCollection you will be reminded to update the cache tables for the hierarchies.

With this import routine, you can import data from text files (as tab-separated lists) into the database. A short introduction is provided in a video Video starten. Choose Data Import Wizard Agent from the menu. A window as shown below will open that will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choose for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

Choosing the File and Settings

  • File: As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Choosing a file will automatically set the default directory for the import files. To avoid setting this directory, deselect the option Adapt default directory in the context menu of the button to open the file.
  • Encoding: Choose the Encoding of the file, e.g. Unicode. The preferred encoding is UTF8.
  • Lines: The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the
  • First line: The option First line contains the column definition decides if this line will not be imported.
  • Duplicates: To avoid duplicate imports you can Use the default duplicate check - see a video Video starten for an explanation.
  • Language: If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data.
  • Line break: With the option Translate \r\n to line break the character sequence \r\n in the data will be translated in a line break in the database.
  • SQL statements: To save all SQL statements that are generated during a test or import, you can check the option Record all SQL statements. Video starten
  • Schema: Finally you can select a prepared Schema (see chapter Schema below) for the import.

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

The import of certain tables can be paralleled. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import information of logging columns like who created and changed the data, click on the include logging columns button in the header line. This will include additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue background (see below and chapter Table data).

Merging data

You can either import your data as new data or Merge them with data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported. Otherwise the data will be updated.

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

Empty content will be ignored e.g. for the Merge or Update option. To remove content you have to enter the value NULL. As long as the column will allow emty values, the content will be removed using the NULL value.

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you which actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive columns, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparison   = For all merge types other than insert columns for comparison with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

Testing

- To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and then click on the Test data in line:  button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display any errors that occurred as shown below. All datasets marked with a red background, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets:

  • INSERT
  • MERGE
  • UPDATE,
  • No difference
  • Attach
  • No data

The colors of the table columns indicate whether a column is decisive , a key column or an attachment column .  

If you suspect, that the import file contains data already present in the database, you may test this and extract only the missing lines in a new file. Choose the attachment column (see chapter Attaching data) and click on the button Check for already present data. The data already present in the database will be marked red (see below). Click on the button Save missing data as text file to store the data not present in the database in a new file for the import. The import of agents contains the option Use default duplicate check for AgentName that is selected by default. To ensure the employment of this option the column AgentName must be filled according to the generation of the name by the insert trigger of the table Agent (InheritedNamePrefix + ' ' + Inheritedname + ', ' + GivenName  + ' ' + GivenNamePostfix + ', ' + InheritedNamePostfix + ', ' + AgentTitle - for details, see the documentation of the database).

If you happen to get a file with a content as shown below, you may have seleted the wrong encoding or the encoding is incompatible. Please try to save the original file as UTF8 and select this encoding for the import. 

Import

- With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below). You optionally can include a description of your schema and with the button you can generate a file containing only the description.


Schedule for import of tab-separated text files into DiversityAgents

  • Target within DiversityAgents: Agent
  • Database version: 02.01.13
  • Schedule version: 1
  • Use default duplicate check:
  • Lines: 2 - 7
  • First line contains column definition:
  • Encoding: UTF8
  • Language: US

Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings according to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

Description

- A description of the schema may be included in the schema itself or with a click on the Import button generated as a separate file. This file will be located in a separate directory Description to avoid confusion with import schemas. An example for a description file is shown below, containing common settings, the treatment of the file columns and interface settings as defined in the schema.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Jul 22, 2024

Diversity projects

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.
Jul 22, 2024

Diversity projects

Menu

Overview of the menu in DiversityProjects

Connection

  • DatabaseCreate database Create a new DiversityAgents database on the current server
  • Database Database Choose one of the databases available on the server. Only those databases will be listed to which the user has access permission
  • Module connections Edit the connections to the other modules within the Diversity Workbench.
  •  Transfer settings Transfer previous settings IP-Address and port of the server, name of the database, login etc. of a previous version of the client to the current version.
  •  Timeout for database Setting the timeout for queries in the database.
  •  Timeout web requests Setting the timeout for web requests.
  •  Current server activity
  •  Quit Quit the application and stop all processes started by the application

Data

  •  Archive
    •  Administrate archive Administrate the current archives
    •  Create archive Create a new archive
    •  Reset archive Reset the database resp. clear user tables
    •  Restore archive Restore an existing archive
    •  Create schema Create a schema of the database
  • Backup database Backup of the whole database
  • Export
    • Export wizard Export data of the whole database as csv files
    • CSV (bcp) Export data of the whole database as csv files
  •  Import
    •  GFBio Import data from a GFBio project
    •  Import Wizard Import of tab-separated text files
  • Table Editors Edit the data in single tables
    •  Project Edit data of the Project table
    •  Agent Edit data of the ProjectAgent table
    •  Descriptor Edit data of the ProjectDescriptor table
    •  IDs Edit data of the ProjectIdentifier table
    •  IPR Edit data of the ProjectLicense table
    • References Edit data of the ProjectReference table
    •  Resources Edit data of the ProjectResource table
  • Scan modules Scan modules for links to the current dataset
    • DiveristyAgents
    • DiveristyCollection
    • DiveristyReferences
    • DiveristySamplingPlots
    • DiveristyScientificTerms
    • DiveristyTaxonNames

Admininstration

  • Documentation Opens a window providing documentation tools for the database
  •   Logins… Administration of the user
  •    Rename database Rename the current database
  •  Set published address Setting the address published for links by other modules
  •    Database tools … Tools for handling the objects in the database (experts only!)

Help

  • Manual Opens the online manual
  • Feedback … Opens a window for sending feedback
  •   Feedback history … Opens a window for browsing former feedback
  •   Feedback editing … Opens a window for editing the feedbacks (Admins only)
  •   Websites Websites providing further informations
  • Info Show the version of the program and corresponding information

Update

  • Update database … Update database to current version
  • Update client … Download latest version of client

 

 

 

 

 

Mar 24, 2025

Query

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many colunns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Mar 24, 2025

Diversity Projects

Editing

To save the changes in a dataset click on the button.

To undo the changes in a dataset click the button. This will recover the original data unless the changes had been saved or changes were done in certain tables or hierarchies were the data must be stored to display the hierarchy.

To create a new entry in the database, click on the  button below the search result listbox. This will create a entry with the specimen and show it in the list.

To copy a specimen, choose it from the list and click on the button .

To delete a dataset click on the button .

Mar 24, 2025

Subsections of Editing

Diversity Projects

Project

DiversityProjects - UI structure

Like all Diversity Workbench modules, the main window of DiversityProjects consists of a search area (left) and an editing area (right) (see the image below).

List all available projects

  1. To list all available projects, click on the button in the middle section of the search area.
  2. All available projects are listed in the Query results / Suchergebnisse list.
  3. To display the metadata of a project, select one in the results list by clicking on it.

 

Database information

Data about the project is stored in the table Project.

Mar 24, 2025

Diversity Projects

Agents

Institutions and editors of the project

You can manage the agents (editors and institutions) associated with a project in the Agents section. To edit, click the Agents tab at the bottom of the editing area (see the image below).

Add and remove an agent

  1. Use the button  to add an agent or the button to remove an agent.
  2. If you want to link an editor to DiversityAgents, click the button .
  3. If you want to remove the link to the module, click the button .
  4. Select the type, either Person or Institution.
  5. You can add one or more roles to an agent, e.g. Author, Data Curator etc.. Therefor click on the button below the Roles label and select a role from the list.
  6. To change the order in the list, use the buttons .

Database information

The data about the agents are stored in the table ProjectAgent.

Mar 24, 2025

Diversity Projects

Archive

Archives of the project

You can manage the archives of a project in the Archives section. To edit, click the OAIP tab at the bottom of the editing area (see the image below).

Add and remove an archive

  1. Use the button  to add an archive or the button to remove an archive.
  2. Archives can be organized in a hierarchy. To add an archive dependent on an existing archive, you have to select the parent archive before you click on the button to add the depending archive. You will be ask if you want to add a dependent project.

Database information

The data about the archives are stored in the table ProjectArchive.

Mar 24, 2025

Diversity Projects

Descriptor

For an introduction see the video Video starten. To add resp. remove descriptors of a project use the and buttons as shown in the image below.

The types Geographical name, Scientific name and Taxon name are linked to modules. As long as the entry is linked to the corresponding modules, the type can not be changed (see below).

To change the type you have to remove the link to the module (see below).

 

To administrate the types of descriptors, choose Administration - Descriptor types… from the menu. A window as shown below will open. The descriptor types provided by the system can not be changed (see below). The types Geographical name, Scientific name and Taxon name are linked to the corresponding modules DiversityGazetteer, DiversityScientificTerms and DiversityTaxonNames.

You can add, remove and edit your own types of the descriptors (see below). Use the button, to add a new descriptor type, the button to remove the selected type and the resp. button to edit the hierarchy.

 

The data for the descriptors are stored in the tables ProjectDescriptor. and ProjectDescriptorElement.

Mar 20, 2025

Diversity Projects

Hierarchy

To hierarchy of the project is shown in the upper part of the form. Click on the button to set the superior project of the current project. To add and remove project related to the hierarchy, use the  and buttons. The current project will be highlighted with a yellow background.

Jun 21, 2024

Diversity Projects

Identifier

Identifier of the project

Identifier related to a project can be administated in the IDs part (see below).

To edit the types of the identifier open Administration - Identifier types… from the menu. A window as shown below will open where you can manage the types available in you database.

As an Administrator you can add and delete types using the and buttons.

Database information

The data for the references are stored in the table ProjectIdentifier.

Mar 24, 2025

Diversity Projects

Licenses

Add or remove licenses to a project

You can manage the licenses which are related to a project in the IPR & Licenses section. To edit, click the IPR&Licenses tab at the bottom of the editing area (see the image below).

Use the   and button to add or remove a license.

Database information

The data about the agents are stored in the table ProjectLicense .

Mar 24, 2025

Diversity Projects

References

Citations and references of the project

Citations and references used or related to a project can be managed in the Citations & References part (see below).

Watch a short German video as an introduction: Video starten.

Add or remove citations and references

As an editor you can add and delete citations and references.

  1. Add a citation using the button or remove a citation using the button .
  2. To convert a citation into a reference or vice versa you can use the resp. button.

Database information

The data for the references are stored in the table ProjectReference.

Mar 24, 2025

Diversity Projects

Resources

Resources like images or data files that are related directly to a project can be administated in the Resources part (see below). As an editor you can add and delete resources using the and buttons.

The data for the resources are stored in the table ProjectsResources.

Jun 21, 2024

Diversity Projects

Settings

Deprecated

The settings are deprecated. Please use Descriptors instead.

For an introduction see the video Video starten.The settings of the project are shown in the lower part of the form. To edit the template for the settings, select Administration - Settings from the menu. A window as shown below will open. Use the button to add a new setting. With the button you can define the superior setting for a selected setting. With the button you can remove the relation to a superior setting for the selected setting. To change the sequence of the settings within a group of settings (having the same superior setting) set the value of the display order (Ord.:) accordingly. With the button a selected setting may be removed again.

To add settings to a project, you choose among the settings defined as described above. To edit the definition of the settings either use the menu as described above or click on the button (see below). Use the and buttons to add or remove a setting. To copy all settings from another project use the button. To change the value of a setting, choose it in the tree and edit the text in the Value textbox above the tree (see below). According to the hierarchy of the projects, settings defined in any project above the current project will be inherited. This is indicated by a brown color of the setting and the [ name of the superior project ]. To overwrite an inherited value just add the same setting in the current project and enter the value that should be used instead of the inherited value, an empty value in case no value should be given.

Nov 19, 2024

Diversity Projects

History

To inspect the history of a dataset click on the button. A form will open, showing all former states of the data in the tables with the current dataset at the top.

The version will be set automatically. If a dataset is changed the version will be increased if the last changes where done by a different user or the last change is more than 24 hours ago (for further details see topic Logging ).

Mar 24, 2025

Diversity Projects

Table Editors

For the data selected in the main window the table editors offer a direct access to the tables of the database. The menu Data - Table editors provide an editor e.g. for Project… and Agent…

A window with the content of the table will open. Columns with a gray background can not be edited here. Columns with a light gray background are linked to the contents of lookup tables where you can change according to the contents of these tables.

Select Set timeout … from the menu to increase the default timeout from 5 seconds to a higher value, e.g. for greater amounts of data.  

For more details see chapter TableEditors

Jan 14, 2025

Diversity Projects

Import Export

Mar 24, 2025

Subsections of Import Export

Diversity Projects

Import

There are two options to import data:

Project

Mar 24, 2025

Subsections of Import

Diversity Projects

Import GFBio

Import data from GFBio online service

For a short introduction see Video starten.

In the menu choose Data - Import - GFBio to open a window as shown below. Enter the login data (User + Password) and the Key of the project. To retrieve the data click on the Connect button. The software will retrieve the data provided for the project as shown below. Information concerning agents will be taken from the selected DiversityAgents database and the project selected within this database. The GFBio portal does not enforce roles for all the agents enter. If you want to add a role for agents where no role has been given in the GFBio portal, you may choose a default.

If you get an error message about missing identifier types, please open Administration - Identifier types… and insert the missing types.

If all needed types are available click Start import to import the data either into an existing project or a new project that you may include in an existing parent project.

Jan 14, 2025

Feedback

Feedback

If you have suggestions for improvement, need any changes in the programm or encouter an error you can give a feedback to the administrator. Click on the ALT and PRINT buttons to get a screen shot of your current form. After creating the screen shot choose Help - Feedback from the menu to open the feedback form as shown below.

 

Click on the Insert image button to insert the screen shot and give a comment about your problem. In the field Topic enter the topic of your feedback (will appear in response e-mail). The Priority can either be empty or set to 3 levels:

  • urgent
  • as soon as possible
  • nice to have

If necessary, enter a date in the field ToDo until when you would like to have the task described in you feedback be solved. Then click on the  Send feedback button to send your feedback to the administrator. If you would like to receive a message when the problem you described is solved, please enter you e-mail address in the field below the description.

To inspect your former feedbacks choose Feedback history from the menu. A window will open where you can browse your past feedback together with the state of progress.

Mar 24, 2025

Diversity projects

Internals

For users that need more detailed information about the software including database design etc.

Mar 24, 2025

Subsections of Internals

Diversity projects

Database

The database for DiversityProjects is based on Microsoft SQL-Server 2014 or later. There are list for the datatabes and enumeration tables.

Organisation of the data

The data domains of the database are shown in the image below Video starten.

The main table of the database is Project. The structure of the whole database is shown in the image below.

 

 

Jul 22, 2024

Subsections of Database

Diversity Projects

TABLES, VIEWS, FUNCTIONS, PROCEDURES, ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES

ER-Diagram


Table Project

Information on the project

Column Data type Description Nullable Relation
ProjectID int PK, ID of the Project NO -
ProjectParentID int ID of the superior project YES Refers to table Project
Project nvarchar (255) A short title for the project as displayed e.g. for selection from a list in an user interface NO -
ProjectTitle nvarchar (200) An explicit title for the project YES -
ProjectType nvarchar (50) Type of the project YES Refers to table ProjectType_Enum
ProjectDescription nvarchar (MAX) A text, describing characteristic features, e. g. the purpose and scope, of the project YES -
ProjectDescriptionType nvarchar (50) classification of the public description, e. g. abstract YES -
PublicDescription nvarchar (MAX) Public description of the project if different from the description YES -
InternalDescription nvarchar (MAX) Internal description of the project, not to be published YES -
ProjectNotes nvarchar (1000) Internal notes regarding the project, not published on the web YES -
ProjectVersion nvarchar (255) Version number (refers to the database content of this project, not to application development) YES -
ProjectURL varchar (255) An URL where e.g. the project is described YES -
ProjectRights nvarchar (255) The rights, e.g. the copyright of the project YES -
ProjectEditors nvarchar (255) The editors of the project YES -
ProjectInstitution nvarchar (500) The institution responsible for the Project YES -
ProjectSettings xml (MAX) The settings used within the project YES -
ProjectCopyright nvarchar (255) Copyright statement for the data collected for and revised by this project YES -
ProjectLicenseURI nvarchar (255) The license under which the project is re-used or may be re-used YES -
EmbargoDate date The date until which the data should not be published, made available to the public YES -
CreateArchive bit If an archive e.g. by a task schedule should be created YES -
ArchiveProtocol nvarchar (MAX) The protocol created during the last archive YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • ProjectType_Enum

Table ProjectAgent

The persons or institutions involved in the project

Column Data type Description Nullable Relation
ProjectAgentID int Unique ID for the Agent, Primary key NO -
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO Refers to table Project
AgentName nvarchar (255) The name of the agent. Only cached value where AgentURI is given, Part of PK NO -
AgentURI varchar (255) An URL linked to e.g. the module DiversityAgents within the Diversity Workbench, Part of PKDefault value: '' NO -
AgentType nvarchar (50) The type of the agent, e.g. person or institution as defined in ProjectAgentType_Enum YES Refers to table ProjectAgentType_Enum
AgentRole nvarchar (50) The role of the agent within the project as defined in ProjectAgentRole_Enum YES -
AgentSequence int The sequence of an agent within a project YES -
Notes nvarchar (MAX) Notes about the agent YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project
  • ProjectAgentType_Enum

Table ProjectAgentRole

The role of the person or institution involved in the project

Column Data type Description Nullable Relation
ProjectAgentID int Unique ID for the Agent, Part of primary key NO Refers to table ProjectAgent
AgentRole nvarchar (50) The role of the agent within the project as defined in ProjectAgentRole_Enum NO Refers to table ProjectAgentRole_Enum
ProjectID int Part of PK, ID of the Project NO -
AgentName nvarchar (255) The name of the agent. Only cached value where AgentURI is given NO -
AgentURI varchar (255) An URL linked to e.g. the module DiversityAgents within the Diversity Workbench NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • ProjectAgent
  • ProjectAgentRole_Enum

Table ProjectArchive

Archives of the project

Column Data type Description Nullable Relation
ProjectID int Part of PK, ID of the Project NO Refers to table Project and table ProjectArchive
ArchiveID int Part of PK, ID of the Archive NO -
ParentArchiveID int The ID of the parent archive YES Refers to table ProjectArchive
Format nvarchar (50) The format of the archive,e.g. SDD, EML, ABCD etc. YES Refers to table ProjectArchiveFormat_Enum
MimeType nvarchar (50) The mime type of the archive, e.g. zip YES Refers to table ProjectArchiveMimeType_Enum
StorageLocation nvarchar (500) The path or URI of the archive file YES -
ExternalStorageLocation nvarchar (500) The path or URI of the archive file as stored on an external server YES -
FileSHA512Hash nvarchar (529) The hash value generated from the file YES -
FileSize int Size of the file in bytes YES -
TransferDate datetime The date and time when the data were transferred from the productive database (Last date and time when changes may have happend)Default value: getdate() YES -
PublicationDate date The date when the archive is published YES -
DataWithholdingReason nvarchar (50) The reason for locking the data from publication. If empty data may be published YES -
Notes nvarchar (MAX) Notes about the archive YES -
Published bit If the dataset is published and no further changes are allowedDefault value: (0) YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project
  • ProjectArchiveFormat_Enum
  • ProjectArchiveMimeType_Enum

Table ProjectArchiveIdentifier

Identifier of archives of the project

Column Data type Description Nullable Relation
ProjectID int Part of PK, ID of the Project NO Refers to table ProjectArchive and table ProjectIdentifier
ArchiveID int Part of PK, ID of the Archive NO Refers to table ProjectArchive
Identifier nvarchar (255) The identifier if archive is linked to an identifier NO Refers to table ProjectIdentifier
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • ProjectArchive
  • ProjectIdentifier

Table ProjectDescriptor

Object names, event names, keywords, etc., providing indexing information for a resource.

Column Data type Description Nullable Relation
ID int Internal system generated primary key. Note that multiple values for a descriptor concept may be added (e.g. keywords) NO -
ProjectID int ID of the project, foreign key NO Refers to table Project
Language varchar (5) Language in which element content is expressed. Necessary even for numeric or date content (because expressed through string using language-specific conventions)Default value: ’en' NO -
ElementID int ID of a descriptor element concept (foreign key)Default value: (0) NO Refers to table ProjectDescriptorElement
Content nvarchar (255) A name, state, or value text for the descriptor element.Default value: '' NO -
ContentURI varchar (500) The URI of a conceptual ontological resource considered equivalent with the content, especially URIs for taxon names or keywords from ontologies.Default value: '' NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project
  • ProjectDescriptorElement

Table ProjectDescriptorElement

Examples of descriptor elements (= concepts for variables) are keyword, taxon name, pathogen name, host name, or host feature. Association with ResourceCollections is defined in ProjectDescriptorAssociation, relations in Res.DescriptorElementRelation.

Column Data type Description Nullable Relation
ElementID int Numeric identifier (primary key). NO -
ParentElementID int The ID of the parent element YES -
Abbreviation nvarchar (25) Short abbreviated name for descriptor element.Default value: '' NO -
DisplayText nvarchar (80) Concise English label of a descriptor element definition.Default value: '' NO -
DisplayOrder int Order in which elements are displayed independently of a resource collection (for order within a collection see ProjectDescriptorAssociation.DisplayOrder).Default value: (0) NO -
Description nvarchar (1000) A free-form text that may be displayed in user interfaces as explanatory text.Default value: '' NO -
URL varchar (500) The URI of a conceptual ontological resource considered equivalent with this descriptor element.Default value: '' NO -
InternalNotes nvarchar (1000) Internal notes and remarks. Although normally not published in public reports, this should not be used for truly confidential information.Default value: '' NO -
DisplayEnabled bit Whether this DescriptorElement is to be displayed in the user interface. NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table ProjectIdentifier

External identifiers for the project, e.g. a DOI

Column Data type Description Nullable Relation
ProjectID int Part of PK, ID of the Project NO Refers to table Project
Identifier nvarchar (255) The name of the agent. Only cached value where AgentURI is given NO -
Type nvarchar (50) The type of the identifier as defined in table ExternalIdentifierType YES Refers to table ProjectIdentifierType
URL varchar (500) A URL with further informations about the identifier YES -
Notes nvarchar (MAX) Notes about the identifier YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project
  • ProjectIdentifierType

Table ProjectIdentifierType

The type of an external identier, e.g. DOI

Column Data type Description Nullable Relation
Type nvarchar (50) The type of project identifiers (primary key) NO -
ParentType nvarchar (50) The superior type of this type YES -
URL varchar (500) A URL providing with further informations about this type YES -
Description nvarchar (MAX) The description of this type YES -
InternalNotes nvarchar (MAX) Internal notes about the type YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newid() NO -

Table ProjectLicense

The Licenses within a project

Column Data type Description Nullable Relation
LicenseID int ID of the License, part of primary key NO -
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO Refers to table Project
DisplayText nvarchar (200) A display text as shown in the interface generated by the system or edited by the user YES -
LicenseURI varchar (500) The URL of the license under which the project is re-used or may be re-used YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses, Copyright Licenses YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI varchar (500) The link to a module containing futher information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of the license declaration YES -
Context nvarchar (500) The context of the license, e.g. for publication YES -
LicenseDetails nvarchar (500) Details of the license YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
IPRHolder nvarchar (500) The person or institution holding the Intellectual Property Rights YES -
IPRHolderAgentURI varchar (500) The link to a module containing futher information on the person or institution holding the YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
CopyrightHolder nvarchar (500) The person or institution holding the copyright YES -
CopyrightHolderAgentURI varchar (500) The link to a module containing futher information on the person or institution holding the copyright YES -
Notes nvarchar (MAX) Notes about the license YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newid() NO -

Depending on:

  • Project

Table ProjectReference

The references related to the project

Column Data type Description Nullable Relation
ProjectID int Refers to the ID of table Project (= Foreign key and part of primary key) NO Refers to table Project
ReferenceTitle nvarchar (500) The title of the data publication of the project data package or literature reference publication where information on the project and/ or on project dataset(s) was published. Note this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (255) URI of project data citation/ data package citation or URI of literature reference where information on the project and/ or on project dataset(s) was published, e.g. referring to the module DiversityReferences YES -
ReferenceDetails nvarchar (50) Details within the project data citation/ data package citation, e.g. versioning, or details within the literature reference, e.g. pages YES -
ReferenceType nvarchar (255) The type of the data citation or literature reference YES -
IsCitation bit If a reference is the citation for the project data, i.e. the way the project data should be citedDefault value: (0) NO -
ReferenceCitation nvarchar (500) The way the reference should be cited; suggested citation style YES -
URI nvarchar (500) The URI of a reference YES -
Notes nvarchar (MAX) Notes on the project data citation or literature reference YES -
LogInsertedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogInsertedBy nvarchar (50) Who created this datasetDefault value: suser_sname() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project

Table ProjectResource

Resources of the project

Column Data type Description Nullable Relation
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO Refers to table Project
URI varchar (255) The complete URI address of the resource. NO -
SpecificRights nvarchar (500) The rights, e.g. the copyright of the resource YES -
SpecificLicenseURI nvarchar (500) The license under which the resource is re-used or may be re-used YES -
ResourceURI varchar (255) The URI of the image, e.g. as stored in the module DiversityResources. YES -
Notes nvarchar (MAX) Notes about the resource YES -
LogInsertedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogInsertedBy nvarchar (50) Who created this datasetDefault value: suser_sname() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project

Table ProjectSetting

Settings of a project

Column Data type Description Nullable Relation
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO Refers to table Project
SettingID int Refers to ID of Settings, foreign key and part of primary key NO Refers to table Setting
Value nvarchar (MAX) The value of the settingDefault value: '' NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: suser_sname() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: suser_sname() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newid() NO -

Depending on:

  • Project
  • Setting

Table ProjectUser

The projects available for a user

Column Data type Description Nullable Relation
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc.. NO Refers to table UserProxy
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO Refers to table Project
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • Project
  • UserProxy

Table Setting

The settings used within the projects

Column Data type Description Nullable Relation
SettingID int ID of the setting, primary key NO -
ParentSettingID int The ID of the superior setting YES Refers to table Setting
DisplayText nvarchar (50) Short abbreviated description of the setting, displayed in the user interface YES -
Description nvarchar (MAX) Description of the setting YES -
DisplayOrder int The sequence in which the items should be shown in an interface YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: suser_sname() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: suser_sname() YES -
RowGUID uniqueidentifier -Default value: newid() NO -

VIEWS


View Project_Core

Provides all columus of table Project restricted to the projects accessible for a user as set in table ProjectUser with the exception of the dbo

Column Data type Description Nullable
ProjectID int PK, ID of the Project NO
ProjectParentID int ID of the superior project YES
Project nvarchar (255) A short title for the project as displayed e.g. for selection from a list in an user interface NO
ProjectTitle nvarchar (200) An explicit title for the project YES
ProjectType nvarchar (50) Type of the project YES
ProjectDescription nvarchar (2000) A text, describing characteristic features, e. g. the purpose and scope, of the project YES
ProjectNotes nvarchar (1000) Internal notes regarding the project, not published on the web YES
ProjectCopyright nvarchar (255) Copyright statement for the data collected for and revised by this project YES
ProjectRights nvarchar (255) The rights, e.g. the copyright of the project YES
ProjectLicenseURI nvarchar (255) The license under which the project is re-used or may be re-used YES
ProjectVersion nvarchar (255) Version number (refers to the database content of this project, not to application development) YES
ProjectURL varchar (255) An URL where e.g. the project is described YES
ProjectSettings nvarchar (MAX) The settings used within the project YES
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible. YES
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system. YES
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES
RowGUID uniqueidentifier - YES

Depending on:

  • Project
  • ProjectList

View ProjectAgent_Core

Content of table ProjectAgent restricted to user accessible datasets

Column Data type Description Nullable
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO
AgentName nvarchar (255) The name of the agent. Only cached value where AgentURI is given, Part of PK NO
AgentURI varchar (255) An URL linked to e.g. the module DiversityAgents within the Diversity Workbench, Part of PK NO
AgentRole nvarchar (50) The role of the agent within the project as defined in ProjectAgentRole_Enum YES
Notes nvarchar (MAX) Notes about the agent YES
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible. YES
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system. YES
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES
RowGUID uniqueidentifier - NO

Depending on:

  • ProjectAgent
  • ProjectList

View ProjectResource_Core

Content of table ProjectResource restricted to those accessible for a user

Column Data type Description Nullable
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO
URI varchar (255) The complete URI address of the resource. NO
SpecificRights nvarchar (500) The rights, e.g. the copyright of the resource YES
SpecificLicenseURI nvarchar (500) The license under which the resource is re-used or may be re-used YES
ResourceURI varchar (255) The URI of the image, e.g. as stored in the module DiversityResources. YES
Notes nvarchar (MAX) Notes about the resource YES
LogInsertedWhen datetime The time when this dataset was created YES
LogInsertedBy nvarchar (50) Who created this dataset YES
LogUpdatedWhen datetime The last time when this dataset was updated YES
LogUpdatedBy nvarchar (50) Who was the last to update this dataset YES
RowGUID uniqueidentifier - NO

Depending on:

  • ProjectList
  • ProjectResource

View View_ProjectDescriptor

Project descriptors for query

Column Data type Description Nullable
ProjectID int ID of the project, foreign key NO
Descriptor nvarchar (337) Descriptor of the project (Type + Value) NO

Depending on:

  • ProjectDescriptor
  • ProjectDescriptorElement

View View_ProjectSetting

Project settings for query

Column Data type Description Nullable
ProjectID int Refers to the ID of the project (= Foreign key and part of primary key) NO
Setting nvarchar (MAX) Setting of the project (Type + Value) YES

Depending on:

  • ProjectSetting
  • Setting

View ViewBaseURL

Value of the function BaseURL provided via a view for usage e.g. by linked servers

Column Data type Description Nullable
BaseURL varchar (255) Value of the function BaseURL YES

Depending on:

  • BaseURL

View ViewDataCitation

The citation of published data from the project; references of the data publication of the project data package

Column Data type Description Nullable
ProjectID int Refers to the ID of table Project (= Foreign key and part of primary key) NO
ReferenceTitle nvarchar (255) The title of the data publication of the project data package. Note this is only a cached value where ReferenceURI is present. NO
ReferenceURI varchar (255) URI of project data citation/ data package citation of the project data package, e.g. referring to the module DiversityReferences. YES
ReferenceDetails nvarchar (50) Details within the project data citation/ data package citation, e.g. versioning YES
ReferenceType nvarchar (255) The type of the project data citation/ data package citation YES
Notes nvarchar (MAX) Notes on the project data citation/ data package citation YES
URI nvarchar (500) URI of project data citation/ data package citation with information on the project dataset(s) YES
ReferenceCitation nvarchar (500) The way the project data/ data package should be cited; suggested citation style YES

Depending on:

  • ProjectReference

View ViewDiversityWorkbenchModule

Value of the function DiversityWorkbenchModule provided via a view for usage e.g. by linked servers

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) Value of the function DiversityWorkbenchModule YES

Depending on:

  • DiversityWorkbenchModule

View ViewLiteratureReference

The references related to the project; references of literature publications where information on the project and/ or on project dataset(s) is given

Column Data type Description Nullable
ProjectID int Refers to the ID of table Project (= Foreign key and part of primary key) NO
ReferenceTitle nvarchar (255) The title of the literature reference publication where information on the project and/ or on project dataset(s) was published. Note this is only a cached value where ReferenceURI is present. NO
ReferenceURI varchar (255) URI of literature reference with information on the project and/ or on the project dataset(s), e.g. referring to the module DiversityReferences. YES
ReferenceDetails nvarchar (50) Details within the literature reference, e.g. pages YES
ReferenceType nvarchar (255) The type of the literature reference YES
Notes nvarchar (MAX) Notes on the literature reference YES
URI nvarchar (500) URI of the literature reference with information on the project dataset(s) YES
ReferenceCitation nvarchar (500) The way the literature reference should be cited; suggested citation style YES

Depending on:

  • ProjectReference

View ViewProject

Content of table Project including the StableIdentifier

Column Data type Description Nullable
ProjectID int PK, ID of the Project NO
ProjectParentID int ID of the superior project YES
Project nvarchar (255) A short title for the project as displayed e.g. for selection from a list in an user interface NO
ProjectTitle nvarchar (200) An explicit title for the project YES
ProjectDescription nvarchar (2000) A text, describing characteristic features, e. g. the purpose and scope, of the project YES
ProjectNotes nvarchar (1000) Internal notes regarding the project, not published on the web YES
ProjectVersion nvarchar (255) Version number (refers to the database content of this project, not to application development) YES
ProjectURL varchar (255) An URL where e.g. the project is described YES
StableIdentifier varchar (500) The StableIdentifier for the project YES
ProjectType nvarchar (50) Type of the project YES
InternalDescription nvarchar (MAX) Internal description of the project, not to be published YES
PublicDescription nvarchar (MAX) Public description of the project if different from the description YES
ProjectDescriptionType nvarchar (50) classification of the public description, e. g. abstract YES
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible. YES
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system. YES
LogUpdatedBy nvarchar (50) Name of user who last updated the data. YES
LogUpdatedWhen smalldatetime Date and time when the data were last updated. YES
RowGUID uniqueidentifier - YES

Depending on:

  • Project
  • StableIdentifier

FUNCTIONS


Function BaseURL

Provides the basic address for accessing the database

DataType: varchar (255)


Function DiversityWorkbenchModule

Provides the name of the DiversityWorkbench module

DataType: nvarchar (50)


Function PrivacyConsentInfo

Providing common information about the storage and processing of personal data within the DiversityWorkbench

DataType: varchar (900)


Function ProjectChildNodes

Returns a result set that lists all the items within a hierarchy starting at the topmost item related to the given item.

Parameter DataType Description
@ID int ID of the project
Column DataType Description
ProjectID int PK, ID of the Project
ProjectParentID int ID of the superior project
Project nvarchar (50) A short title for the project as displayed e.g. for selection from a list in an user interface
ProjectTitle nvarchar (200) An explicit title for the project
ProjectDescription nvarchar (MAX) A text, describing characteristic features, e. g. the purpose and scope, of the project
ProjectNotes nvarchar (1000) Internal notes regarding the project, not published on the web
ProjectVersion nvarchar (255) Version number (refers to the database content of this project, not to application development)
ProjectURL varchar (255) An URL where e.g. the project is described
ProjectType nvarchar (50) Type of the project
InternalDescription nvarchar (MAX) Internal description of the project, not to be published
PublicDescription nvarchar (MAX) Public description of the project if different from the description
ProjectDescriptionType nvarchar (50) classification of the public description, e. g. abstract
EmbargoDate date The date until which the data should not be published, made available to the public
CreateArchive bit If an archive e.g. by a task schedule should be created
ArchiveProtocol nvarchar (MAX) The protocol created during the last archive

Depending on:

  • Project
  • ProjectChildNodes

Function ProjectDataLastChanges

DataType: datetime

Parameter DataType Description
@ProjectID int PK, ID of the Project

Depending on:

  • Project

Function ProjectHierarchy

Returns a table that lists all the items related to the given item

Parameter DataType Description
@ProjectID int ID of the project
Column DataType Description
ProjectID int PK, ID of the Project
ProjectParentID int ID of the superior project
Project nvarchar (50) A short title for the project as displayed e.g. for selection from a list in an user interface
ProjectTitle nvarchar (200) An explicit title for the project
ProjectDescription nvarchar (MAX) A text, describing characteristic features, e. g. the purpose and scope, of the project
ProjectNotes nvarchar (1000) Internal notes regarding the project, not published on the web
ProjectVersion nvarchar (255) Version number (refers to the database content of this project, not to application development)
ProjectURL varchar (255) An URL where e.g. the project is described
ProjectType nvarchar (50) Type of the project
InternalDescription nvarchar (MAX) Internal description of the project, not to be published
PublicDescription nvarchar (MAX) Public description of the project if different from the description
ProjectDescriptionType nvarchar (50) classification of the public description, e. g. abstract
EmbargoDate date The date until which the data should not be published, made available to the public
CreateArchive bit If an archive e.g. by a task schedule should be created
ArchiveProtocol nvarchar (MAX) The protocol created during the last archive

Depending on:

  • Project
  • ProjectChildNodes

Function ProjectList

The list of Projects accessible for the current user

Column DataType Description
ProjectID int ID of the project

Depending on:

  • Project
  • ProjectUser

Function ProjectParents

Returns a table that lists all the parents of the given project

Parameter DataType Description
@ProjectID int ID of the project as stored in table Project
Column DataType Description
ProjectID int PK, ID of the Project
ProjectParentID int ID of the superior project
Project nvarchar (50) A short title for the project as displayed e.g. for selection from a list in an user interface
ProjectTitle nvarchar (200) An explicit title for the project
ProjectDescription nvarchar (MAX) A text, describing characteristic features, e. g. the purpose and scope, of the project
ProjectNotes nvarchar (1000) Internal notes regarding the project, not published on the web
ProjectCopyright nvarchar (255) Copyright statement for the data collected for and revised by this project
ProjectRights nvarchar (255) The rights, e.g. the copyright of the project
ProjectLicenseURI varchar (255) The license under which the project is re-used or may be re-used
ProjectVersion nvarchar (255) Version number (refers to the database content of this project, not to application development)
ProjectURL varchar (255) An URL where e.g. the project is described
HierarchyLevel int The level of the hierarchy: 1 = level of selected project; increasing with parents in hierarchy

Depending on:

  • Project

Function SettingHierarchyAll

Returns a table that lists all the settings including a display text with the whole hierarchy

Column DataType Description
SettingID int ID of the setting as defined in table Setting
ParentSettingID int ID of the superior setting
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder int The sequence in which the items should be shown in an interface
Description nvarchar (MAX) Description of enumerated object, displayed in the user interface
Hierarchy nvarchar (4000) The hierarchy composed of the display texts of the superior settings

Depending on:

  • Setting

Function SettingHierarchyChildren

Returns a table that lists all the settings depending on a setting

Parameter DataType Description
@SettingID int ID of the setting
Column DataType Description
SettingID int ID of the setting as defined in table Setting
ParentSettingID int The ID of the superior setting
DisplayText nvarchar (50) Short abbreviated description of the setting, displayed in the user interface
DisplayOrder int The sequence in which the items should be shown in an interface
Description nvarchar (MAX) Description of the setting

Depending on:

  • Setting

Function SettingHierarchyNonProject

Returns a table that lists all the settings including a display text with the whole hierarchy that are not included in a project so far

Parameter DataType Description
@ProjectID int The ID of the project
Column DataType Description
SettingID int ID of the setting as defined in table Setting
ParentSettingID int ID of the superior setting
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder int The sequence in which the items should be shown in an interface
Description nvarchar (MAX) Description of enumerated object, displayed in the user interface
Hierarchy nvarchar (4000) The hierarchy composed of the display texts of the superior settings

Depending on:

  • ProjectSetting
  • SettingHierarchyAll

Function SettingHierarchyProjectAll

Returns a table that lists all the settings for a project including those inherited from superior projects.

Parameter DataType Description
@ProjectID int Input parameter. Enter a valid ProjectID.
Column DataType Description
SettingID int The ID of the setting as defined in table Setting
ParentSettingID int The ID of the superior setting
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder int The sequence in which the items should be shown in an interface
Description nvarchar (MAX) Description of enumerated object, displayed in the user interface
Hierarchy nvarchar (4000) The hierarchy composed of the display texts of the superior settings
Value nvarchar (4000) The value of the setting
ProjectID int ID of the superior project from which this setting has been inherited
Project nvarchar (200) The name of the project from which this setting has been inherited

Depending on:

  • ProjectParents
  • ProjectSetting
  • SettingHierarchyAll

Function SettingsForProject

Returns a table that lists all the settings for a project including those inherited from parent projects including formatting options. Used for Metadata retrieval by DiversityCollection cache databases

Parameter DataType Description
@ProjectID int The ID of the project
@SettingFilter nvarchar (255) A optional filter for the settings
@Spacer nvarchar (20) Optional. A spacer placed between the
@DisplayType int Formatting mode of the column ProjectSetting: 1= Whole hierarchy; 2= Remove leading value of @SettingFilter from hierarchy
Column DataType Description
SettingID int ID of the Setting
ParentSettingID int ID of the superior setting
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
Description nvarchar (MAX) Description of enumerated object, displayed in the user interface
ProjectSetting nvarchar (4000) The hierarchy composed of the display texts of the superior settings formatting depending from parameter
Value nvarchar (4000) The value of the setting

Depending on:

  • SettingHierarchyProjectAll

Function StableIdentifier

The stable identifier published for a project

DataType: varchar (500)

Parameter DataType Description
@ProjectID int ID of the project

Depending on:

  • Project

Function UserID

ID of the User as stored in table UserProxy

DataType: int

Depending on:

  • UserProxy

Function Version

Version of the database

DataType: nvarchar (8)


Function VersionClient

Version of the client software compatible with the version of the database

DataType: nvarchar (11)


PROCEDURES


Procedure procInsertProjectCopy

Copy project including all depending data

Parameter DataType Description
@ProjectID int Output parameter, ID of the new project
@CopyID int ID of the project that should be copied
@ProjectTitle nvarchar (200) Title of the new project

Depending on:

  • Project
  • ProjectAgent
  • ProjectLicense
  • ProjectReference
  • ProjectResource
  • ProjectSetting
  • ProjectUser

Procedure SetUserProjects

Parameter DataType Description
@User varchar (50) -

Depending on:

  • UserProxy

ROLES

Content of cell Permission
Not granted
Name of other role Inherited from other role
Granted

Role DiversityWorkbenchAdministrator

Database Role for administrative actions within the database.

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Language_Enum Diversity Workbench User TABLE
Project Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
Project_log Diversity Workbench User Diversity Workbench Editor TABLE
ProjectAgent Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectAgent_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectAgentRole Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectAgentRole_Enum Diversity Workbench User TABLE
ProjectAgentRole_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectAgentType_Enum Diversity Workbench User TABLE
ProjectArchive TABLE
ProjectArchive_log TABLE
ProjectArchiveFormat_Enum TABLE
ProjectArchiveIdentifier TABLE
ProjectArchiveIdentifier_log TABLE
ProjectArchiveMimeType_Enum TABLE
ProjectDescriptor Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectDescriptor_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectDescriptorElement Diversity Workbench User TABLE
ProjectDescriptorElement_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectIdentifier Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectIdentifier_log Diversity Workbench User Diversity Workbench Editor TABLE
ProjectIdentifierType Diversity Workbench User TABLE
ProjectIdentifierType_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectKeyword Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectKeyword_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectLabel Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectLabel_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectLicense Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectLicense_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectReference Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectReference_log Diversity Workbench User Diversity Workbench Editor TABLE
ProjectResource Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectResource_log Diversity Workbench User Diversity Workbench Editor TABLE
ProjectSetting Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectSetting_log Diversity Workbench Editor Diversity Workbench Editor TABLE
ProjectType_Enum Diversity Workbench User TABLE
ProjectUser Diversity Workbench User Diversity Workbench Editor TABLE
Setting Diversity Workbench Editor TABLE
Setting_log Diversity Workbench Editor Diversity Workbench Editor TABLE
Project_Core Diversity Workbench User VIEW
ProjectAgent_Core Diversity Workbench User VIEW
ProjectResource_Core Diversity Workbench User VIEW
View_ProjectDescriptor Diversity Workbench User VIEW
View_ProjectSetting Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDataCitation Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewLiteratureReference Diversity Workbench User VIEW
ViewProject Diversity Workbench User VIEW
BaseURL Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
ProjectChildNodes Diversity Workbench User FUNCTION
ProjectDataLastChanges Diversity Workbench User FUNCTION
ProjectHierarchy Diversity Workbench User FUNCTION
ProjectList Diversity Workbench User FUNCTION
ProjectParents Diversity Workbench User FUNCTION
SettingHierarchyAll Diversity Workbench User FUNCTION
SettingHierarchyChildren Diversity Workbench User FUNCTION
SettingHierarchyNonProject Diversity Workbench User FUNCTION
SettingHierarchyProjectAll Diversity Workbench User FUNCTION
SettingsForProject Diversity Workbench User FUNCTION
StableIdentifier Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procInsertProjectCopy Diversity Workbench Editor PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchEditor

Role DiversityWorkbenchEditor

Database Role with read/write accesss to the database.

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Language_Enum Diversity Workbench User TABLE
Project Diversity Workbench User TABLE
Project_log Diversity Workbench User TABLE
ProjectAgent Diversity Workbench User TABLE
ProjectAgent_log TABLE
ProjectAgentRole Diversity Workbench User TABLE
ProjectAgentRole_Enum Diversity Workbench User TABLE
ProjectAgentRole_log TABLE
ProjectAgentType_Enum Diversity Workbench User TABLE
ProjectArchive TABLE
ProjectArchive_log TABLE
ProjectArchiveFormat_Enum TABLE
ProjectArchiveIdentifier TABLE
ProjectArchiveIdentifier_log TABLE
ProjectArchiveMimeType_Enum TABLE
ProjectDescriptor Diversity Workbench User TABLE
ProjectDescriptor_log TABLE
ProjectDescriptorElement Diversity Workbench User TABLE
ProjectDescriptorElement_log TABLE
ProjectIdentifier Diversity Workbench User TABLE
ProjectIdentifier_log Diversity Workbench User TABLE
ProjectIdentifierType Diversity Workbench User TABLE
ProjectIdentifierType_log TABLE
ProjectKeyword Diversity Workbench User TABLE
ProjectKeyword_log TABLE
ProjectLabel Diversity Workbench User TABLE
ProjectLabel_log TABLE
ProjectLicense Diversity Workbench User TABLE
ProjectLicense_log TABLE
ProjectReference Diversity Workbench User TABLE
ProjectReference_log Diversity Workbench User TABLE
ProjectResource Diversity Workbench User TABLE
ProjectResource_log Diversity Workbench User TABLE
ProjectSetting Diversity Workbench User TABLE
ProjectSetting_log TABLE
ProjectType_Enum Diversity Workbench User TABLE
ProjectUser Diversity Workbench User TABLE
Setting TABLE
Setting_log TABLE
Project_Core Diversity Workbench User VIEW
ProjectAgent_Core Diversity Workbench User VIEW
ProjectResource_Core Diversity Workbench User VIEW
View_ProjectDescriptor Diversity Workbench User VIEW
View_ProjectSetting Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDataCitation Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewLiteratureReference Diversity Workbench User VIEW
ViewProject Diversity Workbench User VIEW
BaseURL Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
ProjectChildNodes Diversity Workbench User FUNCTION
ProjectDataLastChanges Diversity Workbench User FUNCTION
ProjectHierarchy Diversity Workbench User FUNCTION
ProjectList Diversity Workbench User FUNCTION
ProjectParents Diversity Workbench User FUNCTION
SettingHierarchyAll Diversity Workbench User FUNCTION
SettingHierarchyChildren Diversity Workbench User FUNCTION
SettingHierarchyNonProject Diversity Workbench User FUNCTION
SettingHierarchyProjectAll Diversity Workbench User FUNCTION
SettingsForProject Diversity Workbench User FUNCTION
StableIdentifier Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procInsertProjectCopy PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchUser

Role DiversityWorkbenchUser

Database Role with reading accesss to the database.

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
Language_Enum TABLE
Project TABLE
Project_log TABLE
ProjectAgent TABLE
ProjectAgent_log TABLE
ProjectAgentRole TABLE
ProjectAgentRole_Enum TABLE
ProjectAgentRole_log TABLE
ProjectAgentType_Enum TABLE
ProjectArchive TABLE
ProjectArchive_log TABLE
ProjectArchiveFormat_Enum TABLE
ProjectArchiveIdentifier TABLE
ProjectArchiveIdentifier_log TABLE
ProjectArchiveMimeType_Enum TABLE
ProjectDescriptor TABLE
ProjectDescriptor_log TABLE
ProjectDescriptorElement TABLE
ProjectDescriptorElement_log TABLE
ProjectIdentifier TABLE
ProjectIdentifier_log TABLE
ProjectIdentifierType TABLE
ProjectIdentifierType_log TABLE
ProjectKeyword TABLE
ProjectKeyword_log TABLE
ProjectLabel TABLE
ProjectLabel_log TABLE
ProjectLicense TABLE
ProjectLicense_log TABLE
ProjectReference TABLE
ProjectReference_log TABLE
ProjectResource TABLE
ProjectResource_log TABLE
ProjectSetting TABLE
ProjectSetting_log TABLE
ProjectType_Enum TABLE
ProjectUser TABLE
Setting TABLE
Setting_log TABLE
Project_Core VIEW
ProjectAgent_Core VIEW
ProjectResource_Core VIEW
View_ProjectDescriptor VIEW
View_ProjectSetting VIEW
ViewBaseURL VIEW
ViewDataCitation VIEW
ViewDiversityWorkbenchModule VIEW
ViewLiteratureReference VIEW
ViewProject VIEW
BaseURL FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo FUNCTION
ProjectChildNodes FUNCTION
ProjectDataLastChanges FUNCTION
ProjectHierarchy FUNCTION
ProjectList FUNCTION
ProjectParents FUNCTION
SettingHierarchyAll FUNCTION
SettingHierarchyChildren FUNCTION
SettingHierarchyNonProject FUNCTION
SettingHierarchyProjectAll FUNCTION
SettingsForProject FUNCTION
StableIdentifier FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
procInsertProjectCopy PROCEDURE
SetUserProjects PROCEDURE
Jun 5, 2024

Diversity Projects

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table

Column Data type Description
Code nvarchar (50) A text code that uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (500) Description of enumerated object, displayed in the user interface
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayEnable bit Enumerated objects can be hidden from the user interface if this attribute is set to false (= unchecked check box)
InternalNotes nvarchar (500) Internal development notes about usage, definition, etc. of an enumerated object
ParentCode nvarchar (50) The code of the superior entry, if a hierarchy within the entries is necessary
URL nvarchar (500) A URL with further information about this entry
RowGUID uniqueidentifier -Default value: newsequentialid()

Table Language_Enum

Language codes used within the database


Table ProjectAgentRole_Enum

Roles of the agents

Dependent tables:

  • ProjectAgentRole

Table ProjectAgentType_Enum

Types of the agents

Dependent tables:

  • ProjectAgent

Table ProjectArchiveFormat_Enum

Standards for the created archives, e.g. EML

Dependent tables:

  • ProjectArchive

Table ProjectArchiveMimeType_Enum

The MIME (accoridig to the Multipurpose Internet Mail Extensions specification) types of the created archives

Dependent tables:

  • ProjectArchive

Table ProjectType_Enum

Type of the project, e.g. corresponding to a DWB module

Dependent tables:

  • Project
May 3, 2024

Diversity Projects

No-SQL Interface

JSON Cache

Databases of the modules provid a No-SQL interface where the data of the main table and the depending tables are merged as JSON.

Table JsonCache

Content of table JsonCache restricted to public available data

Column Data type Description Nullable Relation
ID int Unique ID for the Dataset, Primary key NO ID of the source
URI varchar (500) The URL as combination of BaseURL and ID NO BaseURL and ID of the source
DisplayText nvarchar (500) Representation in the interface NO Main table of the source
LogUpdatedWhen datetime Date and time when the data were last updated NO -
Data json Data related to the current dataset NO -

procFillJsonCache is started by an update trigger trgUpd… of the main table in the database

Interface in clients

All modules provide data via a cache table. In the header of the clients you can inspect the content of the JsonCache with a click on the button. For modules with a difference between local and public data, you can inspect the content of the public data with a click of the right mouse button.

Update

Apart of the update via the Trigger (see below) you can update the JsonCache via the update button underneath the button.

To update the JsonCache for the whole database select Administration - JsonCache… from the menu. a window as shown below will open where you can update the JsonCache for single datasets or the whole database.

Summary

graph TD;
    TaxonName[Main table in database] 
    trgUpdTaxonName[trgUpd.. of main table in database]
    TaxonName --> |Update in table| trgUpdTaxonName
    proc[Procedure procFillJsonCache setting the content in table JsonCache]
    trgUpdTaxonName --> proc
graph TD;    
    Mainform[Main form]
    ButtonShow[Button show JsonCache of current dataset]
    Mainform --> ButtonShow
    Left[Show Data]
    ButtonShow --> |Left click| Left
graph TD;    
    Mainform[Main form]
    Admin[Administration menu]
    Mainform --> Admin
    Cache[JsonCache...]
    Admin --> Cache
    Adminform[Administration form]
    Cache --> Adminform
    AdminUpdateSingle[Update single dataset]
    Adminform --> AdminUpdateSingle
    AdminUpdateDB[Update for whole database] 
    Adminform --> AdminUpdateDB
Jul 16, 2024

Diversity projects

Version

For information about the version of the client application choose Help, Info…

The current version in the example above is 4.0.0 for the client and 2.1.13 for the database

 

 

Jul 22, 2024

Diversity projects

License

This manual is copyrighted work licensed under a Creative Commons License.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

 

For information about the license of the client software choose Help, Info…

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License (GPL) for more details.

Jul 22, 2024

Diversity projects

Data Access

Access to the data

To get access to the data, you have to fulfill several requirements. In DiversityCollection, you must be a member of one of the user groups. You can only access data, which is listed in the projects you have access to. For external users data may be blocked by entries in the data withholding reasons or due to a data embargo.

   

Jul 22, 2024

Subsections of Access

Diversity projects

Login Administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

To set the website where information about details concerning the General Data Protection Regulation are shown, click on the button.   

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

To administrate the  linked servers, click on the button.   

To send a feedback click on the button.   

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the time span (From - To) and the number of data sets where any activity of the current login has been found.

 

Creation of login

To create a new login click on the button. A window will open as shown below. A login that should be able to create new logins must to be a System administrator.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has [no access] will be listed in [gray] while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

The state and date of the privacy consent according to the General Data Protection Regulation is shown in dependence of the selected database.

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

As a database owner you can edit the permissions and role memberships with the and buttons. Please keep in mind that any change of the permissions may cause serious troubles and should only be used for testing and bug fixing. The final setting of the permissions should be performed by a proper update script of the database. For every action you will get the code that is to be included in an update script (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below). Projects are related to the module DiversityProjects. To get additional information about a project select it in the list and click on the button. 

Starting with database version 02.05.35 next to the projects with full access, a second list provides projects with [Read Only] access (see image below). Use the and buttons to move projects between Accessible and Read Only. If a project is set on [Read Only] a user can still add annotations. Starting with version 4.3.219 a project as a whole can be locked with the restriction of access to read only. For more details see chapter Project administration.

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

To see an overview of the users within a project select one of the project in either list and click on the corresponding button . A window as shown below will open listing all users and their roles with access to the selected project.

To add or remove a role for a login, select the corresponding field and choose or from the context menu (see below).

 

Settings of a login in a database

Depending on the database you can edit the settings of a login as shown below.

If you wish to use settings already defined for another login, click on the Search template button. A window (see below) will open where you can choose among the settings defined for logins in the database.

 

Overview for a login

If you want to see an overview of all permissions and project for a login, click on the button. A window as shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user, roles and projects in the database. 

To remove a user, select it in the list and click on the button. 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

To find users within the database that have no valid login, click on the button. A window as shown below will open, listing the users without a login. Select those that should be removed and click OK. This will include a removal from the collection managers.

 

Jul 22, 2024

Diversity projects

Security

A user may be in several groups with diverse rights in the database. Here certain higher groups have all rights of lower groups in addition to special rights for the higher group, e.g. the group User may only read data of certain tables while Typist has the rights of User and additionally may edit the data in certain tables - see overview below.

Summarized overview of some of the groups and their permissions as an example for the module DiversityCollection

Role Permissions in addition to lower role and user group respectively Included rights
Administrator Delete data, edit user permissions DataManager
CollectionManager Administration of collections, handling loans etc. StorageManager
DataManager Delete data, edit image descripton templates Editor
Editor Create new entries and delete details (not entire data sets) Typist
Requester Has the right to place requests for specimen
StorageManager Administration of stored parts, handling loans etc. User
Typist Edit data User
User See the data of the data tables, add annotations

To place a user in one of the groups, select Administration - Database - Logins... from the menu. In the window that will open select a login and a database. The roles available in the selected database will be listed as shown below. Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

 

If you are an Administrator you may add a user to one of these groups.

Any user may have access to several projects.

Jul 22, 2024

Diversity projects

Project access for user

The accessibility of projects for users can have 4 different states:

  • No access: The current user has no access to the project
  • Accessible: The current user has access to the project
  • [Read only]: The current user has read only access to the project
  • [Locked]: The project is locked. Any user can either none or read only access to the project

To allow the current user access projects use the [ > ] button for the selected project resp. the [ >> ] button for all projects. To revoke access for the current user use the [ < ]  button for the selected project resp. the [ << ] button for all projects. To change the access for a project to read only use the button and the button to remove a project from the read only list.

 

 

Locking of a project

To lock a selected project use the button. For all users the project will be removed from the accessible or read only list and transferred to the locked list. This is only allowed for a database owner (dbo). Please make sure that you really want to lock a project. Any dataset related to this project will be set to read only for all users. For an introduction, please see the a short tutorial Video starten.

To remove the locked state of a project, select the project in the No access list and click on the  button. The selected project will be moved from the locked list into the read only list for those users that had access to the project.

 

Retrieval of projects from DiversityProjects

Details of the projects within the DiversityWorkbench are stored in the database DiversityProjects. To access further information on a project click on the  button. To edit details in projects you require the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you may use the synchronize function in the user administration window as shown below. If DiversityProjects is not available, you may create a new project by clicking the button. If DiversityProjects is available, use the synchronize function .

     

Jul 22, 2024

Diversity projects

Update

Update of database and client

If either the database or the client needs to be updated, the menu will show an additional entry: Update.

Database update

To update the database, choose Update Update database … from the menu. See chapter Database update for details.

Client update

To update the client, choose Update Update client … and download the lastest version of the client. ee chapter Update client for details.

Jul 22, 2024

Subsections of Update

Diversity projects

Update Client

Replace the files and folders of your installation of DiversityCollection with the files you received by e-mail or downloaded from the DiversityWorkbench portal. The database will not be influenced by this replacement. After starting the new software you need to transfer the settings of the previous version. When you start the program and connect to a database, the program will check if it is compatible with the database or if the database needs an update. In any of these cases an update entry in the menu will appear. If a new version of the client is available, this menu will contain an update client … entry. Click on it to open the webpage where you may download the client as shown below.

 

Jul 22, 2024

Diversity projects

Update Database

Update database to current version

If you are the owner of the database (Database role = dbo) and the database needs to be updated, the menu will contain an update database … entry. Select this entry to open a window as shown below to run the provided update scripts, delivered with the client software. These scripts need to run consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either have to run the script DiversityCollectionUpdate_020501_To_020504 or the scripts DiversityCollectionUpdate_020501_To_020502, DiversityCollectionUpdate_020502_To_020503 and DiversityCollectionUpdate_020503_To_020504. The program will guide you through these steps and check for the scripts. All you need to do is click the Start update button. 

Update of all databases on a server

If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:

DiversityCollection.exe UpdateDatabase 127.0.0.1 5432

The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.

Jul 22, 2024

Diversity projects

Errorlog

If any error messages show up while working with the application, you can find further details concerning the part of the application where the error occurred and the parameters involved in the file e.g. DiversityCollectionError.log in the Module DiversityCollection located in your resources directory.

To open the errorlog, choose Help - ErrorLog from the menu. A window will open showing the content of the errolog. By default the errorlog will be reset at program start. You can keep the errorlog if needed by chossing Help - Errorlog - Keep error log from the menu. A button will appear that allows you to clear the error log manually: Help - Clear ErrorLog.

Jul 22, 2024

Diversity projects

Module connections

Connections between the modules of the Diversity Workbench

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. DiversityAgents is referred by several modules. To scan for references from these modules on data in DiversityAgents choose Data - Scan modules - from the menu (see image below).

With these options the program will scan all sources of the selected module as listed in the connections for references to the current agent. After selecting an agent in the tree, the sources of the selected modules together with the linked data will be listed as shown below.

Select a link to see a summary of the linked data (see below).

To get further information about an item click on the button. If so far the path to the respective application has not been set, you will get a corresponding message (see below).

Click on the button to set the path to the application (see below).

By default the path to the application is C:\Program Files (x86)\DiversityWorkbench\Diversity...\Diversity.…exe as shown.

Jul 22, 2024

Diversity projects

Resources

The resources directory is set via the menu (Administration - Resources).

There are 3 possibilities for the resources directory:

  • Select any directory you have read/write access (User defined)
  • Select the "Home" directory of the user
  • Select the "My Documents" directory of the user

The default is set to Home. This directory will contain all files the user needs access to (see image below as an example for the module DiversityAgents).

Certain directories are hidden (Query) and are handled by the software i.e. the content should not be changed by the user. The other folders are generated by the software if missing, e.g. Export for any exports (see below).

Optional copy

By default all files the software needs from the application directory will be copied into the selected resources directory of the user. You can change this behaviour to one of the options listed below:

  • Copy files at program start
  • Add missing files at program start
  • Do not copy

With the next start of the program the software will act according to the selected behaviour. If you change from the Do not copy option to one of the other options the software will act at once according to the new option and e.g. copy missing directories and files into the user directory.

Jul 22, 2024

Diversity projects

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024

Diversity References

Details about References within the Diversity Workbench are stored in the module DiversityReferences. For explicit documentation of this module see DiversityReferences on the homepage of the DiversityWorkbench. This site further provides software for online access to the database DiversityReferences and should be regarded as the prefered way to handle data within this database. This client is a simple tool to provide you with the basic functionallity needed for the local work.

For access to the references from other modules, you need access to the Database DiversityReferences. For a direct access to the data you can use the application DiversityReferences.exe .

Dec 17, 2024

Subsections of References

Diversity references

Download

Current version

4.3.2 (2023-12-14)

Download  

Previous versions

4.3.1 (2023-09-05)

Download  

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Mar 26, 2024

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.
Mar 26, 2024

Tutorial

Training database

For the first steps we provide a training installation on:

training.diversityworkbench.de,5432

Please turn to the development team for a login.

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.

Editing

The main forms of all modules have a design as shown below

Main form

Status

In the status area you find

  • The name of the module,
  • The name of the database if different fron the module
  • The version of the software

The menu contains the options provided by the module

Commands

The commands area contains buttons for e.g. handling the data:

  • - To connect to a database click on the button.
  • - To save the changes in a dataset click on the button.
  • - To propagate the changes in a dataset to linked modules click on the button.
  • - To undo the changes a dataset click the button. This will recover the original data unless the changes had been saved or changes were done in certain tables or hierarchies were the data must be stored to display the hierarchy.
  • - To create a new entry in the database, click on the  button below the search result listbox. This will create a entry with the specimen and show it in the list.
  • - To copy a specimen, choose it from the list and click on the button .
  • - To options a dataset click on the button .
  • - To change the arrangement of the query click on the button.
Mar 26, 2024

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many columns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Jul 29, 2024

Data Editing

Data editing

To edit the data, start the query (click on the button) and choose an item from the query result list. The window will show the details of the dataset as shown below. With button in the upper right area of the form you may access the history of the selected dataset.

In the lower part of the window you find a tab control with various additional data. Click on the tab in the window above to visit the corresponding manual chapter.

Table editor

As an alternative you may edit the datasets in the result list with dedicated table editors.

May 3, 2024

Subsections of Editing

Authors

Authors and editors

The authors, editors etc. are shown in a treeview as shown below. To add a new author, editor etc. click on the  button.

If you want to delete an author, select the dataset in the tree and click on the button. To change the sequence e.g. of the authors use the  and  buttons.

 

 

May 3, 2024

Keywords

Keywords

Every reference title can be attributed to an unlimited number of keywords. Use the button to enter a new keyword and the button to delete a selected keyword. You can specify the language of your keyword, the type of your keyword and an URI. Either choose a keyword from the keywords that are already existing in the database by typing the initial characters and using the the drop down button of the field or type a new keyword.

To view and/or change the URI click on the  button. A simple browser will open as shown below.

 

Click on the  botton if you want to return to the homepage of this browser (www.google.com). Click on the OK button to take the current URI in your database record and close the window.

 

 

May 3, 2024

Marker

Private marker

Marker are the private counterpart of the keywords. You can only see your own marker in this section. To add a marker use the  button. To delete a marker, choose it in the list and click the  button.

Data are stored in table ReferencePrivateDescriptor.

 

 

May 3, 2024

Abstract

Abstract (Notes)

Every user with the proper rights can add one abstract for every language.

For private notes please use the private notes section.

 

 

Jan 14, 2025

Notes

Private notes

In this section you can add private notes to the reference. Every user can enter his or her own notes and will have exclusive access to these notes.

Data are stored in table ReferencePrivateNote.

 

 

May 3, 2024

Availability

Availability

The availability of a reference. To add a availability use the  button. To delete a availability, choose it in the list and click the  button.

Data are stored in table ReferenceAvailability.

 

 

May 3, 2024

Projects

Projects

Every reference can be assigned to any number of projects. To assign a reference to a project click on the  button. To remove it from a project, select the project from the list and click on the  button.

 

If there are projects, to which you have no access to, these will be listed in a separate list at the top as shown above.

Data are stored in the table ReferenceProject. Details upon the projects within the Diversity Workbench are stored in the database DiversityProjects. To open a project to see further information upon a project click on the   button. 

To load projects from the central storage for projects in the module DiversityProjects, choose Administration - Projects … from the menu. A window as shown below will open. Select the database where the projects should be retrieved from. After selecting the projects you need in DiversityReferences you can load these project with a click on the Start download button.

To edit details in the projects you need the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you can use the synchronize functionality in the useradministration form as shown below. If DiversityProjects is not available you can create a new project with the button. If DiversityProjects is available, use the synchronize functionality.

 

 

 

May 3, 2024

Images

Images

Every reference title can be attributed to an unlimited number of images.

Use the button to enter a new image. A window as shown below will open where you can choose either a local stored image or an image provided on a website

To open an image in a separate window, choose if from the list and click on the button. To delete a selected link, click on the button.

 

 

May 3, 2024

Links

Every reference title can be attributed to an unlimited number of Web links, links to PDF files, links providing the Full text and Related links.

Use the button to enter a new link. A Window as shown below will open where you can search an select the links.

Click on the  botton if you want to return to the homepage of this browser (www.google.com). Click on the OK button to take the current URI in your database record and close the window.

To open a link in the system browser, choose if from the list and click on the button. To delete a selected link, click on the button.

 

 

 

May 3, 2024

Hierarchy

Hierarchy

References may be organized in a hierarchy as shown below. Use on the resp. button to set or remove the superior reference (see below). With the button you can change to one of the references shown in the hierarchy.

 

 

May 3, 2024

Import Export

Import

There are several import mechanisms:

Import wizard: Import reference data from tabulator separated text file.

Import tagged text: Import reference data from a tagged text file, e.g. ReferenceManager.

 

 

Export

There are several export mechanisms:

Export wizard: Export reference data to tabulator separated text file.

Export text or RIS: Export reference data as text file or in RIS (Reference Manager) format.

Export CSV: Export data in a tab separated format for external analysis.

 

 

Jan 14, 2025

Subsections of Import Export

Export

Export

Text format

To export data as a text file choose Data - Export … from the menu. A window as shown below will open. You have several options to adapt the format of the export. E.g. you may use a different style for the first author, specifiy the separator for the last author etc.

The colums that should be displayed can be specified in the list Displayed columns. A click on the Transfer to grid button to transfers the data into the data grid as shown below. The sequence of the columns can be changed by dragging a column in the position of your choice. After setting the correct sequence and formatting options (e.g. Format of year - see below) click on the Transfer to text button. Then the text ready for export will be shown in the textbox below. Click on the Save to file button to store the data in the specified file.

 

RIS format (Reference Manager)

To export data in the RIS format according to the commercial database Reference Manager use the RIS-Export function.

Choose Data → Export from the menu to start the export. A form will open.

Click on the Start export button to generate the RIS tagged format and on the Save button to store the result in the specified file.

Jan 14, 2025

Subsections of Export

Export CSV

Export CSV

Notes:

  • The Export CSV function provides a direct copy of selected database table as tabulator separated text file. If you want to generate flles that give a strutured overview of descriptors or description data, you should prefer the Export … Lists or the Export Wizard (coming soon).
  • The Export CSV function requires the “Bulk Copy” tool, which is part of a local Microsoft SQL Server installation. If “Bulk Copy” is not available on your computer, you will get an error message after opening the window.

To export the tables of the database in the a tabulator, comma or semicolon separated format, choose Data → Export → Export CSV … from the menu. A window as shown below will open where you can select the tables to be exported in sections Selection criteria and in the Tables for export.

To start the export click on the Start export button. By default the data will be exported into a directory <working directory>\Export\<database_name>. Click on the button to select a different target directory before starting export.

After export the tables are marked with green backgound, if table schema and data were exported successfully. If only the data were exported, this is marked with yellow background, if nothing was exported, the background is red. A detailled export report can be viewd by a click on the export result file name.  

May 16, 2024

Export Text

Export as text or RIS

To export data as a text file choose Data → Export → Export text or RIS … from the menu. A window as shown below will open. You have several options to adapt the format of the export. E.g. you may use a different style for the first author, specifiy the separator for the last author etc.

 

Text format

The first tab Export as text provides the plain text export. The colums that should be displayed can be specified in the list Displayed columns. A click on the Transfer to grid button to transfers the data into the data grid beneath the button. The sequence of the columns can be changed by dragging a column in the position of your choice. After setting the correct sequence and formatting options (e.g. Format of year - see below) click on the Transfer to text button. Then the text ready for export will be shown in the textbox below. Click on the Save to file button to store the data in the specified file.

If you select the option Generate tab separated  list and click on the Transfer to text button, the data as shown in the data grid will be inserted in a tabulator-separated text file and column titles will be inserted (see image below). Such a file could be edited with a spreadsheet application an re-imported using the Importwizard.

 

RIS format (Reference Manager)

The second tab RIS Export provides the export of data in the RIS format according to the commercial database ReferenceManager use the RIS-Export function.

Click on the Start export button to generate the RIS tagged format and on the Save button to store the result in the specified file.

Jan 14, 2025

Export Wizard

The export wizard provides a possibility to export the data selected in the main form. The data are exported as tab separated text file. The export may include transformations of the data as well as information provided by linked modules and webservices. Choose Data - Export - Export wizard from the menu and then select one of the export targets (Event, Specimen, ...). For a short introduction see the tutorial.  

Adding tables

There are the following ways to add tables:

  • One parallel table
  • Several parallel tables according to selected data
  • Dependent table

All options will include the depending tables as defined for the default table. The option for several tables will add as many tables as there are found in the data.

If you added parallel tables, you should set the sequence of the datasets within these tables: For the columns that should be used for sorting the data, set the ordering sequence to a value > 0 and choose if the ordering sequence should be ascending or descending .

Certain columns in the database may provide information linked to another table or a module resp. webservice . Click on the button to add a linked value.

Adding and editing file columns

To add columns to the exported file, use the buttons. In the textbox at the top of the file column, you can change the header for the column. To change the position of a file column use the resp. button. To fuse a column with the previous column, click in the gray bar on the left side of the column that will change to for fused columns. To remove a file column, use the button. Pre- and postfixes for the columns can directly be entered in the corresponding fields. To apply transformations on the data click on the button.  

Filter

To filter the exported data, use the filter function. Click on the button and enter the text for the filter. Only data matching the filter string will be exported. If a filter is set, the button will have a red background to remind you of the filter. The filter may be set for any number of columns you need for the restriction of the exported data.  

Rowfilter

This filter in contrast to the filter above strictly applies to the row according to the sequence of the data. For an explanation see a short tutorial Video starten.

 

Test

To test the export choose the Test tab, set the number of lines that should be included in the test and click on the Test export button. To inspect the result in a separate window, click on the button.

SQL

If you want to inspect the SQL commands created during the test check this option. To see the generated SQL click on the SQL button after the Test export. A window containing all commands including their corresponding tables will be shown.

 

Export

To export your data to a file, choose the Export tab. If you want to store the file in different place use the button to choose the directory and edit the name of the file if necessary. Check the include a schema option if you want to save a schema together with your export. To start the export, click on the Export data   button. To open the exported file, use the button.

 

Export to SQLite

To export your data into a SQLite database, choose the Export to SQLite tab. You may change the preset name of the database in order to keep previous exports. Otherwise you overwrite previous exports with the same filename. To start the export, click on the Export data   button. To view the exported data, use the button.

 

Schema

To handle the settings of your export, choose the Schema tab. To load a predefined schema, click on the button. To reset the settings to the default, click on the button. To save the current schema click on the button. With the button you can inspect the schema in a separate window.

Mar 26, 2024

Subsections of Export Wizard

Export Wizard Transformation

The exported data may be transformed e.g. to adapt them to a format demanded by the user. Click on the button to open a window as shown below. For an introduction see a short tutorial Video starten.

Here you can enter 6 types of transformation that should be applied to your data. Cut out parts,  Translate contents from the file, RegEx apply regular expressions or Replace text and apply Calculations Σ or Filters on the data from the file. All transformations will be applied in the sequence they had been entered. Finally, if a prefix and/or a postfix are defined, these will be added after the transformation. To remove a transformation, select it and click on the button.

 

Cut

With the cut transformation you can restrict the data taken from the file to a part of the text in the file. This is done by splitters and the position after splitting. In the example below, the month of a date should be extracted from the information. To achieve this, the splitter '.' is added and then the position set to 2. You can change the direction of the sequence with the button Seq starting at the first position and starting at the last position. Click on the button Test the transformation to see the result of your transformation.

With the Start at Pos. option the given splitters will be converted into space (' ') and the whole string starting with the given position will be used (see below).

 

Translate

The translate transformation translates values from the file into values entered by the user. In the example above, the values of the month should be translated from roman into numeric notation. To do this click on the button to add a translation transformation (see below). To list all different values present in the data, click on the button. A list as shown below will be created. You may as well use the and buttons to add or remove values from the list or the button to clear the list. Then enter the translations as shown below. Use the save button to save entries and the Test the transformation button to see the result. 

To load a predefined list for the transformation use the   button. A window as shown below will open. Choose the Encoding of the data in your translation source and indicate if the First line contains column definition. Click OK to use the values from the file for the translation.

 

Regular expression

The transformation using regular expressions will transform the values according to the entered Regular expression and Replace by values. For more details please see documentations about regular expressions.

 

Replacement

The replacement transformation replaces any text in the data by a text specified by the user. In the example shown below, the text "." is replaced by "-". 

 

Calculation 

The calculation transformation Σ performs a calculation on numeric value, dependent on an optional condition. In the example below, 2 calculations were applied to convert 2-digit values into 4 digit years.

 

Filter 

The filter transformation compares the values from the data with a value entered by the user. As a result you can either Export content into file or Export fixed value. To select another column that should be compared, click on the button and choose a column from the file in the window that will open. If the column that should be compared is not the column of the transformation, the number of the column will be shown instead of the symbol. To add further filter conditions use the button. For the combination of the conditions you can choose among AND and OR. 

 

 

 

 

 

 

Mar 26, 2024

Export Wizard Tutorial

This tutorial demonstrates the export of a small sample from the database. For an introduction see a short tutorial Video starten.

Choosing the data

In the main form, select the data that should be exported (only the data displayed in the query results are exported).

Exporting the data

Choose Data → Export → Wizard → Organism ... from the menu. A window as shown below will open where the available tables for export are listed in the upper left area. To show the data columns of a table, select this table in the list.

 

Adding additional tables

In this example, we want to add as many parallel identification tables as present in the data. To do this, click on the button of the Identification table. At the end of the list (depending on your data) the additional tables are added (see below).

 

Setting the sequence for the tables

To set the sequence of the Identifications, select the first table and for the column IdentificationSequence set sorting sequence to 1 and the direction for sorting to descending

 

Choosing data from linked modules

Some columns provide the possibility to add data from linked tables or modules. In this example we choose the column NameURI linking to the module DiversityTaxonNames (see below).

To provide linked values, click on the button. A window as shown below will open, where you can choose among the provided services.

After the service is selected, you will be asked for the value provided by the service (see below).

Now the selected link is added underneath the column as shown below. You can add as many links as you need for your export.

For some modules there are values that refer to other modules with a name like [Link to ...] as shown in the example below.

If you select one of theses values, you will be asked to select the service or database linked to this modul (see below)

... and then to select one of the provided columns (see below)

Within the form this linked values will be marked as shown below. If several results are retrieved these will be separated with by " | ".

 

Adding columns to the file

To add columns to the exported file, click on the buttons for the columns resp. linked values. In this example select all Family values and the TaxonomicName (see below).

 

Fusing columns

The families should appear as one column and as the sources can exist only once for each identification we can fuse these columns. To do so, click on the delimiters between these columns (see below).

 

Setting the headers

By default the headers for the exported data are set according to the names of the columns in the database. To change this, edit them as shown below where TaxonomicName has been changed to Taxon (see below). For fused columns only the header in the first column will be used.

 

Testing

To test the export, click on the Test export button. The result depends on the content in your data but should look similar as shown below.

 

Export

To finally export the data, choose the Export tab. By default the data will be exported into tab separated file in a directory in the application directory (see below). You can change the directory (click on the button). You can choose the Include schema option to create a schema that you may reuse in a later export.

Mar 26, 2024

Import

Import

Reference Manager

To import data stored in the commercial database Reference Manager use the RIS-Export function of Reference Manager.

Import

Choose Data → Import from the menu to start the import. A form will open where you can set the import options.

Filename: Click on the  button to choose the file you want to import from your file system.

Source: Specify the source of the data. This information will be documented in the [ImportedFrom] field in the table ReferenceTitle (see Import: in the main form) and used for subsequent imports and updates from the same source.

Responsible: The user who is responsible for the imported data.

Abstracts: Give the language of the abstracts in the references.

Availability: If more than one filing code is placed in one field, enter the separator for the filing codes.

Keywords: Give the language of the keywords in the references. The keywords can be transferred either to the private descriptors or the public available the descriptors. If you use special signs to classify you keywords you can use the mapping to translate this classification into the descriptor concept in DiversityReferences. This is shown in the [Mapping for descriptor elements] section in the image above. 

Mapping User defined: The UserDefined fields within Reference Manager will be transferred to the corresponding fields within the table ReferenceTitle of DiversityReferences unless you specify it otherwise. If possible, use the more exact targets within DiversityReferences for your import.

Import options: You may either update data allready in the database and import new data from the source or just import new data.

Import format: Currently there is only one import format that is supported by DiversityReferences - Reference Manager (RIS).

Click the [Start import] button to start the import.

Jan 14, 2025

Subsections of Import

Import Text

Import tagged text

Reference Manager

To import data stored in the commercial database Reference Manager use the RIS-Export function of Reference Manager.

Import

Choose Data → Import -> Import tagged text … from the menu to start the import. A form will open where you can set the import options.

Filename: Click on the  button to choose the file you want to import from your file system.

Responsible: Select the user who is responsible for the imported data.

Abstracts: Select the language of the abstracts in the references.

Availability: If more than one filing code is placed in one field, enter the separator for the filing codes.

Keywords: Select the language of the keywords in the references. The keywords can be transferred either to the private descriptors or the public available the descriptors. If you use special signs to classify you keywords you can use the mapping to translate this classification into the descriptor concept in DiversityReferences. This is shown in the Mapping for descriptor elements section in the image above. 

Mapping User defined: The UserDefined fields within Reference Manager will be transferred to the corresponding fields within the table ReferenceTitle of DiversityReferences unless you specify it otherwise. If possible, use the more exact targets within DiversityReferences for your import.

Import options: You may either update data allready in the database and import new data from the source or just import new data.

Import format: Currently there is only one import format that is supported by DiversityReferences - Reference Manager (RIS).

Click the Start import button to start the import. You will be informed about import errors and the number of imported datasets by message windows. If any datasets have been imported, they will be displayed in the query list of the main window, when you close the import form (see image below).

Jan 14, 2025

Import wizard

The examples below are from the module DiversityAgents, but are valid for any other module as well.

With the current solution please ensure that there are no concurrent imports in the same database.

For some imports like e.g. for Collections in DiversityCollection you will be reminded to update the cache tables for the hierarchies.

With this import routine, you can import data from text files (as tab-separated lists) into the database. A short introduction is provided in a video Video starten. Choose Data Import Wizard Agent from the menu. A window as shown below will open that will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choose for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

Choosing the File and Settings

  • File: As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Choosing a file will automatically set the default directory for the import files. To avoid setting this directory, deselect the option Adapt default directory in the context menu of the button to open the file.
  • Encoding: Choose the Encoding of the file, e.g. Unicode. The preferred encoding is UTF8.
  • Lines: The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the
  • First line: The option First line contains the column definition decides if this line will not be imported.
  • Duplicates: To avoid duplicate imports you can Use the default duplicate check - see a video Video starten for an explanation.
  • Language: If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data.
  • Line break: With the option Translate \r\n to line break the character sequence \r\n in the data will be translated in a line break in the database.
  • SQL statements: To save all SQL statements that are generated during a test or import, you can check the option Record all SQL statements. Video starten
  • Schema: Finally you can select a prepared Schema (see chapter Schema below) for the import.

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

The import of certain tables can be paralleled. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import information of logging columns like who created and changed the data, click on the include logging columns button in the header line. This will include additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue background (see below and chapter Table data).

Merging data

You can either import your data as new data or Merge them with data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported. Otherwise the data will be updated.

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

Empty content will be ignored e.g. for the Merge or Update option. To remove content you have to enter the value NULL. As long as the column will allow emty values, the content will be removed using the NULL value.

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you which actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive columns, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparison   = For all merge types other than insert columns for comparison with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

Testing

- To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for your test and then click on the Test data in line:  button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display any errors that occurred as shown below. All datasets marked with a red background, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets:

  • INSERT
  • MERGE
  • UPDATE,
  • No difference
  • Attach
  • No data

The colors of the table columns indicate whether a column is decisive , a key column or an attachment column .  

If you suspect, that the import file contains data already present in the database, you may test this and extract only the missing lines in a new file. Choose the attachment column (see chapter Attaching data) and click on the button Check for already present data. The data already present in the database will be marked red (see below). Click on the button Save missing data as text file to store the data not present in the database in a new file for the import. The import of agents contains the option Use default duplicate check for AgentName that is selected by default. To ensure the employment of this option the column AgentName must be filled according to the generation of the name by the insert trigger of the table Agent (InheritedNamePrefix + ' ' + Inheritedname + ', ' + GivenName  + ' ' + GivenNamePostfix + ', ' + InheritedNamePostfix + ', ' + AgentTitle - for details, see the documentation of the database).

If you happen to get a file with a content as shown below, you may have seleted the wrong encoding or the encoding is incompatible. Please try to save the original file as UTF8 and select this encoding for the import. 

Import

- With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below). You optionally can include a description of your schema and with the button you can generate a file containing only the description.


Schedule for import of tab-separated text files into DiversityAgents

  • Target within DiversityAgents: Agent
  • Database version: 02.01.13
  • Schedule version: 1
  • Use default duplicate check:
  • Lines: 2 - 7
  • First line contains column definition:
  • Encoding: UTF8
  • Language: US

Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings according to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

Description

- A description of the schema may be included in the schema itself or with a click on the Import button generated as a separate file. This file will be located in a separate directory Description to avoid confusion with import schemas. An example for a description file is shown below, containing common settings, the treatment of the file columns and interface settings as defined in the schema.

  • and the video: Anpassungen für HUGO Video starten: Umzug von chm nach html. Anleitung für Umstellung auf html. Übersetzung von html nach markdown. Auswahl der Dateien im Programm. Pandoc als Voraussetzung für Konvertierung. Ansicht der markdown Dateien. Ersetzen des headers (Frontmatter). Anpassungen für Bilder, Ersatz der Icons durch Vektorgrafiken. Beispiel für Vektorgrafik. Bearbeitung der Liste für Ersetzungen über Tabelle. Laden einer Datei mit Ersetungen. Ansicht der Datei und Laden der Datei. Durchfürung der Ersetzungen.
  • How to export the content of enum tables for inclusion in the manual for HUGO
  • and the video Ausgabe des Inhalts von Aufzählungstabellen Video starten: Auswahl der Aufzählungstabellen, Anwählen der Ausgabeoption, Auswahl der Spalten, Export und Ansicht im Formular und im Browser.
  • How to fix broken links for Hugo
  • and the video: Video starten

  • How to related reference links for Hugo

  • and the video: Video starten

Administration

  • How to set the access to projects
    • see chapter Zugriff auf Projekte
    • and the video Video starten: Einstellungen des Zugriffs auf Projekte, Zugriff auf Daten innerhalb von Projekten

Editing

  • How to set the language of a dataset
    • see chapter Sprache
    • and the video Video starten: Festlegen der Sprache des Inhalts eines Datensatzes.
    • How are addresses retrieved from the hierarchy
      • see chapter Hierarchien
      • and the video Video starten: Haupthierarchie mit Ermittlung der Adresse und zusätzliche Hierarchien.
        • How to remove loops from a hierarchy
          • see chapter Schleifen entfernen
          • and the video Video starten: Entfernen von Schleifen in der Hierarchie anhand von Beispieldaten.
    • How to remove loops in the synonymy
    • How to see the public contanct infos
      • see chapter Öffentliche Kontaktdaten
      • and the video Video starten: Ermittlung der öffentlichen Kontaktdaten anhand zugänglichen Kontaktdaten des aktuellen Eintrags sowie der in der Haupthierarchie verfügbaren Kontaktdaten.
    • How to set the icons of descriptors
      • see chapter Descriptoren - Icons einstellen
      • and the video Video starten: 2 prinzipielle Typen von Deskriptor: Modul zugeordnet oder ohne Modul. 4 Möglichkeiten für die Einstellung der Icons - OHNE ICON: Modul zugeordnet: Default Icon des Moduls. ohne Modul: Default Icon für Deskriptor. MIT ICON: ohne Modul: Ausgabe des gesetzten Icons. Modul zugeordnet: Ausgabe des gesetzten Icons. Default Icon des Moduls wird ersetzt.
    • How to propagate changes to linked data
      • see chapter Änderungen verlinkter Datensätze weiterleiten
      • and the video Video starten: DiversityAgents als Modul in der DWB. Darstellung der Beispieldaten in DiversityCollection und DiversityAgents. Änderung in DiversityAgents, Eintrag des geänderten Datensatzes in Update Liste. Auswahl der zu aktualsierenden Datenbanken. Display types in DiversityAgents. Eintrag von aktuellem Datensatz, Eintrag aller Datensätze, Ansicht der Liste, Löschen der Liste. Aktualisieren des Datensatzes. Kontrolle der Änderungen in DiversityCollection.
    • Spreadsheet

  • How to include column RowGUID to enable changes in the PK of a table
  • see chapter …
  • and the video RowGUID einschliessen Video starten: Erläuterung der RowGUID. Beispieldaten im TableEditor. Laden der Daten im Spreadsheet. Versuch der Änderung einer Spalte die Teil des Primärschlüssels ist. Einschliessen der RowGUID. Versuch der Änderung mit eingeschlossener RowGUID. Ablehnung der Änderung bei Kollision mit Primärschlüssel. Änderung der Daten ohne Kollision. Ergebnis der Bearbeitung.

Import

  • How to import data
    • see chapter Überblick
    • and the video Video starten: Import von Daten anhand des Beispiels im Tutorial.
    • How to check for duplicates
      • see chapter Duplikate
      • and the video Video starten: Prüfung auf in der Datenbank bereits vorhandene Duplikate während des Imports.
    • How to transform data during the import
      • see chapter Transformation
      • and the video Video starten. Transformation von Daten für den Import am Beispiel eines Datums.

Archive

  • How to create an achive including the log tables
  • see chapter Archiv inclusive des Logs
  • and the video Video starten.
    (Aufbau von Logtabellen, Vorstellung der Beispieldaten, Erstellung eines Archivs: Einschliessen der Logtabellen, Suche nach Daten, Anlegen des Archivs. Wechsel in leere Datenbank. Einlesen der Archivdaten: Auswahl des Archivs, Log einschliessen, Einlesen der Daten, Archivdaten einspielen, Meldung zu vorhandenem Projekt. Anmeldebestätigung. Ansicht der Daten einschliesslich der Daten in den Logtabellen)
  • How to create an archive
  • see chapter Archiv erstellen
  • and the video Video starten.
    (Automatisierte Erstellung durch Server, Manuelle Erstellung, Suche nach Daten, Erstellung, Inhalt einer xml-Datei, Protokoll).

General

Mar 26, 2024

Subsections of General

High Resolution

High-resolution displays

More and more computers are nowadays delivered with high-resolution displays. Since Diversity References is a Windows forms application, which works pixel-oriented, the program window would become smaller and smaller with increasing display resolution.

To face this problem, Windows uses a scaling mechanism, which zooms pixel-oriented applications, which may lead to a burry picture. To avoid this, an alternative is to increase the font sizes within the application and magnify elements like buttons, data grids and so on, which is called “DPI-awareness” of the application. Since the icons within the application are not zoomed automatically, this mechanism usually only works satisfactory with moderate scaling factors of some 125% or 150%. For higher factors the icons within the application will become too small. You can check the scaling factor fo your system in the Windows settings → System → Display, section “Scale and layout”  

If you have problems with DiversityReferences with a high-resolution display, please try out if you get better results with the Windows scaling. Therefore right-click the program icon (usually on your desktop), select “Properties” and go to the “Compatibility” tab (see image below).

Please click on button Change high DPI setting and another window as shown below will appear.

Check the option “High DPI caling override” and you will be able to select a different value than the default “Application”. Please try out if “System” or “System (Enhanced)” gives better results. After confirming with OK start the application and check the adjustment.

 

May 16, 2024

Feedback

If you have suggestions for improvement, need any changes in the programm or encouter an error you can give a feedback to the administrator. Click on the ALT and PRINT buttons to get a screen shot of your current form. After creating the screen shot choose Help - Feedback from the menu to open the feedback form as shown below.

 

Click on the Insert image button to insert the screen shot and give a comment about your problem. In the field Topic enter the topic of your feedback (will appear in response e-mail). The Priority can either be empty or set to 3 levels:

  • urgent
  • as soon as possible
  • nice to have

If necessary, enter a date in the field ToDo until when you would like to have the task described in you feedback be solved. Then click on the  Send feedback button to send your feedback to the administrator. If you would like to receive a message when the problem you described is solved, please enter you e-mail address in the field below the description.

To inspect your former feedbacks choose Feedback history from the menu. A window will open where you can browse your past feedback together with the state of progress.

Jan 3, 2025

Internals

For users that need more detailed information about the software including database design etc.

May 3, 2024

Subsections of Internals

Administration

Administration

There are several menu items that are only available for database role DiversityReferencesAdministrator:

Keyword types: Administration of the keyword types (descriptors).

Periodicals: Administration of the periodicals.

Reference types: Administration of the reference types.

Logins: Administration of the logins of the server their permissions in the databases.

Rename database: Rename the current database.

Set published names: Setting the address published for links by other modules.

 

 

The other menu items are also available for database role DiversityReferencesEditor:

Documentation: Documentation of the structure of the database.

Projects: Administration of the projects.

 

 

Jan 14, 2025

Subsections of Administration

Descriptors

Keyword types (descriptors)

For the administration of the keywords (= descriptors) choose Administration → Keyword types … from the menu. A window as shown below will open, where you can enter, edit and delete descriptors used as keywords for the references. Click on button to start a new query, for details refer to the manual section concerning the query. Use the button to enter a new descriptor and the button to delete a selected descriptor. Click on the  botton if you want to save your changes of the current dataset. The changes will be saved automatically, if you select a different entry in the query result list. With button you may undo changes of the current dataset since the last save.

A descriptor may have relations to other descriptors (see image below). In section Relations to other descriptor elements use the button to enter a new relation and the button to delete a selected relation. To view and/or change the URI for the descriptor resp. a relation click on the  button.

 

If you try to delete a descriptor that is still referenced by other one as a parent, you will ge an error message as shown below. You may easily find the referencing desceriptor by entering you descriptor label in quey field Relation - Parent

 

With button in the upper right area of the form you may access the history of the selected dataset. After resoring a deleted descriptor, you wil have to restore its deleted relations in separate steps. With button you may send a feedback to the software developers. By clicking on button you may search for reference titles that use the current descriptor (see image below). After closing the reference title overview you have the option to return to the main program window with the found reference titles. 

 

 

Jan 14, 2025

Documentation

Documentation

For the documentation of the database choose Admininstration -> Database → Documentation … from the menu. A window as shown below will open, where you can create diverse formats for the documentation of the structure of the database.

 

 

 

May 16, 2024

Periodicals

Periodicals

For the administration of the periodicals choose Admininstration -> Periodidals … from the menu. A window as shown below will open, where you can enter, edit and delete periodicals used for the references. Click on button to start a new query, for details refer to the manual section concerning the query. Use the button to enter a new periodical and the button to delete a selected periodical. Click on the  botton if you want to save your changes of the current dataset. The changes will be saved automatically, if you select a different entry in the query result list. With button you may undo changes of the current dataset since the last save.

A periodical may have several synonyms (see image above). In section Synonyms use the button to enter a new synonym and the button to delete a selected synonym. Furthermore you may assign the periodical to one or several projects. In section Projects use the button to assign a new project and the button to remove a selected project.

With button in the upper right area of the form you may access the history of the selected dataset. With button you may send a feedback to the software developers. By clicking on button you may search for reference titles that use the current periodical (see image below). After closing the reference title overview you have the option to return to the main program window with the found reference titles. 

 

 

Jan 14, 2025

Reference types

Reference types

For the administration of the reference types (= keywords) choose Admininstration → Reference types … from the menu. A window as shown below will open, where you can edit the definitions for the fields Miscellaneous 1-3 and User defined 1-5. The labels will be shown in the interface according to the type of the reference. You can save your changes by clicking OK or omit your changes by clicking Abort. With button in the upper right area of the form you may access the history of the selected dataset. With button you may send a feedback to the software developers.

 

 

 

May 16, 2024

Database

Database

The database for DiversityRefences is based on Microsoft SQL-Server.

Organisation of the data

The main table of the database are ReferenceTitle corresponding to the reference. Connected to this table you find tables for holding additional information.

The structure of the whole database is shown in the image below.

 

For details about the tables and project relevant data: tables, projects.

 

Jan 14, 2025

Subsections of Database

Installation

Diversity Workbench modules use Microsoft SQL-Server 2014 or above as database engine. If you do not have a database server with DiversityAgents already available, you have to install the database engine first. Download the free version of Microsoft SQL Server Express 2016 or above from http://www.microsoft.com/downloads/.. Start the program and follow the instructions for the installation.

 

Server configuration

To configure your server for remote access, launch the SQL Server Configuration Manager (see image below).

If the tool is not available via the app menu but you have SqlServerManagmentStudio and SqlServer installed type [Win] + r to open the Run dialog, type the command SQLServerManager16.msc and press [Enter] to start the tool.

Then click on the "Protocols for SQLEXPRESS" node. Right click on "TCP/IP" in the list of Protocols and choose "enable" for TCP/IP.

Right click on the TCP/IP node and select, "Properties" to open a window as shown below.

In the part IPALL clear out the value for "TCP Dynamic Ports". Give a TCP-Port number to use when making remote connections, e.g. "4321" as shown above. You have to restart the SQL Server Express service before you can connect to your database. 

If you use a database on a server, make sure that the firewall of the server allows access via the port you set for the connections (see below). 

Start the Microsoft SQL Server Managment Studio and attach the database as shown below. Choose the node "databases" and right-click on it to open the context menu (see below). Then choose "attach" from the context menu. A window will open where you can choose the file DiversityAgents_Data.MDF from your database directory and attach it to the database engine.

 

After the installation make shure to get the latest updates from http://windowsupdate.microsoft.com/.

 

Database configuration

To configure your Database, use the Client as described in

Database configuration.

Mar 26, 2024

Project tables

The access to the data is managed via projects where each project of DiversityReferences may be linked to a project from DiversityProjects. Every entry of table “ReferenceTitle” is assigned to the related projects by table “ReferenceProject”. DiversityReferences contains the tables “UserProxy”, “ProjectUser” and “ProjectProxy” to allow an independent administration of the basic functions related to projects and users.

 

 

Index

Table ProjectProxy

The projects as stored in the module DiversityProjects

Column Data type Description
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
Project nvarchar (50) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects)
ProjectURI nvarchar (255) URI of a project in a remote module, e.g. refering to database DiversityProjects

Table ProjectUser

The projects that a user can access

Column Data type Description
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc..
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects)
ReadOnly bit If the user has only read access to data of this project
Default value: (0)

Table UserProxy

The user as stored in the module DiversityAgents

Column Data type Description
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc..
CombinedNameCache nvarchar (255) The short name of the user, e.g. P. Smith
AgentURI nvarchar (255) URI of a user in a remote module, e.g. refering to database DiversityAgents
Queries xml (MAX) Queries created by the user
ID int ID of the user
PrivacyConsent bit If the user consents the storage of his user name in the database
PrivacyConsentDate datetime The time and date when the user consented or refused the storage of his user name in the database
May 3, 2024

Diversity References

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES


Table ReferenceAvailability

Availability and location of reference items in private or official filing system; e.g., book signatures or reprint article availability. Each responsible user may enter multiple filing codes.

Column Data type Description Nullable Relation
RefID int Refers to the ID code of the main ReferenceTitle table (= foreign key) NO Refers to table ReferenceTitle
RecordID int Unique random ID (see trigger) to identify the availability record. (Technical note: to improve reliability of database replication, the primary key is formed in combination with the RefID. Note that FilingCode is optional and not suitable.)Default value: CONVERT([int],rand()*(2147483647.1),(0)) NO -
FilingCode nvarchar (255) Information about availability or location of a copy of the referenced publication: Filing code of reprint or book in private filing system, institutional catalogue code, signature, official call number, or shelf code in a library. //[RefMan 27: AV]Default value: '' NO -
ReprintStatus smallint Refers to filing system of responsible person. Reprint may be ‘Not in file’ (0), ‘On request (card to author)’ (1), ‘On request (internal order/copy marker)’ (2), ‘On request (interlibrary loan)’ (3), or ‘In file’ (4) //[RefMan 08: RP pro parte]Default value: (0) NO Refers to table Ref_AvailabilityReprintStatus_Enum
RequestDate datetime Only if ReprintStatus = ‘On request’ (1/2): The date on which the reprint was requested. //[RefMan 08: RP pro parte] YES -
Responsible int The person responsible for the availability/filing code information, and to which the reprint status/request date refers. //[RefMan: not supported] NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Ref_AvailabilityReprintStatus_Enum
  • ReferenceTitle

trgInsReferenceAvailability


Table ReferenceDescriptor

Object names, event names, keywords, etc., providing indexing information for a resource.

Column Data type Description Nullable Relation
RefID int ID of external resource to which the descriptor applies (foreign key) NO Refers to table ReferenceTitle
Language varchar (5) Language in which element content is expressed. Necessary even for numeric or date content (because expressed through string using language-specific conventions)Default value: ’en’ NO -
ElementID int ID of a descriptor element concept (foreign key)Default value: (0) NO Refers to table ReferenceDescriptorElement
Content nvarchar (255) A name, state, or value text for the descriptor element.Default value: '’ NO -
ContentURI varchar (255) The URI of a conceptual ontological resource considered equivalent with the content, especially URIs for taxon names or keywords from ontologies.Default value: '’ NO -
InstanceGrouping smallint Normally Null. If set, element relations are evaluated only within same-numbered instances. Example: 3 host-pathogen-pairs exist in one resource, each pair would get same instance number. Still, a place name set to instance=Null would apply to all.Default value: NULL YES -
ID int Internal system generated primary key. Note that multiple values for a descriptor concept may be added (e.g. keywords) NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ReferenceDescriptorElement
  • ReferenceTitle

Table ReferenceDescriptorElement

Examples of descriptor elements (= concepts for variables) are keyword, taxon name, pathogen name, host name, or host feature. Association with ResourceCollections is defined in ReferenceDescriptorAssociation, relations in Res.DescriptorElementRelation.

Column Data type Description Nullable Relation
ElementID int Numeric identifier (primary key). NO -
ElementAbbrev nvarchar (25) Short abbreviated name for descriptor element.Default value: '’ NO -
ElementLabel nvarchar (80) Concise English label of a descriptor element definition.Default value: '’ NO -
DisplayOrder int Order in which elements are displayed independently of a resource collection (for order within a collection see ReferenceDescriptorAssociation.DisplayOrder).Default value: (0) NO -
ElementDescription nvarchar (1000) A free-form text that may be displayed in user interfaces as explanatory text.Default value: '’ NO -
ElementURI varchar (255) The URI of a conceptual ontological resource considered equivalent with this descriptor element.Default value: '' NO -
InternalNotes nvarchar (1000) Internal notes and remarks. Although normally not published in public reports, this should not be used for truly confidential information.Default value: '' NO -
DisplayEnabled bit Whether this DescriptorElement is to be displayed in the user interface. NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Table ReferenceDescriptorElementRelation

General relations between descriptor elements (applicable to all values present in ReferenceDescriptor)

Column Data type Description Nullable Relation
FromElement int Starting point of relation (foreign key, part of primary key) NO Refers to table ReferenceDescriptorElement
RoleLabel nvarchar (25) Abbreviated label for relation in forward directionDefault value: '' NO -
ToElement int End point of relation (foreign key, part of primary key) NO Refers to table ReferenceDescriptorElement
RoleDescription nvarchar (1000) A free-form text that may be displayed in user interfaces as explanatory text.Default value: '' NO -
RoleURI varchar (255) The URI of a conceptual ontological resource considered equivalent with the role of this relation.Default value: '' NO -
InternalNotes nvarchar (1000) Internal notes and remarks. Although normally not published in public reports, this should not be used for truly confidential information.Default value: '' NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ReferenceDescriptorElement

Table ReferenceNote

Public reference abstracts/notes.

Column Data type Description Nullable Relation
RefID int Refers to the ID code of the main ReferenceTitle table (= foreign key) NO Refers to table ReferenceTitle
Responsible int * The person responsible for the abstract information. Abstracts are copyright protected! Clearly state if the abstract was not written by you, but copied from the publication itself or a bibliographic database. //[RefMan: not supported]Default value: [dbo].wbCurrentUserID NO -
Language varchar (20) * Language of the abstract, as ISO 2 letter codes. //[RefMan : not supported!]Default value: ‘UNK’ NO -
Content nvarchar (4000) An abstract containing a short summary of the content of the article or book //[RefMan 25: N2] NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ReferenceTitle

Table ReferencePeriodical

Periodical (journal/magazine, etc.) titles.

Column Data type Description Nullable Relation
Abbreviation nvarchar (255) Standardized abbreviation of periodical or journal. Use periods after the abbreviations //[RefMan 11: JA, JO] NO -
FullName nvarchar (255) Full, non-abbreviated name of periodical or journal //[RefMan 11: JF, JO]Default value: '' NO -
Notes nvarchar (4000) Notes, remarks, or comments regarding the journal/periodical as a whole, incl. “continued as (new title)” or notes about local availabilityDefault value: '' NO -
ImportedFrom nvarchar (255) If imported from another database: The name of the database system or provider; otherwise empty.Default value: '' NO -
PeriodicalID int - NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

trgInsReferencePeriodical


Table ReferencePeriodicalProject

Column Data type Description Nullable Relation
Abbreviation nvarchar (255) Standardized abbreviation of periodical or journal, as defined in ReferencePeriodical entity (= foreign key). NO Refers to table ReferencePeriodical
ProjectID int ID of the project to which the periodical belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectProxy
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ProjectProxy
  • ReferencePeriodical

Table ReferencePeriodicalSynonym

Periodical (journal/magazine, etc.) titles: thesaurus with synonyms -> valid name. Any entry in Periodical.Abbreviation and Periodical.FullName must also be added to the synonym table.

Column Data type Description Nullable Relation
Synonym nvarchar (255) Alternative, synonymous names for the main record. Automatically translated into StdAbbrev if a thesaurus pick list is used in forms. //[RefMan 11: J1, J2] NO -
Abbreviation nvarchar (255) Standardized abbreviation of periodical or journal, as defined in ReferencePeriodical entity (= foreign key). NO Refers to table ReferencePeriodical
Source nvarchar (255) Source of the synonym/thesaurus name: ‘ABBR’ for standard abbreviation, ‘FULL’ for standard full name, else name or abbrev. of user who added a non-standard synonym (like PNAS for Proc. Nat. Acad. Sci.) NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ReferencePeriodical

Table ReferencePrivateDescriptor

Object names, event names, keywords, etc., providing indexing information for a resource.

Column Data type Description Nullable Relation
RefID int ID of external resource to which the descriptor applies (foreign key) NO Refers to table ReferenceTitle
PrivateTo int (UNUSED : using table ProvateDescriptor instead!)Either the UserID of the user who created this descriptor for private usage or null for a public descriptor Default value: [dbo].wbCurrentUserID NO -
Language varchar (5) Language in which element content is expressed. Necessary even for numeric or date content (because expressed through string using language-specific conventions)Default value: ’en’ NO -
ElementID int ID of a descriptor element concept (foreign key)Default value: (0) NO Refers to table ReferenceDescriptorElement
Content nvarchar (255) A name, state, or value text for the descriptor element.Default value: '’ NO -
ContentURI varchar (255) The URI of a conceptual ontological resource considered equivalent with the content, especially URIs for taxon names or keywords from ontologies.Default value: '' NO -
InstanceGrouping smallint Normally Null. If set, element relations are evaluated only within same-numbered instances. Example: 3 host-pathogen-pairs exist in one resource, each pair would get same instance number. Still, a place name set to instance=Null would apply to all.Default value: NULL YES -
ID int Internal system generated primary key. Note that multiple values for a descriptor concept may be added (e.g. keywords) NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ReferenceDescriptorElement
  • ReferenceTitle

Table ReferencePrivateNote

User specific notes. Each user will only see the notes entered under the same responsible user name.

Column Data type Description Nullable Relation
RefID int Refers to the ID code of the main ReferenceTitle table (= foreign key) NO Refers to table ReferenceTitle
PrivateTo int * The person responsible for the Notes. //[RefMan: not supported]Default value: [dbo].wbCurrentUserID NO -
Content nvarchar (4000) Internal notes regarding the reference title. Notes will normally be visible only under the same Responsible login name. //[RefMan 06: N1, AB] NO -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ReferenceTitle

Table ReferenceProject

The projects within which the Reference were placed

Column Data type Description Nullable Relation
RefID int Refers to the ID of ReferenceTitle (= Foreign key and part of primary key) NO Refers to table ReferenceTitle
ProjectID int ID of the project to which the Reference belongs (Projects are defined in DiversityProjects) NO Refers to table ProjectProxy
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • ProjectProxy
  • ReferenceTitle

Table ReferenceRelator

Reference authors, book editors, or series editors.

Column Data type Description Nullable Relation
RefID int Refers to the ID code of the main ReferenceTitle table (= foreign key) NO Refers to table ReferenceTitle
Role nvarchar (3) Relator codes from MARC; Reference manager supports only aut = primary author, 2 = secondary author/editor, 3 = series editor. //[RefMan implicit] NO Refers to table Ref_RelatorRole_Enum
Sequence int The sequence of authors of the article. (Default based on system date/time; counter attrib. wouldn’t work with replication -> random sequence! Note: Au+RefID+Type is not necessarily unique. Two authors may have identical abbreviated names, e.g. spouses!)Default value: CONVERT([int],(99999)*(CONVERT([float],getdate(),(0))-(37200)),(0)) NO -
Name nvarchar (255) Author, editor, etc. Example: ‘Miller, W. I., Jr.’. Format: Last name, comma, first initial with period and blank, optional middle initial, and optional comma plus suffix (Jr./Sr./III./MD etc.) //[RefMan 04: A1/AU, 14: A2/ED, 24: A3; no ‘*’ allowed!] NO -
AgentURI varchar (255) The URI of the Agent, e.g. as stored within the module DiversityAgents YES -
SortLabel nvarchar (255) Name of the agent without special characters formatted to facilitate sorting YES -
Address nvarchar (1000) The address of the author, if available. Entered only in cases where it is of special relevance to one of the users of the database (or if imported from a database). //[RefMan 32: AD]Default value: '’ YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Ref_RelatorRole_Enum
  • ReferenceTitle

trgInsReferenceRelator


Table ReferenceTitle

Main entity; compatible with Reference Manager™ v.9-11

Column Data type Description Nullable Relation
RefType nvarchar (10) Type of literature reference, determines which fields are available for data entry. The value must come from the pick list provided. //[RefMan 01: TY]Default value: ‘JOUR’ NO Refers to table Ref_Type_Enum
RefID int Unique reference ID code for the reference record. Currently supporting only integer numbers. Note that RefMan in principle supports 20 char., but uses only integers. //[RefMan 02: ID]Default value: CONVERT([int],rand()*(2147483647.1),(0)) NO -
RefDescription_Cache nvarchar (255) * A short system generated text identifying the reference, usually authors, year, title. Example: ‘Smith. & Nao 1999. New Taxa.’ //[RefMan: not applicable]Default value: '’ NO -
Title nvarchar (MAX) The main (primary) title. Use normal capitalization, omit a period (’.’) at the end, and do not type a paragraph return (Enter) at the end of each line! //[RefMan 03: TI, T1, CT, BT only for BOOK & UNPB]Default value: '’ NO -
DateYear smallint Year of the publication date (primary date). Only numbers are allowed and the year must be entered with 4 digits (‘1998’, not ‘98’). //[RefMan 05: Y1,PY pro parte] YES -
DateMonth smallint Optional: The month of the publication date. [Note: in DateYear/Month/Day the information printed on the book or journal are entered, even if this is not the true date!] //[RefMan 05: Y1,PY pro parte] YES -
DateDay smallint Optional: The day of the publication date. [Note continued: if the true date is relevant, e.g. for the purpose of nomenclatural priority, it can be entered under DateSecondary.] //[RefMan 05: Y1,PY pro parte] YES -
DateSuppl nvarchar (255) Optional: A date supplement, like ‘approx.’, a season (‘Summer’), a quarter (‘1st Quarter’), or any other information regarding the publication date. //[RefMan 05: Y1,PY pro parte]Default value: '’ NO -
SourceTitle nvarchar (MAX) The book (secondary) title in cases where the reference is an article or chapter from a book. Use normal capitalization.//[RefMan 13: T2; BT for all types except BOOK & UNPB]Default value: '’ NO -
SeriesTitle nvarchar (255) The series title. Use normal capitalization, omit a period (’.’) at the end, and do not type a paragraph return (Enter) at the end of each line! //[RefMan 23: T3]Default value: '’ NO -
Periodical nvarchar (255) Journal/periodical in which the article appeared. Linked to the Abbreviation attribute of ReferencePeriodical. //[RefMan 11: JF, JO, JA]Default value: '’ NO -
Volume nvarchar (255) The volume (for periodicals or journals, excluding the issue number), report number, etc. //[RefMan 12: VL pro parte, comp. Edition!]Default value: '’ NO -
Issue nvarchar (255) The issue, if any. Useful also to enter a special designation for a supplement, for example for ‘xxx 45 (Suppl.)’ enter volume = 45 and issue = ‘Suppl.’. Do not put ‘()’ around the issue number. //[RefMan 15: IS]Default value: '’ NO -
Pages nvarchar (255) The page, table, or figure numbers for the reference, e.g. ‘23-41’, ‘341 pp.’, or ‘20, 22-24, 32’ (for non-consecutive pages). //[RefMan 09: SP + 10: EP]Default value: '’ NO -
Publisher nvarchar (255) The name of the publisher (publishing company or institution, including universities or scientific societies). //[RefMan 17: PB]Default value: '’ NO -
PublPlace nvarchar (255) The location where the item being referenced was published, such as a city and state. //[RefMan 16: CY, CP]Default value: '’ NO -
Edition smallint Number of the edition of a book. Use only positive integer numbers. //[RefMan 12: VL pro parte, compare Volume!] YES -
DateYear2 smallint Year of a secondary date, esp. the true publ. date where relevant for nomenclatural priority. Only numbers are allowed and the year must be entered with 4 digits (‘1998’, not ‘98’). //[RefMan 28: Y2 pro parte] YES -
DateMonth2 smallint Optional: The month of a secondary date. //[RefMan 28: Y2 pro parte] YES -
DateDay2 smallint Optional: The day of a secondary date. //[RefMan 28: Y2 pro parte] YES -
DateSuppl2 nvarchar (255) Optional: A date supplement a secondary date, like ‘approx.’, a season (‘Summer’), a quarter (‘1st Quarter’), or any other information regarding the secondary date. //[RefMan 28: Y2 pro parte]Default value: '’ NO -
ISSN_ISBN nvarchar (18) The ‘International Standard Serial Number’ or ‘International Standard Book Number’. Optional information; use is recommended only for publications that are otherwise difficult to order. //[RefMan 26: SN]Default value: '’ NO -
Miscellaneous1 nvarchar (255) Various reference type dependent information; e.g. the total number of volumes for books //[RefMan 29: M1]Default value: '’ NO -
Miscellaneous2 nvarchar (255) Various reference type dependent information //[RefMan 30: M2]Default value: '’ NO -
Miscellaneous3 nvarchar (255) Various reference type dependent information //[RefMan 31: M3]Default value: '’ NO -
UserDef1 nvarchar (MAX) User defined fields as entered in Reference Manager, only provided for import/export compatibility and not supported beyond that. //[RefMan 18: U1]Default value: '’ NO -
UserDef2 nvarchar (MAX) User defined fields as entered in Reference Manager, only provided for import/export compatibility and not supported beyond that. //[RefMan 19: U2]Default value: '’ NO -
UserDef3 nvarchar (MAX) User defined fields as entered in Reference Manager, only provided for import/export compatibility and not supported beyond that. //[RefMan 20: U3]Default value: '’ NO -
UserDef4 nvarchar (MAX) User defined fields as entered in Reference Manager, only provided for import/export compatibility and not supported beyond that. //[RefMan 21: U4]Default value: '’ NO -
UserDef5 nvarchar (MAX) User defined fields as entered in Reference Manager, only provided for import/export compatibility and not supported beyond that. //[RefMan 22: U5]Default value: '' NO -
WebLinks nvarchar (MAX) One or several URLs; use the semicolon as separator (http://www…). A URL may point to a local file (C:\graphic.gif; \servername\Data\x.doc) //[RefMan 33: UR]Default value: '' NO -
LinkToPDF nvarchar (MAX) One or several URLs; use the semicolon as separator (http://www…). A URL may point to a local file (C:\graphic.gif; \servername\Data\x.doc) //[RefMan 34: L1]Default value: '' NO -
LinkToFullText nvarchar (MAX) One or several URLs; use the semicolon as separator (http://www…). A URL may point to a local file (C:\graphic.gif; \servername\Data\x.doc) //[RefMan 35: L2]Default value: '' NO -
RelatedLinks nvarchar (MAX) One or several URLs; use the semicolon as separator (http://www…). A URL may point to a local file (C:\graphic.gif; \servername\Data\x.doc) //[RefMan 36: L3]Default value: '' NO -
LinkToImages nvarchar (MAX) One or several URLs; use the semicolon as separator (http://www…). A URL may point to a local file (C:\graphic.gif; \servername\Data\x.doc) //[RefMan 37: L4]Default value: '' NO -
SourceRefID int * Independent publication (e.g. an edited book) in which a dependent publication was published. Refers to the ID code of a reference already entered in this system. Provided as an alternative to ref. manager’s denormalized storage! YES -
Language nvarchar (25) * Language of the article/book, as ISO 2 letter codes. //[RefMan: not supported!]Default value: ‘UNK’ NO -
DuplicateCheck_Cache nvarchar (255) * A system generated string (typically Au. 1-4/Yr./Jour./Vol./first page) that is assumed to be unique. Use ‘DuplicateOverride’ to override if two reference titles are falsely identified as duplicates. //[RefMan: not applicable]Default value: '’ YES -
DuplicateOverride bit * A number to manually override automatic duplicate check, enter a number 1-255 if the system claims that non-duplicate entries are duplicates. //[RefMan: not applicable]Default value: (0) NO -
ReplaceWithRefID int * Old RefIDs are maintained to provide stable object links. Instead of direct deletes, users may select a reference to be the valid one, into which all related information (keywords, markers) is merged. YES -
Problem nvarchar (4000) * A problem that occurred during data editing within the application. Typically the entries here should later be deleted after help has been obtained. Do not enter scientific or bibliographic problems here; use Notes for such permanent problems!Default value: '' NO -
ProblemUpdatedBy int * Operator who entered the problem text YES -
ProblemUpdatedWhen datetime * Date and time when problem was recorded YES -
CitationText nvarchar (1000) * Full text of a citation that describes the current reference. Use if ref. is only known as a citation in the bibliography of another publication, or if imported from unstructure data source. Empty if reference is transcribed from original publication!Default value: '' NO -
CitationFrom nvarchar (255) * Description of publication, Only known as citation from bibliography of another publication given here (as ID code or author/year description); Empty if transcribed from original publication!Default value: '' NO -
ImportedFrom nvarchar (80) * If imported from a reference database (esp. a commercial one): The name of the database system or provider; otherwise empty. This information is important to prevent copyright violations!Default value: '' NO -
ImportedID nvarchar (50) * If imported from a reference database (esp. a commercial one): The ID identifying the record in that database; otherwise empty. Requires ImportedFrom //[RefMan: not supported!; Internal management attribute]Default value: '' NO -
PlausibilityCheckedBy int * Person responsible for a first plausibility or consistency check. User and Date are automatically filled if ‘Original check’ performed directly. //[RefMan: not applicable. Internal mgmt.attribute] YES -
PlausibilityCheckedWhen datetime * Date and time when plausibility/consistency was checked (i.e. data entry rules and spelling errors checked, no comparison with original publication) //[RefMan: not applicable. Internal mgmt.attribute] YES -
OriginalComparedBy int * Name of user responsible for comparison of ReferenceTitle record with original publication //[RefMan: not applicable. Internal mgmt.attribute] YES -
OriginalComparedWhen datetime * Date and time when entry was compared with the original publication (important esp. when ReferenceTitle was entered from secondary ReferenceTitle list) //[RefMan: not applicable. Internal mgmt.attribute] YES -
DateFrom_Cache datetime Calculated field, based on DateYear, DateMonth, DateDay, where missing information is replaced with earliest possible value (e.g. “1999” results in 1.1.1999) YES -
DateTo_Cache datetime Calculated field, based on DateYear, DateMonth, DateDay, where missing information is replaced with latest possible value (e.g. “1999” results in 31.12.1999) YES -
Date2From_Cache datetime Calculated field, based on Date2Year, Date2Month, Date2Day, where missing information is replaced with earliest possible value (e.g. “1999” results in 1.1.1999) YES -
Date2To_Cache datetime Calculated field, based on Date2Year, Date2Month, Date2Day, where missing information is replaced with latest possible value (e.g. “1999” results in 31.12.1999) YES -
Responsible int * Person responsible for entering this reference into the data collectionDefault value: (-1) NO -
SysRecordVersion int (Under trigger control; number automatically increased with every record update, enabling manual version tracking)Default value: (0) YES -
ParentRefID int Refers to the RefID of the superior reference YES -
LogInsertedBy nvarchar (50) ID of the creator of this data setDefault value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of the person to update this data set lastDefault value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -

Depending on:

  • Ref_Type_Enum

trgInsReferenceTitle

May 3, 2024

Diversity References enumeration tables

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table


Table Ref_AvailabilityReprintStatus_Enum

Provides codes for ReferenceAvailability.ReprintStatus field

Dependent tables:

  • ReferenceAvailability

Table Ref_RelatorRole_Enum

Provides codes for creator or contributor roles like author, editor, photographer, advisor, etc. These roles are used in ReferenceRelator

Dependent tables:

  • ReferenceRelator

Table Ref_Type_Enum

Reference type definitions. Which reference attributes are enabled and how they should be labeled? Currently only the usage of a type is defined here; the attribute labels are defined directly in the vba code.

Dependent tables:

  • ReferenceTitle
May 3, 2024

Creation

To configure your Database, choose Administration → Database → Rename database to change the name of the database according to your requirements. During this renaming all processes in the database will be terminated (you will get a warning if processes from other host are active).

Afterwards you should adapt the address that is published by the database for access by other modules. Choose Administration → Database → Set published address from the menu. This will change the published address to the name of the server where your database is located and an identifier for you database, e.g. http://xy.diversityworkbench.de/Collection/

 

Mar 26, 2024

Configuration

To configure your Database, choose Administration → Database → Rename database to change the name of the database according to your requirements. During this renaming all processes in the database will be terminated (you will get a warning if processes from other host are active).

Afterwards you should adapt the address that is published by the database for access by other modules. Choose Administration → Database → Set published address from the menu. This will change the published address to the name of the server where your database is located and an identifier for you database, e.g. http://xy.diversityworkbench.de/Collection/

 

Mar 26, 2024

History

To inspect the history of a dataset click on the button. A form will open, showing all former states of the data in the tables with the current dataset at the top. The version is shown in the header of the main.

The version will be set automatically. If a dataset is changed the version will be increased if the last changes where done by a different user or the last change is more than 24 hours ago (for further details see topic Logging ).

For analysis of the succession of changes the log tables contain additional columns:

  • Kind of change: This column is set by the trigger inserting data into the log table
    • current version: This is the current state of the data in the table
    • UPDATE: This is the state of the data before an update happened
    • DELETE: This is the state of the data when the data have been deleted
  • Date of change: The date and time of the changes. This column has the default value getdate() that means the current date an time is set when any data are inserted into the log table
  • Responsible: The user reponsible for the changes. This column has the default value suser_sname() that means the current user is set when any data are inserted into the log table
  • LogID: A unique ID of the logtable. This column is an identity that means it is set by the database when any data are inserted into the log table
Mar 26, 2024

Logging

Changes within the database will be documented for each dataset with the time and the responsible user in the columns shown in the image below.

All main tables have a corresponding logging table. If you change or delete a dataset the orignial dataset will be stored in this logging table together with informations about who has done the changes and when it happend. To see the data stored in the logging tables, click on the button to open the history of a dataset.

Mar 26, 2024

Login administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the timespan (From - To) and the number of data sets where any activity of the current login has been found.

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

 

Creation of login

To create a new login click on the button. A window will open as shown below.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has no access will be listed in gray while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

 

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below).

There are 4 states of accessibility for projects

  •     Full access: The user can edit the data
  •      Read only access: The user can only read the data
  •      Locked: The project is locked. Nobody can change the data
  •     No access: The user has no access via a project

Projects are related to the module DiversityProjects. To get additional information about a project select it in the the list and click on the button. 

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

 

 

Overview for a login

If you see an overview of all permissions and project for a login, click on the button. A window a shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user and roles in the database. 

To remove a user, select it in the list and click on the button. 

 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates, that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

Mar 26, 2024

Linked server

Databases not available on the local server may be accessible via a linked server. Provided the option for loading the connections is set, the program will automatically try to connect to these databases. Otherwise you can connect to these databases as described in chapter ModuleConnections. To administrate the linked servers, choose Administration - Linked servers ... from the menu. A form (see below) will open where you can add linked servers and inspect the content of the available databases.

Use the  resp. buttons to add or remove a linked server. To add a linked server, you need the name of the server and the port, e.g. tnt.diversityworkbench.de, 5432, the login associated with the connection of the linked server e.g. TNT and the password for this login. The available databases will be listed as shown above. To inspect the content, select among the tables or views listed in the right part as shown above. Linked servers have certain restrictions for the availability of data, e.g. XML and geography data are not available via a linked server. For a table or view containing incompatible content you may encounter a corresponding error mentioning the reason for the incompatibility.

An expample for a linked server as provided for central databases is shown below (using the management studio for SQL-Server) Linked servers

Mar 26, 2024

Tools

These are the tools to handle the basic parts of the database. These tools are only available for the owner of the database and should be handled with care as any changes in the database may disable the connection of your client to the database. Before changing any parts of the database it is recommended to backup the current state of the database. To use these tools, choose Administation → Database → Database tools ... from the menu. A window will open as shown below.

Description

The Description section (see above) shows the basic definitions of the objects in the database and enables you to enter a description for these objects including tables and their columns, functions and their parameter etc. With the buttons SQL for adding, update and both you can generate SQL statements for the creation of the descriptions in your database. Use the button both if you are not sure if a description is already present as it will generate a SQL statement working with existing and missing descriptions (see below).

The button  Fill Cache  fills the table CacheDescription where all descriptions are collected for easy access.

 

Log table and trigger

In the Log table and trigger section (see below) click on the List tables button to see all tables within the database. The Table section shows the basic definitions of a selected table. If columns for logging the date and responsible user for inserting and updating the data are missing, you can use the Attach ... button to attach these columns to the table. Furthermore you may add a RowGUID to the table as e.g. a preparation for a replication.

In the Log table section (see below) you can create a logging table for the selected table in a format as used within the Diversity Workbench. Click on the Show SQL ... button to show the SQL-statement that will create the logging table. If an old logging table should be kept, choose the Keep old log table option. If your table should support the version setting from a main table, choose the Add the column LogVersion option. To finally create the logging table click on the Create LogTable ... button.

The triggers for insert, update and delete are created in the according sections (see below). If an old trigger exists, its definition will be shown in the upper part of the window. Click on the Show SQL button to see the definition of the trigger according to the current definition of the table in a format as used in the Diversity Workbench. If a trigger should set the version in a main table, which the current table is related to, choose the Add version setting to trigger option. To enable this option you must select the version table first. To finally create the trigger click on the Create trigger button. The update and delete triggers will transfer the original version of the data into the logging tables as defined above, where you can inspect the history of the data sets.

If so far no procedure for setting the version in a main table is defined, you can create this procedure in the last section. Click on the Show SQL button to see the definition and on the Create Procedure button to create the procedure (see below).

 

Preparation for replication

If you want to use replication within you module, the tables need certain columns and a log table. These preparations can be performed by a script, generated in the section Replication (see below). Select the tables you want to include in the process and create the script. This script can than be included in an update of the database. Please ensure that these changes are only be done by expert staff.

 

Clear logtables

If for any reason you want to clear the log tables of the database, this can be done in the Clear log tab as shown below. Click on the List tables button to list the log tables. Then select those that should be cleared and click on the Clear log of selected tables button (see below). Please keep in mind that any restoration of data from the log is only possible as long as the data can be retrieved from the log.

 

Data protection

To implement the General Data Protection Regulation of the European Union several steps have to be performed in a database:

  • Generate a skript using this tool (see below) to convert all tables and insert objects according to the requirements:
    • Add columns ID, PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Grant update to PrivacyConsent and PrivacyConsentDate in table UserProxy
    • Create update trigger for UserProxy setting the PrivacyConsentDate
    • Create the function providing the ID of the user from UserProxy
    • Create the function providing the name of the user from UserProxy
    • Create the function PrivacyConsentInfo providing common information
    • For every table:
      • Insert users from a table into UserProxy (if missing so far)
      • Insert users from the corresponding log table into UserProxy (if missing so far)
      • Change the constraints for the logging columns (User_Name() → UserID())
      • Replace user name with ID in logging columns
      • Replace user name with ID in logging columns of the log table
      • Adapt description of the logging columns
  • Include the skript in an update of the database
  • Check the database for update triggers, functions using e.g. CURRENT_USER, USER_NAME, SUSER_SNAME etc. where user names must be replaced with their IDs. Create a script performing these tasks and include it into an update for the database
  • Adapt the client to the now changed informations (e.g. query for responsible etc.)

After these changes the only place where the name of a user is stored is the table UserProxy together with the ID. Removing the name (see below) will remove any information about the user leaving only a number linked to the information within depending data.

To generate a script for the objects and changes needed to implement the General Data Protection Regulation use the Data protection tab as shown below. The generated script will handle the standard objects (logging columns) but not any additional circumstances within the database. For these you need to inspect the database in detail and create a script to handle them on your own.

To set the website where detailed information about the handling of the General Data Protection Regulation within the DiversityWorkbench resp. the current database is provided, click on the button on the Info site tab. If unchanged, the default site for the DiversityWorkbench is set (see below).

If for any reason a user wants his name to be removed from the database, select the users name from the list as shown below and click on the  button (see below).

Mar 26, 2024

Documentation

Tools for the database documentation

These are the tools to describe the parts of the database and create documentations of the structure. To use these tools, choose Administation - Database - Documentation… from the menu. A window will open as shown below.

Click on the List objects button to list the objects of the database. With the  button resp. button you can select resp. deselect the types in the type selection and the object in the list.

Select the objects that should be listed all button resp. none button you can select resp. deselect the types in the type selection and the object in the list.

Select the objects that should be included in the documentation:

  • Tables
    • Trigger
  • Views
  • Roles
  • Functions and procedures
  • Context

… and exclude the objects that should not be included in the documentation:

  • Logging tables
  • Enumeration tables
  • Old versions of objects
  • System objects
  • Deprecated objects

 

The button Set default seletion will select all items in the list without:

  • System objects
  • Older version of an object indicated by the number at the last position
  • Logging tables
  • Enumeration tables
  • Objects with a description starting with e.g. outdated, deprecated, obsolete etc.
  • HTML options:
    • include index for objects
    • include NULL / NOT NULL
    • include relations and dependencies
    • include Description
    • exclude standard trigger
    • exclude definition
    • include permissions for *_Enum etc.
    • exclude obsolete columns
    • exclude columns starting or ending with the given strings
    • include list of tables that are depending on a table

The buttons Add to seletion and  Remove from seletion  will use the given strings with * as wildcard to add resp. remove items from the selection.

With the Context  option you can show or hide the context area for the html and media wiki tab as shown above.

HTML, MediaWiki, JSP-Wiki

To create a documentation choose among the provided options and click on the button Create ... documentation to create the documentation in one of the available formats (HTML, MediaWiki, JSP-Wiki). 

Mar 26, 2024

Subsections of Documentation

chm

With the chm tab you can generate index and keyword html files as well as markdown files for a website generated out of the hhc and hhk files of the HTML Help Workshop for the creation of chm manual as described in the video .

The button Generate keywords for HUGO creates a text file keywords.txt containing the keywords needed for the HUGO manual in a simple format. A pre- or postfix is set for every module to avoid conflicts. Use the Open button to open the file in a text editor.

Mar 26, 2024

HUGO

In the HUGO / HTML tab you generate markdown files according to HUGO and the relearn theme.

The conversion and adaptions are explained in a short tutorial: Video starten

For enumeration tables the content can be exported as explained in a short tutorial: Video starten

Installation of HUGO

Update des Themes

um das Theme auf die letzte Version zu bringen kann man den Befehl git submodule update --remote --merge themes/relearn verwenden

Übersetzung des Bestands an html

  • Übersetzung der *.html Seiten mit pandoc in *.md
  • Aufbau einer Ordnerstruktur die dem Index der chm Datei entspricht
  • Das Basisdokument der Ordner wird in die Ordner verschoben und in _index.md umbenannt
    • Dort im Frontmatter steht der Titel der im Menü angezeigt wird, e.g.:
      --- 
      title: Installation 
      ---  

Überarbeitung der md Dateien

  • Korrektur der Bildverweise
    • Ordner mit den Bildern in den Ordner static kopieren
    • von e.g. ![](img/...) in ![](img/...)
    • ACHTUNG - Case sensitiv. Namen müssen stimmen
    • Icons gegebenenfalls freistellen für Darkmode
  • Entfernung aller störenden Formatierungsangaben
  • Entfernung der Kopfzeile (Überschrift wird von HUGO automatisch erzeugt)
  • Korrektur der internen Verweise
    • ändern von [![](img/VideoDE.svg?class=inlineimg)](http://media.snsb.info/Tutorials/dwb/Editing/OeffentlicheKontaktdaten.webm) zu [![Video starten](img/VideoDE.svg?class=inlineimg)](http://media.snsb.info/Tutorials/dwb/Editing/OeffentlicheKontaktdaten.webm)
      • ansonsten wird das Bild gezeigt statt das Video zu starten
    • ändern von
      [Contact](Contact.htm)
      zu e.g.
      [Contact](editingdata/contact)
    • Wenn als Basisadresse in hugo.toml etwas angegeben wurde, e.g. baseURL = "http://www.diversityworkbench.de" dann muss diese auch für Verweise innerhalb der Files verwendet werden.
      • e.g. Bildverweise ![](img/IcoFeedback.gif?class=inlineimg)
      • Dateiverweise [Anmelden](database)
      • HUGO relearn erzeugt für Überschriften Anker die man ansteuern kann, e.g. kann man ### Table **AgentResource** über die Adresse database/database/#table-agentresource erreichen. Ein Index Eintrag dafür wäre e.g. [AgentResource](database/database/#table-agentresource). ACHTUNG - Case sensitiv: ### Table **AgentResource** wird in #table-agentresource übersetzt
    • Kommentare starten mit # ohne folgendes Leerzeichen

Frontmatter

You can change the frontmatter to a default using the documentation tool

  • Steht am Anfang der Datei und ist bei yaml durch --- oben und unten abgegrenzt, e.g.
    ---
    title: Login administration
    linktitle: Logins
    weight: 5
    menuPre: img/Documentation.svg
    alwaysopen: false
    ---
  • Seiten die noch in Entwicklung sind kann man mit draft: true im Frontmatter markieren. Diese werden dann nicht in die Ausgabe übernommen
  • Der Titel wird mit title: Login administration angegeben. Dieser erscheint dann auch in der Seite als Überschrift
  • Der Text im Menü kann abweichend definiert werden mit linktitle: Logins. Ansonsten erscheit der Titel im Menü
  • Die Reihenfolge im Menü kann mit weight: 5 angegeben werden. Ansonsten wird alphabetisch sortiert
  • Ein Logo kann man mit `menuPre: img/LinkedServer.svg
  • Wenn das Untermenue erst beim Anwählen geöffnet werden soll: alwaysopen: false

Template files

Starting with a Dash: If the first line of your Markdown file starts with a dash (-), Hugo might misinterpret it as a YAML delimiter, leading to an error

Bilder

You can adapt the images to a default using the documentation tool

  • Icons die e.g. in den Text integriert werden sollen, müssen folgedermassen eingebaut werden:
    • ![](img/Database.svg?class=inlineimg)
  • Die Bilder am Anfang der Seite werde wie folgt eingebaut:
    • ![](img/LinkedServer.svg?class=headerimg)

mit px wird das Bild mitgezoomt, bei vw bleibt es gleich gross

  • noch nicht zu svg konvertierte Bilder die im Fliesstest erscheinen sollen werden wie folgt eingebunden:
    • ![](img/Delete.svg?class=inlineimg)
  • sonstige Bilder mit
    • ![](img/Delete.svg)

mit der Angabe ...lightbox=false wird verhindert, dass ein Bild beim Anklicken mit der Maus geöffnet wird. Dies sollte bei Bildern die nicht nach svg konvertiert wurden und nicht im Fliesstext erscheinen nicht verwendet werden, damit der User bei kleinen Bildern diese in Originalauflösung betrachten kann. Unten 2 Beispiele

![](img/Delete.svg?class=inlineimg)

![](img/Delete.svg?class=inlineimg)

Für Bilder die aus der Quelle fontawesome kommen kann man hier suchen: fontawesome. Es funktionieren nicht alle die dort bereitstehen. Daher bitte testen!

Für Links innerhalb des Manuals kann man shortcodes verwenden. Dafür entweder auf den Namen der Datei oder auf Links von Überschriften (ab ##) verwenden. Diese müssen innerhalb des Manuals eindeutig sein. Für Header als erstes Zeichen # dann Überschrift und alles lower case und Leerzeichen werden durch - ersetzt. Beispiel:

## Main form of diversityexsiccatae

wird zu sofern es sich in der gleichen Datei befindet: 2 x { und % relref "#main-form-of-diversityexsiccatae" % und 2 x }

Für Links ausserhalb der Datei werden Verweise unter Einschluss des Dateinamens verwendet:

Verweis auf ein Kapitel innerhalb einer Datei 2 x { und % relref "diversityexsiccatae#main-form-of-diversityexsiccatae" % und 2 x }

bzw. nur auf die Datei 2 x { und % relref "diversityexsiccatae" % und 2 x }

Leerzeichen zwischen 2 x { und % und % und 2 x } entfernen

Von ausserhalb kann e.g. eine Überschrift mit https://www.diversityworkbench.demodules/diversityexsiccatae/index.html#main-form-of-diversityexsiccatae aufgerufen werden. Diese können direkt aus dem Manual kopiert werden.

  • hierfür das Logo in den Ordner static kopieren
  • im Ordner layouts einen Ordner partials anlegen
  • dort eine Datei logo.html anlegen
    • in dieser auf das Logo verweisen e.g.:
      <h4><b>DiversityAgents</b></h4>
      <img src="/DA_4D.svg">
  • in static - layouts - partials die Datei menu-footer.html anlegen und anpassen

favicon

Im Ordner static den Ordner images anlegen Datei favicon.ico in der Ordner static/images kopieren

Einschliessen von Dateien

Das Verzeichnis templates enthält Dateien die in andere Dateien über eine shortcode eingeschlossen werden können, e.g.:  2 x { und % include file="templates/template_workbench.md" % und 2 x } Diese Dateien dürfen kein frontmatter enthalten. Shortcodes müssen überprüft werden, da diese in der Regel nicht ausgewertet werden.

ER-Diagramm

dieses kann als Mermaid eingebaut werden, e.g.

 
graph LR;
    A[Agent] --> B[AgentContact<br/>Kontaktdaten der Agents]
    A --> C[AgentReference]
    A --> D[AgentIdentifier]
    A --> E[AgentResource]
    A --> F[AgentExternalID]
    G[AgentExternalDatabase] --> F[AgentExternalID]

soll das Diagramm zoombar sein wird die Version 5.23 des Themes benoetigt. Ausserdem kann der Parameter nur für die Shortcode Version angegeben werden, nicht für die Codefences:

2 x { und % mermaid align="center" zoom="true" % und 2 x }
... 
(remove space between 2 x { und  and < resp > and  und 2 x } in header and footer for correct code)
...
2 x { und % /mermaid % und 2 x }

Anpassung des Themes

  • es werden 2 eigene Themes bereitgestellt

    • im Verzeichnes
      • themes
        • relearn
          • static
            • css:
            • theme-dwb-dark.css
            • theme-dwb.css

    diese an DWB Anforderungen anpassen

    • in \themes\relearn\static\css\theme.css
      #body img.inline {
          display: inline !important;
          margin: 0 !important;
          vertical-align: middle;
          /* vertical-align: bottom; */
      }
    • in \themes\relearn\static\css\theme-dwb.css
      /*--MENU-HEADER-BG-color: rgba( 28, 144, 243, 1 );*/ /* Background color of menu header */
      --MENU-HEADER-BG-color: rgba( 220, 220, 220, 1 ); /* Background color of menu header */
      --MENU-HEADER-BORDER-color: rgba( 51, 161, 255, 1 ); /*Color of menu header border */
      

      –MENU-SEARCH-color: rgba( 255, 255, 255, 1 ); /* Color of search field text / /–MENU-SEARCH-BG-color: rgba( 22, 122, 208, 1 );/ / Search field background color (by default borders + icons) / –MENU-SEARCH-BG-color: rgba( 90, 90, 90, 1 ); / Search field background color (by default borders + icons) / /–MENU-SEARCH-BORDER-color: rgba( 51, 161, 255, 1 );/ / Override search field border color / –MENU-SEARCH-BORDER-color: rgba( 0, 0, 0, 1 ); / Override search field border color */

Konfiguration - in hugo.toml:

```native
baseURL = "http://www.diversityworkbench.de"
languageCode = "en-us"
title = "DiversityAgents"
theme = "relearn"

[outputs] home = ["HTML", "RSS", "SEARCH", "SEARCHPAGE"] section = ["HTML", "RSS", "PRINT"] page = ["HTML", "RSS", "PRINT"]

[params] themeVariant = [ "auto", "dwb", "dwb-dark" ]

</code></pre>
<h2 id="start-des-testservers">Start des Testservers:</h2>
<ul>
<li>mit einem Terminal in das Verzeichnis des Projekts wechseln</li>
<li>dort <code>hugo server </code> eingeben.</li>
<li>bei Problem mit Sonderzeichen: den Inhalt der Datei config.toml in hugo.toml kopieren und config.toml löschen (beide sollten wenn vorhanden UTF8 sein - werden manchmal als UTF16 angelegt - dieses dann nach UTF8 ändern)
<ul>
<li>Error: &ldquo;&hellip;\diversityworkbench\hugo.toml:1:1&rdquo;: unmarshal failed: toml: invalid character at start of key: ÿ</li>
</ul>
</li>
<li>Im Browser an die angegebene Adresse navigieren, e.g. <code>localhost:1313</code></li>
<li>Wenn als Basisadresse in hugo.toml etwas angegeben wurde, e.g. <code>baseURL = &quot;http://www.diversityworkbench.de&quot;</code> dann muss die passende Adresse eingeben werden also e.g. <code>localhost:1313</code></li>
</ul>
Mar 26, 2024

MediaWiki

With the MediaWiki tab you can generate markdown files according to MediaWiki.

Mar 26, 2024

License

This manual is copyrighted work licensed under a Creative Commons License.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

 

For information about the license of the client software choose Help, Info…

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License (GPL) for more details.

Mar 26, 2024

Data Access

Access to the data

To get access to the data, you have to fulfill several requirements. In DiversityCollection, you must be a member of one of the user groups. You can only access data, which is listed in the projects you have access to. For external users data may be blocked by entries in the data withholding reasons or due to a data embargo.

   

May 3, 2024

Subsections of Access

Login Administration

To administrate the logins on the database server, their permissions and roles respectively as well as access to projects choose Administration - Database - Logins ... from the menu. A window will open as shown below.

To set the website where information about details concerning the General Data Protection Regulation are shown, click on the button.   

To see the current activity on the server click on the button. A window as shown below will open listing all user related processes on the server.

To administrate the  linked servers, click on the button.   

To send a feedback click on the button.   

 

Statistics

To see the activity of a login click on the button. A window will open as shown below listing all databases and tables together with the time span (From - To) and the number of data sets where any activity of the current login has been found.

 

Creation of login

To create a new login click on the button. A window will open as shown below. A login that should be able to create new logins must to be a System administrator.

Here you can enter the name of the new login, the password and the information about the user which will be stored in a DiversityAgents database. You may either create a new entry in this database or select an existing one: Click on the button to search for a name in the database (see below).

 

Copy a login

To copy a login including all permissions etc. into a new login, select the original login in the list and click on the button.

 

Edit a login

To edit the access for a login on the server select the login in the list. If a login should be disabled , uncheck the enabled checkbox (see below).

All databases on the server will be listed with the current database showing a yellow background. The databases where the login has [no access] will be listed in [gray] while the databases accessible for a login are black.

 

Access of a login to a database

To allow the access to a database select the database from the list and choose database as shown below.

The state and date of the privacy consent according to the General Data Protection Regulation is shown in dependence of the selected database.

Roles of a login in a database

Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

As a database owner you can edit the permissions and role memberships with the and buttons. Please keep in mind that any change of the permissions may cause serious troubles and should only be used for testing and bug fixing. The final setting of the permissions should be performed by a proper update script of the database. For every action you will get the code that is to be included in an update script (see below).

 

Projects for a login in a database

Depending on the database you can edit the list of projects accessible for a login (see below). Projects are related to the module DiversityProjects. To get additional information about a project select it in the list and click on the button. 

Starting with database version 02.05.35 next to the projects with full access, a second list provides projects with [Read Only] access (see image below). Use the and buttons to move projects between Accessible and Read Only. If a project is set on [Read Only] a user can still add annotations. Starting with version 4.3.219 a project as a whole can be locked with the restriction of access to read only. For more details see chapter Project administration.

To load additional projects click on the Load projects button. A window will open as shown below. Projects already in the database will be listed in green, missing projects in red (see below). Check all projects you need in your database and click the Start download button.

To see an overview of the users within a project select one of the project in either list and click on the corresponding button . A window as shown below will open listing all users and their roles with access to the selected project.

To add or remove a role for a login, select the corresponding field and choose or from the context menu (see below).

 

Settings of a login in a database

Depending on the database you can edit the settings of a login as shown below.

If you wish to use settings already defined for another login, click on the Search template button. A window (see below) will open where you can choose among the settings defined for logins in the database.

 

Overview for a login

If you want to see an overview of all permissions and project for a login, click on the button. A window as shown below will open. It lists all modules and their databases, the roles, accessible projects and read only projects for a login. 

To copy the permissions and projects of the current login to another login, select the login where the settings should be copied to from the list at the base of the window and click on the button to copy the settings for all databases or the button to copy the settings of the selected database into this login. 

 

Overview for a database

If you see an overview of all user and roles in a database, click on the button. A window a shown below will open. It lists all user, roles and projects in the database. 

To remove a user, select it in the list and click on the button. 

 

Correction of logins

If you select one of the databases, at the base a button may appear. This indicates that there are windows logins listed where the name of the login does not match the logins of the server. This may happen if e.g. a database was moved from one server to another. To correct this, click on the button. A list of deviating logins will be shown, that can be corrected automatically.

If logins with the same name but different server are found, one of them has to be deleted to make the correction possible. You will get a list where you can select those that should be removed.

Select the duplicate logins that should be removed and click OK.

To find users within the database that have no valid login, click on the button. A window as shown below will open, listing the users without a login. Select those that should be removed and click OK. This will include a removal from the collection managers.

 

May 3, 2024

Security

A user may be in several groups with diverse rights in the database. Here certain higher groups have all rights of lower groups in addition to special rights for the higher group, e.g. the group User may only read data of certain tables while Typist has the rights of User and additionally may edit the data in certain tables - see overview below.

Summarized overview of some of the groups and their permissions as an example for the module DiversityCollection

Role Permissions in addition to lower role and user group respectively Included rights
Administrator Delete data, edit user permissions DataManager
CollectionManager Administration of collections, handling loans etc. StorageManager
DataManager Delete data, edit image descripton templates Editor
Editor Create new entries and delete details (not entire data sets) Typist
Requester Has the right to place requests for specimen
StorageManager Administration of stored parts, handling loans etc. User
Typist Edit data User
User See the data of the data tables, add annotations

To place a user in one of the groups, select Administration - Database - Logins... from the menu. In the window that will open select a login and a database. The roles available in the selected database will be listed as shown below. Use the > and < buttons to add or remove roles for the login in the database (see below).

To see the detailed permissions of a role, select it in the list of [Available] roles and click on the button. A window as shown below will open listing all objects in the database the role has permissions for (see below).

 

If you are an Administrator you may add a user to one of these groups.

Any user may have access to several projects.

May 3, 2024

Project access for user

The accessibility of projects for users can have 4 different states:

  • No access: The current user has no access to the project
  • Accessible: The current user has access to the project
  • [Read only]: The current user has read only access to the project
  • [Locked]: The project is locked. Any user can either none or read only access to the project

To allow the current user access projects use the [ > ] button for the selected project resp. the [ >> ] button for all projects. To revoke access for the current user use the [ < ]  button for the selected project resp. the [ << ] button for all projects. To change the access for a project to read only use the button and the button to remove a project from the read only list.

 

 

Locking of a project

To lock a selected project use the button. For all users the project will be removed from the accessible or read only list and transferred to the locked list. This is only allowed for a database owner (dbo). Please make sure that you really want to lock a project. Any dataset related to this project will be set to read only for all users. For an introduction, please see the a short tutorial Video starten.

To remove the locked state of a project, select the project in the No access list and click on the  button. The selected project will be moved from the locked list into the read only list for those users that had access to the project.

 

Retrieval of projects from DiversityProjects

Details of the projects within the DiversityWorkbench are stored in the database DiversityProjects. To access further information on a project click on the  button. To edit details in projects you require the application DiversityProjects.exe in your application directory and access to the database DiversityProjects. To synchronize the projects listed in DiversityProjects you may use the synchronize function in the user administration window as shown below. If DiversityProjects is not available, you may create a new project by clicking the button. If DiversityProjects is available, use the synchronize function .

     

Mar 26, 2024

Update

Update of database and client

If either the database or the client needs to be updated, the menu will show an additional entry: Update.

Database update

To update the database, choose Update Update database … from the menu. See chapter Database update for details.

Client update

To update the client, choose Update Update client … and download the lastest version of the client. ee chapter Update client for details.

Mar 26, 2024

Subsections of Update

Update Client

Replace the files and folders of your installation of DiversityCollection with the files you received by e-mail or downloaded from the DiversityWorkbench portal. The database will not be influenced by this replacement. After starting the new software you need to transfer the settings of the previous version. When you start the program and connect to a database, the program will check if it is compatible with the database or if the database needs an update. In any of these cases an update entry in the menu will appear. If a new version of the client is available, this menu will contain an update client … entry. Click on it to open the webpage where you may download the client as shown below.

 

Mar 26, 2024

Update Database

Update database to current version

If you are the owner of the database (Database role = dbo) and the database needs to be updated, the menu will contain an update database … entry. Select this entry to open a window as shown below to run the provided update scripts, delivered with the client software. These scripts need to run consecutively, so e.g. to update from version 2.5.1 to 2.5.4 you either have to run the script DiversityCollectionUpdate_020501_To_020504 or the scripts DiversityCollectionUpdate_020501_To_020502, DiversityCollectionUpdate_020502_To_020503 and DiversityCollectionUpdate_020503_To_020504. The program will guide you through these steps and check for the scripts. All you need to do is click the Start update button. 

Update of all databases on a server

If you are database owner and have a windows login to the database server (user=dbo), you have the option to update all DiversityCollection databases on this server by starting the application with command line parameters. Open a command line window, navigate to the program directory and start DiversityCollection with the keyword “UpdateDatebase”, the server name (or IP address) and the port number:

DiversityCollection.exe UpdateDatabase 127.0.0.1 5432

The program will connect to the server and update all available databases to the current version. If you want to exclude dedicated databases from update, create a text file named “ExcludeDb.txt” that contains the excluded database names - each name in a separate line - and locate it in the resources directory. The update will be done in the background without opening a program window. When the update processing is finished, an overview of the performed actions will be written into the protocol file “Updatereport.log” in directory resources/Updates.

Mar 26, 2024

Errorlog

If any error messages show up while working with the application, you can find further details concerning the part of the application where the error occurred and the parameters involved in the file e.g. DiversityCollectionError.log in the Module DiversityCollection located in your resources directory.

To open the errorlog, choose Help - ErrorLog from the menu. A window will open showing the content of the errolog. By default the errorlog will be reset at program start. You can keep the errorlog if needed by chossing Help - Errorlog - Keep error log from the menu. A button will appear that allows you to clear the error log manually: Help - Clear ErrorLog.

Mar 26, 2024

Module connections

Connections between the modules of the Diversity Workbench

The DiversityWorkbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. DiversityAgents is referred by several modules. To scan for references from these modules on data in DiversityAgents choose Data - Scan modules - from the menu (see image below).

With these options the program will scan all sources of the selected module as listed in the connections for references to the current agent. After selecting an agent in the tree, the sources of the selected modules together with the linked data will be listed as shown below.

Select a link to see a summary of the linked data (see below).

To get further information about an item click on the button. If so far the path to the respective application has not been set, you will get a corresponding message (see below).

Click on the button to set the path to the application (see below).

By default the path to the application is C:\Program Files (x86)\DiversityWorkbench\Diversity...\Diversity.…exe as shown.

Mar 26, 2024

Resources

The resources directory is set via the menu (Administration - Resources).

There are 3 possibilities for the resources directory:

  • Select any directory you have read/write access (User defined)
  • Select the "Home" directory of the user
  • Select the "My Documents" directory of the user

The default is set to Home. This directory will contain all files the user needs access to (see image below as an example for the module DiversityAgents).

Certain directories are hidden (Query) and are handled by the software i.e. the content should not be changed by the user. The other folders are generated by the software if missing, e.g. Export for any exports (see below).

Optional copy

By default all files the software needs from the application directory will be copied into the selected resources directory of the user. You can change this behaviour to one of the options listed below:

  • Copy files at program start
  • Add missing files at program start
  • Do not copy

With the next start of the program the software will act according to the selected behaviour. If you change from the Do not copy option to one of the other options the software will act at once according to the new option and e.g. copy missing directories and files into the user directory.

Mar 26, 2024

Diversity Sampling Plots

Scope within the Workbench

DiversitySamplingPlots is part of the database framework Diversity Workbench. Within this framework the application DiversitySamplingPlots is confined to the display of sampling plots in geographic areas. Any module within the Diversity Workbench is focused on a specific data domain. DiversitySamplingPlots keeps only data regarding sampling plots. Data of other realms like e.g. taxonomy are handled in separate modules.

DiversitySamplingPlots is based on Microsoft SQL-Server 20016 or later and the .Net Framework, Version 4.8.

For licence and copyright see the licence section.

Diversity Workbench modules

Jan 23, 2025

Subsections of Sampling plots

Diversity Sampling Plots

Download

Upcoming version

4.5.2

SQL Server 2016

For this version you need SQL Server 2016 or higher

  • New table JsonCache containing the data related to a plot as JSON. In the menu accessible via Administration → Json cache … or in the header click on the Show JsonCache button to see the json cache for the current plot.
  • Inclusion of ExternalID for comparision in maintenance for links to DiversityScientificTerms

Current version

4.5.1 (2023-08-25)

Download

  • Inclusion of maintenance for links to DiversityScientificTerms Video starten
  • Inclusion of hierarchy of location properties
  • Show or hide query
  • Mainform shown as single dialog form

Previous versions

4.5 (2023-05-09)

  • Bugfixes in Workbench.dll
  • Bugfix for linked specimen and images from DiversityCollection

4.4.11 (2023-04-21)

  • Several bugfixes getting properties from databases
  • Improvements in error logging in WorkbenchUnit
  • Linked specimen and images from DiversityCollection Video starten
  • webBrowser replaced in:
    • UserControlGeography
    • UserControlGIS
  • Query
    • Many order columns enabled
    • Additional columns:
      • Plot type
      • Country
      • Property
      • Locality

Database updates

  • 01.00.37: ViewLocality for query; SamplingPlotListForCurrentProject - add columns PlotType and CountryCache; ViewSamplingPlotListForCurrentProject - adding missing columns PlotType and CountryCache; Missing View ViewDiversityWorkbenchModule for linked server; Missing Grants; Missing Descriptions;

4.4.9

  • Transfer of selected projects
  • Bugfix hierarchy query
  • Bugfix LookupTable.cs
  • Menue - Transfer to project added

4.4.10

  • Table editors for:
    • Plot
    • Localisation
    • Site
  • Spreadsheet for Plot

 

Diversity Sampling Plots

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Aug 9, 2024

Diversity Sampling Plots

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.

Diversity Sampling Plots

Menu

Overview of the menu in DiversitySamplingPlots:

  • Connection

    • Database    Database … Choose one of the databases available on the server. Only those databases will be listed to which the user has access
    •    Module connections … Edit the connections to the other modules within the Diversity Workbench.
    •     Transfer previous settings Transfer the settings for IP-Address and port of the server, name of the database, login etc. of a previous version of the client to the current version.
    •     Quit Quit the application and stop all processes started by the application
  • Data

    •   Backup database … Creating a backup of the currently connected database
    •   Import
      •   Wizard Import data from tab-separated text files
      •   Sampling plot … Import data into SamplingPlots database …
    •   Replication Synchronise the content of 2 databases
      •   Add publisher … Define a publishing database
      •   Database on Server List entry of an added publisher
      •   Download … Download data from the data provider and server respectively in your local database
      •   Merge … Merge data between the data provider and server respectively and your local database
      •   Upload … Upload data from your local database to the replication provider and server respectively
      •   Remove … Remove the replication publisher from the list
      •   Clean database … Clean your local database
  • Administration

    •   Projects … Administration of the projects
    •   Database … Administration of the database
      •   Logins … Administration of the users and their permissions in the database
      •   Rename database … Rename the currently connected database
      •   Set published DB address … Set the base URL address of the currently connected database
      •   Documentation … Documentation of the structure of the database
      •   Maintenance … Maintenance of the database
      •   Database tools … Database tools
  • Update (Only visible, if a new version is available)

    •   Update database … Update to a new available database version
    •   Update client … Update to a new available client version
  • Help

    • Manual  Manual Opens the online manual
    • Feedback  Feedback … Opens a window for sending feedback
    • Feedback history  Feedback history… Opens a window for browsing former feedback
    • Info Show the version of the program and corresponding information

 

 

 

 

 

Apr 15, 2025

Tutorial

Tutorial - first steps

This tutorial will guide you through the first basic steps in DiversitySamplingPlots. After the installation, make sure, you have access to the database. To start the programm, double click on the DiversitySamplingPlots.exe in the directory where you copied the files of DiversitySamplingPlots. The main window will open.

Start page 

If you open this window for the first time, you have to connect to the database. Click on the button or choose Connection → Database… from the menu to open a window where you can enter your account information and choose the database (see image below, for further informations see databaseaccess).

Connect page 

After connecting to the server and choosing a database click on the OK button to return to the main form. As indicated by the  symbol in the right upper corner, you are now connected to the database. The tooltip of the button will show your current login informations.

Apr 15, 2025

Subsections of Tutorial

Tutorial Backlinks

Video starten

DiversityCollection

Message box To display dataset in the module DiversityCollection that are linked to the current plot, you can activate the query for these data in the menu Data - Scan modules - DiversityCollection (for the specimen) and Data - Scan modules - Images for the images. Please keep in mind that these backward query will increase the response time of the application.

 Specimen

Message box All specimen within the DiversityCollection databases as listed in the connections and linked to the current plot will be listed as shown below.

Message box

Images

To show the images within a certain DiversityCollection database, linked to a plot, in the Message box images tab use the Message box button to connect to the DiversityCollection database. Then all images will be listed as shown below.  

Message box

Use the link beneath the image to show the image in a separate window. The EXIF tab contains the corresponding information of the image.

May 3, 2024

Tutorial Edit Plots

Tutorial - create or change plots

To create a new sampling plot click at the New icon of the tool bar. A Window will pop up and ask you to enter the identifier of the new plot.

New plot dialog

The new plot will be created and shown on the screen.

New plot window

Now you may edit the parameters and either add a geography of any kind using the GIS-Editor window or a certain point with WGS84 coordinates using the Localisation control.

For the usage of the GIS-Editor please see the Description in the second part of the help file. You may select an appropriate map style, navigate to your region of interrest by shiftig and zooming the map and create it as a background map by clicking the Add button. Then select Point, Line or Area mode and draw your geography on the background map. Add one or more geographies using the Add button. The geographies may be changed later on using the Editmode of the GIS-Editor. Finally save the geography to the database by clicking on the Save button of the GIS-Edit window ( not that of the Query toolbar!). A WGS84 localisation will be created automatically.

Plot geography

Alternatively you may create a WGS84 localisation using the New button in the Localisation tab below the GIS-Edit window. A dialog will pop up.

Plot geography

Select “Coord. WGS84” from the drop down list and then press the OK butten. The new localisation will be shown in the list of the Localisation tab.

Plot geography

Select the localisation in the list and click at the MaltaCross button. The coordinates window as known from other DiversityWorkbench modules will be shown.

Plot geography

Shift the map using the mouse to localise a certain coordinate point with the static cross in the center. Then press the OK button and the coordinate point will be shown in the WGS84 localisation tab.

Plot geography

Additionally an Altitude and a Named area localisation will be created automatically by calling the Geonames web service. Press the Save button of the Query toolbar to save the new localisation.

Apr 3, 2025

Tutorial Hierarchy

Tutorial - plot hierarchy

The plots may be hierarchical organised as a tree view. The location of the current plot within the hierarchy is displayed in the hierarchy window:

Message box

To add a new plot within the selected plot click on the Messagebox button.

To change to another plot within the hierarchy tree just select the plot in the tree view and click on the Message box button. The new plot will be displayed.

To set the superior plot for the current sampling plot click on the Message box button.

To remove the superior plot for the current sampling plot click on the Message box button.

Apr 3, 2025

Wizard Tutorial

Import wizard - tutorial

This tutorial demostrates the import of a small file into the database. The following data should be imported (the example file is included in the software):   At the end of this tutorial you will have imported several datasets and practiced most of the possibilities provided by the import wizard. The import is done in 2 steps to demonstrate the attachment functionallity of the wizard.

 Step1 - Import of the collection events

Choose Data → Import → Wizard Sampling plot … from the menu. A window as shown below will open. that will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choosed for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

 

Choosing the File

As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Than choose the Encoding of the file, e.g. Unicode. The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the First line contains the column definition this line will not be imported as well. If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data. Finally you can select a prepared Schema (see chapter Schema below) for the import.

 

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

Certain tables can be imported in parallel. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import informations of logging columns like who created and changed the data, click on button in the header line. This will include a additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

 

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue backgroud (see below and chapter Table data).

 

Merging data

You can either import your data as new data or Merge them wih data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported, otherwise the data will be updated..

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

 

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you what actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive colums, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparision   = For all merge types other than insert columns for comparision with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for you test and than click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display you any errors that occurred as shown below. All datasets marked with a red backgroud, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets: INSERT, MERGE, UPDATE, No difference. Attach, No data. The colors of the table colums indicate whether a colums is decisive , a key column or an attachment column.  

 

Import

With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

Schedule for import of tab-separated text files into DiversityCollection
Target within DiversityCollection: Specimen
Schedule version: 1 Database version: 02.05.41
Lines: 2 - 3215 First line contains column definition: ?
Encoding: Unicode Language: de

Tables

CollectionSpecimen (CollectionSpecimen)
Parent: CollectionEvent
Merge handling: Insert

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
CollectionSpecimenID Database
AccessionNumber ? ? 0 File

IdentificationUnit_1 (IdentificationUnit)
Parent: CollectionSpecimen
Merge handling: Merge

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
CollectionSpecimenID Database
IdentificationUnitID Database
LastIdentificationCache ? 2 File
+ 3 File
+ 4 File
+ 5 File
TaxonomicGroup ? fish Interface

IdentificationUnitAnalysis_1_1 (IdentificationUnitAnalysis)
Parent: IdentificationUnit_1
Merge handling: Update

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
CollectionSpecimenID Database
IdentificationUnitID Database
AnalysisID 94 Interface
AnalysisNumber 1 Interface
AnalysisResult ? ? 39 File

 Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

 

 

Apr 4, 2025

Tutorial Localisation

Tutorial - localisation

Different kinds of localisation may be assigned to the sampling plots:

Message box

To add a new localisation for the selected plot click at the Messagebox button. Select the desired kind of localisation from the drop down list and press the OK button.

Message box

Fill up the data fields in the right part of the window. Each kind of localisation can only be assigned once. The list will contain the remaining choices.

Some buttons are provided depending on the selected localisation:
Message box: Open a GoogleMaps window to select the coordinates.
Message box: Convert coordinates to another coordinate system.
Message box: Open an appropriate Diversity Workbench remote module.

To remove a localisation, select it and click at the Messagebox button. The localisation will disappear from the list.

Finally press the Message box item in the Query toolbar to store the localisation for the plot in the database.

Apr 3, 2025

Tutorial Maps

Tutorial - show plots on the maps

The results list box displays the current set of plots found by the database query. To show a certain plot on the map, just click at the entry. Due to the coordinates of the place the map will be adjusted to this area and build up. There are 3 choices how to display the plot: Message box Browser, Message box GIS - View and Message box GIS - Edit:

Message box

Message box Browser uses a GoogleMaps window and pins to show the geography of the plot, if any. This is rather fast and interactive, but there is currently no support of areas or line strings and no possibility to display more than one plot.

Message box GIS - View uses the powerful GIS Editor tool of the Diversity Workbench, which can handle all kinds of geographies and display distribution maps of multiple plots. Depending on the internet connection and the map server it can take some seconds until the map tiles have been build. A message box will pop up to advice the user to wait, until the map is complete:

Message box

When all tiles of the background map are drawn, press OK to continue. Then the online map will be scanned and frozen and the plots should appear on the map:

Message box

Be aware that this mode is just a viewer of the GIS Editor’s geography objects. If multiple plots have been selected in the query list box, press the Message box reload button to display them. If you want a certain zoom level for the map, select the Use zoom level check box and adjust the desired level.

Message box GIS - Edit provides all controls and capabilities of the GIS Editor including editing the sample plot. Select a plot in the query list, then the map will be adjusted and a message box will pop up according to the GIS - View mode. Press OK to add the map and the plot to the sample list and display the geography:

Map with all places

Apr 3, 2025

Tutorial Properties

Tutorial - properties

Some kinds of properties may be assigned to the selected sampling plot.

Message box

To add a new property for the selected plot click at the Messagebox button. Select the desired kind of property from the drop down list and press OK.

Message box

Press the Message box button to open an appropriate Diversity Workbench remote module for the property data.

To remove a property, select it and click at the Messagebox button. The property will disappear from the list.

Finally press the Message box item in the Query toolbar to store the properties for the plot in the database.

Apr 3, 2025

Tutorial Query

Tutorial - query

To search for data in the database, use the query section in the left part of the window. To select the query conditions, click on the button in the top panel. A window as shown below will open.

 

With the Maximal number of results, you can limit the paket size that should be retrieved from the server. For a slow connection to the database server choose a low value (e.g. 100 as set by default).

Select the desired entries, e.g.:

 

Click OK to close the window. Your query conditions will look like the image below.

Within the query options you have several possibilities to specify your search restriction. Use the drop down button to change between the operators.

If the hierarchy operator Δ is selected, you may choose a desired hierarchy node by clicking at the drop down box on the right. Then a tree view of the current hierachy pops up, where you can select a given node with the mouse:

After all query conditions are set, click on the button to start the query. In the resultlist all plots will be displayed which matches your query and the selected maximal number of results.

Apr 3, 2025

Tutorial Query Results

Tutorial - query results

Pressing the Filter button will display all plots in the list box which matches the query conditions and the selected maximal number of results:

Query results

The kind of entries to be shown can be selected in the “order by” list box. They may be the plot identifiers, the plot descriptions or the plot hierarchy strings.

The data of the selected plot (identifier, description, ID, type, notes etc.) is displayed right of the query area. If a geography has been assigned, the place is shown on the map in the middle. The plot identifier is marked with yellow background, embedded in the hierarchy tree in the box below the map.

Query results

Apr 3, 2025

Tutorial Resources

Tutorial - resources

Resources (e.g. pictures) may be assigned to the selected sampling plot.

Message box

To add a new resource click at the Message box button. A browser will open where you can select and add the desired file.

Press the Message box button to open the DiversityAgents remote module, where you may select the responsible for the resource data. Annotations may be entered in the Notes field.

To remove a resource, select it and click at the Messagebox button. The resource will disappear from the list.

Finally press the Message box item in the Query toolbar to store the resource settings for the plot in the database.

Apr 3, 2025

Diversity Sampling Plots

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many colunns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Apr 15, 2025

Diversity Sampling Plots

Editing the data

For an introduction see the Tutorial

Apr 15, 2025

Subsections of Editing

Diversity Sampling Plots

Projects

Every plot can be assigned to any number of projects. To assign a plot to a project click on the  button. To remove it from a project, select the project from the list and click on the  button.

 

If there are projects, to which you have no access to, these will be listed in a separate list at the top as shown below.

 

Details upon the projects within the Diversity Workbench are stored in the database DiversityProjects. To edit the projects you need the application DiversityProjects.exe and access to the database DiversityProjects. If DiversityProjects is not available you can create a new project with the Administration -  Projects … button.

 

Apr 3, 2025

Diversity Sampling Plots

Import Export

Apr 15, 2025

Diversity Sampling Plots

Fequently Asked Questions

  • Common
    • How to link to data in DiversityCollection
      • see chapter Verknüpfte Datensätze und Bilder aus DiversityCollection and the video Video starten
        (Beispiel mit verknüpften Daten in DiversityCollection, Detaildarstellung von Datensatz, Bilder in DiversityCollection, Auswahl der Datenbank, mit Organismus verknüpfte Bilder zeigt zusätzlich Name des Taxon, Bild in separater Ansicht).
  • Wartung
    • How to link to site properties from DST
      • see chapter Standorteigenschaften verknüpfen
      • and the video Video starten
        (Vorstellung der Beispieldaten in DSP und DST. Bearbeitung nicht verknüpfter Daten. Erläuterung der Optionen. Suche nach Daten mit übereinstimmenden Werten. Ansicht eines Einzeldatensatzes zur Kontrolle. Aktualisierung der Daten mittels Update. Neuabruf der Daten. Kontrolle im Hauptformular. Änderung der Hierarchie mittels Maintenance. Aufruf bereits verknüpfter Daten. Update der Hierarchie und Kontrolle im Hauptformular).

 

Diversity Sampling Plots

General

Apr 15, 2025

Subsections of General

Diversity Sampling Plots

License

This manual is copyrighted work licensed under a Creative Commons License.

All material in this manual is the property of the contributing authors and fully copyrighted. By choosing this way of publication, the contributing authors have agreed to license the work under a Creative Commons License permitting reproduction, distribution, and derivative works, requiring attribution, notice, and share-alike, and prohibiting commercial use.

For information about the license of the client software choose Help -> Info…

The client software is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation.

The client software is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License (GPL) for more details.

Jan 23, 2025

Diversity Sampling Plots

Internals

For users that need more detailed information about the software including database design etc.

Apr 15, 2025

Subsections of Internals

Diversity Sampling Plots

Maintenance

To synchronize the entries with the module ScientificTerms choose Administration → Database → Maintenance from the menu. A window will open as shown below. On the tab page Synchonizing, you can synchronize the content in DiversitySamplingPlots with the linked resources or search for new links via text.

Linked data

To synchonize the content for linked data select the database, the project, the table and the target for which the entries should be synchronized. There are 2 targets for the synchronization: The term itself and the hierarchy. There is 1 table which may contain links to DiversityScientificTerms: 

Site properties Video starten

To synchronize linked data start the query click on the Search for differences button. Terms with differing content will be listed as shown below.

To include the hierarchy in the comparision, check the Compare hierarchy option as well if the hierarchy derived from [DiversityScientificTerms ]should be from the option Top→ Detail or Detail → Top . As shown below 2 more columns will be included, containing the hierarchies in DiversitySamplingPlots and DiversityScientificTerms. 

To establish new connections for terms corresponding to terms in DiversityScientificTerms (see below) click on the Search for identical terms button. All matching terms will be listed. For comparision you may use the text (= default) or the external ID of the term.

As with the query for linked data, you may include the hierarchy. In addition there are two options to restrict the search: Restrict to terms like ... and Restrict to max. results ... . The option Include accession number will split the data according to the specimen as shown below. With this option set, you can inspect the content of single specimen in the list using the button (see below).

In the result list you can select the data that should be included in the update in the first column (OK ) by de/selection of single lines or with the buttons Select all resp. Select none. To update the database click on the [Start update] button.

Jul 22, 2024

Diversity Sampling Plots

Database

The database for DiversitySamplingPlots is based on Microsoft SQL-Server 2014 or higher.

Organisation of the data

The central table of the database is SamplingPlot. The image below shows the main tables of the database.

Further details: tables, views, …

Jul 22, 2024

Subsections of Database

Diversity Sampling Plots

TABLES, VIEWS, FUNCTIONS, PROCEDURES, ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES


Table LocalisationSystem

The geographic localisation systems, e.g. coordinates

Column Data type Description Nullable Relation
LocalisationSystemID int Unique ID for the localisation system (= Primary key) NO -
LocalisationSystemParentID int LocalisationSystemID of the superior LocalisationSystem YES Refers to table LocalisationSystem
LocalisationSystemName nvarchar (100) Name of the system used for the determination of the place of the collection, e. g. Gauss-Krüger, MTB, GIS NO -
DefaultAccuracyOfLocalisation nvarchar (50) The default for the accuracy of values that can be reached with this method YES -
DefaultMeasurementUnit nvarchar (50) The default measurement unit for the localisation system, e.g. m, geograpic coordinates YES -
ParsingMethodName nvarchar (50) Internal value, specifying a programming method used for parsing text in fields Location1/Location2 in table SamplingPlotLocalisation YES -
DisplayText nvarchar (50) Short abbreviated description of the localisation system as displayed in the user interface YES -
DisplayEnable bit Specifies if this item is enabled to be used within the database. LocalisationSystems can be disabled to avoid seeing them, but to keep the definition for the future. YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Description nvarchar (255) Description of the localisation method YES -
DisplayTextLocation1 nvarchar (50) Short abbreviated description of the attribute Location1 in the table CollectionGeography as displayed in the user interface YES -
DescriptionLocation1 nvarchar (255) Description of the attribute Location1 in the table CollectionGeography as displayed in the user interface YES -
DisplayTextLocation2 nvarchar (50) Short abbreviated description of the attribute Location2 in the table CollectionGeography as displayed in the user interface YES -
DescriptionLocation2 nvarchar (255) Description of the attribute Location2 in the table CollectionGeography as displayed in the user interface YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -
LogCreatedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogCreatedWhen datetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen datetime Date and time when the data were last updated.Default value: getdate() YES -

Table ProjectUser

The projects a user has access to

Column Data type Description Nullable Relation
LoginName nvarchar (50) The login of the user NO -
ProjectID int The ID of the project the user has access to NO -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Table Property

Properties of the site of the sampling plot as stored in DiversityScientificTerms

Column Data type Description Nullable Relation
PropertyID int The ID of the sampling property, Primary key NO -
PropertyParentID int LocalisationSystemID of the superior LocalisationSystem YES Refers to table Property
PropertyName nvarchar (100) Name of the system used for the determination of the place of the collection, e. g. Gauss-Krüger, MTB, GIS NO -
DefaultAccuracyOfProperty nvarchar (50) The default for the accuracy of values that can be reached with this method YES -
DefaultMeasurementUnit nvarchar (50) The default measurement unit for measured properties YES -
ParsingMethodName nvarchar (50) Internal value, specifying a programming method used for parsing text in fields Location1/Location2 in table CollectionLocalisation NO -
DisplayText nvarchar (50) Short abbreviated description of the localisation system as displayed in the user interface YES -
DisplayEnabled bit Specifies if this item is enabled to be used within the database. LocalisationSystems can be disabled to avoid seeing them, but to keep the definition for the future. YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Description nvarchar (255) Description of the localisation method YES -
LogCreatedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogCreatedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -
PropertyURI varchar (1000) The link to the entry in a DiversityScientificTerms database YES -

Table ReplicationPublisher

For data replication - the links to publishers

Column Data type Description Nullable Relation
DatabaseName varchar (255) The name of the publishing database NO -
Server varchar (255) The name or address of the server where the publishing database is located NO -
Port smallint The port used by the server YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: user_name() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: user_name() YES -

Table SamplingPlot

A sampling plot with its geographical position and geometry

Column Data type Description Nullable Relation
PlotID int The ID of the sampling plot, Primary key NO -
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key YES Refers to table SamplingPlot
PlotIdentifier nvarchar (500) The identifier or name of the plot NO -
PlotGeography_Cache geography The cached geography of the plot as geographical entry, e.g. as a polygon derived from the geography in table SamplingPlotPoints YES -
PlotGeometry_Cache geometry (MAX) The cached geometry of a sampling plot, e.g. as a polygon derived from the geometry in table SamplingPlotPoints YES -
PlotDescription nvarchar (MAX) A short text, describing the sampling plot YES -
InternalNotes nvarchar (MAX) Internal notes regarding the sampling plot, not published on the web YES -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
PlotType nvarchar (50) The type of the plot, e.g. trap YES -
CountryCache nvarchar (50) The country where the collection sampling plot is located. Cached value derived from an entry in SamplingPlotLocalisation YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Table SamplingPlotLocalisation

The geographic localisation of a sampling plot

Column Data type Description Nullable Relation
PlotID int Refers to the ID of SamplingPlot (= Foreign key and part of primary key) NO Refers to table SamplingPlot
LocalisationSystemID int Refers to the ID of LocalisationSystem (= Foreign key and part of primary key) NO Refers to table LocalisationSystem
Location1 nvarchar (255) Either a named location selected from a thesaurus (e. g. ‘Germany, Bavaria, Kleindingharting’) or altitude range or other values (e. g. 100-200 m) YES -
Location2 nvarchar (255) Corresponding value to Location1 e.g. ID or URI of gazetteer or thesaurus YES -
LocationAccuracy nvarchar (50) The accuracy of the determination of this locality YES -
LocationNotes nvarchar (MAX) Notes on the location YES -
DeterminationDate smalldatetime Date of the determination of the geographical localisation YES -
DistanceToLocation varchar (50) Distance from the specified place to the real location of the sampling plot (m) YES -
DirectionToLocation varchar (50) Direction from the specified place to the real location of the sampling plot (Degrees rel. to north) YES -
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES -
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES -
Geography geography The geography of the localisation YES -
AverageAltitudeCache float Calculated altitude as parsed from the location fields YES -
AverageLatitudeCache float Calculated latitude as parsed from the location fields YES -
AverageLongitudeCache float Calculated longitude as parsed from the location fields YES -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • LocalisationSystem
  • SamplingPlot

trgInsSamplingPlotLocalisation


Table SamplingPlotProperty

Properties of the site of a sampling plot

Column Data type Description Nullable Relation
PlotID int The ID of the sampling plot, foreign key and part of primary key NO Refers to table SamplingPlot
PropertyID int ID of the property to which the sampling plot property belongs NO Refers to table Property
PropertyURI varchar (255) URI referring to an external datasource e.g. DiversityTerminology NO -
DisplayText nvarchar (255) The text for the property as shown e.g. in a user interface YES -
PropertyHierarchyCache nvarchar (MAX) A cached text of the complete name of the descriptor including superior categories if present YES -
PropertyValue nvarchar (255) The value of a captured feature e.g. temperature, pH, vegetation etc. If there is a range this is the lower or first value YES -
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES -
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES -
Notes nvarchar (MAX) Notes about the property of the colletion site. YES -
AverageValueCache float For numeric values - a cached average value according to the YES -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • Property
  • SamplingPlot

Table SamplingPlotResource

Resouces of the sampling plot, e.g. images

Column Data type Description Nullable Relation
PlotID int The ID of the sampling plot, foreign key and part of primary key NO Refers to table SamplingPlot
ResourceURI varchar (255) URI referring to the file or link of the resource NO -
ResponsibleName nvarchar (255) The name of the agent (person or organization) responsible for this entry. YES -
ResponsibleAgentURI varchar (255) URI of the person or organisation responsible for the data (see e.g. module DiversityAgents) YES -
Notes nvarchar (MAX) Notes about the resource. YES -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • SamplingPlot

Table SamplingProject

The projects to which a sampling plot is related

Column Data type Description Nullable Relation
PlotID int The ID of the sampling plot, foreign key and part of primary key NO Refers to table SamplingPlot
ProjectID int ID of the project to which the sampling plot belongs (Projects are defined in DiversityProjects) NO -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • SamplingPlot

VIEWS


View PlotID_UserAvailable

IDs of the plots a user has access to

Column Data type Description Nullable
PlotID int The ID of the sampling plot, Primary key NO

Depending on:

  • ProjectUser
  • SamplingPlot
  • SamplingProject

View ProjectList

The list of the projects a user has access to

Column Data type Description Nullable
Project nvarchar (50) The name or title of the project as shown in a user interface (Projects are defined in DiversityProjects) YES
ProjectID int ID of the project to which the specimen belongs (Projects are defined in DiversityProjects) NO

Depending on:

  • ProjectProxy
  • ProjectUser

View SamplingPlotGeoInfo

Geographical properties of a plot extracted from column PlotGeography_Cache including up to 4 hierarchy levels

Column Data type Description Nullable
Latitude float Latitude of the center of the plot YES
Longitude float Longitude of the center of the plot YES
Accuracy angle varchar (32) maximum angle between the center and the circumference as string YES
AccuracyAngle float maximum angle between the center and the circumference as numeric value YES
AreaM2 float Area in square meters YES
Area varchar (34) Area including unit YES
Geography nvarchar (MAX) Geography of the plot or a parent plot YES
CountryCache nvarchar (50) The country where the collection sampling plot is located. Cached value derived from an entry in SamplingPlotLocalisation YES
PlotID int The ID of the sampling plot, Primary key NO

Depending on:

  • SamplingPlot

View ViewBaseURL

Providing the BaseURL for linked servers

Column Data type Description Nullable
BaseURL varchar (255) Content of function BaseURL YES

Depending on:

  • BaseURL

View ViewDiversityWorkbenchModule

Provides the name of the DiversityWorkbench module as defined in function DiversityWorkbenchModule

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) The name of the DiversityWorkbench module YES

Depending on:

  • DiversityWorkbenchModule

View ViewLocality

Gazetteer data for query

Column Data type Description Nullable
PlotID int Refers to the ID of SamplingPlot (= Foreign key and part of primary key) NO
Locality nvarchar (255) Content of column Location1 YES

Depending on:

  • LocalisationSystem
  • SamplingPlotLocalisation

View ViewSamplingPlot

Providing the content of table SamplingPlot for linked servers with conversion of geography tables to text

Column Data type Description Nullable
PlotID int The ID of the sampling plot, Primary key NO
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key YES
PlotIdentifier nvarchar (500) The identifier or name of the plot NO
PlotGeography_Cache nvarchar (MAX) The cached geography of the plot as geographical entry, e.g. as a polygon derived from the geography in table SamplingPlotPoints YES
PlotGeometry_Cache nvarchar (MAX) The cached geometry of a sampling plot, e.g. as a polygon derived from the geometry in table SamplingPlotPoints YES
PlotDescription nvarchar (MAX) A short text, describing the sampling plot YES
InternalNotes nvarchar (MAX) Internal notes regarding the sampling plot, not published on the web YES
CountryCache nvarchar (50) The country where the collection sampling plot is located. Cached value derived from an entry in SamplingPlotLocalisation YES
PlotType nvarchar (50) The type of the plot, e.g. trap YES

Depending on:

  • SamplingPlot

View ViewSamplingPlotAllLocalisations

Providing the result of SamplingPlotAllLocalisations for linked servers

Column Data type Description Nullable
PlotID int The ID of the sampling plot, Primary key NO
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key YES
LocalisationSystemID int Unique ID for the localisation system (= Primary key) NO
Location1 nvarchar (255) Either a named location selected from a thesaurus (e. g. ‘Germany, Bavaria, Kleindingharting’) or altitude range or other values (e. g. 100-200 m) YES
Location2 nvarchar (255) Corresponding value to Location1 e.g. ID or URI of gazetteer or thesaurus YES
DisplayText nvarchar (255) Short abbreviated description of the localisation system as displayed in the user interface YES

Depending on:

  • SamplingPlotAllLocalisations

View ViewSamplingPlotGeoInfo

Providing the result of SamplingPlotGeoInfo for linked servers

Column Data type Description Nullable
Latitude float Latitude of the center of the plot YES
Longitude float Longitude of the center of the plot YES
Accuracy angle varchar (32) maximum angle between the center and the circumference as string YES
AccuracyAngle float maximum angle between the center and the circumference as numeric value YES
AreaM2 float Area in square meters YES
Area varchar (34) Area including unit YES
Geography nvarchar (MAX) Geography of the plot or a parent plot YES
CountryCache nvarchar (50) The country where the collection sampling plot is located. Cached value derived from an entry in SamplingPlotLocalisation YES
PlotID int The ID of the sampling plot, Primary key NO
URL varchar (285) URL as retrieved from BaseURL + PlotID YES

Depending on:

  • SamplingPlot
  • ViewBaseURL

View ViewSamplingPlotHierarchy5

Basic for for ViewSamplingPlotHierarchy

Column Data type Description Nullable
PlotID int The ID of the sampling plot, Primary key NO
DisplayText nvarchar (3015) - NO

Depending on:

  • SamplingPlot

View ViewSamplingPlotList

Providing the result of SamplingPlotList for linked servers

Column Data type Description Nullable
PlotID int The ID of the sampling plot, Primary key NO
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key YES
PlotIdentifier nvarchar (500) The identifier or name of the plot NO
PlotGeography_Cache nvarchar (MAX) The cached geography of the plot as geographical entry, e.g. as a polygon derived from the geography in table SamplingPlotPoints YES
PlotGeometry_Cache nvarchar (MAX) The cached geometry of a sampling plot, e.g. as a polygon derived from the geometry in table SamplingPlotPoints YES
PlotDescription nvarchar (MAX) A short text, describing the sampling plot YES
InternalNotes nvarchar (MAX) Internal notes regarding the sampling plot, not published on the web YES
DisplayText nvarchar (MAX) The combined Identifiers of the whole hierarchy related to a plot NO

Depending on:

  • SamplingPlotList

View ViewSamplingPlotListForCurrentProject

Providing the result of SamplingPlotListForCurrentProject for linked servers

Column Data type Description Nullable
PlotID int The ID of the sampling plot, Primary key NO
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key YES
PlotIdentifier nvarchar (500) The identifier or name of the plot NO
PlotGeography_Cache nvarchar (MAX) The cached geography of the plot as geographical entry, e.g. as a polygon derived from the geography in table SamplingPlotPoints YES
PlotGeometry_Cache nvarchar (MAX) The cached geometry of a sampling plot, e.g. as a polygon derived from the geometry in table SamplingPlotPoints YES
PlotDescription nvarchar (MAX) A short text, describing the sampling plot YES
InternalNotes nvarchar (MAX) Internal notes regarding the sampling plot, not published on the web YES
DisplayText nvarchar (MAX) The combined Identifiers of the whole hierarchy related to a plot NO
PlotType nvarchar (50) The type of the plot, e.g. trap YES
CountryCache nvarchar (50) The country where the collection sampling plot is located. Cached value derived from an entry in SamplingPlotLocalisation YES
ProjectID int The ID of the project the user has access to NO

Depending on:

  • SamplingPlotListForCurrentProject

View ViewTest

Column Data type Description Nullable
spid smallint - NO
ecid smallint - NO
status nchar (30) - NO
loginame nvarchar (128) - YES
hostname nchar (128) - NO
blk char (5) - YES
dbname nvarchar (128) - YES
cmd nchar (16) - NO
request_id int - NO

FUNCTIONS


Function BaseURL

Provides the basic address for accessing the database

DataType: varchar (255)


Function DefaultProjectID

The ID of the current project selected by a user or first project available

DataType: int

Depending on:

  • ProjectUser
  • UserProxy

Function DiversityWorkbenchModule

The name of the module within the DWB

DataType: nvarchar (50)


Function PrivacyConsentInfo

The website providing information concerning the privacy consent

DataType: varchar (900)


Function SamplingPlotAllLocalisations

Returns a table that lists all the localisations of a plot included those inherited from a parent plot

Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
LocalisationSystemID int Unique ID for the localisation system (= Primary key)
Location1 nvarchar (255) Either a named location selected from a thesaurus (e. g. ‘Germany, Bavaria, Kleindingharting’) or altitude range or other values (e. g. 100-200 m)
Location2 nvarchar (255) Corresponding value to Location1 e.g. ID or URI of gazetteer or thesaurus
DisplayText nvarchar (255) Short abbreviated description of the localisation system as displayed in the user interface

Depending on:

  • LocalisationSystem
  • SamplingPlot
  • SamplingPlotLocalisation

Function SamplingPlotAllProperties

Returns a table that lists all the properties of a plot included those inherited from a parent plot

Column DataType Description
PropertyID int ID of the property to which the sampling plot property belongs
PlotID int The ID of the sampling plot, Primary key
PropertyURI varchar (255) URI referring to an external datasource e.g. DiversityTerminology
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
DisplayText nvarchar (255) The text for the property as shown e.g. in a user interface
PropertyHierarchyCache nvarchar (MAX) A cached text of the complete name of the descriptor including superior categories if present

Depending on:

  • SamplingPlot
  • SamplingPlotProperty

Function SamplingPlotChildNodes

Returns a result set that lists all the items within a hierarchy starting at the topmost item related to the given item.

Parameter DataType Description
@ID int PlotID for which the children should be returned
Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
PlotIdentifier nvarchar (500) The identifier or name of the plot

Depending on:

  • SamplingPlot

Function SamplingPlotGeography

Returns a table that lists all plots togeher with the geography possibly derived from the parent plot.

Parameter DataType Description
@PlotIDs varchar (8000) List of comma separated PlotIDs for which the geography should be returned
Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
Geography geography (MAX) Content of column PlotGeography_Cache if available within the hierarchy

Depending on:

  • SamplingPlot

Function SamplingPlotHierarchy

Returns a table that lists all the plots related to the given plot

Parameter DataType Description
@PlotID int The ID of the sampling plot, Primary key
Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
PlotIdentifier nvarchar (500) The identifier or name of the plot

Depending on:

  • SamplingPlot
  • SamplingPlotChildNodes

Function SamplingPlotList

Returns a table that lists all the SamplingPlot items related to the given SamplingPlot.

Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
PlotIdentifier nvarchar (500) The identifier or name of the plot
PlotGeography_Cache geography (MAX) The cached geography of the plot as geographical entry, e.g. as a polygon derived from the geography in table SamplingPlotPoints
PlotGeometry_Cache geometry (MAX) The cached geometry of a sampling plot, e.g. as a polygon derived from the geometry in table SamplingPlotPoints
PlotDescription nvarchar (MAX) A short text, describing the sampling plot
InternalNotes nvarchar (MAX) Internal notes regarding the sampling plot, not published on the web
DisplayText nvarchar (MAX) The combined Identifiers of the whole hierarchy related to a plot

Depending on:

  • SamplingPlot

Function SamplingPlotListForCurrentProject

Returns a table that lists all the SamplingPlot items related to the given project.

Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
PlotIdentifier nvarchar (500) The identifier or name of the plot
PlotGeography_Cache geography (MAX) The cached geography of the plot as geographical entry, e.g. as a polygon derived from the geography in table SamplingPlotPoints
PlotGeometry_Cache geometry (MAX) The cached geometry of a sampling plot, e.g. as a polygon derived from the geometry in table SamplingPlotPoints
PlotDescription nvarchar (MAX) A short text, describing the sampling plot
InternalNotes nvarchar (MAX) Internal notes regarding the sampling plot, not published on the web
DisplayText nvarchar (MAX) The combined Identifiers of the whole hierarchy related to a plot
PlotType nvarchar (50) The type of the plot, e.g. trap
CountryCache nvarchar (50) The country where the collection sampling plot is located. Cached value derived from an entry in SamplingPlotLocalisation
ProjectID int The ID of the project the user has access to

Depending on:

  • DefaultProjectID
  • ProjectList
  • SamplingPlot
  • SamplingProject

Function SamplingPlotSuperiorNodes

Returns a table that lists all the plots related to the given plot

Parameter DataType Description
@PlotID int The ID of the sampling plot, Primary key
Column DataType Description
PlotID int The ID of the sampling plot, Primary key
PartOfPlotID int The ID of the plot of which the current plot is a part of, Foreign key
PlotIdentifier nvarchar (500) The identifier or name of the plot
PlotHierarchyCache nvarchar (4000) The combined Identifiers of the whole hierarchy related to a plot

Depending on:

  • SamplingPlot

Function UserID

ID of the User as stored in table UserProxy

DataType: int

Depending on:

  • UserProxy

Function UserName

Name of the User as stored in table UserProxy

DataType: nvarchar (50)

Parameter DataType Description
@ID varchar (10) ID of the user

Depending on:

  • UserProxy

Function Version

The version of the database

DataType: nvarchar (8)


Function VersionClient

The version of the client compatible with the database

DataType: nvarchar (11)


PROCEDURES


Procedure procGetSiteProperties

Depending on:

  • SamplingPlot
  • SamplingPlotProperty

Procedure procInsertSamplingPlotCopy

Creation of a copy of a dataset in table SamplingProject including the content in depending tables

Parameter DataType Description
@PlotID int The ID of the sampling plot, Primary key
@OriginalPlotID int The ID of the original plot
@PlotIdentifier nvarchar (50) reserved for future, not used in current version

Depending on:

  • SamplingPlot
  • SamplingPlotLocalisation
  • SamplingPlotProperty
  • SamplingPlotResource
  • SamplingProject

Procedure ProcSamplingPlotLocalisationAll

Depending on:

  • LocalisationSystem
  • SamplingPlot
  • SamplingPlotLocalisation

Procedure SetUserProjects

Create database user and assign training projects

Parameter DataType Description
@User varchar (50) database user to assign training projects for

Depending on:

  • UserProxy

ROLES

Content of cell Permission
Not granted
Name of other role Inherited from other role
Granted

Role DataManager

Permissions as Editor but with permission to delete data in table SamplingPlot

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LocalisationSystem Diversity Workbench User TABLE
LocalisationSystem_log TABLE
ProjectUser Diversity Workbench User TABLE
Property Diversity Workbench Editor TABLE
Property_log TABLE
ReplicationPublisher Diversity Workbench Editor TABLE
SamplingPlot Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlot_log TABLE
SamplingPlotLocalisation Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotLocalisation_log Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotProperty Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotProperty_log Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotResource Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotResource_log TABLE
SamplingProject Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingProject_log Diversity Workbench Editor Diversity Workbench Editor TABLE
PlotID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
SamplingPlotGeoInfo Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewLocality Diversity Workbench User VIEW
ViewSamplingPlot Diversity Workbench User VIEW
ViewSamplingPlotAllLocalisations Diversity Workbench User VIEW
ViewSamplingPlotGeoInfo Diversity Workbench User VIEW
ViewSamplingPlotHierarchy5 Diversity Workbench User VIEW
ViewSamplingPlotList Diversity Workbench User VIEW
ViewSamplingPlotListForCurrentProject Diversity Workbench User VIEW
ViewTest VIEW
BaseURL Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
SamplingPlotAllLocalisations Diversity Workbench User FUNCTION
SamplingPlotAllProperties Diversity Workbench Editor FUNCTION
SamplingPlotChildNodes Diversity Workbench User FUNCTION
SamplingPlotGeography Diversity Workbench User FUNCTION
SamplingPlotHierarchy Diversity Workbench User FUNCTION
SamplingPlotList Diversity Workbench User FUNCTION
SamplingPlotListForCurrentProject Diversity Workbench User FUNCTION
SamplingPlotSuperiorNodes Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
UserName Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procGetSiteProperties PROCEDURE
procInsertSamplingPlotCopy Diversity Workbench Editor PROCEDURE
ProcSamplingPlotLocalisationAll PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchEditor

Role DiversityWorkbenchAdministrator

Role with full permission to the content

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LocalisationSystem Diversity Workbench User TABLE
LocalisationSystem_log TABLE
ProjectUser TABLE
Property Diversity Workbench Editor TABLE
Property_log TABLE
ReplicationPublisher TABLE
SamplingPlot Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlot_log TABLE
SamplingPlotLocalisation Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotLocalisation_log Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotProperty Diversity Workbench Editor TABLE
SamplingPlotProperty_log Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingPlotResource Diversity Workbench Editor TABLE
SamplingPlotResource_log TABLE
SamplingProject Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SamplingProject_log Diversity Workbench Editor Diversity Workbench Editor TABLE
PlotID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
SamplingPlotGeoInfo Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewLocality Diversity Workbench User VIEW
ViewSamplingPlot Diversity Workbench User VIEW
ViewSamplingPlotAllLocalisations Diversity Workbench User VIEW
ViewSamplingPlotGeoInfo Diversity Workbench User VIEW
ViewSamplingPlotHierarchy5 Diversity Workbench User VIEW
ViewSamplingPlotList Diversity Workbench User VIEW
ViewSamplingPlotListForCurrentProject Diversity Workbench User VIEW
ViewTest VIEW
BaseURL Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
SamplingPlotAllLocalisations Diversity Workbench User FUNCTION
SamplingPlotAllProperties Diversity Workbench Editor FUNCTION
SamplingPlotChildNodes Diversity Workbench User FUNCTION
SamplingPlotGeography Diversity Workbench User FUNCTION
SamplingPlotHierarchy Diversity Workbench User FUNCTION
SamplingPlotList Diversity Workbench User FUNCTION
SamplingPlotListForCurrentProject Diversity Workbench User FUNCTION
SamplingPlotSuperiorNodes Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
UserName Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procGetSiteProperties PROCEDURE
procInsertSamplingPlotCopy Diversity Workbench Editor PROCEDURE
ProcSamplingPlotLocalisationAll PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchEditor

Role DiversityWorkbenchEditor

Role for editing the content

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LocalisationSystem Diversity Workbench User TABLE
LocalisationSystem_log TABLE
ProjectUser Diversity Workbench User TABLE
Property TABLE
Property_log TABLE
ReplicationPublisher TABLE
SamplingPlot TABLE
SamplingPlot_log TABLE
SamplingPlotLocalisation Diversity Workbench User TABLE
SamplingPlotLocalisation_log TABLE
SamplingPlotProperty TABLE
SamplingPlotProperty_log TABLE
SamplingPlotResource TABLE
SamplingPlotResource_log TABLE
SamplingProject Diversity Workbench User TABLE
SamplingProject_log TABLE
PlotID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
SamplingPlotGeoInfo Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewLocality Diversity Workbench User VIEW
ViewSamplingPlot Diversity Workbench User VIEW
ViewSamplingPlotAllLocalisations Diversity Workbench User VIEW
ViewSamplingPlotGeoInfo Diversity Workbench User VIEW
ViewSamplingPlotHierarchy5 Diversity Workbench User VIEW
ViewSamplingPlotList Diversity Workbench User VIEW
ViewSamplingPlotListForCurrentProject Diversity Workbench User VIEW
ViewTest VIEW
BaseURL Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
SamplingPlotAllLocalisations Diversity Workbench User FUNCTION
SamplingPlotAllProperties FUNCTION
SamplingPlotChildNodes Diversity Workbench User FUNCTION
SamplingPlotGeography Diversity Workbench User FUNCTION
SamplingPlotHierarchy Diversity Workbench User FUNCTION
SamplingPlotList Diversity Workbench User FUNCTION
SamplingPlotListForCurrentProject Diversity Workbench User FUNCTION
SamplingPlotSuperiorNodes Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
UserName Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procGetSiteProperties PROCEDURE
procInsertSamplingPlotCopy PROCEDURE
ProcSamplingPlotLocalisationAll PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchUser

Role DiversityWorkbenchUser

Role with read only access

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LocalisationSystem TABLE
LocalisationSystem_log TABLE
ProjectUser TABLE
Property TABLE
Property_log TABLE
ReplicationPublisher TABLE
SamplingPlot TABLE
SamplingPlot_log TABLE
SamplingPlotLocalisation TABLE
SamplingPlotLocalisation_log TABLE
SamplingPlotProperty TABLE
SamplingPlotProperty_log TABLE
SamplingPlotResource TABLE
SamplingPlotResource_log TABLE
SamplingProject TABLE
SamplingProject_log TABLE
PlotID_UserAvailable VIEW
ProjectList VIEW
SamplingPlotGeoInfo VIEW
ViewBaseURL VIEW
ViewDiversityWorkbenchModule VIEW
ViewLocality VIEW
ViewSamplingPlot VIEW
ViewSamplingPlotAllLocalisations VIEW
ViewSamplingPlotGeoInfo VIEW
ViewSamplingPlotHierarchy5 VIEW
ViewSamplingPlotList VIEW
ViewSamplingPlotListForCurrentProject VIEW
ViewTest VIEW
BaseURL FUNCTION
DefaultProjectID FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo FUNCTION
SamplingPlotAllLocalisations FUNCTION
SamplingPlotAllProperties FUNCTION
SamplingPlotChildNodes FUNCTION
SamplingPlotGeography FUNCTION
SamplingPlotHierarchy FUNCTION
SamplingPlotList FUNCTION
SamplingPlotListForCurrentProject FUNCTION
SamplingPlotSuperiorNodes FUNCTION
UserID FUNCTION
UserName FUNCTION
Version FUNCTION
VersionClient FUNCTION
procGetSiteProperties PROCEDURE
procInsertSamplingPlotCopy PROCEDURE
ProcSamplingPlotLocalisationAll PROCEDURE
SetUserProjects PROCEDURE
Jan 30, 2025

Diversity Sampling Plots

No-SQL Interface

JSON Cache

Databases of the modules provid a No-SQL interface where the data of the main table and the depending tables are merged as JSON.

Table JsonCache

Content of table JsonCache restricted to public available data

Column Data type Description Nullable Relation
ID int Unique ID for the Dataset, Primary key NO ID of the source
URI varchar (500) The URL as combination of BaseURL and ID NO BaseURL and ID of the source
DisplayText nvarchar (500) Representation in the interface NO Main table of the source
LogUpdatedWhen datetime Date and time when the data were last updated NO -
Data json Data related to the current dataset NO -

procFillJsonCache is started by an update trigger trgUpd… of the main table in the database

Interface in clients

All modules provide data via a cache table. In the header of the clients you can inspect the content of the JsonCache with a click on the button. For modules with a difference between local and public data, you can inspect the content of the public data with a click of the right mouse button.

Update

Apart of the update via the Trigger (see below) you can update the JsonCache via the update button underneath the button.

To update the JsonCache for the whole database select Administration - JsonCache… from the menu. a window as shown below will open where you can update the JsonCache for single datasets or the whole database.

Summary

graph TD;
    TaxonName[Main table in database] 
    trgUpdTaxonName[trgUpd.. of main table in database]
    TaxonName --> |Update in table| trgUpdTaxonName
    proc[Procedure procFillJsonCache setting the content in table JsonCache]
    trgUpdTaxonName --> proc
graph TD;    
    Mainform[Main form]
    ButtonShow[Button show JsonCache of current dataset]
    Mainform --> ButtonShow
    Left[Show Data]
    ButtonShow --> |Left click| Left
graph TD;    
    Mainform[Main form]
    Admin[Administration menu]
    Mainform --> Admin
    Cache[JsonCache...]
    Admin --> Cache
    Adminform[Administration form]
    Cache --> Adminform
    AdminUpdateSingle[Update single dataset]
    Adminform --> AdminUpdateSingle
    AdminUpdateDB[Update for whole database] 
    Adminform --> AdminUpdateDB
Jul 16, 2024

Diversity Sampling Plots

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024

Diversity Scientific Terms

Scope of DiversityScientificTerms within the Diversity Workbench

DiversityScientificTerms is part of the database framework Diversity Workbench. Within this framework the application DiversityScientificTerms is confined to the management of scientific terms. Any module within the Diversity Workbench is focused on a specific data domain. DiversityScientificTerms keeps only data connected with the handling of scientific terms. Data of other realms are handled in separate modules. For an overview of the available modules see the image below. The current version relies on the service of DiversityAgents for explicit information of users etc., on DiversityProjects for further informations about terminologies and DiversityReferences for explicit information about references. DiversityCollection is dependent upon DiversityScientificTerms to characterize terms.

Despite the connections to other modules of the Diversity Workbench DiversityScientificTerms may be used as a stand-alone application.

Dec 17, 2024

Subsections of Scientific terms

Diversity Scientific terms

Download

Upcoming version

4.2.1

SQL Server 2016

For this version you need SQL Server 2016 or higher

  • New table JsonCache containing the data related to a term as JSON. In the menu accessible via Administration → Json cache … or in the header click on the Show JsonCache button to see the json cache for the current term.

Current version

4.2 (2023-05-10)

Download

  • Bugfixes in Workbench.dll
  • Bugfix setting permissions
  • Database documentation: Enumeration tables with specific title and generic table definition

 

Previous versions

4.1.21 (2023-02-22)

  • Bugfix creating archive
  • Bugfix linking to client software site
  • Many order columns enabled
  • New order columns Property, Section, Resource, Reference Ranking hierarchy included Video starten
  • Docu: Bugfix retrieving column description for views

Database updates

  • 01.00.15: New views View_TermProperty, View_SectionTerm, View_TermReference, View_TermResource, View_TermRankingHierarchy for query; Missing defaults for table TermDependency; Missing descriptions for tables, views, …; New function TerminologySize if missing; New column ArchiveProtocol in table Terminology including log table and trigger; Function TerminologyDataLastChanges; Missing grants for table TerminologyPropertyValue; Removing not used type - moved to table TermRepresentation;

 

Diversity Scientific terms

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Aug 9, 2024

Diversity Scientific terms

Database login

To use a module from the DiversityWorkbench framework, such as “DiversityCollection”, you need access to a database. If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, you will find instructions here.

Connect to a database

  1. At the top left of the main window, go to ConnectionDatabase … or click the Connect button . A dialog form “Connect to database” opens.

  2. In the “Server” section, add the server name or the IP address and the port number.

  3. In the “Login” section, choose an option:

    • Windows authentication: Using the Windows Login information.

    • SQL-Server authentication: User and password as defined in the database.

  4. Click on the Connect to server button.

  5. If the connection information is valid, you can Choose a database from the drop-down list at the bottom.

  6. Choose the database you want to work with and click OK.

  7. If you access a database for the first time, you will be asked to consent to the storage and processing of your personal data (see below) according to the General Data Protection Regulation. Without your consent the access is not possible.

Important The standard port number for SQL-Server is 1433 and is set as default. If the database server is configured to use a different port, you must change the port number in the port input field.

Previous connection

If you have been connected to a database in previous sessions, you can select one of these connections:

  1. At the top of the “Connect to database” dialog form, click on the Previous connections button .
  2. Select a connection from the drop-down list. This inserts the name or IP address and the port in the corresponding input fields in the server section.
  3. To log into a database, proceed as described above starting from step 3.

Testing a connection

To test the connection, you can send a ping by clicking the button .

Switch between databases

  1. At the top left, go to ConnectionDatabase … or click on the Connect button .
  2. If you are already connected to a server, you can select a database from the drop-down list Choose database at the bottom of the dialog box.

Reset and Cancel

Reset: If you are connected to a server, there is a Reset button below the “Login” section of the “Connect to database” dialogue box. Click the Reset button to change your server or login settings.

Cancel: If you do not want to change anything, click on Cancel.

Encryption

By default, the connection to the databases is encrypted. The icon next to the Connect to server button indicates an encrypted connection. By clicking on the icon, you can switch to an unencrypted connection, indicated by the icon .

Videos

  • Login to a database: Video starten.

Diversity Scientific terms

Menu

Overview of the menu in DiversityScientificTerms

  • Connection
    •  Database Choose one of the databases available on the server. Only those databases will be listed to which the user has access permission..png?class=inlineimg)
    •  Module connections … Edit the connections to the other modules within the DiversityWorkbench.
    •  Transfer previous settings Transfer the settings of a previous version.
    • Quit Quit the application and stop all processes started by the application.
  • Data
    •   Table editors Edit data as selected in the query data directly in the data tables.
      •  Term … Edit data of the Term table.
      •  Representation … Edit data of the TermRepresentation table.
      •  Property … Edit data of the TermProperty table.
      •   Reference … Edit data of the TermReference table.
      •  Resource … Edit data of the TermResource table.
    •  Backup database … Backup of the whole database
    •  CSV (bcp) Export data of the whole database as csv files
  • Administration
    •  Database Administration of the database
    •  Documentation … Documentation of the tables within the database
    •  Logins … Administration of the logins of the server their permissions in the databases
    •  Rename database Rename the current database
    •  Set published address Setting the address published for links by other modules
    •  Database tools … Creation of log tables, triggers etc. (only for dbo)
    •  Language … Enabling languages for the terms.
    •  Resources directory … Setting the directory for the resources.
    •  Terminologies … Administration of the terminologies.
  • Help
    •  Manual Opens the online manual - Info Show the version and corresponding information
    •  Feedback … Opens a form for sending feedback
    •   Feedback history … Opens a window for browsing former feedback.
    •   Edit feedback … Opens a window for editing the feedbacks sent to the administrator (for admins only).
    •   Websites Websites related to DiversityScientificTerms
    • Download applications … Download DiversityScientificTerms from the website of the Diveristy Workbench project
    • Information model … Inspect the information model on the website of the Diveristy Workbench project
    •  Errorlog Inspect the errorlog of DiversityScientificTerms
  • Update
    •  Update database … Update the database to the current version
    •  Update client … Download the current version of the client

 

 

 

 

 

Apr 15, 2025

Diversity Scientific terms

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many colunns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Apr 15, 2025

Diversity Scientific terms

Editing the data

The main form of DiversityScientificTerms contains two main areas. On the left you find the query and the results of this query. On the right part the details of a dataset selected in the result list is shown. The upper part of the data area shows the position of the current term within the hierarchy. In the lower part you find the fields for the details of a term. At the base of the window the properties, references and resources of a term are listed. 

For every term one representation can be set the preferred one, indicated by the icon. To make a representation the preferred representation, simply click on this icon.

Display settings for charts etc.

For display in an interface used from other modules like DiversityCollection, e.g. via a chart, a term may have a display order, a color for the background and an image.

The display order will be applied within the terms of the same hierarchy level and works top down, so the term with the lowest display order will be presented at the top of the list.

To set the display color, click on the set color button. A window will open where you can either select an available color or define a new one. The color will e.g. be used as background in a chart. If depending terms should use a color of the same hue, click on the button to activate the inheritance for the color. The button will change to . See chapter chart for details.

To set the display image for a term, click on the button. A window will open where you can search for the image that should be presented. In a chart, the size of the image will be scaled down to a maximal width of 100. To remove an image, use the button next to the image.

After editing the data, click on the button to save your data. To see the description of the fields, just move the mouse into it. A small window will appear, showing the description. To see the description of all fields turn to the description of thedatabase.

 

Copy data

To create a new term click on the button above the query list. A form as shown below will open where you can enter some basic informations for the new term.

 

To create a copy of a term, choose an entry in the query list and click on the button besides the hierarchy. A form as shown below will open providing you with the possibility to create a synonym, an inferior dataset or a copy on the same level in the hierarchy as the original dataset.

 

To create a synonym of a term, choose an entry in the query list and click on the button besides the hierarchy. This will create a synonym to the original dataset.

To make a term a synonym to another term, choose the term in the hierarchy and click on the button besides the hierarchy. This will open a window, where you can select the term to which the current term should become a synonym to.

To delete a dataset, select it an click on the button.

Apr 15, 2025

Subsections of Editing

Diversity Scientific terms

Chart

The module DiversityScientificTerms provides other modules the option to query the terms on basis of a chart. These charts are created on basis of the selected terminology or sections and in case there are sections available To test the chart of the current terminology, select Test - Chart from the menu. In case there are sections a window will open where you choose the data you want to show in the chart. A window as shown below will open. To test the chart, select an entry and click OK. Video starten

Ranking terms resp. types

The chart is not available for ranking terms resp. types

Sections

Terminologies may contain sections. If no sections are available, only the whole terminology will be presented (see below). 

If the terminology contains sections, you can choose either the whole terminology or a section. If you choose a section only the terms within the section will be shown and the name of the section is shown in the header (see below). 

Images

Video starten

If a term has images, these images will be shown in the chart as shown below. The images will be shown according to the order set for the images. If a title for an image has been defined, this will be shown in the tool tip when you moove the mouse above the image. If no title has been defined either the synonyms the term will be shown or if no synonyms are defined the display text of the term. The width of the images is restricted to 100 pixel, larger images will be adapted accordingly. 

Colors

Video starten

Every term may have display color . Click on the set color button to select a color for the term. This color will  be shown as background for the term as shown below. If no color has been choosen, a greyscale value will be used as background as shown above.

If the terms depending on a term do not have a color of their own and the inheritance of the color is activated, a hue of the parent term will be used as shown in the image below. To activate the inheritance of the color, click on the button. It will change to and the color will be inherited to depending values as shown in the image below.

To select an item, click on it so the corresponding ID will appear in the box in the left upper corner. If there are synonyms available for a term these will be shown via a tooltip as shown below.

Files

The html files for the chart will be generated in the user directory as shown below. The file …_ChartSelect.html is the main file. the other files like e.g. …_ChartSelect_71_76.html are depending files that contain the items with the parent ID 71. These files will be removed when you close the chart.

The html files and the chart are adapted to the width of the window of your application, so if you change the width of your main window, the files will be regenerated to ensure that the displayed columns fit into the available space. In the examples below, the chart has been selected with two different widths that result in a regeneration of the files.

The html file below has been generated with a reduced with of the window with the links to subpages starting on a higher level. The fields with a colored background let you select the displayed items while the fields with a link lead you to a subpage containing depending items (e.g. Coastal dune and sand habitatas in the example below).

A field with a link will lead you to a subpage as shown below. The link at the top of the subpage will lead you back to the page where you came from (← Coastal habitatas in the example below).

 

Sep 2, 2024

Diversity Scientific terms

Dependency

For an introduction see the video: Video starten

The terms of a certain type/ranking may be dependent on terms that are no types/ranking, e.g. terms of the type Zement may only be available for terms underneath the term Sedimentgestein which itself is of the type Gestein. Clients that want to use any term of a dependent type (e.g. Zement) must therefore first insert a term of the type of these terms depend on (e.g. Sedimentgestein) or underneath in the hierarchy (e.g. Kalkgestein). The clients afterwards will contact the database including the information of the first term (e.g. Kalkgestein) and will in return get a list of all terms of which the type (e.g. Zement) is defined as dependent on the first term (e.g. Kalkgestein) resp. a parent of this term (e.g. Sedimentgestein). The image below shows the relationships in an example.  

To define dependencies, change to Ranking terms (in the menu click on Ranking terms to switch to the administration of the types resp. ranking terms (see image below)). This part is only accessible for users in the group Editor or above.

Mar 25, 2025

Diversity Scientific terms

Hierarchy

The upper part of the form shows the term in the hierarchical relation. To insert a relation to a broader term, click no the button. In the window that will open, select the broader term from the list and click OK. To remove the relation to a broader term, click on the button. The image below summarizes the options to depict the relations in the hierarchy.

 

The default view of the hierarchy is shown below.

 

If you want to see the synonyms, click on the button. The button will change to   and the hierarchy will show the synonyms with the indaction of the language. Synonyms of the current term will have a pink backgroud.

 

If you restrict the output in the hierarchy to a certain language, only one language will be shown in the hierarchy as shown below.

 

In the image above the hierarchy is restricted to the superior terms. If you want to see the whole hierarchy click on the button. It will change to and all terms will be shown. To return to the previous view, just click the button again.

 

 

A cached value of the hierarchy is stored in two fields (downward and upward) for every term. These entries are needed e.g. for queries where the whole hierarchy is used instead of the term itself. The hierarchies are build using the preferred terms (see Editing thedata ).

 

Jul 22, 2024

Diversity Scientific terms

History

To inspect the history of a dataset click on the button. A form will open, showing all former states of the data in the tables with the current dataset at the top.

 

Jul 22, 2024

Diversity Scientific terms

Language

To edit the language list available for the selection of the synonyms, choose Administration - Language from the menu. In the window that will appear, you can enanble or disable certain languages (see  below). With a click on the Disable languages that are not used button, you can disable all languages that are not used for synonyms so far, which will shorten the list for selection in the main form..

Jul 22, 2024

Diversity Scientific terms

Properties

The properties that can be asigned for a term might be defined under the terminology to which the term belongs. To insert a new property, open the form Terminology. You find the properties defined for a terminology in the base part of the form as shown below.

The properties that are defined in the terminology are then available for a term. Depending on the datatype set for a property in the terminology, you can either enter list, text, numeric or date values for a property of a term as in the example above numeric values for an age. For properties of the datatype list, an area for the entry of the dedicated (text) values will appear as shown below.

The values for a term will be restricted to the list of values (see below).

 

Jul 22, 2024

Diversity Scientific terms

Ranking terms

Every term should be characterized by a ranking term or type. These ranking terms are edited in a separate list, not to be mixed up with the terms. To switch to the editing of the ranking terms, click on Ranking terms in the menu that will switch to Ranking terms and list the ranking terms (see image below).

If in the query for the terms Ranking has been selected as the display column, this will be changed to Display Text as Ranking is not available for Ranking terms. To edit the ranking terms / types a user needs to be in the group DiversityWorkbenchEditor or above. For the ranking terms, you can define a dependency from a term.

Jul 22, 2024

Diversity Scientific terms

References

For every terminoloy and every term you can insert references.

There are 3 options to enter a reference:

1 as simple text
just enter the title of the reference in the text field as shown below
2 linked to a module like DiversityReferences or a webservice
Click on the  button to open a window where you can search and select for a reference in e.g. the module DiversityReferences. You need access to DiversityReferences or a corresponding webservice to use this option.
3 a URI of a website
click on the button to open a browser where you can choose the reference from the web

The data are stored in the tables TermReference and TerminologyReference respectively.

 

Jul 22, 2024

Diversity Scientific terms

Resources

For every term you can insert resources, including informations about the creator, the license etc. (see image below). Use the and button to add or remove images. If an image should not be shown in an external user interface, e.g. in a chart in another modul like DiversityCollection, enter the reason in the  field. The image will change to  and the pink background will indicate the withholding of the image. The title will be shown as tooltip in a chart.

To see an image, click on the button. A window as shown below will open.

The data are stored in the tables TermResource.

 

Jul 22, 2024

Diversity Scientific terms

Sections

Video starten

The sections that can be asigned for a term must be defined under the terminology to which the term belongs. To insert a new section, open the form Terminology. You find the sections defined for a terminology in the base part of the form as shown below.

The sections that are defined in the terminology are then available for a term. Choose the and button to add resp. remove a term from a section (see below). To Insert all Terms listed in the query results to a section, choose Data - Add to section from the menu.

 

Jul 22, 2024

Diversity Scientific terms

Synonyms

Every term may have several synonmys. The preferred synonym, shown in picklists and the like is marked with a green icon. To make another synonym the preferred icon, click on the button. To make a term a synonym to another term, click on the button. In the window that will open, select the synonym from the list and click OK.

To create a synonym of a term, choose an entry in the query list and click on the button besides the hierarchy. A window as shown below will open. Enter the display text and choose the language of the new synonym. This will create a synonym to the original dataset.

To make a term a synonym to another term, choose the term in the hierarchy and click on the button besides the hierarchy. This will open a window, where you can select the term to which the current term should become a synonym to (see below).

If you want to see the synonyms in the Hierarchy, click on the button. The button will change to   and the hierarchy will show the synonyms with the indaction of the language. Synonyms of the current term will have a pink backgroud.

 

 

If there are several synonyms, the perferred term will be marked green while the other synonyms are marked pink. The current term will be marked yellow (see below).

 

 

Jul 22, 2024

Diversity Scientific terms

Table Editors

For the data selected in the main window the table editors offer a direct access to the tables of the database. The menu Data - Table editors provide an editor for Term… , Representation… and Resource…

A window with the content of the table will open. Columns with a gray background can not be edited here. Columns with a light gray background are linked to the contents of lookup tables where you can change according to the contents of these tables.

Select Set timeout … from the menu to increase the default timeout from 5 seconds to a higher value, e.g. for greater amounts of data.  

Editing

You can either edit the contents of the table directly or perform changes to any number of marked fields. To mark a whole column use the  button. Once you have selected the contents to change, select one of the modes of change that appear in the upper left corner. The modes of change are:

  • Insert: Insert the given value at the beginning of the content
  • Append: Append the given value at the end of the content
  • Replace: Replace a string in the content with the given value
  • Clear: Remove the content

After selecting the change mode, enter the text in the field where necessary and click on the corresponding button to perform the changes

Filtering

To filter the content of the table, click in the column that should be used for filtering. Then choose the mode of comparision:

  • = : The content must be exactly like the given value
  • ~ : The content must contain the given value
  • ≠ : The content must be different to the given value

If you want the filtering to be case sensitive, choose the a<>A option. After all parameters are set, click on the button. To undo the filtering, click on the button. This will reset the data to the last saved version. If you want your changes to be saved, click the button before you reset the filtering. If you close the window all changes so far will be saved automatically. So if you do not want to save your changes, click on the button before closing the window.

Export

To export the data as a tab separated text file, click on the button. The file will be automatically saved in the client-folder.  

Log data

To see the log data of the table, you can click on the button. The content of the log table can not be changed, but is read only.  

Jul 22, 2024

Diversity Scientific terms

Terminology

To edit the terminologies select Administration - Terminologies … from the menu.

 

A form as shown below will open. A terminology may optionally be linked to a project in DiversityProjects. Click on the button to get further informations about the project or directly access the module DiversityProjects. To remove the connection to DiversityProjects, click on the button.

 

After changes in the data, especially in the hierarchy, please use the button Refresh the cache entries for the hierarchy to update the hierarchy cache for the terms within the terminology. The hierarchies are build using the preferred terms (see Editing the data ). 

On the left the terminologies accessible for the user are listed, on the right you find the details. At the bottom of the window the properties, references and users with access to the selected terminology are listed. In the User tab, use the < and > buttons to decide if a user has access to a terminology. To add missing users use the  button. This functionallity is as well available under the Login Administration

Jul 22, 2024

Diversity Scientific terms

Import Export

The import wizard reachable in the menu Data -> Import can be used to import data into DiversityScientifcTerms. Currenlty there is no export wizard, but the data tables from DiversityScientificTerms can be exported using the Table editors, accessible via the menu -> Data -> Table Editors.

Apr 15, 2025

Diversity Scientific terms

Internals

For users that need more detailed information about the software including database design etc.

Jul 22, 2024

Subsections of Internals

Diversity Scientific terms

Database

The image below shows the main datadomains within DiversityScientificTerms.

  The database for DiversityScientificTerms is based on Microsoft SQL-Server 2014 or above.

Organisation of the data

The main data are kept in the tables Terminology, Term and TermRepresentation. For further tables and details see the table descriptions.

Jan 14, 2025

Subsections of Database

Diversity Scientific Terms

TABLES, VIEWS, FUNCTIONS, PROCEDURES, ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES

ER-Diagram


Table Section

A section of terms within a scientific terminology, e.g. the terms of a certain geographic area extracted from a terminology

Column Data type Description Nullable Relation
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) NO Refers to table Terminology
SectionID int ID of the section, Primary key NO -
DisplayText varchar (500) The label or name of the section YES -
Notes nvarchar (MAX) Notes about the section YES -
LogInsertedBy nvarchar (50) ID of user who first entered (typed or imported) the recorde into this system. This is the operator (or typist) name, which may be different from the person responsible.Default value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • Terminology

Dependent tables:

  • SectionTerm

Table SectionTerm

A term within a section of terms within a scientific terminology, e.g. the terms of a certain geographic area extracted from a terminology

Column Data type Description Nullable Relation
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) NO Refers to table Section and table Term
SectionID int ID of the section, Part of primary key NO Refers to table Section
TermID int ID of the term, Part of primary key NO Refers to table Term
LogInsertedBy nvarchar (50) ID of user who first entered (typed or imported) the recorde into this system. This is the operator (or typist) name, which may be different from the person responsible.Default value: [dbo].UserID YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) ID of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • Section
  • Term

Table Term

The scientific term within a scientific terminology, e.g. the name of a soil in soil sciences or the name of a mineral in mineralogy

Column Data type Description Nullable Relation
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) NO Refers to table Term and table Terminology
TermID int ID of the term, Primary key NO -
BroaderTermID int ID of the superior term within DiversityScientificTerms to which this record belongs to, e.g. Rosaceae is broader term for Rosa YES Refers to table Term
RankingTermID int ID of the ranking term of the term, e.g. Epoch is rank for Paleocene, family is rank of Rosaceae YES Refers to table Term
IsRankingTerm bit If the term is a ranking term, e.g. epoch in paleontolgoyDefault value: (0) YES -
PreferredRepresentationID int The ID of the preferred representation of this term YES -
TermIdentifier nvarchar (500) An identifier for a term, valid for all representations of this term YES -
Notes nvarchar (MAX) Notes about the term YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • Terminology

Dependent tables:

  • SectionTerm
  • TermDependency
  • TermProperty
  • TermRepresentation

Table TermDependency

Dependency within terms

Column Data type Description Nullable Relation
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) NO Refers to table Term
TermID int ID of the term, Part of primary key NO -
DependsOnTermID int ID of the term the current term depens on, Part of primary key NO Refers to table Term
LogInsertedBy nvarchar (50) -Default value: [dbo].UserID YES -
LogInsertedWhen smalldatetime -Default value: getdate() YES -
LogUpdatedBy nvarchar (50) -Default value: [dbo].UserID YES -
LogUpdatedWhen smalldatetime -Default value: getdate() YES -

Depending on:

  • Term

Table Terminology

A terminology used in a certain scientifc area, e.g. mineralogy, soil sciences, paleontology, stratigraphy

Column Data type Description Nullable Relation
TerminologyID int The ID of the terminology (primary key) NO -
DisplayText nvarchar (50) The text for the terminology as shown e.g. in a user interface NO -
Description nvarchar (MAX) The description of the terminology YES -
ExternalDatabase nvarchar (200) The name of the source that has been imported or can be linked to for further analysis YES -
ExternalDatabaseVersion nvarchar (255) The version of this data collection (either official version number, or dates when the collection was integrated) YES -
ExternalDatabaseAuthors nvarchar (200) The persons or institutions responsible for the external database YES -
ExternalDatabaseURI varchar (255) The URI of the database provider resp. the external database YES -
ExternalDatabaseInstitution nvarchar (300) The institution responsible for the external database YES -
ExternalAttribute_NameID nvarchar (255) The table and field name in the external data collection to which TaxonNameExternalID refers YES -
Rights nvarchar (100) Information about rights (copyright, intellectual property) held in and over the database. Enter esp. name of person or institution holding the copyright. Leave empty if unknown. YES -
DefaultLanguageCode nvarchar (50) The code of the default language of the terminologyDefault value: N’en' YES Refers to table LanguageCode_Enum
ProjectURI varchar (500) Link to the module DiversityProjects YES -
InternalNotes nvarchar (MAX) Additional notes concerning this data collection YES -
ArchiveProtocol nvarchar (MAX) The protocol created during the last archive YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • LanguageCode_Enum

Dependent tables:

  • Section
  • Term
  • TerminologyProperty
  • TerminologyReference
  • TerminologyUser

Table TerminologyProperty

Properties of scientific terms in a certain terminology, e.g. the specific weight of a mineral in mineralogy

Column Data type Description Nullable Relation
TerminologyID int An ID to identify an external data collection of scientific terms (primary key, the ID has no meaning outside of the DiversityScientificTerms) NO Refers to table Terminology
Property nvarchar (50) The name of the property NO -
DisplayText nvarchar (50) The text shown e.g. in a user interface YES -
Description nvarchar (MAX) Description of the property YES -
Datatype varchar (50) The datatype of the property YES Refers to table TerminologyPropertyDataType_Enum
DisplayOrder smallint The sequence with which the properties are shown in a user interface if different from alphabetic order YES -
DisplayEnable bit True if the property should be shown, otherwise false YES -
InternalNotes nvarchar (500) Internal notes about this property YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • Terminology
  • TerminologyPropertyDataType_Enum

Dependent tables:

  • TerminologyPropertyValue
  • TermProperty

Table TerminologyPropertyValue

Dedicated property values of a certain property of a scientific term

Column Data type Description Nullable Relation
TerminologyID int An ID to identify an external data collection of scientific terms (primary key, the ID has no meaning outside of the DiversityScientificTerms) NO Refers to table TerminologyProperty
Property nvarchar (50) The name of the property NO Refers to table TerminologyProperty
DisplayText nvarchar (50) The text shown e.g. in a user interface NO -
Description nvarchar (MAX) Description of the property YES -
InternalNotes nvarchar (500) Internal notes about this property YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • TerminologyProperty

Table TerminologyReference

A TerminologyReference used in a certain scientifc area, e.g. mineralogy, soil sciences, paleontology, stratigraphy

Column Data type Description Nullable Relation
TerminologyID int An ID to identify an external data collection of scientific terms (primary key, the ID has no meaning outside of the DiversityScientificTerms) NO Refers to table Terminology
Reference nvarchar (255) A link to e.g. a website containing a description of the terminology or the title of the publication where the collection event was published. Note this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (255) URI of reference where specimen is published, e.g. referring to the module DiversityReferences YES -
ReferenceDetails varchar (255) The exact location within the reference, e.g. pages, plates YES -
InternalNotes nvarchar (MAX) Additional notes concerning the reference YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • Terminology

Table TerminologyUser

Users with access to a terminology

Column Data type Description Nullable Relation
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc.. NO Refers to table UserProxy
TerminologyID int An ID to identify an external data collection of scientific terms (primary key, the ID has no meaning outside of the DiversityScientificTerms) NO Refers to table Terminology

Depending on:

  • Terminology
  • UserProxy

Table TermProperty

The property of a scientific term, e.g. the specific weight of a certain mineral in mineralogy

Column Data type Description Nullable Relation
TerminologyID int An ID to identify an external data collection of terms (primary key, the ID has no meaning outside of the DiversityScientificTerms) NO Refers to table Term and table TerminologyProperty
TermID int ID of the term, refers to table Term (foreign key) NO Refers to table Term
Property nvarchar (50) The property as defined in table TermiologyProperty, Foreign key NO Refers to table TerminologyProperty
TextValue nvarchar (500) The text if the value is a text value YES -
NumericValue float The numeric value if the value is numeric YES -
DateValue datetime The date if the value is a date YES -
Notes nvarchar (MAX) Notes about the property entry YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • Term
  • TerminologyProperty

Table TermReference

A reference for a term used in a certain scientific area, e.g. mineralogy, soil sciences, paleontology, stratigraphy

Column Data type Description Nullable Relation
RepresentationID int ID of the term, refers to table TermRepresentation (foreign key) NO Refers to table TermRepresentation
Reference nvarchar (255) A link to e.g. a website containing a description of the terminology or the title of the publication where the collection event was published. Note this is only a cached value where ReferenceURI is present NO -
ReferenceURI varchar (255) URI of reference where specimen is published, e.g. referring to the module DiversityReferences YES -
ReferenceDetails varchar (255) The exact location within the reference, e.g. pages, plates YES -
InternalNotes nvarchar (MAX) Internal notes about the reference YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • TermRepresentation

Table TermRepresentation

The representation of a scientific term within a scientific terminology in a certain language, e.g. the name of a soil in soil sciences in English or German

Column Data type Description Nullable Relation
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key) NO -
TerminologyID int The ID of the terminology in which the term belongs (foreign key) NO Refers to table Term
TermID int ID of the term to which the representation belongs (foreign key) NO Refers to table Term
DisplayText nvarchar (400) The label or name of the term as shown e.g. in a user interface NO -
Description nvarchar (MAX) Description of the term YES -
HierarchyCache nvarchar (MAX) A system generated list defining the hierarchy of the term above the current entry, necessary to distinguish synonymous entries YES -
HierarchyCacheDown nvarchar (MAX) A system generated list defining the hierarchy from the top to the current entry, necessary to distinguish synonymous entries YES -
ExternalID nvarchar (50) If the entry was retrieved from an external database, a code or number for the entry as defined in the external database YES -
Notes nvarchar (MAX) Notes about the term YES -
LanguageCode nvarchar (50) The code of the language of the property (foreign key)Default value: N’en' YES Refers to table LanguageCode_Enum
DisplayOrder int The order as shown in die user interface YES -
DisplayARGB int The 8-Bit-ARGB-values (Alpha, red, green und blue) as shown in die user interface YES -
DisplayInheritARGB bit If the display color should be inherited to depending valuesDefault value: (0) YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -

Depending on:

  • LanguageCode_Enum
  • Term

Dependent tables:

  • TermReference
  • TermResource

trgInsTermRepresentation


Table TermResource

A resource connected to the scientific term, e.g. a picture, video etc.

Column Data type Description Nullable Relation
RepresentationID int ID of the term, refers to table TermRepresentation, Foreign key NO Refers to table TermRepresentation
URI varchar (255) The complete URI address of the resource. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO -
ResourceURI varchar (255) The URI of the resource, e.g. as stored in the module DiversityResources. YES -
Notes nvarchar (MAX) Notes on the resource YES -
Description xml (MAX) Description of the resource YES -
Title nvarchar (500) Title of the resource YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
Creator nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES -
InternalNotes nvarchar (500) Internal notes which should not be published e.g. on websites YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI nvarchar (500) The link to a module containing further information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
DisplayOrder int The sequence in which the resource should be displayed in a user interface YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise nullDefault value: '' YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: user_name() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() NO -

Depending on:

  • TermRepresentation

VIEWS


View ProjectUser

Interface for handling Terminology as Project

Column Data type Description Nullable
LoginName nvarchar (50) A login name which the user uses for access the DivesityWorkbench, Microsoft domains, etc.. NO
ProjectID int TerminologyID in table Terminology NO

Depending on:

  • TerminologyUser

View TerminologyID_UserAvailable

The terminologies a user has access to

Column Data type Description Nullable
TerminologyID int The ID of the terminology (primary key) NO
DisplayText nvarchar (50) The text for the terminology as shown e.g. in a user interface NO

Depending on:

  • Terminology
  • TerminologyUser

View View_SectionTerm

Content of table SectionTerm for query

Column Data type Description Nullable
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) YES
SectionID int ID of the section, Primary key YES
TermID int ID of the term, Part of primary key YES
Section varchar (500) DisplayText in table Section YES
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key) NO

Depending on:

  • Section
  • SectionTerm
  • TermRepresentation

View View_TermProperty

Providing content of table TermProperty including combined column DisplayText for query

Column Data type Description Nullable
TerminologyID int An ID to identify an external data collection of terms (primary key, the ID has no meaning outside of the DiversityScientificTerms) NO
TermID int ID of the term, refers to table Term (foreign key) NO
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key) NO
Property nvarchar (50) The property as defined in table TermiologyProperty, Foreign key NO
TextValue nvarchar (500) The text if the value is a text value YES
NumericValue float The numeric value if the value is numeric YES
DateValue datetime The date if the value is a date YES
Notes nvarchar (MAX) Notes about the property entry YES
PropertyValue nvarchar (552) Column Property combined with valid value column YES

Depending on:

  • TermProperty
  • TermRepresentation

View View_TermRanking

Combines ranking type of the term with hierarchy

Column Data type Description Nullable
Ranking nvarchar (MAX) Combines ranking type of the term with hierarchy YES
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key) NO
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) NO
TermID int ID of the term, Primary key NO

Depending on:

  • Term
  • TermRepresentation

View View_TermRankingHierarchy

Providing content of table TermRepresentation including hierarchy of ranking terms combined with column DisplayText for query

Column Data type Description Nullable
RankingHierarchy nvarchar (MAX) Hierarchy of ranking terms combined with column DisplayText YES
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key) NO
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key) NO
TermID int ID of the term, Primary key NO

Depending on:

  • Term
  • TermRepresentation

View View_TermReference

Providing content of table TermReference for query

Column Data type Description Nullable
RepresentationID int ID of the term, refers to table TermRepresentation (foreign key) NO
Reference nvarchar (255) A link to e.g. a website containing a description of the terminology or the title of the publication where the collection event was published. Note this is only a cached value where ReferenceURI is present NO
ReferenceURI varchar (255) URI of reference where specimen is published, e.g. referring to the module DiversityReferences YES
ReferenceDetails varchar (255) The exact location within the reference, e.g. pages, plates YES
InternalNotes nvarchar (MAX) Internal notes about the reference YES
TerminologyID int The ID of the terminology in which the term belongs (foreign key) NO
TermID int ID of the term to which the representation belongs (foreign key) NO

Depending on:

  • TermReference
  • TermRepresentation

View View_TermResource

Providing content of table TermResource for query

Column Data type Description Nullable
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key) NO
URI varchar (255) The complete URI address of the resource. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO
ResourceURI varchar (255) The URI of the resource, e.g. as stored in the module DiversityResources. YES
Notes nvarchar (MAX) Notes about the term YES
Description xml (MAX) Description of the term YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
Creator nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI nvarchar (500) The link to a module containing further information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
DisplayOrder int The order as shown in die user interface YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
TerminologyID int The ID of the terminology in which the term belongs (foreign key) NO
TermID int ID of the term to which the representation belongs (foreign key) NO

Depending on:

  • TermRepresentation
  • TermResource

View ViewBaseURL

View for access via linked server

Column Data type Description Nullable
BaseURL varchar (255) Content of functionBaseURL YES

Depending on:

  • BaseURL

View ViewDiversityWorkbenchModule

View for access via linked server

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) Content of function DiversityWorkbenchModule YES

Depending on:

  • DiversityWorkbenchModule

View ViewTermResource

View excluding XML column to provide access via linked server

Column Data type Description Nullable
RepresentationID int ID of the term, refers to table TermRepresentation, Foreign key NO
URI varchar (255) The complete URI address of the resource. This is only a cached value, if ResourceID is available and referring to the module DiversityResources NO
ResourceURI varchar (255) The URI of the resource, e.g. as stored in the module DiversityResources. YES
Notes nvarchar (MAX) Notes on the resource YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
Creator nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (255) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI nvarchar (500) The link to a module containing further information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
DisplayOrder int The sequence in which the resource should be displayed in a user interface YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
LogCreatedWhen datetime Point in time when this data set was created YES
LogCreatedBy nvarchar (50) Name of the creator of this data set YES
LogUpdatedWhen datetime Point in time when this data set was updated last YES
LogUpdatedBy nvarchar (50) Name of the person to update this data set last YES
RowGUID uniqueidentifier - NO

Depending on:

  • TermResource

FUNCTIONS


Function BaseURL

Provides the basic address for accessing the database

DataType: varchar (255)


Function DiversityMobile_Terminology

For Application DiversityMobile: Content of a Terminology

Parameter DataType Description
@TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key)
@LanguageCode nvarchar (50) The code of the language of the property (foreign key)
Column DataType Description
PropertyID int TerminologyID from table TermRepresentation
PropertyURI nvarchar (255) Combined content of function BaseURL and column RepresentationID
DisplayText nvarchar (400) The label or name of the term as shown e.g. in a user interface
TermID int ID of the term, Primary key
BroaderTermID int ID of the superior term within DiversityScientificTerms to which this record belongs to, e.g. Rosaceae is broader term for Rosa

Depending on:

  • BaseURL
  • Term
  • TermRepresentation

Function DiversityMobile_TermsList

Returns the scientific terms of a terminology

Parameter DataType Description
@TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key)
Column DataType Description
PropertyID int TerminologyID from table TermRepresentation
PropertyURI varchar (255) Combined content of function BaseURL and column RepresentationID
DisplayText nvarchar (400) The label or name of the term as shown e.g. in a user interface
HierarchyCache nvarchar (800) A system generated list defining the hierarchy of the term above the current entry, necessary to distinguish synonymous entries
TermID int ID of the term, Primary key
BroaderTermID int ID of the superior term within DiversityScientificTerms to which this record belongs to, e.g. Rosaceae is broader term for Rosa

Depending on:

  • BaseURL
  • Term
  • TermRepresentation

Function DiversityMobile_TermsListsForUser

Returns the datasources for the scientific terms lists for a user

Parameter DataType Description
@Login nvarchar (50) User for which the list should be retrieved
Column DataType Description
DataSource nvarchar (MAX) DisplayText of table Terminology
DisplayText nvarchar (50) The text for the terminology as shown e.g. in a user interface
PropertyID int TerminologyID from table Terminology

Depending on:

  • Terminology
  • TerminologyUser

Function DiversityWorkbenchModule

Returns name of Module: DiversityScientificTerms

DataType: nvarchar (50)


Function PrivacyConsentInfo

Providing common information about the storage and processing of personal data within the DiversityWorkbench

DataType: varchar (900)


Function TermChildNodes

Children of a given term

Parameter DataType Description
@TermID int ID of the term, Primary key
Column DataType Description
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key)
TermID int ID of the term, Primary key
BroaderTermID int ID of the superior term within DiversityScientificTerms to which this record belongs to, e.g. Rosaceae is broader term for Rosa
RankingTermID int ID of the ranking term of the term, e.g. Epoch is rank for Paleocene, family is rank of Rosaceae
Notes nvarchar (MAX) Notes about the term

Depending on:

  • Term
  • TermChildNodes

Function TermHierarchy

Hierarchy for a given term

Parameter DataType Description
@RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key)
Column DataType Description
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key)
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key)
TermID int ID of the term, Primary key
BroaderTermID int ID of the superior term within DiversityScientificTerms to which this record belongs to, e.g. Rosaceae is broader term for Rosa
RankingTermID int ID of the ranking term of the term, e.g. Epoch is rank for Paleocene, family is rank of Rosaceae
DisplayText nvarchar (400) The label or name of the term as shown e.g. in a user interface
LanguageCode nvarchar (400) The code of the language of the property (foreign key)

Depending on:

  • Term
  • TermChildNodes
  • TermRepresentation

Function TerminologyDataLastChanges

Returns the data of the last changes for a given TerminologyID

DataType: datetime

Parameter DataType Description
@TerminologyID int An ID to identify an external data collection of terms (primary key, the ID has no meaning outside of the DiversityScientificTerms)

Depending on:

  • TermProperty
  • TermReference
  • TermRepresentation
  • TermRepresentation_log
  • TermResource

Function TerminologySize

Returns the number of datasets within a terminology e.g. to check if a direct creation of the hierarchy if feasible

DataType: int

Parameter DataType Description
@RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key)

Depending on:

  • TermRepresentation

Function TermSuperiorNodes

Superior datasets for a term

Parameter DataType Description
@RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key)
Column DataType Description
RepresentationID int ID of the representation of a term within DiversityScientificTerms (primary key)
TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key)
TermID int ID of the term, Primary key
BroaderTermID int ID of the superior term within DiversityScientificTerms to which this record belongs to, e.g. Rosaceae is broader term for Rosa
RankingTermID int ID of the ranking term of the term, e.g. Epoch is rank for Paleocene, family is rank of Rosaceae
DisplayText nvarchar (400) The label or name of the term as shown e.g. in a user interface
LanguageCode nvarchar (400) The code of the language of the property (foreign key)

Depending on:

  • Term
  • TermRepresentation

Function UserID

Providing the ID of the current user from UserProxy

DataType: int

Depending on:

  • UserProxy

Function UserName

Providing the name of the user from UserProxy

DataType: nvarchar (50)

Parameter DataType Description
@ID varchar (10) ID of the user according to table UserProxy

Depending on:

  • UserProxy

Function Version

The version of the database

DataType: nvarchar (8)


Function VersionClient

The version of the client application compatible with the database

DataType: nvarchar (11)


PROCEDURES


Procedure procInsertTermCopy

Copy a dataset of table Term and depending data in tables TermRepresentation and TermProperty

Parameter DataType Description
@TermID int ID of the term, Primary key
@OriginalTermID int The TermID of the original dataset

Depending on:

  • Term
  • TermProperty
  • TermRepresentation

Procedure procRefreshHierarchyCache

Refreshing the content in the columns HierarchyCache and HierarchyCacheDown in table TermRepresentation according to the hierarchy as stored in table Term

Parameter DataType Description
@TerminologyID int The ID of the terminology, refers to PK in table Terminology (foreign key)

Depending on:

  • Term
  • TermRepresentation

Procedure SetUserProjects

Create database user and assign training projects

Parameter DataType Description
@User varchar (50) The login that should be created resp. the training projects assigned

Depending on:

  • UserProxy

ROLES

Content of cell Permission
Not granted
Name of other role Inherited from other role
Granted

Role DiversityWorkbenchAdministrator

Role for the administration of the database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LanguageCode_Enum TABLE
Section Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
Section_log Diversity Workbench User Diversity Workbench Editor TABLE
SectionTerm Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
SectionTerm_log Diversity Workbench User Diversity Workbench Editor TABLE
Term Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
Term_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TermDependency Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TermDependency_log Diversity Workbench Editor Diversity Workbench Editor TABLE
Terminology TABLE
Terminology_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TerminologyProperty TABLE
TerminologyProperty_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TerminologyPropertyDataType_Enum Diversity Workbench User TABLE
TerminologyPropertyValue Diversity Workbench User TABLE
TerminologyPropertyValue_log TABLE
TerminologyReference Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TerminologyReference_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TerminologyUser TABLE
TermProperty Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TermProperty_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TermReference Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TermReference_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TermRepresentation Diversity Workbench Editor Diversity Workbench Editor TABLE
TermRepresentation_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TermResource Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TermResource_log Diversity Workbench User Diversity Workbench Editor TABLE
ProjectUser Diversity Workbench User VIEW
TerminologyID_UserAvailable VIEW
View_SectionTerm Diversity Workbench User VIEW
View_TermProperty Diversity Workbench User VIEW
View_TermRanking Diversity Workbench User VIEW
View_TermRankingHierarchy Diversity Workbench User VIEW
View_TermReference Diversity Workbench User VIEW
View_TermResource Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewTermResource Diversity Workbench User VIEW
BaseURL Diversity Workbench User FUNCTION
DiversityMobile_Terminology Diversity Workbench User FUNCTION
DiversityMobile_TermsList Diversity Workbench User FUNCTION
DiversityMobile_TermsListsForUser Diversity Workbench User FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
TermChildNodes Diversity Workbench User FUNCTION
TermHierarchy Diversity Workbench User FUNCTION
TerminologyDataLastChanges Diversity Workbench User FUNCTION
TerminologySize Diversity Workbench User FUNCTION
TermSuperiorNodes Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
UserName Diversity Workbench User FUNCTION
Version FUNCTION
VersionClient FUNCTION
procInsertTermCopy PROCEDURE
procRefreshHierarchyCache PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchEditor

Role DiversityWorkbenchEditor

Role for editing the data

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LanguageCode_Enum TABLE
Section Diversity Workbench User TABLE
Section_log Diversity Workbench User TABLE
SectionTerm Diversity Workbench User TABLE
SectionTerm_log Diversity Workbench User TABLE
Term Diversity Workbench User TABLE
Term_log TABLE
TermDependency Diversity Workbench User TABLE
TermDependency_log TABLE
Terminology TABLE
Terminology_log TABLE
TerminologyProperty TABLE
TerminologyProperty_log TABLE
TerminologyPropertyDataType_Enum Diversity Workbench User TABLE
TerminologyPropertyValue Diversity Workbench User TABLE
TerminologyPropertyValue_log TABLE
TerminologyReference Diversity Workbench User TABLE
TerminologyReference_log TABLE
TerminologyUser Diversity Workbench User TABLE
TermProperty Diversity Workbench User TABLE
TermProperty_log TABLE
TermReference Diversity Workbench User TABLE
TermReference_log TABLE
TermRepresentation Diversity Workbench User TABLE
TermRepresentation_log TABLE
TermResource Diversity Workbench User TABLE
TermResource_log Diversity Workbench User TABLE
ProjectUser Diversity Workbench User VIEW
TerminologyID_UserAvailable VIEW
View_SectionTerm Diversity Workbench User VIEW
View_TermProperty Diversity Workbench User VIEW
View_TermRanking Diversity Workbench User VIEW
View_TermRankingHierarchy Diversity Workbench User VIEW
View_TermReference Diversity Workbench User VIEW
View_TermResource Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewTermResource Diversity Workbench User VIEW
BaseURL Diversity Workbench User FUNCTION
DiversityMobile_Terminology Diversity Workbench User FUNCTION
DiversityMobile_TermsList Diversity Workbench User FUNCTION
DiversityMobile_TermsListsForUser Diversity Workbench User FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
TermChildNodes Diversity Workbench User FUNCTION
TermHierarchy Diversity Workbench User FUNCTION
TerminologyDataLastChanges Diversity Workbench User FUNCTION
TerminologySize Diversity Workbench User FUNCTION
TermSuperiorNodes Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
UserName Diversity Workbench User FUNCTION
Version FUNCTION
VersionClient FUNCTION
procInsertTermCopy PROCEDURE
procRefreshHierarchyCache PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchUser

Role DiversityWorkbenchTypist

Role with restricted access for editing the data

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LanguageCode_Enum Diversity Workbench User TABLE
Section Diversity Workbench User TABLE
Section_log Diversity Workbench User TABLE
SectionTerm Diversity Workbench User TABLE
SectionTerm_log Diversity Workbench User TABLE
Term Diversity Workbench User TABLE
Term_log TABLE
TermDependency Diversity Workbench User TABLE
TermDependency_log TABLE
Terminology Diversity Workbench User TABLE
Terminology_log TABLE
TerminologyProperty Diversity Workbench User TABLE
TerminologyProperty_log TABLE
TerminologyPropertyDataType_Enum Diversity Workbench User TABLE
TerminologyPropertyValue Diversity Workbench User TABLE
TerminologyPropertyValue_log TABLE
TerminologyReference Diversity Workbench User TABLE
TerminologyReference_log TABLE
TerminologyUser Diversity Workbench User TABLE
TermProperty Diversity Workbench User TABLE
TermProperty_log TABLE
TermReference Diversity Workbench User TABLE
TermReference_log TABLE
TermRepresentation Diversity Workbench User TABLE
TermRepresentation_log TABLE
TermResource Diversity Workbench User TABLE
TermResource_log Diversity Workbench User TABLE
ProjectUser Diversity Workbench User VIEW
TerminologyID_UserAvailable Diversity Workbench User VIEW
View_SectionTerm Diversity Workbench User VIEW
View_TermProperty Diversity Workbench User VIEW
View_TermRanking Diversity Workbench User VIEW
View_TermRankingHierarchy Diversity Workbench User VIEW
View_TermReference Diversity Workbench User VIEW
View_TermResource Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewTermResource Diversity Workbench User VIEW
BaseURL Diversity Workbench User FUNCTION
DiversityMobile_Terminology Diversity Workbench User FUNCTION
DiversityMobile_TermsList Diversity Workbench User FUNCTION
DiversityMobile_TermsListsForUser Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
TermChildNodes Diversity Workbench User FUNCTION
TermHierarchy Diversity Workbench User FUNCTION
TerminologyDataLastChanges Diversity Workbench User FUNCTION
TerminologySize Diversity Workbench User FUNCTION
TermSuperiorNodes Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
UserName Diversity Workbench User FUNCTION
Version FUNCTION
VersionClient FUNCTION
procInsertTermCopy PROCEDURE
procRefreshHierarchyCache PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchUser

Role DiversityWorkbenchUser

Role with readonly access to the data

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
LanguageCode_Enum TABLE
Section TABLE
Section_log TABLE
SectionTerm TABLE
SectionTerm_log TABLE
Term TABLE
Term_log TABLE
TermDependency TABLE
TermDependency_log TABLE
Terminology TABLE
Terminology_log TABLE
TerminologyProperty TABLE
TerminologyProperty_log TABLE
TerminologyPropertyDataType_Enum TABLE
TerminologyPropertyValue TABLE
TerminologyPropertyValue_log TABLE
TerminologyReference TABLE
TerminologyReference_log TABLE
TerminologyUser TABLE
TermProperty TABLE
TermProperty_log TABLE
TermReference TABLE
TermReference_log TABLE
TermRepresentation TABLE
TermRepresentation_log TABLE
TermResource TABLE
TermResource_log TABLE
ProjectUser VIEW
TerminologyID_UserAvailable VIEW
View_SectionTerm VIEW
View_TermProperty VIEW
View_TermRanking VIEW
View_TermRankingHierarchy VIEW
View_TermReference VIEW
View_TermResource VIEW
ViewBaseURL VIEW
ViewDiversityWorkbenchModule VIEW
ViewTermResource VIEW
BaseURL FUNCTION
DiversityMobile_Terminology FUNCTION
DiversityMobile_TermsList FUNCTION
DiversityMobile_TermsListsForUser FUNCTION
DiversityWorkbenchModule FUNCTION
PrivacyConsentInfo FUNCTION
TermChildNodes FUNCTION
TermHierarchy FUNCTION
TerminologyDataLastChanges FUNCTION
TerminologySize FUNCTION
TermSuperiorNodes FUNCTION
UserID FUNCTION
UserName FUNCTION
Version FUNCTION
VersionClient FUNCTION
procInsertTermCopy PROCEDURE
procRefreshHierarchyCache PROCEDURE
SetUserProjects PROCEDURE
Jul 16, 2024

Diversity Scientific Terms

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table

Column Data type Description
Code varchar (50) The datatype of the property
Description nvarchar (500) The description of the datatype
DisplayText nvarchar (50) The display text shown e.g. in a user interface
DisplayOrder smallint The display order if different from alphabetic order
DisplayEnable bit True if the entry should be displayed, otherwise false
InternalNotes nvarchar (500) Internal notes for this entry

Table LanguageCode_Enum

The Code of a language according to ISO

Dependent tables:

  • Terminology
  • TermRepresentation

Table TerminologyPropertyDataType_Enum

Datatypes of a property of a terminology

Dependent tables:

  • TerminologyProperty
Jul 17, 2024

Diversity Scientific Terms

No-SQL Interface

JSON Cache

Databases of the modules provid a No-SQL interface where the data of the main table and the depending tables are merged as JSON.

Table JsonCache

Content of table JsonCache restricted to public available data

Column Data type Description Nullable Relation
ID int Unique ID for the Dataset, Primary key NO ID of the source
URI varchar (500) The URL as combination of BaseURL and ID NO BaseURL and ID of the source
DisplayText nvarchar (500) Representation in the interface NO Main table of the source
LogUpdatedWhen datetime Date and time when the data were last updated NO -
Data json Data related to the current dataset NO -

procFillJsonCache is started by an update trigger trgUpd… of the main table in the database

Interface in clients

All modules provide data via a cache table. In the header of the clients you can inspect the content of the JsonCache with a click on the button. For modules with a difference between local and public data, you can inspect the content of the public data with a click of the right mouse button.

Update

Apart of the update via the Trigger (see below) you can update the JsonCache via the update button underneath the button.

To update the JsonCache for the whole database select Administration - JsonCache… from the menu. a window as shown below will open where you can update the JsonCache for single datasets or the whole database.

Summary

graph TD;
    TaxonName[Main table in database] 
    trgUpdTaxonName[trgUpd.. of main table in database]
    TaxonName --> |Update in table| trgUpdTaxonName
    proc[Procedure procFillJsonCache setting the content in table JsonCache]
    trgUpdTaxonName --> proc
graph TD;    
    Mainform[Main form]
    ButtonShow[Button show JsonCache of current dataset]
    Mainform --> ButtonShow
    Left[Show Data]
    ButtonShow --> |Left click| Left
graph TD;    
    Mainform[Main form]
    Admin[Administration menu]
    Mainform --> Admin
    Cache[JsonCache...]
    Admin --> Cache
    Adminform[Administration form]
    Cache --> Adminform
    AdminUpdateSingle[Update single dataset]
    Adminform --> AdminUpdateSingle
    AdminUpdateDB[Update for whole database] 
    Adminform --> AdminUpdateDB
Jul 16, 2024

Diversity Scientific terms

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024

Diversity Taxon Names

Scope of DiversityTaxonNames within the Diversity Workbench

DiversityTaxonNames provides taxonomic names, their synonyms and hierarchical position for other modules, e.g. DiversityCollection and DiversityDescriptions and on the other hand uses services provided by the modules like DiversityReferences and DiversityProjects.

  The modules communicate with each other to provide their services for the other modules.

May 3, 2024

Subsections of Taxon names

Diversity Taxon Names

Download

Upcoming version

SQL Server 2016

For this version you need SQL Server 2016 or higher

  • New table JsonCache containing the data related to an agent as JSON. In the menu accessible via Administration → Json cache … or in the header click on the Show JsonCache button to see the json cache for the current agent.

Current version

4.2.2 (2025-02-11)

Download

  • Show Images for analysis value in case the value is a link to an image
  • Bugfix in init for reference objects

Database updates

02.05.39
  • Hierarchy
    • TaxonOrder: Adding additional levels of hierarchy
    • TaxonFamily: Adding additional levels of hierarchy
02.05.40 (Repeat 2.5.38 in case of missing updates)
  • Project
    • ProjectUser: Adding ReadOnly for locking a project
    • New function ProjectDataLastChanges
    • ProjectProxy: Adding missing columns for archive
  • Missing descriptions
  • TaxonNameListAnalysisCategory: Adding parent relation

Previous versions

4.2.1 (2023-08-21)

Download

  • Adaptions for IPM
  • Analysis:
    • Additional query column Hierarchy in administration
    • Display of whole hierarchy in tree in main form
  • Hierarchy
    • Bugfix setting hierarchy cache in administration - using database timeout
    • Bugfix setting hierarchy
    • Expanding new parent node after Drag & Drop changes in hierarchy and ensure visibilty of edited node
    • Unified icons for ranks
    • Showing rank or synonymy and name of current taxon in the header
    • Refreshing the hierarchy: Warning when changing the root of the displayed hierarchy
  • Bugfix for external identifiers
  • Bugfix not optimized query
  • Bugfixes creating and restoring archive

Database updates

02.05.38
  • Project
    • ProjectUser: Adding ReadOnly for locking a project
    • New function ProjectDataLastChanges
    • ProjectProxy: Adding missing columns for archive
  • Missing descriptions
  • TaxonNameListAnalysisCategory: Adding parent relation

 

4.2 (2023-05-11)

  • Bugfix setting module connections
  • Database documentation: Enumeration tables with specific title and generic table definition

 

4.1.28 (2023-03-28)

  • New button for filling table SynonymyListCache Video starten
  • New menu for filling table SynonymyListCache
  • Many order columns enabled
  • Several additional order columns
  • Several bugfixes in query using many order columns
  • Bugfix in generation of database documentation
  • Database tools: Adding option to add existence check for description generation
  • Database tools: Adding option to insert deprecated for description
  • Bugfixes for query with many order columns
  • Bugfixes for list view
  • List view with setting for file handling, button to open file etc. Video starten

Database updates

  • 02.05.37: Missing descriptions; TaxonOrder: Adding column IgnoreButKeepForReference for query; TaxonFamily: Adding column IgnoreButKeepForReference for query; New table SynonymyListCache to store results of function SynonymyList; New procedure [procFillSynonymyListCache] to fill table SynonymyListCache; SynonymyList - Try to get data from cache;

4.1.27 (2022-11-29)

  • Update for linked data Video starten
  • Selection of database involved in update of linked data
  • Several bugfixes

Database updates

  • 02.05.35: New view AcceptedNameChanges; Grants for TaxonNameReference;
  • 02.05.36: New function TaxonChildNodes including FamiliyCache, OrderCache, HierarchyCache;

Subsections of Download

Diversity Taxon Names

Installation

Resources

To run a module of the Diversity Workbench framework, you need access to a database and an installation of the respective client. The following instructions explain how to install the DiversityCollection client. All other modules are installed in the same way.

If you do not yet have an account for your institutional DWB platform, please contact your institution’s DWB administrator. If you wish to set up and use your own personal, institutional, domain-specific, or research-group-internal database environment, see Installation of a database for more information.

A German-language video demonstrates the installation using the DC client as an example. Please note that the initial steps in the video are outdated, as the downloads are now available via this manual, as described below. .

Download

All DiversityWorkbench modules can be downloaded free of charge. Within each module in the manual, you will find a Download menu item. There, you can download the latest version in the Current version section.

Installation of the client

The client is currently based on the .Net framework version 4.8 from Microsoft. If not already present, the software will prompt you to install it.

After downloading the client, unzip the .zip folder. The extracted setup folder contains two files: an .msi and a .bat file.

If you want to install the client on your computer, start the installation by double-clicking the .msi file.

If necessary, you can adjust the installation location in the next step.

Once the installation is complete, the software will be added to the program menu (see below) and a shortcut will be created on the desktop.

In the next chapter Database Login the login process is explained.

Troubleshooting

If you don’t have sufficient permissions on your computer to install anything, you can use the client by following the instructions Run the program without an installer. If you receive a warning from Windows that this computer is protected, follow the instructions Windows protection warning.

Run program without installer

There are several reasons why you might prefer to run DiversityCollection without installation. E.g. if you lack administrative permissions on your computer or if you want to use several different versions of DiversityCollection in parallel.

Therefore, the downloaded .zip file contains a .bat file. With this .bat file, a folder DiversityCollection_x_x_x is created on your desktop containing all relevant files to run the client DiversityCollection.

You have to unzip the downloaded .zip file to a local folder. The unzipped folder contains the .msi file and the .bat file. Within this unzipped! folder start the .bat file with a double-click. You might get a security warning, as shown in the section Windows protection warning.

The batch file unpacks the program files to a folder on your desktop named DiversityCollection_x_x_x, where "x_x_x" stands for the program version.

To start the DiversityCollection program, go to the folder and double-click on the file DiversityCollection.exe.

The login process is explained in the next chapter Database Login.

Technical notes and additional information

The software will be placed in the programs directory, as shown below.

Additionally, a folder is created in the user directory. This folder contains files and templates, for example, for label printing. It also contains hidden folders, such as Query. User input is saved there so that it can be loaded again the next time the program is started.

Windows protection warning

If you receive the following warning from Windows

please click on Weitere Informationen. A button Trotzdem ausführen will appear.

Please click on Trotzdem ausführen to install the software.

 

Apr 16, 2025

Diversity Taxon Names

Menu

Overview of the menu in DiversityTaxonNames

Connection

  • Database …: Choose one of the databases available on the server. Only those databases will be listed to which the user has access permission
  • Module connections …: Edit the connections to the other modules within the Diversity Workbench.
  • Timeout for database …: Set the timeout for database queries.
  • Transfer previous settings: Transfer the settings for IP-Address and port of the server, name of the database, login etc. of a previous version of the client to the current version.
  • Quit: Quit the application and stop all processes started by the application

Query

  • Show query: Show resp. hide the query area
  • Show ignored data: If data that were set on ignore should be visible
  • Predefined queries: This dialog will only appear if predefined queries are available. The submenu then lists the names for the predefined queries

Table views

  • View taxa in table …: Show the taxa in a spreadsheet
  • Edit taxa in table …: Edit the taxa in a spreadsheet
  • Spreadsheets: Edit data in configurable tables.
    • Taxon sheet…: Edit taxon and dependent data.
  • Table editors: Edit data direct in tables.
    • Taxon name…: Edit data in table TaxonName.
    • Common name…: Edit data in table TaxonCommonName.
    • Typification…: Edit data in table TaxonNameTypification.
    • Geography…: Edit data in table TaxonGeography.
    • External source…: Edit data in table TaxonNameExternalID.
    • Project: Edit data in tables depending on project.
    • Accepted name…: Edit data in table TaxonAcceptedName.
    • Synonymy…: Edit data in table TaxonSynonymy.
    • Hierarchy…: Edit data in table TaxonHierarchy.
    • Resource…: Edit data in table TaxonNameResource.
    • List: Edit data in tables depending on list.
      • Specimen…: Edit data in table TaxonNameListCollectionSpecimen.
      • Reference…: Edit data in table TaxonNameListReference.
      • Distribution…: Edit data in table TaxonNameListDistribution.
      • Analysis…: Edit data in table TaxonNameListAnalysis.

Data

  • Import
    • Import taxonomic names …: Import taxonomic names from text files
    • Import wizard: Import data from tab-separated text files
      • Import Taxa…: Import taxa from tab-separated text files
      • Import Synonyms…: Import synonyms from tab-separated text files
      • Import Hierarchy…: Import hierarchy from tab-separated text files
      • Import Analysis…: Import analysis from tab-separated text files
      • Webservices: Import taxonomic names from webservices
      • MYCOBANK…: Import taxa from MYCOBANK
  • Export
    • Export hierarchy and synonymy …: Export the taxonomic names with their hierachy and synonoymy
    • Export taxon lists …: Export the taxon lists as XML / HTML files
    • Export wizard …: Export tab-separated text files
      • Export taxa…: Export taxa as tab-separated text file
      • Export as CSV (bcp): Export data of the whole database as csv files
  • Replication …: Synchronise the content of 2 databases.
    • Add publisher …: Add a replication publisher for the replication.
    • Replication publisher: Database and server publishing data for replication.
    • Download …: Download data from the data provider in your local database.
    • Merge …: Merge contents between your local database and the replication provider.
    • Upload …: Upload data from your local database to the replication provider.
    • Remove: Remove the replication provider.
    • Clean database …: Clean your local database.
  • Archive: Archives of projects.
    • Administrate archives…: Administrate the projects that should be included in a schedule based archiving.
    • Create archive…: Create and archive of project data.
    • Reset database…: Reset the database, i.e. remove all user data.
    • Restore archive…: Restore project data from an archive.
  • Backup database …: Backup of the whole database
  • Remove taxa…: Remove all taxa selected in the query
  • Remove from project…: Remove all taxa selected in the query from a project

Administration

  • Analysis categories…: Administration of the analysis categories used within the taxon lists
  • Data sources …: Administration of the data sources of the taxonomic names
  • Database
    • Documentation…: Documentation functions for the database
    • Logins …: Administration of the logins and user
    • Maintenance…: Maintenace functions within the DiversityTaxonNames
    • Rename database: Rename the current database
    • Set published address: Setting the address published for links by other modules
    • Database tools: Tools to create and change objects in the database

    Help

  • Manual: Opens the online manual
  • Feedback…: Opens a window for sending feedback
  • Feedback history…: Opens a window for browsing former feedback
  • Statistics: Show the statistics within a project
  • Info: Show the version and corresponding information
  • Errorlog: Show the error log of the application

Test

  • Chart: Opens a chart query

 

Apr 10, 2025

Diversity Taxon Names

Query

Once you are connected to your database, you can search across all data. You have a wide range of options for this search.

Everything related to the query can be found on the left-hand side of the main window.

The upper part of the query section contains the list of all results “Query results”.

Below this you will find a section with all the buttons that are relevant for the search.

Under the query buttons you will find the “Query conditions”. You can enter all possible search criteria here.

Perform a query

Display the entire data set

To display the entire data set, start a search without specifying any criteria in the “Query conditions” section:

  1. In the middle of the query section on the left side of the main window, click on the “filter” button.

  2. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label.

Unter the query buttons, at the bottom of the query section, you will find the “Query conditions”.

  1. Enter the filter criteria for your search. E.g. you can select a project from the dropdown list.
  2. You can combine as many criteria as you want to limit your results.
  3. Start the query by clicking on the filter button .
  4. A list of the results is displayed in the “Query results” section. The number of results is displayed above the list next to the “Query results” label. If no result matches the query, the list is empty and the label “No match” is displayed.

Edit and customize query conditions

You can choose which query conditions are displayed in the main window. You can change this at any time.

  1. At the top left above the query results list, click on the “checkbox” button .

  1. Select any query conditions you want to use for your searches by selecting the respective checkboxes in the treeview.

Customize the interface

Hide/show the entire query section

In the main window go to the menu item QueryShow Query.

Hide the “Query conditions” section

On the left side of the “query buttons” in the middle of the query section, click on the “arrow” button .

Switch vertical/horizontal arrangement

You can change the arrangement of the query elements from vertical to horizontal and vice versa. To do this, click on the button below the main menu bar:

Edit the result list

Add results to the existing list

You can add new results with different query conditions to your current result list.

  1. Enter the new filter criteria for your additional search.
  2. Start and add these query results to the existing result list by clicking on the button .
  3. The new results are appended to the existing list.

Remove result items from the list

You can remove entries from your current result list.

  1. Select the entries you want to delete.
  2. Click on the button .

Important This will not delete the data from the database. It only affects the current display in the results list.

Many result columns

The option to provide a result list with many columns is described in chapter Many result columns.

Query conditions

Remember the last query

By default the values you entered for the query will be remembered. Your query criteria will be pre-filled when the program starts. To change this behaviour, click on the button .

Query annotation

The query for annotations deviates from the standard query (see below). Additionally, you may specify a type of the annotation (Annotation , Problem , Reference ) and the linked table (see Annotation).

Duplicates

Certain query condition fields provide the option to add up to 3 duplicates of themselves. For adding a ‘duplicate’ search criteria, click on the green “Plus” button . Remove a ‘duplicate’ search condition with a click on the red “Minus” button . The restrictions can be combined with AND + and OR |. To change between the modes click on the + resp. | icon.

Query modules

In the “Query conditions” section, some values might be linked to other modules. E.g. within the “Identification” group the fields “Taxa” and “Terms” are linked to the “DiversityTaxonNames” and “DiversityScientificTerms” modules. You can also add “linked” values to your query condition.

  1. Select the operator that determines how the entries are integrated into the search. See an explanation of all available operators in the table below.
  2. To connect to the linked module, click on the “Ammonite” button at the right of the respective query field.

  1. A query window for the linked module will open.
  2. Search for values within the linked module and click ok.
  3. If you want to see a list of the selected items, click on the magnifying glass button .

Info: There is also a detailed Video available, which explains all possible operators and how to use them.

Operator Meaning Example
Search for entries with a list Rosa | Rosa caninia \
Search for entries not within a list Rosa | Rosa caninia | ...
+H search for entry including lower hierarchy Picea | Picea abies | ...
+S search for entry including synonyms Picea abies | Pinus abies | ...
+HS search for entry including lower hierarchy and synonyms Picea | Picea abies | Pinus abies | ...
Change filter mode between link and text http://tnt.diversityworkbench.de/TaxonNames_Plants/4269 <> Picea abies L.

Query any fields

The query for any fields will search in several fields, e.g. withholding reasons in specimen, images etc. There are two versions: The first version (e.g. Notes) will search in all tables but not in collection event tables while the second version (e.g. Any notes) will search in any table (see image below).

Videos

  • Introduction how to use the query conditions: Video starten
  • How to use special query conditions: Video starten
  • Tutorial on how to query modules: Video starten
  • Tutorial on how to save a query: .

Wildcards in SQL

There are 4 different possibilities for wildcards in SQL:

Operator Description Example Result
%   any string consisting of no, one or many characters Pinus % will find anything like Pinus, Pinus sylvestris, Pinus strobus etc.
*  same effect as % (see above)
_  a single character Pinus s_lvestris will find Pinus sylvestris and Pinus silvestris etc.
[…] any character out of a given range like [abcde] or [a-e] Pinus s[iy]lvestris will find Pinus sylvestris and Pinus silvestris
[^…]   any character not in a given range like [^abcde] or [^a-e] Pinus s[^i]lvestris will find Pinus sylvestris but not Pinus silvestris

Many colunns

The option to include several columns in the result list is only available for optimized queries . To display several columns in the result list, click on the button next to the order by column (see below). A window will open where you can select the next column for the sorting. Underneath the order by column the second column for the sorting will be added. To remove this sorting column you can click on the    button. By default the width for the columns is set to 10. You can change this according to content. To set the width to the maximal length of the current content, click on the button. To change the sorting of the added order column click on the button. The colums are separated via " | " as shown in the image below.

For an introduction see the videos:

  • Mehrspaltige Suche: Video starten
  • Sortierung: Video starten

 

Apr 16, 2025

Diversity Taxon Names

Editing the data

The header of the main form allways shows you, with which database you are working, the version of the client, the database server and your login. The area for the data entry is devided into 2 main parts. In the upper part you enter nomenclatural information and facts, in the lower part taxonomic opinions of the editors (see topic database for further informations).

 

To see the descriptions for the fields of the database, simply move your mouse over it. A tooltip will appear with an explanation as shown in the example below.

Where you have to choose names from lists, type the beginning of the name in the field and then click on the drop down button . This will start a query in the database and list the result in the combobox.

If a field is to small for reading its content double-click on it. A form will open, where you can edit the text.

 

Apr 16, 2025

Subsections of Editing

Diversity Taxon Names

External databases

Most names in DiversityTaxonNames were imported from external sources. These sources are documented in the area External data sources.

 

To enter or delete an external datasource, use the and button button respectively. With the button you will get a detailed information about the external database. For a valid URI you can use the button to open the corresponding website in a separate window.

To edit the datasources themselve, choose TaxonNameExternalID and TaxonNameExternalDatabase

Apr 9, 2025

Diversity Taxon Names

Hierarchy

The taxonomy for the choosen name is depicted in the area Hierarchy. If the taxonomy has not been specified a button set hierarchy will be visible

click on it to insert a dataset for the hierarchy of this taxon.

To choose a higher taxon you first have to specify the taxonomic rank of the choosen name

and type at least 2 characters of the higher taxon in the ‘Superior taxon:’ field.

Click on the drop down button to get the list of taxa above the rank of the name for which you want to set the hierarchy. The hierarchy will then be shown in the tree view (see below). The taxa below the current taxon will be displayed in gray.

The first line shows the taxon or taxonomic group superior to the choosen taxon. To directly access the database entry of a higher taxon, choose this taxon in the hierarchy tree and click on . The button  will delete this entry. As an alternative to delete the entry for the hierarchy, you may set it on Ignore to keep the information but exclude it from the creation of a hierarchical tree (see chapter Ignoreddata for further details). To get an overview of the whole hierarchy click on the button . You get an overview for the whole taxonomy including the current taxon as shown below. The line above the hierarchy tree shows the cached value for the hierarchy. After changes in the hierarchy this cached value may differ from the actual hierarchy. To refresh it, click on the button.

 

In the taxon tree the main taxonomic groups are indicated with icons (S = species, G = Genus, F = Family, O = Order, C = Class, K = Kingdom). To change the position of a taxon within the hierarchy, use the drag & drop function of the tree.

To enable a search within the hierarchy, please use the maintenace function to update the hierachy cache. The hierarchy is stored in one string, so to search for e.g. all members of e.g. a certain familiy e.g. Rosaceae, please use the ~ operator and a leading wildcard in your search string e.g. “% Rosaceae” or “* Rosaceae”.

The information about the hierarchy is related to opinions of the editors and are allways restricted to a certain project. The data of the hierarchy are stored in table TaxonHierarchy.

Apr 9, 2025

Diversity Taxon Names

List view

To see the data in a spreadsheet, choose View → List view … from the menu. A window will open where all names from the query will be listed.

Customize visibility of fields

To change the selection of the visible fields, click on the Column visibility button. A window as shown below will open, where you can change the visibility of the columns.

 

Customize sequence

To change the sequence of the columns, just use your mouse to drag the columns to the position of your choice.

Sorting of the data

To sort the data in the grid just click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. That means that if you change a value in the sorting column the changed dataset will be placed at the new position according to its new value. The sorting of a column will be indicated with an arrow for the direction of the sorting (up or down).   

Change to data in main form

To change to a name in the main form, click on the , use the button. 

Formatting the grid

To adapt the width of the columns or the height of the rows either drag the border with the mouse, double click the border to get the optimal size for one column or respectively or click on the button for an optimal height of the rows or the button for an optimal width of the columns.

Exporting data

For an introduction see the video: Video starten

After setting the form according to your preferences, you can export the data with a click on the button. If the data should be appended in an existing file, change the option for the file handling from (= New file) to (= Append). The botton opens the folder containing the exported file.

 

 

Apr 9, 2025

Diversity Taxon Names

Projects

Projects with the DiversityWorkbench are located in the database DiversityProjects. The access to the data is organized via projects. The projects a user has access to can be selected in the query options.

 

To edit the project list use the project area. Use the  and  buttons to add or delete projects from the list.

If there are projects, to which you have no access, an additional list will appear, showing these projects (see below).

The information related to opinions of the editors are allways restricted to a certain project (see Database.).

Mar 20, 2025

Diversity Taxon Names

References

References related to a taxon can be added in the area “References”. Use the (add) and the (remove) buttons to handle the references.

The data of the references are stored in table TaxonNameReference.

Apr 9, 2025

Diversity Taxon Names

Relations

Relations between a taxa can be added in the area Relation. Use the (add) and the (remove) buttons to handle the relations.

The data of the relations are stored in table TaxonNameRelation.

Feb 11, 2025

Diversity Taxon Names

Synonymy

Basionym

The name on which the choosen name is based on should be entered in the “Based on:” field.

 

A name can be either an accepted name or a synonym to an accepted name. If nothing was specified so far, two buttons are visible:

choose one of these to make the choosen name to either an accepted name or a synonym.

Synonym

If the name is a synonym, the area for the synonymy will appear as shown in the images<

A name in most cases is synonym to one name but may sometimes be synonym to several names (e.g. pro parte). If you want to keep information of the synonymy you can set it to ignore (see chapter Ignored data for further details).

Delete a synonym

To delete a synonym, choose it in the list and click on the delete button .

Accepted Name

If the name is accepted, the form will show data related to accepted names

You can indicate accepted names in the search result list (in the menu choose View, indicate accepted names)

Conflict (Name declared a synonym and a basionym)

If by any chance (e.g. after import of synonymy relations from a foreign source) a name happens to be a synonym and an accepted name at the same time this is regarded as an error and will be shown as in the image below.

The data for the synonym are shown on the right side with blue labels, while the data for the accepted name are shown on the left with green labels. To correct this error you can either remove or ignore (see chapter Ignoreddata for further details) the assignement as a synonym or an accepted name.

Overview

In the area Synonymy overview you see the accepted name for the name you chose and a list of all the synonyms to this name. The sign   in front of a name following the accepted name means that this and the following names are homotypic synonyms to the accepted name. Groups of hetereotypic names start with a = in front of the first entry. If present, the first entry in each group is the basionym of this group. Names with unclear relation to the accepted name are preceeded by a “-”. To change to one of the names in the list, choose it in the list and click on the search button . The overview can be shown either as a list, corresponding to lists in publications or as a tree view. Use the  and  button to change between these views. In the tree view the current name is marked with a yellow background as shown below. The scrutiny of the search can be adapted by changing the number in the tool bar 3. As standard it is set on 3, but can be changed to values between 0 (just the current name) to 9. The higher the scrutiny the more thoroughly the search for synonyms will be performed and the longer it will take. To speed up the retrieval of the synonymy the results can be stored in a cache table as explained in the tutorial Video starten. Use the button next to the basionym to update the synonymy in the cache table for the current name or choose Administation - Refresh SynonymyListCache from the menu to update the content for all taxa in the database.

Explanation of the example above:

Type Example
accepted name Ceratiomyxa fruticulosa (O.F.Müll) T.Macbr.
basionym  ≡ Byssus fruticulosa O.F.Müll.
homotypic synonym Famintzinia fruticulosa (O.F.Müll.) Lado
heterotypic synonym and basionym  = Tremella hydnoidea Jacq.
heterotypic synonym Ceratium hydnoideum (Jacq.) Alb.& Schwein.

Editor

For a direct editing of synonymy list click on the button  . The list with the selected names and the synonymy overview will get a yellow background (see image).

Now you can add synonyms to the synonymy list by simply dragging them from the selected names list on a name in the synonymy tree view. If you drag the name on the accepted name, it will become a homotypic synonym of the accepted name. If you drag it on a heterotypic synonym, it will become a heterotypic synonym of the accepted name and get the same basionym as the name you dragged it upon. If this name has no basionym, the dragged name will become a homotypic name of the name you dragged it upon. If you want to create a new heterotypic synonym or a synonym with unknown relation to the accepted name, drag the name in the empty space of the tree view.

If you want to correct the synonymy you can drag the names within the synonymy overview either on another name to create a homotypic synonym or into the free space underneath the names to create a heterotypic synonym to the accepted name.

To remove a name from the lists of synonyms, choose it in the tree view and click on the button.

Isonyms, duplicates and orthographic variants

Some names are a variant spelled exactly as another name but with deviating citation of the author(s). These might be a name with wrong citation of the publishing or recombining author(s) or an isonym sensu ICBN. To change the type of the synonymy to an isonym choose the taxon and change the syn. type e.g. to “isonym”. In the synonymy overview list the isonyms, duplicates etc. are indicated by square brackets “[duplicate: … ]”.

Ignored datasets

If it should happen, that a dataset that is ignored is included in a synonymy in the form that another name is referring to this ignored name, the system will not be able to generate the synonymy properly. To detect ignored datasets in the synonymy choose “Query → Show ignored data” from the menu (see chapter Ignored data for further details). Ignored dataset will than be shown with red letters in the synonymy as shown below.

The information about the synonymy is related to opinions of the editors and are allways restricted to a certain project. The data of the synonymy are stored in table TaxonSynonymy. The data of the accepted names are stored in table TaxonAcceptedName.

Apr 9, 2025

Diversity Taxon Names

Lists for taxonomic names

With DiversityTaxonNames you can document list for taxonomic names like e.g. checklists. The taxon lists may refers to a project defined in DiversityProjects (see Administration - User … in the menu). To edit the taxon lists choose Administration → Taxon lists … from the menu. A window as shown below will open, where you can enter, edit or delete taxon lists. The administrative functions are only available for administrators. 

 

For the detailed documentation of the Taxon lists please use DiversityProjects. To load projects into the list, click on the Download projects from DiversityProjects button (see above). A window as shown below will open. If several Databases for DiversityProjects are available on your server you have to choose one of these. The projects available in the DiversityProjects database will be listed as shown below where those already present are checked and green, while missing projects are red. Check those projects you need as lists and click the Start download button.  

For access to the related data choose the tab Taxon lists (see below).  

 

To enter a new list, click on the button. This will open a window where you can choose from the available taxon lists. Choose the list in which you want to include your name and click OK.

Area

The geographical area can be definded for a single name (via Distribution) or for the whole taxon list. The entries refer to the World geographical scheme for recoding plantdistributions. To enter the geographic area for the whole list, click on the button. A form will open where you can choose geographical places from the module DiversityGazetteer. To open the link to the module, click on the button and search for the region as described in the chapter Module related entry.

If you need a certain region not provided in the list, just type the name of the region and click OK. The new region will be listed directly underneath the list (see below).

 

 

References

For every name in a taxon list, you can enter the references where the informations for the list are derived from. To add a reference, select the list for which you want to add a reference and click on the button. The entry for the reference will appear underneath the taxon as shown below. To edit this entry, select it in the hierarchy and use the contols underneath the tree. You may link the reference to an external source like DiversityReferences or one of the provided webservices.

If you want to transfer the informations of a reference together with depending analysis and distribution entries to another name, select the reference in the tree und click on the button. As a result you can use the button to insert these informations at a different place.

 

Analysis

For a name within a list, you can enter an analysis either directly for the name or a reference linked to this name. Select the name or the reference in the tree and click on the  button to enter a new analysis. Depending on the definition of the analysis To edit the analysis used within the database, select it in the tree and use the area below the the tree. Depending on the definition of the analysis (see above) the values are either typed or selected from a list.

To prevent a analysis from publication e.g. via the cache database in DiversityCollection, enter a withholding reason in the corresponding field . The sorting in an interface is set via the sorting. To check the current sorting click on the button.

 

Distribution

For every entry in a taxon list, you can document the distribution of a taxon (see below). This information may be linked to the taxon or a reference (see below).

 

Choose either the list taxon or the reference in the tree and click on the  button to insert a new distribution. The entries refer to the World geographical scheme for recoding plantdistributions. A form will open where you can choose geographical places from the module DiversityGazetteer. To open the link to the module, click on the button and search for the region as described in the chapter Module related entry.

If you need a certain region not provided in the list, just type the name of the region and click OK.

 

Specimen

For every entry in a taxon list, you can document the collection specimen linked to this taxonomic name (see below). The entries may be linked to the module DiversityCollection. To enter a distribution for the specimen, use the button. A window will open (see above), where you can select a geographic region as defined in the  World geographical scheme for recoding plant distributions

 

Export

To export the taxon lists resp. checklist, choose Data → Export taxon list … from the menu. A window as shown below will open. By default the data will be exported as XML (see below). Choose a schema file of your choice to convert the XML-output in a HTML document. You have several options for the export in regard of the names as shown in the window below. The export may be based on the names in the list and can be restricted to the accepted names among these (see below - left). In the second option (see below - right), the accepted names for all names in the list will be selected and the taxon list will contain only these names and optionally their synonyms. Regarding the synonyms, if you want to suppress the export of isonyms and duplicates, use the according checkbox. For long lists, the second method will be rather time consuming, as the synonymy must be checked for every single name. The synonymy for the exort may be derived from any available project. The path of the exported file (either *.xml or *.html) is shown in the field Export file at the bottom of the form. The names in the list may be sorted according to the names or the synonymy where synonyms will be inserted after their assigned accepted names. The format the XML-export with a schema file of your choice, choose the schema file and click on the button.

 

The tables involved in the storage for the taxon list are documented in the taxon list tables part.

Apr 9, 2025

Subsections of Taxon List

Diversity Taxon Names

Analysis in taxonomic lists

To administrate the analysis categories within the taxon lists choose Administration - Analysis … in the menu.

 

The button will open a table editor window where you can edit certain parts of the data.

To export the selected analysis use the button.

To check the sorting of the analysis click on the button. A window will open listing all analysis categories sorted according to the IDs.

The tables involved in the storage for the taxon list are documented in the taxon list tables.

Feb 11, 2025

Diversity Taxon Names

Access restriction to taxonomic lists

If the access of a user should be restricted to names within a taxonomic list, choose Administration - List user … in the menu. A windows as shown below will open, where you can add and remove lists thats should be accessible by a user. The users with no restriction are listed in the left. To restrict a user to a certain list, choose the user in the  list, the list the user should be restricted to and click on the button. The lists a restricted user has access to are listed in the list. To add or remove lists, use the < and > buttons.  

 

The tables involved in the storage for the taxon list are documented in the taxon list tables part.

Jul 19, 2024

Diversity Taxon Names

Edit Taxa In List

To edit the taxa in a spreadsheet, choose View → Edit taxa in list … from the menu. A window will open where all names from the query will be listed.

Customize visibility of fields

To change the selection of the visible fields, click on the Column visibility button. A window as shown below will open, where you can change the visibility of the columns.

 

Customize sequence

To change the sequence of the columns, just use your mouse to drag the columns to the position of your choice.

Sorting of the data

To sort the data in the grid just click in the header of the column which you want to use as sorting column. The sorting sequence will be kept even if you change values in this column. That means that if you change a value in the sorting column the changed dataset will be placed at the new position according to its new value. The sorting of a column will be indicated with an arrow for the direction of the sorting (up or down).   

Change to data in main form

To change to a name in the main form, click on the , use the button. 

Formatting the grid

To adapt the width of the columns or the height of the rows either drag the border with the mouse, double click the border to get the optimal size for one column or respectively or click on the button for an optimal height of the rows or the button for an optimal width of the columns.

 

Apr 9, 2025

Diversity Taxon Names

Data

To save the changes in a dataset click on the button.

To undo the changes in a dataset click the button. This will recover the original data unless the changes had been saved or changes were done in the synonymy.

To create a new entry in the database, click on the  button above the search result listbox. A window will open where you can add additional projects to the list in which the new name shoul be included (see below). By default only your current project will be selected.

 

Leave only those projects the new name is related to. Click OK to create a entry with the name “New Taxon”.

To copy a taxon, choose it from the list and click on the button . As with the creation of a new dataset you can insert the copy of a name into other projects (see above).

To delete a dataset click on the button .

Jul 19, 2024

Diversity Taxon Names

Taxonomic Name

The header shows the name, the ID and the version of the name - these data can not be edited. If a dataset should be ignored, check the checkbox “Ignore”. In the last field you can enter a revision level for the dataset. If you want to inspect the history of a dataset click on the  button.

 

Data concering the taxonomic name including the authors are entered in the corresponding area (see image below).

 

Depending on the taxonomic rank, the form will show only the fields available for this rank.

If the genus is linked to an entry in the database, the field for the genus will change as shown here and the program will not allow you to edit the name. To edit the genus of the name, click the button to release the link to the genus. The list of genera is restricted to the project you selected. If a hierarchy is availble for the selected genus the hierarchy will be automatically inserted for the current name.

If the name is a hybrid , check the checkbox “Is hybrid” to get access to the fields for hybridization.

Apr 9, 2025

Diversity Taxon Names

Authors

For names according to an official code (ICBN) the authors of the name should be given.

To edit the authors using standard abbreviation list click on the Button. This will open the form for editing the authors.

here you add (click on the button) and remove (click on the button) authors according to the standard list. You can choose the standards for the abbreviation from the provided lists.

For names not following an official code authors should not be given. Instead, include a descriptive phrase in the field Non nomenclatural name suffix.

To edit the selected list of the authors click on the Edit author list button.

Jul 19, 2024

Diversity Taxon Names

Nomenclature

DiversityTaxonNames was developed to follow, for the most part, the International Code of Botanical Names (ICBN). Other codes like the code for names in zoology have not yet been taken into account. Information corresponding the nomenclature are entered in the provided fields as shown below.

Jul 19, 2024

Diversity Taxon Names

Taxonomic reference and protologue

Details about the protologue are entered in the area Taxonomic reference / Protologue

 

To enter a website for the protologue either enter the link in the field or click on the button to start a query. This will open simple browser where you can search the URL for the protologue as shown below.

 

Apr 9, 2025

Diversity Taxon Names

Typification

Details about the type can be entered in the area “Typification”.

 

The navigate through the data use the , , and button. To add a new typification use the button, to delete the current dataset, use the button.

Jul 19, 2024

Diversity Taxon Names

Hybrids

As for the time being a definite rule for the creation of a valid taxonomic name on the basis of the parent names is not available. Therefore the name is build from the genus and all the rest placed in the field for the epithet. Some examples for hybrids are: 

  • Asplenium x alternifolium Wulfen.
  • Coeloglossum x Dactylorhiza Coeloglossum viride x Dactylorhiza majalis subsp. praetermissa
  • Ononis repens subsp. procurrens x spinosa subsp. spinosa
  • Salix (caprea x viminalis) x (purpurea x viminalis)
  • Salix alba var. vitellina x babylonica x matsudana
  • Symphoricarpos albus var. laevigatus x microphyllus x orbiculatus

As soon as a rule is available the name can be generated from the parent names that are entered as described below.

If a taxon is a hybrid, check the checkbox to open the part for the entry for the parents of the hybrid. You can determine up to 4 parents for a hybrid as shown in the figure below

 

Jul 19, 2024

Diversity Taxon Names

Common names

A name can have several common names. These are entered in the section Common names. To add or delete a common name use the  and  buttons.

The data of the common names are stored in table TaxonCommonName.

Apr 9, 2025

Diversity Taxon Names

Ignored Data

To remove data from the creation of the hierarchy, the synonymy etc. on one hand and not to delete them but to keep the information, use the Ignore option. All data set to Ignore are no longer involved in the normal queries, but kept to ensure e.g. links from other modules. To display ignored data, select Query - Show ignored data in the menu.

Synonyms

In the example below, a synonym was set on ignore.

 

If it should happen, that a ignored name is included in a synonymy and a name within the synonymy is referring to this ignored name, the system will not be able to generate the synonymy properly. Ignored names will than be shown with red letters in the synonymy overview as shown below.

Accepted names

In the example below, the entry for an accepted name was set to ignore, now showing this information side by side with the current setting of the name as a synonym.

If several entries for an accepted name exist, a list will appear at the left side as shown below where to top entry (0) is the valid entry, while all other entries (> 0) are set to ignore (see below).

Hierarchy

As with the accepted names, ignored data will be listed as shown below in a list where to top entry (0) is the valid entry, while all other entries (> 0) are set to ignore. 

 

 

Jul 19, 2024

Diversity Taxon Names

Geography

Details about the type can be entered in the area “Geography”.

The geographical distribution of the type specimen according to the protologue can be typed in the field Locality of the area Typification. In the area Geography names according to a standard can be entered as a list as shown above. To remove an entry from the list click on the button. To add an entry click on the button. A form will open where you can choose geographical places from the module DiversityGazetteer. To open the link to the module, click on the  button and search for the region as described in the chapter Module relatedentry.

 

The data of the geography are stored in table TaxonGeography.

Apr 9, 2025

Diversity Taxon Names

Resources

Resources related to a taxon can be added in the area “Resources”. Use the (add), (remove) and (save) buttons to handle the resources.

Resources are sorted by their order which can be set in the field shown below. If a resource should not be published, enter any text in the field. The title will be shown e.g. in a chart query in the tooltip of the image.

The data of the resources are stored in table TaxonNameResource.

Mar 20, 2025

Diversity Taxon Names

Import Export

  • Export

    Exporting data to text files

  • Import

    Importing data from text files

Apr 16, 2025

Subsections of Import Export

Diversity Taxon Names

Import

To import taxonomic names you have two options. Either use an import taxonomic names including evaluation of names according to codes like ICBN and automatic splitting of the names or a generic import wizard providing the additional possibilty to import synonyms and hierarchies.

Apr 16, 2025

Subsections of Import

Diversity Taxon Names

Import List

To import taxonomic names, choose Data → Import taxonomic names … from the menu. A window as shown below will open. Choose the encoding of your datasource, that means if your datasource was encoded with ASCII or a unicode format. To ensure a correct import of special signs please provide resp. convert your data in one of the available formats. You must choose a Project, in which your data should be imported. You may choose a Taxon list and a Datasource and if the names should be imported as accepted.

If there are additional columns in the source file (separated by tab) you may add these unsing the Add column button (see below) in the sequence as found in the source file. The additional columns will be included in the analysis of the data as shown below. To remove a column use the button.

To start the analysis of the data, just click on the button to open the source file. If you want to re-analyse a file with new settings, click on the   button. To send a feedback, use the button. If the names should be linked to higher taxa, check the Link taxa to genera if present option. The names can be compared with existing names within the current project or the whole database. If you compare the names with the whole database, you can insert a link for the current project for identical names that are missing in the project.

 

Your names will be listed as shown in the image above. If an error (e.g. special signs converted with the wrong encoding)

 

or a similar name

 

or an identical name

 

is found these will be marked as shown above and the names of your list will not be imported unless you check the according field (second column - Import name). If you changed one of the options, click on the Requery button to see the result.

To start the import, click on the according button Start import.

 

Apr 9, 2025

Diversity Taxon Names

Wizard

Import wizard for tab separated lists

With this import routine, you can import data from text files (as tab-separated lists) into the database. Choose Data → ImportWizard and then the type of data that should be imported, e.g. Import Taxa … from the menu. A window as shown below will open that will lead you through the import of the data. The window is separated in 3 areas. On the left side, you see a list of possible data related import steps according to the type of data you choosed for the import. On the right side you see the list of currently selected import steps. In the middle part the details of the selected import steps are shown.

Choosing the File

As a first step, choose the File from where the data should be imported. The currently supported format is tab-separated text. Then choose the Encoding of the file, e.g. Unicode. The Start line and End line will automatically be set according to your data. You may change these to restrict the data lines that should be imported. The not imported parts in the file are indicated as shown below with a gray background. If the First line contains the column definition this line will not be imported as well. If your data contains e.g. date information where notations differ between countries (e.g. 31.4.2013 - 4.31.2013), choose the Language / Country to ensure a correct interpretation of your data. Finally you can select a prepared Schema (see chapter Schema below) for the import.

 

Choosing the data ranges

In the selection list on the left side of the window (see below) all possible import steps for the data are listed according to the type of data you want to import.

The import of certain tables can be paralleled. To add parallels click on the button (see below). To remove parallels, use the button. Only selected ranges will appear in the list of the steps on the right (see below).

To import informations of logging columns like who created and changed the data, click on button in the header line. This will include a additional substeps for every step containing the logging columns (see below). If you do not import these data, they will be automatically filled by default values like the current time and user.

Attaching data

You can either import your data as new data or Attach them to data in the database. Select the import step Attachment from the list. All tables that are selected and contain columns at which you can attach data are listed (see below). Either choose the first option Import as new data or one of the columns the attachment columns offered like SeriesCode in the table Series in the example below.

If you select a column for attachment, this column will be marked with a blue background (see below and chapter Table data).

 

Merging data

You can either import your data as new data or Merge them with data in the database. Select the import step Merge from the list. For every table you can choose between Insert, Merge, Update and Attach (see below).

The Insert option will import the data from the file independent of existing data in the database.

The Merge option will compare the data from the file with those in the database according to the Key columns (see below). If no matching data are found in the database, the data from the file will be imported, otherwise the data will be updated..

The Update option will compare the data from the file with those in the database according to the Key columns. Only matching data found in the database will be updated.

The Attach option will compare the data from the file with those in the database according to the Key columns. The found data will not be changed, but used as a reference data in depending tables. 

 

Table data

To set the source for the columns in the file, select the step of a table listed underneath the Merge step. All columns available for importing data will be listed in the central part of the window. In the example shown below, the first column is used to attach the new data to data in the database.

A reminder in the header line will show you what actions are still needed to import the data into the table:

  • Please select at least one column   = No column has been selected so far.
  • Please select at least one decisive column   = If data will be imported depends on the content of decisive colums, so at least one must be selected.
  • Please select the position in the file   = The position in the file must be given if the data for a column should be taken from the file.
  • Please select at least one column for comparision   = For all merge types other than insert columns for comparision with data in the database are needed.
  • From file or For all   = For every you have to decide whether the data are taken from the file or a value is entered for all
  • Please select a value from the list   = You have to select a value from the provided list
  • Please enter a value   = You have to enter a value used for all datasets

The handling of the columns in described in the chapter columns.

 

Testing

To test if all requirements for the import are met use the Testing step. You can use a certain line in the file for you test and then click on the Test data in line: button. If there are still unmet requirements, these will be listed in a window as shown below.

If finally all requirements are met, the testing function will try to write the data into the database and display any errors that occurred as shown below. All datasets marked with a red background, produced some error.  

To see the list of all errors, double click in the error list window in the header line (see below).

If finally no errors are left, your data are ready for import. The colors in the table nodes in the tree indicate the handling of the datasets: INSERT, MERGE, UPDATE, No difference. Attach, No data. The colors of the table colums indicate whether a colum is decisive , a key column or an attachment column .  

If you suspect, that the import file contains data allready present in the database, you may test this an extract only the missing lines in a new file. Choose the attachment column (see chapter Attaching data) and click on the button Check for allready present data. The data allready present in the database will be marked red (see below). Click on the button Save missing data a text file to store the data not present in the database in a new file for the import. Please keep in mind, that this comparision will be performed without any transformations of the data, that means the data in the file must match exactly those in the database. 

 

Import

With the last step you can finally start to import the data into the database. If you want to repeat the import with the same settings and data of the same structure, you can save a schema of the current settings (see below).

Schedule for import of tab-separated text files into DiversityTaxonNames
Target within DiversityTaxonNames: TaxonName
Schedule version: 1 Database version: 02.05.14
Lines: 3 - 5 First line contains column definition: ?
Encoding: ANSI Language: US

Tables

TaxonName (TaxonName)
Merge handling: Merge

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
NameID 2027929 Interface
TaxonomicRank fam. Interface
GenusOrSupragenericName ? ? 0 File
NomenclaturalCode 3 Interface

TaxonNameProject (TaxonNameProject)
Parent: Merge

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
NameID ParentTable
ProjectID ? ? 58 Interface

TaxonAcceptedName_1 (TaxonAcceptedName)
Parent: TaxonNameProject
Merge handling: Insert

Column in table ? Key Copy Pre Post File pos. Transformations Value Source Table
ProjectID ParentTable
NameID ParentTable

 Lines that could not be imported will be marked with a red background while imported lines are marked green (see below).

If you want to save lines that produce errors during the import in a separate file, use the Save failed lines option. The protocol of the import will contain all settings acording to the used schema and an overview containing the number of inserted, updated, unchanged and failed lines (see below).

 

 

Apr 9, 2025

Subsections of Wizard

Diversity Taxon Names

Import Wizard Tutorial

This tutorial demostrates the import of a small file into the database. The example file is included in the software.  At the end of this tutorial you will have imported several datasets and practiced most of the possibilities provided by the import wizard. The import is done in several steps to demonstrate the functionality of the wizard. Please keep in mind, that this tutorial will only work as shown, if the names contained in the file are not already present in the database.

 

 Step1 - Import of the taxa

Choose Data → Import Wizard → import Taxa … from the menu. A window as shown here below will open. Click on the button to open the file ImportTutorial.txt shipped with this application. In addition to the preselected steps, select the step Common names to import the common name contained in the file. In the Merging step leave all tables as Insert (see below). 

In the Taxon step, set the first column NameID to Generate new value. Then select the additional columns as shown below. For the column TaxonomicRank choose For all and select species from the list. For the column NomenclaturalCode choose For all and select Botany (incl. Mycology) from the list. All columns besides NameID, NomenclaturalCode and TaxonomicRank are set on From file and the colums are set as shown in the image below.

The column CombiningAuthors needs a transformation. To add this, click on the button. Enter a translation as shown below where the value NULL is translated to nothing.

Select a translation transformation (click on the button) and press the button to enter a translation (see below).

Press Test the transformation to visualize how the data would be imported (see below).

To allow the import of this table, choose the 2 columns GenusOrSupragenericName and SpeciesEpithet as Decisive columns (see below). 

In the step Common name choose the column CommonName as Decisive column and From file (column 6) for and For all for the other 3 columns as shown in the image below.

In the step Project select For all and the project DiversityWorkbench from the list and select this column as Decisive column. 

In the step Accepted name no further action is needed. 

In the step Testing check if you missed any settings described above. A test should return a result as shown below. 

Finally   Import the taxa. If no errors occur, the import should return a result as shown below. 

 Proceeded with Steps 2 & 3 - Import of the higher taxa

Apr 9, 2025

Subsections of Tutorial

Diversity Taxon Names

Import Wizard Tutorial

Hierarchy

 Step2 - Import of the higher taxa - family

To import the hierarchy, the higher taxa must be imported first. Choose the same file as in the first step for the import. The data for the higher taxa are not unique in the file. Therefore in the Merging step, choose Merge for all tables (see below).

In the Taxon step, set the first column NameID to Generate new value. Then select the column
TaxonomicRank and choose For all and select family from the list. Finally select the column GenusOrSupragenericName, set it as Decisive columns, set it on From file and the column 1 as source (see below).

In the step Project select For all and the project DiversityWorkbench from the list and select this column as Decisive column. 

In the step Accepted name no futher action is needed. 

Finally Import the taxa. If no errors occur, the import should return a result as shown below. Only the green lines are imported. The yellow lines are found identical to the already imported data and are therefore not imported. 

 

 Step3 - Import of the higher taxa - order

Next we Import the order. Follow the steps as described for the family above with the difference that now for TaxonomicRank we select order from the list and choose column 0 as source for the column GenusOrSupragenericName taxa. If no errors occur, the import should return a result as shown below. Only the green lines are imported. The yellow lines are found identical to the already imported data and are therefore not imported (see below). 

 

 

 Proceeded with Step 4 - Import of the hierachycal relation between families and the order

 

 

Apr 9, 2025

Diversity Taxon Names

Import Wizard Tutorial

Species & Family

 Step 4 - Import of the hierachycal relation between species and families

To import the hierarchical relation between the taxa choose Data → Import Wizard → Import Hierarchy … from the menu. For every hierarchical rank, you have to import the relations between the taxa. We start with the relations from the species to the family (the genus as intermediate rank between species and family is omitted in this example).

As described in the previous steps, open the file ImportTutorial.txt shipped with this application. In the Merging step leave the table on Insert (see below).

In the Hierachy step, select the columns  Taxon (Name or ID) and Higher taxon (Name or ID) as Decisive columns (see below).

For the column ProjectID, select For all as shown below and select the project of your choice from the list (e.g. DiversityWorkbench if available).

As the file does not contain the IDs of the name, we let the program determine the ID on basis of the name. To enable the program to detect the ID we need to provide the whole name from the data in the file. We start with the column Taxon (Name or ID). As first step, click on the button to set the source for the genus, the first part of the taxonomic name. A window as shown below will open. Mark the column as shown below an click on the OK button.

Next we need the species epithet as second part of the names. Click on the button to add another column. A window as shown below will open where where the previous selected column for the Genus is marked with 1. We select the column containing the species epithet (see below) and click OK.

Now we need the authors as last part of the names. Again click on the button to add a column and select the source as shown below.

As shown below, enter a space in the Postfix for the first 2 columns.

If combining authors do exist for a name, the authors of the basionym are set in brackets. To ensure the correct build-up of the name, we need to add a transformation. Click on the button to enter the a filter as shown below where an opening bracket ( is inserted in dependence of the content of the column of the combining authors.

To set the column for the filter, click on the button and choose the column containing the combining authors as shown below.

The final Transformation should look like shown below.

After adding the optional opening bracket we add the authors of the basionym. Click on the button and select the column as shown below.

As final step for the authors of the basionym we need the optional closing bracket. Click on the button and select the column as shown above. For the new colum enter another filter transformation as shown below. To set the column for the filter, click on the button as described for the opening bracket.

Finally we need the combining authors, provided they do exist. Click on the button and select the column containing the combining authors. As these are missing for some names we have to add a transformation where the content NULL is translated into nothing. Click on the button to add a transformation and in the window that will open, click on the button to add a  translation (see below).

To add a value that should be translated, click on the button and type NULL into the window as shown below.

The final transformation should look like shown in the image below.

The final build-up for the Taxon should look like in the image below.

Now we enter the higher taxon, in this example the family. Click on the button and choose the column containing the family as shown below.

Now the Hierarchy step is finished and should look like shown below.

In the Testing steps use the test for a check if you missed any settings described above. The result of the test should appear like shown below.

Finally Import the data according to your settings. The result of the import should appear like shown below.

 

 Proceeded with Step 5 - Import of the hierachycal relation between families and the order

 

Apr 9, 2025

Diversity Taxon Names

Import Wizard Tutorial

Family & Order

 Step 5 - Import of the hierachycal relation between families and the order

After the relations between the species and the families are imported we proceed with the hierarchical relation between families and the order. Choose Data → Import Wizard → Import Hierarchy … from the menu. 

As described in the previous steps, open the file ImportTutorial.txt shipped with this application. In the Merging step set the table on Merge (see below).

As described in the previous step, select the project of your choice and set the columns Taxon and Higher Taxon to From file. 

Click on the button to select the source for the family (see below).

… and the orders as shown below.

Additionally you must select these columns as Key columns, used to compare the data from the file with the content in the database (see below).

A final test before importing the data turns positive (see below).

Now we are ready to import the relation into the database. For every family this relation will be imported only once (see below).

As a last step, search for the highest taxon “Russulales” in the hierarchy in the main from and click on the button set hierarchy (see below) .

After the hierarchy for the Russulales is set, all imported name will show the complete hierarchy as shown in the example below.

 

 

 Proceeded with Step 6 - Import of the synonyms

 

Apr 9, 2025

Diversity Taxon Names

Import Wizard Tutorial

Synonyms

 Step 6 - Import of the synonyms

To import the synonyms, choose Data → Import Wizard → import Synonyms … from the menu. A window as shown below will open. 

In the Taxon step choose From file for the Genus and select the colums
Synonym1 as shown below.

To get only the genus from the name in the source, add a transformation for the column. Click on the button and in the window as shown below add a cutting transformation. Enter a space as Splitter. A Test of the transformation should produce the result as shown below.

Next select the SpeciesEpithet and again From file (see below).

Select the same column as for the genus (see below).

… and as for the genus add a cutting transformation with a space as splitter but this time set the Position to 2 (see below).

Choose the columns for the genus and the epithet as Decisive columns (see below). Next we turn to the authors of the synonym. Select the From file for BasionymAuthors …

And choose the SynonymAut1 Column as shown below.

To cut out the basionym authors we add a cut transformation as shown below. Enter ) as splitter.

Next we add a  Replace transformation to get rid of the leeding bracket (see below).

Now we turn to the combining authors …

Again we add a cut transformation with ) as Splitter, but 2 as Position (see below). 

The window now should look like below. 

As a last entry in the taxon step we choose Botany for the Nomenclatural Code (see below).

In the Project step select For all, choose the project where you want to import the data and set this column as Decisive column.

In the Synonymy step select From file for the accepted name. Now we must combine the accepted name from the entries in the file to match the entry in the database.

Select the Genus column for the first part of the accepted name (see below).

Click on the button to add another column and choose the Species column as shown below as source.

For both columns enter a space into the Postfix (see below).

Next we add the authors. For the basionym authors we need to add brackets if combining authors do exist. Select the Author column …  

… and add a filter transformation (see below). Here we choose Import fixed value and enter ( as a value. As condition we choose that the colum of the combining autors should not contain the string NULL. 

To complete this transformation click on the button and select the column containing the combining authors (see below).

To add the basionym authors themselves, click on the  button and choose the corresponding source as shown below.

Next we need the closing bracket for the basionym authors. As before we click on the button and for the new entered columns we add a filter transformation as shown below. Enter ) as fixed value and as before select that the source for the combining authors should be unequal to NULL.

Finally we get the values for the combining authors. Add another column and select the corresponding column in the source (see below).

To remove the NULL value, we add a  translation transformation. As only string that should be translated, we click on the  button and enter NULL (see below).

Now the translation should look like below.

As final action in the Synonym step we choose the column for the Acc.name as Decisive column (see below).

A final Testing will detect any missed settings.

After the final test is passed, we can Import the data as shown below. The schema will automatically be created and is available for subsequent imports. 

Apr 9, 2025

Subsections of Export

Diversity Taxon Names

Export hierarchy and synonymy

To export the taxonomy, including the hierarchy and the synonymy, select the corresponding taxon, choose Data → Export → Export hierarchy and synonymy… from the menu.

To see the whole hierarchy, select the desired node in the hierarchy tree and click on the button besides the hierarchy.

A window as shown below will open

 

The data you in the export will depend upon the taxon you selected in the main form. So if e.g. you want to export the names within a genus, select the genus in the main form.

If you want to include the synonyms, check Restrict to accepted names and Show synonyms and click on the button (see below).

 If you start the export without any schema file, you will get the data strutured as xml (see below).

To format the data, specify the schema file containing your preferred format as shown below. 

You can export the data including all higher taxa (see above) or starting with the taxon for which you selected the export (see below). mao format the data, specify the schema file containing your preferred format as shown below.

To export only the higher taxa, you can restrict the lowest rank to e.g. the genus as shown below.

If you choose the option Summary, the numbers of the differnet hierarchical levels will be listed at the bottom of the report (see image below)

Apr 9, 2025

Diversity Taxon Names

Export List

To export lists, including information about the distribution or the synonymy, choose Data → Export → Export taxon list … from the menu. A window as shown below will open, where you can choose the taxonomic list and the project where the synonomy of the taxa is documented.

 

Choose a Schema file and the options for your export. Than click on the Create the taxon list to start the export. The resulting html file (see below) will be named according to the choosen schema file.

If you miss to choose a schema file, the original XML file will be shown (see below). To convert this into a html file, choose a schema file and click the button.

Apr 9, 2025

Diversity Taxon Names

Fequently Asked Questions

Editing

  • Modules
    • How does DTN interact with other modules in the DWB
      • see chapter Verbindung anderer Module auf DiversityTaxonNames
      • and the video Video starten.
        Aufbau der Workbench, Position der Darstellung im Client, Start mit leeren Listen, Verbinden zu Quelldatenbanken Anzeige von Übersicht im Client, Setzen des Pfads zu DD-Client, Öffnen eines Datensatzes mit DD, Beispiel mit DC, Einschränkung auf Typusbelege, Öffnen eines Datensatzes mit DC
    • How to propagate changes to linked data
      • see chapter Aktualisierung verknüpfter Datensätze
      • and the video Video starten.
        Vorstellung der Beispieldaten in DTN und DC, keine Aktualisierung bei Änderung irrelevanter Inhalte, Aktualisierung bei Änderung relevanter Inhalte, Einbindung von Datenbanken in Aktualisierung, kein Einschluss von Datenbanken die über LinkedServer einschlossen sind, Demonstration der Aktualisierung an 2 Beispielen (Art, Familie)

Export

  • How to export data from a list
    • see chapter Aus Liste
    • and the video Video starten.
      Vorstellung der Exportoptionen. Optionen in der Taxonliste, Auswahl von exportierten Spalten, Anpassung von Spaltenbreite und Höhe, Art der Erzeugung der Exportdatei (neu oder Anhängen), Sortieren der Daten, Exportieren der Daten und Ansicht der Datei.

Maintenance

  • How to clear self referencing synonyms
    • see chapter Bereinigung selbstbezogener Synonyme
    • and the video Video starten.
      Aufbau in Datenbank, Aufruf von Maintenance - Synonyms, 2 Optionen: Ignore und Remove, Ansicht von Datensätzen aus der Liste in der Datenbank, Demonstration - Löschen eines Datensatzes, Demonstration - Ignorieren eines Datensatzes
  • How to update the cache for the synonyms
    • see chapter Aktualisierung des Zwischenspeichers der Synonymie
    • and the video Video starten.
      Ermittlung der Synonymy für einzelne Namen, Funktion für Ermittlung der Synonymy, Cachetabelle mit Inhalt, Button für Aktualisierung eines Namens und Menüpunkt zur Aktualisierung der gesamten Liste

Diversity Taxon Names

General

General aspects of the software

  • Feedback

    Sending feedback for the software

Apr 16, 2025

Subsections of General

Diversity Taxon Names

Feedback

If you have suggestions for improvement, need any changes in the programm or encouter an error you can give a feedback to the administrator. Click on the ALT and PRINT buttons to get a screen shot of your current form. After creating the screen shot choose Help - Feedback from the menu to open the feedback form as shown below.

 

Click on the Insert image button to insert the screen shot and give a comment about your problem. In the field Topic enter the topic of your feedback (will appear in response e-mail). The Priority can either be empty or set to 3 levels:

  • urgent
  • as soon as possible
  • nice to have

If necessary, enter a date in the field ToDo until when you would like to have the task described in you feedback be solved. Then click on the  Send feedback button to send your feedback to the administrator. If you would like to receive a message when the problem you described is solved, please enter you e-mail address in the field below the description.

To inspect your former feedbacks choose Feedback history from the menu. A window will open where you can browse your past feedback together with the state of progress.

Apr 16, 2025

Diversity Taxon Names

Internals

For users that need more detailed information about the software including database design etc.

Jul 19, 2024

Subsections of Internals

Diversity Taxon Names

Database

The database for DiversityTaxonNames is based on Microsoft SQL-Server 2008 or higher. The names of the taxa were separated for practical reasons in several databases, each comprising a certain range of taxa. There is one master version, DiversityTaxonNames, containing the names of all databases and several databases containing the complete datasets including synonymy, hierarchy etc. for the following groups:

Database Taxa Source
DiversityTaxonNames_Fungi higher fungi including lichens LIAS
DiversityTaxonNames_Myxomycetes slime moulds NomenMyx
DiversityTaxonNames_Plants higher plants Species 2000, Tropicos, IPNI, Precis, …
DiversityTaxonNames_Vertebrates vertebrates SAPM, …

To access any database, you must specify the server where the database is located. For the configuration of this connection click on the button or choose Connection, Database… from the menu. If you got a new version of the client you can transfer the settings for the previous version: Choose Connetion → Transfer previous settings from the menu. (see Database access for details)

Organisation of the data

The data are organised in several groups, data connected with the  name , data based on the opinion of an editor within a projects , the source of the data and the lists .

TaxonName, TaxonCommonName, TaxonNameTypification and TaxonGeography  are containing the nomenclatural information. Most items are expected to be undisputed nomenclatural facts. Some data items include editorial opinion (nomenclatural status, but also the accepted spelling which may involve orthographical or grammatical corrections as required by ICBN). However, it is expected that within a project agreement can be achieved on the information contained in TaxonName, i.e. collaborators can “correct” information without consultation.

TaxonNameProject document the projects of the names. The access for the users is determined by the projects.

Editor opinion

The tables TaxonHierarchy, TaxonNameResource, TaxonAcceptedName and TaxonSynonymy - represent a higher level of taxonomic opinion, where different editors and different digitized data sources need to be kept separate. This is achieved by making a “Project” attribute part of the primary key. Editors that wish to collaborate and form agreement may work in a single project, editors that desire to define separate opinions work in separate projects. Furthermore, if the opinion is based on published information, the reference and page number may be recorded (in …RefText, …RefID, …RefDetail). The duality of representing editorial opinion and remaining true to a digitized sources causes some problems. For example, a species accepted in a referenced source may not longer be accepted by the project editors. To avoid a further complication of the model, the “IgnoreButKeepForReference” attribute (default “false”) may be set to “true”, indicating that the statement is true from the perspective of the referenced source, but should be ignored when representing editorial opinion.

  • TaxonHierarchy contains information about the hierarchical position of the taxa. For each project, a name may be referred to a single parent taxon. The attribute “NameParentID” may, however, be Null, in which case “HierarchyPositionIsUncertain” should be true.
  • TaxonNameResource contains links to resources, e.g. images of the taxa.
  • TaxonAcceptedName contains the accepted names (“valid or preferred taxon names”). For each project, a name in “TaxonName” may either be accepted (a corresponding record in “TaxonAcceptedName” exists) or not. Examples for not accepted names are synonyms of accepted names and nomenclaturally rejected names.
  • TaxonSynonymy contains names, which are synonym to other names. Here a single name may be a synonym of multiple accepted names (“pro parte synonym”). The “pro parte” or corresponding sensu information is captured in the “ConceptSuffix” attribute, which is part of the primary key.

External sources

TaxonNameExternalID and TaxonNameExternalDatabase document the sources of the names.

Lists

The tables TaxonNameList… contain informations connected to e.g. checklists. In addition to the restriction to projects the access of users may be restricted to certain lists.

 

Overview of the main tables of the database

 

For details about the tables see Data tables and Enumeration tables.

Apr 9, 2025

Subsections of Database

Diversity TaxonNames

TABLES, VIEWS, FUNCTIONS, PROCEDURES, ROLES

The following objects are not included:

  • Logging tables
  • Enumeration tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

TABLES


Table ProjectUser

User with access to a project

Column Data type Description Nullable Relation
LoginName nvarchar (50) ID of the User as stored in table UserProxy NO -
ProjectID int ID of the project. Foreign key, relates to PK of table ProjectProxy NO Refers to table ProjectProxy
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • ProjectProxy

Table ReplicationPublisher

Source providing data for replication

Column Data type Description Nullable Relation
DatabaseName varchar (255) The name of the publishing database NO -
Server varchar (255) The name or address of the server where the publishing database is located NO -
Port smallint The port used by the server YES -
LogCreatedWhen datetime Point in time when this data set was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Name of the creator of this data setDefault value: user_name() YES -
LogUpdatedWhen datetime Point in time when this data set was updated lastDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of the person to update this data set lastDefault value: user_name() YES -

Table SynonymyListCache

Storing results of function SynonymyList

Column Data type Description Nullable Relation
ID int NameID of the selected taxon NO -
ProjectID int ProjectID of the synonymy NO -
NameID int ID of the synonymized name. Refers to the NameID of TaxonName (= foreign key). NO -
DisplayText nvarchar (900) A preformatet textstring for display in a synoymlist YES -
TaxonName nvarchar (500) The name of the taxon including the genus and the species epithet YES -
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) YES -
InfraspecificEpithet nvarchar (200) The epithet of the infraspecific entity YES -
Authors nvarchar (500) The combined authors of this name YES -
SynonymText nvarchar (500) The text string containing the citation of the synonymisation YES -
Prefix nvarchar (5) The prefix as used in synonym lists YES -
Ord int The preferred sequence of the synonyms. The numbers in Ord correspond to the different kinds of the synonyms:
-20 = Accepted name
-10 = Basionym
0 = Homotypic Synonym

0 = Heterotypic Synoyms
x + 1 = Isonym resp. Assigned to like ‘duplicate’, ‘isonym’, ‘orthographic variant’ (will be display after the name it is a variant of)| YES| -| | YearOfPubl| int| The year when the name was published| YES| -| | TaxonNameCache| nvarchar (255)| A full unique version of the name. Generated by the database, not entered by the user (candidate key)| YES| -| | ConceptSuffix| nvarchar (200)| Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc.| YES| -| | ConceptNotes| nvarchar (500)| Notes on the concept of the name, e.g. incl. forms with black apothecia| YES| -| | BasedOnNameID| int| The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID.| YES| -| | SynType| nvarchar (50)| Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’| YES| -| | SynNameID| int| The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key).| NO| -| | NameParentID| int| The NameID of the parent within the synonymy| YES| -|


Table TaxonAcceptedName

TaxonAcceptedName contains the accepted names (“valid or preferred taxon names”). For each project, a name in “TaxonName” may either be accepted (a corresponding record in “TaxonAcceptedName” exists) or not. Examples for not accepted names are synonyms of accepted names and nomenclaturally rejected names.

Column Data type Description Nullable Relation
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module.Default value: 0 NO Refers to table ProjectProxy and table TaxonNameProject
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameProject
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.Default value: 0 NO -
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc.Default value: '’ YES -
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES -
RefURI varchar (255) ReferenceURI: Source publication where synonymization is published (not publication of name!) YES -
RefText nvarchar (255) Free text, esp. where a RefURI is missing. Source publication where synonymization is published (not publication of name!) YES -
RefDetail nvarchar (255) Esp. page number on which the synonymization is published YES -
TypistsNotes nvarchar (255) An internal note of the responsible person concerning this synonymization. This information is NOT included in any report. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • ProjectProxy
  • TaxonNameProject

trgInsTaxonAcceptedName

Setting version of taxon


Table TaxonCommonName

TaxonCommonName contains the common names that are assigned to a scientific name.

Column Data type Description Nullable Relation
NameID int ID taxonomic name. Refers to the column NameID of the table TaxonName (= foreign key). NO Refers to table TaxonName
CommonName nvarchar (220) A common name of the taxonomic name NO -
LanguageCode varchar (2) The 2-letter code of the language of the common name according to ISO NO Refers to table LanguageCode_Enum
CountryCode varchar (2) The 2-letter code of the country where the common name is used according to ISO ISO 3166-1 NO Refers to table CountryCode_Enum
ReferenceTitle nvarchar (220) The title of the reference where the common name was published NO -
ReferenceURI varchar (255) The URI of the reference e.g. as provided by the module DiversityReferences YES -
ReferenceDetails nvarchar (500) Esp. page number on which the common name is published YES -
SubjectContext nvarchar (500) The context in which the common name is used, e.g. pharmacy, food YES -
Transliteration nvarchar (255) Transliteration of the original name YES -
Notes nvarchar (MAX) Notes about the common name YES -
LogInsertedBy nvarchar (50) Who inserted this datasetDefault value: user_name() YES -
LogInsertedWhen smalldatetime The time when this dataset was insertedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
LogUpdatedWhen smalldatetime The last time when this dataset was updatedDefault value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • CountryCode_Enum
  • LanguageCode_Enum
  • TaxonName

trgInsTaxonCommonName

Setting version of taxon


Table TaxonGeography

TaxonGeography is containing the information about the geographic distribution according to the protologue.

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonName
PlaceURI varchar (255) URI (e.g. LSID) within e.g. the DiversityGazetteer for a place (which may have several names) as found in the protologue NO -
PlaceNameCache nvarchar (100) The name of the place NO -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonName

trgInsTaxonGeography

Setting version of taxon


Table TaxonHierarchy

TaxonHierarchy contains information about the hierarchical position of the taxa. For each project, a name may be referred to a single parent taxon. The attribute “NameParentID” may, however, be Null, in which case “HierarchyPositionIsUncertain” should be true.

Column Data type Description Nullable Relation
ProjectID int Each project can implement a different taxonomic hierarchy. Refers to the common project definition in the DiversityProjects module.Default value: 0 NO Refers to table ProjectProxy and table TaxonNameProject
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key). NO Refers to table TaxonNameProject
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.Default value: 0 NO -
NameParentID int Next higher taxon (e.g. the family or subfamily if this taxon is a genus) YES -
HierarchyRefURI varchar (255) Reference URI: Source publication where the hierarchy is published (not publication of name!) as stored e.g. in DiversityReferences YES -
HierarchyRefText nvarchar (255) Free citation, esp. where a HierarchyRefURI is missing. Source publication where the hierarchy is published (not publication of name!) YES -
HierarchyRefDetail nvarchar (255) Esp. page number on which the hierarchy is published YES -
HierarchyPositionIsUncertain bit If the position of this taxon within this taxonomic group is uncertain.Default value: 0 YES -
HierarchyTypistsNotes nvarchar (255) An internal note of the responsible person concerning this hierarchy. This information is NOT included in any report. YES -
HierarchyListCache nvarchar (1000) CALCULATED FIELD: List of higher taxa for faster access: “div.; class; ord.; fam.” YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • ProjectProxy
  • TaxonNameProject

trgInsTaxonHierarchy

Setting version of taxon and HierarchyListCache


Table TaxonName

TaxonName is the nomenclatural information. Most items are expected to be undisputed nomenclatural facts. Some data items include editorial opinion (nomenclatural status, but also the accepted spelling which may involve orthographical or grammatical corrections as required by ICBN). However, it is expected that within a project agreement can be achieved on the information contained in TaxonName, i.e. collaborators can “correct” information without consultation.

Column Data type Description Nullable Relation
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO -
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES -
Version smallint The version of a name record (revision number, internally filled by system)Default value: (1) YES -
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES Refers to table TaxonName
CreationType nvarchar (50) E.g.: taxon based on new type, combination based on a previously publ. name (‘comb. nov.’), new name (’nom.nov.’) introduced to replace a homonym (may occur for genera!), validation of previously invalidly publ. taxon name (’ex’), or unknown. YES Refers to table TaxonNameCreationType_Enum
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank)Default value: N’sp.’ NO Refers to table TaxonNameTaxonomicRank_Enum
GenusOrSupragenericName nvarchar (200) If rank is above species: Name of taxon above species level (currently accepted spelling). Includes infrageneric taxon names, genera, families, etc. NO -
SpeciesGenusNameID int If rank is species or below: NameID of the Genus name. Refers to same table with TaxonomicRank = genus. YES Refers to table TaxonName
InfragenericEpithet nvarchar (200) If rank below genus and above species: Name of infrageneric taxon above species level (currently accepted spelling). Includes subgenus, series, etc. YES -
SpeciesEpithet nvarchar (100) The species name part of the species name, for example ‘alba’ in ‘Abies alba’. YES -
InfraspecificEpithet nvarchar (100) The epithet of the infraspecific entity YES -
BasionymAuthors nvarchar (100) The authors of a newly created name. For all taxonomic ranks, only for ‘comb. nov.’ or ’nom. nov.’: Author(s) of the basionym (will be displayed in ‘()’, do not enter the parentheses), abbreviated according to authors standard YES -
CombiningAuthors nvarchar (255) The names of the combining authors if the name is base on another older name (e.g. combined into a different genus) YES -
PublishingAuthors nvarchar (255) If the authors of the taxon differ from the authors of the publication: the latter (…‘in ’ Publishing authors … ) YES -
SanctioningAuthor nvarchar (100) Sanctioning is a special instrument available for fungi to allow the starting date of taxonomy to be identical with higher plants, but preserve names used by Fries (Fr.) and Person (Pers.) YES -
NonNomenclaturalNameSuffix nvarchar (200) A suffix for concept names not included in any nomenclatural code. If present fields for authors and typification must be empty and NomenclaturalCode set to ’not under code’. YES -
IsRecombination bit True if the name is a recombinationDefault value: (0) NO -
IsHybrid bit If checked (or ‘True’), the new taxon is a hybrid with or without a hybrid epithet.Default value: (0) YES -
HybridNameID1 int If IsHybrid is checked (or ‘True’): Name of hybrid species 1. Refers to NomID code of publ. TaxonomyName (= foreign key). YES Refers to table TaxonName
HybridNameID2 int If IsHybrid is checked (or ‘True’): Name of hybrid species 2. Refers to NomID code of publ. TaxonomyName (= foreign key). YES Refers to table TaxonName
HybridNameID3 int If IsHybrid is checked (or ‘True’): Name of hybrid species 3. Refers to NomID code of publ. TaxonomyName (= foreign key). YES Refers to table TaxonName
HybridNameID4 int If IsHybrid is checked (or ‘True’): Name of hybrid species 4. Refers to NomID code of publ. TaxonomyName (= foreign key). YES Refers to table TaxonName
ReferenceTitle nvarchar (600) The title of the publication where the name was published. Note this is only a cached value where ReferenceURI is present YES -
ReferenceURI varchar (255) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in Database DiversityReferences: Source publication where name is published YES -
Volume nvarchar (20) The volume of the journal YES -
Issue nvarchar (255) The issue of the literature YES -
Pages nvarchar (50) The pages within the literature YES -
DetailLocation nvarchar (200) Additional information like plates etc. YES -
DayOfPubl tinyint The day when the name was published YES -
MonthOfPubl tinyint The month when the name was published YES -
YearOfPubl smallint The year when the name was published YES -
DateOfPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES -
YearOnPubl smallint The year cited on the original paper as year of publication YES -
DateOnPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES -
Protologue nvarchar (MAX) Full text of the protologue. If protologue is provided in Latin and in another language
languages, both only the Latin or several languages may be stored together. YES -
ProtologueURI varchar (255) URI of externally available Protologue information (scanned image, full text from external provider, etc.) YES -
ProtologueResourceURI varchar (255) The ResourceID of an image of the protologue as stored in the module DiversityResources. Primary key of table Resource in the database DiversityResources.(= Foreign key) YES -
NameUsageReferences nvarchar (255) Indexing volumes like Index of Fungi or any Name usage that caused this name to be added to the database
YES -
OriginalOrthography nvarchar (255) The original spelling of the name YES -
NomenclaturalCode nvarchar (50) Code of Nomenclature under which this taxon was created: ‘Bacteriology’, ‘Botany’ (incl. Mycology), ‘Zoology’, ‘Biocode’ (for future use), ‘Non nomenclatural name’. Default value: ‘Botany’ YES Refers to table TaxonNameNomenclaturalCode_Enum
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES Refers to table TaxonNameNomenclaturalStatus_Enum
NomenclaturalComment nvarchar (MAX) Comments on the nomenclature. e.g. ‘according to ICBN Art. 39.1’ YES -
Typification nvarchar (50) The status of the type specimen(s) as written in the protologue, e.g. holotype YES -
TypificationDetails nvarchar (255) Details concerning the typification as written in the protologue, e.g. if just parts of a specimen were accepted as the type YES -
TypificationReferenceTitle nvarchar (255) The title of the publication where the typification was published. Note this is only a cached value where Typification-LiteratureLink is present YES -
TypificationReferenceURI varchar (255) URI (e.g. LSID) of Reference, refers to e.g DiversityReferences: Source publication where the typification is published YES -
TypificationNotes nvarchar (200) Notes concerning the typification YES -
TypeSubstrate nvarchar (255) The substrate the type was growing on as written in the protologue YES -
TypeLocality nvarchar (255) The locality where the type was found as written in the protologue YES -
TypeSpecimenNotes nvarchar (200) Notes about the type specimen, e.g. the herbarium where a type specimen is located, Collector, collection date/number, etc. YES -
AnamorphTeleomorph nvarchar (255) If the name is related to a anamorph or a teleomorph as written in the protologue YES -
TypistNotes nvarchar (200) Additional notes and problems YES -
RevisionLevel nvarchar (50) The level of the revision of the taxonomic name, e.g. ‘unchecked’, ‘fully checked’ YES Refers to table TaxonNameRevisionLevel_Enum
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.Default value: (0) YES -
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -
BasionymAuthorsYear int The year when the name was published by the authors of the Basionym YES -

Depending on:

  • TaxonNameCreationType_Enum
  • TaxonNameNomenclaturalCode_Enum
  • TaxonNameNomenclaturalStatus_Enum
  • TaxonNameRevisionLevel_Enum
  • TaxonNameTaxonomicRank_Enum

trgInsTaxonName

Setting TaxonNameCache


Table TaxonNameExternalDatabase

TaxonNameExternalDatabase document the sources of the names.

Column Data type Description Nullable Relation
ExternalDatabaseID int An ID to identify an external data collection of plant names (primary key, the ID has no meaning outside of the DiversityWorkbench system) NO -
ExternalDatabaseName nvarchar (800) The name of the data collection that has been integrated or can be linked to for further analysis NO -
ExternalDatabaseVersion nvarchar (255) The version of this data collection (either official version number, or dates when the collection was integrated) YES -
Rights nvarchar (500) A description of copyright agreements or permission to use data from the external database YES -
ExternalDatabaseAuthors nvarchar (200) The persons or institutions responsible for the external database YES -
ExternalDatabaseURI nvarchar (300) The URI of the database provider resp. the external database YES -
ExternalDatabaseInstitution nvarchar (300) The institution responsible for the external database YES -
InternalNotes nvarchar (1500) Additional notes concerning this data collection YES -
ExternalAttribute_NameID nvarchar (255) The table and field name in the external data collection to which TaxonNameExternalID refers YES -
PreferredSequence tinyint For selection in e.g. picklists: of several equal names only the name from the source with the lowest preferred sequence will be provided. YES -
Disabled bit If this source should be disabled for selection of names e.g. in picklists YES -
LogCreatedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogCreatedWhen datetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen datetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Table TaxonNameExternalID

TaxonNameExternalID document the source of a name together with the ID of the source.

Column Data type Description Nullable Relation
NameID int The ID of a name in DiversityTaxonNames (foreign key + part of primary key: the name string associated with NameID may occur in multiple external databases) NO Refers to table TaxonName
ExternalDatabaseID int The ID of an external taxonomic data collection as defined in TaxontNameExternalDatabase (foreign key + part of primary key) NO Refers to table TaxonNameExternalDatabase
ExternalNameURI varchar (255) The URI (e.g. a LSID) of the external name as defined in the external database YES -
LogCreatedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogCreatedWhen datetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen datetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonName
  • TaxonNameExternalDatabase

Table TaxonNameList

The table is containing the names listed in e.g. a checklist corresponding to the project.

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonName
ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameListProjectProxy
Notes nvarchar (MAX) An note concerning this entry. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonName
  • TaxonNameListProjectProxy

Table TaxonNameListAnalysis

Analysis values for list entries in the database, “Red list category: R”, “Time of observation: Sept. - Nov.”

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameList and table TaxonNameListReference
ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameList and table TaxonNameListReference
TaxonNameListRefID int Unique ID of the reference within the list, refers to table TaxonNameListReference, part of primary keyDefault value: (-1) NO Refers to table TaxonNameListReference
AnalysisID int ID of the analysis (= foreign key) NO Refers to table TaxonNameListAnalysisCategory
AnalysisValue nvarchar (MAX) The result of the analysis YES -
Notes nvarchar (MAX) Notes concerning this analysis YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameList
  • TaxonNameListAnalysisCategory
  • TaxonNameListReference

Table TaxonNameListAnalysisCategory

Analysis types used within the database, e.g. “Red list category”, “Frequency”

Column Data type Description Nullable Relation
AnalysisID int ID of the analysis (Primary key) NO -
AnalysisParentID int Analysis ID of the parent analysis if it belongs to a certain type documented in this table YES -
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface YES -
Description nvarchar (MAX) Description of the analysis YES -
AnalysisURI varchar (255) URI referring to an external documentation of the analysis YES -
Notes nvarchar (MAX) Notes concerning this analysis YES -
LogCreatedWhen datetime The time when this dataset was createdDefault value: getdate() YES -
LogCreatedBy nvarchar (50) Who created this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -
ReferenceTitle nvarchar (800) The title of the publication where details about the analysis are published. Note this is only a cached value where ReferenceURI is present YES -
ReferenceURI varchar (400) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in module DiversityReferences: Source publication where details about the analysis are published YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES -
SortingID int An ID for sorting the data YES -

Table TaxonNameListAnalysisCategoryValue

Value lists for analysis types with predefined values, e.g. “0, 1, 2, 3, …” for Red list category. Includes description etc. for the values in the list.

Column Data type Description Nullable Relation
AnalysisID int ID of the analysis (Primary key) NO Refers to table TaxonNameListAnalysisCategory
AnalysisValue nvarchar (255) The categorized value of the analysis NO -
Description nvarchar (500) Description of enumerated object, displayed in the user interface YES -
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface YES -
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique. YES -
Notes nvarchar (500) Internal development notes about usage, definition, etc. of an enumerated object YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameListAnalysisCategory

Table TaxonNameListArea

The area defined for the whole taxon list

Column Data type Description Nullable Relation
ProjectID int Each project can have a different opinion regarding the parameters defined for a list. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameListProjectProxy
PlaceURI varchar (255) URI or identifier for a place (which may have several names) derived from e.g. TDWG NO -
PlaceNameCache nvarchar (255) The name of the place YES -
Notes nvarchar (MAX) An note concerning this entry. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameListProjectProxy

Table TaxonNameListCollectionSpecimen

The collection specimens on which the taxon list is based

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameList
ProjectID int ProjectID of the taxon list. Foreign key and part of primary key. NO Refers to table TaxonNameList
DisplayText varchar (255) The name of the collection specimen as shown e.g. in a user interface. Part of the primary key NO -
CollectionSpecimenURI varchar (255) URI of the collection specimen. May refer to the module CollectionSpecimen YES -
Role nvarchar (50) The role of the specimen in relation to the taxon list (= foreign key, see table TaxonNameListSpecimenRole_Enum) YES Refers to table TaxonNameListSpecimenRole_Enum
Description nvarchar (MAX) Description of the collection specimen YES -
PlaceURI varchar (255) URI or identifier for a place (which may have several names) derived from e.g. TDWG YES -
PlaceNameCache nvarchar (255) The name of the place YES -
Notes nvarchar (MAX) Notes about the collection specimen YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameList
  • TaxonNameListSpecimenRole_Enum

Table TaxonNameListDistribution

The geographical distrbution for the organisms within the taxon list.

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameList and table TaxonNameListReference
ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameList and table TaxonNameListReference
TaxonNameListRefID int Unique ID of the reference within the list, refers to table TaxonNameListReference, part of primary keyDefault value: (-1) NO Refers to table TaxonNameListReference
PlaceURI varchar (255) URI or identifier for a place (which may have several names) derived from e.g. TDWGDefault value: '’ NO -
PlaceNameCache nvarchar (255) The name of the placeDefault value: '’ NO -
Notes nvarchar (MAX) Notes concerning this analysis YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameList
  • TaxonNameListReference

Table TaxonNameListImage

Media, e.g. images of the organisms within the taxon list

Column Data type Description Nullable Relation
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameList
ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameList
URI varchar (255) The complete URI address of the image. NO -
Description xml (MAX) Description of the image YES -
Notes nvarchar (MAX) Notes concerning this analysis YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameList

Table TaxonNameListReference

The reference where the taxon list resp. the name is published

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameList
ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameList
TaxonNameListRefID int Unique ID of the reference within the list, part of primary key NO -
TaxonNameListRefText nvarchar (800) Free text, esp. where a TaxonNameListRefURI is missing. Source publication where distribution is published (not publication of name!) NO -
TaxonNameListRefURI varchar (255) Reference URI: Source publication where the distribution is published (not publication of name!) as stored e.g. in DiversityReferences YES -
TaxonNameListRefDetail nvarchar (255) Esp. page number on which the distribution is published YES -
ReferenceType nvarchar (50) The type of the reference, e.g. a webpage YES Refers to table TaxonNameListReferenceType_Enum
TaxonUsageContext nvarchar (50) The context of the usage of the taxonomic name within the reference, e.g. ecology YES -
Notes nvarchar (MAX) An note concerning this entry. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonNameList
  • TaxonNameListReferenceType_Enum

Table TaxonNameListUser

The table is containing the lists accessible for a user.

Column Data type Description Nullable Relation
LoginName nvarchar (50) Login of a user. NO -
ProjectID int Project accessible for a user. Refers to ProjectID in table TaxonNameList (= foreign key). NO Refers to table TaxonNameListProjectProxy

Depending on:

  • TaxonNameListProjectProxy

Table TaxonNameProject

TaxonNameProject documents the projects of the names and provides access to the data.

Column Data type Description Nullable Relation
NameID int The ID of a name in DiversityTaxonNames (foreign key + part of primary key: the name may occur in multiple projects) NO Refers to table TaxonName
ProjectID int ID of the project. Refers to the common project definition in the DiversityProjects module.Default value: 0 NO Refers to table ProjectProxy
LogInsertedWhen datetime The time when this dataset was insertedDefault value: getdate() YES -
LogInsertedBy nvarchar (50) Who inserted this datasetDefault value: user_name() YES -
LogUpdatedWhen datetime The last time when this dataset was updatedDefault value: getdate() YES -
LogUpdatedBy nvarchar (50) Who was the last to update this datasetDefault value: user_name() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • ProjectProxy
  • TaxonName

Table TaxonNameReference

References related to a taxonomic name

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonName
TaxonNameRefID int Unique ID of the reference, part of primary key NO -
TaxonNameRefText nvarchar (800) The citation text of the reference NO -
TaxonNameRefURI varchar (500) Reference URI: Link to the source where the publication as stored e.g. DiversityReferences YES -
TaxonNameRefDetail nvarchar (255) Esp. page number on which the distribution is published YES -
ReferenceType nvarchar (50) The type of the reference, e.g. a webpage YES Refers to table TaxonNameListReferenceType_Enum
Notes nvarchar (MAX) An note concerning this entry. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonName
  • TaxonNameListReferenceType_Enum

Table TaxonNameResource

Resouces related to the taxonomic name

Column Data type Description Nullable Relation
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameProject
ProjectID int ID of the project. Refers to the common project definition in the DiversityProjects module. NO Refers to table TaxonNameProject
URI varchar (255) The complete URI address of the resource. NO -
Description xml (MAX) Description of the resource YES -
Notes nvarchar (MAX) A note concerning this entry. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when the data were first entered (typed or imported) into this database.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when the data were last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -
Title nvarchar (500) Title of the resource YES -
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES -
Creator nvarchar (500) Person or organization originally creating the resource YES -
CreatorAgentURI varchar (500) Link to the module DiversityAgents YES -
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES -
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES -
LicenseHolder nvarchar (500) The person or institution holding the license YES -
LicenseHolderAgentURI varchar (500) The link to a module containing further information on the person or institution holding the license YES -
LicenseYear nvarchar (50) The year of license declaration YES -
DisplayOrder int The sequence in which the resource should be displayed in a user interfaceDefault value: (1) YES -
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise nullDefault value: '’ YES -
ResourceType nvarchar (50) Type of the resource as defined in table TaxonNameResourceType_Enum YES Refers to table TaxonNameResourceType_Enum

Depending on:

  • TaxonNameProject
  • TaxonNameResourceType_Enum

Table TaxonNameTypification

The typification of a taxonomic name, e.g. where the type information of the name was published

Column Data type Description Nullable Relation
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO Refers to table TaxonName
TypificationReferenceTitle nvarchar (255) The title of the publication where the typification was published. Note this is only a cached value where Typification-LiteratureLink is present NO -
TypificationReferenceURI varchar (255) URI (e.g. LSID) of Reference, refers to e.g DiversityReferences: Source publication where the typification is published YES -
Typification nvarchar (500) The status of the type specimen(s) as written in the protologue, e.g. holotype YES -
TypificationDetails nvarchar (255) Details concerning the typification as written in the protologue, e.g. if just parts of a specimen were accepted as the type YES -
TypificationNotes nvarchar (200) Notes concerning the typification YES -
TypeSubstrate nvarchar (255) The substrate the type was growing on as written in the protologue YES -
TypeLocality nvarchar (255) The locality where the type was found as written in the protologue YES -
TypeSpecimenNotes nvarchar (500) Notes about the type specimen, e.g. the herbarium where a type specimen is located, Collector, collection date/number, etc. YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • TaxonName

Table TaxonSynonymy

TaxonSynonymy contains names, which are synonym to other names. Here a single name may be a synonym of multiple accepted names (“pro parte synonym”). The “pro parte” or corresponding sensu information is captured in the “ConceptSuffix” attribute, which is part of the primary key.

Column Data type Description Nullable Relation
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module.Default value: (0) NO Refers to table ProjectProxy and table TaxonNameProject
NameID int ID of the synonymized name. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameProject
SynNameID int The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key). NO Refers to table TaxonNameProject
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.Default value: (0) NO -
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc.Default value: '’ YES -
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES -
SynRefURI varchar (255) Reference URI: Source publication where synonymization is published (not publication of name!) as stored e.g. in DiversityReferences YES -
SynRefText nvarchar (255) Free text, esp. where a SynRefURI is missing. Source publication where synonymization is published (not publication of name!) YES -
SynRefDetail nvarchar (255) Esp. page number on which the synonymization is published YES -
SynTypistsNotes nvarchar (255) An internal note of the responsible person concerning this synonymization. This information is NOT included in any report. YES -
SynType nvarchar (50) Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’Default value: ‘unknown’ NO Refers to table TaxonNameSynonymisationType_Enum
SynIsUncertain bit If the synoymization is uncertain. Corresponding to =? for heterotypic synonyms and ? if the type of the synonymisation is unknown. Homotypic synonyms can not be uncertain.Default value: (0) YES -
LogInsertedBy nvarchar (50) Name of user who first entered (typed or imported) the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogInsertedWhen smalldatetime Date and time when record was first entered (typed or imported) into this system.Default value: getdate() YES -
LogUpdatedBy nvarchar (50) Name of user who last updated the data. This is the operator (or typist) name, which may be different from the person responsible.Default value: user_name() YES -
LogUpdatedWhen smalldatetime Date and time when record was last updated.Default value: getdate() YES -
RowGUID uniqueidentifier -Default value: newsequentialid() YES -

Depending on:

  • ProjectProxy
  • TaxonNameProject
  • TaxonNameSynonymisationType_Enum

trgInsTaxonSynonymy

Setting version of taxon


VIEWS


View AcceptedNameChanges

Listing NameID of previous accepted names and the NameID of the current accepted name

Column Data type Description Nullable
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. YES
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). YES
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES
LogDate datetime Date of the changes according to the log table NO
LogID int ID of the changes in the log table NO
CurrentAcceptedNameID int NameID of the accepted name YES

Depending on:

  • TaxonAcceptedName
  • TaxonAcceptedName_log
  • TaxonSynonymy

View GenusList

All Taxa with rank genus

Column Data type Description Nullable
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO
TaxonNameCache nvarchar (200) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES

Depending on:

  • TaxonName

View NameID_UserAvailable

List of NameIDs accessible for the current user

Column Data type Description Nullable
NameID int The ID of a name in DiversityTaxonNames (foreign key + part of primary key: the name may occur in multiple projects) NO

Depending on:

  • ProjectUser
  • TaxonNameProject

View ProjectList

List of projects accessible for the current user

Column Data type Description Nullable
Project nvarchar (50) The name of the project NO
ProjectID int ID of the project NO
ProjectURI varchar (255) The URI of the project, e.g. as provided by the module DiversityProjects. YES

Depending on:

  • ProjectProxy
  • ProjectUser

View TaxonAcceptedName_Core

Content of TaxonAcceptedName restricted to datasets accessible for a user

Column Data type Description Nullable
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. NO
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. YES
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
RefURI varchar (255) ReferenceURI: Source publication where synonymization is published (not publication of name!) YES
RefText nvarchar (255) Free text, esp. where a RefURI is missing. Source publication where synonymization is published (not publication of name!) YES
RefDetail nvarchar (255) Esp. page number on which the synonymization is published YES
TypistsNotes nvarchar (255) An internal note of the responsible person concerning this synonymization. This information is NOT included in any report. YES

Depending on:

  • NameID_UserAvailable
  • TaxonAcceptedName

View TaxonAcceptedName_Indicated

List of IDs of accepted names

Column Data type Description Nullable
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. NO
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. YES
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
RefURI varchar (255) ReferenceURI: Source publication where synonymization is published (not publication of name!) YES
RefText nvarchar (255) Free text, esp. where a RefURI is missing. Source publication where synonymization is published (not publication of name!) YES
RefDetail nvarchar (255) Esp. page number on which the synonymization is published YES
TypistsNotes nvarchar (255) An internal note of the responsible person concerning this synonymization. This information is NOT included in any report. YES

Depending on:

  • TaxonAcceptedName

View TaxonAcceptedNameList

List of accepted names excluding ignored names

Column Data type Description Nullable
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO
DisplayText nvarchar (4000) Combining taxon, publication and nomenclatural information YES
TaxonName nvarchar (301) Combining taxon information excluding authors YES
TaxonomicRank nvarchar (52) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
InfraspecificEpithet nvarchar (101) The epithet of the infraspecific entity YES
Authors nvarchar (719) Combining all author information of the taxon YES
SynonymText nvarchar (1683) Combining publication and nomenclatural information YES
YearOfPubl smallint The year when the name was published YES
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. YES
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES

Depending on:

  • TaxonAcceptedName
  • TaxonName

View TaxonAcceptedNameListIncludeIgnored

List of accepted names including ignored names

Column Data type Description Nullable
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO
DisplayText nvarchar (2609) Combining taxon, publication and nomenclatural information YES
TaxonName nvarchar (301) Combining taxon information excluding authors YES
TaxonomicRank nvarchar (52) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
InfraspecificEpithet nvarchar (101) The epithet of the infraspecific entity YES
Authors nvarchar (719) Combining all author information of the taxon YES
SynonymText nvarchar (1338) Combining publication and nomenclatural information YES
YearOfPubl smallint The year when the name was published YES
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. YES
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES

Depending on:

  • TaxonAcceptedName
  • TaxonName

View TaxonFamily

Family information for taxa

Column Data type Description Nullable
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key). NO
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
FamilyNameID int NameID for the family YES
Family nvarchar (200) The name of the family YES
IgnoreButKeepForReference int If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. NO

Depending on:

  • TaxonHierarchy
  • TaxonName
  • TaxonNameTaxonomicRank_Enum

View TaxonGeography_Core

User available information of the geography

Column Data type Description Nullable
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO
PlaceURI varchar (255) URI (e.g. LSID) within e.g. the DiversityGazetteer for a place (which may have several names) as found in the protologue NO
PlaceNameCache nvarchar (100) The name of the place YES

Depending on:

  • NameID_UserAvailable
  • TaxonGeography

View TaxonHierarchy_Core

User available information of the hierarchy

Column Data type Description Nullable
ProjectID int Each project can implement a different taxonomic hierarchy. Refers to the common project definition in the DiversityProjects module. NO
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key). NO
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. NO
NameParentID int Next higher taxon (e.g. the family or subfamily if this taxon is a genus) YES
HierarchyRefURI varchar (255) Reference URI: Source publication where the hierarchy is published (not publication of name!) as stored e.g. in DiversityReferences YES
HierarchyRefText nvarchar (255) Free citation, esp. where a HierarchyRefURI is missing. Source publication where the hierarchy is published (not publication of name!) YES
HierarchyRefDetail nvarchar (255) Esp. page number on which the hierarchy is published YES
HierarchyPositionIsUncertain bit If the position of this taxon within this taxonomic group is uncertain. YES
HierarchyTypistsNotes nvarchar (255) An internal note of the responsible person concerning this hierarchy. This information is NOT included in any report. YES
HierarchyListCache nvarchar (1000) CALCULATED FIELD: List of higher taxa for faster access: “div.; class; ord.; fam.” YES

Depending on:

  • NameID_UserAvailable
  • TaxonHierarchy

View TaxonListSynType

Public available information for taxa including synonymy

Column Data type Description Nullable
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
CreationType nvarchar (50) E.g.: taxon based on new type, combination based on a previously publ. name (‘comb. nov.’), new name (’nom.nov.’) introduced to replace a homonym (may occur for genera!), validation of previously invalidly publ. taxon name (’ex’), or unknown. YES
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
GenusOrSupragenericName nvarchar (200) If rank is above species: Name of taxon above species level (currently accepted spelling). Includes infrageneric taxon names, genera, families, etc. NO
SpeciesGenusNameID int If rank is species or below: NameID of the Genus name. Refers to same table with TaxonomicRank = genus. YES
InfragenericEpithet nvarchar (200) If rank below genus and above species: Name of infrageneric taxon above species level (currently accepted spelling). Includes subgenus, series, etc. YES
SpeciesEpithet nvarchar (100) The species name part of the species name, for example ‘alba’ in ‘Abies alba’. YES
InfraspecificEpithet nvarchar (100) The epithet of the infraspecific entity YES
BasionymAuthors nvarchar (100) The authors of a newly created name. For all taxonomic ranks, only for ‘comb. nov.’ or ’nom. nov.’: Author(s) of the basionym (will be displayed in ‘()’, do not enter the parentheses), abbreviated according to authors standard YES
CombiningAuthors nvarchar (255) The names of the combining authors if the name is base on another older name (e.g. combined into a different genus) YES
PublishingAuthors nvarchar (255) If the authors of the taxon differ from the authors of the publication: the latter (…‘in ’ Publishing authors … ) YES
SanctioningAuthor nvarchar (100) Sanctioning is a special instrument available for fungi to allow the starting date of taxonomy to be identical with higher plants, but preserve names used by Fries (Fr.) and Person (Pers.) YES
NonNomenclaturalNameSuffix nvarchar (200) A suffix for concept names not included in any nomenclatural code. If present fields for authors and typification must be empty and NomenclaturalCode set to ’not under code’. YES
IsHybrid bit If checked (or ‘True’), the new taxon is a hybrid with or without a hybrid epithet. YES
HybridNameID1 int If IsHybrid is checked (or ‘True’): Name of hybrid species 1. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID2 int If IsHybrid is checked (or ‘True’): Name of hybrid species 2. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID3 int If IsHybrid is checked (or ‘True’): Name of hybrid species 3. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID4 int If IsHybrid is checked (or ‘True’): Name of hybrid species 4. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
ReferenceTitle nvarchar (600) The title of the publication where the name was published. Note this is only a cached value where ReferenceURI is present YES
ReferenceURI varchar (255) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in Database DiversityReferences: Source publication where name is published YES
Volume nvarchar (20) The volume of the journal YES
Issue nvarchar (255) The issue of the literature YES
Pages nvarchar (50) The pages within the literature YES
YearOfPubl smallint The year when the name was published YES
YearOnPubl smallint The year cited on the original paper as year of publication YES
NameUsageReferences nvarchar (255) Indexing volumes like Index of Fungi or any Name usage that caused this name to be added to the database
YES
OriginalOrthography nvarchar (255) The original spelling of the name YES
NomenclaturalCode nvarchar (50) Code of Nomenclature under which this taxon was created: ‘Bacteriology’, ‘Botany’ (incl. Mycology), ‘Zoology’, ‘Biocode’ (for future use), ‘Non nomenclatural name’. Default value: ‘Botany’ YES
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES
NomenclaturalComment nvarchar (MAX) Comments on the nomenclature. e.g. ‘according to ICBN Art. 39.1’ YES
Typification nvarchar (50) The status of the type specimen(s) as written in the protologue, e.g. holotype YES
TypificationDetails nvarchar (255) Details concerning the typification as written in the protologue, e.g. if just parts of a specimen were accepted as the type YES
TypeSubstrate nvarchar (255) The substrate the type was growing on as written in the protologue YES
TypeLocality nvarchar (255) The locality where the type was found as written in the protologue YES
TypificationReferenceTitle nvarchar (255) The title of the publication where the typification was published. Note this is only a cached value where Typification-LiteratureLink is present YES
TypificationReferenceURI varchar (255) URI (e.g. LSID) of Reference, refers to e.g DiversityReferences: Source publication where the typification is published YES
TypificationNotes nvarchar (200) Notes concerning the typification YES
AnamorphTeleomorph nvarchar (255) If the name is related to a anamorph or a teleomorph as written in the protologue YES
TypistNotes nvarchar (200) Additional notes and problems YES
SynType nvarchar (50) Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ YES
ValidSynType nvarchar (50) “accepted name” or type of the synonymy YES
IgnoreAcceptedName int If accepted name is ignored (1 = ignored, 0 = not ignored) NO
IgnoreSynonymy int If synonymy is ignored (1 = ignored, 0 = not ignored) NO

Depending on:

  • TaxonAcceptedName
  • TaxonName
  • TaxonSynonymy

View TaxonName_Core

User available taxa

Column Data type Description Nullable
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO
Display nvarchar (255) Corresponds to TaxonNameCache YES
DisplayEpithet nvarchar (358) SpeciesEpithet including information for whole taxon for query YES
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
Version smallint The version of a name record (revision number, internally filled by system) YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
CreationType nvarchar (50) E.g.: taxon based on new type, combination based on a previously publ. name (‘comb. nov.’), new name (’nom.nov.’) introduced to replace a homonym (may occur for genera!), validation of previously invalidly publ. taxon name (’ex’), or unknown. YES
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
GenusOrSupragenericName nvarchar (200) If rank is above species: Name of taxon above species level (currently accepted spelling). Includes infrageneric taxon names, genera, families, etc. NO
SpeciesGenusNameID int If rank is species or below: NameID of the Genus name. Refers to same table with TaxonomicRank = genus. YES
InfragenericEpithet nvarchar (200) If rank below genus and above species: Name of infrageneric taxon above species level (currently accepted spelling). Includes subgenus, series, etc. YES
SpeciesEpithet nvarchar (100) The species name part of the species name, for example ‘alba’ in ‘Abies alba’. YES
InfraspecificEpithet nvarchar (100) The epithet of the infraspecific entity YES
BasionymAuthors nvarchar (100) The authors of a newly created name. For all taxonomic ranks, only for ‘comb. nov.’ or ’nom. nov.’: Author(s) of the basionym (will be displayed in ‘()’, do not enter the parentheses), abbreviated according to authors standard YES
CombiningAuthors nvarchar (255) The names of the combining authors if the name is base on another older name (e.g. combined into a different genus) YES
PublishingAuthors nvarchar (255) If the authors of the taxon differ from the authors of the publication: the latter (…‘in ’ Publishing authors … ) YES
SanctioningAuthor nvarchar (100) Sanctioning is a special instrument available for fungi to allow the starting date of taxonomy to be identical with higher plants, but preserve names used by Fries (Fr.) and Person (Pers.) YES
NonNomenclaturalNameSuffix nvarchar (200) A suffix for concept names not included in any nomenclatural code. If present fields for authors and typification must be empty and NomenclaturalCode set to ’not under code’. YES
IsHybrid bit If checked (or ‘True’), the new taxon is a hybrid with or without a hybrid epithet. YES
HybridNameID1 int If IsHybrid is checked (or ‘True’): Name of hybrid species 1. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID2 int If IsHybrid is checked (or ‘True’): Name of hybrid species 2. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID3 int If IsHybrid is checked (or ‘True’): Name of hybrid species 3. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID4 int If IsHybrid is checked (or ‘True’): Name of hybrid species 4. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
ReferenceTitle nvarchar (600) The title of the publication where the name was published. Note this is only a cached value where ReferenceURI is present YES
ReferenceURI varchar (255) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in Database DiversityReferences: Source publication where name is published YES
Volume nvarchar (20) The volume of the journal YES
Issue nvarchar (255) The issue of the literature YES
Pages nvarchar (50) The pages within the literature YES
DetailLocation nvarchar (200) Additional information like plates etc. YES
DayOfPubl tinyint The day when the name was published YES
MonthOfPubl tinyint The month when the name was published YES
YearOfPubl smallint The year when the name was published YES
DateOfPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
YearOnPubl smallint The year cited on the original paper as year of publication YES
DateOnPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
Protologue nvarchar (MAX) Full text of the protologue. If protologue is provided in Latin and in another language
languages, both only the Latin or several languages may be stored together. YES
ProtologueURI varchar (255) URI of externally available Protologue information (scanned image, full text from external provider, etc.) YES
ProtologueResourceURI varchar (255) The ResourceID of an image of the protologue as stored in the module DiversityResources. Primary key of table Resource in the database DiversityResources.(= Foreign key) YES
NameUsageReferences nvarchar (255) Indexing volumes like Index of Fungi or any Name usage that caused this name to be added to the database
YES
OriginalOrthography nvarchar (255) The original spelling of the name YES
NomenclaturalCode nvarchar (50) Code of Nomenclature under which this taxon was created: ‘Bacteriology’, ‘Botany’ (incl. Mycology), ‘Zoology’, ‘Biocode’ (for future use), ‘Non nomenclatural name’. Default value: ‘Botany’ YES
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES
NomenclaturalComment nvarchar (MAX) Comments on the nomenclature. e.g. ‘according to ICBN Art. 39.1’ YES
Typification nvarchar (50) The status of the type specimen(s) as written in the protologue, e.g. holotype YES
TypificationDetails nvarchar (255) Details concerning the typification as written in the protologue, e.g. if just parts of a specimen were accepted as the type YES
TypificationReferenceTitle nvarchar (255) The title of the publication where the typification was published. Note this is only a cached value where Typification-LiteratureLink is present YES
TypificationReferenceURI varchar (255) URI (e.g. LSID) of Reference, refers to e.g DiversityReferences: Source publication where the typification is published YES
TypificationNotes nvarchar (200) Notes concerning the typification YES
TypeSubstrate nvarchar (255) The substrate the type was growing on as written in the protologue YES
TypeLocality nvarchar (255) The locality where the type was found as written in the protologue YES
TypeSpecimenNotes nvarchar (200) Notes about the type specimen, e.g. the herbarium where a type specimen is located, Collector, collection date/number, etc. YES
AnamorphTeleomorph nvarchar (255) If the name is related to a anamorph or a teleomorph as written in the protologue YES
TypistNotes nvarchar (200) Additional notes and problems YES
RevisionLevel nvarchar (50) The level of the revision of the taxonomic name, e.g. ‘unchecked’, ‘fully checked’ YES
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES

Depending on:

  • NameID_UserAvailable
  • TaxonName

View TaxonName_Indicated

Content of table TaxonName including synonymy information

Column Data type Description Nullable
ProjectID int ID of the project. Refers to the common project definition in the DiversityProjects module. NO
Display nvarchar (263) Content of column TaxonNameCache with synonymy prefix YES
DisplayEpithet nvarchar (366) Content of column SpeciesEpithet with synonymy prefix and trailed by TaxonNameCache YES
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
Version smallint The version of a name record (revision number, internally filled by system) YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
CreationType nvarchar (50) E.g.: taxon based on new type, combination based on a previously publ. name (‘comb. nov.’), new name (’nom.nov.’) introduced to replace a homonym (may occur for genera!), validation of previously invalidly publ. taxon name (’ex’), or unknown. YES
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
GenusOrSupragenericName nvarchar (200) If rank is above species: Name of taxon above species level (currently accepted spelling). Includes infrageneric taxon names, genera, families, etc. NO
SpeciesGenusNameID int If rank is species or below: NameID of the Genus name. Refers to same table with TaxonomicRank = genus. YES
InfragenericEpithet nvarchar (200) If rank below genus and above species: Name of infrageneric taxon above species level (currently accepted spelling). Includes subgenus, series, etc. YES
SpeciesEpithet nvarchar (100) The species name part of the species name, for example ‘alba’ in ‘Abies alba’. YES
InfraspecificEpithet nvarchar (100) The epithet of the infraspecific entity YES
BasionymAuthors nvarchar (100) The authors of a newly created name. For all taxonomic ranks, only for ‘comb. nov.’ or ’nom. nov.’: Author(s) of the basionym (will be displayed in ‘()’, do not enter the parentheses), abbreviated according to authors standard YES
CombiningAuthors nvarchar (255) The names of the combining authors if the name is base on another older name (e.g. combined into a different genus) YES
PublishingAuthors nvarchar (255) If the authors of the taxon differ from the authors of the publication: the latter (…‘in ’ Publishing authors … ) YES
SanctioningAuthor nvarchar (100) Sanctioning is a special instrument available for fungi to allow the starting date of taxonomy to be identical with higher plants, but preserve names used by Fries (Fr.) and Person (Pers.) YES
NonNomenclaturalNameSuffix nvarchar (200) A suffix for concept names not included in any nomenclatural code. If present fields for authors and typification must be empty and NomenclaturalCode set to ’not under code’. YES
IsHybrid bit If checked (or ‘True’), the new taxon is a hybrid with or without a hybrid epithet. YES
HybridNameID1 int If IsHybrid is checked (or ‘True’): Name of hybrid species 1. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID2 int If IsHybrid is checked (or ‘True’): Name of hybrid species 2. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID3 int If IsHybrid is checked (or ‘True’): Name of hybrid species 3. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
HybridNameID4 int If IsHybrid is checked (or ‘True’): Name of hybrid species 4. Refers to NomID code of publ. TaxonomyName (= foreign key). YES
ReferenceTitle nvarchar (600) The title of the publication where the name was published. Note this is only a cached value where ReferenceURI is present YES
ReferenceURI varchar (255) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in Database DiversityReferences: Source publication where name is published YES
Volume nvarchar (20) The volume of the journal YES
Issue nvarchar (255) The issue of the literature YES
Pages nvarchar (50) The pages within the literature YES
DetailLocation nvarchar (200) Additional information like plates etc. YES
DayOfPubl tinyint The day when the name was published YES
MonthOfPubl tinyint The month when the name was published YES
YearOfPubl smallint The year when the name was published YES
DateOfPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
YearOnPubl smallint The year cited on the original paper as year of publication YES
DateOnPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’ YES
Protologue nvarchar (MAX) Full text of the protologue. If protologue is provided in Latin and in another language
languages, both only the Latin or several languages may be stored together. YES
ProtologueURI varchar (255) URI of externally available Protologue information (scanned image, full text from external provider, etc.) YES
ProtologueResourceURI varchar (255) The ResourceID of an image of the protologue as stored in the module DiversityResources. Primary key of table Resource in the database DiversityResources.(= Foreign key) YES
NameUsageReferences nvarchar (255) Indexing volumes like Index of Fungi or any Name usage that caused this name to be added to the database
YES
OriginalOrthography nvarchar (255) The original spelling of the name YES
NomenclaturalCode nvarchar (50) Code of Nomenclature under which this taxon was created: ‘Bacteriology’, ‘Botany’ (incl. Mycology), ‘Zoology’, ‘Biocode’ (for future use), ‘Non nomenclatural name’. Default value: ‘Botany’ YES
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES
NomenclaturalComment nvarchar (MAX) Comments on the nomenclature. e.g. ‘according to ICBN Art. 39.1’ YES
Typification nvarchar (50) The status of the type specimen(s) as written in the protologue, e.g. holotype YES
TypificationDetails nvarchar (255) Details concerning the typification as written in the protologue, e.g. if just parts of a specimen were accepted as the type YES
TypificationReferenceTitle nvarchar (255) The title of the publication where the typification was published. Note this is only a cached value where Typification-LiteratureLink is present YES
TypificationReferenceURI varchar (255) URI (e.g. LSID) of Reference, refers to e.g DiversityReferences: Source publication where the typification is published YES
TypificationNotes nvarchar (200) Notes concerning the typification YES
TypeSubstrate nvarchar (255) The substrate the type was growing on as written in the protologue YES
TypeLocality nvarchar (255) The locality where the type was found as written in the protologue YES
TypeSpecimenNotes nvarchar (200) Notes about the type specimen, e.g. the herbarium where a type specimen is located, Collector, collection date/number, etc. YES
AnamorphTeleomorph nvarchar (255) If the name is related to a anamorph or a teleomorph as written in the protologue YES
TypistNotes nvarchar (200) Additional notes and problems YES
RevisionLevel nvarchar (50) The level of the revision of the taxonomic name, e.g. ‘unchecked’, ‘fully checked’ YES
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES

Depending on:

  • ProjectList
  • TaxonAcceptedName_Indicated
  • TaxonName
  • TaxonNameProject
  • TaxonSynonymy_Indicated

View TaxonNameExternalID_Core

User available content of table TaxonNameExternalID

Column Data type Description Nullable
NameID int The ID of a name in DiversityTaxonNames (foreign key + part of primary key: the name string associated with NameID may occur in multiple external databases) NO
ExternalDatabaseID int The ID of an external taxonomic data collection as defined in TaxontNameExternalDatabase (foreign key + part of primary key) NO
ExternalNameURI varchar (255) The URI (e.g. a LSID) of the external name as defined in the external database YES

Depending on:

  • NameID_UserAvailable
  • TaxonNameExternalID

View TaxonOrder

Not ignored Order for taxa

Column Data type Description Nullable
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key). NO
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
OrderNameID int The NameID of the Order YES
Order nvarchar (200) The Name of the Order YES
IgnoreButKeepForReference int If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. NO

Depending on:

  • TaxonHierarchy
  • TaxonName

View TaxonSynonymy_Core

User available content of table TaxonSynonymy

Column Data type Description Nullable
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NameID int ID of the synonymized name. Refers to the NameID of TaxonName (= foreign key). NO
SynNameID int The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key). NO
IgnoreButKeepForReference tinyint If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. NO
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. NO
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
SynRefURI varchar (255) Reference URI: Source publication where synonymization is published (not publication of name!) as stored e.g. in DiversityReferences YES
SynRefText nvarchar (255) Free text, esp. where a SynRefURI is missing. Source publication where synonymization is published (not publication of name!) YES
SynRefDetail nvarchar (255) Esp. page number on which the synonymization is published YES
SynTypistsNotes nvarchar (255) An internal note of the responsible person concerning this synonymization. This information is NOT included in any report. YES
SynType nvarchar (50) Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ YES
SynIsUncertain bit If the synoymization is uncertain. Corresponding to =? for heterotypic synonyms and ? if the type of the synonymisation is unknown. Homotypic synonyms can not be uncertain. YES

Depending on:

  • NameID_UserAvailable
  • TaxonSynonymy

View TaxonSynonymy_Indicated

Prefix information for Synonyms

Column Data type Description Nullable
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NameID int ID of the synonymized name. Refers to the NameID of TaxonName (= foreign key). NO
SynType nvarchar (50) Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ YES
Prefix nvarchar (4) Prefix for Synonyms as displayed in query YES
Indent varchar (4) Indent for Synonyms as displayed in query YES

Depending on:

  • TaxonSynonymy

View TaxonSynonymyAcceptedNameID

Accepted names for synonyms

Column Data type Description Nullable
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key). NO
AcceptedNameID int ID of the accepted name YES

Depending on:

  • TaxonAcceptedName
  • TaxonSynonymy

View TaxonSynonymyList

Taxon information including synonymy for not ignored data

Column Data type Description Nullable
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO
DisplayText nvarchar (4000) Taxon name including publication and nomenclatural information YES
TaxonName nvarchar (301) Taxonomic name excluding authors YES
TaxonomicRank nvarchar (52) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
InfraspecificEpithet nvarchar (101) The epithet of the infraspecific entity YES
Authors nvarchar (922) Combining all author information of the taxon YES
SynonymText nvarchar (1683) Combining publication and nomenclatural information YES
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
YearOfPubl smallint The year when the name was published YES
SynIsUncertain bit If the synoymization is uncertain. Corresponding to =? for heterotypic synonyms and ? if the type of the synonymisation is unknown. Homotypic synonyms can not be uncertain. YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. YES
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
SynType nvarchar (50) Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ NO
SynNameID int The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key). NO
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES

Depending on:

  • TaxonName
  • TaxonSynonymy

View TaxonSynonymyListIncludeIgnored

Taxon information including synonymy and including ignored data

Column Data type Description Nullable
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key) NO
DisplayText nvarchar (2613) Taxon name including publication and nomenclatural information YES
TaxonName nvarchar (301) Taxonomic name excluding authors YES
TaxonomicRank nvarchar (52) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank) NO
InfraspecificEpithet nvarchar (101) The epithet of the infraspecific entity YES
Authors nvarchar (922) Combining all author information of the taxon YES
SynonymText nvarchar (1338) Combining publication and nomenclatural information YES
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key) YES
YearOfPubl smallint The year when the name was published YES
SynIsUncertain bit If the synoymization is uncertain. Corresponding to =? for heterotypic synonyms and ? if the type of the synonymisation is unknown. Homotypic synonyms can not be uncertain. YES
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. YES
ConceptSuffix nvarchar (200) Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. YES
ConceptNotes nvarchar (500) Notes on the concept of the name, e.g. incl. forms with black apothecia YES
SynType nvarchar (50) Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ NO
SynNameID int The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key). NO
ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module. NO
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc. YES
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. YES

Depending on:

  • TaxonName
  • TaxonSynonymy

View ViewBaseURL

Result of function dbo.BaseURL() for linked servers

Column Data type Description Nullable
BaseURL varchar (255) The BaseURL of the database YES

Depending on:

  • BaseURL

View ViewDefaultProjectID

Result of function dbo.DefaultProjectID() for linked servers

Column Data type Description Nullable
ProjectID int ID of the project. Foreign key, relates to PK of table ProjectProxy YES

Depending on:

  • DefaultProjectID

View ViewDiversityWorkbenchModule

Result of function dbo.DiversityWorkbenchModule() for linked servers

Column Data type Description Nullable
DiversityWorkbenchModule nvarchar (50) The DiversityWorkbenchModule of the database = DiversityTaxonNames YES

Depending on:

  • DiversityWorkbenchModule

View ViewTaxonNameResource

A View for TaxonNameResource excluding XML columns

Column Data type Description Nullable
NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key). NO
ProjectID int ID of the project. Refers to the common project definition in the DiversityProjects module. NO
URI varchar (255) The complete URI address of the resource. NO
Notes nvarchar (MAX) A note concerning this entry. YES
Title nvarchar (500) Title of the resource YES
IPR nvarchar (500) Intellectual Property Rights; the rights given to persons for their intellectual property YES
Creator nvarchar (500) Person or organization originally creating the resource YES
CreatorAgentURI varchar (500) Link to the module DiversityAgents YES
CopyrightStatement nvarchar (500) Notice on rights held in and for the resource YES
LicenseType nvarchar (500) Type of an official or legal permission to do or own a specified thing, e. g. Creative Common Licenses YES
LicenseHolder nvarchar (500) The person or institution holding the license YES
LicenseHolderAgentURI varchar (500) The link to a module containing further information on the person or institution holding the license YES
LicenseYear nvarchar (50) The year of license declaration YES
DisplayOrder int The sequence in which the resource should be displayed in a user interface YES
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null YES
ResourceType nvarchar (50) Type of the resource as defined in table TaxonNameResourceType_Enum YES

Depending on:

  • TaxonNameResource

FUNCTIONS


Function AcceptedNameID

Returns ID of accepted name if any is found, otherwise NULL

DataType: int

Parameter DataType Description
@NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key).
@ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module.

Depending on:

  • DefaultProjectID
  • TaxonAcceptedName
  • TaxonName
  • TaxonSynonymy

Function AnalysisCategoryHierarchyAll

Returns a table that lists all the analysis categorys.

Column DataType Description
AnalysisID int ID of the analysis (Primary key)
AnalysisParentID int Analysis ID of the parent analysis if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (MAX) Description of the analysis
Notes nvarchar (MAX) Notes concerning this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
OnlyHierarchy bit Reserved for future application
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null
SortingID int An ID for sorting the data
HierarchyDisplayText varchar (900) DisplayTexts of the hierarchy separated by "

Depending on:

  • TaxonNameListAnalysisCategory

Function BaseURL

Returns BaseURL for the database

DataType: varchar (255)


Function DefaultProjectID

ID of the current project selected by the user

DataType: int

Depending on:

  • ProjectUser
  • UserProxy

Function DiversityMobile_TaxonList

Returns a result set that lists all taxa in a given project resp. list

Parameter DataType Description
@ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module.
@ListID int The ID of the List corresponding to column ProjectID in table TaxonNameList
Column DataType Description
NameURI varchar (255) Combines content of dbo.BaseURL() and NameID of the taxon
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key)
TaxonNameSinAuthors nvarchar (255) Taxonomic name excluding authors
GenusOrSupragenericName nvarchar (255) If rank is above species: Name of taxon above species level (currently accepted spelling). Includes infrageneric taxon names, genera, families, etc.
SpeciesEpithet nvarchar (255) The species name part of the species name, for example ‘alba’ in ‘Abies alba’.
InfraspecificEpithet nvarchar (255) The epithet of the infraspecific entity
Synonymy varchar (50) Simple synonymy information for the taxon as either “Accepted” or “Synonym”
Family nvarchar (255) Family of the taxon
Order nvarchar (255) Order of the taxon

Depending on:

  • BaseURL
  • TaxonAcceptedName
  • TaxonHierarchy
  • TaxonName
  • TaxonNameList
  • TaxonNameProject
  • TaxonSynonymy

Function DiversityWorkbenchModule

Returns the DiversityWorkbenchModule = “DiversityTaxonNames”

DataType: nvarchar (50)


Function HierarchyCache

Returns a string of all the taxa superior to a given taxon separated with the value of parameter @Separator

DataType: nvarchar (-1)

Parameter DataType Description
@NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
@DiversityProjectID int ID of the project
@Separator char (1) Separator for the hierarchy levels

Depending on:

  • ProjectList
  • TaxonHierarchy
  • TaxonHierarchy_Core
  • TaxonName
  • TaxonNameProject

Function HierarchyFamilyList

Returns a result set that lists all families of the taxa in a given project

Parameter DataType Description
@ProjectID int Each project can implement a different taxonomic hierarchy. Refers to the common project definition in the DiversityProjects module.
Column DataType Description
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
TaxonNameCache nvarchar (500) A full unique version of the name. Generated by the database, not entered by the user (candidate key)
FamilyNameID int NameID of the family
Family nvarchar (500) The name of the family

Depending on:

  • TaxonHierarchy
  • TaxonName

Function HierarchyList

Returns a result set that lists hierarchy of the taxa in a given project

Parameter DataType Description
@ProjectID int Each project can implement a different taxonomic hierarchy. Refers to the common project definition in the DiversityProjects module.
Column DataType Description
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
TaxonNameCache nvarchar (500) A full unique version of the name. Generated by the database, not entered by the user (candidate key)
Hierarchy nvarchar (2000) Hierarchy above the taxon separated by "

Depending on:

  • TaxonHierarchy
  • TaxonName
  • TaxonNameTaxonomicRank_Enum

Function HierarchyOrderList

Returns a result set that lists all orders of the taxa in a given project.

Parameter DataType Description
@ProjectID int Each project can implement a different taxonomic hierarchy. Refers to the common project definition in the DiversityProjects module.
Column DataType Description
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
TaxonNameCache nvarchar (500) A full unique version of the name. Generated by the database, not entered by the user (candidate key)
OrderNameID int NameID of the order
Order nvarchar (500) Name of the order

Depending on:

  • TaxonHierarchy
  • TaxonName

Function HierarchySuperiorList

Returns a result set that lists all the taxa superior to a given taxon

Parameter DataType Description
@NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
@ProjectID int Each project can implement a different taxonomic hierarchy. Refers to the common project definition in the DiversityProjects module.
Column DataType Description
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
NameParentID int Next higher taxon (e.g. the family or subfamily if this taxon is a genus)
Seq int The sequence for the hierarchy starting with 1 for the Taxon corresponding to the given NameID
TaxonNameCache nchar (500) A full unique version of the name. Generated by the database, not entered by the user (candidate key)
Taxon nvarchar (500) Taxon excluding authors
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank)
TaxonomicRankDisplayText nvarchar (50) The taxonomic rank in the case of a infraspecific taxon

Depending on:

  • TaxonHierarchy
  • TaxonHierarchy_Core
  • TaxonName
  • TaxonNameTaxonomicRank_Enum

Function NameList

Returns a result set that lists all the taxa starting with a string corresponding to @NameStart and including the taxon corresponding to @NameID

Parameter DataType Description
@NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key)
@NameStart nvarchar (255) Initial string of the taxon (TaxonNameCache)
Column DataType Description
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key)
TaxonName nvarchar (200) Content of column TaxonNameCache

Depending on:

  • TaxonName

Function NextNameID

Returns the next free NameID in the table TaxonName for the taxonomic group

DataType: int

Parameter DataType Description
@InitialNameID int ID of the name where the query should start
@TaxonomicGroup nvarchar (50) TaxonomicGroup of the name. Ranges for the groups:
Biota: 0
Myxomycetes: 1 - 99 999
Plants: 100 000 - 999 999
Lichens: 1 000 000 - 1 999 999
Fungi: 2 000 000 - 2 999 999
Vertebrata: 3 000 000 - 3 999 999

Depending on:

  • TaxonName

Function PrivacyConsentInfo

Website with information about the privacy consent. Default = http://diversityworkbench.net/Portal/Default_Agreement_on_Processing_of_Personal_Data_in_DWB_Software

DataType: varchar (900)


Function SynonymyList

Returns a result set that lists all the Synonyms for a given name

Parameter DataType Description
@NameID int ID of the synonymized name. Refers to the NameID of TaxonName (= foreign key).
@ProjectID int ProjectID of the synonymy
@Level int the depth of the synonymy that should be requested. 0 = only linked via the basionym. Default = 3
Column DataType Description
NameID int ID of the synonymized name. Refers to the NameID of TaxonName (= foreign key).
DisplayText nvarchar (900) A preformatet textstring for display in a synoymlist
TaxonName nvarchar (500) The name of the taxon including the genus and the species epithet
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank)
InfraspecificEpithet nvarchar (200) The epithet of the infraspecific entity
Authors nvarchar (500) The combined authors of this name
SynonymText nvarchar (500) The text string containing the citation of the synonymisation
Prefix nvarchar (5) The prefix as used in synonym lists
Ord int The preferred sequence of the synonyms. The numbers in Ord correspond to the different kinds of the synonyms:
-20 = Accepted name
-10 = Basionym
0 = Homotypic Synonym

0 = Heterotypic Synoyms
x + 1 = Isonym resp. Assigned to like ‘duplicate’, ‘isonym’, ‘orthographic variant’ (will be display after the name it is a variant of) | | YearOfPubl | int | The year when the name was published | | TaxonNameCache | nvarchar (255) | A full unique version of the name. Generated by the database, not entered by the user (candidate key) | | ConceptSuffix | nvarchar (200) | Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. | | ConceptNotes | nvarchar (500) | Notes on the concept of the name, e.g. incl. forms with black apothecia | | BasedOnNameID | int | The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. | | SynType | nvarchar (50) | Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ | | SynNameID | int | The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key). | | NameParentID | int | The NameID of the parent within the synonymy |

Depending on:

  • DefaultProjectID
  • SynonymyListCache
  • TaxonAcceptedName
  • TaxonAcceptedNameList
  • TaxonName
  • TaxonSynonymy
  • TaxonSynonymyList

Function SynonymyListIncludeIgnored

Returns a result set that lists all the Synonyms for a given name

Parameter DataType Description
@NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key).
@ProjectID int Each project can have a different opinion regarding synonmy. Refers to the common project definition in the DiversityProjects module.
@Level int the depth of the synonymy that should be requested. 0 = only linked via the basionym. Default = 3
Column DataType Description
NameID int ID of the accepted name. Refers to the NameID of TaxonName (= foreign key).
DisplayText nvarchar (900) A preformatet textstring for display in a synoymlist
TaxonName nvarchar (500) The name of the taxon including the genus and the species epithet
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank)
InfraspecificEpithet nvarchar (200) The epithet of the infraspecific entity
Authors nvarchar (500) The combined authors of this name
SynonymText nvarchar (500) The text string containing the citation of the synonymisation
Prefix nvarchar (5) The prefix as used in synonym lists
Ord int The preferred sequence of the synonyms. The numbers in Ord correspond to the different kinds of the synonyms:
-20 = Accepted name
-10 = Basionym
0 = Homotypic Synonym

0 = Heterotypic Synoyms
x + 1 = Isonym resp. Assigned to like ‘duplicate’, ‘isonym’, ‘orthographic variant’ (will be display after the name it is a variant of) | | YearOfPubl | int | The year when the name was published | | TaxonNameCache | nvarchar (255) | A full unique version of the name. Generated by the database, not entered by the user (candidate key) | | ConceptSuffix | nvarchar (200) | Empty for default and primary concept; else ’s. lat.’, ’s. str.’, ‘sec.’, ‘sensu Muell.’, ’emend.’ , ‘(Auct.)’ etc. | | ConceptNotes | nvarchar (500) | Notes on the concept of the name, e.g. incl. forms with black apothecia | | BasedOnNameID | int | The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID. | | SynType | nvarchar (50) | Type of the synonymization, e.g. ‘heterotypic’, ‘homotypic’ | | SynNameID | int | The ID of the synonym to which this name has been assigned to. Refers to the NameID of TaxonName (= foreign key). | | NameParentID | int | - | | IgnoreButKeepForReference | bit | If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead. |

Depending on:

  • DefaultProjectID
  • TaxonAcceptedName
  • TaxonAcceptedNameListIncludeIgnored
  • TaxonName
  • TaxonSynonymy
  • TaxonSynonymyListIncludeIgnored

Function TaxonChildNodes

Returns the list of taxa within the hierarchy underneath the taxon with the given NameID

Parameter DataType Description
@NameID int The NameID of the taxon for which the hierarchy should be retrieved
@ProjectID int The ProjectID of the taxon for which the hierarchy should be retrieved
Column DataType Description
NameID int Unique NameID code of the higher taxon. Refers to the NameID code of LichenName (= foreign key).
TaxonNameCache nvarchar (255) A full unique version of the name. Generated by the database, not entered by the user (candidate key)
Version smallint The version of a name record (revision number, internally filled by system)
BasedOnNameID int The Basionym of this name, resp. the NameID of the Basionym. A name is a Basionym, if NameID = BasionymID.
CreationType nvarchar (50) E.g.: taxon based on new type, combination based on a previously publ. name (‘comb. nov.’), new name (’nom.nov.’) introduced to replace a homonym (may occur for genera!), validation of previously invalidly publ. taxon name (’ex’), or unknown.
TaxonomicRank nvarchar (50) Taxonomic rank of the taxon (var., subsp., species, genus, family, order, etc.). The rank must be selected from the associated list of ranks (= TaxonomyRank)
GenusOrSupragenericName nvarchar (200) If rank is above species: Name of taxon above species level (currently accepted spelling). Includes infrageneric taxon names, genera, families, etc.
SpeciesGenusNameID int If rank is species or below: NameID of the Genus name. Refers to same table with TaxonomicRank = genus.
InfragenericEpithet nvarchar (200) If rank below genus and above species: Name of infrageneric taxon above species level (currently accepted spelling). Includes subgenus, series, etc.
SpeciesEpithet nvarchar (100) The species name part of the species name, for example ‘alba’ in ‘Abies alba’.
InfraspecificEpithet nvarchar (100) The epithet of the infraspecific entity
BasionymAuthors nvarchar (100) The authors of a newly created name. For all taxonomic ranks, only for ‘comb. nov.’ or ’nom. nov.’: Author(s) of the basionym (will be displayed in ‘()’, do not enter the parentheses), abbreviated according to authors standard
CombiningAuthors nvarchar (255) The names of the combining authors if the name is base on another older name (e.g. combined into a different genus)
PublishingAuthors nvarchar (255) If the authors of the taxon differ from the authors of the publication: the latter (…‘in ’ Publishing authors … )
SanctioningAuthor nvarchar (100) Sanctioning is a special instrument available for fungi to allow the starting date of taxonomy to be identical with higher plants, but preserve names used by Fries (Fr.) and Person (Pers.)
NonNomenclaturalNameSuffix nvarchar (200) A suffix for concept names not included in any nomenclatural code. If present fields for authors and typification must be empty and NomenclaturalCode set to ’not under code’.
IsRecombination bit True if the name is a recombination
IsHybrid bit If checked (or ‘True’), the new taxon is a hybrid with or without a hybrid epithet.
HybridNameID1 int If IsHybrid is checked (or ‘True’): Name of hybrid species 1. Refers to NomID code of publ. TaxonomyName (= foreign key).
HybridNameID2 int If IsHybrid is checked (or ‘True’): Name of hybrid species 2. Refers to NomID code of publ. TaxonomyName (= foreign key).
HybridNameID3 int If IsHybrid is checked (or ‘True’): Name of hybrid species 3. Refers to NomID code of publ. TaxonomyName (= foreign key).
HybridNameID4 int If IsHybrid is checked (or ‘True’): Name of hybrid species 4. Refers to NomID code of publ. TaxonomyName (= foreign key).
ReferenceTitle nvarchar (600) The title of the publication where the name was published. Note this is only a cached value where ReferenceURI is present
ReferenceURI varchar (255) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in Database DiversityReferences: Source publication where name is published
Volume nvarchar (20) The volume of the journal
Issue nvarchar (255) The issue of the literature
Pages nvarchar (50) The pages within the literature
DetailLocation nvarchar (200) Additional information like plates etc.
DayOfPubl tinyint The day when the name was published
MonthOfPubl tinyint The month when the name was published
YearOfPubl smallint The year when the name was published
DateOfPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’
YearOnPubl smallint The year cited on the original paper as year of publication
DateOnPublSupplement nvarchar (200) Verbal or additional date information, e.g. ’end of summer 1985’, ‘first quarter’, ‘1888-1892’
Protologue nvarchar (MAX) Full text of the protologue. If protologue is provided in Latin and in another language
languages, both only the Latin or several languages may be stored together.
ProtologueURI varchar (255) URI of externally available Protologue information (scanned image, full text from external provider, etc.)
ProtologueResourceURI varchar (255) The ResourceID of an image of the protologue as stored in the module DiversityResources. Primary key of table Resource in the database DiversityResources.(= Foreign key)
NameUsageReferences nvarchar (255) Indexing volumes like Index of Fungi or any Name usage that caused this name to be added to the database
OriginalOrthography nvarchar (255) The original spelling of the name
NomenclaturalCode nvarchar (50) Code of Nomenclature under which this taxon was created: ‘Bacteriology’, ‘Botany’ (incl. Mycology), ‘Zoology’, ‘Biocode’ (for future use), ‘Non nomenclatural name’. Default value: ‘Botany’
NomenclaturalStatus nvarchar (50) Categories for effective/valid/legitimate… esp. ’nom. illeg.’, ’nom. inval.’, ’nom. nudum’, etc.
NomenclaturalComment nvarchar (MAX) Comments on the nomenclature. e.g. ‘according to ICBN Art. 39.1’
Typification nvarchar (50) The status of the type specimen(s) as written in the protologue, e.g. holotype
TypificationDetails nvarchar (255) Details concerning the typification as written in the protologue, e.g. if just parts of a specimen were accepted as the type
TypificationReferenceTitle nvarchar (255) The title of the publication where the typification was published. Note this is only a cached value where Typification-LiteratureLink is present
TypificationReferenceURI varchar (255) URI (e.g. LSID) of Reference, refers to e.g DiversityReferences: Source publication where the typification is published
TypificationNotes nvarchar (200) Notes concerning the typification
TypeSubstrate nvarchar (255) The substrate the type was growing on as written in the protologue
TypeLocality nvarchar (255) The locality where the type was found as written in the protologue
TypeSpecimenNotes nvarchar (200) Notes about the type specimen, e.g. the herbarium where a type specimen is located, Collector, collection date/number, etc.
AnamorphTeleomorph nvarchar (255) If the name is related to a anamorph or a teleomorph as written in the protologue
TypistNotes nvarchar (200) Additional notes and problems
RevisionLevel nvarchar (50) The level of the revision of the taxonomic name, e.g. ‘unchecked’, ‘fully checked’
IgnoreButKeepForReference bit If true, the record is ignored for all purposes of evaluation (because contradicted). It is kept only to maintain the cited reference. If no reference is given, it may be deleted instead.
DataWithholdingReason nvarchar (255) If the dataset is withhold, the reason for withholding the data, otherwise null
BasionymAuthorsYear int The year when the name was published by the authors of the Basionym
FamiliyCache nvarchar (50) Name of the family
OrderCache nvarchar (50) Name of the order
HierarchyCache nvarchar (MAX) Hierarchy above the current taxon starting at top level and separated via "

Depending on:

  • TaxonHierarchy
  • TaxonName

Function TaxonListLastUpdate

Returns the last date when any list related data were updated

DataType: datetime

Parameter DataType Description
@ListID int ProjectID as defined in table TaxonNameListProjectProxy

Depending on:

  • TaxonNameList
  • TaxonNameListAnalysis
  • TaxonNameListArea
  • TaxonNameListCollectionSpecimen
  • TaxonNameListDistribution
  • TaxonNameListReference

Function TaxonListsForUser

Returns the taxon lists for a user as defined in table TaxonNameListUser

Parameter DataType Description
@Login nvarchar (50) Login of the user as stored in table TaxonNameListUser
Column DataType Description
ProjectID int ID of the Project, Primary key. May be related to module DiversityProjects
DataSource nvarchar (50) The project as defined in table TaxonNameListProjectProxy
DisplayText nvarchar (50) The text as shown in a user interface. Corresponds to ProjectTitle in DiversityProjects.Project
TaxonomicGroup nvarchar (50) The taxonomic group as used in DiversityCollection resp. DiversityMobile
DefaultProjectID int The ID of the default project where informations about e.g. the synonymy are taken from

Depending on:

  • TaxonNameListProjectProxy
  • TaxonNameListUser

Function TaxonListsLastUpdate

Function providing informations needed by the webservice: Returns a result set that lists all the taxon lists and the date of their last change

Column DataType Description
maxlog smalldatetime Date of the last change of a TaxonList
projectid int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module.

Depending on:

  • TaxonName
  • TaxonName_Log
  • TaxonNameList

Function TaxonNameCache

Returns the TaxonNameCache for a taxon

DataType: nvarchar (255)

Parameter DataType Description
@NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key)

Depending on:

  • TaxonName

Function TaxonNameCacheSinAut

returns the TaxonName for a taxon excluding authors

DataType: nvarchar (255)

Parameter DataType Description
@NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key)

Depending on:

  • TaxonName

Function TaxonNameListAnalysisCategoryChildNodes

Returns a result set that lists all analysis items within a hierarchy starting at the topmost item related to the given item

Parameter DataType Description
@ID int AnalysisID of the analysis for which the child nodes should be returned
Column DataType Description
AnalysisID int ID of the analysis (Primary key)
AnalysisParentID int Analysis ID of the parent analysis if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (500) Description of the analysis
Notes nvarchar (1000) Notes concerning this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
ReferenceTitle nvarchar (800) The title of the publication where details about the analysis are published. Note this is only a cached value where ReferenceURI is present
ReferenceURI varchar (400) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in module DiversityReferences: Source publication where details about the analysis are published
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null
SortingID int An ID for sorting the data

Depending on:

  • TaxonNameListAnalysisCategory

Function TaxonNameListAnalysisCategoryHierarchy

Returns a table that lists all the analysis items related to the given analysis

Parameter DataType Description
@AnalysisID int ID of the analysis (Primary key)
Column DataType Description
AnalysisID int ID of the analysis (Primary key)
AnalysisParentID int Analysis ID of the parent analysis if it belongs to a certain type documented in this table
DisplayText nvarchar (50) Name of the analysis as e.g. shown in user interface
Description nvarchar (500) Description of the analysis
Notes nvarchar (1000) Notes concerning this analysis
AnalysisURI varchar (255) URI referring to an external documentation of the analysis
ReferenceTitle nvarchar (800) The title of the publication where details about the analysis are published. Note this is only a cached value where ReferenceURI is present
ReferenceURI varchar (400) URI (e.g. LSID) of Reference, referes to table ReferenceTitle in module DiversityReferences: Source publication where details about the analysis are published
DataWithholdingReason nvarchar (255) If the data set is withhold, the reason for withholding the data, otherwise null
SortingID int An ID for sorting the data

Depending on:

  • TaxonNameListAnalysisCategory
  • TaxonNameListAnalysisCategoryChildNodes

Function TaxonNameListUserNameID

Returns a result set that lists all the NameIDs for a user related to the taxon lists

Column DataType Description
NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key)

Depending on:

  • TaxonName
  • TaxonNameList
  • TaxonNameListUser

Function UserID

ID of the User as stored in table UserProxy

DataType: int

Depending on:

  • UserProxy

Function Version

Version of the database

DataType: nvarchar (8)


Function VersionClient

Version of the client compatible with the database

DataType: nvarchar (11)


PROCEDURES


Procedure procFillSynonymyListCache

Fills table SynonymyListCache for the given NameID or any if missing and ProjectID or any if missing

Parameter DataType Description
@ProjectID int The ProjectID of the taxon for which the hierarchy should be retrieved
@NameID int The NameID of the taxon for which the hierarchy should be retrieved
@Level int The level how deep the hierarchy should extracted

Depending on:

  • ProjectProxy
  • SynonymyList
  • SynonymyListCache
  • TaxonName

Procedure procHierarchyCache

Update of the hierarchy cache for all entries with disabled triggers to avoid increase of logfile entries

Depending on:

  • HierarchyList
  • TaxonHierarchy

Procedure procSetVersionTaxonName

Setting the value for column Version in table TaxonName

Parameter DataType Description
@ID int The NameID of the taxon

Depending on:

  • TaxonName

Procedure procTaxonNameInsertCopy

Copy all entries of a name into a new dataset

Parameter DataType Description
@NameID int The ID of a name in DiversityTaxonNames (foreign key + part of primary key: the name may occur in multiple projects)
@OriginalNameID int The NameID of the dataset that should be copied
@Projects varchar (8000) List of comma separated ProjectIDs that should be copied

Depending on:

  • DefaultProjectID
  • NextNameID
  • ProjectList
  • TaxonHierarchy_Core
  • TaxonName_Core
  • TaxonNameProject

Procedure procTaxonNameInsertNew_3

Inserts a new dataset in the table TaxonName

Parameter DataType Description
@NameID int The ID of a name in DiversityTaxonNames_Fungi (primary key)
@Projects varchar (8000) Comma separated list of the project IDs for which the new taxon should be inserted
@NomenclaturalCode int Code of Nomenclature under which this taxon was created: ‘Bacteriology’, ‘Botany’ (incl. Mycology), ‘Zoology’, ‘Biocode’ (for future use), ‘Non nomenclatural name’. Default value: ‘Botany’

Depending on:

  • TaxonName
  • TaxonNameProject

Procedure procTaxonNameListInsertCopy

Copy all list entries of a name into the list of the current name

Parameter DataType Description
@NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key).
@OriginalNameID int The NameID of the dataset that should be copied
@ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module.

Depending on:

  • TaxonNameList
  • TaxonNameListAnalysis
  • TaxonNameListCollectionSpecimen
  • TaxonNameListDistribution
  • TaxonNameListReference

Procedure procTaxonNameListInsertReferenceCopy

Copy all list entries of a name into the list of the current name

Parameter DataType Description
@NameID int ID of the name. Refers to the NameID of TaxonName (= foreign key).
@O_TaxonNameListRefID int The PK of the reference that should be copied
@ProjectID int Each project can may contain one taxon list. Refers to the common project definition in the DiversityProjects module.

Depending on:

  • TaxonNameList
  • TaxonNameListAnalysis
  • TaxonNameListDistribution
  • TaxonNameListReference

Procedure SetUserProjects

Create database user and assign training projects

Parameter DataType Description
@User varchar (50) Login of the user

Depending on:

  • UserProxy

ROLES

Content of cell Permission
Not granted
Name of other role Inherited from other role
Granted

Role DiversityWorkbenchAdministrator

Role for administration of the database content

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
CountryCode_Enum Diversity Workbench User TABLE
LanguageCode_Enum Diversity Workbench User TABLE
ProjectUser TABLE
ReplicationPublisher TABLE
SynonymyListCache Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonAcceptedName Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonAcceptedName_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonCommonName Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonCommonName_log TABLE
TaxonGeography Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonGeography_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonHierarchy Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonHierarchy_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonName Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonName_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameCreationType_Enum Diversity Workbench User TABLE
TaxonNameExternalDatabase Diversity Workbench User TABLE
TaxonNameExternalDatabase_log TABLE
TaxonNameExternalID Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameExternalID_log TABLE
TaxonNameList Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameList_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListAnalysis Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListAnalysis_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListAnalysisCategory Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListAnalysisCategory_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListAnalysisCategoryValue Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListAnalysisCategoryValue_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListArea Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListArea_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListCollectionSpecimen Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListCollectionSpecimen_log TABLE
TaxonNameListDistribution Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListDistribution_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListImage TABLE
TaxonNameListImage_log TABLE
TaxonNameListReference Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameListReference_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameListReferenceType_Enum Diversity Workbench User TABLE
TaxonNameListSpecimenRole_Enum Diversity Workbench User TABLE
TaxonNameListUser Diversity Workbench User TABLE
TaxonNameNomenclaturalCode_Enum Diversity Workbench User TABLE
TaxonNameNomenclaturalStatus_Enum Diversity Workbench User TABLE
TaxonNameProject Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameProject_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameReference Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameReference_log Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameResource Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameResource_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonNameResourceType_Enum Diversity Workbench User TABLE
TaxonNameRevisionLevel_Enum Diversity Workbench User TABLE
TaxonNameSynonymisationType_Enum Diversity Workbench User TABLE
TaxonNameTaxonomicRank_Enum Diversity Workbench User TABLE
TaxonNameTypification Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonNameTypification_log Diversity Workbench User Diversity Workbench Editor TABLE
TaxonSynonymy Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor TABLE
TaxonSynonymy_log Diversity Workbench Editor Diversity Workbench Editor TABLE
AcceptedNameChanges Diversity Workbench User VIEW
GenusList VIEW
NameID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
TaxonAcceptedName_Core Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor VIEW
TaxonAcceptedName_Indicated Diversity Workbench User VIEW
TaxonAcceptedNameList Diversity Workbench User VIEW
TaxonAcceptedNameListIncludeIgnored Diversity Workbench User VIEW
TaxonFamily Diversity Workbench User VIEW
TaxonGeography_Core Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor VIEW
TaxonHierarchy_Core Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor VIEW
TaxonListSynType Diversity Workbench User VIEW
TaxonName_Core Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor VIEW
TaxonName_Indicated Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor VIEW
TaxonNameExternalID_Core Diversity Workbench User VIEW
TaxonOrder Diversity Workbench User VIEW
TaxonSynonymy_Core Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor VIEW
TaxonSynonymy_Indicated Diversity Workbench User VIEW
TaxonSynonymyAcceptedNameID Diversity Workbench User VIEW
TaxonSynonymyList Diversity Workbench User VIEW
TaxonSynonymyListIncludeIgnored Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDefaultProjectID Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewTaxonNameResource Diversity Workbench User Diversity Workbench Editor Diversity Workbench Editor Diversity Workbench Editor VIEW
AcceptedNameID Diversity Workbench User FUNCTION
AnalysisCategoryHierarchyAll Diversity Workbench User FUNCTION
BaseURL Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityMobile_TaxonList Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
HierarchyCache Diversity Workbench Editor FUNCTION
HierarchyFamilyList Diversity Workbench User FUNCTION
HierarchyList Diversity Workbench User FUNCTION
HierarchyOrderList Diversity Workbench User FUNCTION
HierarchySuperiorList Diversity Workbench User FUNCTION
NameList Diversity Workbench User FUNCTION
NextNameID Diversity Workbench Editor FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
SynonymyList Diversity Workbench User FUNCTION
SynonymyListIncludeIgnored Diversity Workbench User FUNCTION
TaxonChildNodes Diversity Workbench User FUNCTION
TaxonListLastUpdate Diversity Workbench User FUNCTION
TaxonListsForUser Diversity Workbench User FUNCTION
TaxonListsLastUpdate Diversity Workbench User FUNCTION
TaxonNameCache Diversity Workbench User FUNCTION
TaxonNameCacheSinAut Diversity Workbench User FUNCTION
TaxonNameListAnalysisCategoryChildNodes Diversity Workbench User FUNCTION
TaxonNameListAnalysisCategoryHierarchy Diversity Workbench User FUNCTION
TaxonNameListUserNameID Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procFillSynonymyListCache Diversity Workbench Editor PROCEDURE
procHierarchyCache Diversity Workbench Editor PROCEDURE
procSetVersionTaxonName PROCEDURE
procTaxonNameInsertCopy Diversity Workbench Editor PROCEDURE
procTaxonNameInsertNew_3 Diversity Workbench Editor PROCEDURE
procTaxonNameListInsertCopy Diversity Workbench Editor PROCEDURE
procTaxonNameListInsertReferenceCopy Diversity Workbench Editor PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchEditor

Role DiversityWorkbenchEditor

Role for editing the user dependent content of the database

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
CountryCode_Enum Diversity Workbench User TABLE
LanguageCode_Enum Diversity Workbench User TABLE
ProjectUser Diversity Workbench User TABLE
ReplicationPublisher TABLE
SynonymyListCache Diversity Workbench User TABLE
TaxonAcceptedName Diversity Workbench User TABLE
TaxonAcceptedName_log TABLE
TaxonCommonName Diversity Workbench User TABLE
TaxonCommonName_log TABLE
TaxonGeography Diversity Workbench User TABLE
TaxonGeography_log TABLE
TaxonHierarchy Diversity Workbench User TABLE
TaxonHierarchy_log TABLE
TaxonName Diversity Workbench User TABLE
TaxonName_log TABLE
TaxonNameCreationType_Enum Diversity Workbench User TABLE
TaxonNameExternalDatabase Diversity Workbench User TABLE
TaxonNameExternalDatabase_log TABLE
TaxonNameExternalID Diversity Workbench User TABLE
TaxonNameExternalID_log TABLE
TaxonNameList Diversity Workbench User TABLE
TaxonNameList_log Diversity Workbench User TABLE
TaxonNameListAnalysis Diversity Workbench User TABLE
TaxonNameListAnalysis_log Diversity Workbench User TABLE
TaxonNameListAnalysisCategory Diversity Workbench User TABLE
TaxonNameListAnalysisCategory_log Diversity Workbench User TABLE
TaxonNameListAnalysisCategoryValue Diversity Workbench User TABLE
TaxonNameListAnalysisCategoryValue_log Diversity Workbench User TABLE
TaxonNameListArea Diversity Workbench User TABLE
TaxonNameListArea_log Diversity Workbench User TABLE
TaxonNameListCollectionSpecimen Diversity Workbench User TABLE
TaxonNameListCollectionSpecimen_log TABLE
TaxonNameListDistribution Diversity Workbench User TABLE
TaxonNameListDistribution_log Diversity Workbench User TABLE
TaxonNameListImage TABLE
TaxonNameListImage_log TABLE
TaxonNameListReference Diversity Workbench User TABLE
TaxonNameListReference_log Diversity Workbench User TABLE
TaxonNameListReferenceType_Enum Diversity Workbench User TABLE
TaxonNameListSpecimenRole_Enum Diversity Workbench User TABLE
TaxonNameListUser Diversity Workbench User TABLE
TaxonNameNomenclaturalCode_Enum Diversity Workbench User TABLE
TaxonNameNomenclaturalStatus_Enum Diversity Workbench User TABLE
TaxonNameProject Diversity Workbench User TABLE
TaxonNameProject_log TABLE
TaxonNameReference Diversity Workbench User TABLE
TaxonNameReference_log TABLE
TaxonNameResource Diversity Workbench User TABLE
TaxonNameResource_log Diversity Workbench User TABLE
TaxonNameResourceType_Enum Diversity Workbench User TABLE
TaxonNameRevisionLevel_Enum Diversity Workbench User TABLE
TaxonNameSynonymisationType_Enum Diversity Workbench User TABLE
TaxonNameTaxonomicRank_Enum Diversity Workbench User TABLE
TaxonNameTypification TABLE
TaxonNameTypification_log Diversity Workbench User TABLE
TaxonSynonymy Diversity Workbench User TABLE
TaxonSynonymy_log TABLE
AcceptedNameChanges Diversity Workbench User VIEW
GenusList VIEW
NameID_UserAvailable Diversity Workbench User VIEW
ProjectList Diversity Workbench User VIEW
TaxonAcceptedName_Core Diversity Workbench User VIEW
TaxonAcceptedName_Indicated Diversity Workbench User VIEW
TaxonAcceptedNameList Diversity Workbench User VIEW
TaxonAcceptedNameListIncludeIgnored Diversity Workbench User VIEW
TaxonFamily Diversity Workbench User VIEW
TaxonGeography_Core Diversity Workbench User VIEW
TaxonHierarchy_Core Diversity Workbench User VIEW
TaxonListSynType Diversity Workbench User VIEW
TaxonName_Core Diversity Workbench User VIEW
TaxonName_Indicated Diversity Workbench User VIEW
TaxonNameExternalID_Core Diversity Workbench User VIEW
TaxonOrder Diversity Workbench User VIEW
TaxonSynonymy_Core Diversity Workbench User VIEW
TaxonSynonymy_Indicated Diversity Workbench User VIEW
TaxonSynonymyAcceptedNameID Diversity Workbench User VIEW
TaxonSynonymyList Diversity Workbench User VIEW
TaxonSynonymyListIncludeIgnored Diversity Workbench User VIEW
ViewBaseURL Diversity Workbench User VIEW
ViewDefaultProjectID Diversity Workbench User VIEW
ViewDiversityWorkbenchModule Diversity Workbench User VIEW
ViewTaxonNameResource Diversity Workbench User VIEW
AcceptedNameID Diversity Workbench User FUNCTION
AnalysisCategoryHierarchyAll Diversity Workbench User FUNCTION
BaseURL Diversity Workbench User FUNCTION
DefaultProjectID Diversity Workbench User FUNCTION
DiversityMobile_TaxonList Diversity Workbench User FUNCTION
DiversityWorkbenchModule Diversity Workbench User FUNCTION
HierarchyCache FUNCTION
HierarchyFamilyList Diversity Workbench User FUNCTION
HierarchyList Diversity Workbench User FUNCTION
HierarchyOrderList Diversity Workbench User FUNCTION
HierarchySuperiorList Diversity Workbench User FUNCTION
NameList Diversity Workbench User FUNCTION
NextNameID FUNCTION
PrivacyConsentInfo Diversity Workbench User FUNCTION
SynonymyList Diversity Workbench User FUNCTION
SynonymyListIncludeIgnored Diversity Workbench User FUNCTION
TaxonChildNodes Diversity Workbench User FUNCTION
TaxonListLastUpdate Diversity Workbench User FUNCTION
TaxonListsForUser Diversity Workbench User FUNCTION
TaxonListsLastUpdate Diversity Workbench User FUNCTION
TaxonNameCache Diversity Workbench User FUNCTION
TaxonNameCacheSinAut Diversity Workbench User FUNCTION
TaxonNameListAnalysisCategoryChildNodes Diversity Workbench User FUNCTION
TaxonNameListAnalysisCategoryHierarchy Diversity Workbench User FUNCTION
TaxonNameListUserNameID Diversity Workbench User FUNCTION
UserID Diversity Workbench User FUNCTION
Version Diversity Workbench User FUNCTION
VersionClient Diversity Workbench User FUNCTION
procFillSynonymyListCache PROCEDURE
procHierarchyCache PROCEDURE
procSetVersionTaxonName PROCEDURE
procTaxonNameInsertCopy PROCEDURE
procTaxonNameInsertNew_3 PROCEDURE
procTaxonNameListInsertCopy PROCEDURE
procTaxonNameListInsertReferenceCopy PROCEDURE
SetUserProjects PROCEDURE
Inheriting from roles:
  • DiversityWorkbenchUser

Role DiversityWorkbenchReplicator

Role involved in the replication of data

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
CountryCode_Enum TABLE
LanguageCode_Enum TABLE
ProjectUser TABLE
ReplicationPublisher TABLE
SynonymyListCache TABLE
TaxonAcceptedName TABLE
TaxonAcceptedName_log TABLE
TaxonCommonName TABLE
TaxonCommonName_log TABLE
TaxonGeography TABLE
TaxonGeography_log TABLE
TaxonHierarchy TABLE
TaxonHierarchy_log TABLE
TaxonName TABLE
TaxonName_log TABLE
TaxonNameCreationType_Enum TABLE
TaxonNameExternalDatabase TABLE
TaxonNameExternalDatabase_log TABLE
TaxonNameExternalID TABLE
TaxonNameExternalID_log TABLE
TaxonNameList TABLE
TaxonNameList_log TABLE
TaxonNameListAnalysis TABLE
TaxonNameListAnalysis_log TABLE
TaxonNameListAnalysisCategory TABLE
TaxonNameListAnalysisCategory_log TABLE
TaxonNameListAnalysisCategoryValue TABLE
TaxonNameListAnalysisCategoryValue_log TABLE
TaxonNameListArea TABLE
TaxonNameListArea_log TABLE
TaxonNameListCollectionSpecimen TABLE
TaxonNameListCollectionSpecimen_log TABLE
TaxonNameListDistribution TABLE
TaxonNameListDistribution_log TABLE
TaxonNameListImage TABLE
TaxonNameListImage_log TABLE
TaxonNameListReference TABLE
TaxonNameListReference_log TABLE
TaxonNameListReferenceType_Enum TABLE
TaxonNameListSpecimenRole_Enum TABLE
TaxonNameListUser TABLE
TaxonNameNomenclaturalCode_Enum TABLE
TaxonNameNomenclaturalStatus_Enum TABLE
TaxonNameProject TABLE
TaxonNameProject_log TABLE
TaxonNameReference TABLE
TaxonNameReference_log TABLE
TaxonNameResource TABLE
TaxonNameResource_log TABLE
TaxonNameResourceType_Enum TABLE
TaxonNameRevisionLevel_Enum TABLE
TaxonNameSynonymisationType_Enum TABLE
TaxonNameTaxonomicRank_Enum TABLE
TaxonNameTypification TABLE
TaxonNameTypification_log TABLE
TaxonSynonymy TABLE
TaxonSynonymy_log TABLE
AcceptedNameChanges VIEW
GenusList VIEW
NameID_UserAvailable VIEW
ProjectList VIEW
TaxonAcceptedName_Core VIEW
TaxonAcceptedName_Indicated VIEW
TaxonAcceptedNameList VIEW
TaxonAcceptedNameListIncludeIgnored VIEW
TaxonFamily VIEW
TaxonGeography_Core VIEW
TaxonHierarchy_Core VIEW
TaxonListSynType VIEW
TaxonName_Core VIEW
TaxonName_Indicated VIEW
TaxonNameExternalID_Core VIEW
TaxonOrder VIEW
TaxonSynonymy_Core VIEW
TaxonSynonymy_Indicated VIEW
TaxonSynonymyAcceptedNameID VIEW
TaxonSynonymyList VIEW
TaxonSynonymyListIncludeIgnored VIEW
ViewBaseURL VIEW
ViewDefaultProjectID VIEW
ViewDiversityWorkbenchModule VIEW
ViewTaxonNameResource VIEW
AcceptedNameID FUNCTION
AnalysisCategoryHierarchyAll FUNCTION
BaseURL FUNCTION
DefaultProjectID FUNCTION
DiversityMobile_TaxonList FUNCTION
DiversityWorkbenchModule FUNCTION
HierarchyCache FUNCTION
HierarchyFamilyList FUNCTION
HierarchyList FUNCTION
HierarchyOrderList FUNCTION
HierarchySuperiorList FUNCTION
NameList FUNCTION
NextNameID FUNCTION
PrivacyConsentInfo FUNCTION
SynonymyList FUNCTION
SynonymyListIncludeIgnored FUNCTION
TaxonChildNodes FUNCTION
TaxonListLastUpdate FUNCTION
TaxonListsForUser FUNCTION
TaxonListsLastUpdate FUNCTION
TaxonNameCache FUNCTION
TaxonNameCacheSinAut FUNCTION
TaxonNameListAnalysisCategoryChildNodes FUNCTION
TaxonNameListAnalysisCategoryHierarchy FUNCTION
TaxonNameListUserNameID FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
procFillSynonymyListCache PROCEDURE
procHierarchyCache PROCEDURE
procSetVersionTaxonName PROCEDURE
procTaxonNameInsertCopy PROCEDURE
procTaxonNameInsertNew_3 PROCEDURE
procTaxonNameListInsertCopy PROCEDURE
procTaxonNameListInsertReferenceCopy PROCEDURE
SetUserProjects PROCEDURE

Role DiversityWorkbenchUser

Role with read only access to the data

Permissions SELECT INSERT UPDATE DELETE EXECUTE Type
CountryCode_Enum TABLE
LanguageCode_Enum TABLE
ProjectUser TABLE
ReplicationPublisher TABLE
SynonymyListCache TABLE
TaxonAcceptedName TABLE
TaxonAcceptedName_log TABLE
TaxonCommonName TABLE
TaxonCommonName_log TABLE
TaxonGeography TABLE
TaxonGeography_log TABLE
TaxonHierarchy TABLE
TaxonHierarchy_log TABLE
TaxonName TABLE
TaxonName_log TABLE
TaxonNameCreationType_Enum TABLE
TaxonNameExternalDatabase TABLE
TaxonNameExternalDatabase_log TABLE
TaxonNameExternalID TABLE
TaxonNameExternalID_log TABLE
TaxonNameList TABLE
TaxonNameList_log TABLE
TaxonNameListAnalysis TABLE
TaxonNameListAnalysis_log TABLE
TaxonNameListAnalysisCategory TABLE
TaxonNameListAnalysisCategory_log TABLE
TaxonNameListAnalysisCategoryValue TABLE
TaxonNameListAnalysisCategoryValue_log TABLE
TaxonNameListArea TABLE
TaxonNameListArea_log TABLE
TaxonNameListCollectionSpecimen TABLE
TaxonNameListCollectionSpecimen_log TABLE
TaxonNameListDistribution TABLE
TaxonNameListDistribution_log TABLE
TaxonNameListImage TABLE
TaxonNameListImage_log TABLE
TaxonNameListReference TABLE
TaxonNameListReference_log TABLE
TaxonNameListReferenceType_Enum TABLE
TaxonNameListSpecimenRole_Enum TABLE
TaxonNameListUser TABLE
TaxonNameNomenclaturalCode_Enum TABLE
TaxonNameNomenclaturalStatus_Enum TABLE
TaxonNameProject TABLE
TaxonNameProject_log TABLE
TaxonNameReference TABLE
TaxonNameReference_log TABLE
TaxonNameResource TABLE
TaxonNameResource_log TABLE
TaxonNameResourceType_Enum TABLE
TaxonNameRevisionLevel_Enum TABLE
TaxonNameSynonymisationType_Enum TABLE
TaxonNameTaxonomicRank_Enum TABLE
TaxonNameTypification TABLE
TaxonNameTypification_log TABLE
TaxonSynonymy TABLE
TaxonSynonymy_log TABLE
AcceptedNameChanges VIEW
GenusList VIEW
NameID_UserAvailable VIEW
ProjectList VIEW
TaxonAcceptedName_Core VIEW
TaxonAcceptedName_Indicated VIEW
TaxonAcceptedNameList VIEW
TaxonAcceptedNameListIncludeIgnored VIEW
TaxonFamily VIEW
TaxonGeography_Core VIEW
TaxonHierarchy_Core VIEW
TaxonListSynType VIEW
TaxonName_Core VIEW
TaxonName_Indicated VIEW
TaxonNameExternalID_Core VIEW
TaxonOrder VIEW
TaxonSynonymy_Core VIEW
TaxonSynonymy_Indicated VIEW
TaxonSynonymyAcceptedNameID VIEW
TaxonSynonymyList VIEW
TaxonSynonymyListIncludeIgnored VIEW
ViewBaseURL VIEW
ViewDefaultProjectID VIEW
ViewDiversityWorkbenchModule VIEW
ViewTaxonNameResource VIEW
AcceptedNameID FUNCTION
AnalysisCategoryHierarchyAll FUNCTION
BaseURL FUNCTION
DefaultProjectID FUNCTION
DiversityMobile_TaxonList FUNCTION
DiversityWorkbenchModule FUNCTION
HierarchyCache FUNCTION
HierarchyFamilyList FUNCTION
HierarchyList FUNCTION
HierarchyOrderList FUNCTION
HierarchySuperiorList FUNCTION
NameList FUNCTION
NextNameID FUNCTION
PrivacyConsentInfo FUNCTION
SynonymyList FUNCTION
SynonymyListIncludeIgnored FUNCTION
TaxonChildNodes FUNCTION
TaxonListLastUpdate FUNCTION
TaxonListsForUser FUNCTION
TaxonListsLastUpdate FUNCTION
TaxonNameCache FUNCTION
TaxonNameCacheSinAut FUNCTION
TaxonNameListAnalysisCategoryChildNodes FUNCTION
TaxonNameListAnalysisCategoryHierarchy FUNCTION
TaxonNameListUserNameID FUNCTION
UserID FUNCTION
Version FUNCTION
VersionClient FUNCTION
procFillSynonymyListCache PROCEDURE
procHierarchyCache PROCEDURE
procSetVersionTaxonName PROCEDURE
procTaxonNameInsertCopy PROCEDURE
procTaxonNameInsertNew_3 PROCEDURE
procTaxonNameListInsertCopy PROCEDURE
procTaxonNameListInsertReferenceCopy PROCEDURE
SetUserProjects PROCEDURE
Mar 5, 2025

Diversity TaxonNames

Enumeration tables

The following objects are not included:

  • Logging tables
  • System objects
  • Objects marked as obsolete
  • Previous versions of objects

Table

Column Data type Description
Code nvarchar (50) A text code that uniquely identifies each object in the enumeration (primary key). This value may not be changed, because the application may depend upon it.
Description nvarchar (800) Description of enumerated object, displayed in the user interface
DisplayText nvarchar (50) Short abbreviated description of the object, displayed in the user interface
DisplayOrder smallint The order in which the entries are displayed. The order may be changed at any time, but all values must be unique.
DisplayEnable bit Enumerated objects can be hidden from the user interface if this attribute is set to false (= unchecked check box)
InternalNotes nvarchar (500) Internal development notes about usage, definition, etc. of an enumerated object
ParentCode nvarchar (50) The code of the superior entry, if a hierarchy within the entries is necessary
RowGUID uniqueidentifier -Default value: newsequentialid()

Content

Code Description DisplayText
1 Bacteriology Bacteriology
2 Botany (incl. Mycology) Botany (incl. Mycology)
3 Zoology Zoology
4 Biocode (for future use) Biocode (for future use)

Table CountryCode_Enum

2 letter codes for countries according to ISO 3166-1 alpha-2

Dependent tables:

  • TaxonCommonName

Content

Code Description DisplayText
AD Andorra Andorra
AE United Arab Emirates United Arab Emirates
AF Afghanistan Afghanistan
AG Antigua and Barbuda Antigua and Barbuda
AI Anguilla Anguilla
AL Albania Albania
AM Armenia Armenia
AO Angola Angola
AR Argentinia Argentinia
AS American Samoa American Samoa
AT Austria Austria
AU Australia Australia
AW Aruba Aruba
AZ Azerbaijan Azerbaijan
BA Bosnia and Herzegovina Bosnia and Herzegovina
BB Barbados Barbados
BD Bangladesh Bangladesh
BE Belgium Belgium
BF Burkina Faso Burkina Faso
BG Bulgaria Bulgaria
BH Bahrain Bahrain
BI Burundi Burundi
BJ Benin Benin
BM Bermuda Bermuda
BN Brunei Darussalam Brunei Darussalam
BO Bolivia Bolivia
BR Brazil Brazil
BS Bahamas Bahamas
BT Bhutan Bhutan
BW Botswana Botswana
BY Belarus Belarus
BZ Belize Belize
CA Canada Canada
CD congo The democratic republic of the congo The democratic republic of the
CF Central African Republic Central African Republic
CG Congo Congo
CH Switzerland Switzerland
CI Ivory Coast Ivory Coast
CK Cook Islands Cook Islands
CL Chile Chile
CM Cameroon Cameroon
CN China China
CO Colombia Colombia
CR Costa Rica Costa Rica
CU Cuba Cuba
CV Cape Verde Cape Verde
CX Christmas Island Christmas Island
CY Cyprus Cyprus
CZ Czech Republic Czech Republic
DE Germany Germany
DJ Djibouti Djibouti
DK Denmark Denmark
DM Dominica Dominica
DO Dominican Republic Dominican Republic
DZ Algeria Algeria
EC Ecuador Ecuador
EE Estonia Estonia
EG Egypt Egypt
ER Eritrea Eritrea
ES Spain Spain
ET Ethiopia Ethiopia
FI Finland Finland
FJ Fiji Fiji
FK Falkland Islands Falkland Islands
FO Faroe Islands Faroe Islands
FR France France
GA Gabon Gabon
GB United Kingdom United Kingdom
GD Grenada Grenada
GE Georgia Georgia
GF French Guiana French Guiana
GG Guernsey Guernsey
GH Ghana Ghana
GI Gibraltar Gibraltar
GL Greenland Greenland
GM Gambia Gambia
GN Guinea Guinea
GP Guadeloupe Guadeloupe
GR Greece Greece
GT Guatemala Guatemala
GU Guam Guam
GW Guinea-Bissau Guinea-Bissau
GY Guyana Guyana
HN Honduras Honduras
HR Croatia Croatia
HT Haiti Haiti
HU Hungary Hungary
ID Indonesia Indonesia
IE Ireland Ireland
IL Israel Israel
IM Isle of Man Isle of Man
IN India India
IQ Iraq Iraq
IR Iran Iran
IS Iceland Iceland
IT Italy Italy
JE Jersey Jersey
JM Jamaica Jamaica
JP Japan Japan
KE Kenya Kenya
KG Kyrgyzstan Kyrgyzstan
KH Cambodia Cambodia
KI Kiribati Kiribati
KM Comoros Comoros
KN Saint Kitts and Nevis Saint Kitts and Nevis
KY Cayman Islands Cayman Islands
KZ Kazakhstan Kazakhstan
LA Laos Laos
LB Lebanon Lebanon
LC Saint Lucia Saint Lucia
LI Liechtenstein Liechtenstein
LK Sri Lanka Sri Lanka
LR Liberia Liberia
LS Lesotho Lesotho
LT Lithuania Lithuania
LU Luxembourg Luxembourg
LV Latvia Latvia
LY Libya Libya
MA Morocco Morocco
MC Monaco Monaco
MD Moldova Moldova
MG Madagascar Madagascar
MH Marshall Islands Marshall Islands
MK Macedonia Macedonia
ML Mali Mali
MM Myanmar (Burma) Myanmar (Burma)
MN Mongolia Mongolia
MO Macao Macao
MP Northern Mariana Islands Northern Mariana Islands
MQ Martinique Martinique
MR Mauritania Mauritania
MS Montserrat Montserrat
MT Malta Malta
MU Mauritius Mauritius
MV Maldives Maldives
MW Malawi Malawi
MX Mexico Mexico
MY Malaysia Malaysia
MZ Mozambique Mozambique
NA Namibia Namibia
NC New Caledonia New Caledonia
NE Niger Niger
NF Norfolk Island Norfolk Island
NG Nigeria Nigeria
NI Nicaragua Nicaragua
NL Netherlands Netherlands
NO Norway Norway
NP Nepal Nepal
NR Nauru Nauru
NU Niue Niue
NZ New Zealand New Zealand
OM Oman Oman
PA Panama Panama
PE Peru Peru
PF French Polynesia French Polynesia
PG Papua New Guinea Papua New Guinea
PH Philippines Philippines
PK Pakistan Pakistan
PL Poland Poland
PN Pitcairn Pitcairn
PR Puerto Rico Puerto Rico
PT Portugal Portugal
PW Palau Palau
PY Paraguay Paraguay
QA Qatar Qatar
RE Reunion Reunion
RO Romania Romania
RU Russia Russia
RW Rwanda Rwanda
SA Saudi Arabia Saudi Arabia
SB Solomon Islands Solomon Islands
SC Seychelles Seychelles
SD Sudan Sudan
SE Sweden Sweden
SG Singapore Singapore
SH Saint Helena Saint Helena
SI Slovenia Slovenia
SK Slovak Republic Slovak Republic
SL Sierra Leone Sierra Leone
SM San Marino San Marino
SN Senegal Senegal
SO Somalia Somalia
SR Suriname Suriname
ST Sao Tome and Principe Sao Tome and Principe
SV El Salvador El Salvador
SZ Swaziland Swaziland
TC Turks and Caicos Islands Turks and Caicos Islands
TD Chad Chad
TG Togo Togo
TH Thailand Thailand
TJ Tajikistan Tajikistan
TK Tokelau Tokelau
TM Turkmenistan Turkmenistan
TN Tunisia Tunisia
TO Tonga Tonga
TR Turkey Turkey
TT Trinidad and Tobago Trinidad and Tobago
TV Tuvalu Tuvalu
TW Taiwan Taiwan
TZ Tanzania Tanzania
UA Ukrayina Ukrayina
UG Uganda Uganda
US United States United States
UY Uruguay Uruguay
UZ Uzbekistan Uzbekistan
VC Saint Vincent and the Grenadines Saint Vincent and the Grenadines
VE Venezuela Venezuela
VN Vietnam Vietnam
VU Vanuatu Vanuatu
WF Wallis and Futuna Wallis and Futuna
WS Samoa Samoa
YE Yemen Yemen
YT Mayotte Mayotte
ZA South Africa South Africa
ZM Zambia Zambia
ZW Zimbabwe Zimbabwe

Table LanguageCode_Enum

2 letter language codes according to ISO 639-1

Dependent tables:

  • TaxonCommonName

Content

Code Description DisplayText
af Afrikaans Afrikaans
ar Arabic Arabic
az Azerbaijani Azerbaijani
be Byelorussian Byelorussian
bg Bulgarian Bulgarian
ca Catalan Catalan
cs Czech Czech
da Danish Danish
de German German
el Greek Greek
en English English
es Spanish Spanish
et Estonian Estonian
eu Basque Basque
fa Persian Persian
fi Finnish Finnish
fo Faeroese Faeroese
fr French French
gl Galician Galician
gu Gujarati Gujarati
he Hebräisch Hebräisch
hi Hindi Hindi
hr Croatian Croatian
hu Hungarian Hungarian
hy Armenian Armenian
id Indonesisch Indonesisch
is Icelandic Icelandic
it Italian Italian
ja Japanese Japanese
ka Georgian Georgian
kk Kazakh Kazakh
kn Kannada Kannada
ko Korean Korean
ky Kirghiz Kirghiz
lt Lithuanian Lithuanian
lv Latvian Latvian
mk Macedonian Macedonian
mn Mongolian Mongolian
mr Marathi Marathi
ms Malay Malay
nl Dutch Dutch
no Norwegian Norwegian
pa Punjabi Punjabi
pl Polish Polish
pt Portuguese Portuguese
ro Romanian Romanian
ru Russian Russian
sa Sanskrit Sanskrit
sk Slovak Slovak
sl Slovenian Slovenian
sq Albanian Albanian
sv Swedish Swedish
sw Swahili Swahili
ta Tamil Tamil
te Tegulu Tegulu
th Thai Thai
tr Turkish Turkish
tt Tatar Tatar
uk Ukrainian Ukrainian
ur Urdu Urdu
uz Uzbek Uzbek
vi Vietnamese Vietnamese

Table TaxonNameCreationType_Enum

Types of the creation of a taxonomic name

Dependent tables:

  • TaxonName

Content

Code Description DisplayText
auto The name is an autonym, implicitly created through the creation of another taxon name – For example, if for “Poa alpina L.” a new subspecies “Poa alpina ssp. stefanovii Fiserova” is described, the autonym “Poa alpina L. ssp. alpina” is implicitly created as well. It is not published anywhere, and has no author on the subspecies (and neither author nor publication of Fiserova are given). auto
comb A new combination of a name into a different parent taxon that causes a name change. comb
combstat A new combination with a different name and change in rank of a taxon in a single nomenclatural action – For example, a subspecies in genus “Aus” is combined with genus “Bus” and the rank elevated to species at the same time. combstat
nom The name is a nomen novum (= replacement name, = avowed substitute). nom. nov.
sanct (Applicable only to Fungi:) The name is based on a prestarting-point name and sanctioned by the ICBN because is has been used in specific publications by Fries or Persoon. sanct
stat Change in rank of a taxon name, like a subspecies elevated to species rank, or a series to section. stat
tax Creation of a name at any rank, intended to represent a taxon that is new to science and based on an newly designated type. tax
validation The name is a validation of invalidly published names (sometimes expressed by “ex” in the author citation string). validation

Table TaxonNameListReferenceType_Enum

The types of the reference of the taxon list

Dependent tables:

  • TaxonNameListReference
  • TaxonNameReference

Table TaxonNameListSpecimenRole_Enum

Roles of collection specimen within a taxon list

Dependent tables:

  • TaxonNameListCollectionSpecimen

Table TaxonNameNomenclaturalCode_Enum

Codes of Nomenclature under which this taxa are created, e.g. Zoology

Dependent tables:

  • TaxonName

Content

Code Description DisplayText
1 Bacteriology Bacteriology
2 Botany (incl. Mycology) Botany (incl. Mycology)
3 Zoology Zoology
4 Biocode (for future use) Biocode (for future use)

Table TaxonNameNomenclaturalStatus_Enum

Nomenclatural stati for taxonomic names

Dependent tables:

  • TaxonName

Content

Code Description DisplayText
ad interim in the meantime ad interim
comb. combinatio = combination comb.
comb. ined. combinatio inedita = unpublished combination comb. ined.
comb. invalid. comb. invalid. comb. invalid.
comb. superfl. combinatio superflua = superfluous combination (if a combining author has missed on the pre-existence of the same combination, therefore creating an isonym) comb. superfl.
ined. indeditum = unpublished (name) ined.
nom. confus. nomen confusum = confused name nom. confus.
nom. cons. If a name of a family, genus, or species is accepted as a nomen conservandum the abbreviation “nom. cons.” should be added in a formal citation nom. cons.
nom. dub. nom. dub. nom. dub.
nom. excl. nom. excl. nom. excl.
nom. herb. nomen in herbario = name given on herbarium labels nom. herb.
nom. illeg. nomen illegitimum = illegitimate name (ICBN: 6.4, 52-54, App. VII) nom. illeg.
nom. inval. nom. invalid. nom. invalid.
nom. nov. nomen novum = new name, replacement name (ICBN: 45A.1, App. VII) nom. nov.
nom. nud. nom. nudum nom. nud.
nom. provis. nomen provisorium = provisional name nom. provis.
nom. rej. nomen rejiciendum = name, to be rejected (ICBN: 50E.2, 56, App.V, VII) nom. rej.
nom. superfl. nomen superfluum = superfluous name (ICBN: 52.1+3) nom. superfl.
pro syn. In the citation of a name that is not validly published because it was merely cited as a synonym, the words “as synonym” or “pro syn.” should be added pro syn.

Table TaxonNameResourceType_Enum

The type of an resource of a taxon, e.g. preview

Dependent tables:

  • TaxonNameResource

Content

Code Description DisplayText
audio E.g. audio file related to a taxon sound
drawing Original line or color drawing and painting of a taxon drawing, painting
image Still image of any raster or vector format without any further information regarding the content type, e. g. graphic designs, plans and maps, vector graphics 2D, 3D models image
information Any resource provided for the taxon, e.g. websites containing further information information
preview A small version of an image used as preview for an image preview
supporting files text-xml or text-WKT encoded files, assigned to multimedia objects supporting files
video E. g. video file related to a taxon video

Table TaxonNameRevisionLevel_Enum

States of revision for the taxa

Dependent tables:

  • TaxonName

Content

Code Description DisplayText
effectively published effectively published (ICBN Art. 29-31) effectively published (ICBN Art. 29-31)
final revision final revision final revision
review required review required review required
validly published validly published (ICBN Art. 32-45) validly published (ICBN Art. 32-45)

Table TaxonNameSynonymisationType_Enum

Types of the synonyms

Dependent tables:

  • TaxonSynonymy

Content

Code Description DisplayText
duplicate name is a duplicate of an other name, e.g. for imports of the same name from different sources duplicate
heterotypic heterotypic, the names have different basionyms heterotypic
homotypic homotypic, the names have the same basionym homotypic
isonym variant spelled exactly as another name but with deviating citation of the author(s), might be a name with wrong citation of the publishing or recombining author(s) or a even a isonym sensu ICBN isonym
orthographic variant variant spelled different as another name orthographic variant
unknown unknown if synonym is heterotypic or homotypic unknown

Table TaxonNameTaxonomicRank_Enum

Taxonomic ranks of the taxa

Dependent tables:

  • TaxonName

Content

Code Description DisplayText
agg. species aggregate species aggregate
aggr. species aggregate species aggregate
biovar. bio-variety bio-variety
cand. candidate candidate
cl. class class
convar. convar convar
cult. cultivar cultivar
cultivar. group cultivar-group cultivar-group
dom. domain (= empire) domain (= empire)
f. form form
f. sp. special form special form
fam. family family
gen. genus genus
graft-chimaera graft-chimaera graft-chimaera
grex infraspecific aggregate grex
infracl. infraclass infraclass
infrafam. infrafamily infrafamily
infragen. infragenus infragenus
infraord. infraorder infraorder
infraphyl./div. infraphylum (= infradivision) infraphylum (= infradivision)
infrareg. infrakingdom infrakingdom
infrasp. infraspecies infraspecies
infratrib. infratribe infratribe
ord. order order
pathovar. patho-variety patho-variety
phyl./div. phylum (= division) phylum (= division)
reg. kingdom kingdom
sect. section section
ser. series series
sp. species species
sp. group species group species group
subcl. subclass subclass
subfam. subfamily subfamily
subfm. subform subform
subgen. subgenus subgenus
subord. suborder suborder
subphyl./div. subphylum (= subdivision) subphylum (= subdivision)
subreg. subkingdom subkingdom
subsect. subsection subsection
subser. subseries subseries
subsp. subspecies subspecies
subsubfm. subsubform subsubform
subtrib. subtribe subtribe
subvar. sub-variety sub-variety
supercl. superclass superclass
superfam. superfamily superfamily
superord. superorder superorder
superphyl./div. superphylum (= superdivision) superphylum (= superdivision)
superreg. super kingdom super kingdom
supertrib. supertribe supertribe
tax. infragen. infrageneric tax. of undefined rank infrageneric tax. of undefined rank
tax. infrasp. infraspecific tax. of undefined rank infraspecific tax. of undefined rank
tax. supragen. suprageneric tax. of undefined rank suprageneric tax. of undefined rank
trib. tribe tribe
var. variety variety
May 3, 2024

Diversity TaxonNames

No-SQL Interface

JSON Cache

Databases of the modules provid a No-SQL interface where the data of the main table and the depending tables are merged as JSON.

Table JsonCache

Content of table JsonCache restricted to public available data

Column Data type Description Nullable Relation
ID int Unique ID for the Dataset, Primary key NO ID of the source
URI varchar (500) The URL as combination of BaseURL and ID NO BaseURL and ID of the source
DisplayText nvarchar (500) Representation in the interface NO Main table of the source
LogUpdatedWhen datetime Date and time when the data were last updated NO -
Data json Data related to the current dataset NO -

procFillJsonCache is started by an update trigger trgUpd… of the main table in the database

Interface in clients

All modules provide data via a cache table. In the header of the clients you can inspect the content of the JsonCache with a click on the button. For modules with a difference between local and public data, you can inspect the content of the public data with a click of the right mouse button.

Update

Apart of the update via the Trigger (see below) you can update the JsonCache via the update button underneath the button.

To update the JsonCache for the whole database select Administration - JsonCache… from the menu. a window as shown below will open where you can update the JsonCache for single datasets or the whole database.

Summary

graph TD;
    TaxonName[Main table in database] 
    trgUpdTaxonName[trgUpd.. of main table in database]
    TaxonName --> |Update in table| trgUpdTaxonName
    proc[Procedure procFillJsonCache setting the content in table JsonCache]
    trgUpdTaxonName --> proc
graph TD;    
    Mainform[Main form]
    ButtonShow[Button show JsonCache of current dataset]
    Mainform --> ButtonShow
    Left[Show Data]
    ButtonShow --> |Left click| Left
graph TD;    
    Mainform[Main form]
    Admin[Administration menu]
    Mainform --> Admin
    Cache[JsonCache...]
    Admin --> Cache
    Adminform[Administration form]
    Cache --> Adminform
    AdminUpdateSingle[Update single dataset]
    Adminform --> AdminUpdateSingle
    AdminUpdateDB[Update for whole database] 
    Adminform --> AdminUpdateDB

Example

The JsonCache of the current dataset will be shown as in the example below:

[
    {
        "Type": "Taxon",
        "ID": 4403792,
        "Attributes": {
            "FullName": "Arachnida Cuvier, 1812",
            "Rank": "cl.",
            "GenusOrSupragenericName": "Arachnida",
            "Authors": "Cuvier",
            "Publication": ". 1812",
            "Project": [
                {
                    "Project": "SNSBnames"
                }
            ],
            "Checklist": {
                "Analysis": [
                    {
                        "Checklist": "TaxRef_SNSB_NHC-Pests",
                        "Analysis": "IPM | Group",
                        "Value": "70"
                    },
                    {
                        "Checklist": "TaxRef_SNSB_NHC-Beneficials",
                        "Analysis": "IPM | Group",
                        "Value": "70"
                    },
                    {
                        "Checklist": "TaxRef_SNSB_NHC-Bycatchs",
                        "Analysis": "IPM | Group",
                        "Value": "70"
                    }
                ]
            },
            "Synonymy": [
                {
                    "ID": 4403792,
                    "FullName": "Arachnida Cuvier, 1812",
                    "Name": "Arachnida",
                    "Type": "accepted name"
                }
            ],
            "HierarchyListCache": [
                {
                    "HierarchyListCache": "Animalia | Arthropoda | Arachnida"
                }
            ],
            "Hierarchy": [
                {
                    "ID": 4403792,
                    "FullName": "Arachnida Cuvier, 1812",
                    "Name": "Arachnida",
                    "Rank": "cl."
                },
                {
                    "ID": 4403934,
                    "FullName": "Arthropoda Gravenhorst, 1843",
                    "Name": "Arthropoda",
                    "Rank": "phyl./div."
                },
                {
                    "ID": 4403805,
                    "FullName": "Animalia Linnaeus, 1758",
                    "Name": "Animalia",
                    "Rank": "reg."
                }
            ],
            "CommonNames": [
                {
                    "CommonName": "spider",
                    "LanguageCode": "en",
                    "CountryCode": "GB",
                    "Context": "IPM"
                },
                {
                    "CommonName": "Spinnentier",
                    "LanguageCode": "de",
                    "CountryCode": "DE",
                    "Context": "IPM"
                }
            ],
            "Resource": [
                {
                    "URI": "https://museumsschaedlinge.de/gaeste/",
                    "Title": "diverse animals that migrate or are introduced into buildings seasonally, generally don't casue any damage to objects",
                    "Type": "information"
                }
            ]
        }
    }
]
Aug 6, 2024

Diversity Taxon Names

Workbench

The Diversity Workbench is composed of components for building and managing biodiversity information, each of which focuses on a particular domain. Each component can provide services to the other components. DiversityTaxonNames can link data to the modules DiversityProjects, DiversityGazetteer, DiversityAgents, DiversityCollection and DiversityReferences as illustrated in the image below. DiversityTaxonNames itself is a source for other modules like DiversityCollection and DiversityDescriptions.

 

The modules communicate with each other to provide their services for the other modules.

Jul 19, 2024

Subsections of Workbench

Diversity Taxon Names

Modules

The Diversity Workbench is a set of components for building and managing biodiversity information, each of which focuses on a particular domain. To see the open connections to other modules, choose Connection - Module connections …. from the menu. Each component can provide services to the other components. The optional links to other modules within the Diversity Workbench are shown in the image below.

  • Links to DiversityGazetteer
  • Links to DiversityReferences
  • Links to DiversityProjects
  • Links to DiversityCollection

 

Apr 9, 2025

Diversity Taxon Names

Descriptions

If you are connected to a DiversityDescriptions database (see menu Connection - Module connections … ), and you select the option Scan module DiversityDescriptions the program will search in all available databases for descriptions linked to the current name. If you select an entry from the list the basic data as provided by the module DiversityDescriptions are shown. To see the details of the data you have to set the link to the software DiversityDescriptions.exe with a click on the  botton (see below).

After this link is set, you can click on the  botton to open the software with the details of the selected dataset (see below). For an introduction see a short tutorial.

Apr 9, 2025

Diversity Taxon Names

Specimen

If you are connected to a DiversityCollection database (see menu Connection → Module connections … ), and you select the option Scan module DiversityCollection the program will search in all available databases for specimen linked to the current name. With the option Restrict to type specimen you can restrict this search to type specimen. If you select an entry from the list the basic data as provided by the module DiversityCollection are shown. To see the details of the data you have to set the link to the software DiversityCollection.exe with a click on the  botton (see below).

All DiversityCollection databases listed in the connections will be scanned for links to the selected name (see above). To see the details select the entry in the tree (see below).

A click on the button will open the client of DiversityCollection with the respective dataset (see below. In case the installation path of DiversityCollection is not detected by default, you will be asked to enter it. If the option Restrict to type specimen is selected, only type specimen will be listed. For an introduction see  a short tutorial.

To forward changes in DiversityTaxonNames to databases containing data linked to data in e.g. DiversityCollection you must include the corresponding databases as described here. After changes in the data the
button will be marked with a pink background       indicating the option to update the linked data. Click on the
button to perform the update as described here Video starten.

Apr 9, 2025

Diversity Taxon Names

Settings

The settings for the software are stored in a directory created by the application, e.g. C:\Users\[LoginName]\AppData\Local\DiversityWorkbench\[DiversityWorkbenchModule].exe_Url_0he1anjeninqrrxpdywiwnwxaqvlezn3\4.4.13.0 where [LoginName] is the name of the user and [DiversityWorkbenchModule] the name of the Diversity Workbench module e.g. DiversityCollection. This directory contains the file user.config where all settings are stored in xml format. An example for the content in the module DiversityCollection is shown below:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <sectionGroup name="userSettings">
            <section name="DiversityWorkbench.WorkbenchSettings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
        </sectionGroup>
    </configSections>
    <userSettings>
        <DiversityWorkbench.WorkbenchSettings>
            <setting name="ModuleName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="GenerateTraceFile" serializeAs="String">
                <value>False</value>
            </setting>
            <setting name="DatabaseServer" serializeAs="String">
                <value>zsm.diversityworkbench.de</value>
            </setting>
            <setting name="IsTrustedConnection" serializeAs="String">
                <value>True</value>
            </setting>
            <setting name="DatabaseName" serializeAs="String">
                <value>DiversityCollection</value>
            </setting>
            <setting name="QueryMaxResults" serializeAs="String">
                <value>100</value>
            </setting>
            <setting name="DatabasePort" serializeAs="String">
                <value>5432</value>
            </setting>
            <setting name="DatabaseUser" serializeAs="String">
                <value>User</value>
            </setting>
            <setting name="ResourcesDirectory" serializeAs="String">
                <value>Home</value>
            </setting>
            <setting name="HowToCopyAppToUserDirectory" serializeAs="String">
                <value>Missing</value>
            </setting>
        </DiversityWorkbench.WorkbenchSettings>
        <DiversityCollection.Forms.FormCollectionSpecimenSettings>
            <setting name="SplitContainerData_SplitterDistance" serializeAs="String">
                <value>270</value>
            </setting>
            <setting name="QueryConditionVisibility" serializeAs="String">
                <value>10000100011000010000000000001000000001100000000000000000000000000001110000110110000000000000000000000000000000000000000000000000000000000000000000000000011100001000000000000000010000000000000000001000000000000000000000000001000000000000000000000000000000000000000000000000000000000000000</value>
            </setting>
            <setting name="ImageDisplay" serializeAs="String">
                <value>Hidden</value>
            </setting>
            <setting name="AskOnExit" serializeAs="String">
                <value>True</value>
            </setting>
        </DiversityCollection.Forms.FormCollectionSpecimenSettings>
    </userSettings>
</configuration>
Aug 9, 2024