Lynn Eskenazi, Founder, Global Photo Solutions LLC
Ray Segal, Producer, Ducat Media
Dayna Bealy, Rights Clearance (non-Collection), New York Historical Society
This panel discussion was moderated by Julie C. Maher and Alice Merchant.
In case you missed this NYC DAM Meetup in person or want to review this passionate discussion again, below is the unedited audio recording of this panel discussion (Duration: 74 minutes)
There may be follow-up discussions on this topic. What are your thoughts on this?
Henrik de Gyor: [0:01] This is Another DAM Podcast about Digital Asset Management. I’m Henrik de Gyor. Today I’m speaking with Jay O’Brien.
Jay, how are you?
Jay O’Brien: [0:09] I’m doing great. How are you?
Henrik: [0:10] Great. Jay, how are you involved with Digital Asset Management?
Jay: [0:14] In my role at the Baltimore Ravens, I’m the director of broadcasting and stadium productions. I fell into the Digital Asset Management role here. I started 11 years ago here as an intern, just logging tape, doing tape‑to‑tape editing and logging tape in the…I think it was AVID media logger.
[0:35] I got very good at Digital Asset Management in terms of typing out every single play of every single Ravens’ game. That’s how I became a stickler for asset management and also became a football fan.
[0:47] I say I fell into it, because Digital Asset Management, as I’ve advanced through the Ravens and now I’m in charge of the broadcasting department, we were faced with a situation where we basically had to make a move. The previous system we’re on was at its end of life and it was, of course, going to be a big investment to upgrade.
[1:06] I took on the role of learning as much as I could about all the new asset management systems that were out there. It’s pretty exciting. It’s not something I thought I would be interested in but I’ve been working with some great people at other teams, and with our consulting group that we used to implement this new system that we’re on.
[1:24] I’ve really learned a lot and there are some great people in the field like yourself who’ve been very, I guess, instrumental in helping me to learn as much as I can about this. Now, I wouldn’t in any respect call myself an expert. I’m an intermediate novice in this whole thing and learning more about it every day.
[1:38] Our primary objective here is to create great content. When we made this change, I guess more involved in automating our Digital Asset Management, helped us to get away from the tedious typing out every player’s name and to actually editing content.
Henrik: [1:53] How does a football team use Digital Asset Management?
Jay: [1:57] It’s pretty interesting. For an NFL team, there are actually two different video departments that are using Digital Asset Management for two completely different purposes.
[2:06] We have a coaching video department which is using Digital Asset Management to record every play from practice and every play from the games so that our coaches can then go through to analyze the plays for teaching and to get ready for future opponents and that type of thing.
[2:22] What my department does is more on the entertainment side. We create television shows that air in our local market here in Baltimore and Washington, DC, also on our team’s website and mobile app and iPad app and all that kind of good stuff. Then, we also create all the entertainment at our home games on our big screens and our ancillary video boards.
[2:47] What we’re using Digital Asset Management for is to capture all the footage that we shoot at practice, at games, off the field with our players doing work in the community and that sort of thing. We’re using Digital Asset Management to capture and tag all that media so that it’s very easily searchable for us.
[3:11] You don’t know that you need a shot until you need a shot. We were working on a feature this past season about our old national anthem singer who sang national anthem for the first 18 years of our franchise. We had logged the first game that he sang the national anthem.
[3:29] While you’re logging and tagging that asset, you’re probably thinking to yourself “When am I ever going to need this?” But you eventually do. I’m sure that the people that are for us doing a lot of loggings sometimes are thinking “Wow, they’re never going to use this clip.” Surprisingly, we often do.
[3:45] With a team that’s now in our 20th season of existence like the Baltimore Ravens, we’re getting to the point now where we’re doing a lot of look backs and in‑a‑moment‑in‑time of the most famous plays and players in our history. Without a robust Digital Asset Management system, we wouldn’t be able to create the content and the quality that our fans demand.
Henrik: [4:06] Jay, what are the biggest challenges and successes you’ve seen with Digital Asset Management?
Jay: [4:10] For us, the biggest challenge is, with this new system that we have, we’re utilizing the Levels Beyond Reach engine. But it gives you the chance to create as many metadata fields and as many metadata keywords as you want.
[4:24] That’s the challenge and the success of the new system. You want to be able to search by all sorts of different tags. You also don’t want to create too many that you get bogged down with it or that the tagging process takes such a long time that it becomes not very worthwhile.
[4:43] That was our big challenge with this new system. Now going back in time, before you were able to tag metadata using drop down menus and things like that, everything was manual. You were typing everything out. At least, we were.
[4:58] For example, we had someone logging for us back 10 years ago who spelt a certain player’s name wrong for the entire season and nobody caught it. That’s a big challenge because when we’re searching for that player’s name and we’re thinking, “We know this player had good plays during the year. Why aren’t any of them showing up in our asset manager?” It was all just because of a misspelling.
[5:19] That’s a challenge that we’ve certainly overcome now with this new system where we can easily load an Excel roster of our players and then you type in the first letter or two letters of the player’s name and you move on. This new system has saved us a lot of time.
[5:32] At the same time, when we were first establishing the system and determining what fields and what key words we wanted, I think at first we may have gotten too overly ambitious of creating so many different fields that it was taking longer for the first few weeks of our season to log our games and not less time, which is what we anticipated going into the season.
[5:54] We were logging everything from what color jerseys our players were wearing, what the weather was like. It’s really just trying to be ambitious without being overly so where it’s really costing you time and not saving you time.
Henrik: [6:07] What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?
Jay: [6:12] When we went through the process of choosing a new asset manager, we demoed as many of the new systems as we could. We also spoke with, in our case, other football teams that we knew had made this transition to a new system or teams that we knew were as robust as we are in terms of the amount of content we produce.
[6:33] Reach out to other people. Demoing is great and that was certainly helpful for us to demo every system we could. It was equally important for us to talk to people who have actually used the system, specific to our needs.
[6:46] We talked to some people who were using the system we went with and other systems but whose objectives are different than ours. What system may work for a sports team may not work for somebody who’s doing news programming or something like that.
[7:02] Reach out to as many people as you can who you think would be using the system for similar purposes. In our case, we leaned heavily on our consultant and integrator during the project to have them connect us to other sports leagues and organizations who we knew would be using the system for somewhat similar purposes.
[7:22] As I said before, as much as you can, figure out in advance what types of fields and key words you would like to use and have that all laid out. In our circumstance, we’re still evolving and we’re still adding metadata fields and key words and we’re removing some too. Don’t be afraid to do that and say, “This one is unimportant. We don’t really need this.”
[7:44] Those would be my two pieces of advice. It’s certainly a learning experience. This will be our sixth game of the season coming up. Just now we’re starting to get really into a flow and using the system in a way that is most beneficial to us.
Henrik: [8:00] Thanks, Jay.
Jay: [8:01] Thank you. Anytime.
Henrik: [8:02] For more on this and other Digital Asset Management topics go to anotherdamblog.com. For this and 170 other podcast episodes, go to anotherdampodcast.com. If you have any comments or questions, please feel free to reach out to me at anotherdamblog@gmail.com. Thanks again.
Henrik de Gyor: [0:01] This is Another DAM Podcast about Digital Asset Management. I’m Henrik de Gyor. Today I’m speaking with Jade Jourdan.
Jade, how are you?
Jade Jourdan: [0:11] I’m doing well, thank you. How are you?
Henrik: [0:13] Good. Jade, how are involved with Digital Asset Management?
Jade: [0:17] I work at Edwards Lifesciences, and we’re a medical device company. I’m a Senior Digital Asset Specialist, and every day is focused on our Digital Asset Management. I’m responsible for the DAM structure and ensuring we are collecting all the necessary metadata for searching and making sure that everyone gets assets that they need for their projects.
Henrik: [0:40] How does a medical equipment company specializing in artificial heart valves and hemodynamic monitoring use Digital Asset Management?
Jade: [0:48] Our DAM system must primarily archive our marketing assets, product images, and corporate images. Once projects go through our regulatory approval process, they are uploaded by our creative vendors globally into our DAM system and then assets are processed, metadata tags added for searching, etc.
[1:10] Our DAM system is accessed globally by our regional employees and vendors and once our main creative is completed, our projects are repurposed locally and globally. Each region translates the project into their language, processes it to their regulatory, and then produces it for their marketplace.
Henrik: [1:31] What are the biggest challenges and successes you’ve seen with Digital Asset Management?
Jade: [1:35] Well, we are very successful at having our library organized by individual product groups and functional areas so that images and source files are easily located for individual projects and repurposing existing designs.
[1:49] The challenge is working with a high volume of projects and making sure we receive all of our source files from the many agencies we utilize. So working with their marketing departments which are very busy and getting them to retrieve all of our projects from the agencies that we work with, making sure we have everything in our library.
Henrik: [2:12] What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?
Jade: [2:15] Well, I think DAM is an exciting and growing industry. I’m relatively new to it, four years in, and have learned a lot about it and I think the technology is constantly improving with innovative new ways to accommodate and efficiently store large data assets.
[2:34] Most companies have major digital components that need to be managed and organized for productive workflow and I would encourage people with an interest in becoming a DAM professional to absolutely go for it. It’s an exciting field to get involved in.
Henrik: [2:48] Well, thanks, Jade.
Jade: [2:49] Thank you.
Henrik: [2:49] For more on this and other Digital Asset Management topics, go to anotherDAMblog.com. For this and 170 other podcast episodes, go to anotherDAMpodcast.com. If you have any comments or questions, feel free to email me at anotherdamblog@gmail.com. Thanks again.
Nila Bernstengel discusses Digital Asset Management
Transcript:
Henrik de Gyor: [0:01] This is Another DAM Podcast about Digital Asset Management. I am Henrik de Gyor. Today I’m speaking with Nila Bernstengel.
[0:08] Nila, how are you?
Nila Bernstengel: [0:10] I’m good. How are you today?
Henrik: [0:11] Great. Nila, how are you involved with Digital Asset Management?
Nila: [0:15] I have been involved on the job and also in library school. On the job, I have worked in the DAM field for almost 7 years and digital repositories for about 10 years.
[0:26] I also went to library school. While in library school, I focused on emerging technologies, how to create digital repositories, digital collections and how to implement metadata properly.
[0:38] On the job, I have worked the full cycle of implementing a system and upgrading a system. This generally has entailed creating user files, metadata scrubbing or as I like to call it, “untangling the metadata”.
[0:50] I set standards, cataloging, standards for terminology, create dictionaries and permission sets and also taxonomies. In total, I did everything to bring up a system and release a system.
Henrik: [1:02] How does a nonprofit educational organization use Digital Asset Management?
Nila: [1:06] The main objective was to have a centralized location for the company assets for the purpose of storage access and content distribution. Having a centralized location of assets allowed for the discovery of our assets as well as new collections for the creation of either content or product.
[1:27] Not everyone knew what was being created in the company. People would just ask for assets. They would either come to the Creative Resources Department, or they would just look around on the servers, not realizing there was much, much more out there that they could be using.
[1:43] For this reason, we really brought in a system for the centralization for access. There needed to be a place where everyone could go in, view and download without having to contact us. That means we set up a system that was based on permissions, which was really, really important.
[1:59] This really tied into our content distribution. We wanted a place for people to go in, see everything the company offered them, and nothing that was on there was out of their reach. Everything they see, they could use and we really did that by setting up a system that was centralized and was focused on permission sets.
[2:21] Lastly, the content distribution part. This was key to bringing in a system because prior to this, we were mailing out assets, mailing hard drives, CDs, DVDs, even books in the mail and it became very, very costly and not time efficient.
[2:38] To cut down on that, we brought in a system to have something that was instant for someone to use globally and domestically. The system also allowed for the governance of assets. No more like, “I’m using the logo from 10 years ago”. It was up‑to‑date and current.
Henrik: [2:57] What are the biggest challenges and successes you’ve seen with Digital Asset Management?
Nila: [3:01] One of the biggest challenges I have seen is changing workflow. There are a lot of companies that had the same work flow for decades and all of a sudden we’re asking people to no longer use servers, no longer to use their personal hard drives. We’re asking them to change workflow completely and that was pretty hard because a lot of people resist change, especially when it comes to technology.
[3:24] It was something that was different. They had to think about it differently. It really changed how they retrieved assets.
[3:30] The big selling point was showing them the benefits of a system. All of a sudden, you didn’t have to look for hours for something or that one photograph you were looking for. Now you could go on to one place, just do a simple search and download it and that would always be there.
[3:46] One of the biggest challenges was changing people’s workflow, changing them to move away from a physical to a digital environment. One of the biggest challenges for a system was having a lot of duplicates and a lot of versions.
[4:00] A version would be something like have a master file and then there’s five derivatives and different file formats under it. People really still wanted that and I eliminated that because I really believe that the system has the capability to download file formats, whatever you need it for. That was a big challenge also. It’s just like training people to understand all the capabilities of a system.
[4:26] Another big challenge was naming conventions. I standardized the naming convention for the system and people wanted to make sentence structures out of a name, which believe it or not, really actually affects the search. It was a big thing, standardizing how files are named and how they’re presented to people.
[4:47] One of the biggest successes I’ve heard from an end user was how easy the system was to use, how the learnability was really low. This really communicated to me that it was not only easy, but this was something that they would go back to readily and keep using because it wasn’t complicated. The visual space wasn’t overpopulated. That was really good to hear.
[5:10] I think for the company’s success, the ability to reuse assets was key. This really cut down on costs. It also cut down on time. People could reuse the same assets for many different things, which really helps the company also just save money. It enhanced work flow because it cut down on time also.
Henrik: [5:32] What advice would you like to share with DAM professionals and people aspiring to become DAM professionals?
Nila: [5:36] For people starting out in the field, I would recommend start small, something manageable and then use it as a model to scale up. What I mean by this is get your hands dirty a little bit.
[5:49] There was a couple of systems that people could easily download onto their own devices or machines. OpenRefine is a metadata cleanup program. It allows you to bring in a spreadsheet and really dive into cleaning up metadata and structuring metadata. That’s a really good tool for people to use who are looking to get into this field and also, understand the dynamics of metadata.
[6:14] A couple of systems they could try? I think SharePoint is really good. A lot of people use it. It’s pretty easy. I would really recommend going there. Try to create a collection, apply metadata and try searching. See how it works. See what it visually looks like once you apply metadata to it.
[6:30] Drupal is a system a lot of libraries use. It’s also open source. I recommend trying it. Create some pages, create a collection, apply metadata and then see what it looks like and see how it functions.
[6:42] I think just doing that over and over really clicks and makes people understand how dynamic the system is because we are moving from physical to digital and it’s basically a stratosphere of information that is being linked together.
[6:57] I think hands on is the best I could say for people. There is reading resources for people to supplement doing the hands on. I look at The Accidental Taxonomist quite a bit. I think it’s really great. It’s easy to understand and I think if you join, especially reading and a hands‑on experience, it will make you feel a lot more comfortable going into a company or going into an organization and tackling how to set up a system and how a system works.
[7:25] Another great reading source I also use is Real Story Group. They have great vendor information. They have really great white papers and documentation lists to look at because there is a system for almost everything.
[7:37] Different systems do different things. It breaks apart this idea that there’s just Digital Asset Management. There’s Digital Asset Management for a lot of different content types and a lot of systems gear towards different content types. I do recommend doing some reading and just doing a little bit of research on vendors.
[7:55] For people in the field, I would definitely recommend, even if it’s not possible, to reach out to the vendor of the system you’re using and really give them sky‑high expectations of something you want, because even if they can’t do it, they’re going to remember that and they’re going to probably try to put it into their core systems so it will be part of their system.
[8:17] Something like an example of that was we needed content pools. I needed a way to separate content by permissions without creating new portals. I wanted to use one portal for everybody to go into but not everyone saw the same content. Now that’s easily available in most systems.
[8:35] It’s really great if you really talk to the vendor, if you talk to people. It really advances the system. It advances our work flow, which I think is only beneficial.
[8:44] This is for people already in the field. If you’re creating a DAM team or a team that is going to tackle the DAM system, I really, really recommend having a dynamic from all parts of the company or organization. This means three or four representations of business IT, someone who can organize it, like a librarian and I would recommend having an end user involved in part of the process.
[9:09] IT definitely supports the company. They support the technology, but the business requirements and what the system is geared for and how it will used will come from business, because they are the ones who need to use it and they’re the ones who need this workflow to work for the company.
[9:24] A librarian or someone who can organize it is key. This is definitely a skill set people are trained to do. Organizing digital content is a huge task and there is ways to do it and ways to not do it properly.
[9:39] An end user are the people who are going to be using the system. They’re going to be the ones going into the front end and engaging in the system. They’re going to be searching, downloading. They’re key to how the system and the metadata is applied.
Henrik: [9:54] Thanks, Nila.
Nila: [9:55] Thank you.
Henrik: [9:56] For more on this and other Digital Asset Management topics, go to AnotherDAMblog.com. For this and 170 podcast episodes, go to AnotherDAMpodcast.com. If you have any comments or questions, please feel free to email me at anotherdamblog@gmail.com. Thanks again.