Watchfolder Tutorial (Azure Function Media Uploaded Trigger)

To add to the new record this tutorial assumes that Media will be used to trigger the watchfolder. If metadata is important, see alternative considerations

Contents

• How it works
  • App Topology
• How it's built
  • Create an Azure storage account
  • Create an Azure function app
  • Program the function app (Sample code)

  • Alternative considerations

How it works

1. To initiate the watch folder, a media file is uploaded to Azure Storage, either by manual upload via the Azure Portal or by using the Azure Storage Explorer 
   If you are looking to upload XML metadata see alternative considerations
   

   Azure portal link

   Azure storage explorer link

2. To create a new record,  An event trigger will pick up on the new media file and will send a REST call to the Imagen API 
   

   Azure event trigger link

   Imagen API link

3. Finally: Media is then added to the new record using the media path that has been defined in the generated XML 
   

   Imagen XML link

    

App Topology

How it's built

1. First, to listen for new events we need to create an Azure storage account
   Microsoft guide link
   
   Can't see the guide below? Open it in a new tab ↗ (may not work when viewing this page in SharePoint)

   If SharePoint blocks the link, copy this address and paste it into a new browser tab:

   https://scribehow.com/embed/Storage_Account_creation_tutorial__WLb4f2v4Sne0UCY3W8ydvQ?as=scrollable&removeLogo=true
2. To handle the event we then need to create a new function app to handle the event
   Microsoft guide link
   

    

   Can't see the guide below? Open it in a new tab ↗ (may not work when viewing this page in SharePoint)

   If SharePoint blocks the link, copy this address and paste it into a new browser tab:

   https://scribehow.com/embed/Creating_an_Azure_Function_App__K3mv6FPFS8iQSvLv9WGoWg?as=scrollable&removeLogo=true

    

3. To create a trigger for your function app follow the tutorial below
   
   
   

   ⚡Pro Tip: The Image below shows the integration of our Function App. It's worth noting that the entire Input blob is loaded into memory, allowing us to send the input blob as the body of our REST call.  This is fine for XML files, but media is better suited to an event grid trigger. Media watchfolder link

    

4. Create a SAS token
5. To program the Function App to create records in Imagen simply follow the guide below

    

    

   Can't see the guide below? Open it in a new tab ↗ (may not work when viewing this page in SharePoint)

   If SharePoint blocks the link, copy this address and paste it into a new browser tab:

   https://scribehow.com/embed/Azure_Function_code_tutorial__BeN8d0rNSKuCK0oLEp_uLA?as=scrollable&removeLogo=true
   
   

   Sample code

   function.json

   {
       "bindings": [
           {
               "name": "InputBlob",
               "type": "blobTrigger",
               "direction": "in",
               "path": "xmlblobcreatedtrigger/{name}",
               "connection": "xmllandingzone_STORAGE"
           }
       ]
   }

   run.ps1

   ####################################################
   ### Input bindings are passed in via param block ###
   ####################################################
   param([byte[]] $InputBlob, $TriggerMetadata)
   
   ###############################################################
   ### Write out the blob name and size to the information log ###
   ###############################################################
   Write-Host "PowerShell Blob trigger function Processed blob! Name: $($TriggerMetadata.Name) Size: $($InputBlob.Length) bytes"
   
   #####################
   ### GET FILE NAME ###
   #####################
   $filename = $TriggerMetadata.Name
   Write-Host "Blob has been created: $filename"
   
   ##################
   ### Set params ###
   ##################
   $apiKey = '[Your API Key]'
   $bearer = '[Your bearer token]'
   
   $headers     = @{"X-Imagen-API-Key"="$apiKey";"Authorization"="Bearer $bearer"}
   $contentType = "text/xml;charset=utf-8"
   $workflow    = "[Your workfow here]"
   
   ######################
   ### Set media type ###
   #############################################
   ### [Video]. [Image], [Audio], [Document] ###
   #############################################
   $mediaType   = "[Media type here]"
   
   #######################
   ### Set REST params ###
   #######################
   $restparams = @{
       Uri         = "https://[MCC Server].cloudapp.azure.com:83/imcc/v1/import/record/NativeImagenXML?workflow=$workflow"
       Headers     = $headers
       Method      = 'PUT'
       Body        = $InputBlob
       ContentType = "text/xml;charset=utf-8"
       SslProtocol = 'Tls12'
   } # end rest params
   
   try{
       $restOutput=Invoke-RestMethod @restparams -skipcertificatecheck
       $restResponse1=$restOutput.Response.DatabaseJob.InnerText
       Write-Host "REST CALL try: $restResponse1"
   }catch{
       Write-Host "REST call failed because: $_"
   }

6. Test the watchfolder

   The final step is to check that the expected outcome has been achieved

Alternative considerations

Azure storage

If media is a trigger:

1. XML arrival in Azure triggers a blob creation event. Media is ingested from HTTP(s) URL and stored in Azure

2. Media & XML arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in Azure

3. Media arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in Azure

Wasabi storage

1. XML arrival in Azure triggers a blob event. HTTP(s) Ingest. Media is stored in Wasabi
2. Media & XML arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in Wasabi

3. Media arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in Wasabi

AWS storage

1. XML arrival in Azure triggers a blob creation event. HTTP(s) Ingest. Media is tored in AWS
2. Media & XML arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in AWS
3. Media arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in AWS
   

   ---

   Dump

   
   

   Media & XML arrival in Azure triggers a blob creation event. Media is ingested from the blob in the landing area. The media is then stored in Azure