Digital Asset Management Systems (DAM)

From MODwiki

Navigation Shortcuts

• MODwiki Table of Contents (Main Page)

---

---

Contents 1 Overview 1.1 Defining a Digital Asset 1.2 Managing Digital Assets 1.3 COPE 1.4 Who Is Involved In Digital Asset Management 1.5 Facilities, Hardware & Software Supporting Digital Asset Management 1.6 Support Personnel for Digital Asset Management 1.7 Desirable Features for a Digital Asset Management System 2 Resources

[edit] Overview

[edit] Defining a Digital Asset

A Digital Asset may be broadly defined as any video or video segment, audio clip, office document, image, map, chart, 3-D image, diagram, flowchart, web site, learning object or interactive multimedia object. These files and documents may be targeted for internal consumption and distribution within institutions or organizations, or for publishing to external communities, such as outside institutions, schools, educators, homes, or libraries. Although paper, hard copy, magnetic or optical media are forms in which assets may be generated and stored, the Digital Assets that are proliferating today originate in a computerized, digital format or are converted into a variety of digital architectures and files. Assets that remain in "non-file-based" forms, such as videotapes, audiotapes, DVDs, CD-ROMs, or hard copy, may be indexed in asset management systems but be referenced with locater information to point to the physical storage location of an item, e.g., barcoded tapes on vault shelves or publications housed in stacks.

A Digital Asset has two components:

1. Essence

The essence is the actual “thing,” whether it is videotape, DVD, document, audiotape or CD, analog or digital file. The essence is what a user actually views, plays, reads, or listens to.

2. Metadata

In order to facilitate the discovery, retrieval, and sharing of an asset, it must be described. Think of the traditional card catalog system in a library as metadata stored by subject and author. Think of metadata as standardized or customized descriptions of the essence, depending on the user community. Media production organizations have specific and unique metadata descriptors. Educators have extended needs that include the utilization of assets within instructional settings. Geographers have different metadata needs than image archivists or art historians. Many custom metadata schemes have been generated to serve these communities. Without metadata, the essence may be lost, stranded and not retrievable.

[edit] Managing Digital Assets

Properly managing digital assets offers widespread or universal access to an organization or institution’s accumulated knowledge base and may offer the added benefits of streamlining internal operations and the flow of information throughout. As information and the forms in which it is stored expand within and across related organizations, the need for managing and publishing such assets increases. Otherwise, the organization risks losing valuable resources, expends more resources to reconstruct what already existed, misses out on new business or service opportunities, or simply mires within its own information generation and overflow.

During the past two decades, many sectors of the academic community have come to recognize the potential benefits of using digital technologies to enhance educational experiences. Universities and school systems are working with public and private organizations across the nation to incorporate multimedia content and electronic interaction in their programs.

The challenge today is to organize and focus these efforts into meaningful projects that will optimize the use of existing on-line educational repositories. On the one hand, there is a bewildering choice and availability of technologies. On the other hand, the amount of available on-line content can be overwhelming. In determining the best application of scarce resources to these projects, a cost-benefits analysis is not enough; it is at least as important to evaluate the qualitative educational and service benefits.

Attaching value to media content is allusive. We can define media content value both monetarily and from an educational perspective.

• DOLLAR VALUE. There are few practical methods for assigning a monetary value to materials in educational repositories. Even though revenue production is not the primary objective of educational institutions, the difficulties in determining the financial worth of their educational assets interferes with their ability to make informed decisions about the appropriate repurposing, reuse and replacement of these assets. Variables that define the dollar value of assets include acquisition costs, creation and production costs, promotional costs, and long-term storage costs; all of these have various assumptions attached to them. Additionally, an analysis consumer demand for stored assets may be used to determine dollar value.
• EDUCATIONAL SERVICE VALUE. Determining the intrinsic worth of a media asset for educational purposes is akin to asking, “How long is a string?” or "How much is lunch?" The answer depends on many factors (such as "What is on the menu?") that require identification and analysis.

[edit] COPE

