Uploaded image for project: 'SimplyE 2.0'
  1. SimplyE 2.0
  2. SIMPLY-3661

Implement new library search algorithm

XMLWordPrintable

    • SIMPLY S9 April 27 - May 11, SIMPLY S10 May 11 - May 25, SIMPLY S13 June 22 - July 6, SIMPLY S14 July 6 - July 20, SIMPLY S15 July 20 - Aug 3, SIMPLY S20 Sep 28 - Oct 12
    • 13

      This ticket is for handling a search query typed in by an end-user, not for matching a specific geographic point to a list of libraries.

      The new library search algorithm is defined in the Technical Approach Document. Highlights:

      • We only interpret the search input as a name if we're not able to find a matching geographic location.
      • We run two geographic searches: one for local libraries and one for supralocal libraries. At most one supralocal library will show up in the search results.
      • We return at most three search results. (We may not be able to stick with this in all cases, but that's the initial plan.)

      The TAD also gives a large number of motivating examples which should guide implementation.

        1.
        		 Normalize inbound location data Sub-task Ready for QA Nick Ballenger (Inactive)
        2.
        		 Standardize request-derived Library, Location via decorators, Flask global scope Sub-task To Do Nick Ballenger (Inactive)
        3.
        		 Tokenize user-supplied search strings Sub-task Won't Do Nick Ballenger (Inactive)
        4.
        		 Use tokenized search string and derived Location to return Libraries Sub-task Won't Do Nick Ballenger (Inactive)

            NickBallenger Nick Ballenger (Inactive)
            leonardrichardson Leonard Richardson [X] (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: