Tag Filtering.

[Davide DB]

Just for fun I create a thumbnail dive which mimic a dive computer
display. I was inspired by Black BT layout. I don't know the Petrel
logbook layout :) Of course the classic divelist it's still the best
choice.

Jokes apart, I moved listboxes of my previous mockup to accomodate a
date range selection widget but...
What's the best way to easily and rapidily select a date range?

The amazing examples of faceted search below, filter only by year.
http://moritz.stefaner.eu/projects/elastic-lists/NYT/
http://well-formed-data.net/experiments/elastic_lists/

The year bar graph below is a good idea for the stats page... Diving
log has something similar.
http://archive.stefaner.eu/projects/elastic-lists/MACE%20ProjectSearch/index.html

I put a search box in the upper right corner. It should be always
visible and it could be a main entry point for the search
functionality without accessing a menu. It could be a free text search
or bounded to the location that in our specific case it's the only
free text field.

Bye






On Mon, Sep 22, 2014 at 12:44 PM, Davide DB <dbdavide at gmail.com> wrote:
> On Fri, Sep 19, 2014 at 4:21 PM, Dirk Hohndel <dirk at hohndel.org> wrote:
>>
>> I don't have the time for a beautiful mockup...
>>
>> Imagine having all the tags, alphabetically ordered, each with a gray
>> bubble around it. You click on one, the bubble turns blue and that tag
>> is selected as filter.
>>
>> The bubbles look just like the ones we are using for tags and the likes
>> on the Notes panel.
>>
>> Makes sense?
>
> Yes but only if we will have just tag filtering.
> I was the first to propose a sort of tag cloud and I fell in love with
> it but later I realized that tag filtering is just one of the many
> filtering options that we should implement: date, location, equipment,
> buddy, etc...
> Hence I began to think to a more "holistic" approach in which tag
> filtering is one of the several search I need.
> From the UI point of view would be important having the same approach
> for the various searches and not having a tag cloud, a text input and
> combo boxes for different task/search.
> Tomaz told that the search code is pretty much independent from the UI
> implementation.
>
> Regarding the OR/AND between tags I agree that could be useful having
> both options but I guess we all are accustomed to AND by default. When
> we search via google we expect having only results with all input
> words/keys (and not like the ancient Altavista model). Same with usual
> web tag clouds. So when selecting "drift" and "reef" I would like
> seeing only dives with both tags. Otherwise the more tags I select the
> more dives I find.
>
>
> --
> Davide
> https://vimeo.com/bocio/videos



-- 
Davide
https://vimeo.com/bocio/videos
-------------- next part --------------
A non-text attachment was scrubbed...
Name: full search III.png
Type: image/png
Size: 43209 bytes
Desc: not available
URL: <http://lists.hohndel.org/pipermail/subsurface/attachments/20140922/83af7519/attachment-0001.png>