An overarching objective of any Digital Asset Management System is to encourage and implement the concept of “COPE.” Although the acronym has various interpretations, we shall define COPE as “Create Once, Peruse (or Play) Everywhere,” regardless of format or user (internal to the organization or external). The desire is to expend the resources in personnel, facilities, and materials only once in the original creation of a video or audio program, a document, an image, or a rich media file. Afterwards, the source material can be discovered, reformatted, repurposed, and reused by others in situations other than the item’s initial, intended purpose. The assumption is that the value of the original item can be rolled over many times, thus increasing the return on the original investments.

[edit] Who Is Involved In Digital Asset Management

In terms of creating assets, there are graphic artists, camera operators, audio operators, media directors and producers who design, development and generate original materials. In educational venues, teachers, professors and students also generate content directly related to the learning objectives at hand.

In terms of harvesting and procuring existing assets, there are buyers, content specialists, gatekeepers, purchasing committees, and vetting professionals who evaluate, select, buy and license content…either through direct purchases or subscription services.

In terms of migrating assets into a management system, there may be teams of individuals who facilitate the inventory of, ingestion, metadata cataloging, file conversion, file transcoding, and storage of assets.

In terms of distributing and publishing assets, there are computer network administrators, IT professionals, Database Managers and World Wide Web Site designers and programmers who make it possible for others to search, retrieve and view assets. Distribution systems must be robust, reliable, and scalable as expansion of asset repositories is undertaken. The type of interface attached to these distribution systems should be customized to meet the needs and perspectives of individual communities of users, i.e., K-12 educators, higher education faculty, media producers, librarians, students and researchers.

In terms of end users internal to an organization, there are staff, HR personnel, producers, marketing and creative service groups, legal departments, accounting departments, managers, and executive directors who may access the knowledge base and Digital Assets of an organization in order to facilitate work or generate business and services. Each organization has unique arrays of departments, divisions, and missions.

In terms of external end users, there are customers, clients, related organizations, businesses, non-profits, and the educational and consumer markets that access information through extended distribution channels (broadcast, Internet, in-hand media). External access to an organization’s assets requires extensions to the infrastructure and security protocols for a Digital Asset Management System.

[edit] Facilities, Hardware & Software Supporting Digital Asset Management

Several different configurations of audio-visual and computer equipment are required to build and run a Digital Asset Management System. Much infrastructure is required to simply manage the procurement and conversion of assets for publishing, not to mention the storage required to house the various versions of digital assets and their associated metadata. Other equipment is needed for archival, legacy and backup. Still other servers are required to mirror the media and metadata generated internally by an organization so that external users can freely search, browse, and retrieve assets from the system without interrupting or interfering with the internal servers.

The following list identifies representative facilities and hardware configurations, many of which may already exist within an organization. These may be called upon to multitask for Digital Asset Management functions; they may need to be improved and expanded to meet the rigor of a DAM System.

FACILITIES & HARDWARE

1. Storage/Servers

a. Inactive, Legacy Archival Storage of Media

Media which is no longer required for production workflow or media conversion may be relegated to offline, archival storage.

b. Backup and Recovery Storage

Drives and servers that can backup data for security and recovery are not just a good idea, but essential to the service and business and mission functions of an organization.

c. On-line Storage Solutions for DAM Development and Access (Centralized)

While assets are being ingested, converted, and marked up with descriptive metadata, an organization needs on-line storage solutions for developing collections and repositories. These servers are most likely separate for the media essence versus the associated metadata (database server). Users internal to the organization have access to these storage devices.

d. Distributed Storage Solutions

For convenience and efficiency, media and its metadata may be stored on redundant servers distributed outside the core organization, such as in schools, institutions and branch offices. These servers may be mirrors of the centralized servers or may be On-Demand servers that receive media and metadata from user requests over the Internet or through the Datacast Bursts available through Digital Television broadcasts.

e. Specialized Storage Solutions

One example that can be cited is the “playout” systems used by broadcasters in order to distribute their programming. In light of the Advanced Television Standards (ATSC or Digital TV), such playout systems include multicasts of different video streams as well as datacasting of information, web pages, data, communications and Digital Assets. Specialized file servers connected to scheduling, traffic operations, satellite feeds and master control facilities are required to service a broadcaster’s mission and needs.

2. Web & Application Servers (some servers are capable of multiple functionality)

a. Web Server for User Access to the system

b. Database Server housing Asset Metadata

c. Application Server for the DAM System

