Another DAM Podcast

Audio about Digital Asset Management

Tag Archives: interoperability


by Leave a comment

Another DAM Podcast interview with Ralph Windsor about Digital Asset Management

Listen to Another DAM Podcast interview with Ralph Windsor on Digital Asset Management

 

(Duration – 13:17)

 

Here are the questions asked:

How are you involved with Digital Asset Management?

What are Digital Asset Management Open Specifications?

What are the biggest challenges and successes you’ve seen with Digital Asset Management?

What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?

Transcript:

Henrik de Gyor:             00:00                This is Another DAM Podcast about Digital Asset Management. I’m Henrik de Gyor. Today I’m speaking with Ralph Windsor. Ralph, how are you?

Ralph Windsor:             00:08                Hi Henrik. How are you?

Henrik de Gyor:             00:11                Good. Ralph, how are you involved with Digital Asset Management?

Ralph Windsor:             00:15                Yeah, that’s a good question. I’ve been doing DAM for about 25 years now. if you can believe, originally when I first started in this, I was a freelance multimedia software developer. This is sort of back in the days of multimedia CD-ROMs in the mid-nineties. I had a client around that time there was a photo library and they wanted a searchable catalog of all their images with a lightbox where you can select favorites and so on. And I built that for them. And then I had a few other similar sort of clients, so smaller, medium-size stock media libraries. They wanted the same kind of thing. That progressed later. We had design agencies and some enterprise clients. We wanted what used to be called corporate style guidelines, which is where basically that like a logo, print artwork, a key photos, people put all that onto a CD-ROM and instead it’s sort of like early forerunners of the kind of enterprise DAMs that you get these days.

Ralph Windsor:             01:22                And then around 2000, we were mainly doing web-based catalogs. Most of the clients were corporate and we were essentially looking to build in house media libraries rather than kind of yeah, going to stock video libraries and are there around that time we’re still doing offering all the sorts of services. So developing the software, doing scanning, because a lot of the images were still non-digital at that time. Sometimes managing digital asset libraries and also consulting, which is a big part of the service that needed to be provided then. And now I would argue also around 2012, we sold off the software side of the business to another vendor. We’re interested in taking that on for their own platform. And we focus now entirely on consulting since things like managing DAM implementations, vendor selection, metadata analysis, troubleshooting. We usually get asked to participate across the whole sort of range of, yeah, the DAM delivery life cycle you might say. And the thing I’ve probably worked on, I work this out, about 120 unique projects and each one of them has, yeah, I’ve learned something new from each one of them. So yeah, there’s a fair bit, yeah. In terms of my involvement with DAM, it’s pretty much defined my professional life you might say.

Henrik de Gyor:             02:52                Ralph, What are Digital Asset Management Open Specifications?

Ralph Windsor:             02:56                Yeah. No, that’s not a good question. there’s been a lot talk about standards in the DAM over the years. Various initiatives kind of come and gone tend to go anywhere because there isn’t really the kind of commercial motivation for the vendors to make the products work together. And the other sort of participants don’t really have the time or necessarily the inclination to make things happen. I know that the DAM Foundation, when that was still going, they set up this thing that the 10 core characteristics, I believe that was around 2014 and that’s not actually a bad first attempt at some sort of standard to work to. And it does cover the basics. But one thing I notice as you go through this towards the latter half of it, some of the areas of it get quite vague. So you’ve got sections like administrative capabilities, which are sort of quite broad and open to interpretation.

Ralph Windsor:             03:59                And there’s other things about being able to handle many types of files, which isn’t particularly a unique feature. I just kind of got the feeling there as they were coming up with this they maybe had the realization that this is quite a deep and complex sort of subject and just the fact that, you know, there are 10 characteristics rather than five or four or something. It gives you a clue that this is sort of an in-depth subject that doesn’t lend itself very well to a kind of static list so to speak. And just following on from that. Yeah, there’s things like APIs, reporting, audit trials…they’re not actually addressed by the 10 core, which I think they were aware of DAM Foundation and there was maybe an expectation that they might add those in later on.

