1. NemasLan, MysidLan, Taxonlan: a story of database development T. Deprez, J. Wittoeck, G. De Smet and M. Vincx

2. Zoology department, University Ghent Expertise in Nematoda: Huge collection of reprints Introduction 1998: How to preserve collection for the future? How to make this collection more valuable also for non – taxonomists ? How to make the collection accessible worldwide ? ANSWER: STORE THE INFORMATION IN A DATABASE = systematical info = literature info = morphology info = ecology info = biogeography info ??? Biolgist ≠ Informatician

3. NemasLan (1) ??? Biolgist ≠ Informatician Private software developer was contacted Needs: Input of taxonomical data must be possible in an easy way Availability of morphological, ecological and distribution info at specis level Connection to data source must be available Data access and input in a network environment (LAN) must be possible NemasLan was Born !!!!

4. NemasLan (2) Evaluation:+ data input could be started + project came alive - A lot of money involved - A lot of time in negociations  - connection with software developer still needed Informatician ≠ Biolgist

5. NemasLan  Mysidlan 1999:Thesis project: Taxonomy and Biogeography of the Mysida of the Western Indian Ocean Database similar to NemasLan was needed Software developer: Creation of Mysidlan Addition of new features: Quick Search module Functional Search module Export to Spreadsheets Program Code NemasLan ≠ Program Code Mysidlan

6. Mysidlan Evaluation:+ valuable dataset was created + evolution in dataset concept - A lot of money involved - no independance of software developer - two program codes (NemasLan – Mysidlan) => double cost of maintenance

7. Towards TaxonLan Program Code NemasLan ≠ Program Code Mysidlan If interest in new dataset  3 codes  3 Costs Need for 1 generic database program: TaxonLan Specifications for each dataset defined in metadata Multiple backend (mdb, SQL)

8. Taxonlan Evaluation:+ Can handle different datasets + Works with multiple types of backends + Has all functionalities of MysidLan – NemasLan + Creation of new datasets is possible - Definition of new dataset in metadata: very complex - Code still remains property of software developer => still not independant - problems with installation of the software cfr. New operating systems... cfr. Keeping costs as low as possible Datasets running:- Mysida - Nematoda - Copepoda BCP - Turbellaria BCP TaxonLan = good concept aching of lots of child diseases

9. The future... TaxonLan = good concept aching of lots of child diseases Curing diseases will cost a lot of money => New steps were taken: Interest of software developper is disappearing expertise in databases is rising new evolutions in technology contacts with institutions in belgium working on and with biological databases Databases were converted to a more standardised format

10. The future... Databases were converted to a more standardised format + independance of software developer + one program code created in-house => maintainance easy + cheap + exchange of data with other organisations easier + publishing the data through a web-browser (intranet) => userfriendly + operating system independant

11. Current database structure Taxonomic Units ITIS, VLIZ Reference library Taxonlan Geographical gazetteer Morphology Characteristics –States Measurements Ecology Records 1-∞ Pictures SQL-SERVER WEB Frontend Lan-Wan MSACCESS Frontend Lan

12. Conclusions Setting up biological databases: Setting up biological databases: Theory ≠ reality Theory ≠ reality Use of software developer: usefull but expensive Use of software developer: usefull but expensive New technologies can be a help for giving a new value to ‘old’ science New technologies can be a help for giving a new value to ‘old’ science