Exchanging assets and metadata across platforms
- PDF / 497,486 Bytes
- 4 Pages / 595 x 765 pts Page_size
- 31 Downloads / 154 Views
Papers Exchanging assets and metadata across platforms Jennifer Binder Since 2000, Jennifer has been involved in the development of digital asset management systems and services. She is the founder of Secure Digital Assets (SDA), a DAM company serving Fortune 1000 companies. SDA develops digital asset management systems (DAM) that archive and manage photos, graphics, audio and video. A central location where employees may Ingest, Search, Re-Purpose and Retrieve Digital Assets they need from any desktop 24/7. SDA’s services enable a company to create integrated content that delivers a clear message consistent with the company’s brand.
Keywords: metadata, SOAP, REST, HTTP, XML, assets, XMP, embed, export, import, multiple platforms Abstract Software is growing as a service leading clients to choose providers based on UI, features and relationships instead of platforms. This is leading to a greater demand for systems to exchange assets on differing platforms. This article focuses on how an asset travels with metadata embedded in the file from one system to another. Journal of Digital Asset Management (2006) 2, 215–218. doi:10.1057/palgrave.dam.3650045
INTRODUCTION As the demand to make workflows more efficient through digital processes grows, two main factors have opened the door to dramatically change the landscape. The ability to easily embed data into an asset at multiple points of the workflow and the ability to exchange assets across platforms have revolutionized workflows. Gathering accurate metadata at the earliest stage by the content creator is simple with the use of Extensible Metadata Platform (XMP). Once the asset moves into a managed digital asset management (DAM) system, a director may edit and embed new data into the file. Once the asset has been posted, it may travel safely across platforms into other systems with the insurance that its data will be there to describe what the asset is and how it can and cannot be used.
CAPTURING METADATA IN ASSETS USING XMP Jennifer Binder CEO, SD Assets, 101 West 23rd St., New York, NY 10011, USA Email: jennifer@sdassets. com
The earlier metadata are embedded digitally into an asset, the better, and it can start with the content creator using XMP. XMP is an Adobe product that is compatible with all Adobe applications. XMP allows for descriptive information to be entered into standardized
© 2006 Palgrave Macmillan Ltd 1743-6540 $30.00
Vol. 2, 5 215–218
fields where creators can add a title, author, description, keywords, copyright notice, headline, instructions and more. As soon as these data are entered into an asset, it becomes a part of that asset and travels with it. XMP automatically picks up the file’s properties like date created, format, resolution, history and more. This is a win-win for all, the content creator is guaranteed credit and explanation of proper copyright usage and the client receives metadata formatted in the file from the get go. This translates into less work for the client and more security for the content creator.
IMPORTING ASSETS INT
Data Loading...
