2021-08-25 Meeting notes
Date
Attendees
- Maura Byrne
- patty.wanninger
- Uschi Klute
- Cammie Wyckoff
- Magda Zacharska
- Philip Robinson
- Björn Muschall
- Matthew Harrington
- mey
- Andrea Loigman
- Nancy Burford
Goals
- Review user record fields priority that need to be supported by the Bulk Edit:
- Wildcard searches
- Patron blocks (search criteria and edits)
- Other?
- Review delete limitation:
- Open unexpired proxy
- Open loans
- Open fees/fines
- Open requests
- Other?
- Permissions:
- Who should have access to the bulk edit app?
- Should edit and delete functionality require the same permissions or should be separated?
- Concerns related to data privacy
- Other?
Discussion items
| Time | Item | Who | Notes |
|---|---|---|---|
| 5 min | Note taker | Maura | |
| Review user record fields priority | Magda | It's recommended that we focus our rankings and use cases on things that we don't have/don't like in our current system. Also, functions that we do like, and would like to keep. Use cases that we discussed are included in the document. | |
| Edits to permissions | Magda | Should we do bulk edits to permissions? That would be better served by editing permission sets. It would be terribly useful to be able to search by permissions, to get a list of people assigned to a permission. Perhaps it would be helpful to search for the students assigned to a permission set, and removing that permission set once the student records have expired. | |
| Wildcard searches | Magda | Should a wildcard search be anchor-left or anchor-right? That would depend on the data being searched. Using a "contains" search may solve that question. | |
| Search by patron blocks | Magda | There is value to being able to search by patron blocks. |