MediaBeacon grew as an answer to the struggles of the digital asset management (DAM) space. The DAM Bill of Rights was created to put into words the pain points of DAM solutions. It is a demand for paradigm shift that can enable the industry as a whole.
Fill out the brief form to receive the ten-part video series and start learning all about the Digital Asset Management Bill Of Rights.
Get a head start on the series below with Data Should Be Durable.
Old solutions weakly attach metadata, forcing you to move it separately. They force you to understand data export, map fields from one database to another, and import data to make it available. Demand that solutions are standards compliant. Demand that moving a file moves the data.
>>Peter: So Jason, one of the DAM Bill of Rights is durable smart assets. Could you talk a little bit about why that's important and why people should be thinking about that when they're talking about a Digital Asset Management system?
>>Jason: Sure. So you know Digital Asset Management, in general, is all about being able to manage, right? So, it's asset management, and the word management means that you have to make decisions. Decisions require information.
So let me give you an example:
You want to be able to have a project and you might have a picture of a whiteboard, an Excel document, and a picture of a famous actress. The famous actress has been paid quite a lot to be able to be in that product or that shot. The thing is, you need to be able to discreetly manage each one of those pieces. So, that information has to be part of those files. It's called metadata. It's not in the file, it's actually about the file. What you really need to have is the ability to have this information inside the file and strongly attached to it. So as the file goes through the system, it has to carry this data with it. So, it has to be durable and it has to have information about the file. So, it has to be smart, right? So, it's durable and smart. Now, they're couple of other things that you need around that to make it useful.
You need to be able to have the data in a structure that is standardized. So, we need to have an industry standard and we do. MediaBeacon uses XMP, which is kind of RDF, which is kind of XML. Ok, that gobbledygook. That actually just means that we're standard and we have the ability for you to read that data outside of MediaBeacon and it's permanently attached. It needs to be attached to the file, but not be in the filestream. In other words, it has to be able to be attached to the file permanently in the file system and, as it moves around, that data has to go with it. Second of all, it has to be able to have a structure that's flexible because what you want to track might not be what I want to track. So, an example is EXIF. There's a standard called EXIF and it's a metadata standard that competes with XMP, or it's part of XMP now, but it was an original standard. It has "flash did fire." So "flash did fire" doesn't make a lot of sense if I opened it and created it from Photoshop, right? So the flash didn't fire, it did fire... I don't know because it never occurred, because it's a virtual thing. So, it doesn't make sense to track it. You can't dictate what the fields are. So, flexible fields and then it has to be in multiple languages because a lot of the original metadata standards weren't flexible enough to have metadata in different languages. So, that was kind of traumatic. So, you're like as long as it's English, it's great.
>>Peter: (Smirking) But you're saying there are other languages.
>>Jason: There are, in fact, other languages.
>>Peter: Got ya.
>>Jason: So, the important part is that it has to be durable, attached to the assets, move with it. It has to be flexible namespace and it has to change, and I can't dictate to you what it is, and it has to be in multiple languages.
So that's why durable smart assets are so important. And that's why that's a core principle around the Digital Asset Management Bill of Rights and why it's a fundamental principle in everything we do at MediaBeacon.
>>Peter: Great, thanks.