Difference between revisions of "DiversityDescriptions Quiz (Artenquiz)"

Revision as of 23:40, 14 March 2016

The ER diagram of DiversityDescriptions_Quiz (DD_Quiz) is a clone of DiversityDescriptions 3.00.10. July 17th, 2014 that is intended to work with the Web-Framework Django to have a quiz for species descriptions in German. This project is presently under development. Additional tables see below. For further information see under DiversityDescriptions Quiz implementations.

Suggested citation is that of DiversityDescriptions 3.00.10: G. Hagedorn, A. Plank, A. Link, G. Rambold & D. Triebel (2014). DiversityDescriptions information model (version 3.00.10). http://www.diversityworkbench.net/Portal/DescriptionsModel_v3.00.10.

Hover the mouse over a table to jump to the documentation (linked to DiversityDescriptions 3.00.10. July 17th, 2014).

Documentation

Database

Scheme of DiversityDescriptions Quiz:

Graph image creation requires permission to upload.

The following conventions and abbreviations have been used in the tables: Columns of primary key:underlined. Categorical data are presented to a user in the quiz therefore some tables (in gray) are not used for the quiz.

Graph image creation requires permission to upload.

Table: Contribution

Multiple contributors may contribute in different roles

Table: Contributor

People contibuting to a work. Roles are recorded in Contribution

Note: in the Quiz all users/contributors are requested to input their full name.

Table: ResourceWatchedTime

The time a resource thumb was watched (=mouse hover)

Table: TaxonQuiz

User’s correctly answered taxa.

unique together = ('project_id', 'contributor_id', 'taxon_id', 'scope_id')

New projects

Schematic important relations for a project:

Project
├ code (used for URL)
├ label (directly used for user display and in text context)
├ TaxonSet (i.e. taxa, media-resources etc.)
├ DescritorTree (i.e. characters and its states, media-resources etc.)
├ …
… 

Steps to enter data for a new project:

1. Create a project (table: Project)
   • Project.code is important: it is used as URL part and within the Django application as internal project identifier it should never be changed
   • eventually create or associate scopes, like “female”, “male” (table: OtherScope, Project_AvailableScope)
2. Eventually create the taxa (table: TaxonProxy)
   • associate taxa to the project (tables: TaxonSet, TaxonSet_Taxon)
   • associate images of taxa (tables: Resource, ResourceVariant, BaseEntity.specific_rights_text should contain the corresponding picture’s author name like: “© Author Name”). A set of maximum of 16 thumbs will be displayed
     1. an image is associated correctly, when 1 taxon has 1 Resource, but 2 (or multiple) ResourceVariant(!!)
     2. resource variants as ReourceVariant_Enum.code "tiny_sample" (=thumb 75×75px) and "best_quality" (max 500×500px displayed) should have corresponding urls in ResourceVariant.url:
Resource
├ ResourceVariant
│ (e.g. with ResourceVariant_Enum.code='best_quality')
└ ResourceVariant
  (e.g. with ResourceVariant_Enum.code='tiny_sample')
   • eventually associate geographic area (table: GeographicAreaProxy, GeographicArea_Taxon)
3. Create character and character states (table Descriptor, CategoricalState), character tree (tables: DescriptorTree, DescriptorTreeNode)
   • associate images to characters or character states (tables: Resource, ResourceVariant, BaseEntity.specific_rights_text should contain the corresponding picture’s author name like: “© Author Name”), size of images with maximal height 40px (height should precced)
4. Finally make the project publicly available: set the Project‘s tag (table: Tag)
   • tag "Artenquiz" means it is a quiz
   • tag "Public" means it will be publicly accessible
   • tag "Identification" make the project available for identification (URL: …/mobile_bestimmung/, TODO: not yet implemented)