1 / 15

BRAHMS 8

BRAHMS 8. Development Strategies. BRAHMS, developed over the last 20 years, embodies the collective knowledge and requirements of a wide range of botanical projects. Using this as a template and joining forces with key partner institutions.

zora
Télécharger la présentation

BRAHMS 8

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. BRAHMS 8 Development Strategies

  2. BRAHMS, developed over the last 20 years, embodies the collective knowledge and requirements of a wide range of botanical projects. Using this as a template and joining forces with key partner institutions our objective is to create a ‘next generation’ modular, flexible, powerful and sustainable data management system for the botanical sciences. Research Curation and management services

  3. An opportunity to review how BRAHMS operatesat all levels. DATABASE RDE FILES EXTRACT FILES Physical Database(s) BRAHMS 7- a working template Direct data entry

  4. Ensure that successful aspects of BRAHMS are carried forward • Rapid Data Entry (RDE) • Project specific data fields • The ability to add and execute command scripts • Allow editing in spreadsheet mode as well as via forms • Simple and compound query options including user defined • Flexible formatting, reporting and mapping tools • Fast response time for improved and new functionality • Can be deployed by users lacking IT support • Reasonable cost (or free) – licensing policy to be estabished • Diverse sources of funding – sustainable

  5. The development of ‘core modules’ could be drafted in 4-6 months. BRAHMS data modules Taxa Geodata People Herbaria Botanical Records Living collections Seed manager Images Plot-samples Literature DNA Visual materials Modular development will faciltate entire functional areas to be redeveloped separately, for example the seed and literature components.

  6. Current tools and functions are targets for separate development. Some examples: Mapping Image display and management Conservation assessments Import/export functions Lookups from internal and external files WebConnect for website development Configuration/preferences setup Data grid features (zoom, sum, sort, etc.) Numerous module specific ‘tools’ General editing functions Visual reports equivalent to current HTML (text) reporting Diversity analysis

  7. Example: spreadsheet functionality Ribbon commands are organized in logical groups, which are collected together under tabs.

  8. Language translatable Additional coordinate conversions (e.g. UTM) Improved map stype setting (colour/symbol/size) Automation of ArcGIS Addition of links to other GIS Example: mapping Updating BRAHMS mapping functions is a stand-alone task. Existing functionality can be copied and improved.

  9. Example: conservation assessment

  10. Example: seed manager

  11. Anatomy of a BRAHMS 8 Module MVVM = Model View – View Model. View Model is testable code with no dependence on the UI elements (buttons, lists etc.). XAML is an XML derivative language used to define the UI controls. Data is exchanged between a View Model and the UI elements using a declarative data binding scheme. The physical database can be changed (e.g. Postgres, MYSQL) with the respective DLI. User Interface(UI) MVVM Data Layer Implementation Service Layer (Business Layer) Implementation View Model XAML (Declarative) Interface Interface Physical Database(s) Dependency Injection (DI) Dependency Injection (DI)

  12. Flexible, modular development • Each module (and module component) can be developed and maintained independently of every other module/component. • The user interface, although initially developed using the Windows Presentation Foundation (WPF) framework as a ‘Desktop application’, could gradually be replaced or enhanced by any other implementation of a user interface e.g. in Html5/JavaScript. • The service layer could additionally implement Web Services making selected facilities available to mobile devices and third party applications through http calls.

  13. In this way, we can develop an extremely flexible and easily maintainable application, easy to edit and highly adaptable for any conceivable future task.

  14. Getting started with v8 …

More Related