MRSS Feed Requirements!

 Ingesting videos into the Platform using an MRSS feed requires you to comply with our default .xslt transformation file.

Note: Although this is not preferred, if your feed does use custom attributes, please provide us with your custom mapping .xslt transformation file. For further details, please see the 'Transformation Url' field under step 12 of How to create an MRSS feed

 

Required Parameters

The following table describes the metadata attributes that are required to create a valid MRSS feed using the system:

Note: Metadata attribute tags that are marked with a * are self-closing tags. All other tags required to have an appropriate closing tag, for example: <media:title>The title</media:title>.

Name Metadata Attribute Description Example
Title <media:title> Used to enter the title of the particular video. (We prefer titles to be capitalized in AP Style)
<media:title> Obama Honors Veterans at New Memorial</media:title>
Description <media:description> Used to enter a description for a video.  This is typically 2-3 sentences describing the video without repeating the title.
<media:description> U.S. President Barack Obama honored American 
veterans during the dedication of the American Veterans Disabled for Life
Memorial, near the U.S. Capitol, in Washington. </media:description>
Category <media:category> Used to enter the lowest IAB sub category.  This should be decided based on the main theme of the video.  Please ask your Oath contact for our Category List to ensure your videos are being optimized for search.
<media:category>US News </media:category>
Keywords <media:keywords> Used to enter 10 keyword phrases to best describe the video.  This will help your video become optimized for search in the portal.
<media:keywords> Barack Obama, president Obama, president barack Obama, 
American veterans, veteran memorial, us capitol, American veterans
disabled for life memorial, us veterans memorial,
us memorial </media:keywords>
Video <media:content> Used to attach relevant links to the original video file. (This is not a link of the video in an existing player) We require videos to be no smaller than 1280x720 HD.
<media:content url= ’http://www.videos.com/123456.mp4’ 
width=’1020’ height=’1080’/>
Thumbnail <media:thumbnail> Used to attach original thumbnail file. This is an HD image that represents the video. 1280x720 required
<media:thumbnailurl=’www.videos.com/mythumbnail.jpg’ width’1280’ height=’720/>
GUID <guid> A video identifier used to differentiate between videos that have identical metadata.  The system detects new videos by looking at this field.
<guid> 00000001</guid>

 

Optional Parameters

The following table describes the available optional metadata attributes that can be applied to your MRSS feed using the system:

Note: The following 'Metadata Attribute' column only refers to opening tags.
All of the attributes are required to have appropriate closing tags, for example: <media:title>The title</media:title>.

 

Name Metadata Attribute Description Example
Transcripts <media:transcript> Used to attach a text version of all the spoken words in your video.
<media:transcript> Transcript content…</media:transcript>
Language <media:content…lang=”es”> Two letter code used to define content in a language other than English.
<media:content url= ‘http://www.videos.com/123456.mp4’ 
width ‘1020’ height=’1080’ lang=”es”/>
Publish Date <pubdate> Used to define the date and time the video was first published.
<pubdate>Wed, 15 Jul 2015 13:56:23</pubdate>
Closed Captions <media:subtitle> Closed captions or subtitles for the hearing impaired or for comfort of use.
<media:subTitle type="application/ttml+xml" lang="en-us"url=

https://www.myserver/captionsfile_CC.DFXP"/>

Expiration Date <media:expiration> Used to set a dusking time for an aired video due to broadcasting time limitations
<media:expiration>Mon, 10 Apr 2017 05:00:00 GMT</media:expiration>

 

Note: Please make sure to run your feed through an MRSS feed validation tool prior to submitting to the curation team, in order to avoid potential problems.

 

Un-encoded or Special Characters

Make sure to encode the special characters in your MRSS feed according to the table below:

Character Encoding
& &amp;   or   &#38;
< &lt;   or   &#60;
> &gt;    or   &#62;
&quot;   or   &#34;
\ &#92;

 

Security Limits

