Discussing the following Jiras which did not make the CAP plan.
The UM SIG agrees that this is not important for MVP.
Meaning of CAP comment is unclear. Björn: Perhaps if a field is not delivered (=empty), it will not be overwritten. Phil: But you might want to remove a field in FOLIO during import.
Result / Action item: Patty will ask the CAP plan group for feedback. Erin will work with Patty to write a user story for a "thin thread" v.1 of this - a flag or checkbox on record, that if checked, would cause a record to not be updated.
UXPROD-33 is important for Duke. Was put on hold when the Custom Fields were marked for MVP. But now CF are non-MVP.
Patty: meanwhile the CF development team was given other tasks. Notes could be used as an alternative to CF.
Erin: What about the National Library of Florence? They need CF for their FOLIO migration. Consensus - no need for specific reaching out, presumably they are seeing some information we are.
can be closed.
Result / Action item: Erin added a comment to the Jira since Cate Boerema was the reporter suggesting that it be closed.
For Q1, only a few issues will be planned; the focus will be on testing, bugfixing and stabilization.
So we did not identify any issues that needed to go back to CAP plan, other than seeking clarification on UXPROD-242 comment. Erin heard from Holly Mistlebauer after the SIG meeting that she was working on getting feedback on that comment.
User search facilities (Uschi)
Briefly scanned notes from Uschi and her test results. Erin is hoping to do some additional testing specifically about patrons with short last names.
Action item - Patty will write a feature about Improving Search in the Users App so that it can be ranked.
postponed to next meeting
Resolution / Next Steps
Searching by specific fields
Right now Users has general keyword searching; we will want to be able to search specific fields - IDs, emails, addresses, notes?
Erin to discuss with RA SIG requirements for fielded searching
Erin to investigate a searching
Yes; this is not yet resolved.
Pop-ups on user transactions
notes may be used for communication about users, and pop-ups on user transaction (or displaying of notes) is desired. Khalilah indicated this should be raised as a new feature request.
May need to be raised with RA SIG
Bulk User import
Does anyone know (or can tell me) what the current, supported approach is (or will be) for bulk importing user records? I can see a github for mod-user-import, jiras for that project with comments that ask if that mod is still being supported. |I can see a very old jira (https://issues.folio.org/browse/MODUSERS-3) for bulk-loading that was last updated last year.I can see a very old jira about performance improvements (https://issues.folio.org/browse/MODUIMP-4) that was last updated last
Patty to ask for info / updates from Ebsco staff while in Sweden next week
Yes; may need additional discussion in group as we go.
the tag cap-mvp has been removed - reason? Further activities?
The tag was removed, and this was dropped from the MVP due to capacity (discussed at RA SIG meeting)
We can and probably should review the requirements that Khalilah has generated; they are attached to the master Jira.
Discussion on PIN needs for user records
Important to discuss - Because the entry of an account password (e.g. university login) in a public space, e.g. self-checkout is not very protective. The input, especially in vertically hanging touch screen monitors, is not protected from the view of others behind me. Also, if I feel someone has been watching me, I can simply change my PIN without having to change my account (university) password. This provides extra security. The principle should be the same as with a bank card, where the account password and card PIN are different. We'd all be surprised if it wasn't that way with our bank, I think. Leipzig does not need this urgently, because we need at least another 2 years for go-live. But in the long run all Saxon libraries need this.
Multiple Patron Identifiers
Additional patron identifiers will not be in the MVP(?). Conversation turns to custom fields and wondering if they are searchable. Will custom fields work for multiple user identifiers?
Patty & Erin will work on users stories for:
Repeatable ID Field which must be 'nameable'
User stories have been written. We can probably drop this from our list of ongoing topics.