Presented by Howard Goldstein at the Annual Conference of the Visual Resources Association, April 3rd - April 6th, 2013, in Providence, Rhode Island.
Session #4: Every Asset, Everywhere: Perspectives on Digital Asset Management
ORGANIZER / MODERATOR : Elisa Lanzi, Smith College
PRESENTERS:
Howard Goldstein, HR Goldstein Consulting, Digital Imaging Strategies
Elisa Lanzi, Smith College, Director of Digital Strategies and Services
Noah Richman, SRP Phoenix, Media Librarian
Are you hearing the terms “DAM, Digital Preservation, and Media Repositories” more and more at your institution? As our organizations increasingly depend on digital content for all areas of business, the need for enterprise-wide digital asset management is being expressed loud and clear. While cultural institutions are just beginning to implement systems for managing and preserving assets, other media communities (broadcasting, advertising, publishing, etc.) have broad experience in this area. This session brings together panelists for a multi-point perspective on DAM and its impact on the Visual Resources community. Topics include: Digital Asset Management systems demystified; Metadata, taxonomy and DAM; and Digital Preservation. In addition, an open dialogue on VR and organizational change with DAM will be moderated by Lanzi.
4. Also Known as:
• MAM= Media Asset Management (or Marketing
Asset Management depending on who you ask)- the
Media aspect focuses more on video and audio
assets
• CMS= Content Management System- usually
associated with web site maintenance
• BAM= Brand Asset Management ( see also
Marketing Asset Management)- brand and marketing
material workflows for brochures, ad material, etc.
5. The same yet Different
• All center around assets used for
different uses
• Foundational infrastructure is the
same
• Different workflows
6. D
A
M
• DAM in isolation is merely an
organizational tool.
• The more important aspects
of an implementation are:
Workflow processes and
procedures
Links internally and externally
to other organizational systems
Changes and enhancements to
the business processes around
the use of digital assets
7. D
A
M
How an organization gets from
the need for a digital asset to
the
use of that asset, including the
cataloguing and metadata
tagging of the asset can be a
very complicated path.
8. Thinking about DAM
Implementation
•Re-define stakeholders and re-assess
their workflows and business
processes.
•Optimize efficiencies and create new
opportunities via a digital flowchart.
•Realize the true potential of a DAM
system.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18. TMS Field XMP Path namespace
Creator (concatenated w ;) vrae:work.agent http://www.vraweb.org/vracore4.htm
Title (concatenated w ;) vrae:work.title http://www.vraweb.org/vracore4.htm
Display Date vrae:work.date http://www.vraweb.org/vracore4.htm
style; period vrae:work.stylePeriod http://www.vraweb.org/vracore4.htm
culture; dynasty; reign vrae:work.culturalContext http://www.vraweb.org/vracore4.htm
classification; subclassification; object name vrae:work.worktype http://www.vraweb.org/vracore4.htm
medium vrae:work.material http://www.vraweb.org/vracore4.htm
dimensions vrae:work.measurements http://www.vraweb.org/vracore4.htm
Label Only Label Only Label Only
The Walters Art Museum (Baltimore,
Maryland, United States)
vrae:work.locationRepository http://www.vraweb.org/vracore4.htm
Geography Thes X Ref or, if null then
Geography (concatenated w ;)
vrae:work.locationDiscovery http://www.vraweb.org/vracore4.htm
Current Location Display; The Walters Art
Museum
vrae:work.locationExhibition http://www.vraweb.org/vracore4.htm
Credit Line vrae:work.rights http://www.vraweb.org/vracore4.htm
Description vrae:work.description http://www.vraweb.org/vracore4.htm
department; subject vrae:work.subject http://www.vraweb.org/vracore4.htm
19. TMS Field XMP Path namespace
Caption =
ArtistName, Title, Date, Medium, Dimensions,
The Walters Art Mseum, Credit Line, (Accession
Number)
dc:description http://purl.org/dc/elements/1.1/
ObjectID dc:identifier http://purl.org/dc/elements/1.1/
Department + Classification + SubClassification dc:coverage http://purl.org/dc/elements/1.1/
Curator + Cataloguer dc:contributor http://purl.org/dc/elements/1.1/
The Walters Art Museum, Baltimore, Maryland dc:publisher http://purl.org/dc/elements/1.1/
Creative Commons Attribution-NonCommercial-
ShareAlike 3.0 Unported License.
http://creativecommons.org/licenses/by-nc-sa/3.0/
dc:rights http://purl.org/dc/elements/1.1/
Accession Number dc:source http://purl.org/dc/elements/1.1/
object name + TMS Subject dc:subject http://purl.org/dc/elements/1.1/
Title dc:title http://purl.org/dc/elements/1.1/
DCMI Type Value = "Image" dc:type http://purl.org/dc/elements/1.1/
20. What Makes A DAM
File Structure / Archival Repository
Database
Metadata
Model
Security
Model
Search Engine
Transformation Engine
Business Process Engine
User Interfaces
21. The Building Blocks of
DAM
•Archival Repository- DAM does not generally address
this
•Database- SQL database is the standard
•Security Model- internal security, LDAP, or Active
Directory
•Metadata Model- standard schemas like IPTC, Dublin
Core, as well as customized fields and schemas
•Search Engine- open source or vendor proprietary
•Transformation Engine- open source or proprietary
•User Interface- client application or web-based client
22.
23. Open Source
Pros
• TCO may be lower- no
software license
• Vendor independence,
community-driven, more
choices for support
• Supports open standards
and formats
• Software code is
transparent
Cons
• Free does not mean
inexpensive
• Not as clear a model for
vendor support
• Sustainability of the
software
• May be less secure due to
published code
25. D
A
M
Think Outside The Box!
Research DAM not in relation to products
but in context of what is going on
overall in technology and culture-
Techcrunch: http://www.techcrunch.com
Gigaom: http://www.gigaom.com
ArsTechnica: http://www.arstechnica.com
TED: http://www.ted.com