d. Specialized Functionality Server(s) for optional modules handling office documents, image file transcoding, etc.

3. Work Stations

a. Conversion Station for Images, Multimedia, Rich Media and Documents

b. Ingestion & Digital Conversion Station for Video and Audio Assets

c. Ingestion and Digital Conversion Station for Supplementary Media Analysis

d. DVD Authoring & Burning Station

e. Metadata Markup Work Station

f. Various DAM System Client Work Stations

SOFTWARE

1. Graphics/Image Read/Write

2. Graphics/Image Conversion

3. Text/Document Read/Write

4. Text/Document Conversion

5. Multimedia Read/Write

6. Multimedia Conversion

7. Video/Audio Ingestion

8. Video/Audio Editing

9. Video/Audio Conversion & Compression

10. Audio/Speech to Text Conversion

11. Closed Caption to Open Caption Conversion

12. DVD Authoring Software and MPEG-2 Conversion

13. Digital Asset Management Software

a. TCP/IP client/server architecture

b. Cross platform client software

c. Check-In/Check-Out Version Control

d. Distribute catalogs + assets on CDs & DVDs

e. URL central asset storage (ftp and http)

f. Administrative and Office document archiving and management

g. Publish and market digital assets to the web

h. Database connectors

i. Metadata markup

14. Data backup and recovery software

15. Web server utility

16. Database (such as Oracle or Sybase)

[edit] Support Personnel for Digital Asset Management

Depending on the organization, there may already exist staff generating content and Digital Assets or procuring them for further distribution. Television and Radio stations have Programming and Production departments. Educational institutions have media purchasing agents or committees. Libraries have acquisition specialists and cataloging professionals.

New roles are played by a special team of individuals who actually introduce assets to a DAM management system, manage the service, and create extended distribution channels for the assets. Depending on the organization and its mandates, roles may be performed by separate individuals, by one individual fulfilling several roles, or by individuals already fulfilling similar roles within the organization.

• 1. Team Leader or Chief Digital Asset Accountant

Supervises the entire process of Digital Asset management. Achieves consensus amongst all participating stakeholders, parties and players regarding asset inventory, selection criteria, procurement, and workflow patterns and adjustments. Coordinates each step of the Digital Asset management service, including inventory, ingestion, cataloging/indexing, storage, posting, distribution, archiving, and collections management. Acts as liaison to all staff and stakeholders generating and retrieving assets from the management system.

• 2. Media Procurement Specialist

Depending on an organization and its codependent institutions and departments, the type of media and the methods used to obtain that media will vary. In some cases, media items are designed and created as original, custom assets. The production of documents, graphics, images, photographs, audio programs, video programs, and rich media objects are examples. In other cases, media items are obtained from outside vendors, suppliers and publishing houses for further classification and distribution to interested or vested communities. When obtaining media from other suppliers, the assets may be outright purchased, licensed for specific time periods and methods of distribution, or be part of a larger subscription service that provides vast numbers of ready-made items, both long form and short form/segmented.

• 3. Video/Audio Ingestion Specialist for Time-based Media

Handles, digitizes and conforms video and audio source materials. Conducts actual digitization and ingestion processes, having a keen familiarization with digital video and audio formats, media conversion and transcoding, and data rates. Assets are prepared for CD, DVD, Analog Video and Audio, Digital Video and Audio Production, and Internet compatibility/streaming/downloading. For Digital TV broadcasters, this individual may also conform media to be carried as part of the DTV signal transmissions.

• 4. Image, Multimedia & Rich Media Conversion Specialist

Handles, digitizes and conforms all manner of image formats, both analog and digital. Handles and conforms various multimedia objects, learning objects, rich media files, or activities and experiences programmed in Flash, Authorware, Director, HTML, Java, I-Shell, Interactive QuickTime, MPEG-4 interactive layers, etc.

• 5. Document Conversion Specialist

Handles, digitizes and conforms all manner of word processing, spreadsheet, and other text and office documents that are to be included in a Digital Asset management system. Converts documents to Acrobat PDF file format whenever possible for indexing and posting. (Note: depending on the DAM system purchased, some solutions offer automatic conversion utilities to PDF file format)

• 6. Librarian/Catalog Information and Metadata Specialist (Cyberian)

