Organizations in media and broadcast use media asset management solutions (MAMs) to manage their terabytes, or even petabytes, of data. While each company has its own unique requirements to help decide which media asset management solution to choose, the aspect of file transfer is often overlooked as a feature. As we’ve mentioned in previous blogs, the size of media files is increasing, making them challenging to transfer using traditional methods. These file transfer challenges are now being addressed at the MAM level, to ensure efficient and effective file-based workflows.
Once the files are in the MAM, work can be done on them. The question is, how to ingest them into the MAM? Also once we create a clip or edit a proxy, how do we distribute these files to the intended people and locations?
In terms of ingesting the files into the MAM, some media companies have jumped on board and started using technology and infrastructure they pay for to execute file transfers, while others still ship drives and tapes, which can be costly. These files (which end up on local storage), tapes and drives can then be ingested into a MAM.
Once files are worked on and need to be delivered, they can either be sent using conventional file transfer methods put on a drive or tape and shipped.
Being able to perform these file transfer functions from within the MAM interface offers large time savings as users are now able to ingest a file from their local system or bring in a file from another location into the MAM to work on. In addition, having the ability to do this over the web allows for users to access files even when they are not in the office.
FileCatalyst has a number of tools and features that can help MAMs ingest and distribute files. In addition FileCatalyst offers the ability to accelerate, secure and manage these file transfers. FileCatalyst has APIs that can help tightly integrate file transfer into a MAM.
#1 on 2014-Feb-03 Mon 02:12+-14400