Lisa McIntyre knows exactly what it was like to manage content before the digital evolution. She was a librarian.
“During the ‘early years’ of multimedia content, there was relative control over copies of items and a fairly clear distribution channel,” McIntyre, technical account manager at Nuxeo, said during last week’s CMSWire webinar, “Manage Complex Digital Assets at Massive Scale.”
“Replication of content, while not impossible, still took effort to do," she added. "Items were tangible, visible. You knew you had it because you saw it, held it. The time to creation allowed for research of available items and control was relatively centralized. We organized in physical folders and content was produced and delivered by well-defined roles.”
Essentially, she said, your digital asset management (DAM) system was a clipboard.
Changing Times
The digital asset world is changing. And growing. We’ll be managing $5.36 billion worth of digital assets by 2020.
That’s where a strong DAM system — and DAM processes by people — comes into play, according to McIntyre.
“Our digital experience is changing,” she said. “The digital world has truly transformed the way we behave both as general consumers as marketers/advertisers and especially within the enterprise. Our consumer experiences started overlapping into the enterprise.”
Online storage and connected applications and device must be managed globally available via a myriad of distribution channels. The growth of rich media and the way in which we used it outpaced the growth of work group DAM solutions, mostly because traditional systems were not designed for rapid change, she said.
“Trying to track usage can be difficult as models are shifting,” McIntyre said. “The digital transformation has presented companies with a new set of complexities when it comes to content and assets. Most importantly, we see that the need for DAM has moved out of the workgroup/marketing groups and expanded into the enterprise. Workgroup dams have a hard time adapting and weren’t built to deal with this.”
Nuxeo Use Cases
New York City-based Nuxeo thinks it has the answer. It provides a DAM system used by clients like Verizon. The communications and cable provider needs to manage images and content on a massive scale and complex contracts that surround what people have access to.
“Files can be upwards of 80 gigs for one single file,” McIntyre said. “That’s pretty difficult to manage, especially to keep in one place.”
Learning Opportunities
Webinar
Mar
29
The CX Commute vs. the CX Joy Ride
Is your CX traffic holding up your customer's journey?
Webinar
Mar
29
Is Your Microsoft 365 Data Recoverable? How to Survive the IT Hotseat When Data is Lost
See why MIcrosoft recommends third party backup
Webinar
Mar
30
An Optimized Customer Contact Strategy Combines Transparency and Intelligence: The State of Outbound Communications
Learn from the Neustar-commissioned Forrester Consulting study on challenges and solutions for contact centers
Webinar
Apr
5
Adopt a Modern Digital-First Marketing Strategy
Learn how to use a composable DXP to your advantage
Another traditionally print company that went to digital channels, JC Decaux, had to have new distribution models and new information to track. And another Nuxeo client, EA Sports, was worried about security leaking through online workflows.
“They needed to ensure that only the people that needed access to the information had access,” McIntyre said. “They also needed a way to track who accesses — and when they accessed — files.”
Inside Nuxeo DAM
The Nuxeo platform is designed to scale beyond a single box and can be setup with various configurations, McIntyre said.
It also includes:
- Ability to edit content models using schemas and facets and make workflows and other business logic apply
- Ability to make changes to a wide range of Nuxeo parts, including data models and other DAM based features like on-demand and automatic rendition creation
- Track rights to allow users to build out and support complex data models (and make them changeable) and put the information at the mercy of robust backend systems like Elasticsearch to make working with the metadata meaningful, whether through search or reporting
- APIs, extensible, as a business model
- Elasticsearch shards to index and query to content
- Database options either SQL-based (i.e. Postgres) or NoSQL (MongoDB)
“While it’s nice to dream of a world where everything will be done within your DAM application, it’s not very realistic,” McIntyre said. “It’s nice when your DAM not only accepts the idea of content elsewhere, but also embraces it.”
Learn how you can join our contributor community.