Ralph Windsor:             04:56                But obviously the DAM Foundation’s not around anymore. So that doesn’t happen. The way I looked at it was this is less like a kind of fixed list or list of sort of characteristics. And it was more like something like an open specification, a functional specification of what a DAM system might be would be something that would be more appropriate just because of the fact that if it’s open, anybody who’s involved in the DAM community can in theory, contribute and comment on it and participate. And also cause it’s open-ended if there is new functionality becomes important in DAM systems, like some of the areas that I’ve mentioned or even if it’s simply just a missed off, it’s quite easy to develop those and it’s far more organic and dynamic as well. So, yeah, that that’s one of the things we’ve been looking at is I can open specification for DAM systems that you can benchmark when is against that can kind of grow and evolve as the industry does.

Ralph Windsor:             06:02                Obviously there are going to be caveats with it just like there are anything else. Just cause the system maybe ticks all the functional boxes doesn’t necessarily mean that it’s going to be superior to another one because things like usability and so on. And there’s the whole question of how to interpret whether or not a system has the functionality where it doesn’t. But yeah, open specification seem to be more suitable as a framework for evaluating and assessing DAMs. going forward then was we’ve got with the, the current initiatives, which were, were good at the time, but I think they’re becoming less fit for purpose than they were when they were originally envisaged.

Henrik de Gyor:             06:48                Ralph, what are the biggest challenges and successes you’ve seen with Digital Asset Management?

Ralph Windsor:             06:53                I think on the challenges side, there are two of them. The first would be user adoption and the second one would be interoperability. Just taking the user adoption first. I’m persuading as you know and we both participated in the webinar at the end of last year on user adoption with Lisa Grim, Ian Matzen and Frank De Carlo. What we talked a lot about a lot of these issues, but yeah, getting people to actually use a DAM once it’s been implemented and set up and so on remains one of the biggest challenges. I think that that affects everybody across, across the industry. it’s almost, it’s kind of chicken and egg conundrum. If you’ve got an organization where the DAM gets widely adopted, then it kind of almost, it generates a spark which maintains interest in it and a lot of buzz and activity and it becomes kind of self-sustaining.

Ralph Windsor:             07:57                but if you don’t get that right, then it never actually touches people’s imagination and it almost seems like it doesn’t matter what you do, it doesn’t actually get taken up. I think I’ve, I’ve mentioned this, made this comparison a number of times before. It really is DAM user adoption is a lot like a kind of sales and marketing activity and there’s definitely a lot of similarities between those sorts of activities with adoption and getting people to take up the DAM. So that’s, that’s one of the main challenges and I think that that’s always going to remain the case as well. yeah, so certainly on that side, the other big challenge has been interoperability. I was talking about standards earlier and basically, there aren’t our interoperability standards in DAM and on top of that there are hundreds, literally hundreds of systems.

Ralph Windsor:               08:54                Where this really becomes a challenge is it’s less about two DAM systems talking to each other. Although that does come in, it’s more where you’ve got third-party component that has to integrate a DAM with something else like a web content management system or you just want to build some plugin. Some functionality is going to extend upon a DAM to develop it in a way that the vendor didn’t envisage. If you one of these sort of tool vendors or you want to integrate with something, you’ve got a hundred products which you potentially got to develop a component for. Then what happens then is that the developers of those tools kind of have to make a choice about which ones they’re going to support, which ones are not. And profile, you know, using numbers and all kinds of things like that.

Ralph Windsor:             09:43                And, and I think yeah, interoperability, yeah. Is a big challenge for this asset management right now. And in terms of the successes, it’s almost like the flip side of, of the interoperability point. I think a lot of people now have, I’ve realized I’m certainly in the last six or seven years. I’m the integration and this whole digital asset supply chain piece which is coming in now is really important. And the, the advantages of being able to integrate and connect DAM’s, we’ve lost different systems and put your DAM’s system kind of like at the heart of the enterprise in terms of its, its role as a kind of media construct content hub. That’s been a massive success. That’s really what’s kind of keeping them in the game as an enterprise technology at the moment. So yeah, those would be my three or my two top 10 challenges and and top success.

