well a simple way would be to let data entry be open. the more people entering the info, the faster the database fills.
the logic im getting behind it though would be the need to:
1) clearly define the dataset.
2) Develope a compatibility key
3) develope an incompatiblity key
4) develope database (this could be a simple shell database to start with, say 50 or 60 fish in it as a test base)
5) stop using my new mobile as my computer mouse
6) set searches:
6.1) simple searches - seach my species etc
6.2) complicated search - multiple search catagories e.g. species and agressiveness.
6.3) the difficult recursive cross-referencing search: it would need to first recursively search all trees for matching:
6.3.1) agressiveness
6.3.2) matching compatibility keys (notice plural, may match more than one)
6.3.2) no primary keys from search so far matching incompatibility key. remove those that match
6.3.3) species match/living requirements sub scan to remove those requiring specialist care/settings eg high ph etc.
6.3.4) do the same scan on every result against the other results to ensure that the results wont clash with each other.
Im more worried about a simple hosting server getting hit at the same time by multiple people - dont think id host this myself, think id maybe get it professionally hosted...
[edit] hey, im in the middle of building a nice wooden lid for my corner tank, not doing this for you guys!! may hold this one off, maybe better for a winter project when im more inclined to stay indoors. then again, i may go an make a formal plan when im bored in work tomorrow...[/edit]
the logic im getting behind it though would be the need to:
1) clearly define the dataset.
2) Develope a compatibility key
3) develope an incompatiblity key
4) develope database (this could be a simple shell database to start with, say 50 or 60 fish in it as a test base)
5) stop using my new mobile as my computer mouse
6) set searches:
6.1) simple searches - seach my species etc
6.2) complicated search - multiple search catagories e.g. species and agressiveness.
6.3) the difficult recursive cross-referencing search: it would need to first recursively search all trees for matching:
6.3.1) agressiveness
6.3.2) matching compatibility keys (notice plural, may match more than one)
6.3.2) no primary keys from search so far matching incompatibility key. remove those that match
6.3.3) species match/living requirements sub scan to remove those requiring specialist care/settings eg high ph etc.
6.3.4) do the same scan on every result against the other results to ensure that the results wont clash with each other.
Im more worried about a simple hosting server getting hit at the same time by multiple people - dont think id host this myself, think id maybe get it professionally hosted...
[edit] hey, im in the middle of building a nice wooden lid for my corner tank, not doing this for you guys!! may hold this one off, maybe better for a winter project when im more inclined to stay indoors. then again, i may go an make a formal plan when im bored in work tomorrow...[/edit]