1 / 9

EMu enhancements and developments

EMu enhancements and developments. Darrell J. Siebert NHM Collections Database Manager. EMu. Object oriented data model Convenient for collections management purposes Some relational functionality Can link between some modules in many-to-1 relationship Client-Server architecture

rylee-rice
Download Presentation

EMu enhancements and developments

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. EMu enhancements and developments Darrell J. Siebert NHM Collections Database Manager

  2. EMu • Object oriented data model • Convenient for collections management purposes • Some relational functionality • Can link between some modules in many-to-1 relationship • Client-Server architecture • EMu user community-wide aspects server side • NHM bespoke aspects client side • Indexing methods to support data model • ‘joins’ not supported

  3. EMu enhancements and developments to support digitisation programme • Export of data for NHM data portal (Informatics Initiative) • Server side image loading • Batch Operations • IMu • Barcodes

  4. Data export for data portal • EMu data model and indexing methods not suitable for our needs for fast web display • ‘Table dump’ -- core product functionality • Initial dump of data from relevant tables • Only records with appropriate security setting are exported! • Automatic weekly change list • Informatics Initiative team structures and indexes data to suit needs of data portal

  5. Server side image loading • Images typically processed client side (on desktop PC) • Can be ‘slow’: > 10 min for 220MB Mellon Project botanical image • 100,000 Mellon images: 1.9 years to load • Bulk server side image loading (images processed by server) • 220MB Mellon Project image processed in 1 min • 100,000 Mellon images: 69 days to load • Effectively 24/7 background process • Currently using 1 core; can increase this but need to understand impact on server performance

  6. EMu Batch Operations module: dataset cleanup • Collections digitisation programme: high quality, end-to-end outcomes • Collections information in digital form associated with appropriate image(s) • High quality collections information – our biggest challenge • Duplicates • Identical records • Near identical records for same information • EMu Batch Operations module • Standard, client side ‘Merge’ operation addresses duplicate records • Bulk ‘Merge’ operations moved to server side • Frees client for other uses • Effectively 24/7 background process

  7. IMu API • IMu – api delivered as standard with EMu • Standard functionality: query; insert; update; and delete • IMu is ‘EMu data model aware’ • IMu is ‘EMu security model aware’ • Informatics Initiative team exploring delivering data to a scratch pad for the SCORE project using IMu api • With appropriate developer expertise IMU can enable development of mobile (tablet) applications

  8. Barcodes • Labels too small to fit much information on • Palaeo labels 42x42mm • Slide labels 25x25mm (or smaller) • Barcode • Machine readable object • Encodes registration number • Can be linear or 2D -- these are 2D - 5x5mm • Can be ‘read’ with mobile phone • Link to richer information • Wireless infrastructure • Mobile devices and applications

  9. Questions

More Related