Editing Digital asset management (section)

=== Requirements ===
Assets that require specific technologies to be used in a workflow need to have their bandwidth, latency, and access control requirements considered in the design of the tools that create or store them, as well as in the architecture of the system that distributes and archives them.<ref>{{cite book |author1=Elizabeth Keathley |title=Digital Asset Management: Content Architectures, Project Management, and Creating Order out of Media Chaos |publisher=APress |url=https://books.google.com/books?id=C5mJAwAAQBAJ |year=2014 |isbn=978-1430263777}}</ref>
When assets are not actively being worked on, they can be stored in a DAM in various formats, including as a blob ([[binary large object]] in a [[database]]) or as a file in a standard file system, which is "cheaper" to store than the form needed during operations on them.<ref>{{Cite web |title=What is Digital Asset Management (DAM)? - Artwork Flow |url=https://www.artworkflowhq.com/resources/what-is-digital-asset-management-dam |access-date=2023-02-03 |website=www.artworkflowhq.com |language=en}}</ref> This allows the implementation of large-scale DAM as an assembly of high-performance processing systems within a network with a high-density storage solution at its center.<ref>{{cite book |author1=Diamond, David |title=DAM Survival Guide: Digital Asset Management Initiative Planning |publisher=DAMSurvivalGuide.com |url=https://books.google.com/books?id=5HW_NAEACAAJ |year=2012|isbn=9781478287667 }}</ref>