In our last DAM post we just started to share with you the foundation of the DAM model We have explained how to evaluate a DAM system with the 10 core characteristics Among these 10 criteria we will start highlighting one of them this week, the Ingest.
Among these 10 criteria we will start highlighting one of them this week, the Ingest.
DAM system have to demonstrate:
- There are different methods by which digital assets and metadata can be uploaded to the DAM. (file server, FTP, web upload, email, mobile).
- Embedded metadata writing and extraction.
- Bulk / batch actions and ingestion workflows.
Different methods of ingestion are important strategic variables. In our digital lives we all consume and ingest data in ever more personalised ways. So why should DAM be any different? Our first interaction with the DAM is often ingestion. You can be a photographer, a agency, a creative, a brand and but how does this impact the way they ingest content?
Long time ago are the days that FTP (File Transfer Protocol) was considered innovative, nowadays we want drag and drop, cloud access from a mobile app on 4G, we want to link Dropbox or Google Drive to the DAM system so we can search through our written content, we want to use the API to drag in content from the company CMS. This is new way of INGEST.
Without a strategic plan for metadata you will fail to truly reap the benefits of DAM. Without properly marked up content, you will continue to operate a disorganized silo, pay money to reproduce digital assets, your staff will waste time looking for content and you will have little to no control over what happens to your content once it has left the DAM.
Before you ingest a single asset into your DAM be sure to think about how information describing the asset (metadata IPTC – XMP) will be added. Before you ingest a single asset into your DAM be sure to think about how information describing the asset (metadata IPTC – XMP) will be added.
Embedded metadata is fundamental in that information assigned to a digital asset remains with it throughout its lifecycle. Without the ability to embed metadata you can’t really call something a digital asset; it is not an asset to us, merely a file, as useful as any disorganized, hard to find, meaningless file that you might shove into a shared folder or leave on an external hard drive in a drawer. It is more important than just adding a few keywords for SEO.
Metadata is part of the story you want to tell about your content and is the basis on which all successful, mature businesses ensure that important content, digital assets and information are not lost or destroyed. Embedding metadata into digital files is a key feature to check before buying a DAM system.
Conclusion and key points:
- Different ingestion methods is important in order to cater to the differing work practices of your business.
- Ingestion from other software can be a crucial piece of the workflow puzzle and allow you to ‘connect silos’
- Metadata is absolutely critical to any content driven organization (IPTC, XMP, Custom, Taxonomy, facets).
- Embedded metadata is the key to extending a digital asset’s usefulness along its entire lifecycle.
Embedded metadata is more and more used as an automation process, driving workflow, rights management, governance, creative actions and many other downstream processes. Implement a DAM solution is all but just buying another product from the market. This is an Enterprise level strategy with deep intricacies And rely on agileStreams’ experts can contribute to your project success!
Get in touch right now to let us know about your DAM project!