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
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
*
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
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