If your feed has security limits, such as password protection or a security token, we might not be able to ingest the feed. Please contact the Content Strategies and Solutions Team for more information.

 

Video Expiration

If your videos have expiration times, we might not be able to ingest the videos in time and this will result in a delay in ingestion throughout the whole system. Please contact the Content Strategies and Solutions Team if your videos have expirations.

 

Video Quality

Videos should be in 16:9 aspect ratio.
1080p: 1920x1080
720p: 1280x720
Accepted formats are .mp4 or .mov.

Please see the detailed requirements in the table below:

Type

Video Bitrate

Mono Audio Bitrate

Stereo Audio Bitrate

Audio Bitrate

1080p

8,000kbps

128 kbps

384 kbps

512 kbps

720p

5,000 kbps

128 kbps

384 kbps

512 kbps

 

Thumbnail Quality

Thumbnails must be in 16x9 aspect ratio and the width should be specified if there are several variants for each video item.
1280x720 96 DPI is a required thumbnail quality.
1920x1080 96 DPI is a preferred thumbnail quality.

 

Closed Captions

We support SRT, VTT, DFXP, .TT and XML formats of closed captions files.
Ensure language is selected when uploading caption file.

 

Category

Each asset should be categorized according to the video’s subject/topic. If you are unsure about how to categorize your content, please consult the Content Solutions Team. Please include only ONE category per video. Categories should be written in the feed as the lowest desired level of the IAB category. For example, if your video fell under “Movies & TV/Movies/Reviews,” you would only need to supply “Reviews” as your selected category in the feed. For a complete list of IAB categories, click here.

Alternately, we do accept category-specific feeds, where the entire feed is relevant to one subcategory only. For example, if you maintain 3 different series, one focusing on Tech News, another on Celebrity News, and a third on Pet Virals we can accept 3 separate feeds and can map accordingly.

 

Example

The following is an example showing an MRSS Feed:

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<rss version=-"2.0" xmlns:media="http://search.yahoo.com/mrss/" xmlns:bc="http://www.brightcove.tv/link" xmlns:dcterms="http://purl.org/dc/termsr/">
<channel>
<title>Site: AOL Feed – AOL MRSS</title>
<link>http://link.brightcove.com/services/mrss/player4539399784001/playlist4539564435001</link>
<description/>
<copyright>Copyright 2017</copyright>
<lastBuildDate>Tue, 24 Jan 2017 09:11:35 -0800</lastBuildDate>
<generator>http://www.brightcove.com/?v=1.0</generator>
<item>
<title>The Bachelorette: Lee wins Georgia Love's love, Matty J left speechless</title>
<link>http://link.brightcove.com/services/link/bcpid4539399784001/bclid4539564435001/bctid5187860375001?src=mrss</link>
<description/>
<guid>http://link.brightcove.com/services/link/bcpid4539399784001/bclid4539564435001/bctid5187860375001?src=mrss</guid>
<pubDate>Thu, 27 Oct 2016 15:41:05 -0700</pubDate>
<media:player height="630" url="http://link.brightcove.com/services/link/bcpid4539399784001/bclid4539564435001/bctid5187860375001?src=mrss" width="650"/>
<media:keywords>Inhouse,matty j,bachelorette,lee,Georgia,Love</media:keywords>
<media:thumbnail height="90" url="http://brightcove04.o.brightcove.com/761709621001/761709621001_5187865679001_5187860375001-th.jpg?pubId=761709621001" width="120"/>
<media:thumbnail height="360" url="http://brightcove04.o.brightcove.com/761709621001/761709621001_5187865680001_5187860375001-vs.jpg?pubId=761709621001" width="480"/> <media:category>AOL MRSS</media:category>
<bc:playerid>4539399784001</bc:playerid>
<bc:lineupid>4539564435001</bc:lineupid>
<bc:titleid>5187860375001</bc:titleid>
<bc:duration>44</bc:duration>
<dcterms:valid/>
<bc:accountid>761709621001</bc:accountid>
</item>
Have more questions? Submit a request