Interface Draft: Advanced Search

MPDL

The following page is a interface draft for a redesign of the advanced search functionality in PubMan. Please mind that this is a abstract GUI draft. It is not done to define a detailed level but serves as a base for further discussions.

=New Design Advanced Search=

Requirements

 * The first page displays the advanced search without scrolling
 * Most common search terms are always visible and easy accessible
 * Complexity only on demand
 * More specific/ rarely used search terms can be added by the user
 * By default boolean operators between search terms are AND, the user can choose to alter the default value

Functional Prototype
A functional prototype of the new Advanced Search can be found here: AS Prototype

Additional Information

 * Organization is renamed in Affiliation. A Button "Tree view" is added to enable selecting an organization out of the organization tree
 * The identifier search field is divided into a selectbox identifier type and a text field for the identifier value
 * Checkboxes: for every checkbox group exists a button for selecting All or None, (the label changes dynamically, contextually)
 * The user gets the opportunity to change all boolean operators between the parameter groups from all (AND) to any (OR)
 * The user gets the opportunity to enter boolean operators in the search string of a parameter (e.g.: Person: Müller AND Meier NOT Maier)


 * Which function is triggered by "show boolean"? --Inga 16:14, 20 October 2008 (UTC)
 * The "show boolean" button reveals the boolean operators between the different search boxes (like it is now in pubman). For default the boolean connection between the boxes is AND, when the user clicks the "show boolean" button the operators are visible so he can perform a more complex search.--Kleinfercher 15:01, 23 October 2008 (UTC)

=Preceding Thoughts=

Current Approach
The old approach was discussed during a workshop with librarians and scientists. The main drawbacks are:
 * too extensive
 * open/close buttons not used
 * very different to existing solutions

Main Questions
In how far should dynamic/detail/complexity be separated from static/most used/easy.



Examples of other solutions were discussed and the idea of a more condensed one was roughly sketched as an outcome. To start with we propose to decompose the old approach and see what components could be generalized. Using those existing components will allow a fast and easy approach with a minimum of functional changes.





The following abstract scheme is used to discuss varieties (terms are only used here):




 * 1) Type: The criteria like (Persons, Word or Phrase)
 * 2) Input: Most of the types require text input.
 * 3) Options: All checkboxes
 * 4) Actions: Mostly buttons like (Add, Clear form, ...)

Examples:
 * http://pubs.er.usgs.gov/usgspubs/index.jsp?view=adv
 * http://edoc.mpg.de/search.epl
 * http://www.sciencedirect.com/science?_ob=MiamiSearchURL&_method=requestForm&_btn=Y&_acct=C000004898&_version=1&_urlVersion=1&_userid=46021&md5=0a8321eb63f6681c81d0e259d51b8f8e
 * http://www.springerlink.com/find.mpx
 * http://publica.fraunhofer.de/starweb/pub08/servlet.starweb

Preconditions

 * 1) The first page displays the advanced search without scrolling
 * 2) The most used criteria is displayed primarily. Other criteria is shown on demand.

New Approach
Strictly separated static/dynamic





Pros:
 * Easy to use for most cases
 * Complexity only on demand
 * Extensible

Cons:
 * The user can`t see on first sight what he can search for

Open Questions
How can we design the input options for the increments?
 * Minimum space
 * Maximum information of further search options

We will go with Buttons/Links --Friederike

Boolean Search only on demand?
 * Button show boolean/hide boolean (This would be conform to the idea to show less important information dynamically/only on demand)

Decided: default no boolean, boolean operators are shown when pressing a button --Friederike


 * You may want to add the "show boolean"-function to the abstract prototype --Inga 16:12, 20 October 2008 (UTC)


 * Please note that we could reduce the functionality provided with this "advanced search" interface, if we consider to recommend/document the SRU interface to enable "power users" with complete control of their search requests. --Inga 16:01, 20 October 2008 (UTC)

Statistics of eDoc Searches
Word or Phrase: 77,59% Date:           25,42% Person:         21,64% Organization:   15,58% (SubUnitSearch:12.64, SubsubunitSearch:2,67)