Responsible for entry and integrity of metadata and all asset descriptions added to the metadata database and the DAM system selected to manage all assets. Skills include dealing with metadata regardless of content discipline or asset utilization, subject control of descriptors and their database fields, compulsivity, and tenacity in collecting metadata from asset creators, producers, contributors and suppliers.

• 7. Database Administrator

Responsible for maintaining and managing the core database behind the asset management system.

• 8. Network Administrator

Responsible for ensuring content can be delivered over an organization’s LAN, WAN, or Intranet. Maintains and upgrades the LAN, WAN or Intranet.

• 9. Media Storage Administrator

Responsible for the installation and maintenance of whatever storage devices and servers are used to house and distribute the Digital Assets both within the organization and external to the organization via other distributed servers.

• 10. Internet and Web Server Administrator

Responsible for maintaining and managing the web server(s) used to deliver the user interface to internal and external users who are searching for, retrieving, viewing and downloading Digital Assets.

• 11. Web Designer/Programmer

Either an individual or team specializing in the design and programming of World Wide Web sites and interfaces capable of delivering Digital Assets and their metadata to users internal and external to the organization. Depending on the DAM solution implemented, customized user interfaces and branding are features built into the software functionality.

• 12. Stakeholders

The managers, supervisors and directors whose divisions and departments are stakeholders in the use of the Digital Asset management system and the delivery of those assets to various user communities.

[edit] Desirable Features for a Digital Asset Management System

Properly managed digital assets offer universal access to an organization's knowledge base and can streamline internal and external operations, services, and information flow. As information and the forms in which it is stored expands within and across related organizations, the need for managing and distributing these assets increases. Otherwise, the organization risks losing valuable resources, expends more resources to reconstruct what already existed, misses out on new business or service opportunities, or simply mires within its own information generation and overflow.

There are desirable features that any asset management and workflow system should embrace or offer.

• 1. Inventory of Existing Assets and Archives

If the stakeholders decide that existing assets, media or document archives are a top priority for harvesting and inclusion in a DAM System, then a method for conducting an inventory of media and related files must be undertaken. Ideally, the DAM System can facilitate the inventory process. However, if an inventory must precede the implementation of a DAM System, then whatever tracking methods and data accummulation that occur must be able to crosswalk or import into the selected DAM System at the appropriate time. XML data sharing is desirable.

• 2. Selection Criteria

Before any item is introduced to an asset management system, an organization must establish its criteria for the selection and harvesting of assets to digitize and distribute. These criteria will vary, depending on the organization's mission and objectives. Based on the number of players invested in the creation and deployment of an asset management system, there may be complementary and conflicting selection criteria to be identified and negotiated. Nevertheless, if the selection criteria are well defined, then the entire asset management system can be better planned, not only in its initial implementation, but also for future scalability, extensibility, and capability.

• 3. Organizational and Communication Workflow

An organization must carefully examine and articulate its standard operating procedures in the procurement, generation, conversion, and dissemination of its knowledge base and assets. With the implementation of a DAM System, traditional methods of working and communication between departments and organizations may undergo adjustment. Traditional areas of responsibility and organization charts may require new "dotted" lines to be superimposed over established structures and pre-conceived missions. A DAM System should be able to facilitate workflow enhancements within the organization, yielding efficiencies and cost savings.

• 4. Asset Ingestion

Depending on the type of asset, it must be ingested as some form of digital file by the asset management system. Various mechanisms and methods should be in place in order to accommodate video and audio clips, documents, images or multimedia objects. These systems may be autonomous ingestion hardware/software suites, but with data sharing hooks into the centralized asset management system. The Virage SmartEncoder and Media Analysis Plug-ins are examples of tool sets designed for the ingestion and transcoding of time-based media. Sophisticated DAM Systems accommodate either manual ingestion and uploading of individual assets or batch processing of many assets and collections at one (unattended) session.

• 5. Transformation Services

  Broadbased File Transcoding

Components can be added to a basic DAM System which accommodate batch processing of files as they are transcoded into multiple file formats and architectures for perusal and playback on any computer, any browser.

• 6. Office Document Management Module

