It would be fantastic if this module allowed you to set default taxonomy terms by user roles... this would come in handy with sites that have many roles and want to make the user interface quicker and simpler. I don't know how hard this would be to implement...

Comments

jjeff’s picture

jjeff commented

I like the idea of this, but that feature would really start to make things complicated. For instance: What if a user has two roles, each with different taxonomy terms, and the node-type has a taxonomy term as well, but the vocabulary doesn't allow multiple selections? Which term is going to get assigned?

And probably the hardest part is keeping the interface relatively understandable. I'd be willing to hear suggestions though.

-Jeff

bomarmonk’s picture

bomarmonk commented

Yep, sounds like there are some rather complex considerations.

Suggested possibilities:

Have a checkbox to choose one way of setting defaults: by user role or by node type (not both)

For the user-role, you can only select one default term per-role for each node-type.

While this wouldn't be entirely flexible, it still might be very useful.

This is just a little brainstorming on how to simplify the considerations.

Let me know what you think... would this be potentially useful and possibly a less complicated way to implement something with user roles? I'm working with limited experience and understanding at this point, but I thought my suggestions might work.

jjeff’s picture

jjeff commented

I think the right way to do this is with profiles (similar to what Mathias has done with TinyMCE.module). Each profile would be a group of roles. And it would contain the full page of defaults like what's there now. That way you could assign different defaults to different (sets of) roles. The only problems happen when a user is a member of several roles and those roles have different defaults. There may be a way around this though.

I'll see if I can find some time for that, but it may not be for a few months. I'm really busy right now. Sorry I won't be able to get to it sooner.

-Jeff

bomarmonk’s picture

bomarmonk commented

I'm excited about the possibility that this feature could be added. One thing I'm wondering is if taxonomy defaults would also be compatible with organic groups? The reason I wonder this: organic groups and taxonomy access are incompatible, so you must choose between them.

However, I think many people want to be able to use at least some of the features of taxonomy access in combination with organic groups; being able to limit users to a specific list of taxonomy terms when creating nodes will help reduce user error and even more importantly, make node creation more user friendly (a large taxonomy for a site makes things very non-user friendly if you can't use taxonomy access).

So, even if taxonomy defaults doesn't block people from using particular terms, it could help them find the right terms more readily. Combine this with organic groups, and perhaps the solution for tightening up a specific user experience is almost complete.

Just food for thought... thanks again for the contribution to Drupal!

heine’s picture

heine commented
Status: Postponed » Closed (won't fix)

See http://drupal.org/project/user_force_term