Virtualizing
Entomology
Collection
Student:
Di Wang (Alan)
Sponsors:
John Marris: Curator, Entomology Research Museum
Stuart Charters: Department of Applied Computing
What is entomology
 is
the scientific study of insects.
 more than two-thirds of known organisms
are insects.
 many kinds of interactions with humans
and other forms of life on earth.
 Important for both biodiversity and
biosecurity.
Lincoln Entomology Research
Museum (ERM)
Curator: John Marris
Aim:
• Contribute to New Zealand
biodiversity study
• provide taxonomic expertise
and resources to Researchers
Current Holding:
Around 250,000 Specimens
Around 50 HoloType Specimen
Majority use of data
 Identify
specimen’s species
 Collection event and locality information
 Geographic Spread of Species.
 Description of species and references.
Data stored in spreadsheets or word document
Specimens stay in draws.
Solution
Build a system that can manage and
provide information about an Entomology
Type Collection via a web interface for
searching and web services to federate
information with other Biodiversity Services
Web Browsing
Input
Collection
Database
federate with other site
Approach
 Investigated





existing software
Identified Biota
Well used software in entomology
Built by researchers
Built using 4D
Recently Open sourced
 High
level architecture online database
with web service
implementation
 Use
Biota as front end for input
 Web services to publish externally
 MySQL as database for W/S.
 Sync MySQL with 4D database.
4D DB
MySQL DB
Dreams do not always come true!
Biota developed by a 4D ver6 old version, 10 years old.
Code not match on current 4D v12.
Massive errors on Biota’s source code need to fix
PHP/MySQL integration with 4D Database was done
by 3rd party add-ons not very stable.
Alternative Plan



Use Biota’s Database structure and its workflow .
Build the functions that are most useful and
needed in our web application.
federate information with other Biodiversity
Services
Web App
MySQL DB
Pro & Con of alternative Plan
Pro
Con
More flexibility
Have to rethink whole
workflow
Better integration between
More work on rebuild UI
user interface and database and logic tier
Less DB management as no
4D DB needed
Save time compare to fix all
the issue with biota
Outcomes and future task
Done
To Do
Customized database structure adapt
for current needs and Biota users
Import/Export to other
data formats
New UI and logic tier to manage
Input and output records
Allow system to
support other
collection disciplines,
e.g. herbaria.
Integrate with Biota’s data structure
Build in image function for future
imaging projects
Authentication system
Label print system
Complete federation
with GBIF
Benefits with Lincoln Web:







Publish information about LUERM Collection
Can easily access meta-data about specimen.
Related data is linked together
Improved data management system for museum
curator
Work can be distributed to multiple web users
with web access.
Speed up work process
Resource could contribute to global research
Questions?
Thanks for your time