feedapi

In my system I have a series of nodes that are created every hour, each one with a set of environmental paramaters. the date is stored as a cck datetime with the time ignored and the time is stored as an integer in a cck feild and is from 0-23. Lastly is a field called station which contains a code for a particular station. Now at run time during creation of the nodes, which is handled by feedapi, a series of physics equations which has been converted into php functions and are activated by a set of trigger rules and rule sets.

LinkedIn is still lacking a public API in spite of several announcements in 2007 and 2008 (they even confirmed OpenSocial support but so far did not deliver anything).

I did it. A huge milestone in my Drupal development life. I completed my first custom module. While at this point it would only work on my site (I hard coded the name of content types and some other variables from the notification module) but it works. I have attached it but know that you can’t just add it to your site. At minimum you might have to change the name of the feed-item content type on line 85.

notification_block.zip

I'm working on an Aggregation site. I am using FeedAPI to pulling the feeds. I have a vocabulary for "tags" and "category." I assign each feed at least on "category" when the feed is created. I control the create of the Feeds and the "category". The "category" vocabulary also drives a menu on top of my page. I am using Feed Element Mapper to add tags from the Feeds to the "tags" vocabulary so I have no control over what gets put in it.

I am also using Messaging/Notifications to allow the users to subscribe to feeds and/or "category" vocabulary.

I've been working on an extension module / processor for FeedAPI (similar to feedapi_node) that does node deletions based upon incoming feed items parsed by FeedAPI. So, you can bring in and create new nodes from feed items -- why not be able to delete them as well!

I am currently matching on guid or node title -- the match type is configurable. Guid is pretty safe and should be unique. Also, you are probably not going to bring in and process a "delete feed" from an untrusted source.

Jose Reyero blogged this morning about how he used FeedAPI to aggregate mailing lists:

http://www.developmentseed.org/blog/2008/jul/29/surviving-information-ov...

The major new feature of OpenPackage Video 5.x-3.8 is integration with Feed Element Mapper (feedapi_mapper).

The development of this functionality was sponsored by Hudson Street Media using our bounty system:
http://openpackage.biz/bounty/15
http://openpackage.biz/bounty/14

Feed Element Mapper is an add-on module for FeedAPI that maps a feed's elements such as tags or (in this case) videos to taxonomy or CCK fields on your site.

This enables your site to aggregate videos from other sites.

I have set up various video feeds on our site as a demonstration. Click on the 'Feed item' links to view the videos.

We have finally gone live with our redesign of the Georgia Podcast Network! For a rundown of what's new from an end user standpoint, check out our announcement blog post.

GAPN is based on Drupal 5.7, and makes heavy use of the following modules: CCK, Views, Workflow-ng, FeedAPI, ImageCache, Usernode, Bio, Fivestar, and Voting API. That's not a full list, but the site leans on those the most.

Additionally, we built a custom theme and wrote several custom modules to get things working just the way we wanted them to. In writing these modules, we built custom Drupal integration for getID3, SWFUpload, and the JW Media Player.

Hope you like the site! I'll be happy to answer any "how did you do that?" questions if you have them.

There are many people, who ask a possibility to filter feed items based on keywords in order to exclude them from processing (or possibly based on some other criteria like on timestamp, etc.). This issue has been raised under most aggregator modules and such feature request is in the pipeline of FeedAPI project as well:

FeedAPI:
http://drupal.org/node/160692

The usual recommendation for such problem is to relay on standard syndication and use Views module afterwards for filtering.

Is anybody working/experimenting with aggregating comments for articles? I'd love to see a (FeedAPI) processor for pulling in comments for aggregated articles.

See also feature request here:

http://drupal.org/node/241935