EMu roadmap Axiell User Conference, Denver, 2019 Ale x Fe ll - Head of R&D, EMu Product Manager EMu 6 .0 EMu 6 .0 - Released and available • 48 customers currently upgraded • 0.5 < n > 5.75 days per customer • Reactions mainly positive • Upgrades mainly undertaken by helpdesk • Minor UI glitches being resolved by dev team EMu - Forthcoming enhancements • Deep links • Link directly to records within same institution • Clicking a link opens EMu at appropriate record • Questions to be resolved around links between installations • UI scaling improvements • Provide a better response when changing DPI or font size • Fa irly s ig nific a nt d e ve lo p m e nt • May be released over time EMu - Forthcoming enhancements • Client timeout facility • Handle user inactivity more gracefully • Optional timeout set in Registry • Brings EMu in line with NIST standards Axie ll Co lle c t io ns Eng ine (formally the CDP) Axie ll Colle c t ions Eng ine • Development is feature complete • Significant internal effort with a world -wide team • Work continues on efficiency and improvements • Multi -lingual data final feature to add • Scalable to many records, horizontally • Vertical scaling - buy a bigger server • Horizontal scaling - buy another server • Question of when to scale (number of nodes / size of node) Axie ll Colle c t ions Eng ine • Data storage and indexing are separated (CQRS) • Elasticsearch provides indexing • MongoDB (currently) provides storage • System is modular and technologies can be changed • Offers a wide variety of scaling combinations • CDP, retrieval and storage may each be scaled differently • Integrates with a variety of authentication methods • OAuth2 (OpenID), PAM, LDAP Axie ll Colle c t ions Eng ine • All functionality exposed through REST level 3 API • Level 0 – HTTP based transport layer • Level 1 – Resources (nouns) • Level 2 – HTTP Verbs (GET, POST, PUT, PATCH, DELETE) • Level 3 – Hypermedia Controls (links and actions) • API is used for all internal communication except events • By definition feature complete • Standards followed by preference wherever possible • JSON (RFC 7493), Currency (ISO 4217), Date (ISO 8601), Latitude/Longitude (ISO 6709), String (RFC 3629 – UTF-8), Time (ISO 8601), Timestamp (ISO 8601), UUID (ISO 11578:1996), HTTP (RFC 2616) Axie ll Colle c t ions Eng ine • R&D projects have started using ACE already • Axiell Go, Axiell DAMS • EMu system migration is ongoing • NHM London is test bed (~20m records, > 80m audit) • Outcome will inform upgrade strategy • Large amount of validation code to migrate and test • Data migration mainly automated (no schema changes) • Other products will need different approaches Axie ll Go Axie ll Go • Fully web -based interface to CMS • Available to EMu users • No initial licence charge for existing customers • Focused on working away from desk • Fully responsive, mobile -first interface • Capture images • Record movement / check current location • Condition checks • New functionality to be added on future upgrades.