 |
 |
I think there are ways to dispense with it without actually dispensing with it. David, you've of course seen what I did with Xerxes, where instead of calling it 'advanced search' I call it 'more options'. That was of course a much simpler case--the difference between Metalib's "advanced" search and "simple" search is pretty small, there isn't that many features available even using all the features in Metalib search. Unlike WorldCat, where the difference between a 'start' screen and a 'full' list of options is greater. I think it makes sense that you might need an initial search screen with fewer options, and a way to then get more search options (more options typically including more fields to search/limit, as well as more complicated ways to boolean combine those searches). But I think we should find ways to provide that "more" functionality other than the typical "click here to see advanced search" pattern. I think it should never be called 'advanced search'. Something like 'more options' is better. But maybe not even just one 'more options' link. What exactly is it that this additional functionality is providing, and what are the use cases for it? Maybe provide links to add different components of this advanced functionality to the search page, identified by explaining what they are/are for, instead of just calling them "advanced". They don't need to be added all at once neccesarily. For instance, if you want to add another search field to the screen for boolean combination, a button that says "add another search field" seems appropriate. Click it to add a second one, click it again to add a third one, etc. No "advanced search", just offering functionality. I also like the idea of allowing a syntax for expressing fielded search and boolean combination even in the initial 'simple' search box. Even Google does this. Most users might not use it, but for power users it's awfully convenient. CQL would be one potential choice for a textual query syntax that can be entered in the initial search field. Jonathan Walker, David wrote: >> How about dispensing altogether with the >> basic/advanced dichotomy in a search interface? >> > > I'm not sure I can dispense with it completely, Peter. > > As Peter Morville said on the site Susan posted: "[I]t may be worth offering advanced features that are useful to a small yet important subset of users." I'll give you three guesses as to who my "small yet important subset of users" are, and the first two don't count. ;-) > > --Dave > ================== > David Walker > Library Web Services Manager > California State University > http://xerxes.calstate.edu > ________________________________________ > From: Code for Libraries [[log in to unmask]] On Behalf Of Peter Schlumpf [[log in to unmask]] > Sent: Saturday, November 15, 2008 5:45 PM > To: [log in to unmask] > Subject: Re: [CODE4LIB] Good advanced search screens > > How about dispensing altogether with the basic/advanced dichotomy in a search interface? Just create a well designed interface that's consistent and works well for all users. The basic/advanced dichotomy is really quite arbitrary, and exists in the mind of the designer. > > One thing that seems to be underappreciated these days is a straightforward and flexible search syntax. A command line in the search field may be a much more elegant and consistent solution than trying to make all options available and visible in a GUI. > > Make the basic features of the search interface clear and easy to use, but design the interface in such a way that more advanced users can easily "discover" the features they need as they use it. With this approach Basic and Advanced exist on a continuum. There's a little learning curve but all users will have the motivation to learn to use the interface to the level that satisfies their needs, and in the long run probably find it much easier to use. > > Peter > > Peter Schlumpf > [log in to unmask] > http://www.avantilibrarysystems.com > > > > -----Original Message----- > >> From: "Walker, David" <[log in to unmask]> >> Sent: Nov 14, 2008 4:48 PM >> To: [log in to unmask] >> Subject: [CODE4LIB] Good advanced search screens >> >> I'm working on an advanced search screen as part of our WorldCat API project. >> >> WorldCat has dozens of indexes and a ton of limiters. So many, in fact, that it's rather daunting trying to design it all in a way that isn't just a big dump of fields and check boxes that only a cataloger could decipher. >> >> So I'm looking for examples of good advanced search screens (for bibliographic databases or otherwise) to gain some inspiration. Thanks! >> >> --Dave >> >> ================== >> David Walker >> Library Web Services Manager >> California State University >> http://xerxes.calstate.edu >> > > -- Jonathan Rochkind Digital Services Software Engineer The Sheridan Libraries Johns Hopkins University 410.516.8886 rochkind (at) jhu.edu