2019-01-24 Metadata Management Meeting notes

Former user (Deleted)

Search enhancements - link to slide deck: https://docs.google.com/presentation/d/1Z3IgcTtBd5nb8ODOOMr5D_LLvOqo-_Udo7SwDOj1NyU/edit#slide=id.p

Working group - wiki page: Search enhancements / Advanced Search

• See the details in the slide deck
• Work will be handled by Stripes Force, and maybe some of the other dev teams
• When we talk about search, where are we talking about? Across all apps, though in phase 1, it might be a single app for proof of concept, or may have to be rolled into the individual apps over time

Refactor routing architecture: Kahlilah Gambrell explained that the current routing architecture is not optimal for the scale we need. It is becoming a limitation in many ways. Timeline of refactoring? Answer: Gathering requirements is helpful to this work. It could be done in parallel with working groups. There is a team that is beginning to work on this.

Improve Search and Filter pane UX: Right now, it can only support check box display, which interferes with long lists that can come up in filtering. Instead, they are developing a multi-select box. Any app can control default display now. Re-ordering filter groups is now available. Charlotte voiced the need to have a hierarchical display. Ann-Marie asked if these are completed and available? Kahlilah said it is a mix: some features are planned and some are currently in progress. The "Improve Search Filter pane UX" is available now.

Boolean/Exact Phrase support: Currently only happening in Eholdings and MARCCat. This will occur in a phase approach. They will work in conjunction with apps that are supporting Boolean functions already.

Search/Filter tags: No development has begun. This is important for Chalmers.

Felix (via chat): "Is all this work happening under a specific SIG or Sub Group?"
Ann-Marie (via chat): "I think it crosses many groups; this is general infrastructure"
Charlotte (via chat): "The MM-SIG ‘own’ the requirement for search in Inventory (UXPROD-140), and input/requirement for the general use of Search and filter pane"

Advanced Search Page: This is an idea that they would like to discuss with groups. Ann-Marie is very interested in this for the use of tags.

It was noted by some members that Filip spent some time with members of the MARCCat group to work on features of an Advanced Search Page.

Patty: "Would this be a problem of being able to search by barcode number or item since that is a separate index. Charlotte said they had a barcode search, it was deprecated, she is not sure if it is back again.

Felix asked if an "AND/OR" search will be available in the Boolean search. Right now it is an "OR" search by default. Charlotte said it is possible to perform an AND search.

Ann-Marie mentioned searching by date ranges and price ranges are important for Acquisitions. Kahlilah said they are working on a range component app to support searching by range.

Question from Cornell (via chat): "Khalilah, is your drop-down list representing only languages with available material, or all languages possible?" Answer: Not sure if these represent the languages of the available materials or all possible languages. Charlotte thinks it should express the available languages.

If group is aware of issues tied to routing and developing of functionality and features needed, please link user stories to the issues like this: (e.g. https://folio-org.atlassian.net/browse/STCOM-302)

Laura mentioned that a working group will be formed next month that will hopefully provide feedback to Kahlilah.

Felix Hemme

Theodor Tolstoy (One-Group.se)