RSS - EX.CO Motion Video from RSS feed

TABLE OF CONTENTS



Description

Ex.co allows you to dynamically generate catching video from the site content.

High-level requirements

  • Valid RSS feed
  • <link> from feed should be accessible


RSS parser work principle

In order for the EX.CO parser to support your RSS feed you need to know a few simple principles of how we get content to generate a video


Supported feed tags are (all of these tags should be under the <channel <item>REQUIRED_TAGS_HERE</item> </channel> tag):


Tag

Description

Required

<title>

Will be used as scene title

true


<link>

Will be used to access web page and parse content from html

true


<category>

Specifies one or more categories item belongs to.

false


<enclosure> or <content:encoded>

Will be used to get media content form it (images only supporter at this moment)

false


<isoDate> or <pubDate>

Will be used to include topic creation date to the scene

false


<author> or <dc:creator>

Will be used to include topic author to the scene

false

<media:content> and <media:group> more details

Will be used to get media content form it (images only supporter at this moment)

false

2. In case of required values - title, image can't be fetched from the feed, parser will try to grab content from the <link> tag link, and extract information from the web page. Parser will search for the content in the next html tags:


Tag

Description

Examples

<meta property="og:image" content="" />

An image for a video scene


<meta property="og:image" content="http://site.com/images/example.jpg" />

Any <address>, <a>, <link> with a class or rel attributes with author value

An image for a video scene


<a herf="http://test.com" class="author">Author Name</a>

You can find an example of a valid feed and page(s) under this link



Good to know

  • Supported image formats are JPEG (.jpg, .jpeg) and PNG (.png)
  • Scenes order in video based on <pubDate> or <isoDate> tag(s), ordered from newest to oldest. In case if those tags are not exist, scenes will be built in order <item> appear in feed, from top to bottom.
  • Parser sends requests with User-Agent: Playbuzz RSS parser header, in case if page is not available, we retry with an empty User-Agent header
  • Timeout for a request to RSS link and any link under <link> tag is 20s
  • Parser does not support any kind of authorizations and/or authentications
  • Parser support 301 redirects
  • In order to build a correct scene all media (images) content should be available for a direct download without any restrictions

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us how can we improve this article!

Select atleast one of the reasons

Feedback sent

We apprciate your effort and will try to fix the article