Henrik de Gyor:             10:46                And Ralph, what advice would you like to share with DAM professionals and people aspiring to become DAM professionals?

Ralph Windsor:             10:52                Yeah. This is quite a broad-based one. I think to be a successful professional digital asset manager, you’ve really got to be self-reliant perhaps more so than the many other roles. You’ve got to take on a lot of different activities. They’re all quite different from Italia, quite unique terms of the skills that chances are you’re probably not going to have a team. And even if you have, it’s going to be a very small one. So, yeah, you’ve definitely got to be a self-starter or one of these people who’s prepared to learn a lot of different stuff and kind of get on with it without other people kind of yes, sort of coming along and spoon-feeding you or helping you. So the work kind of covers all sorts of different subjects. You’ve got to be a bit of a technical expert, you’re going to have very strong metadata skills.

Ralph Windsor:             11:44                I [have] at least an understanding of library science and some of the best digital managers I’ve come across all got MLIS library science qualifications. I talked earlier about sales and marketing knowledge for you getting people to adopt DAM systems. And there’s, there’s an element of that as well. You’ve got to be a bit of a kind of marketer and you’ve got to be constantly demonstrating to your senior management though that DAM and what you do does generate huge amounts of value for the organization. So there’s all those sorts of skills that have to get thrown into the mix. And I think if you really need to be as a professional, digital asset manager you’ve got to be honest with yourself and look at where you’re strong, where you’re weak, and if there are areas that you’re weak at, then you have to work on those. Yeah, keep your skills and the knowledge up to date. And if I make a plug here, I would obviously recommend you look at publications like DAM News and also, yeah, the DAM section on CMSwire and stay up to date with what’s going on in the industry so you can learn a lot more and, and develop your expertise as your career progresses.

Henrik de Gyor:             13:02                Great. Well, thanks Ralph.

Ralph Windsor:             13:04                Thank you Henrik. Thanks for the opportunity.

Henrik de Gyor:             13:06                For more on this, visit anotherdampodcast.com. If you have any comments or questions, feel free to send me an email at anotherdamblog@gmail.com. Thanks again.

 

Listen to Another DAM Podcast on Amazon Alexa, Apple Podcasts, AudioBoom, CastBox, Google Podcasts,  RadioPublic, RSS, Spotify or TuneIn

Need a Digital Asset Management Consultant?

Another DAM Consultancy can help. Contact us today.


by Leave a comment

Another DAM Podcast interview with Alex Struminger on Digital Asset Management and Storytelling 3.0

Alex Struminger on Digital Asset Management and Storytelling 3.0

 

 

Transcript:

Henrik de Gyor:  [0:01] This is Another DAM Podcast about Digital Asset Management. I’m Henrik de Gyor. Today, I’m speaking with Alex Struminger. Alex, how are you?

Alex Struminger:  [0:09] Fine, Henrik. Thanks for having me again.

Henrik:  [0:12] Alex, how are you involved with Digital Asset Management?

Alex:  [0:15] Henrik, in the last time we spoke, we talked a lot about the big enterprise rollout of the UNICEF Digital Asset Management System. That was a big project. It was terrific the way it came off, but one of the things that wasn’t happening then, that’s happening a lot now is the focus on transmedia storytelling. This has shifted my focus and the focus of a lot of folks in that direction.

[0:38] One of the areas I’m working on right now is the idea of storytelling. Storytelling supported by technology. I’m calling it Storytelling 3.0 to acknowledge the advent of semantic web, search and taxonomy, DAM enabled technologies, and you got to include mobile apps in that as well.

Henrik:  [0:59] How is storytelling supported by DAM?

