Another version of the online program for collections

Community and Forum → Other questions. Insects topics → Another version of the online program for collections

Peter Khramov, 29.03.2014 15:08

From time to time, people ask about the possibility of creating an online program/catalog of collectible specimens not only for butterflies, but also for other groups of insects.
While people are testing the main part of the program on butterflies from this topic http://molbiol.ru/forums/index.php?showtopic=508344 I have a little time, and I want to discuss with you another option with a different approach.
The general meaning is the same: accounting for collectible items with the ability to transfer information about them to other users, as well as exchange and buy/sell them.
The first major difference is all Insecta, not just Lepidoptera (complication).
The second main difference is that the taxon database is needed for loading / selecting instances, and there is nothing else to do (simplification).

On a Lepidopter, the main element in the database is the view. Therefore, it is important to have the most appropriate taxon tree (without any duplicates, with an indication of the main valid names, etc.), to which this very species can be hung. Here, a piece of the tree will look like this (for simplicity, I'll reduce the number of intermediate taxa):
Nymphalidae
Aglais
Aglais io = Inachis io

On an Insect, the main element in the database is an instance. The taxon tree is used here not for hanging views, but for linking instances when loading and, most importantly, for selecting instances of the necessary taxa when viewing collections. Here the tree may be different, with extra branches:
Nymphalidae
Aglais
Aglais io
Inachis
Inachis io

In the first case, we say search: "find all instances of Inachis io". He grit: here are all instances of Aglais io, and Inachis io is a generic combination of Aglais io.
In the second case, we say search: "find all instances of Inachis io". He grit: here are all the instances of Inachis io plus all the instances of Aglais io, because they are the same thing.

In this case:
— The second version of the tree is easier to create, which, to put it mildly, is important when the number of species in the database is estimated at hundreds of thousands.
— In the second option, if the user loading the instance did not find the desired taxon, he can simply upload this taxon to the database himself, if necessary, linking synonyms to it (and the program will offer these synonyms to him, for example, based on the similarity of names and/or author/year, taxon level). In the first case, he would have to wait for the taxon to be entered into the database by moderators. In general, in the second version, the program adapts more to a specific curator of collections, and in the first-to the general "correct" view.

— In the first version, instances are immediately linked to species with descriptions on the site, photos, etc., i.e. you can get additional information about them, and also select them not only by the characteristics of instances and taxa, but also by the characteristics of species, and in the second case — no. But. For the second case, you can create automatic links to species descriptions on the same Lepidopter and other entosites plus, if you want to load information on other characteristics in separate groups — you can select them.

Oh, yes, one more thing. The Lepidopter has a Russian and English version. Accordingly, the program is bilingual. It will be possible to create a multilingual interface for Insecta, when there will be a version in both Spanish and Italian, etc. As it turns out, a lot of dudes will still search for and use such resources in their native language, and not in universal English.

Note: of course, if there was a single and non-repeatable tree for insects with all synonyms/combinations, then it would have to be charged. But, since there is no single classification that would suit everyone, we have to choose compromise options.

Note 2: it goes without saying that child projects for individual insect groups or locations are also easily linked to the Insect, but this is already an elective for those who want to do this, but do not have a software base. The framework is an interface for collectible instances.

Who can say what-are your thoughts adequate or not? Is it worth fixing up this option for all insects (the benefit is that programmatically it is very similar to the program for lepidoptera, which for the most part is already ready) or not?

This post was edited by Asar - 03/29/2014 15: 20