Skip to end of banner
Go to start of banner

2021-10-27 Meeting notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

Date

Attendees

Goals

  • Discuss use cases for extending Elastic Search for users
  • UM-SIG representation on bulk edit working group
  • Bugfest comments and issues (patron count not working)
  • What, if anything, happened with the ticket for counting active patrons in a calendar year?

Discussion items

TimeItemWhoNotes
35 min.Use Cases for Elastic Search 

Elastic Search could allow for faster searches, retrieval of counts of the search results, and more comprehensive searching. It would solve the issue of counts over 1,000 not being accurate. Requests make the best use case for Elastic Search, as these include barcode, patron name and patron group information. Elastic Search would also make searching custom fields easier and faster. Consensus of the SIG was that Elastic Search would be nice to have, but is not a high priority. Permissions Re-design was viewed as a much higher priority.

5 min.Interfile of Diacritical characters
Brief discussion on whether we need to look at how diacritics such as œ, æ are interfiled alphabetically. Do we need this to be done the same way in the U.S. as in Germany, for example?
10 min.Representation on the Bulk Edit Working Group
Erin Nettifee has expressed concern about being the only representative from Users or RA on the Working Group. Greater representation would help User / RA issues receive more attention / weight. Anyone interested in joining can contact Patty via Slack. The group meets biweekly Tuesdays at 9 am U.S. Central Time.
10 minPatron count limit issue
Counts greater than 1,000 in patron groups are completely inaccurate, which is highly misleading for those not aware of this issue. This problem should be fixed when Elastic Search is implemented. For now, a fix would be to have counts over 1,000 replaced by "greater than 1,000". Brooks also suggested implementing an automatic second 'Limit=0' query to populate the count. Brooks felt this would not cause significant slowdown issues, but for institutions with very large numbers of users, having this be an option would be advisable.
2 minCount Active Borrowers in Calendar Year

Some of the German institutions were especially desirable of this feature. It was agreed to bring this up at the next meeting. See UXPROD-2569 - Getting issue details... STATUS

Action items

  •  
  • No labels