Interface PIApiFeed

The seemingly best artwork we can find for the feed. Might be the same as ‘image’ in most instances.

The channel-level author element. Usually iTunes specific, but could be from another namespace if not present.

The Content-Type header from the last time we pulled this feed from it’s url.

The number of errors we’ve encountered trying to pull a copy of the feed. Errors are things like a 500 or 404 response, a server timeout, bad encoding, etc.

At some point, we give up trying to process a feed and mark it as dead. This is usually after 1000 errors without a successful pull/parse cycle. Once the feed is marked dead, we only check it once per month.

The channel-level description.

The channel-level generator element if there is one.

The channel-level image element.

[Unix Epoch] The last time we attempted to pull this feed from it’s url.

[Unix Epoch] Timestamp of the last time we got a "good", meaning non-4xx/non-5xx, status code when pulling this feed from it’s url.

The last http status code we got when pulling this feed from it’s url. You will see some made up status codes sometimes. These are what we use to track state within the feed puller. These all start with 9xx.

[Unix Epoch] The last time we tried to parse the downloaded feed content.

[Unix Epoch] The channel-level pubDate for the feed, if it’s sane. If not, this is a heuristic value, arrived at by analyzing other parts of the feed, like item-level pubDates.

The channel level link in the feed.

The url of the feed, before it changed to it’s current url.

The channel-level owner:name element. Usually iTunes specific, but could be from another namespace if not present.

The number of errors we’ve encountered trying to parse the feed content. Errors here are things like not well-formed xml, bad character encoding, etc. We fix many of these types of issues on the fly when parsing. We only increment the errors count when we can’t fix it.

0 = RSS, 1 = ATOM