Jake Jaroch and Ryan Messier discuss Digital Asset Management
Here are the questions asked:
How are you involved with Digital Asset Management?
Why does an organization focused on motorcycles use a DAM?
What are the biggest challenges and successes with Digital Asset Management?
What advice would like to give to 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 Jake Jaroch and
Ryan Messier. How are you? Jake Jaroch: [0:12] Good. How you doing? Henrik: [0:13] Good. How are you involved with Digital Asset Management? Jake: [0:16] I oversee our photography department, art studio, and I oversee
our Digital Asset Management System. The way I’m tied to Digital Asset
Management System is I do more of the long-term planning and the functionality
for the system. Ryan does more of the day-to-day, hands on operations support of the system. Ryan Messier: [0:35] I handle the day-to-day operation for the DAM and support
the system from the admin side. I also handle requests from different
stakeholders, both internally and externally for the company. Any projects that
come across the table from an asset management standpoint is my responsibility
to take care of. Henrik: [0:52] Why does an organization focused on motorcycles use a Digital
Asset Management System? Jake: [0:56] Believe it or not, we have about 170,000 in assets in our system. We
have assets sent to us from other departments within the company, for instance,
our motor clothes which aim with our clothing line, our parts and accessories,
our retail environment group, marketing, communications, our HDM, which has
derived our archival, imagery and video. So we’re actually getting fed a lot
of assets from the company and it allows us to reuse the assets in other areas of
the company, therefore saving us a lot of money. Henrik: [1:36] What are the biggest successes and challenges with Digital Asset
Management? Jake: [1:40] I think some of our bigger challenges is with the DAM system, for
extracting from the system search, our metadata, training our stakeholders how
to use the system. We have such a custom vocabulary here at Harley Davidson.
For instance, we have some of our miles are named Dyna, Touring, Softail, so
these are kind of unique names. For instance, Touring might mean something
else to somebody outside of this company. Therefore our search was very complicated.
It was hard to use a synonym dictionary. Ryan: [2:15] The synonym dictionary that we had to establish, would optimize
our search and it was just difficult to establish that taxonomy because it is so
unique to a company. Jake: [2:24] Then another challenge that we faced was selling our leadership on
actually investing money into the system. It’s very hard for leadership to see the
value in something that they are not getting a return on, or a hard number of
return on. It costs us a lot of money, a lot of time, a lot of resources, the implications
of using assets without rights, all these things cost the company money.
[2:49] If we have all that information in the DAM system and we’re able to reuse
the assets, we’re able to save the company money. It was very difficult to sell
that to leadership. Henrik: [2:59] From my understanding, it’s basically a soft cost savings. You’re
not selling things directly from the Digital Asset Management system. Is that
fair to say? Jake: [3:07] Yes. That’s exactly right. Henrik: [3:08] Good. It does save you time likely in search, provided it works
well, to save the amount of time it would take if there wasn’t a system in place to
find those 170 some thousand or however many assets you have til they understand
that point. Jake: [3:21] Right. I’ve run some numbers. I said before that they’re soft numbers,
so it’s really hard to come up with the actual number. We save the company
hundreds of thousands of dollars every year by reusing assets and by
having the rights on all of our assets. [3:35] The successes of the DAM system
are pretty much the same thing. Exactly what I was saying was one of our most
difficult things, selling this, was actually probably one of our most biggest successes.
We were able to sell it to leadership, they bought into it, and they stuck
a lot of money into it. Ryan: [3:50] The system itself is a great success. Our old system that we used
years ago was very difficult to navigate and very difficult to use. Users had a
hard time getting the assets that they actually needed. This new site has vastly
improved the general user-ship, and everybody has received it quite well. [4:09]
That was a huge project that Jake took on over the last three years. I came on
two years ago, and I’ve been running the day-to-day since then. That was a big
success basically, just from a company standpoint. Henrik: [4:19] What advice would you like share with DAM professionals and
people who are aspiring to become DAM professional? Jake: [4:24] I would tell them to run. Henrik: [laughter] [4:27] Jake: [4:28] Run while they can. No. I’m just kidding. It is a very difficult field to
be in though. You’re basically a pioneer. DAM has been around for a while, but
still it’s not perfect. [4:40] It’s a very difficult world to be in, and it feels like you’re
only one. As stupid as that may sound, it’s like nobody speaks your language.
It’s very difficult to find a friend in the DAM world, if you will. Henrik: [4:53] I’ve heard that many times, honestly. Jake: [4:56] You really need to be organized. You have to have thick skin to be
in this profession. I don’t want to turn anybody off by going down this path,
because it is very rewarding, but it is difficult. In a sense, it is kind of fun being a
pioneer and going down this path that most wouldn’t dare travel. Henrik: [5:18] It’s definitely exciting, one way or another. Ryan: [5:22] Playing off of that pioneer analogy, most people, when you tell
them that you’re a DAM Asset Manager or something along those lines, they
don’t know what you’re talking about. Even, for instance, my family really don’t
have an idea of what I do. But knowing that you accomplish such a grand accomplishment
for the company or whoever you work for.
Jake: [5:44] It is the truth. I wouldn’t change what I do in the DAM world. But
looking back at the last six years that I’ve been involved with the DAM here at
the company, it has been very challenging to break down those walls and those
barriers of bringing the DAM system to the company. Henrik: [6:01] You’re implementing change management across the organization
of how they’re managing their people, processes, technology, and information.
I totally value your candor and honesty on those points. Thanks, guys. Ryan: [6:11] Thank you. Jake: [6:12] Thank you. Henrik: [6:13] For more on this and other Digital Asset Management topics, log
onto AnotherDAMblog.com. Another DAM Podcast is available on Audioboom
and iTunes. If you have any comments or questions, please feel free to email me
at AnotherDAMblog@gmail.com. Thanks again.
How are you involved with Digital Asset Management?
I understand your organization focuses on end-to-end signal transmission solutions, what does that mean to customers?
How does an organization focused on end-to-end signal transmission solutions 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 am Henrik de Gyor. Today I am speaking with Lincoln Howell.
Lincoln, how are you? Lincoln Howell: [0:09] I am doing well, thanks. Henrik: [0:11] Lincoln, how are you involved with Digital Asset Management? Lincoln: [0:14] I have helped lead the implementation of our current Digital
Asset Management solution, and essentially have two ongoing responsibilities
with it. The first is driving improvements to both the content and the delivery of
those assets. But second of all, I am one of our global administrators. So I provide
some of that administrative oversight to rights management and any ongoing
proposed structural improvements. Henrik: [0:36] Lincoln, I understand your organization focuses on end-to-end
signal transmission solutions. What does that mean to customers? Lincoln: [0:42] We live in a world that is filled with signals. You have audio signals,
video signals, data signals, every time we get onto the Internet. These signals
all require an infrastructure of copper, fiber and other networking solutions
to help get them from that point of origin to each of us as a consumer. [1:05]
Now, I work with Belden Incorporated, and Belden provides that infrastructure
that enables those signals to go from that starting point to the ending point.
[1:14] For example, each time you watch a sports event on TV that originates
down on a field somewhere with somebody working the camera. In between
that camera and your television is a whole network of fiber solutions, copper
solutions, networking switches and routers. All of that processes that signal, the
audio and visual signal from the field to your living room. That’s the infrastructure
that’s enabled by these Belden solutions.
[1:46] Additionally, data centers, every time that you’re working with Internet
solutions or cloud based applications, data centers run solutions, also, that
can be provided by Belden on the copper, fiber and other solutions within the
data center.
[2:02] Manufacturing, also, has a significant play within the signal transmission.
Automotive manufacturers, for example, will use robotics, machinery and all
sorts of equipment that requires an interconnectedness that relies on copper,
fiber solutions to keep them running, communicating with each other and
achieving the outputs of that factory.
[2:26] In the end, the Belden copper, fiber and networking solutions make it possible
for all of these signals to get from where they start to where they need to
be and keep the world running. Henrik: [2:37] How does an organization focused on end-to-end signal transmission
solutions use Digital Asset Management? Lincoln: [2:45] Building an end-to-end solution with signal transmission has
taken years of growth through a combination of both research and development
as well as some strategic acquisitions. This ongoing journey has resulted in a
very complex organization. [3:00] That complexity is showing up in sells graphs
of varying responsibilities and skillsets, engineering and product management
teams that are scattered across the globe, and marketing staff, too, that are
tasked with consolidating all of the individual components of the signal transmission
solution to a single coherent message for the customers.
[3:18] In the end, without Digital Asset Management, we find ourselves constantly
reinventing the wheel or missing opportunities to win customers by
leveraging materials that we’ve already invested. Our first phase with Digital
Asset Management has been to make significant improvement in our customer
engagement.
[3:34] We’ve been consolidating our assets that can be used in the interaction
with the customer, and we’ve been striving to make them easily accessible
across the globe, opening up channels for sharing these assets across all of the
geographies and across all of these functional themes.
[3:49] Our second phase with the Digital Asset Management is going to be
turning towards more of an internal implementation, where we use it to facilitate
the distribution of corporate standards, other policies and other HR
communications. Henrik: [4:02] What advice would you like to share with DAM professionals and
people aspiring to become DAM professionals? Lincoln: [4:06] I think it’s all about the taxonomy. What we’ve found here is that
you can consolidate digital assets on any server. That’s not the hard part. It’s
the retrieval and the consumption of those assets that’s the real goal. You need
those to be consumed by the right people at the right time. [4:25] What was
learned is that setting up and sustaining, sustaining being the key of successful
taxonomy, makes all the difference in the world. That taxonomy is just comprised
of intuitive categories, tagging, and the metadata that really makes your
asset library searchable by its users. Without that taxonomy, it becomes more of
a frustration than a solution.
[4:48] In order to set that up, we found that it’s not just having that technical
competence, being able to understand the system. But it really requires a
keen organizational eye and a lot of people skills. Because as you have various
people participating in and contributing to your digital asset library, you’ve got
to have a lot of one-on-one interactions with them, to insure that standard work
is followed and to insure that that organizational structure, that taxonomy, stays
intact. Because, once again, without that taxonomy, all you’ve got it a pile of
assets on a server somewhere.
[5:21] What you really need is a clean library that people can easily find what
they’re looking for at their fingertips. Henrik: [5:28] Thanks, Lincoln. Lincoln: [5:29] You bet. Henrik: [5:30] For more on this and other Digital Asset Management topics, log
on to AnotherDAMblog.com. Another DAM Podcast is available on Audioboom, iTunes and the Tech Podcast Network. If you have any comments or questions,
please feel free to email me at AnotherDAMblog@gmail.com. Thanks again.
How are you involved with Digital Asset Management?
How do open source Digital Asset Management (DAM) solutions stack up today?
What advice would you like to share with DAM Professionals and people aspiring to become DAM Professionals?
Transcript:
Henrik de Gyor: [0:02] This is Another DAM Podcast about Digital Asset
Management. I’m Henrik de Gyor. Today I’m speaking with Joe Bachana. Joe,
how are you? Joe Bachana: [0:11] Great. Hi. Henrik: [0:12] Joe, how are you involved with Digital Asset Management? Joe: [0:16] Personally, I’ve been implementing Digital Asset Management since
about 1997. My first project with DAM was when I was working with a company
called Image, Inc. I was implementing a product called Phrasea, which was a
French-based solution. I had way back then experienced implementing products
like MediaBank. North Plains TeleScope I had implemented at a number
of locations around that time, as well. [0:42] I founded DPCI, which is a technology
company that implements content solutions. I founded that in ‘99. We’ve
been doing Digital Asset Management projects ever since with a wide variety of
Digital Asset Management products for a whole variety of use cases, as well. Henrik: [0:58] How do open source Digital Asset Management or DAM solutions
stack up today? Joe: [1:04] We have to look at them in a few different ways. The first is the
business of open source DAM. The second, you would have to look at the legal
underpinnings of those solutions. The third would be the technology. Some
people say, “Let’s take a look at the technology real quickly first,” but I think
that’s a mistake. [1:22] One of the reasons why we look at the business is that
the open source DAM projects are very different from the open source Web content management solutions out there. The CMSs such as WordPress, Drupal, Joomla, or Plone are principally anywhere between a very large collection of
contributors globally to those projects to maybe a little more modest contributor
base.
[1:48] Generally, it’s anywhere between a few hundred people and thousands
and thousands of people contributing to the innovations of these open source
projects, so they’ve taken firm foothold into the rubric or fabric of not only
our country but globally, the way Web content management innovations are
happening.
[2:06] In the case of Digital Asset Management, not as much. You do have solutions
that have been created out of Europe, out of the UK, and here in the
United States that there are a couple of folks that are working on it that are
friends or colleagues, or you’ll have companies that are behind the products
with their own resources. The solutions themselves haven’t necessarily taken
root as global initiatives.
[2:35] That doesn’t mean it’s not going that way. You’re starting to see more of
what happened 10 to 12 years ago in the CMS world starting to happen in the
DAM world. The reason why it’s not going to happen as rapidly is, to me, Digital
Asset Management is a little bit like the plumbing in your and my walls. It’s nice
when it’s working, but it’s not the sexiest thing in the world.
[2:57] The thing that everybody cares about is how nice does your house look.
It’s like the CMS. The CMS is the presentation of your content as well as the
ways in which you develop your content the workflows and so forth. Obviously,
no CMS is created equal. Joe: [3:13] With respect to DAM, companies principally use Digital Asset
Management systems for archive and retrieval of their assets. That’s a simplified
notion of what DAM should do. Both you and I both know there’s a
huge number of reasons people implement DAM, ranging from selling content
through storefronts to integrating DAMs with CMSs, CRMs, or ERPs
and so forth.
[3:38] In the case of media companies where they’re selling their content,
whether it’s through rich media like video or live streaming, these things obviously
are the core of their business. It’s not just about archival. It’s about real
work in progress and delivering that content across multiple channels.
[3:57] The pace of innovation in the open source world from a business standpoint
is certainly not as rapid yet. It’s not as sexy.
[4:06] There’s one project that we’re involved with for a media company. They’re
headquartered here in New York City. They had been veterans of a couple of
different proprietary platforms. They had spent millions on a couple of different
solutions. They made a determination that they were going to try an open
source implementation. They are doing a good amount of work to having us do
some cool customizations for them to add on top of the open source solution.
[4:34] The question always is…What we like to do in open source is, we like to
contribute back to the community, however small or big it is. Hence, we oftentimes
will go to that customer and say, “As a precursor to our signing on,
do you have any objections to us contributing these solutions out in an open
source way?”
[4:53] That gets to the business aspect of it. The other part of the business
aspect of it is operationalizing DAM. For companies that have had experience
with proprietary vendors, some of the vendors have 24/7 support. Some of
them, not so much.
The DAM vendors can be smaller companies in some cases, so they don’t necessarily
have the resources. When you have a president of a company answering
the phone at 11: [5:07] 00 at night to support you, that’s generally not a good
sign, although some of the presidents of these DAM companies are absolute
geniuses. It’s always a pleasure to talk to some of them. But it isn’t a scalable
model. Operationalizing maintenance and support, it’s something that some
of the proprietary vendors don’t do that well. But if you look at it in the CMS
world, when you think about the kind of services you can get out of an Acquia
and Drupal, which is commercial support.
[5:44] There are other alternatives on that side, as well. Those types of things
aren’t necessarily fully hammered out yet in the open source world. Because
businesses behind the open source DAM projects are sometimes not matured
yet. They may be smaller groups. So that’s going to change over time. The
second point was this notion of the legalistic implications of open source. Not all
open source is created equal or licensed equally.
[6:11] You’ve got different licensing schemes out there. A very common one is
the GNU GPL. You hear about that one a lot in the web CMS world. In DAM,
quite a number of them take advantage of the lesser GPL, LGPL, which has
some limitations. These things people have to really reflect on, when they’re getting involved.
Do they want to do an open source implementation where there may be some restrictions.
Joe: [6:37] I also look at these products… Does the company who is creating
it, are they paying lip service to open source? But then you start to think, “Do
they have all their documentation out there online? Can you readily download
and install that product?” If you’re really open source, you’ve got to behave like
open source, which to me means freely downloadable and installing, and freely
available documentation.
[7:01] Then it’s your prerogative to decide whether you want to purchase services
from a company or whichever individual. The legalistic application of it
is quite important when people are reflecting on open source. Now we get to
the technical. This is the one everybody really concentrates on first. People ask
me, “Don’t even look at the products if you can’t first look and see what the
business and the legal implications are of the solution you’re about to go forward
with.”
[7:29] The open source DAMs are approaching, in general, the work group functionalities
of products out there, in the marketplace. If you look at solutions like
Resource Space or Enter Media, Rezuna as well. There are a couple more, I’m
not trying to plug these products, simply giving it as examples that these solutions
are starting to meet the needs of work group, Digital Asset Management,
which would be considered, for me, the ability to import, either individually or
batch, a whole variety of digital asset types.
[8:08] And on ingestion, to be able to automate the creation of thumbnails and
previews and even evoke certain recipes for conversion of the assets. If you,
upload a PSD or any PS file, then you can set up recipes for conversion to JPEG s
at certain widths and depths. The ability to also capture metadata information.
Things aren’t all created equally, but the ability to capture XMP metadata, for
example, is something that is available in several of these products.
[8:38] In one case, we actually did some customizations where we have some
preprocessing of assets within Adobe Bridge for a customer. Then the assets
are going into their open source DAM. It’s a phenomenal thing, because they’re batch modifying with some extended XMP metadata, with their own panel within their Adobe Creative Suite products. And then that information is getting
ingested into those open source DAMs.
[9:06] These kinds of basic functionalities are available. It’s really exciting, because
they’re there. We’ve actually implemented quite a number of these kinds
of projects. They’re working. For a year or two years, they’re in business, in
use. The other thing that I find really exciting is that the whole promise of open source, to me, is you don’t have to say, “Mother, may I?” The whole idea of innovate and ingenuity in software, the open source software world is the ability to just step up and say, “I want to create something of value that’s available or
that I need for the context I need it.” Joe: [9:45] Without saying, “Hey, may I please do that?” And then somebody saying, “Yeah sure. But pay $20,000 for an SDK and sign this agreement that you won’t do this or that.” With open source, you can do it. A couple of the
open source products have robust web services and published APIs that, essentially,
allow you to do anything you want, ranging from connecting the DAM
to a produce like Drupal or WordPress, or connecting it to your CRM, if that’s
what you needed, and so on. That, to me, is the most exciting aspect. In one
case, we did a project down in Atlanta for a company where they had this huge
infrastructure. They needed to just automate the production of real estate guide books. Joe: [10:31] So we have this integration of, in that case it was a product called EnterMedia, with believe it or not, a whole Microsoft infrastructure. Integrated
with Adobe Live Cycle, integrated with Data Plan Journal Designer. And integrated,
I’ll add, with the InDesign server. So the whole infrastructure is automating
the pagination of these real estate books, straight from sales folks just
entering the data on the individual homes that are going to be offered.
[11:02] This content is being used to create both the web listings, as well as the
print catalog books or guide books that are being done in multiple states. It’s saving hundreds of thousands of dollars in their production processes. The DAM is an underlying technology within the architecture. It works flawlessly and it’s
open source. They save themselves… If you think about the amount of money
they spent on the other infrastructure. [laughs]
[11:28] They spent a fraction of their budget on the actual DAM implementation.
There’s a lot you can do with open source DAM solutions as underlying architectural
decisions for larger projects. And for very modest use cases around
archival and retrieval of assets you absolutely can use those types of solutions in
your business. Henrik: [11:54] What advice would you like to share with DAM professionals and
people aspiring to become DAM professionals? Joe: [11:59] That’s a great question and I appreciate it, Henrik. A lot of folks
come into this industry… I should add, I’ve been doing this type of thing for
26 years now. I’m not going to count my tech jobs while I was in college,
which principally were around content technologies. But 26 years ago, content
technologies were a whole different animal. To me, there’s a lot of folks that
enter the market and they want to be DAM professionals and they want to get
jobs doing this. [12:28] My concern has been folks coming out there and never
having laid their hands on a single product, without having done a single implementation.
There’s a lot of information that goes on and a lot of folks that are…
There’s no certification for becoming a DAM professional or a DAM analyst or
consultant. Yet people go out there and help folks with RPs and so forth, and
they’ve never done a DAM project.
[12:54] To me, if you’re right out of college, first of all, there’s some colleges which actually have some programs, like RIT, the print management school.
They have a course in Digital Asset Management. It is modest. But they give
people a chance to understand how to configure. What are the important use
cases trying to be solved in DAM? Getting hands-on experience with DAM is
really important. Even if you never will touch the technology in your career and
you want to be a pundit or someone who’s just a thought leader, you’ve got to
be able to touch them and understand what these types of products, this class
of products, do.
[13:33] What problems do they solve? That’s just me. Other people would probably
emphatically disagree. But I don’t think, going back to the plumber motif
that I said earlier or concept, you can speak with authority about plumbing
if you’ve never laid in the pipes an understand what the heck goes on there.
I certainly don’t understand what’s happening behind the walls. That’s one
thing. The second is, the best, to me, really exciting folks out there are the folks
who’ve gone to library science school.
[14:05] They really fundamentally understand what information science or information
architecture is. How do you define a taxonomy? What is an ontology?
How do you create controlled vocabularies? What’s that process? Sometimes
folks that were in data modeling are very good at that, as well. They’re very
thoughtful. A lot of times we go in as professionals and over engineer the
model, the information architecture of a platform.
[14:35] That becomes onerous for the folks who are trying to capture that metadata
and track it. There has to be a reasonableness that goes on, which again,
goes back to point number one. Which is, try to become a practitioner. But,
understanding that these are human systems, that’s the third thing. Again, we
talk about first laying your hands on these types of things, second is understand
how taxonomy is laid out. If you have money to go to library science school or, if
not, pick up some books on it.
[15:04] There’s some great resources out there for that. The third thing is understanding the use cases or the workflows. Because the DAM systems don’t necessary do workflow really well. But every single person or any company that’s
creating, managing, enriching and delivering assets has implicit workflows.
Some that are simple. Some that are very complex. Until you really understand
what those are, you’re going to be hampered. Joe: [15:34] I’m talking about not just people starting out in their career, but folks
that are 10, 15, 20 years in, that are delivering Digital Asset Management implementations.
A lot of times they don’t pay attention to the ways people interact
with assets through the life cycle. Different asset or content types have different workflows.
The way you’re creating an interactive object is going to be different
from some sort of an image file or video file and so forth.
[16:02] Those have different ways of being manipulated through a whole class of
employee types or user types. So understanding those is really important. Once
you get those you’re going to be more sensitive to the way people work. The
fourth thing is, understand how to listen and understand how people currently
work, meeting them halfway. Just coming in and implementing a DAM and
saying, “This is the way it works,” isn’t good enough.
[16:32] To be able to understand how an organization needs to work is important.
To hopefully deliver a DAM solution that supports that work and bolsters
and improves it, as opposed to makes people change the way they work, which
invariably, as you and I both know, doesn’t work. People rebel. You get into all
kinds of change management issues where folks just fight the DAM implementation.
I want to just end on this note, that a good way to inform your career
in DAM is that everybody high fives themselves when the DAM installation is
completed.
[17:09] But the way you test the success of a DAM solution is two to three years
out. How many people are using it? How many assets are there? Is it supporting
the business? Has duplication of assets been minimized or eliminated? Are there
issues with finding assets that were thrown in two years before, that are important?
That’s the way you test. You always have to think forward in this business.
Think about the results you’re going to be creating, two to three years in. Henrik: [17:38] Thanks, Joe. Joe: [17:40] Cool. Henrik: [17:41] For more on this and other Digital Asset Management topics,
log onto AnotherDAMblog.com. Another DAM Podcast is available on AudioBoom, iTunes and the Tech Podcast Network. If you have any comments or
questions, please feel free to email me at AnotherDAMblog@gmail.com.
Thanks again.
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.
Another DAM Podcast 