Development of mobile key application
This topic is about the development of a mobile key application, which should be compatible with the SDD standard. This page discusses features and the development of the mobile key. The topic Mobile Key Service Strategy discusses how to integrate the key with other components and how to provide automated services for setting up mobile keys.
Contents |
1 The functions of the mobile application
Our mobile application will have the following functions:
- Adjust page for current mobile phone.
- Change language
- Identification keys
- Search function
- Filter for Location
- Filter for Date
1.1 Adjust page for current mobile
Because this is an mobile application, we need to make sure it looks as good as possible on all mobile phones, smart phones and pda's. We have limited ourself to mobile devices:
- With a pixel resolution of 320x240 or greater.
- That support javascript and stylesheets.
To adjust the pages for the mobile device we checks the browser and select the right template.
1.2 Change language
We give the users the possibility to change the language. This is optional, if the user doesn't choose a language the default language is selected.
1.3 Identification keys
This is the most important part of the application. If there are more than one key (for example a key with different difficult levels), the user can choose on of the keys. The keys should allow you to get to the right specie.
1.4 Search function
There will be a search function to search for a specie, a family, a class, etc. When more than one specie is found (if there was a search for family for example). The user should be able to put the remaining species in the identification key.
1.5 Filter for Location
There will be a map where you can click on your location. Only the species that life in that region will be shown. The user should be able to put the remaining species in the identification key.
1.6 Filter for Date
There will be a dropdown menu with the months. When a month is choosen only the species that are active at that moment will be shown. Some birds for example fly to the south in winter time. The user should be able to put the remaining species in the identification key.
2 Identification key and SDD
The identification key should be compatible with the SDD standard.
As said before, the mobile application can handle more than one key. At the moment we have two types of identification keys we would like to use.
- A traditional yes or no key.
- A key with the possibility to skip questions.
2.1 Traditional key
For the traditional yes or no key we use a parent child relation in the same table.
| Id (auto_inc) | ParentId | ChildId | QuestionId | AnswerId |
|---|---|---|---|---|
| 1 | 1 | 2 | 1 ("Does the specie has wings?") | 1 ("yes") |
| 2 | 1 | 3 | 1 ("Does the specie has wings?") | 2 ("no") |
| 3 | 2 | 4 | 2 ("Are the wings taller than 10cm?") | 1 ("yes") |
| 4 | 2 | 5 | 2 ("Are the wings taller than 10cm?") | 2 ("no") |
| 5 | 3 | 6 | 3 ("Another question?") | 1 ("yes") |
I can't seem to find any table relating to this kind of key.
2.2 Other key
But the key with the possibility to skip questions can't use this technique.
For that we use a characters table, a states table and a table to connect the right characters with the states and species.
2.2.1 Characters
| Id (auto_inc) | CharText |
|---|---|
| 1 | "Does the creature have wings?" |
| 2 | "What kind of shape is the eye?" |
| 3 | "How many legs does the specie have?" |
2.2.2 States
| Id (auto_inc) | StateText |
|---|---|
| 1 | "yes" |
| 2 | "no" |
| 3 | "round" |
| 4 | "vertical" |
| 5 | "horizontal" |
| 6 | 2 |
| 7 | 4 |
| 8 | "More than 4" |
2.2.3 CharactersStatesSpecies
| Id (auto_inc) | SpecieId | CharId | StateId |
|---|---|---|---|
| 1 | 1 | 1 | 1 |
| 2 | 2 | 1 | 2 |
| 3 | 3 | 1 | 1 |
| 4 | 1 | 2 | 4 |
| 5 | 2 | 2 | 5 |
| 6 | 3 | 2 | 3 |
| 7 | 1 | 3 | 6 |
| 8 | 2 | 3 | 8 |
| 9 | 3 | 3 | 7 |
I can find the tables that contains the Characters and states (CategoricalCharacter and StateDefinition), these two tables are connected on another table (CategoricalCharacter_StateDefinition). The problem here is that I can't find a specieId in any of these tables.
3 Description page
The description page will show:
- The scientific and common name
- Multimedia
- Descriptions
The scientific and common name shouldn't be to much of a problem. Since we should know the Id of the specie when we are at the Description page. But then again I can't find the SpecieId for the multimedia and descriptions. I assume I miss some logic somewhere. If anyone with good knowledge of the SDD standard knows the solution for this problem, please let me know. dennis 03-Jun-2008 16:13 CEST
- The media items have no link to species, but the SDD.TaxonNames and SDD.Description has links to Multimedia.
- The explicit taxon link of a description is part of the SDD.Scope element. This may appear strange, but makes sense when thinking of using the same standard for describing unidentified objects (where the taxon name is yet unknown). --GregorHagedorn 16:01, 6 November 2008 (CET)