Alex:  [1:01] It’s always been important. It’s one of the most engaging things you can do as a human being, I think. If you’re talking about engagement, you can point to the track record of stories as being the longest and best measurable forms of communication engagement out there.

[1:17] That runs the gambit from the famous “Star Wars” franchise and its success. If we go back 3,000 years and talk about The Iliad and The Odyssey, we’re still talking about that 3,000 years later. I think that that’s a measurable success.

[1:30] We’re talking a lot more about storytelling now in the digital world. And of course, Storytelling, especially the storytelling as it supports brands, has to be done in a way where you can manage the story across the franchise. Everybody took a different approach to how they did it, but it all required technology support, partly because there’s a lot of digital assets involved now in storytelling. We’re not squirting ink on paper like we did in the old days. We’re not even doing the digital form of that, which is the old web. We’re doing a lot of rich, layered media, and managing a tremendous number of assets to make that happen.

[2:06] I heard one person talk about 80,000 pieces of video that had to be managed. That didn’t even include the metadata or the supporting brand assets. So digital asset management is needed on the scale that we’re trying to do it with brands, especially global brands.

Henrik:  [2:22] What is a co‑creation network and how does it fit with DAM?

Alex:  [2:26] Co‑creation network are things to talk a lot about these days. Essentially, the idea behind a co‑creation network is if you have a group of people who are working on different kinds of product sharing a similar story. This could be for the Star Wars example. We talked about transmedia being something that literally transcends different kinds of media. I don’t know if transcends is the word I’m looking for. It is transmedia.

[2:51] It’s transmedia in the sense that there’s no uber story in any particular media so it’s not like “OK, I created the film. The film’s got all the bits in it. We’re just going to then repurpose those bits in these other places. I got the book, and I’m going to take all the stuff of the book.”

[3:06] The idea in Star Wars, again, is a great example, is that there are bits that are in one area and other bits in other areas, and they don’t quite overlap, but they share a common story. You can tell if they’re wrong.

[3:22] A great example of that, there’s the Star Wars films. I’m a big fan of them. I watched all of them several times. There’s the cartoon series about the Clone Wars, then there’s action figures, the product, there’s comic books, the novels, and all that stuff.

[3:39] Five years old at the time, my step‑son came in and he was trying to throw off the yoke of the homemade costume. After a lot of battling back and forth, and a good effort on the part of my wife and I to try and do the homemade costume thing for a few years, we finally capitulated.

[3:56] When he comes in with the costume catalogue from the online store, or the mail‑order store, and he’s got this whole page, there’s like six different bounty hunters he can be in Star Wars. He names every single one of them. I’ve seen every single one of the movies many times. I only knew the name of two of those.

[4:14] This is a great example of how the uber story and transmedia isn’t carried by one particular media type. It’s literally in that sense transmedia. In order to accomplish this, you have to have a co‑creation network in the sense that you’ve got to have a network of people who understand the brand, who understand the story, and who are essentially stewards of that canon, so that you don’t go over here and make that piece about the brand and the cartoon, or on the online thing, or this video over here, or an event in the physical world, and have it not be completely in line with the story. This is how the network has to be brought together.

[4:55] The role of DAM plays here is this is a really difficult thing to do. The challenge has been not just different skillsets with people doing different kinds of product, but they also span things like different localities. “I may need to have this done in French,” or “I may need to have this done in Chinese”. We have to make sure that that local translation works. Where do we keep all this stuff? In the DAM.

[5:21] The rights, the ability to use things for certain purposes, all that stuff has to be put somewhere. Otherwise, this whole thing has become way too expensive. DAM supports the co‑creation network in that sense.

Henrik:  [5:32] It sounds like brand consistency.

Alex:  [5:34] Brand consistency, brand protection, licensing. You don’t want to be shadowing the door of the lawyer’s office all the time, because you didn’t know you couldn’t use the product in China, or whatever it is. In this sense, I think the co‑creation is where the people, the creative people who are making the product, and all of the rules, the availability of the assets, their application, and who can do what with what come together. That’s technology‑enabled.

