Posted by budda on January 27, 2007 at 8:23pm
From the issue queue of Feedparser it came to my attention that a lot of Drupal sites are managing the parsing of hundreds of feeds. Now that I've added OPML import functionality to Feedparser I've been adding lots of feeds - which got me wondering...
What's the best way to manage the ?q=admin/aggregator page listings?
How should feeds be organised? Currently it's just a single page sorted A-Z.
Comments
Needs paging
Core aggregator as well as feedparser need paging.
Ideally, if a taxonomy is applied to feedparser feeds, it should be sortable that way. In fact, if you do public listing (i.e. not in admin) of feeds (not just feed items), then views or directory-style drill down, you should be able to easily edit and manage feeds just like other content.
Hmmm...maybe something to think about: if you treat feeds as content, lots of things become easier, since you can use admin/node and all that....
Using a standard 1.2.3.4...
Using a standard 1.2.3.4... pager as Drupal provides isn't much help in making feed admin navigation easier. Having to guess where a feed beginning with 'H' starts in the pager can be a pain. Having a simple A-Z pager across the top might be the initial solution.
I was thinking of also grouping of feeds based on taxonomy terms somehow as an alternative navigation method?
Aggregator2 used nodes to store feeds. But then you have the whole issue of implementing security for the node types, published feed nodes appearing on sites fron pages if they simply use ?q=node etc.
Look at banner
Banner 4.7 uses banners-as-nodes and they don't appear. I haven't investigated deeply, but "administer banners" is required to see banner nodes.
Once you start dealing with organizing by taxonomy or doing an alpha pager -- both can be made with a simple view (see views_alpha_pager).
re: numeric pager -- I agree it's not that useful, but it's better than trying to load 300 feeds on one page :P