Problems Of Data Retrieval From Entomological Databases <B>Problems Of Data Retrieval From Entomological Databases</B><P> </B><EM><B></B></EM><B>Eckhard K. Groll and Andreas Taeger </B><BR> Deutsches Entomologisches Institut, Schicklerstasse 5, D-16225 Eberswalde, Germany<B></B><P> One of the most important tasks for the DEI at present and in future is the recording of entomological data. This includes entomological literature, names of taxa, description data and assignment to the systematics, names and biographic data of entomologists, faunistics, biological and other notes.<BR> In this presentation, we discuss one problem associated with the use of computerised databases for this task: how to hold all data in a condition that allows retrieving all the information stored in the databases. In our opinion the main problems in retrieving results arise from:<P> SEQ ParaNumbers1_0 \* Arabic \r 11.different spellings (names) for the same objects (synonyms)<BR> SEQ ParaNumbers1_0 \* Arabic \n2.change of the sense of names<BR> SEQ ParaNumbers1_0 \* Arabic \n3.same name for different objects (homonyms)<P> Modelling of the data structure and normalizing the data, necessary for designing and programming databases, do not reduce these problems. On the contrary, many additional data are necessary to make possible a complete retrieval of data.<P> SEQ ParaNumbers1_0 \* Arabic \r 11.Different spellings (names) for the same objects (synonyms)<BR> Example: Names of entomologists extracted from labels, literature and other databases<BR> Lepeletier, St. Farg., Le Peletier, Le Peletier de Saint Fargeau, Lep., Le Pelletier, Saint Fargeau, and so on.<P> Lepeletier (convention) himself used several spellings. All the spellings mentioned above are to be considered to be valid, from the point of view of taxonomists - objective synonyms. Furthermore, misspellings are possible and to be found. Similar problems result from the use of vernacular spellings. The solution is an additional information (a code) to fix the connection of all the spellings. The same code is used for all variations.<P> SEQ ParaNumbers1_0 \* Arabic \n2.Change of the sense of names<B></B><BR> Objects sometimes may change. Unfortunately their names often do not reflect the alterations of the sense. Consequently, the usage of the names become ambiguous. That means, databases should be able to store the sense in addition to a name.<P> Solution: Geographical names in their historical context<P> Name <BR> Explanation of the object <BR> Code <P> Deutschland <BR> until 1945 <BR> e5z <P> Deutschland <BR> 1945-1949 <BR> q3wr <P> Deutschland <BR> 1949-1990 Bundesrepublik Deutschland (Western Germany) <BR> p9c5 <P> Deutschland <BR> since 1990 Bundesrepublik Deutschland (Western and Eastern Germany) <BR> q3wr <P> SEQ ParaNumbers1_0 \* Arabic \n3.Same name for different objects (homonyms)<B></B><P> Example: The same name for more then one object<P> Name <BR> Explanation of the name <BR> Code <P> Brandenburg <BR> town <BR> ap3 <P> Brandenburg <BR> district <BR> 9h8 <P> The examples show some of the difficulties, which are to be found between feeding data into and retrieving them from a database. We propose to solve these problems by the following steps:<P> SEQ Outline_0 \* ROMAN \r 2II.semantic bridges should be created;<BR> SEQ Outline_0 \* ROMAN \nIII.these bridges should be created and maintained by specialists;<BR> SEQ Outline_0 \* ROMAN \nIV.these bridges should be available for other users in a network, perhaps the Internet.<P>