1-24-2020 - Joint UM and RA Meeting at WolfCon 2020

Owned by (OLD ACCOUNT) Erin Nettifee
Last updated: Jan 29, 2020
2 min read


  • Patty facilitated, and began by demo-ing the RA app. We had a number of attendees.
  • Question - will fielded search be available? Right now search is very basic.
    • There is a feature for search improvements -  UXPROD-2092 - Getting issue details... STATUS
  • Creating Users Directly
    • Barcode does basic duplicate checking
    • Barcodes are not case sensitive.
    • Known issues with expiration date on account and connection to active/inactive settings.
  • Lots of discussion about requirements in the UI and requirements on the back end
    • They do not match - the drift has occurred probably for a while and is an issue in multiple apps, not just users
    • Example - in bulk load, username and password aren't required, so password can be left blank. In UI, if you put in a username, you have to put in a password. If bulk loaded w/o password, prompted to send password on UI view.
    • Brooks - API is only requiring two fields - last name and ID - but system will generate the ID.
  • For libraries using SSO, SSO will have to hit something on the user record. 
    • May be a need to prioritize External System IDs or to change password validation options (or both)
  • Everyone gets the option for hold shelf - you can't unselect it right now.
  • Addresses
    • Some libraries are considering not putting physical addresses in.
    • Might be a need for faculty delivery; definitely a need for notices to print.
  • Proxy/Sponsor - discussion about expiration dates - as far as we know it's working.
    • Also discussion about levels of responsibility - you can give different levels of access to someone (request for sponsor, notifications) 
  • Permissions
    • Patty - testing of permissions is really needed. UM has discussed persona exercises, and sharing information about permissions sets so others can see them and not have to reinvent the wheel. (I wonder if we should pre-emptively set up documentation for this in the wiki, or in the tips & tricks section.)

    • Andrea - asking about restrictions on log-ins. There are no restrictions. We need to understand audit behavior since that's not available - will there be something in the LDP?

    • Not having a permission can behave strangely - Patty's test account didn't have loan permissions - so the loan link from check out opened oddly. UX guidance says no permission = hide the option, generally, but it can lead to confusion. Will need to be a consideration for support at early adopter libraries in terms of troubleshooting.
    • Discussion of override for loans - which in FOLIO context is overriding a loan policy - Checkout - all permissions allows for checkout of circulating and non-circulating items, but checkout - circulating items doesn't allow for the override.
  • Anonymization
    • Lots of confusion about how it is working and what is retained or not retained. 
  • Discussion of user fields
    • Strong needs still for both department field and statistical categories. 
    • Custom Fields also really needed - Khalilah discussed current state. Back end is done for its initial work. They are working on making sure custom fields are supported in bulk import.
    • They are also working on the front end for custom fields and hope to have it this quarter with basic field types.
    • Andrea - department has other needed logic, like determining delivery eligibility and setting service points. 
    • Patty & Khalilah will consult on question of state of custom fields and Patty will provide an update.