/
2025-11-03 Cross App SIG Meeting notes

2025-11-03 Cross App SIG Meeting notes

 Date

Nov 3, 2025

Attendees

  • @Tara Barnett, Laura Daniels, Alissa Hafele, Vivian Gould, Kristin Martin, Martin Scholz, Maura Byrne

Homework

Housekeeping

Recording: https://recordings.openlibraryfoundation.org/folio/app-interaction-group-mondays/2025-11-03T12:00/

 Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

5 min

Announcements

 

 

Search and Standards Documentation

 

  • Our next actions for search standards documentation:

    • Agree the list of behaviours we want to document ← let’s finalize this today.

      • We note that we do not actually need to do the analysis in order to complete this step (we do not actually need to know how every search functions). We merely need to identify the behaviors.

        • The list:

          • Keyword/All Search - what fields does Keyword Searching cover, and notes about how it works → change to “Default Search Fields”. This should be included in all documentation.

          • Keyword Search Behavior (as opposed to Phrase search) → identifies the behavior of non-phrase searching

          • Phrase Search - can you do an exact phrase search? How? →

          • Whitespace - how is whitespace handled? Are double spaces ignored, for example

          • Wildcards - what wildcard characters, if any, are used, and how do they work?

            Case Sensitivity - are searches case sensitive?

          • Anchoring/Truncation - Are searches left anchored? Do they include partial matching?

          • Punctuation/Diacritics - how are punctuation and diacritics handled? (Ignored?)

          • Stop Words - does searching make use of any stop words?

          • Escape Characters - are there any escape characters that allow you to search otherwise special characters, such as a wildcard character?

      • Should there be a matrix/table to help with keyword vs phrase searching? Should there be a matrix for individual differing field behavior?

      • Should we add a “see more” link?

    • Reach out to stripes team to see what would be involved in developing a component (assuming they agree a component is the right approach)

      • Who can do this?

    • Present to POs for feedback

      • Who can do this?

Notes

  • We confirmed that we are cancelling our meetings on November 17th and 26th. Additionally, we will cancel December 24th and 29th. These have been removed from the calendar.

  • We finalized a list of search behaviors we want to document (see above). In particular we discussed:

    • Confusing terminology surrounding the word "keyword" in reference to this project. In some cases it is in opposition to phrase searching, and in others it describes what fields are being searched. We decide that "Default Search Fields" would make this clearer.

    • We have questions about what is "assumed" about phrase searching. For example, does it include text exactly as written, including case sensitivity and double spaces? In any case, we agree that documenting phrase search is valuable.

    • We acknowledge that there's going to be an issue where whitespace behavior may differ between keyword and phrase searching. We aren't sure if we need a table, or if a list is sufficient. We want to keep this relatively simple.

    • We note that we only want to require the categories that are pertinent to the app. That may only be "Default Search Fields"

    • We confirm that we are creating unique pop-ups for each app, not a shared modal.

    • We note that it is likely that a "see more" link that goes directly to the docs would be useful.

  • The next two outstanding steps are:

    • Reach out to the stripes team

    • Present this to the POs for feedback.

 Action items

Post our final list somewhere central
Figure out how to do the next two steps.