Components can be added to a basic DAM System that accommodate the ingestion, metadata markup, searching and retrieval of typical office documents, such as Microsoft Word Processing, Spreadsheets (XCEL), and PowerPoint. This feature adds a much-needed and powerful tool for managing hundreds, even thousands of office documents related to normal business processes as well as documents that complement other media assets in the repository.

• 7. Description & Cataloging of Assets

  Metadata Markup

An asset (essence) that is created, but not cataloged or indexed, is an asset with diminished value. The original creator may recall the purpose of the analog source or its digital derivative, but through time and attrition of personnel, the asset is forgotten and its content banished to obscurity. Fortunately, a Digital Asset Management System is designed to accommodate metadata, or descriptive information about the original asset. Through a database operating in the background, each asset is catalogued and assigned descriptors. This process insures each asset is indexed and retrievable by users other than the original creator. It is desirable that both default and customized metadata elements with controlled vocabularies can be created within a particular DAM system. It is also desirable that the “objective attributes” of individual time-based and non-time-based assets, such as file format, size, duration, dimensions, tracks, etc., can be automatically attached as metadata. Many DAM Systems have this facility.

Various metadata dictionaries and schemes can be employed and integrated into a DAM System. There are many to choose from depending on an organization’s mission and needs, the needs of its “customers,” and the purpose and objectives of implementing a Digital Asset Management System. In general, most metadata schemes use various descriptive “elements” that can be grouped into four categories:

a. Subject Descriptors: Elements related to the intellectual or interpretive content of an asset (often termed “subjective metadata”).

b. Property Rights Descriptors: Elements related to the copyright, use restrictions and terms-of-use for an asset across its life-cycle.

c. Instantiation Descriptors: Elements that identify and define the media formats and physical attributes of an asset in both its analog and digital incarnations and derivatives.

d. Utilization Descriptors: Elements that share how a Digital Asset is best used or incorporated into a learning environment, utilization scenario, situation, or session. Such descriptors may also associate an asset with specific learning objectives or established curriculum standards for educators.

• 8. Collect More Metadata than the End Users Interact With

Simplistic DAM Systems exist which show the same metadata entered by catalogers in its original form to end users who are searching and retrieving assets. The needs of metadata databases and the needs of end users are not the same. Ensuring the accuracy and completeness of metadata entered into a DAM System requires data entry screens and data fields that no ordinary end user would ever want to see. Catalogers and database administrators relish these data entry requirements. End users usually are befuddled by the structure and terminologies used. Consequently, a good DAM System presents one set of metadata to catalogers, but concatenates, collapses and massages this information into simpler forms and functions for end users.

• 9. Data Crosswalk Capable

It is inevitable that a single über DAM System cannot be specified and implemented for all stakeholders and eventual partners who wish to exploit a Digital Asset Management System through the University of Utah, the public broadcasting stations, Utah Education Network, University Office of Information Technology, and the Utah Public School Systems. Therefore, depending on the systems and sub-systems that are implemented, it is necessary that metadata and assets can be crosswalked from one system to the other. Or at the very least, one system can search another via portals or other system integration.

• 10. Discovery, Retrieval, Evaluation, View

A Digital Asset management system helps users find existing content by creating a centralized, easily accessed repository of content. Through database search and retrieval capabilities, assets can be evaluated, researched, browsed, viewed, repurposed and shared through standard World Wide Web interfaces. Different communities of users should have customized user interfaces (metaviews) that are tailored to their information needs. Many DAM Systems have the facility to allow customization and branding.

• 11 Compound Objects & Related Assets

A much-needed feature of a DAM System and the metadata used to describe the assets in the repository is the ability to associate one asset with another related asset. These assets complement each other, and together make a complete experience for an end user. Consequently, the ability to craft compound objects of related assets is very desirable.

• 12. Derivative Works

  Detachment & Repurpose

In extended applications of Digital Asset Management Systems, users can detach the original asset and repurpose it in new forms, plans, presentations and projects. Detachment may imply electronic sales of Digital Assets. It may also allow end users to freely extract an asset from the centralized storage repository and download it to their personal computer storage devices. Detachment and repurposing may also mean that derivative works may be created from the original assets, either through built-in tools sets or through other third party software options. Additionally, a DAM system should accommodate order intake and order fulfillment processes for derivative formats of the original asset that cannot be delivered digitally, such as CD-ROMs, CD-Audio discs, videotapes, and DVD-Videodiscs.

