A good proportion of you will be reading this site via a webpage that is powered by the Planet Planet aggregation software. Now, I’m told that Planet Venus is a better aggregator, but I have no real plans to change.

However, I do have vague plans to change the way it works. As part of my LugRadio marathon (status) I got to an episode where they complain, legitimately, that many planets are simply overrun with posts that are not particularly relevant for the topic. However, as the conversation continues (and the subsequent conversation on hashlugradio) it becomes obvious that there is a great deal of subjectivity of what people want to read on a planet site.

So - here’s the plan for “Galaxy Galaxy” (bigger and better than Planet Planet ) - we create a (thoroughly web 2.0) set of tools that allows for a very customisable planet-type system. This has a number of elements and features:

• Key to this will be plugins for blogging software that provide feeds of the categories/tags that are used on that site
• Likewise the blogging software will need to provide feeds for each of the categories - Wordpress already does this
• The “GG” site will be set up to subscribe to particular sites (as they are now) but also which categories are subscribed by default
• Individual readers will be able to select/deselect which categories they actually do want to have feeds from, via a whizzy Ajax-style interface
• Choices will remain persistent (probably through cookies - we don’t really want logins…)

OK - so this may not be a new idea. In fact, it may not even be a good idea. But I would like to hear from anyone who’s interested in developing it

mrBen

OK - if you’re not into Django (the Python webframework), or you don’t know know anyone who does, look away now. Otherwise, I really need your help. Hell - even if you know nothing about Django, but know some database stuff, you might have some insight. Either way, it’s important

I’m trying to create a Rota system - you know, like the bit of paper that you stuck on the fridge when you were student, identifying who was supposed to do what each week? So I will have a table of users, let’s call them Rob, Bob, Mark, Mary, Lisa, and Rupert (for arguments sake). And a table of jobs (washing up, toilet cleaning, hoovering sitting room, etc). These 2 tables need to be linked in some way to indicate who can do which jobs. (Mary gets bad hay-fever, so likes to avoid the dusty hoovering; Rupert is allergic to fairy liquid; etc) Now - this can either be a list of names associate with the Job, or a list of Jobs associated with the User. I’m not overly fussy either way.

Each week there needs to be a rota - the rota should be dated, and contain each of the jobs, and which person is doing the job. But (and this is the big but) when selecting the user for a particular job, you should only have to choose from the users that can do this job.

So - 2 questions:

1. What is the best table structure to do this?
2. What is the best way to represent this in Django? I am beginning to wonder if I will actually need to do a custom admin page for this model, in order to achieve the desired result.

Any help would be gratefully appreciated.

mrBen