Let's create a comprehensive list of all features and options in FeedAPI. The goal is to get a good understanding of the status quo as a first step towards refactoring the API. I've got a bunch of very concrete ideas already of what we would like to improve in a new version, but I'd like us to do first this exercise of getting a comprehensive overview of the existing functionality.

Assigning this to Aron.

Comments

aron novak’s picture

Status: Active » Needs review

As there is another ticket about creating a better API doc (#443436: Create full API documentation, here i mainly focus on features from the user viewpoint.

Structure
pluggable parsers
pluggable processors
custom hooks (hook_after_refresh) to add more flexibilty than parsers + processors
no central download handling

Feed handling / refreshing
Feed can come from a local file (upload or file path) or a remote URL (any kind of protocol, depends of the parser)
Parsers supports various feed types (RSS, Atom, Ical, KML, CSV, etc)
Refreshes the feeds via cron
Feed refresh priority by next_refresh_time
Manages the elapsed time while cron
OPML import / export of feeds
Oveerrideable deduping logic (via feedapi mapper)
Feed handling (inc. refreshing) via Drush for dedicated box w/ shell access
Inherit given things (taxonomy, author, language, og) from the feed to its child items

Configuration management
Per-node settings of a feed
Per-content-type settings of a feed
Parsers and processors can expose their own settings

Statistics
Flexible statistics collecting and storing
Nice UI to show all the statistics (mainly about how the feeds behave, refresh frequency, number of items, processing time)

Misc
Comprehensive testing suite (missing for the parsers, inherit and stat)
Full views integration for child items and feeds as well
FeedAPI translations (not extensive yet, only Hungarian, but w/ OpenAtrium translate project, likely other translations are in progress)
Tons of 3rd party, very useful modules (various parsers, FeedAPI Mapper, FeedAPI Data, Feed Scraper, etc)

Maybe i skipped some of the important things, we have so much features in :) I mark it NR, cause here the deliverable is not a patch, but a description like above.