Were there discussions with the RA SIG around who can be a sponsor?
Do we want an auditory signal when the Proxy Modal pops up to alert the circ desk operator that they need to do something (in case they aren't looking at the screen)?
For the borrower data, let's not use "Institutional status" as the label for what's called "Status" in User Details. We should be consistent.
Status questions
Pushback on changing API from Active Y/N because this is Boolean.
Are we okay with a discrepancy here between UI and API?
Yes, because it really isn't that ambiguous
We aren't labeling status consistently in the UI right now. How do we want to deal with this?
Users app filter should say "Status" not "User Status"
Users app search results column should be "Status" with values Active and Inactive instead of the checkmark
User details page should be Status and values should be Active and Inactive (they need to be capitalized and aren't at the moment)
On Checkout, we want to change Institutional Status to just Status.
Expiration date and status -If a user is manually set to inactive and then the user record expires, when the expiration date is updated, should the user record automatically become active or do we need to remember that it was manually set to inactive and retain that state? Do both of these data elements usually come in on the import feed or just the expiration date?
Manually changing status seems like an edge case, but we can check with RA SIG
Given that, let's do what's technically easiest and just document it well
Patron group
Do we want to display the description in the Patron group selection menu?
Yes this could actually be useful to capture nuanced differences between, say, a Graduate student, a Management student and/or Guest patron type 1, 2 and 3
It may be a challenge to display much of a description in the menu, but Kimie Kester will look into it
In the meantime, if we keep the separate edit screen, let’s make sure the fields are laid out in the same format as the view mode (the section headers do not need to be displayed in view mode, however)
Most have been addressed ("closed") with the exception of the Status one which we discussed
Cate will enter stories for the changes we discussed to the Status labeling in this meeting
Plan for next week
Review Kimie's suggested changes to the Address component
Get a demo of where FOLIO development is now
Possibly review more wireframes (e.g. Loans and Loan details, Requests etc)
Goal is to align around last changes to the Users app and then implement those changes so we can get it out to the SIG for user acceptance testing (UAT)