This article has multiple issues. Please help talk page. (Learn how and when to remove these template messages) or discuss these issues on the(Learn how and when to remove this template message)
Digital photographs, animations, videos and music exemplify the target areas. Digital asset management systems (DAMS) include computer software and hardware systems that aid in the process of digital asset management.
The term "digital asset management" (DAM) also refers to the protocol for downloading, renaming, backing up, rating, grouping, archiving, optimizing, maintaining, thinning, and exporting files or other binary data.
The efficiency of above mentioned protocols could be ensured through a structured taxonomy.
The "media asset management" (MAM) sub-category of digital asset management mainly[quantify] addresses audio, video and other media content. The more recent[when?] concept of enterprise content management (ECM) often deals with solutions which address similar features but in a wider range of industries or applications.
Smaller DAM systems are easier to categorize as to content and usage since they normally operate in a particular operational context. This would hold true for systems attached to audio or video production systems. The key differentiators here are the type of decoders and I/O (input/output) used for the asset ingest, use and outgest. Since metadata describes the essence (and proxy copies), the metadata can serve as a guide to the playout decoders, transcoders, and channels as well as an input to access control rules. This means that the essence can be treated as a non-described storage object except when being accessed for viewing or editing. There is relevance to this when considering the overall design and use of larger implementations. The closer the asset is to the ingest/edit/playout tool, the greater the technical architecture needs to accommodate delivery requirements such as bandwidth, latency, capacity, access control, availability of resources, etc. The further the asset moves into a general storage architecture (e.g. hierarchical storage management [HSM]) the more it can be treated as a general blob (binary large object) that is typically held in the filesystem, not the database. The impact of this set of needs means that it is possible and reasonable to design larger systems using smaller, more expensive performance-systems at the edge of the network where the essence is being used in its intended form and less expensive systems further back for storage and archival. This type of design exemplifies Infrastructure Convergence Architecture, where the line-of-business operations technology and IT technologies depend on one another for functional and performance (non-functional) requirements.
Generally the "asset" being managed is collected and stored in a digital format. There is usually a target version - referred to as "essence" - generally the highest-resolution and highest-fidelity representation. The asset is detailed by its metadata. Metadata is the description of the asset and the description depth can vary depending on the needs of the system, designer, or user. Metadata can describe, but is not limited to, the description of: asset content (what is in the package?); the means of encoding/decoding (e.g. JPEG, tar, MPEG 2); provenance (history to point of capture); ownership; rights of access; as well as many others. There exist some predefined standards and template for metadata such as Dublin Core and PBCore. In cases of systems that contain large-size asset essences, such as MPEG 2 and JPEG2000 for the cases of images and video, there are usually related "proxy" copies of the essence. A proxy copy is a lower-resolution representation of the essence that can be used as a reference in order to reduce the overall bandwidth requirements of the DAM system infrastructure. It can be generated and retained at the time of ingestion of the asset simultaneous or subsequent to the essence, or it can be generated on the fly using transcoders.
DAM software may be open source or proprietary.
||This section may be in need of reorganization to comply with Wikipedia's layout guidelines. (January 2013) (Learn how and when to remove this template message)|
||This "see also" section may contain an excessive number of suggestions. Please ensure that only the most relevant links are given, that they are not red links, and that any links are not already in this article. (January 2016) (Learn how and when to remove this template message)|
Manage research, learning and skills at defaultLogic. Create an account using LinkedIn or facebook to manage and organize your IT knowledge. defaultLogic works like a shopping cart for information -- helping you to save, discuss and share.