How are you involved with Digital Asset Management?
Can you explain the difference between semantics, taxonomy, ontology and metadata?
What advice would you like to share with DAM Professionals and people aspiring to become DAM Professionals?
Transcript:
Henrik de Gyor: [0:00] This is Another DAM Podcast about Digital Asset
Management. I’m Henrik de Gyor. Today I’m speaking with Sarah Berndt. Sarah,
how are you? Sarah Berndt: [0:09] Hi. Good afternoon, Henrik. I’m great, thank you. Henrik: [0:11] Sarah, how are you involved with Digital Asset Management? Sarah: [0:15] Well, I work on the ITAMS contract, specifically for an employer,
DB Consulting. My task is to provide a controlled vocabulary, or a taxonomy,
for the Johnson Space Center, accurately representing over 50 years in manned
space flight. Henrik: [0:31] Can you explain the difference between semantics, taxonomy,
ontology, and metadata? Sarah: [0:39] All of these are relative definitions, but within the semantics system
that I use, and within my own environment, the taxonomy, of course, is a hierarchical
system, a controlled vocabulary with a treelike structure. It’s agreed upon
overarching definitions for classes and concepts. [0:57] Ontology, then, is really
referring to the relationships between those classes and concepts, so we can
see that STS135 is related to a particular vehicle, it’s related to Launch Pad 39A,
it was crewed by these folks, it carried this payload. That type of information is
the ontology.
[1:21] Metadata, the most overused term of the century, is definitely relative, but
in my environment, I use a term “metadata library,” and what these are, specific
fields that have been set up to convey to the end-user, through the interface,
things like a Best Bet URL, a decided upon definition, an official definition, an
official image that might be relative to a specific mission patch or expedition,
for example.
[1:53] These components of the semantic system can be taken on whole and
conveyed to the end-user, or divided apart and plugged into different applications,
so that we have multiple uses throughout the organization. Henrik: [2:09] That makes sense, so you can have multiple metadata
fields. Sarah: [2:12] I think that is absolutely essential to decide on what your definitions
are right from the get-go. You need to decide, is your ontology actually
metadata to your taxonomy, or is it the term “metadata” that’s going to be
making the big influence? All of these things definitely need to be defined,
and shouldn’t be assumed or taken for granted. [2:36] When you start from the
ground up, sometimes you wish you’d had known what to do first, but it’s definitely
better or more advisable to plan the structure from the beginning. The
taxonomy, the basic structure, to have that from the beginning and to build the
ontology from the point and the term metadata from that point.
[2:57] The structure then provides a foundation for all that unstructured content
and data that you’re actually, that’s your angle that you’re actually trying to
represent. Henrik: [3:09] And hopefully find again. Sarah: [3:11] Yes, again, the end goal. We want to find it. We want to reuse it.
We want to improve the end-user search experience. Henrik: [3:19] That totally makes sense. What advice would you
like to share with DAM professionals and people aspiring to become DAM
professionals? Sarah: [3:24] It’s a good thing. [laughter] Sarah: [3:28] No, seriously, I would say don’t pigeonhole yourself. My title is JSC
taxonomist. I’m a contractor. JSC taxonomist, it’s great to have a title, but if that
were all I had to do, that would be quite a pigeonhole. [3:45] To really reach out
and take a look at the interoperability between your systems, between your file
formats, between your duties, you can be one day searching for more subject
matter expert participation, and the next day reporting off to management
about the ROI, and the next day, trying to win funding for a cost benefit analysis
study.
[4:08] There are an endless array of hats that can be worn. I would say definitely
be careful about how you pigeonhole yourself and take advantage of the multiple
definitions that can occur in the workplace. Henrik: [4:24] Great point. Thank you so much, Sarah.
How are you involved with Digital Asset Management?
How does a worldwide entertainment company use Digital Asset Management?
You recently started another DAM meetup group in your area. Tell us more about this.
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 Michelle Jouan.
Michelle, how are you? Michelle Jouan: [0:11] I’m fine, thanks. How are you? Henrik: [0:13] Good. Michelle, how are you involved with Digital Asset
Management? Michelle: [0:16] I am the Digital Asset Manager for one of the online departments
of a global entertainment company, and I’m based in London. Like a
lot of other Digital Asset Managers, I stumbled into the field through a background
in photography, and digital imaging, and managing databases, and all
kinds of computer geekery. [0:35] These are skills that I acquired independently,
which suddenly made sense when I saw my first job listing for Digital Asset
Management. The first job that I got in Digital Asset Management, about 10
years ago, was working for a motion picture company as an image archivist.
Since then, I’ve been known as a digital librarian, and now, actually, a Digital
Asset Manager, so the field is progressing a little bit.
[0:57] I’ve been lucky enough to find positions in companies that recognize the
value of Digital Asset Management, and the benefit of having asset managers
that can bring their expertise to improving workflows, because I get the feeling
that a lot of companies that buy asset management systems expect their asset
troubles to just disappear magically.
[1:15] The thing is that these complex systems, they aren’t just merely software.
They’re systems, and without someone to manage them after implementation, I
think they’re much more likely to fail.
[1:27] That’s not to say that every company, or every team, might have the resources
or vision to employ someone solely for this purpose, or that managing
digital management asset systems is something that can’t be learned by your
current staff, but if you’re investing potentially hundreds of thousands of dollars,
or pounds in my case, in digital management asset systems, you’d be really wise
to bring in a professional to get the most out of your investment. Henrik: [1:51] How does a worldwide entertainment company use
Digital Asset Management? Michelle: [1:55] Well, my company has more than 30 asset systems, globally actually,
company wide, but this is in the context of a company that has more than
100,000 employees. There are all kinds of digital workflows to manage, and 30
asset systems seems in line with what we need at this point, but all of our departments
operate essentially as different companies. [2:23] One of my biggest
challenges when I started working here was to learn how the company worked
as a whole, and to understand where assets were created and how they were
distributed, but the great thing about being at a company of this size is that
there’s lots of other Digital Asset Managers.
[2:37] It’s been really a joy to connect with them and learn from all of their experiences,
because if you work at a really big company, don’t forget how important
internal networking can be. There’s a wealth of knowledge out there, and you
can tap into that. Henrik: [2:50] Michelle, you recently started a Meetup group in London. Tell us
more about this. Michelle: [2:55] Well, after attending a few Henry Stewart DAM Europe conferences,
I really enjoyed meeting up once yearly to talk with other Digital Asset
Managers and basically talk shop with people whose eyes don’t glaze over when
you mention Digital Asset Management. So, kind of following in the lead of the
other meet up groups in New York, D.C., and Los Angeles, I thought it would
be a really good idea to get London Digital Asset Management professionals
together and talk on a regular basis. [3:24] If you’re in the U.K., please search
for London DAM on meetup.com or follow our Twitter account @LondonDAM
with no space. Henrik: [3:33] What advice would you like to share with DAM professionals and
people aspiring to become DAM professionals? Michelle: [3:37] Well, if you’re already a DAM professional, I’d say just be nosy,
be curious, and learn about business processes, and seek allies within your
company and in the professional community. Get a better understanding of
user experience design, service design. There are lots of other fields that are
complimentary to Digital Asset Management that can help you in your role.
[4:00] Also, don’t be afraid to talk to the software developers and other asset
managers. We’re really lucky to be living in an age where the Internet allows you
to easily connect with others who are really far away, so make the most of that.
[4:13] If you’re aspiring to become a DAM professional, I’d say ask yourself, do
you spend your Saturday nights organizing your iTunes catalog or rearranging
your Google+ circles, does the thought of downloading and editing holiday
photos give you a spark of excitement. If so, find yourself a job in Digital Asset
Management right away. Henrik: [4:31] Well, thanks, Michelle. Michelle: [4:32] Thank you very much. Henrik: [4:33] For more on Digital Asset Management, log onto AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, Blubrry, iTunes and the Tech Podcast Network. Thanks again.
How are you involved with Digital Asset Management?
How does a media company focused on cooking 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 Andrew Mannone.
Andrew, how are you? Andrew Mannone: [0:09] I’m good, Henrik. How are you? Henrik: [0:11] Great. Andrew, how are you involved with Digital Asset
Management? Andrew: [0:15] Well, that’s a great question. When I was first hired at America’s
Test Kitchen as an Imaging and Color Specialist, we were really at the beginning
stages of bringing all of our production work in-house for color correction,
proofing. We had some established processes and workflows already, but it was
all rather informal, to a certain extent. Production, my department, is kind of
like the central hub. All of the print projects that my company produces flows
through our department in one way, shape or form, sometimes twice in the life
cycle of a project. [0:54] I was given a really large degree of latitude to completely
rebuild the imaging workflow, from the ground up, which was awesome.
That’s really where I started getting involved in Digital Asset Management,
especially in how we think of it today at the company.
[1:15] Ever since then, production has established itself as the go to place for
anything that the company needs, in terms of retouching, compositing, silhouetting,
proofing, anything prepress, and, of course, Digital Asset Management.
[1:32] Since that time I have a new role at the company as the Workflow and
Asset Manager. Primarily, my goal now is to develop and support the workflows
for the existing products and publications that we have, but all the new initiatives,
the kind the business picks up, whether it be some sort of online social
media initiative or whatever.
[1:59] Like a lot of other publishers, a component of our business model revolves
around repurposing content. In America’s Test Kitchen, we’ve got some,
what I would describe as, unique challenges, one individual image of a plate of
food. That image might have, through its life cycle of going through different
products, up to six to seven output color modes, based on whatever the requirements
are for that publication it appears in.
[2:31] Our job in production is to be able to track all of those assets, where they
came from, what app that they were dragged from, where they were used, back
to the source digital negative file, whenever we need to create a new output
color space. Henrik: [2:48] Just to clarify, when you mean outputs do you mean prints versus
web versus other? Andrew: [2:53] Yeah, exactly. Our flagship magazine “Cook’s Illustrated” relies
heavily on duo tones. Whereas some of our other magazines or books use
quad tones in addition to standard CMYK full color images. Then of course, the
web has its own requirements. To support all of that we had to come up with a
metadata driven automated work flow that not only ties desktop applications
together, but ties together our DAM system. Henrik: [3:21] How does a media company focused on cooking use Digital
Asset Management? Andrew: [3:26] We think about what it is that we do. We’ve got not only our
TV shows, our magazines, our books, and our online websites. We all generate
images and design layouts, PDFs. We need a way to track it all. We use DAM
as a two prong approach. There’s the repository quality of it, storage of our
finished assets. [3:52] There’s also a work flow component of it. That’s really my
focus on DAM. Is using DAM as work flow from the start of an asset’s life cycle
all the way to it goes into the repository side of DAM. When we started using
our DAM system we ultimately decided to go with Cumulus, put out by Canto. It
threw us for a loop at first.
[4:18] We approached it thinking it was an out of the box solution ready to go,
kind of like Adobe Bridge but with a big database backend. After a while it
was like, “Something’s not right here.” Then I started to realize that it’s not just
an out of the box solution. What we got when we chose our system was really
a platform.
[4:46] That’s when the real power of what we got was fully realized. My favorite
way to explain Cumulus to people not familiar with DAM or some other departments
is to think of it like a Lego set. A Lego set for that really awesome
medieval castle, but you threw out the directions. You’ve got all the pieces
there, but you need to figure out how they fit together to build that castle.
[5:14] It will take a while but it’s a puzzle that you have to solve. Once we got the
hang of it, that’s when really good things started to happen. It falls into one of
two categories for what I’ve been trying to use our DAM systems for. Solving a
workload problem or to better communicate information to a user.
[5:35] There are some simple things that you can do on the web front ends,
tweaking the CSS to convey the company branding so it has a consistent look
and feel across all of the different other online systems that we have at our company.
Presenting information to the user in a way that makes sense. Like if you’re
searching for various recipes.
[6:00] Are the recipe elements grouped in a logical fashion? Recipe name is a
part of a book chapter, what’s the book project name? Then there’s the work
flow component. Sometimes it’s really simple things like Cumulus will capture all
of the excess information from the digital camera but it doesn’t always render it
in a completely human consumable way.
[6:25] For example, exposure mode. It renders it as an integer and in most imaging
applications, you would see something like aperture priority, or auto exposure,
but in Cumulus it shows up as zero. I wrote a really simple formula to parse
the integer into an auto exposure. It’s simple things like that that give more
context to the information that’s already there.
[6:58] It helps the user interpret what they’re seeing when they’re viewing the
various records in the DAM. When it comes to solving a work flow problem, a
lot of what I do is getting Cumulus and Photoshop to talk to each other. Most
DAMs have some sort of way or method to convert asset X format into asset Y. I
need this JPEG into a PNG. Most of the times that’s fine.
[7:28] For us, it’s not as sophisticated as we need it to be, because our publications
have some really not mainstream print outputs. Like duo tones or quad
tones. We need to harness Photoshop to get everything the way we need it for
a particular publication. I was able to use the tools that Cumulus provides and
some scripting to select images in Cumulus, route them to Photoshop, process
them based on metadata that’s embedded in the image, then save out the
result and catalog it back into Cumulus.
[8:11] That lets us track where an image has been, what other output mode it’s
come from very easily. Henrik: [8:19] You mentioned earlier that you didn’t have the instructions for the
castle but you were able to build your own castle. Andrew: [8:28] I’ll wager to bet that another user using the exact same DAM,
it won’t look anything like what we built here at ATK. We’ve got tons of formula
fields that pull information out of a file path to display a project name and a lot
of nomenclature that’s specific to America’s Test Kitchen. When people first
start their eyes glaze over because we have so many acronyms that we throw
around. [9:01] We joke that we can talk in complete acronyms and have it make
perfect sense to the people in the know. We’ve incorporated that into our DAM.
It’s familiar to the people who have been here. One of the other things we were
able to do is now that more than ever cross media publishing is important, it’s
just growing exponentially.
[9:28] We needed to rewrite our web CMS and our internal web development
team rewrote the CMS that drives all of our websites and we took that opportunity
to integrate our Cumulus DAM into the CMS with the web services API.
That has saved countless hours for the web editorial department. Saving off
hours from load times for each magazine content load cycle.
[10:02] That’s actually set us up to do some really great things in regards to the
cloud. I can’t get into details right now, but we’re looking to putting a lot of
assets into the cloud, using the DAM to control who can see what. It’s going to
be exciting. Henrik: [10:23] Sounds like it. What advice would you like to share with DAM
professionals, and people aspiring to become DAM professionals? Andrew: [10:29] I thought about this one for a little bit. It occurred to me, I’ve
been working specifically in DAM for three years, and I still feel like I’m just starting
out. I still feel like I’m in that aspiring to be a DAM professional category,
but I’ve learned a few things. [10:50] Having a natural curiosity is really one of the
requirements to do this type of work. You really need to enjoy solving puzzles,
finding a solution to a challenge, and being detail oriented.
[11:05] Once you get past that, read up on some of the industry standard
groups, like Adobe’s XMP, IPTC, Dublin Core, PRISM XML. These are all really
great resources that you can take and figure out, “What’s the best way to
structure my metadata? Can I use something that’s already existing for developing
my taxonomy, instead of having to start from scratch?”
[11:32] Then learn all you can about XML. Whatever your operating system of
choice is, learn the scripting language that’s native to that platform. We’re an all
Mac shop, so AppleScript is my goto for scripting.
[11:53] We’re doing a lot of web projects now. Cumulus has several web front ends
that we use. JavaScript has become one of those languages that I kind of
knew, but I’m learning a whole lot more of.
[12:09] If you can find any sort of professional organization to connect with, to
find people that are in your field, doing what you do. LinkedIn is a great resource.
If your DAM system has a user forum, get involved on that. I’ve met a
lot of great people and made some really great contacts by participating on the
user forum for Cumulus.
[12:31] Read a lot of books, blogs, whatever you can get your hands on.
[12:36] Have fun. Play with stuff. See what works, what doesn’t. The way I learn
the best is to kick it around, see how it works. Possibly break it, and then try to
put it back together. I was the guy who took apart all their toys as a kid, and it
drove my parents nuts. That’s kind of the way I approach working with DAM,
and it’s panned out so far. Henrik: [13:02] Excellent. Thanks Andrew. Andrew: [13:03] Thanks Henrik. Henrik: [13:05] For more on Digital Asset Management, log on to AnotherDAMblog.com. Thanks again.
How are you involved with Digital Asset Management?
How does a health care 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: This is Another DAM Podcast about Digital Asset
Management. I’m Henrik de Gyor. Today I’m speaking with Carol
Thomas Knipes.
Carol, how are you?
Carol Thomas Knipes: [0:10] I’m doing great. Thank you, Henrik. Henrik: [0:12] Good. Carol, how are you involved with Digital Asset
Management? Carol: [0:15] I’m the administrator of the Digital Asset Management System for
a pharmaceutical agency. Essentially, what that means, I administer but I also
design the workflows around that system, and other digital kind of creative
technology that we have going on at the agency.
[0:33] I not only administer the DAM, I’m also in the situation where I drive the workflows that work with the DAM. So I try to have a more unified digital system that we have here. I administer it, everything down to creating folder structures, the actual system stuff, the
actual server set up, dealing with server updates, any of those issues.
[0:58] Actually banging in there, going command line, and doing a lot of that
stuff. All the way to creating taxonomies and dealing with metadata. Then the
process and workflows around that. Henrik: [1:10] How does a healthcare organization use Digital Asset
Management? Carol: [1:15] For us, it’s this two fold thing. It originally was purchased for two
primary reasons. The first one, was to control licensing that we had on a lot of
images that we get by stock houses that have really specific licensing. Especially
as a health care agency, when we’re releasing files and working with files,
making sure that rights managed art is licensed properly and isn’t used when
it’s not, is particularly important.
[1:45] But also, it serves to actually give us an organizational structure, to be able to be a lot more efficient. It broke down the divisions within different departments. Particularly between production and creative. For us to be able to actually have files moved through the various departments very seamlessly without duplication, ensuring that there are checks and balances for things like art and art licensing, art done at multiple stages.
[2:15] Because of the way the DAM works, it kind of works both as an efficiency
tool and as an asset management tool. Henrik: [2:22] All very important, thanks. What advice would you like to share
with DAM professionals and people aspiring to become DAM professionals? Carol: [2:29] The landscape, at the moment, appears to be shifting a little bit.
I recently went to Henry Stuart, and found out what was going on there. There
seemed to be a lot of things going on at the moment, trying to combine multiple
types of systems, like CRM with DAM with document management. All sorts
of things. The biggest thing is, you have to keep up on what’s going on, without
letting it spiral you into a tailspin of drastically changing what you have. [3:00]
You have to both have the bird’s eye view of what’s going on in your organization,
and how the DAM can help what they’re doing. If you see things along
the way that could help, great. But also realize that everything is changing so
quickly, by the time you go through the processes in your organization to get
buy in on a particular type of technology, it frankly might be out of date. So it
really is a matter of taking a look, picking and choosing your battles as to what
you’re going to do.
[3:30] Then if you’ve got a big enterprise DAM system, try your hardest to find
your change champions and try to find a way to integrate as much of the organization’s
other systems into the workflow dealing with the DAM. Because if you
do that, you’ll not only have a better impression of your DAM, better buy in. But
you also will definitely have a more connected, unified system that you can use
for multiple purposes.
[3:55] That really is it. Keep your eyes open, but also be realistic about what you
really need. Some people call it “shiny ball syndrome”. Don’t look at the pretty
new thing thinking you have to get it. You’ve got to think about what is going to
help your organization. Henrik: [4:12] Thanks, Carol. Carol: [4:14] You’re welcome. Henrik: [4:17] For more on Digital Asset Management, log onto AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, Blubrry, iTunes and the Tech Podcast Network. Thanks again.
Another DAM Podcast 