Meeting URL
Date
Attendees
- Maura Byrne
- Uschi Klute Klute
- Philip Robinson
- Björn Muschall
- Jana Freytag
- Catherine Smith
- jackie.gottlieb@duke.edu (Deactivated)
- Michelle Suranofsky
- Edd Merkel
Goals
Notetaker: Maura Byrne
- Welcome to Catherine Smith, our new member from the University of Alabama.
- Barcode management – do we want to keep a list of unique barcode numbers in FOLIO? Also, what should FOLIO do with a barcode when a user loses their ID? What if the user then finds their ID? (added by Maura Byrne)
- Notes, especially regarding tickets for external ID and departments
- Feature request for notes on records being displayed in pop-up or other contexts. (Steffi)
- Because this involves the Check in and Check Out apps, this may end up needing to be a feature request for RA to manage.
- Reviewing requirements that have been created and attached for Custom Fields ( - UXPROD-33Getting issue details... STATUS ) (Erin)
If we have additional time:
- Multiple Phone numbers - UIU-254Getting issue details... STATUS (Erin)
- multiple e-mail addresses - There is no JIRA for this? (Uschi)
- More topics from the Open Topics list
Action items from last meetings
- Patty will create a feature to add validation to the (required) e-mail field
(see also - LIBAPP-94Getting issue details... STATUS - but these proposals do not appear to have been implemented.) - Patty will file a bug or feature to have Expiration date and Status actually decoupled from each other. (also refering to - UIU-1255Getting issue details... STATUS )
- Patty creates a JIRA issue: The field Birth date is not validated, you can enter a date in the future.
- Patty suggests that Theodor Tolstoy presents the Chalmers SSO solution to us at one of the next meetings. Patty will reach out to Theodor to see about scheduling a time.
- Patty will file a feature to work on password rules. It's difficult to find out which character combinations are allowed → It's not userfriendly. Proposal: make the password strength configurable
- - UXPROD-242Getting issue details... STATUS 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.
- Patty will write a feature about Improving Search in the Users App so that it can be ranked.
- Patty will work on a story for preferred name/preferred pronouns - UXPROD-1790Getting issue details... STATUS ("New feature")
- Patty will write a Feature Request for the enhancement os User search (for exact match like "Li")
- Patty will create a feature request for deleting user data.
- Patty will ask Magda (the reporter on - UXPROD-1811Getting issue details... STATUS ) for a status. It may not be a UM-SIG issue.
Notes
Open Topics
Item | Who | Notes | Discussed Today? | Resolution / Next Steps | Carry topic? |
---|---|---|---|---|---|
Searching by specific fields | Erin | Right now Users has general keyword searching; we will want to be able to search specific fields - IDs, emails, addresses, notes? Perhaps one of these issues fits: - UXPROD-1015Getting issue details... STATUS - UXPROD-907Getting issue details... STATUS (New feature) - UXPROD-869Getting issue details... STATUS (Epic) - UXPROD-1941Getting issue details... STATUS (new feature) - UIU-1028Getting issue details... STATUS (Story) |
| Yes; this is not yet resolved. | |
Pop-ups on user transactions | Steffi | 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. |
| ||
Deleting User Records | Erin | Discussing the need for deleting patron records (no Jira currently; need for one discussed in comments of https://issues.folio.org/browse/UIU-1079) |
| ||
Password validation | Uschi | refering to Action Item "Create Feature for password rules" This is the story for the validation of passwords: - MODLOGIN-38Getting issue details... STATUS Some of the rules seem to restrict too much. We would like to configure the password strength. See configuration options in the ILS the GBV libraries use now (at the bottom of this page) | |||
Custom Fields | Uschi | 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. |
Password validation in the ILS of GBV libraries (called "LBS")
In our current ILS we can set these options:
# minimum length, default=0
# Maximum length, default=length of the newly entered password.
# Minimum number of lowercase letters, default=0
# Minimum number of capital letters, default=0
# Minimum number of digits, default=0
# Minimum number of special characters, default=0
# List of allowed special characters, e.g. /$%_-
# Unauthorized words separated by a comma. The user number is generally not allowed. Example: not,yet,or
Translated with www.DeepL.com/Translator