RFC Advanced Patron Search

Problem

The ability is needed to search for patrons on many different fields, including email address, street address, phone number, etc. Using additional patron attributes is not a viable solution as it would require a tremendous amount of duplicate data on all fields that would need to be searchable.

Solution #1

Create a standard search API that functions for both circulation and patron searches and supports the ability to search on many different fields.

Solution #2

Create a member search API that supports the ability to search for patrons on many different fields.

Technical Notes

  • Advanced search should include the following fields
    • Surname
    • First name
    • Date of birth
    • Patron #
    • Guarantor Surname
    • Guarantor First name
    • Address
    • City, state
    • Zip/Post code
    • Each type of phone number
    • Each type of email
    • Card number
    • Patron Category
    • Any searchable additional patron attributes
  • When a Staff member clicks on the Patron menu item, they should immediately be taken to the advanced search screen, which could exist below the browse by last name. This display would be in a similar format to what Staff see when they click on the Search menu item.

Related Enhancements

  • Create a system preference for what fields the quick search searches. The creation of an advanced patron search would allow for the separation of searchable additional patron attributes and the quick search box because searchable additional patron attributes would be searched using the advanced search.

Comments

 
en/development/rfcs3.2/rfc32_advancedpatronsearch.txt · Last modified: 2008/09/02 07:19 by danny.bouman
 
Except where otherwise noted, content on this wiki is licensed under the following license:CC Attribution-Noncommercial-Share Alike 3.0 Unported
Recent changes RSS feed Donate Powered by PHP Valid XHTML 1.0 Valid CSS Driven by DokuWiki