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