Architectural Considerations in Digital Asset Management

What is the proper foundation for an enterprise-scale Digital Asset Management (DAM) system? How much of that system should be part of an organizations shared infrastructure and how much should be tailor-made to a specific application? There is no single answer to these questions, but changes in the technology industry are forcing everyonevendors and customers aliketo change their assumptions about how DAM systems will be built. This paper explains how the content-management infrastructure is changing, why that matters to DAM, and what benefits can be derived from leveraging a content infrastructure for DAM. Examples from an enterprise implementation at the University of Michigan illustrate the types of architectural issues and requirements that affect platform choices when selecting a digital asset management system.

Walter, Mark. Gilbane Report (2004). Articles>Content Management>Multimedia

Rich Media Management and Business Agility

Understanding how rich media assets are used by the enterprise, of course, remains the central prerequisite for the enterprise’s ability to capitalize on the deployment of a rich media content management platform. The keys to a successful platform for rich media management include an approach to development based on service-oriented architectures (SOA) and a rich underlying content repository that exposes both the content and its metadata.

Trippe, Bill. Gilbane Report (2004). Articles>Content Management>Multimedia

EventDV.net: In the Studio: Apple Final Cut Server

There’s a lot of mystery and misinformation surrounding Final Cut Server, and I’m going to try to sort that all out for you in this article. You can limit which members of your team can access its contents and what they can do with the contents, including who can make changes and who can only look at it.

Baiser, Ben. Event DV (2008). Articles>Content Management>Multimedia>Final Cut Pro