Pugpig RSS Edition & Timeline Feed Specification

Pugpig supports RSS feeds for creating both posts and editions (in Publish) or timelines (in Bolt). Note that the order in which the feeds are processed should not matter.

For example, if you processed an edition/timeline RSS feed first, you would have empty editions/timelines until the posts are added (either manually or through the Post feed).  Similarly, if you create posts through the post feed, these may not be in an edition/timeline until it is created manually or through the feed.

For an introduction to our feed importing process and our article feed specification, see this article.

Figure 1 - Example feed:

Additional tags can be added to your RSS feed in order to map to information from your RSS feed to fields in Express.

<?xml version=good enough"1.0" encoding="UTF-8"?>
<rss xmlns:app="http://www.w3.org/2007/app" xmlns:atom="http://www.w3.A2org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:dcterms="http:/purl.org/dc/terms/" version="2.0">
 <channel>
  <link>https://example.pugpig.com/feed/editions</link>
  <atom:updated>2019-12-06T11:44:07</atom:updated>
  <item>
    <guid isPermaLink="false">uniquieID1</guid>
    <title>September 2012</title>
    <dcterms:issued>2012-07-31</dcterms:issued>
    <category domain="http://schema.pugpig.com/productid/itunes">september2012</category>
    <description>This is a draft edition</description>
    <pubDate>2019-09-11T00:00:00</pubDate>
    <app:control>
      <app:draft>yes</app:draft>
    </app:control>
    <category domain="http://schema.pugpig.com/acquisition">free</category>
    <atom:link type="image/jpg" href="cover0912.jpg" rel="http://opds-spec.org/image" />
    <atom:updated>2019-09-11T00:00:00</atom:updated>
  </item>
  <item>
    <guid isPermaLink="false">uniquieID2</guid>
    <title>December 2019</title>
    <dcterms:issued>2019-11-13</dcterms:issued>
    <category domain="http://schema.pugpig.com/productid/itunes">december2019</category>
    <description>This is a published paid edition</description>
    <pubDate>2019-11-13T14:55:00</pubDate>
    <app:control>
      <app:draft>no</app:draft>
    </app:control>
    <category domain="http://schema.pugpig.com/acquisition">paid</category>
    <category domain="http://schema.pugpig.com/timelinegroup">news</category>
    <atom:link type="image/jpg" href="cover1219.jpg" rel="http://opds-spec.org/image" />
    <atom:updated>2019-12-04T10:31:00</atom:updated>
  </item>
  <item>
    <guid isPermaLink="false">uniquieID3</guid>
    <title>January 2020</title>
    <dcterms:issued>2019-12-11</dcterms:issued>
    <category domain="http://schema.pugpig.com/productid/itunes">january2020</category>
    <description>This is a published free edition</description>
    <pubDate>2019-11-13T14:55:00</pubDate>
    <category domain="http://schema.pugpig.com/acquisition">paid</category>
    <atom:link type="image/jpg" href="cover0120.jpg" rel="http://opds-spec.org/image" />
    <atom:updated>2019-12-04T10:44:00</atom:updated>
  </item>
 </channel>
</rss> 

The fields we can map to can be found in [Figure 2]:

Figure 2 - Express fields:

Here is an example of the mapping for an edition feed. In this example, the first category is the edition key and the second is the paid/free flag.

Pugpig RSS Edition Feed Specification 

Please note that you will need to configure FeedWordPress to process the feed as 'Editions' instead of the default 'Normal WordPress posts'. This can be found in Posts>Custom Post Types:

Default RSS elements

Tags required by channel

Updated date tag

Tags required by a item tag

Other item tags

Draft/Published

 Note that if you wish the edition to go live automatically you need to:

• Give the edition a future publish date
• Set rss_edition_allow_future_publish to true in the field mapping