Drop Folder Configuration in Kaltura

Hello !

In this blog I will explain how you could configure drop folder locally in kaltura and two way of using it

1. Pre-encoded flavor ingestion
2. Add Videos to create different flavors .

Lets us move to configuring the Kaltura and enable drop folder

• Step 1 : Go to Admin console in Kaltura
• Step 2 : Select “configure” from the select action drop box provided in publisher table . it will open a “publisher specific configuration” window which provide different configuration property
• Step 3 : Go to “enable/disable” features and make sure Content Ingestion - Drop Folder/s (config) Content Ingestion - Replace Media / Trimming Content Ingestion - Use of Local Transcoder are checked .
• step 4 : click on config Content Ingestion - Drop Folder/s (config) It will open “drop folder profiles window”
• step 5 . Add publisher id , select local and click on create new , it will open a drop folder configuration window
• step 6. In General provide “Drop Folder Name”
• step 7 . In Ingestion Settings

  a) Conversion Profile Id - conversion profiles in which you want to convert videos added to drop folder

  b) add pattern of file

  c)Add Ingestion source content or xml if you select content it will be always Video files needed to be uploaded in drop folder and if you select xml it will read xml and download video file from the link provided

  d) Content Matching Policy First how content Matching is done : it is done by comparing reference Id of Media Entry and Video file name added of the videos added to drop folders There are three policies in content matching Match Existing or Add as New : if a match doesn’t exist it will add a new entry to content in kaltura Match Existing or keep in folder : if a match doesn’t exist , it will keep the video in drop folder . No action will be taken Add as New : It will be always create a new entry e) Now next is slug regex , It define the matching policy .

   

Now Ingestion source is where you need to configure your drop folder , whether you want it for pre-encoded ingestion or not

Three things you should follow

• Use Content Matching Policy : Match Existing or Keep in folder .

  How it helps ? Consider your drop folder is configured for conversion profile “Demo profile” which contain flavors of name “HD” and “SD” . If both flavors doesn’t exist it will not associate a Media Entry and the video

• The files which will be Uploaded to drop folder have file name ReferenceId_flavorName.ext where ReferenceId will be referenceId of Media Entry to which Match is to be done .

• Left Slug Regex empty : if you kept it empty , it will take Video name and trim the name from first underscore it encounter . so it left with ReferenceId and then it match with the Media Entry having same referenceid

  and if you don’t want pre-encoded ingestion , the slug regex will be /(?P.+)[.]\w{3,}/ .

  It will match considering Video Name is referenceid.fileext . It will took referenceId from Video name by deleting the string from name after first ‘.’ and also deleting the ‘.’ .

At Last profile the local path of you drop folder .

Save and you are done .