Project taxonomy reworking [#270349]

I had some ideas about new/different categories for projects - to try to make them more specific, so we eventually end up with more terms, less projects in each one.

I've written it up here: http://groups.drupal.org/node/11996 - any specifics/ideas should ideally be kept there to avoid clogging inboxes and I won't repeat the arguments here. Essentially I want to rename some terms, add some new ones, and eventually get freetagging happening in a different vocabulary.

Actual implementation I think will go something like this.

1. create some new terms in the project vocabulary
2. put project nodes into those new terms
3. create a 2nd vocabulary.
4. move deprecated 'top level' terms from the fixed vocab to the auxiliary one.
5. turn the 2nd vocab into a freetagging vocabulary and assign it to projects (see groups discussion).

1-4 could happen in chunks - so make 'audio', 'video', 'images' terms, reorganise everything currently tagged with media, move media to the other vocabulary. Repeat for the next group. It ought to be possible to have bursts of activity like this so the whole process is fairly non-intrusive on day to day downloading and project maintenance.

The issues are -
* I'm not sure who's responsible for the project taxonomy, who to ask, how I'd actually get permission/consensus to do something like this.
* I don't have permissions on d.o to administer taxonomy - so one way or another the new terms actually need to be made.
* I /do/ have administer content permissions, and I'm prepared to put work in reclassifying stuff (and rounding up some help) - I'm not sure what the deal is with changing people's project pages like this though.
* moving terms between vocabularies is either a trivial database query, or a temporary install of taxonomy_switch module. I'm happy to write queries or do some taxonomy switch donkey work but this probably needs discussion.

Comments

Comment #1

aclight commented 15 June 2008 at 20:55

Comment #2

dww

we/he/they

commented 16 June 2008 at 10:04

- No one's personally responsible for the project taxonomy. It started as a card-sorting job by Kieran and some others over 2 years ago. Nedjo wrote the original code that made this possible, and was probably involved in the original classification, too. Since then, it's been loosely "maintained" by myself, webchick, greggles, and a handful of other people who keep their eyes on the various requests for new categories and try to separate the good from the bad.

- I wouldn't object to adding you to a role with enough permissions to do this stuff yourself, and I doubt anyone else on the infra team would, either. If that became a problem, I'm sure webchick or I could find a few minutes some day to add the new terms once there's agreement on your proposal.

- I don't think there's any problem reclassifying projects as necessary for this sort of thing. In the past, when we add a new category that's more useful for a set of projects, someone just goes in and edits them. The project owner will see their node bumped in their tracker page if they really care, and can always re-classify themselves if they object to whatever you change.

- I suspect Gerhard would be happier with a handful of custom DB queries that one of us w/ DB access just runs, instead of temporarily installing another module on d.o. Hopefully he'll see this issue and comment about that here.

All that said, I haven't had time to read your full proposal and think about it, so I don't know where I stand on that. ;) But, I figured I should answer the easy questions, first.

Cheers,
-Derek

Comment #3

catch

he/him

English

commented 23 June 2008 at 12:20

All of this sounds good. I'm happy to provide specific db queries when there's stuff to move - it's only the vid column in term_data which'll need changing and quicker than using taxonomy_switch anyway.