distractionary: apple in foreground, out-of-focus bridge in background. (Purple.) (Default)
high and mighty robot ([personal profile] distractionary) wrote in [site community profile] dw_suggestions2009-09-21 09:40 am

Create tag sorting for calendar view.

Title:
Create tag sorting for calendar view.

Area:
entries, tags, calendar

Summary:
Allow users to browse their tags by calendar view.

Description:
I had the thought the other night that it would be very nice to have a clearer view of how often and when I use certain tags. When I got to the computer, I tried going to my calendar and adding ?tag=exampletag to the end of the url, and while the calendar loaded it didn't accurately load the calendar showing only those entries that were tagged "exampletag". (Obviously the tag in question wasn't "exampletag", but that's not really the point.)

I have no idea what the technical requirements or limitations would be for this, but if it's possible to create the option to view all entries tagged by a particular tag in a calendar view, I think that people would like to use it.

Benefits: Overview of tag usage; easier to find entries, if you're looking for a specific entry in a journal without remembering any significant phrases (so that Search isn't as useful, if it's available in that journal), but you know one of the tags that was used, and approximately when it was posted, as the journal might have a vast number of entries so searching by calendar view alone or tag view alone would be time-intensive, confusing, and frustrating.

Downsides: Whatever the technical load is; I don't think this is prone to abuse, or at least I can't imagine any real way to abuse it. If someone else knows how much effort would be required, I hope s/he can comment here. Similarly, I don't know how much bandwidth would be required to actually load the page.

Poll #1314 Create tag sorting for calendar view.
Open to: Registered Users, detailed results viewable to: All, participants: 29


This suggestion:

View Answers

Should be implemented as-is.
18 (62.1%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
11 (37.9%)

(Other: please comment)
0 (0.0%)