Just capturing some ideas from earlier this year
--------------------------------------------------
[Moshe on devel list - 5/30/02]
Marco has released a fine image.module, but I need it to do even more. But first, he asked me to kick off a discussion here about personal vocabularies and taxonomy.
Image.module currently enables each user to have a 'personal gallery' which is like a photo blog. I want this module to go even further, and allow users to post their own personal photo albums. An album is just a grouping of images.
Image.module considers each photo as a node. It achieves albums by associating images with term(s) in a vocabulary. So it would seem that the cleanest way to allow users to have personal albums is to let them create their own vocabulary. Personal vocabularies might also be helpful in allowing users to group their own bookmarks or classify their own blog entries [1], [2].
PROPOSAL
- add a field in terms and vocabularies which states the uid of its owner.
- Public terms/vocabularies have no owner.
- we expose a UI to users for add/delete/edit personal terms and
vocabularies (if user has sufficient permission). perhaps this UI is simpler than the one currently in Admin -> Taxonomy
- when a user is composing a node, we display the union of personal and public taxonomies on the compose form
- if a user has no personal vocabularies, drupal looks exactly as it does today
- we display a Block showing the author's personal taxonomy when viewing his personal blog and his user account page. This is easily done in the new taxonomy_html.module
- admins may choose to create links between a private term and a public term
using the 'related terms' feature. see [1], [2] below.
- in Taxonomy Admin, we have 2 overview links. 1 is public taxonomy overview (same as current) and the other is private taxonomy overview. private overview is the page where an admin can browse the vocabularies/terms of his
users.
NOTES
- is there any need to allow multiple personal vocabularies? I think there
is, considering that image.module might use up a whole vocabulary
[1] http://www.drupal.org/node.php?id=55
[2] http://www.drop.org/node.php?id=740
-----------------------------------------------
[marco's reply - 6/3/2002]
> > - we expose a UI to users for add/delete/edit personal terms and
> > vocabularies (if user has sufficient permission). perhaps this
> UI is simpler
> > than the one currently in Admin -> Taxonomy
>
> If we can make it simpler the one in the admin page should be made
> simpler, too.
I don't think the admin page could be made easier without losing some
functionality. Yet a taxonomy user page should be made easier, so we should strip something. We could also give a different interface, perhaps based on a wizard.
> > - admins may choose to create links between a private term and
> a public term
> > using the 'related terms' feature. see [1], [2] below.
>
> I would rather see that the private terms are copied to the queue for
> approval, where the admin may want to edit it. If it gets approved, it
> would be accessible to everybody. Not, that a copy is approved, so if it
> fails it does not affect the public terms.
I'd prefer "links" which could also be something different from "related terms". think about unix links. we could have a public term, and several private terms linking to it. the concept of link is important because the user already categorized his content, and this is info we want to keep.
I agree on everything else
Marco
Comments
Comment #1
moshe weitzman CreditAttribution: moshe weitzman commentedOne excellent way to achieve this is with the classify anything patch.
4969 is a duplicate of this request.
Comment #2
alexandreracine CreditAttribution: alexandreracine commentedToo old, closing.
I think this has improve, but you'll have to search for it in the module area.
Comment #3
magico CreditAttribution: magico commentedComment #4
moshe weitzman CreditAttribution: moshe weitzman commentedage is not a reason to close a valid feature request
Comment #5
alex_b CreditAttribution: alex_b commentedPlease check out Community Tags module.
It stores term node relations with timestamp and user ids. What's missing in community tags?
http://drupal.org/project/community_tags
Comment #6
moshe weitzman CreditAttribution: moshe weitzman commentedthats a useful module, but it lacks the 'vocabulary' aspect, at least out of the box. it ought to autocomplete against the user's prior used terms (maybe it does already?). also, i'm not too keen on people tagging other people's nodes but thats easy to prevent with form_alter().
Comment #7
alex_b CreditAttribution: alex_b commentedautocomplete from all user's terms _can_ be a problem but also a feature: in the scenarios I am using community tags, I consider automatic completion suggestions from all user's tags a feature, not a shortcoming.
I agree that tagging without node edit permissions is not always the desired behavior - it needs to be a separate permission.
Comment #8
dodorama CreditAttribution: dodorama commentedI think this is really needed for user-centric sites. Any news?
Comment #9
catchTwo patches which ought to help with different bits of this:
#413192: Make taxonomy terms fieldable
and #340652: Edit/delete terms permission per vocabulary
Comment #10
catchComment #11
chx CreditAttribution: chx commentedGiven the activity on this issue and the immense popularity of http://drupal.org/project/community_tags shows it's a wont fix.