2. Overview
2
What are we covering?
1. Roadmap review
2. Common Database Platform
3. CMS Business Logic
4. Axiell UIs
5. Customer feedback
3. 3
Long term view - All products
EMu
Business
Rules
Mimsy
Business
Rules
CALM
Business
Rules
Adlib
Business
Rules
User’s Device
Hosted or
Client’s Server
Hosted or
Client’s Server
Texpress Oracle
DScrib
e
SQL
Server
EMU
UIs
Mimsy
UIs
CALM
UIs
Adlib /
Coll UIs
Common Database Platform
(SQL Server, Oracle, MongoDB,
Cassandra)
User Interfaces (Browser,
Tablet, Phone, Watch,
Windows, etc)
Common Database Platform
(SQL Server, Oracle, MongoDB,
Cassandra)
Business Rule Engine
User Interfaces (Browser,
Tablet, Phone, Watch, etc)
Published RESTful
API
Published RESTful
API
Published RESTful
API
TOMORROWTODAY “END STATE”
MicroM
Business
Rules
SQL
Server
MicroM
UIs
Published RESTful
API
4. Roadmap - Goal
Common Database Platform (CDP)
CMS business logic
Axiell Collections Web UI
AXIELL
MOVE
AXIELL
SAPPHIRE
● Modernise technology
● Improve offering
● Consolidate stack
○ Distributed core knowledge
○ Large pool of developers
○ Technical longevity
○ Cross-product functionality
○ Close to customer
● Continued product development
5. Common Database Platform
Common Database Platform (CDP)
CMS business logic
Axiell Collections Web UI
AXIELL
MOVE
AXIELL
SAPPHIRE
6. Common Database Platform
What? Why?
6
What is the CDP?
Why make this change?
● Modernise the backend technology across products
● Future-proof your systems
● First step in a move towards a single software stack
○ Increased developer capacity
○ Cross-product developments
● A new set of database technologies to replace each product’s
underlying database.
● Modern technologies
○ MongoDB, SQL Server, Oracle, Cassandra
○ ElasticSearch
● Highly standards compliant - not proprietary
7. Common database platform
How? When?
7
How will our system change?
When will we see this?
● Significant speed improvements, particularly queries
● New query functionality - geospatial, relationships in grids
● New RESTful API
○ REST level 3 compliant
○ Increased interoperability opportunities
● 24/7 uptime - no maintenance windows
● Options for horizontal scalability
● Release Q3 2018
● First CDP migration Q3 2018
● Additional migrations start Q4 2018
8. Common database platform
What are the benefits?
8
How will our customers benefit?
● Performance improvements
● Potential cost savings on infrastructure
● “Future-proof” systems
● Standards based
● Greater availability
9. CMS Business Logic
Common Database Platform (CDP)
CMS business logic
Axiell Collections Web UI
AXIELL
MOVE
AXIELL
SAPPHIRE
10. CMS Business Logic
What? Why?
10
What is the Business Logic Layer?
Why make this change?
● Various products have advantages, not all necessarily in the same
place
● Reduce duplication of development effort and redundant code
● Easier to support and develop
• Extract business rules from validation, background loads, client
logic, etc. into a single layer
• Communicates with CDP via RESTful API
• Accessible to client interfaces via RESTful API
11. CMS Business Logic
How? When?
11
How will our systems change?
When will we see this?
● Too early to tell
● Development commences 2019
12. CMS Business Logic
What are the benefits?
12
How will our customers benefit?
• Cross-product development – all customers take advantage of
new developments
• Quicker resolution of issues
• New products and upgrades quicker to market
13. Axiell UIs
Common Database Platform (CDP)
CMS business logic
Axiell Collections Web UI
AXIELL
MOVE
AXIELL
SAPPHIRE
14. Axiell User Interfaces
14
A fair bit to discuss
• EMu 6.0
• Adlib 7.5
• Mimsy 1.6
• Collections (Adlib)
• Collections (EMu & Mimsy)
• DAMS
• Move
• Flow
18. Axiell EMu 6.0
18
When?
• Q2 2018
Any additional details?
• Official announcement will be delivered via email with
some additional information
• Training – Optional EMu 6 Highlights class that can be
part of a House Call class
• Some customer upgrades may require more time than
others
20. Axiell Mimsy 1.6
20
When?
• New transaction panel integrated to provide easy access to
popular functions, including:
• Search History for faster retrieval of recent queries.
• Ability to “watch” Groups and efficiently monitor changes.
• New “pin” option to flag records for immediate display.
• Expanded Rights management to create a new Rights / Permits
Activity Module to better manage licensing of digital assets.
• Development of a new Research / Use Activity to support tracking
of how the collection is referenced and accessed by staff and the
public.
Major changes?
• Released Q4 2015, multiple patches since
21. Axiell Mimsy
21
What’s next?
• Mimsy XG 2.0 will be released Q4 2018
• Required for Collections web interface
• Adds UUIDs for records to allow additional linking between records
and systems
22. Axiell Adlib 7.5
22
When?
• Released Q1 2018
• Pseudonyms – New link type e.g Proper name of author related to
psueodnyms
• New Designer functionality
Major changes?
• New Word template format support
• Creating tasks for Axiell Collections
• Setting up connect entities
• Internal link type Pseudonym
• A format string for reverse relations
• Image format strings
• New grid view for Adlib folders
• New ValueCount ADAPL function
23. Axiell Adlib
23
What’s next?
• Development continues for Adlib, but no additional major releases
scheduled
• Development focused on Collections web interface
24. Axiell Collections (Adlib)
What? Why?
24
What is Axiell Collections for Adlib?
• Fully web-based collections management system
• Currently implements 85% of Adlib Windows client software (most
commonly used functions are implemented)
Why make this change?
• Demand for browser-based interfaces is increasing
• Works on Macs, PCs, and tablets
27. Axiell Collections (Adlib)
When?
27
When is this available?
• Available now for Adlib customers
• Future enhancements include roadmap for remaining 15% gap,
and workflow management tools
28. Axiell Collections (EMu & Mimsy)
What? Why?
28
What is Axiell Collections for EMu & Mimsy?
• Browser-based, responsive user interface for EMu and Mimsy
• Supplement existing CMS functions with new use cases, ie. not a
replacement
• Should be lightweight and extremely fast
• Accessible to allow use with little to no training
Why make this change?
• Demand for browser-based interfaces is increasing
• Expand use of CMS to other roles/departments/skills and training
levels
36. Axiell DAMS
asynchronous microservices
● High volume, offline, ingest
● Supports enterprise networks
● Implements predefined machine workflows
● Video, image, audio transcode
○ Dedicated / shared hardware
● Format conversion
○ At ingest
○ In future
● Supporting digital preservation policies
○ Bit-rot / fixity checks
■ Ensure integrity of assets long term
○ Storage abstraction
■ Future migration of storage
■ Leave storage management to experts (IT)
● High availability
● Resilient to faults
● Extremely high performance
37. Axiell DAMS
When?
37
When will the new services be available?
• Currently deployed at Imperial War Museum (Adlib customer)
• Available for any customer at Enterprise level now
• Evaluating means of rolling some services out to mid-tier
38. Axiell Move
What? Why?
39
What is Axiell Move?
• Scan barcodes with an iPad or iPhone
• Access collections data on location
• Document packing/unpacking of objects
• Update object locations data in real time
Why make this change?
● Demand for barcode system to update object location information
41. Axiell Flow
What? Why?
42
What is Axiell Flow?
• Process-driven experience (eg. I want to request an image, I need
to register donated items, etc.)
• Dashboard includes information relevant to each user (ie. What do
I need to do today?)
• Used in conjunction with existing CMS
Why make develop this product?
● Reduce staff training time
● Increase availability of system
● Make it easier to contribute information to CMS
47. Feedback/Q&A
48
CDP
• What information do you require so that you can properly prepare
for the transition? Eg. Hardware, APIs for integrations, software
licences, etc.
• How do you feel about a paid “priority access” model?
• What concerns do you have about this transition?
48. Feedback/Q&A
49
Trends/Product Development
• Is your IT outsourced? Do you plan to?
• Up-front purchase vs. subscription model?
• “Cloud” vs. on-premise?
• Privacy concerns?
• Browser vs. Windows client? Apps? Phones? Watches?
Hinweis der Redaktion
Ensure modernisation of products across ALM
An incremental development strategy that minimises disruption to customers
Long term aim is to consolidate technology across portfolio
Increase available development / implementation resource
Spread core technical knowledge worldwide
Develop new cross-product functionality
Ensure technical longevity of our products
React faster to customer requests
Continue to improve each product during this time, and after
Respond to market demand
Products take advantage of technology roadmap
Services communicate via message queues – Service can perform it’s job and dispatch a completed message, so services can run in isolation, fast services can move as fast as they need to without having to wait for slow services, also allows institutions to start a second copy of a service to work in tandem with the original (second piece of hardware/service to run a transcode service)
We can build and add additional microservices as required, customers only take what they want (additional example is a virus checker)