Evolution of the catalogue of life architecture

Authors:
Andrew C. Jones;Richard J. White;Jonathan Giddy;Alex Hardisty;Hardik Raja
Affiliations:
Cardiff University, School of Computer Science & Informatics, Cardiff, UK;Cardiff University, School of Computer Science & Informatics, Cardiff, UK;Cardiff University, School of Computer Science & Informatics, Cardiff, UK;Cardiff University, School of Computer Science & Informatics, Cardiff, UK;Cardiff University, School of Computer Science & Informatics, Cardiff, UK
Venue:
KES'10 Proceedings of the 14th international conference on Knowledge-based and intelligent information and engineering systems: Part IV
Year:
2010

Citing 3
Cited 0

Experiences with a Hybrid Implementation of a Globally Distributed Federated Database System

WAIM '01 Proceedings of the Second International Conference on Advances in Web-Age Information Management
SPICE: A Flexible Architecture for Integrating Autonomous Databases to Comprise a Distributed Catalogue of Life

DEXA '00 Proceedings of the 11th International Conference on Database and Expert Systems Applications
Techniques for Effective Integration, Maintenance and Evolution of Species Databases

SSDBM '00 Proceedings of the 12th International Conference on Scientific and Statistical Database Management

Quantified Score

Hi-index	0.00

Visualization

Abstract

The Species 2000 and ITIS Catalogue of Life aims to create and deliver a catalogue of all known species, using a distributed set of data sources. The current Species 2000 software has developed over a number of years, and the system requirements have evolved substantially over the same period. In this paper we discuss the current Catalogue of Life software, the way the requirements are evolving, and major elements of a planned new architectural design being developed as part of the 4D4Life EU e-Infrastructure project. Of particular importance in the new design is to be able to maintain the catalogue, dealing with potential overlaps between supplier databases; to keep it up to date and manage revisions that arise out of changes of scientific opinion; to be able to map between different taxonomies within and outside the catalogue; to be able to provide a wider range of services to other electronic systems which need the catalogue as their "taxonomic backbone"; and to support third-party applications by means of an open platform architecture.