[6:05] That makes us better, faster, and more accurate doing what we’re doing, hopefully cheaper.

Henrik:  [6:10] What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?

Alex:  [6:14] One thing that’s really caught my attention recently, that I think is super important. Zach Brand of NPR has mentioned it as he ralled against the monolithic giant one‑size‑fits‑all system. We really want to avoid that kind of thing.

[6:27] This has been back and forth for various reasons. There have been times when a standardized platform has benefitted the organization, but there’s also a give‑and‑take with it. There’s a cost. I think that we’re seeing now more bespoke or custom tools for particular creative tasks. You don’t want to force the creative talent to use a tool that’s a one‑size‑fits‑all and therefore going to compromise the quality of the product.

[6:57] More than anything else, we see that in the world of storytelling, and in the world where brand engagement has to come to entertainment and storytelling, mistakes and lower quality products are noticed.

Henrik:  [7:09] In a negative sense.

Alex:  [7:10] Right. In the sense that the technology of the co‑creation network can support all of the things that help us make use of the assets, find them, use them correctly, and stay on story. At the same time, we don’t want that technology that’s helping us to get in the way of us doing quality work.

[7:26] Caitlin Burns said Starlight Runner talked to me a little bit about the idea of an arts and crafts approach to content creation. We really have to be craftsmen in order to make the kind of product that people are going to consume. If you’re going to be a craftsman, you’re going to have to have the right tools. I am seeing more and more custom tools being made.

[7:47] But here’s the thing. Interoperability is still very important. If we take away the monolithic system that’s supposed to tie everything all together, how are we going to tie everything all together? Are we now back in our silos? We don’t want to do that. What seems to be the approach that is working is the same kind of approach that worked for web 2.0 in a lot of ways. Standards, APIs, interoperability.

[8:13] So if I’ve got a toolset over here that’s working really good for the person who’s curating my digital media video, and I’ve got another toolset over here that’s working really well for somebody who’s creating cartoons, so forth and so on, managing print assets. I don’t want to force them to use one tool that doesn’t do any of that quite as well, but I need them to talk to each other.

[8:34] I don’t want redundant assets. I don’t want redundant metadata. I want to tie it all together, in case I need to bring something from here, and something from over there together to create a product on the web, or through an app, or through any place I want to be able to publish out the content.

[8:51] We can do that by letting the systems talk to each other. We don’t have to insist on the monolithic system. In fact, we’re not dead in the water. We can take a very agile approach to this and knock out little things. Let’s make this system talk to that system. We did this when I was in UNICEF. Tie together taxonomy management with web search engines and web content systems, and basically creating APIs that let them talk to each other and it that turns out, it can do it. Everybody’s happy because I didn’t make the guy over here use something he didn’t like, the data is shared, and it works.

[9:24] That’s the bit, I think, to keep in mind. Stay over the monolithic. The bespoke system. You could do an awful lot that’s not bespoke but still custom these days. Just let them talk to each other, and think about the process, and the people involved.

Henrik:  [9:38] Thanks, Alex.

Alex:  [9:39] Thanks, Henrik. It’s always a pleasure to be with you.

Henrik:  [9:41] For more on this and other digital asset management topics, logon to anotherdamblog.com.

Another DAM Podcast is available on iTunes and AudioBoom.

[9:49] If you have any comments or questions, please feel free to email me at anotherdamblog@gmail.com.

Thanks again.

 

Listen to Another DAM Podcast on Amazon Alexa, Apple Podcasts, AudioBoom, CastBox, Google Play,  RadioPublic, RSS, Spotify or TuneIn

 

Need a Digital Asset Management Consultant?

Another DAM Consultancy can help. Contact us today.


by Leave a comment

Another DAM Podcast interview with Richard Buchanan on Digital Asset Management

 

Here are the questions asked:

  • How are you involved with Digital Asset Management?
  • How does a media company use Digital Asset Management?
  • Do you use specific standards and do you feel there are enough in Digital Asset Management?
  • What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?

