How are you involved with Digital Asset Management?
How does your organization wrestle 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: [0:01] This is Another DAM Podcast about Digital Asset
Management. I’m Henrik de Gyor. Today I’m speaking with Tom Barnouw.
Tom [0:09], how are you? Tom Barnouw: [0:10] Good, thanks. How you doing? Henrik: [0:11] Good. Tom, how are you involved with Digital Asset
Management? Tom: [0:14] Well, I work for WWE, been here about six years, and I retired as a
systems engineer. I’m involved with Digital Asset Management. [0:24] We have
many live shows a year, thousands and thousands of photographs are taken
at each live event, and those assets make their way back to our company for
processing. They are used for a variety of things from websites to publications
to any type of creative services project. As these photos come in, they’re processed
by our photo department and uploaded to servers, at which time our
asset management system catalogs all those. There is metadata written to each
asset so that everything is searchable easily.
[1:03] There are many layers we have on top of our assets that can satisfy different
work flows. We’ve got certain catalogs that are web enabled. Other things
can be sent out via email, with voting and approval processes that can take
place and things. We’re web enabled data where end-users can vote and actually
have metadata written back to the assets.
[1:30] A significant process is in place for easily sharing assets around the company,
without the need to duplicate the files or copy them to other storage
medium. My involvement is in managing that workflow and trying to find efficiencies
throughout the company and ways that we can leverage the asset
management system. Henrik: [1:51] How does your organization wrestle with DAM? Tom: [1:54] It’s been an interesting evolution over the last six years or so.
Working with Cumulus has grown tremendously over those six years, aside from
just doing the system administration of the backend infrastructure. I think one of
the most important and impactful things that’s occurred over that time is really
studying the workflow of our users, and I would say the lifecycle management
of the data that our asset management system tracks. [2:24] We’ve evolved into
a very nice system now. We have several million assets in our system and, as an
asset ages, we need to move it, not just from the asset management side, but
from the storage side, from disk to tape, how does that process?
[2:42] The first thing we wrestled with was how do we manage the lifecycle of
this data? As an asset becomes older it’s used much, much less frequently. Do
we need to keep it on disk? If we do move it to tape, how do we easily access
that asset on tape? We struggled on solving some of those problems.
[3:01] We’ve come to a very nice place with it now where it all works very, very
nicely, including giving the end-user the ability to manage those assets, to some
degree, to a much more limited degree than I can, but still, they have access to
things, even when they’re on tape, which is nice.
[3:18] Other challenges I’d say, we continue to work with is the various workflows.
It’s one thing to have an asset management in place, cataloging assets, but
there are so many different this is going to be different in every company but,
there are so many different workflows.
[3:35] One department or one person may have very different needs for those
assets than another, understanding those various workflows, and customizing
the asset management system to blend in well with those required workflows.
In most cases, improve on those workflows. We’ve been able to leverage our
system to create significant efficiencies in workflows for different people in different
departments.
[4:04] In terms of how we wrestled with that, I think, that process hasn’t stopped,
in fact, I feel like I’m just now at the beginning. Now that we’ve got a very solid
foundation for our system in place managing lifecycle, I can turn my attention
much more to tackling various workflows and creating efficiencies within
the company. Henrik: [4:23] What advice would you like to share with DAM professionals and
people aspiring to become DAM professionals? Tom: [4:28] I think it would probably have to segue way from what I just talked
about, which is there are so many different things. Obviously, each company is
going to have different needs, various storage needs, depending on how much
data you’re actually dealing with. That can significantly impact what lifecycle
management you may or may not need to have in place. [4:53] I think, again, just
what I talked about. Try to think into the future, 1, 5, 10 years from now where
do you think these assets are going to live, what access do you think people will
need to them you can start with that foundation, then, trying to understand the
various workflows that may exist within a company.
[5:16] If you can do a lot of groundwork ahead of time, before deploying something,
even if you have deployed something, start at that 30,000foot view to try
to get a good understanding from the needs of the company as a whole, and
then you can begin to zero in on different topics and processes that you can
help with. Henrik: [5:36] Thanks, Tom. Tom: [5:37] No problem. My pleasure. Henrik: [5:39] For more on Digital Asset Management, log on to AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, iTunesand the Tech Podcast Network. Thanks again.
How are you involved with Digital Asset Management?
How does the broadcasting organization use 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 Dave Klee. Dave, how are you?
Dave Klee: [0:09] I’m doing well, Henrik. How are you?
Henrik: [0:10] Good. Dave, how are you involved with Digital Asset Management?
Dave: [0:14] Well, I actually read one of your earlier blog postings about making your elevator pitch, so I’ll give you mine so far. I’m a systems engineer, working in media asset management at NBC, so most of what I do focuses around organizing video files for NBC News. [0:30] Whenever you see old footage that shows of up of, maybe, a politician saying something contradictory, or some major event that’s happened in the past, I work on the systems that help people within the company find that stuff and put it into stories that they’re working on for the news. [0:45] As you can imagine, those systems are pretty big and complicated, so they need a lot of attention, and I work on a team that helps support them and figure out how to make them work better.
Henrik: [0:53] How does a broadcasting organization use Digital Asset Management?
Dave: [0:56] Well, there are a lot of uses within NBC, and I’ll only speak to the ones I know about. There are some things on the distribution side, obviously, that I don’t work with very much. People when we’re done making a TV show or a program, we’ll ship it off to someone else, and usually in many different formats, and a variety of different ways, so we have systems to facilitate that. [1:17] Also, when making TV programming, we’re working a lot with collateral material or things that would support that programming, so you might have graphic design for a website, or DVD material, or a billboard, or an advertisement. We have systems that help facilitate that, that I don’t work with very much. [1:33] What I do is really work with NBC News, and when I say, “News,” I mean “Nightly News,” anything that happens on MSNBC, the cable channel, the “Today Show,” and then some of our longer shows, the news magazines like “Dateline” and “Rock Center with Brian Williams.” [1:49] In these systems, there are really two major things we’re looking to accomplish with Digital Asset Management. First and foremost, it’s to enable daily editorial workflow, to let people get through the day, and also to build a longterm catalog and archive. I can briefly talk about what those mean, and I think it’s very interesting, because there are some tensions between those. [2:11] First of all, for a daily editorial workflow, it’s a big place, so there are a lot of people working on a lot of different things, as you can imagine, and we need systems that can tie people together, to allow them to collaborate, and share information, and share core footage, underlying what they’re working on. [2:30] A lot of times, things will end up being used across our different platforms. We might have a story that’s developing throughout the day on the cable channel that will incorporate a small piece with the nightly news, or we might have a small piece on the nightly news that ends up becoming a larger piece on one of the news magazine shows like Rock Center. [2:49] We need systems that help people work together, share footage, and we have producers working with editors. Sometimes, we have multiple video editors working on the same project. We just need systems that really facilitate that workflow and get people working together. [3:05] On the other side of things, we’re working on a long-term catalog and archive. Like, I’d imagine many broadcast organizations, we started with a lot of footage on film. Over time, this footage on film got migrated to videotape. Over time, the old videotapes got migrated to new videotapes. Now, we’re taking these videotapes and starting to put them into a centralized system, a centralized repository so that people can find them in the future. [3:36] As we’re doing that, we’re working on cleaning up the metadata because over time, metadata entry was done by many different people and manipulated in many different ways when things moved from one system to the other as you can imagine. There’s a lot of metadata cleanup that’s done during this process. [3:54] Then, there’s new footage, too, that’s constantly coming in. A lot of the new stuff that comes into the building comes in on satellite feeds from all over the world, and so we need some people who are sitting there adding metadata and cataloging things that are coming in in real time. [4:08] This footage is used both in future programming and sometimes, it’s sold to other people because one of the things we can do is license this footage. We need to keep track of rights and what we own and what we’re able sell to other people so when people are making other documentaries or TV shows or films, they may come to us looking for footage. [4:31] I think these two different things, the long-term cataloging and the short-term workflow, are really interesting because they have such different needs. I think there are really a few key conflicts or tensions that we have to think about and work on when we’re trying to support these systems and when we’re trying to fix them and build new ones. [4:54] One of the main ones is accessibility versus security. For daily workflow, we really want assets to be as accessible as possible. We want people to be able to get whatever they might need to get their job done, but in the long-term, you generally want to carefully want to manage your permission structure and make sure that people only get access to the stuff that they should have access to and prevent people from doing things that might be bad like accidentally deleting assets or changing metadata when they shouldn’t. [5:25] If you think about it in terms of a physical place, a building with doors, for the daily workflow, you might really want everyone to have the doors open and people just get wherever they need to go. But, for this long-term archive, you want carefully give out keys and carefully control which keys open which doors, so people only get access to the stuff that is appropriate. [5:47] That’s a real tension. Another big one is speed versus safety. For the daily workflow, you want people to get access to things as quickly as possible, and you want that to be a seamless process. We need systems that are fast enough to be able to grab something while it’s recording, put it into a project, and then ship it off to be played back on the news. [6:09] But that process flies in the face of building systems that are extra safe, because the safer systems aren’t necessarily the fastest systems. When you have a long-term archive, if you really want it to be safe, you want to put things on the safest media you can, but often the safest media is the slowest. [6:26] Another big tension for us is flexibility versus reliability, or maybe flexibility versus consistency. A lot of different people in the building, and you want to allow people to work the ways that they work best so that they can get their jobs done. That means you need to be flexible in daily workflows, but at the same time you really want to produce consistent results for this archive. You want metadata that’s full and complete, and you want things to be very consistent for the long term. [6:54] That’s a big tension for us. The last one I’ll mention is usability versus quality. Ideally, and this is very true for video files, you want the highest possible quality video file in your archive, but there’s a price to that. The highest quality video files not only can be very big, which makes your system much more expensive, because you have to build in extra storage and extra bandwidth to accommodate such big files. [7:22] It can also be complicated when you’re dealing with the highest quality files, because often these are original files that came right out of a camera, and many different cameras use many different types of video files. The video world is very fragmented when it comes to types of video. If you put the original video file, which is arguably the highest quality, into your archive, you may be dealing with a file format that doesn’t exist in a few years, or a file format that’s very complicated to get into the system that want to use it in. [7:55] You end up with these very complicated workflows that make the system less usable. By streamlining a system on just a few codecs, a few types of video, and making them compressed or standardized in a certain way, it can make the system much easier to use, much easier to build. But that’s a real tension that we’re always trying to figure out, because the archival aspect demands quality, and the workflow aspect really demands usability. [8:25] These tensions, I’d imagine, are in a lot of different technologies, but I think they’re just amplified in a big broadcast news environment, because there’s a huge difference between how the fastest system would perform and the safest system. Small choices you make in different types of video formats would demand a whole different type of architecture. [8:45] Really, we need, for the broadcast world, systems that can serve both masters. We need a short-term fast and flexible workflow enabling tool, and we need a long-term, secure, high quality, centralized repository. Both those things need to happen, and I think that provides some interesting challenges and some opportunities.
Henrik: [9:05] What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?
Dave: [9:09] For people who are DAM professionals, I’ve actually listened to some of your other podcasts, I wouldn’t necessarily purport to have any advice to offer them. I’ve gotten some useful tips from the ones I’ve listened to. But, for people looking to get into it, or looking in from the outside, I can tell you there are a few things that have really helped organize my thinking around Digital Asset Management since I’ve gotten into it. [9:31] One of them is about these choices that you have to make, and understanding that Digital Asset Management, once you really get into it, I think is about making some tough choices, often between two different things that are right, but they can’t both be right at the same time. Successful organizations are the ones that, at the outset, do a lot of self-analysis, really look at what the organization needs and wants, and take times to discuss these tradeoffs, because not only does that help you build a better system, but I think that helps you build consensus and set expectations about what your DAM will do and what it won’t do well. [10:12] The second thing is, as a technologist, I’m constantly trying to remind myself that technology doesn’t always have all the answers for us. Those answers are really within the organization or within workflows. [10:26] Rather than just adopting whatever new technology comes out and then trying to force that into the workflow for the users, I think it’s a much more powerful way to work when you centralize on your workflows, how people want to work and how your organization wants to be. Let that drive your technological decisions. [10:46] Then, I think those technologies can really fall into place. You make those decisions from a place of much more power. [10:54] The final thing I might share is that I really believe Digital Asset Management is a journey, not a destination, per se. There are a lot of vendors that I think will encourage this big bang idea of you buy something off the shelf, you implement it and you put all your stuff inside. Bang, your assets are managed, problem is solved. [11:16] I think the more you do things with Digital Asset Management, the more you realize that’s not the case. It’s an ongoing process. Even once you’ve got a very good system in place, over time it’s going to need to adapt to new people, to new workflows, new technologies, new ideas. A good system is going to do that for a very long time, and that’s OK .
Once I stopped looking at Digital Asset Management as a problem that could be solved and started looking at it as a process that could be managed, that really helped me, not only make some better decisions, but set some better expectations within the organization and help build systems that just made more sense.
[11:37] Once I stopped looking at Digital Asset Management as a problem that could be solved and started looking at it as a process that could be managed, that really helped me, not only make some better decisions, but set some better expectations within the organization and help build systems that just made more sense. [11:57] For people starting out or looking at this process, I think those are some things that have helped me ground my thinking.
Henrik: [12:04] Well, thanks, Dave.
Dave: [12:05] Thank you. It has been a pleasure.
Henrik: [12:06] For more on Digital Asset Management, log onto AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, iTunesand the Tech Podcast Network. Thanks again.
How are you involved with Digital Asset Management?
How does an organization focused on entertainment television use Digital Asset Management?
Congratulations on winning the DAMMY Award for Best Strategy Ease of Use for End-User Interface. Tell us about this strategy.
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 Paul Nicholson. Paul,
how are you? Paul Nicholson: [0:09] Good, how are you doing? Henrik: [0:10] Good. Paul, how are you involved with Digital Asset
Management? Paul: [0:14] I am in charge of amongst other things, at Showtime Network, I’m in
charge of Digital Asset Management here for our creative group that we call,
“Red Group.” Henrik: [0:24] How does an organization focused on entertainment television
use Digital Asset Management? Paul: [0:29] We use Digital Asset Management in many, many ways here at
Showtime. There are a couple of different systems around the company handling
different kinds of assets, whether it be the long form shows and movies
that we air on our networks or the creative assets that we create to promote
the various shows. The majority of my responsibility falls under the promotion
aspect. [0:52] We create all of the video commercials or promos that run on
our networks. We manage and maintain them in a Digital Asset Management
system so that we can find them, archive them, keep them organized, distribute
them, et cetera.
[1:06] We also manage and maintain all of the print assets, all the advertising, and
marketing materials that we create in-house logos, graphic files, various elements,
lots of photography those types of things. Henrik: [1:19] Congratulations on winning the DAMMY Award for Best Strategy
Ease of Use for End-User Interface. Tell us about the strategy. Paul: [1:28] Thanks very much. That’s a very, very important part of what we do
here with Digital Asset Management. We really think about the user interface
and the customer experience, if you will, using our DAM system. Our customers
are other departments around the company, not necessarily outside consumers,
but internal customers. [1:49] It’s very, very important that they’re able to
find things quickly, get to exactly what they need in a moment’s notice, so they
can put together either a presentation or distribute a file to a partner that we’re
using to create something, or just find the assets that they need to create other
assets from those assets.
[2:10] User interface is very important. We take a, what we call here, a Tonka
truck mentality with user interface. It’s got to be real simple, big, clearly laid
out buttons and features that people know exactly what they’re doing. We lead
them down the path to what they’re looking for, as opposed to them having to
hunt and shop for things in confusing ways.
[2:34] I think a lot of people take the other approach. They put lots of features
on the screen, lots of buttons, lots of widgets, lots of tools, and great capabilities,
but that takes away from the user experience because they can’t ultimately
navigate it as quickly. There’s lots of training involved when you do it that way.
We take a very simple approach. Henrik: [2:54] What advice would you like to share with DAM professionals and
people aspiring to become DAM professionals? Paul: [2:59] I think the most important part, I always felt, with instituting a DAM
policy, or DAM application, in any organization is that it doesn’t replace the
business process. The business process needs to be there. It needs to be organized,
you need to have good policies and procedures for people to do their
jobs, and then the DAM system can complement that. [3:22] It’s not a replacement.
A lot of people feel like they’re going to buy a piece of software, they’re
going to install it, and that’s going to change and organize their entire operation.
It doesn’t really work that way. It’s just a complement to what you’re already
doing. Of course, it can enhance that, but it’s not going to replace good,
sound business policy and procedure. Henrik: [3:42] Thank you, Paul. Paul: [3:43] You’re welcome. Henrik: [3:44] For more on Digital Asset Management, log onto AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, iTunes and the Tech Podcast Network. Thanks again.
How are you involved with Digital Asset Management?
How long does it take to implement Digital Asset Management within an organization?
Why does it take this long to get it working within the organization? What is involved?
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 Joel Warwick. Joel,
how are you? Joel Warwick: [0:09] I’m good, and how are you? Henrik: [0:11] I’m good. Joel, how are you involved with Digital Asset
Management? Joel: [0:14] I’ve been consulting in this field for almost 10 years now. Primarily,
I’ve done most of my work with end-use firms, firms that are implementing DAM
in one way or another. I’ve also done some work for the technology vendors,
both in DAM and in the auxiliary space, helping them with their strategy. [0:32]
Especially as the proliferation of SAAS-based services have come out there,
DAM vendors have had a challenge figuring out how to meet the needs of hosted type
implementations while still serving firms that are looking for the on site,
enterprise implementation. Henrik: [0:49] How long does it take to implement Digital Asset Management
within an organization? Joel: [0:53] That’s a loaded question. It depends on how you look at what
implementation means. If we’re just talking about implementing the software,
some organizations, it can happen in a few weeks. [1:06] I would argue when I
talk about implementation, the goal that I propose with my clients is, “When are
you going to actually be able to take advantage of new and improved business
processes?”
[1:20] What I mean by that is, “Why do we implement enterprise systems in the
first place?” It’s not because of some feature or function that they have. It’s because
we want to change our business processes in some way that benefits us,
whether it’s cost savings or lighting up a new revenue channel, what have you.
[1:36] In order to change those business processes, there are a lot of other
pieces, other than just implementing the software. Most of my work has been
helping clients through that. That takes a lot longer than just implementing the
software and training users on it.
[1:53] There are a lot of pieces that really have very little to do with the software.
These are issues of what I call “operational design,” which is a big catchall that
covers everything from organizational alignment, to detailed workflow planning.
[2:09] It really depends on the size and complexity of the organization. I would
argue that you’re looking at, at a minimum, a few months to be up and running,
where you say, “We used to do it this way. Now we do it this other way, with the
benefit of this new technology.”
[2:27] The technology itself doesn’t make that change happen. That’s a misconception
that a lot of people fall into. Even after doing this for a long time, I still
tend to fall into that, too. It’s so attractive to think, “We get this thing installed,
then we’ll be able to do this, this new way and it’s going to be great.”…
[2:45] Unfortunately, that change has to be programmatically implemented.
There’s a lot of upfront work that has to happen before the software actually
gets implemented. In some organizations, honestly, it takes years.
[2:59] That’s not to say that they don’t get benefit earlier on. They might get
benefit after three months or six months. But, the real change that they’re looking
for, and the ROI that they’re looking for when they decide to implement
DAM, may be a couple years out. Henrik: [3:15] Why does it take this long to get it working within an organization?
What’s involved? Joel: [3:23] When I talk about operational design…I’ve presented about this
quite a bit, as you know, and written articles about it as well. I’ll throw out some
components that are what people, especially an IT group, wouldn’t typically
think of as part of an enterprise system implementation. [3:41] Things like standards,
workflow design, digital rights models, organizational alignment, all the
capture and migration that have to go on, capturing assets and migrating them
from existing systems. Also, the appropriate scoping can be a real challenge in
figuring out, “What content are we going to put in this thing? What users and
what workflows are going to be included?”
[4:06] People oftentimes don’t have that much patience, especially executive
sponsors. You want to show value right up front, so you want to try to figure out,
“What content do we get in this thing now?” and, “What workflows do we light
up using this new system that are going to show some benefit, but at the same
time isn’t everything under the sun?”
[4:25] That’s how most organizations look at this. They go, “We’re going to throw
everything in here and we’re going to use it for everything.” Unfortunately,
you can’t do that all at once. Just the disruption it would cause makes business
impossible. Staging it appropriately by getting the right user and asset scope,
that’s an exercise in and of itself.
[4:44] In terms of where a lot of the time is, I would actually say that the organizational
alignment piece is the trickiest piece. That can be for a number of reasons.
It could be because you have an organization that’s very fragmented, and
you have groups that have been fairly autonomous up until this point.
[5:03] The model is, “We’re all going to start sharing stuff. We’ll be able to reuse
content.” If those groups aren’t already oriented towards that type kind of work,
there’s going to be a challenge redesigning those business processes.
[5:16] Sometimes it’s not political, at all. It’s just that the groups don’t know that
much about each other, or they’re sharing very little content and there’s an
expectation that that’s going to change overnight. We know how organizations
are. It doesn’t matter what the change is, that type of fundamental operational
change isn’t going to happen overnight.
[5:35] But the most important piece is actually having people working on that
specific problem, going in and understanding the workflows of both groups,
looking at where they interact, designing those interaction points and in particular
the standards, the policies, and the practices that have to change.
[5:51] Just to give you a very specific example, a lot of times let’s say that there’s
a print group, some kind of print publications, whether it’s marketing or publishing,
and there’s the web group. They say, “Why doesn’t the web group have
access to all the images that the print group has? They might as well. We’ll
figure out the rights issues and whatnot.”
[6:13] But the thing is, the web group has not been acquiring their content.
Suddenly, they’re being told, “You have to go look at the print group’s images
first before you go off and buy your other images.” What’s the policy going to
be? This is where you could get into a political issue. Even if it’s not political, you
still could just get into an issue of, “This isn’t the right content for us.”
[6:33] Someone actually has to do an assessment of whether that policy is going
to work. Then, once you’ve established it, there’s the actual enforcement of the
policies. Is this going to be a really hard rule where they really can’t go off and
buy new images as they have been? Or is it going to be more flexible as they
figure out how to do it? It’s just one specific example, but you can imagine in a
lot of organizations that that’s not a minor issue.
[6:59] Because it can get political, it involves people in those organizations at
more senior levels than just what you would look at normally for an implementation.
The head of the business unit, the print business unit for instance, probably
has to talk to the head of the web operations or the online unit to figure out
where that balance is going to be.
[7:20] That’s one of the reasons that involving the right people upfront in getting
that organizational support is really, really important because when you’re
way down the road in a project and you’re trying to figure out the metadata
model so you can get the system turned on in two months, that’s not the time
to run into that snag and say, “Uh-oh. We have to involve all these more senior
people” because you know what happens then.
[7:42] It goes into a bucket of conflict resolution. The solution that comes out of
it may not be the best one for the system or for the operations. It may just be
that someone’s trying to put out this fire so to speak. So getting them engaged
upfront is really important. Henrik: [7:57] What advice would you like to share with DAM professionals and
people aspiring to become DAM professionals? Joel: [8:00] I think the challenges right now is that the space is so fragmented
and complex, even in nature. When people say “digital media,” that’s all over
the map right now. I think that’s the real trick, is to understand the space, who
the players are both in terms of the technology but also firms that can help
organizations whether it’s consulting firms or system integration firms or a professional
services group from the vendors themselves. [8:29] Then, understanding
how to leverage those without just dumping tons and tons of money into it
because that model just doesn’t work anymore. The big consulting firms come
in and say, “We’re going to hang out with you for two years, and it’s going to
cost $2 million.” Nobody has budgets for that kind of thing anymore, which is
probably all for the better.
[8:47] There are a lot of opportunities for people that have some experience like
yourself, managing content operations if you want to call it that, or digital media
services organizations to go out again to help other firms if that’s what they’re
looking to do. Henrik: [9:01] Thanks, Joel. For more on Digital Asset Management log onto AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, iTunes and Tech Podcast Network. Thanks again.
Another DAM Podcast 