DiversityResources information model (version 1.3)
|Authors||Gregor Hagedorn & Andreas Kohlbecker 2006|
|Suggested citation||Hagedorn, G.& Kohlbecker, A. (2006). DiversityResources information model (version 1.3). http://www.diversityworkbench.net/Portal/wiki/ResourcesModel v1.3.|
|Notes||The models currently reside in MS SQL Server, so knowledge of some SQL Server ER-diagram conventions will be helpful.|
This document contains entity-relationship diagrams and a complete list of all entities and relations used in the information model of this DiversityWorkbench component. It is primarily intended as a technical reference. It can also be helpful, however, in understanding the scope and usage of certain attributes. When you have a question like ‘where does this information fit in’, reading the attribute description under the section ‘Entities’ may help you.
The following diagrams show all entities except those entities that are part of the general ‘Workbench’ interface and documentation infrastructure. The size of the diagrams has been reduced to 75%; full-size version have been linked below each image.
Overview over all entities and relations used in DatabaseModel
Abstract items are organized in ResourceCollections. Each item must be a member of exactly one collection (no multiple membership possible). The abstract (or “conceptual”) item refer to the content of a resource, not to its format (for images, e.g., jpg, png) or quality level (for images, e.g., high or low resolution).
Resource metadata are organized using two flexible systems:
- unconstrained, long text like title, caption, description, etc. is handled through ResourceMetadataText (with ...TextElement enumerating the possible elements or “fields”). For each language, a metadata text element may be added only a single time to each resource.
- keyword-like information is handled through ResourceDescriptor (with ResourceDescriptorElement enumerating the possible elements or “fields”). Typical descriptor elements are “keyword”, “taxon name”, “host taxon name”. These elements may be added multiple times to each resource.
Event logging entities
Information on who created, updated or deleted a record, and when this occurred is recorded automatically (through database triggers) in the following logging (or “history”) entities. Except for AbstractItemLog, all tables are linked to the Collection. Consequently, the deletion of a manager, provider, quality class remains available as long as the collection itself is not deleted.
We are interested in your opinion. If you see any problems with the model that you would like to bring to our attention, please contact us.