Transcript:

Henrik de Gyor: [0:01] This is Another DAM Podcast about Digital Asset
Management. I’m Henrik de Gyor. Today I’m speaking with Richard Buchanan.
Richard, how are you?
Richard Buchanan: [0:10] I’m fine today. How are you?
Henrik: [0:12] Good. Richard, how are you involved with Digital Asset
Management?
Richard: [0:15] I work with the Comcast Media Center in Denver, Colorado. We
are a technical facility that supports Comcast and NBCUniversal and commercial
clients throughout North America. We specialize in delivery of file assets, such
as video on demand. We do live events. We do content aggregation and distribution.
We do channel origination, and we do production and post-production.
Henrik: [0:45] Excellent. Richard, how does a media company use Digital Asset
Management?
Richard: [0:52] A media company like ours has a huge inventory of assets with
multiple platforms and routes for delivery. To keep track of all that and be able
to do it efficiently, with high quality, and consistently deliver the customer experience
that’s expected, you have to be able to find your assets and deploy them
in a very rapid turn time. [1:17] For example, we pitch about 10,000 video on
demand assets every 30 days. This comes in from 297 different sources and is
delivered in Canada and the US to 97 percent of the VOD enabled households
available.
Henrik: [1:38] VOD, video on demand.
Richard: [1:40] Video on demand. That’s correct.
Henrik: [1:42] Excellent. Do you use specific standards, and do you feel there
are enough in Digital Asset Management?
Richard: [1:47] In the case of video on demand, we use specific standards that
have been exacted by what’s called CableLabs. A consortium of cable companies
came together about 20 years ago and established a group to test, analyze,
and publish standards so that the industry could share content more easily.
[2:10] This specifically affected how set top boxes were developed, how VOIP
was rolled out over cable MSOs, and now how video on demand is delivered
and managed. There are specifications not only for the file type and the signal
quality, but also the metadata that goes with it.
[2:30] In the Digital Asset Management field, this is a wide open opportunity for
someone to take the reins and form a group to start to define what the standards
are in order to create more interoperability among vendors and more
efficiency for users.
Henrik: [2:52] We would hope that some of those entities may possibly be in
existence such as the DAM Foundation, which was started a few months ago.
Time will tell, for sure.
Richard: [3:02] Yeah.
Henrik: [3:04] Let me finish with the last question I ask individuals that I interview.
What advice would you like to share with DAM professionals and people
aspiring to become DAM professionals?
Richard: [3:12] I would say focus on one of three areas. You can be a technologist,
you can be a leader, or you can be a designer. I think that all three of those
disciplines are very important if you can learn more than one or all three. But I
think the important message is it’s not just technology.
Henrik: [3:39] True.
Richard: [3:40] There has to be some creative thinking, especially around defining
problems, being able to decide what it is you can solve and how you
can solve it and prevent scope creep. So that you know how you’re going to
deliver what, and what it’s going to cost. [3:56] So the benefit to the company
is well demonstrated at the end of the project, and the leaders who are able
to manage these different disciplines and apply the traditional thinking that’s
necessary to deal with legacy libraries and bring them into contemporary digital
multi-platform distribution environments.
[4:19] I think that what I would say is be clear on what your objectives are, define
the problem you’re trying to solve and don’t get distracted from that.
Henrik: [4:29] Great advice. Thanks, Richard.
Richard: [4:32] You’re welcome.
Henrik: [4:35] For more on Digital Asset Management, log on to
AnotherDAMblog.com. Another DAM Podcast is also available on Audioboom,
Blubrry, iTunes and the Tech Podcast Network. Thanks again.

Related Articles

 

Listen to Another DAM Podcast on Amazon Alexa, Apple Podcasts, AudioBoom, CastBox, Google Play,  RadioPublic, RSS, Spotify or TuneIn

 

Need a Digital Asset Management Consultant?

Another DAM Consultancy can help. Contact us today.