[Koha-bugs] [Bug 7031] More options for AdvancedSearchTypes

[bugzilla-daemon at bugs.koha-community.org]

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7031

--- Comment #5 from Ian Walls <ian.walls at bywatersolutions.com> 2011-10-15 17:04:27 UTC ---
Created attachment 5899
  --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=5899
Proposed Patch

Adds the ability to perform advanced searches in both the OPAC and staff client
on more than a single AdvancedSearchType at a time.  Support included for
Itemtype, Collection Code and Shelving Location, but other item fields are also
possible.

AdvancedSearchTypes syspref preference is repurposed; no longer a single value,
it can now take multiple item code fields separated by "|".  The order of these
fields will determine the order of the tabs in the OPAC and staff client
advanced search screens.  Values within the search type are OR'ed together,
while each different search type is AND'ed together in the query limits.  The
current stored values are supported without any required modification.

Each set of advanced search fields are displayed in tabs in both the OPAC and
staff client.  The first value in the AdvancedSearchTypes syspref is the
selected tab; if no values are present, "itemtypes" is used.  For non-itemtype
values, the value in AdvancedSearchTypes must match the Authorised Value name,
and must be indexed with 'mc-' prefixing that name.

<li> elements in tab are assigned unique IDs, so the text of the tab can be
altered to match the library's needs (using JQuery).  Unsupported search values
have the same default text, but still get unique IDs based on their search
index.

The logic to handle the 5 element row limit has been moved from the Perl to the
templates, since Template::Toolkit has a simple method for extracting the count
of an element in a loop and performing 'modulus' on it.

-- 
Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.