Aggregator2 / Podcast Aggregator
I'm implementing a podcast aggregator and I'm working with Agg2. I was going to modify aggregator2_parse_items() to pull the <ENCLOSURE> (which contains the podcast mp3 or whatever) and other fields out of the RSS feed and add them to the agg2_item type. But I feel that the following might be a better solution and would like some feedback. Would it be worthwhile to add an invoke_all call for '_parse_items' and pass the $items to that when parsing new RSS items? This would allow other modules to react when agg2 does an update as at the nodeapi level, you can't access any info that was in the RSS feed that agg2 isn't already sending to the database. Thanks for any input. -- Rob Roy Barreca Electronic Insight Corporation 12526 High Bluff Drive, Suite 300 San Diego, CA 92130 http://www.electronicinsight.com rob@electronicinsight.com
Hmmm...think I might just need to use the prepare nodeapi hook and I'll be golden. Rob Roy Barreca Electronic Insight Corporation 12526 High Bluff Drive, Suite 300 San Diego, CA 92130 http://www.electronicinsight.com rob@electronicinsight.com Rob Barreca wrote:
I'm implementing a podcast aggregator and I'm working with Agg2. I was going to modify aggregator2_parse_items() to pull the <ENCLOSURE> (which contains the podcast mp3 or whatever) and other fields out of the RSS feed and add them to the agg2_item type. But I feel that the following might be a better solution and would like some feedback.
Would it be worthwhile to add an invoke_all call for '_parse_items' and pass the $items to that when parsing new RSS items? This would allow other modules to react when agg2 does an update as at the nodeapi level, you can't access any info that was in the RSS feed that agg2 isn't already sending to the database.
Thanks for any input.
On 25-Apr-06, at 12:42 PM, Rob Barreca wrote:
I'm implementing a podcast aggregator and I'm working with Agg2. I was going to modify aggregator2_parse_items() to pull the <ENCLOSURE> (which contains the podcast mp3 or whatever) and other fields out of the RSS feed and add them to the agg2_item type. But I feel that the following might be a better solution and would like some feedback.
Would it be worthwhile to add an invoke_all call for '_parse_items' and pass the $items to that when parsing new RSS items? This would allow other modules to react when agg2 does an update as at the nodeapi level, you can't access any info that was in the RSS feed that agg2 isn't already sending to the database.
username "budda" was doing a new project -- check cvs.drupal.org for aggregator_node or something like that. It uses the core aggregator to manage all feeds etc., and then just links them to node types. It's an interesting approach. -- Boris
Op woensdag 26 april 2006 19:31, schreef Boris Mann:
username "budda" was doing a new project -- check cvs.drupal.org for aggregator_node or something like that. It uses the core aggregator to manage all feeds etc., and then just links them to node types. It's an interesting approach.
There is also *still* node aggregator. It works for 4.6 and we are getting it ready for 4.7. Budda and I decided to team up and develop a central, general feedparser.module API. I would love to see more people involved, because we would like to make this THE central feed parsing library over time. http://cvs.drupal.org/viewcvs/drupal/contributions/modules/feedparser/feedpa... Bèr -- | Bèr Kessels | webschuur.com | website development | | Jabber & Google Talk: ber@jabber.webschuur.com | http://bler.webschuur.com | http://www.webschuur.com | Heeft het gebruik van Sympal gevolgen voor de eigendomsrechten van het gepubliceerde materiaal?: http://help.sympal.nl/heeft_het_gebruik_van_sympal_gevolgen_voor_de_eigendom...
I was thinking the same thing. Great idea on centralizing feed parsing. I'm really excited about some additions I've made to aggregator2 and tagadelic and I'll be sharing those soon. Rob Roy Barreca Electronic Insight Corporation 12526 High Bluff Drive, Suite 300 San Diego, CA 92130 http://www.electronicinsight.com rob@electronicinsight.com Bèr Kessels wrote:
Op woensdag 26 april 2006 19:31, schreef Boris Mann:
username "budda" was doing a new project -- check cvs.drupal.org for aggregator_node or something like that. It uses the core aggregator to manage all feeds etc., and then just links them to node types. It's an interesting approach.
There is also *still* node aggregator. It works for 4.6 and we are getting it ready for 4.7. Budda and I decided to team up and develop a central, general feedparser.module API.
I would love to see more people involved, because we would like to make this THE central feed parsing library over time.
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/feedparser/feedpa...
Bèr
Bill, One of the additions to agg2 I've made so far is a aggregator2_enclosure module. Since podcasts include an <enclosure> or <link rel="enclosure"> in each RSS/Atom item, I made agg2_enclosure.module check the mime_type of the enclosure and either create an audio/video node depending on the type and they have a relational table linking them to the agg2_item. I probably should have used the node relativity module but just thought it'd be easier to do it myself, but integration with another module of that would allow for "linking" with the agg2_item which would allow cascading deletes using hook_nodeapi, etc. My module is not nearly dynamic as it should be but could be a starting point. I assume you know that agg2 items come in as "nodes" of type aggregator2_item. What kind of functionality did you have planned to import nodes from feeds? Sometime this week I'll be posting all this work to my sandbox (robroy) and will post here once I have done so. Rob Roy Barreca Electronic Insight Corporation 12526 High Bluff Drive, Suite 300 San Diego, CA 92130 http://www.electronicinsight.com rob@electronicinsight.com Bill Fitzgerald wrote:
Hello, Rob,
I saw this post on the Drupal development list, and I was curious because we were just about to start adding some functionality into agg2 -- literally, we are going to start coding on Monday -- some of the finctionality we are planning on adding includes the ability to import feeds as nodes -- basically, we are looking to develop some functionality within agg2 that allows people to move content between sites using rss feeds. We are planning on releasing all code we develop back to the community.
In the interest of not duplicating effort, would you be willing to talk about the functionality you added? If we are working on adding functionalithy that is similar/comparable, would you want to have a conversation about how we can help each other out?
Thanks,
Bill
Rob Barreca wrote:
I was thinking the same thing. Great idea on centralizing feed parsing. I'm really excited about some additions I've made to aggregator2 and tagadelic and I'll be sharing those soon. Rob Roy Barreca Electronic Insight Corporation 12526 High Bluff Drive, Suite 300 San Diego, CA 92130 http://www.electronicinsight.com rob@electronicinsight.com
Bèr Kessels wrote:
Op woensdag 26 april 2006 19:31, schreef Boris Mann:
username "budda" was doing a new project -- check cvs.drupal.org for aggregator_node or something like that. It uses the core aggregator to manage all feeds etc., and then just links them to node types. It's an interesting approach.
There is also *still* node aggregator. It works for 4.6 and we are getting it ready for 4.7. Budda and I decided to team up and develop a central, general feedparser.module API.
I would love to see more people involved, because we would like to make this THE central feed parsing library over time.
http://cvs.drupal.org/viewcvs/drupal/contributions/modules/feedparser/feedpa...
Bèr
participants (3)
-
Boris Mann -
Bèr Kessels -
Rob Barreca