Displaying multiple filters on a page

12 Feb 2010 - 11:10am
4 years ago
3 replies
533 reads
lkruger
2009

I'm wireframing a "resource library" for a client right now and am
struggling with presentation. They have numerous presentations,
documents, etc. that need to be easily searchable and sortable via their
public web site.

The requirements are...

* Must have a keyword search option

* Must be able to sort by topic

* Must be able to sort by the resource type (PPT, Document,
Webinar, etc.)

Here's a site where we've included filters for Topic and Type, but I
feel like adding a search box will clutter the interface too much and
confuse users.

http://www.psr.org/resources/

I'd appreciate any ideas or examples of something similar.

Thanks!

Lacey Kruger
Senior Information Architect
Convio, Inc.
lkruger at convio.com <mailto:lkruger at convio.com>

512.652.7801

Convio. Move People. Internet software and services for fundraising,
constituent relationship and donor management, email marketing, advocacy
and website management. www.convio.com <http://www.convio.com>

Connect with us. Connection Cafe
<blocked::http://www.connectioncafe.com/connectioncafe> | Convio Summit
<blocked::http://www.convio.com/signup/summit-2008-save-the-date.html>
| Convio.com <blocked::http://www.convio.com/> | Convio Open
<blocked::http://open.convio.com/> | Client Community
<blocked::http://community.customer.convio.com/index.jspa>

Comments

12 Feb 2010 - 1:25pm
Susan Oslin
2010

The term 'issue' in the context of publications may be confused with
a single specific publication rather that a series of publications of
a given 'topic'.

How you display the interface also depends in large part how the
backend is locating the publications. I assume that the 'issue'
and 'resource type' act as filters, but it isn't clear whether a
search would override these filters or the search would only look
inside the subset defined by the filters.

Extracting the instructions from the descriptive paragraph would help
to isolate it visually and clarify.

-------------------------- if you want the search button to search
the entire database the instructions might read something like:

For up to date information to help you take action in your community
filter your search for publications by Topic and/or Resource Type:

...interface as you have it minus the submit

OR search our entire database for something more specific:

...search field

[submit]

Then clicking in the search field should un-select any selections to
demonstrate that the search is overriding the selections and
searching the entire database. Then if the user trys to select
again, the search field should be wiped out to make clear its either
filter or search. It would also be good to visually group the
filters and search button, so that it is clear that the submit button
acts on the whole.

-------------------------- if you want the search button to only
search within the filtered selection the instructions might read
something like:

For up to date information to help you take action in your community
filter your search for publications by Topic and/or Resource Type
and/or any Keyword of your choosing:

...interface as you have it minus the submit

further refine your search by typing in keywords separated by commas
(or whatever rules you defined):

...search field

[submit]

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49338

12 Feb 2010 - 1:31pm
Ari Tenhunen
2010

You are right when trying to keep the search function as simple an
elegant as possible. But we need to think about the user, what is the
purpose if this function to her/him?

I think a text search input field is a must. People should be able
make searches based on the information contained in the document
(content, introduction, author, title, filename, keyword etc.). I
think this is primary. Using categories and file types as only search
options may make it more difficult for the user to find what he/she is
looking for especially if there is a high volume of documents.

This is not primarily an aesthetic issue, it%u2019s a usability
issue.

Ari Tenhunen
www.nemeo.fi

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49338

13 Feb 2010 - 6:09am
Magdalena Mateescu
2009

I totally agree with Ari. People are searching for a subject usually
using key words. The issues and the resource type is not the first
thing that comes in mind, they are secondary and a lot of people
never use them.. For searches for this type of data base (research
and publications) is usual to have a normal search and an advanced
one that can be unrevealed, and the issues and the type are usually
to find in the advanced options.

If it is not possible to search with key words on a certain page an
expert user is going to use google to find what he needs.

I think about a library catalog without key words search option. This
really scares me :)

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Posted from the new ixda.org
http://www.ixda.org/discuss?post=49338

Syndicate content Get the feed