[Koha-bugs] [Bug 8962] Create a new index for OPAC simple search, more specific than "any"

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

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

--- Comment #1 from Jared Camins-Esakov <jcamins at cpbibliography.com> ---
It may be preferable to use Any for the new index, and convert the old index to
Anywhere. From the Attribute Set Bib-1 Semantics document
(http://www.loc.gov/z3950/agency/bib1.html):
Any                  1016  The record is selected if there
                           exists a Use attribute that the
                           target supports (and considers
                           appropriate - see note 1) such
                           that the record would be
                           selected if the target were to
                           substitute that attribute.
       Notes:
        (1) When the origin uses 'any' the intent is that the target
            locate records via commonly used access points. The target
            may define 'any' to refer to a selected set of Use
            attributes corresponding to its commonly used access points.
        (2) In set terminology: when Any is the Use attribute, the set
            of records selected is the union of the sets of records
            selected by each of the (appropriate) Use attributes that
            the target supports.

Anywhere             1035  The record is selected if the
                           term value (as qualified by the
                           other attributes) occurs anywhere
                           in the record.

            Note: A target might choose to support 'Anywhere' only in
            combination with specific (non-Use) attributes. For example, a
            target might support 'Anywhere' only in combination with the
            Relation attribute 'AlwaysMatches' (see below), to locate all
            records in a database.

       Notes on relationship of Any and Anywhere:
        (1) A target may support Any but not Anywhere, or vice versa, or
            both.  However, if a target supports both, then it should
            exclude 'Anywhere' from the list of Use attributes
            corresponding to 'Any' (if it does not do so, then the set
            of records located by 'Any' will be a superset of those
            located by 'Anywhere').
        (2) A distinction between the two attributes may be informally
            expressed as follows: 'anywhere' might result in more
            expensive searching than 'any'; if the target (and origin)
            support both 'any' and 'anywhere', if the origin uses 'Any'
            (rather than 'Anywhere') it is asking the target to locate
            the term only if it can do so relatively inexpensively.

-- 
You are receiving this mail because:
You are watching all bug changes.