• 13. Stock Footage and Still Image Resale

A component of a DAM System allows other media producers or parties to search, peruse, and order/buy stock footage, clips and still images for which we have rights or wish to recoup original investment costs.

• 14. Simple URL Denotations for Assets

It is preferred that media assets and attendant metadata, though accessible through DAM System Clients, can also be resolved as simple URLs that can be pasted into any HTML aware document, thus linking Assets through a vast array of user interfaces and existing web-based portals. Online courseware delivery tools, such as Web-CT and BlackBoard are able to place a simple URL link within their HTML-based pages to access the assets of a Digital Asset Management System.

• 15. Version Control & Check-In/Out Monitoring

Many DAM Systems have the ability to track who is checking out an asset for reversioning, when it is checked back in, and which versions of an asset are designed for which distribution purpose or usage period.

• 16. Direct Asset Modification

If an asset is checked-out by a user who needs to update or change an asset, it is desirable that the DAM user interface will directly open an asset in its native application (if loaded on the end users computer). An example would be an image file that can be opened and editing directly within Adobe Photoshop.

• 17. Notifications for Administrators or Users

Depending on the activity undertaken by a user or system administrator, a notification system (such as e-mail) should automatically inform appropriate parties about actions taken with assets or conditions of the System itself.

• 18. End-User Upload of New Assets

Depending on the environment, it may be desirable for end-users to have the capability to upload original and new assets generated locally to the centralized DAM System. With a vetting and approval process in place, uploaded assets may become part of the permanent collections. For educational communities, the facility to create, then upload new assets encourages local buy-in for the system and an embracing of the DAM concept of widespread sharing or resources.

• 19. Protected and Proprietary Collections

Depending upon the number and types of contributors who use or access a Digital Asset Management System, certain collections of assets may be deemed proprietary. In such cases an asset management system must be able to restrict or limit access to designated collections to key individuals or original contributors via password protection or pre-designated IP address ranges.

• 20. Local Suppression for Access to Questionable Collections & Assets

Based on the selection criteria and procurement processes used to endorse and vet the content made available to various constituencies, communities and customers, a Digital Asset Management System should disallow questionable or rejected assets or collections that would otherwise be readily available. Such assets may be blocked or suppressed from searches, selections, browsing, viewing and download for specific end-users. Metadata that identifies audience appropriateness can facilitate this need, as can properly designated access privileges for Users and Groups.

• 21. Rights Management

Whether an organization creates its own intellectual property or purchases and licenses content from outside vendors and subscription services, there must be accommodation for rights management information in a Digital Asset Management System. Metadata such as copyright dates and ownership, authors, publication dates, and use restrictions should be consistently applied to all candidate assets throughout their creation, distribution and life-cycle.

• 22. Storage Options

The physical storage requirements for digital assets vary. Digital video and audio can consume gigabytes, even terrabytes, of storage space. For these assets, storing their low-resolution proxies and perhaps high quality versions of original sources, requires an investment in large SAN devices (Storage Area Network) or removable media jukeboxes. Of course, information about the location and shelving of the original physical tape or media should be included in the Digital Asset Management System’s metadata structure. As well, a means for enumerating or barcoding the original tapes should be implemented. Other assets, such as images, documents, or multimedia objects, require less storage space and thus can exploit less exotic storage solutions, such as servers with large, fast drives. SAN solutions have proven to be most efficient and cost-effective.

• 23. No BLOBs

Some DAM Systems actually store the metadata and the media assets within the database itself (referred to as BLOBs). We prefer that metadata be stored in a database and media assets be stored elsewhere in centralized repositories or distributed storage options.

• 24. Security Protection

Firewall and security measures need to be in place in order to protect the Core Development Facilities from outside intrusion and invasion. External Facilities need similar security protocols to prevent hacking. As well, the DAM System must have a comprehensive ability to manage Users, Groups, WorkGroups, and their privileges and permissions to different collections and different metaviews of available metadata.

• 25. Scalability

A worthy asset management system must be able to integrate with existing technologies within an organization while also being built on an open architecture that facilitates scaling the management system to new opportunities and new technological horizons. If the system that is originally purchased does not support scalability and extensibility over time and circumstance, then a system rebuild may be called for sooner than an organization expects.

