We're using FeedAPI, along with the default Simple Processor, as the heart of our site, and we're processing thousands of nodes per day, so we're always looking for FeedAPI related modules that might improve performance. From the description, I couldn't quite get the sense of what this module does. Is it a node processor / parser offered as an alternative to the two options that come with FeedAPI? If so, what advantages or disadvantages does it have over the other two.

Comments

e2thex’s picture

e2thex commented

It is a parser. But it is intend to be used with one of the other parser. It will parse out all of the fields in the feed, regardless of namespace. May times feeds will have extra fields that are not part of the atom, or rss spec, ofter in there own namespace (such as using dc:creator instead of original author). The default parser will not parse that data, FeedAPI Exhaustive Parser will pull out those fields.

I think the best way to understand is to use try it, with feed Element Mapper.
hit a NYtimes feed like http://feeds.nytimes.com/nyt/rss/Business, and when you go to map the fields you will see that the feed has lots of fields (like media:credit, media:description, dc:creator) that are not available with the standard parser.

FeedAPI Exhaustive Parser makes those fields available. It also make all elements of the feed it self available. In the nytimes example you will see the language and the copyright are list on the feed but not the individual items , if you wanted to store that in a cck field on the node, this would allow that.

fumbling’s picture

fumbling commented

I get it now, that makes good sense. I'll try it.

febbraro’s picture

febbraro commented

This writeup is so good you should put it on the module homepage instead of buried in this issue. :)

e2thex’s picture

e2thex commented
Status: Active » Closed (works as designed)