1 / 16

Developments in floristic data bases at RBGE

Learn about the developments in floristic databases at RBGE, challenges with current systems, aims of a new system, design principles, key features, and the importance of separating core data from flora-specific data.

melissathompson
Download Presentation

Developments in floristic data bases at RBGE

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Developments in floristic data bases at RBGE

  2. Brief History • RBGE active in floristic data base development for the last 14 years • PANDORA • PADME • Prometheus

  3. Problems with PANDORA • Not SQL compliant • Not directly accessible through the internet • No possibility of remote data entry • All data sets separate – large amount of repetition • DOS based – outdated and difficult to maintain

  4. Aims of a new system • Must provide at least the same functionality as PANDORA • Should provide as far as possible an integrated system for RBGE floristic data • Should allow multiple types of access to the data including standard Windows desktop access and access via the web • Should directly support the day to day working practices of floristic taxonomists

  5. Aims of a new system Data base Raw data Data output Data output Raw data Data base

  6. Aims of a new system Data base Raw data Data output Data output Data output Raw data Data base Data output Data output

  7. Design principles and methods • “Use case” driven design • Users inform developers of the behaviours they expect from the system • Developers use the information gained to design appropriate interfaces and underlying data structures • A highly process oriented approach – very different from data centric application design

  8. A multi-tier design Data base Business logic Interfaces

  9. Key features • Flora management module • Separation of core data from flora specific data • Annotation based information storage

  10. Flora management module • Control access to different parts of the flora data depending upon user rights • Controls scheduling and allocation of responsibilities for account editors and account writers

  11. Separation of core data from Flora specific data Core Data Flora specific data

  12. Separation of core data from Flora specific data Core data Flora specific data • Taxon name • Rank • Epithet • Basionym • Authority • Place of publication • Validity • Legitimacy • Taxon • Rank • Taxonomic status • Higher taxon • Name

  13. Separation of core data from Flora specific data Flora specific data Core data

  14. Separation of core data from Flora specific data Flora specific data Core data

  15. Annotation based information recording Taxon Annotation definition Annotation Text for the annotation (XML)

More Related