6. Handling video data in Magnolia DAM
Why shouldn't large video data be stored in the DAM?
Capacity and performance limits
Magnolia's Digital Asset Management is optimised for the storage of media such as images, documents and small video files. Large video files, however, can quickly exhaust the capacity of the DAM. These files are often so large that they can affect performance, resulting in longer loading times and increased server load.
Problems with scalability and maintenance
Over time, bloated repositories can cause problems with export and backup. A DAM that is overloaded with large video files can be difficult to maintain. The backup size becomes unwieldy, which can lead to extended downtime during maintenance.
Limited streaming capability
Magnolia CMS is not primarily designed for streaming video content. Streaming videos directly from the DAM can lead to suboptimal user experiences, as the CMS does not support the necessary adjustments (such as adaptive bitrate) for efficient streaming.
Alternatives for storing and streaming video content
Use of dedicated video hosting services
A common practice is to host video files on specialised platforms such as Vimeo, YouTube or AWS Media Services. These services offer optimised solutions for hosting and streaming video, including adaptive streaming technologies that ensure optimal playback quality across different device types and network speeds.
Integration into Magnolia CMS
After uploading the videos to an external platform, you can integrate the URLs or embedded codes of these videos into Magnolia CMS. To do this, either use special content apps or add a field in your existing templates that references this external resource.
Creating a custom module for video management
For larger projects or specific requirements, you can also develop a custom module in Magnolia that provides an interface to your video hosting service. This allows authors to manage videos directly from the Magnolia interface without having to leave the platform.
Automation of workflows
Automate the process of video processing and uploading using scripts or services such as Zapier. This allows videos to be automatically sent to the external host as soon as they are uploaded to Magnolia, making the process seamless for users.
By shifting the storage and streaming of video content to external services, you can avoid the limitations of Magnolia CMS with regard to large media files and still ensure smooth integration and management within your content strategy.
Contact the author