Imagen professional services can help you to find an automated ingest solution to onboard your content in an efficient and cost-effective way
👩🔬Prerequisite knowledge: ✨None! Here we will guide you through the options available to onboard your content library
Contents
-
Convert an excel spreadsheet to XML
-
XML Watch Folder (Wasabi)
Convert an excel spreadsheet to XML
You have a spreadsheet available outlining your content. Perhaps this is an export from your legacy system. We have a tutorial available on how you can export structured data from excel (XML). Once exported our Record Import Tool can be used to import your library.
We strongly advise adding links to media in this spreadsheet, so our storage servers can grab the media from a publically available HTTP(s) file server. If this is not possible, an Identifier linking media to each record will be advantageous for any automated ingest solutions. For example, a process to iterate through a large number of media files could use a unique filename to tie it to the correct record and trigger media import through our API.
XML Watch folder (Windows)
Watch folders work by monitoring a target location and triggering a process when a new file arrives. As this solution will be deployed on a production server, we recommend using XML to trigger the process - usually transferred to the watch folder via FTP (File Transfer Protocol). This will lessen the impact that transfers will have on the virtual network and the server itself. Media can be transferred from an HTTP(s) file server.
XML Watch folder (Azure Function)
The Azure function watchfolder works in a similar way to the Windows watch folder, but the process is triggered by an upload to an Azure storage account. Media can be uploaded to trigger the process, but we suggest uploading an XML (Sidecar) file, that will create and populate the record with metadata to explain and identify the media. The media can be uploaded alongside this sidecar file.