Collections Management Museums Bristol 2009 – EMu Development Process KE EMu Development Process Alex Fell Operations Manager KE Software UK

Collections Management Museums Bristol 2009 – EMu Development Process KE EMu Development Process Logical structure overview Development strategy  Generic developments  Client-specific development Costing model

Collections Management Museums Bristol 2009 – EMu Development Process EMu logical structure Customised Modules Standard Modules Multimedia & Notes Acc Lots, Loans, etc FinanceBase Catalogue Tasks Module Logic Locations, Biblio, etc. Audit Trails Admin Support Your Catalogue Sub-classed Acc Lots

Collections Management Museums Bristol 2009 – EMu Development Process Development strategy - generic Features added to core components are available to all clients Features added to standard modules are available to all clients who have not customised that feature

Collections Management Museums Bristol 2009 – EMu Development Process EMu logical structure Customised Modules Standard Modules Multimedia & Notes Acc Lots, Loans, etc FinanceBase Catalogue Tasks Module Logic Locations, Biblio, etc. Audit Trails Admin Support Your Catalogue Sub-classed Acc Lots Add task template support Support available here and below

Collections Management Museums Bristol 2009 – EMu Development Process Development strategy – client specific New layer created for affected module(s) for that client only Client-specific changes first cancel standard features that are to be replaced and then add new features New features not visible to any other clients

Collections Management Museums Bristol 2009 – EMu Development Process EMu logical structure Customised Modules Standard Modules Multimedia & Notes Acc Lots, Loans, etc FinanceBase Catalogue Tasks Module Logic Locations, Biblio, etc. Audit Trails Admin Support Your Catalogue Sub-classed Acc Lots Replace Authorisation fields

Collections Management Museums Bristol 2009 – EMu Development Process Client-specific enhancements Problem  Subsequent changes to the standard components which were removed by your customisation are not available to you Solution  As much as possible, client-specific customisations should be applied as generic customisation

Collections Management Museums Bristol 2009 – EMu Development Process Cost model KE funds its own enhancement program Clients fund client-specific enhancements If client-specific enhancements can be made generic (or partly generic), then other clients may have access to these enhancements under their support agreement If a client-specific enhancement can be made generic, generally KE greatly exceeds the original requirements

Collections Management Museums Bristol 2009 – EMu Development Process KE funded enhancement examples Image support – thumbnails, contact sheet, persistent image, image magick libraries, metadata Web interface – PHP object library, XML server Mapping Workflow management – tasks and task templates, auto-notify Reports – images in reports, use of Word and Excel Standards compliance – SPECTRUM, Dublin Core Audit module & audit trails Record Level Security

Collections Management Museums Bristol 2009 – EMu Development Process Client funded enhancement examples Narratives module Parts management Multimedia improvements – scanning, image overlays, multi- resolutions Relocate, revalue tools Archives support