Ability to display journal entries using multiple tags
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mahara |
Fix Released
|
Wishlist
|
Robert Lyon |
Bug Description
Mahara 1.8
Hi Everyone,
At the moment displaying journals by tag allows a user to choose only one tag.
In a scenario where a student writes lots of journal entries for a course say "Underwater basket weaving", but wants some to be public too, they would create two pages: one for the unit and one for the public.
Lets say they assigned the tags to every post "UBW" and to a few of them they add "public".
They create their course page and add journal entries with UBW. No worries!
They create their public page for UBW stuff and add the tag .... which one? They can't add public because that would pickup any other post from oter journals tagges "public", they can't add journals tagged "UBW" because that would add non public posts.
Wishlist item is that: user can display posts with UBW AND Public
Cheers,
Shane.
Changed in mahara: | |
importance: | Undecided → Wishlist |
tags: | added: blog tags |
Changed in mahara: | |
status: | New → In Progress |
assignee: | nobody → Robert Lyon (robertl-9) |
Changed in mahara: | |
status: | In Progress → Fix Committed |
summary: |
- Ability to display journal entries using mulitple tags + Ability to display journal entries using multiple tags |
Changed in mahara: | |
status: | Fix Committed → Fix Released |
One issue we run up against, when dealing with this situation, is the question: When you select multiple tags, are you indicating that you want to display journal entries that contain ANY of those tags? Or do you want to display journal entries that contain ALL of those tags?
From your scenario, it sounds like you're interested in showing entries that contain ANY of those tags?
We could of course add an additional configuration option to let the user specify ANY/ALL, but I'd prefer to avoid adding further config options if we can (because it just makes the "7 clicks to do anything" problem worse), so if ANY is the more common use-case, I'd say it's best to just stick with that.