Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Functional Area

Product Owner

Planned Release (if known)

Decision Reached


Fees/finesHolly MistlebauerPost-MVP

Holly created 2 JIRA issues:

UXPROD-2109: Allow for patron notices to be sent on request for manual patron blocks

UXPROD-2108: Expand patron blocks to allow blocking of borrowing by material/item type

Informational blocks will be handled by user notes


  • Blocks - Holly Mistlebauer

Q: Should patron notices be sent for manual patron blocks, whereby the block is set by someone in the library (because, for instance, we don’t have a valid address for them)? Should patron notices be sent for automatic blocks, whereby the block is set automatically by the system (because, for instance, they have exceeded a fine limit)?

Cornell indicated that they have never sent notices like this in the past? Chicago indicated that they would like this OPTION, but don’t want it to happen every time. Not needed for MVP. Holly reminded everyone that we can already display these blocks in the patron view in the discovery system if we choose to. In response to feedback from Chalmers, Holly clarified that blocks aren’t currently working in self-checkout because it’s not in the API, but this is a known issue that is being worked on. There’s also an issue with EDS, for which Chalmers will create a JIRA.

A: Holly will create a feature for post-MVP giving people the option of sending notices.

Holly also asked about two types of blocks that we haven’t previously discussed:

  • Informational block where nothing is blocked, you just want the patron's attention -- would this be a note or something else?
  • A way to block the patron from checking out laptops due to their bad past behavior with laptops.

Chicago indicated that OLE treats these as notes, not blocks. Erin and Jana from User Management will present to the RA SIG on this topic next week. The consensus in the SIG is that something that gets staff attention (such as a note) is needed, but it doesn’t need to be a block per se.

  • Claims Returned - Emma Boettcher

For claims returned items, does information entered into “additional information” field anywhere other than the comments on the loan itself (which is the only place it displays now)? For instance, should we write an automated note that appears on the user record? Consensus is that this would be a great feature, but is not needed for MVP.

When applying a “Lost” status, the option is given to “notify patron.” The SIG discussed whether or not this notification should include the notes entered in the additional information field and a consensus emerged that the functionality we want is to have the option to enter additional information for both the patron and staff (which might be different) to view. This definitely should be consistent across FOLIO.

  • Requests - Cate Boerema

The notetaker instigated a brief discussion of the reasons why patrons couldn’t be blocked at the point of placing the delivery request instead of at the point of checkout. Mainly, it is because things can happen between the time when the request is placed and when the item is ready to checked out, and these things happen often enough and are great enough significance that this should be avoided at all costs. The SIG was not able to think of an alternative to the solution Cate described in the agenda. The SIG indicated that by and large items with the new status “Awaiting Delivery” should have the same properties as an item “Awaiting Pickup.”