Item Location and Collection Filtering

In Webpac, you can filter your keyword searches by Location and/or Collection by simple modifications to

STEP 1.
Add the Location Search Use attribute (3008) and Collection Search Use attribute (2002) to the Connection CFM file used by WebPAC.

 WebPAC 1.2, Connection CFM, Search Types Section
  # Name Qualifier Category Use Structure Truncation Relation Position Completeness Scannable Normalize  
  Location, LFIL, 0, 3008, 2, 100, 0, 0, 0, 0, 1,  
  Collection, CFIL, 0, 2002, 2, 100, 0, 0, 0, 0, 1,  

 WebPAC 1.3, Connection CFM, SearchAttributes Section
  // Name Qualifier View Category Scannable Normalize Attribute Set ID   Use Structure Truncation      
  [Location, LFIL, BRIEF, 0, 0, 1, BIB1,  [  [1,3008,] [4,2,] [5,100,]] ]
  [Collection, CFIL, BRIEF, 0, 0, 1, BIB1,  [  [1,2002,] [4,2,] [5,100,]] ]
Note that in WebPAC 1.3 the Z39.50 attribute type/value pairs, surrounded by square brackets, are usually placed on a separate line, and the closing bracket on a third.

  • The Use attribute number for Location Filtering is always 3008 and the Use attribute number for Collection Filtering is always 2002, so nothing needs to be added to the Z39.50 sort file,
  • the Structure attribute number is set to Keyword (2), since search filter restrictions only apply to keyword indexes, and
  • the Truncation attribute is the value for disabled (100).

STEP 2.
Determine the Location codes and Collection codes to filter by.

You can list the Location codes and Collection codes by using SQL statements against your database, or by using the Horizon Table Editor to open the "location" view for the Location codes and the "collection" view for the Collection codes. For example,

STEP 3.
Modify the HTML Search Template file to include the case-sensitive Location and Collection Filter Qualifier codes you added to the Connection CFM file, and all the Location codes and Collection codes that you want to filter by.

This usually involves adding a select list or drop box containing the Location code options and another select list or drop box containing the Collection code options to the template file. For example,

     WebPAC 1.2, Search Template
    <font size="-1">Limit Keyword Search by Location:</font><br>
    <select name="LFILTER">
        <option value="">None
        <option value=" and main.LFIL.">Main Library
        <option value=" and med.LFIL.">Medical Library
        <option value=" and law.LFIL.">Law Library
    </select>

    <font size="-1">Limit Keyword Search by Collection:</font><br>
    <select name="CFILTER">
        <option value="">None
        <option value=" and mainstx.CFIL.">Main Stacks
        <option value=" and music.CFIL.">Musical Recordings
        <option value=" and ref.CFIL.">Reference Books
    </select>


     WebPAC 1.3, Search Template
    <font size="-1">Limit Keyword Search by Location:</font><br>
    <select name="LFILTER">
        <option value="">None
        <option value=" and LFIL main">Main Library
        <option value=" and LFIL med">Medical Library
        <option value=" and LFIL law">Law Library
    </select>

    <font size="-1">Limit Keyword Search by Collection:</font><br>
    <select name="CFILTER">
        <option value="">None
        <option value=" and CFIL mainstx">Main Stacks
        <option value=" and CFIL music">Musical Recordings
        <option value=" and CFIL ref">Reference Books
    </select>


STEP 4.
If necessary, modify all occurances of the value of the Search Query Command HTML Tag (the tags having the name "SCMD") within the HTML Search Template file, to include the name of the HTML Select Tags used for filtering, formatted as $${tagname}. For example,

    <input type="Hidden" name="SCMD"
      value="${RUNKEY} ${SESSIONKEY} $${QUERY} $${INPUT} $${LFILTER} $${CFILTER}">

 


Copyright © 1999-2000 epixtech, inc. All rights reserved.
Please email any comments, questions & suggestions to p.roberts@epixtech.com