Page tree
Skip to end of metadata
Go to start of metadata

Date

Attendees


Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia Andrea Loigman
10minSearchingAndrea Loigman

Cross-app searching - homework/thought exercise

UXPROD-858 - Getting issue details... STATUS

The cross-app sub-group (RM/MM) has been working on a feature they are now calling pre-order searching.  Does RA have any similar needs?

UXPROD-2243 - Getting issue details... STATUS


20minSearchingQuery search on Users and Requests (discussion continued)Follow up on User Searching:

1. Improved/"Fielded" searching in User app - https://issues.folio.org/browse/UXPROD-2092 and
2. Boolean/Query Search for Users - https://issues.folio.org/browse/UXPROD-1015

Per RA SIG discussion on 29-06-2020, Fielded search is more important than Boolean/query search. Can you please review your rankings? Boolean search is being ranked higher at the moment.

Per discussion last time, the most common use case is to search by user first and last name. Given that is now supported in the Keyword field, is Fielded search still must-have for go-live? If so, why? If not, ppl should review rankings.

How does this related to Advanced Search (Within Apps) https://issues.folio.org/browse/UXPROD-907? Is this feature redundant now?

Request Searching:

Last time we said that Requests should have fielded search for consistency and that, as with users, fielded search would be more important than boolean search. I have added a new UXPROD for this.

1. Improved/"Fielded" searching in Requests app - https://issues.folio.org/browse/UXPROD-2560
2. Boolean/Query Search for Requests - https://issues.folio.org/browse/UXPROD-2458


Let's discuss this solution, review the wireframes etc. Does this seem important? What types of searches might you conduct using this capability?


Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue














Notes 

  • Notetaker: David Bottorff (Chicago)
  • Andrea stepping down as convener after 4 years; Jana will take over as convener

    • Andrea will remain on SIG; timing of handoff not yet determined

  • Cross-app searching group has been working on pre-order searching as part of a larger cross-app searching need; Andrea and Erin met with subgroup.

    • Thought exercise: What examples of cross-app searching might be needed?

    • For example, pre-order searching would be great to see requests, item status, etc.

    • Are there other places we see a need for cross-app searching?

    • Cate-might be interesting to see demos of mockups/storyboards

    • Shoot Andrea ideas and next Thursday we can talk about it together, and will see if Dennis can join us for demo

    • Consider both cross-app within RA alone as well as cross-app for apps outside of RA

  • Are we meeting on Monday? YES

  • Cate-Improved fielded searching and Boolean searching in Users app

    • As of now ranking of Boolean is higher than fielded-you may want to revisit your rankings.

    • Are either of them critical for go-live? if keyword search by name, email, external ID all work Fielded includes explicit truncation

  • Requests what are the most important use cases for searching requests?

    • David: patron (patron barcode?), item barcode

    • Andrea: search by title

    • fielded explicit truncation is not as important in Users but still important

  • Advanced searching within apps, via query logic, etc.? is this old or redundent?

    • is this a pre-LDP concept?

    • Allows for boolean, etc.

    • we have SQL searching in inventory, and tickets in place for users and RA

    • We believe this is duplicative and can be closed