Videos: Customizing The Content Request Form

The Content Request Form is used to invite content providers (filmmakers, distributors or others) to upload their files directly to the appropriate video asset within your Administrative Portal.  It is a unique URL link that is generated and then sent to the content provider.  For information on generating the link, see Adding Video Assets

  1. Overview
  2. Header Logo
  3. Custom Message
  4. Enabling/Disabling Elements
  5. Adding Custom Metadata Fields
  6. DCP Request Integration

1. Overview


The template of the Content Request Form can be customized in a number of ways.  By default it includes a Header Logo; a Custom Message field;  a main video upload option; a trailer upload option; an Artwork section; and a metadata section for collecting the details about the video.   Let's look at a sample here.

Now let's break this down and see where within the Administrative Portal these elements are coming from.


Presented at the top of the Video Request Page, the logo must be uploaded in your Accounts app > Team Profile.


3. Custom Message

Below the logo is an optional area for a custom message, such as a friendly invite or even specific instructions. This message is setup in the OTT area > SETTINGS > CONTENT REQUESTS.  Scroll down on this screen to the "Message to Uploaders" field.


4. Enabling or Disabling Elements

On the same screen, CONTENT REQUESTS, elements can be disabled if it is preferred not to have them, such as: Video; Trailer; Thumbnail image; Poster image; and/or Metadata (aka Video Details).   If any of the elements are disabled, those will simply not appear on the Content Request Form.  


5. Adding Custom Metadata Fields

The metadata fields include standard fields like Release Year, Director(s), etc.   Custom fields can be added to this Content Request Form, if desired.   Navigate to  WATCH PORTAL> CUSTOM FIELDS > and click the "Add a Custom Field" button.   The field can be an Input field, where it is open entry, a Drop Down field with options you define, or a Switch field that is a button that can be toggled on or off.  The field can be made "searchable" in which case patrons online would be able to search for that data.  The field can be made "hidden" in which case that field will not show up with the video details on the watch portal.

If Custom Fields are added they will appear on the Content Request Form in the metadata section for the content provider to fill out, as long as the option "Allow Metadata Entry?" is enabled.


6. DCP Request Integration

If, along with your CineSend OTT account, you have a CineSend Requests account for managing collection of video files for in-person screenings, you will see the option to turn on DCP requests as part of your OTT account's Content Request Form.  If you do not have a CineSend Requerst account, you will not see this option.  In this way, if for example you are doing a hybrid event with both VOD and in-person, you can send just the one request for both files rather than separate requests.

When enabled, a section will be added to your Content Request Form for uploading a DCP folder to the corresponding area inside your Requests account.  If this title does not yet exist in your Requests account, or the title spelling is different, a new record will be created automatically in your Requests account for this DCP upload to receive.


If you have any questions please let us know by contacting festivals@cinesend.com

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.