• 26. Backups

An organization may already have a backup and restore system in place. Undoubtedly, such a system would accommodate the database information and incidental data files associated with a DAM System. However, backups of time-based and rich media files may need to be evaluated and purchased; storage requirements can become quite large. Additionally, for those assets that no longer require on-line or near-line storage, a system for archiving assets and metadata at the end of their life-cycles should be implemented.

• 27. Training and Knowledge Transfer

Depending on the needs of the organization, a robust transfer of knowledge about the DAM System and its upgrading needs to be in place. Comprehensive training, both on-site and off-site, should be included in any package that is purchased.

• 28. Annual Support, Maintenance and Upgrades

Most enterprise level DAM Systems will include annual maintenance and upgrades through various support packages, depending on the number of support services offered and the immediacy with which they are delivered and fulfilled.

• 29. Flexible Licensing

Some DAM Systems base licensing on the number of proprietary client packages that are sold and installed within the organization. Others are based on the number of concurrent users accessing the system over web-based, IP connectivity.

• 30. Open Architecture

The DAM System should be based on an open architecture and standards-based protocols (e.g., XML, SOAP, J2EE). Third-party components can be integrated into the system as needed. The system retains its scalability and extensibility over time.

• 31. Cross-Platform Compatibility

The DAM System must be able to perform equally well for searches, perusals, playbacks, downloads and uploads on Windows-based and Mac-based computers using Internet Explorer, Netscape Navigator, Firefox, Apple Safari, or others. Agnostic deployment is preferred.

[edit] Resources

Wikipedia Article on Digital Asset Management

http://en.wikipedia.org/wiki/Digital_asset_management

Intro to Digital Asset Management

Just what is a DAM? (Magan Arthur; 2005-04-30)

http://www.cmswatch.com/Feature/124-DAM-vs.-DM?printable=1

MIC-- Moving Image Collections Cataloging and Metadata Portal discussion on Asset Management Systems

http://mic.imtc.gatech.edu/catalogers_portal/cat_asset.htm

WCET -- Western Coooperative for Educational Telecommunications edu-tools "Learning Object Repository Software Reviews"

http://www.edutools.info/static.jsp?pj=8&page=LOR

WCET -- Learning Object Repository Final Report (September 2005)

http://www.media.utah.edu/wiki_pdf_docs/LOR_Report.pdf

WCET -- Learning Object Repository Software Reviews (September 2005)

http://www.media.utah.edu/wiki_pdf_docs/LOR_Reviews.pdf

WCET -- Learning Object Repository LOR Feature Definitions (September 2005)

http://www.media.utah.edu/wiki_pdf_docs/LOR_Feature_Defs.pdf

WCET -- Learning Object Repository Glossary (September 2005)

http://www.media.utah.edu/wiki_pdf_docs/LOR_Glossary.pdf

WCET -- Learning Object Repository Bibliography (September 2005)

http://www.media.utah.edu/wiki_pdf_docs/LOR_Bibliography.pdf

Artesia Digital Asset Management

http://www.artesia.com/

CONTENTdm Digital Collection Management Software

http://www.dimema.com/

MERLOT -- Multimedia Educational Resource for Learning and Online Teaching

http://www.merlot.org/merlot/index.htm

HarvestRoad -- Federated Digital Repository System

http://www.harvestroad.com/

Interwoven -- MediaBin Digital Asset Management

http://www.interwoven.com/products/dam/

North Plains Systems Digital Asset Management

http://www.northplains.com/

ClearStory Systems -- ActiveMedia Digital Asset Management

http://www.clearstorysystems.com/

Utah Education Network -- eMedia

http://www.uen.org/emedia

Utah Education Network -- CollegeMedia

http://www.uen.org/dms

Utah Education Network -- MediaHub (public)

http://www.uen.org/dms

Gallaudet University Video Library

http://videolibrary.gallaudet.edu/scripts/WebObjects.dll/tsweb (register for a free account)

---

---

Navigation Shortcuts

• MODWiki Table of Contents (Main Page)
• ...go to The University of Utah Office of Information Technology website
• ...go to The University of Utah Media On Demand Committee Minutes & Reports
• A Quickie Wiki Guide to Editing Content