2020-10-12 Resource Access Meeting Notes

Override when request is not allowed for patron/item combination: https://folio-org.atlassian.net/browse/UXPROD-2649 Brooks proposed and entered this UXPROD. Let's discuss: - What should this look like? - What does it mean to flag the request as an override for audit trail/reporting? Etc

Meeting Outcomes

Functional Area	Product Owner	Planned Release (if known)	Decision Reached	Reasoning	Link to supporting materials	Comments
e.g. loans, fees/fines	Name	e.g. Q4 2018, Q1 2019	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue
Manual Patron Block Templates	Annika Schröer with help from Holly Mistlebauer	R1 2021?	RA SIG approved the mock-ups as shown in slide deck. Make it more obvious that you can't enter 2 of the template fields (if possible, sticking with the norm for other templates).	Use templates if you want, but don't have to.	Slide deck is here.	Annika Schröer will be PO working with the Leipzig Dev Team. Will come back to the RA SIG with questions and to show result.
Request overrides	Cate Boerema (Deactivated)	TBD	Should be a popup like when overriding loan policy (but with comments only, no due date selector) It should be possible to see that the request was created with override in the circ log along with the comments Ideally, we could display a filtered view of the circ log right on the request record If that's too difficult, we should have another way of displaying that the request was created through override and the override comment Comment could possibly be added as a staff note Definitely need separate override permission When ppl are creating circ rules, they need to make sure that, if they are thinking about allowing recalls via override, that they set up a notice policy that would send a notice (o/w patron would not be notified)		UXPROD-2649 - Getting issue details... STATUS	Cate Boerema (Deactivated) will update the uxprod with more details based on this conversation

Meeting Notes (David Bottorff )

FOLIO RA SIG Meting Notes October 12

Guest: Annika Schroder University of Leipzig joining Holly to discuss manual patron block templates

manual patron block templates - looking for approval fro RA SIG - Holly

not MVP, but Leipzig is interested in developing, Chalmers interested as well
current behavior includes description field and message to patron
if you have a standard block, you'll be typing in the same info again and again, what if you need to enter the same block many times
Allow manual patron block description, action, and message settings to be controllable via settings
Settings>Users>Patron Blocks>Patron Block Templates
Only required field = template name, optional code field
not able to enter staff only info or expiration date
in manual patron block creation, there is a template name drop down (optional) or just make a new blank one without using the template
can you edit fields pre-set by template? The template only helps you, the fields are not locked, they can all be edited
Kimi will check on styles for fields that cannot be filled in on template, some kind of reminder to staff as to why the boxes cannot be filled in per Andrea
Annika will be the PO for this feature
Next steps - approvals needed

Approval of mockups-consensus is that this is great, and wonderful that Leipzig took it up
Approval to save block code with user/block record for reporting purposes requested by Leipzig
Discussion with Reporting SIG to make data (including block code) available in LDP
Ability to make patron message and other parts of block available via API for display in discovery layer--what parts of block are available via API and should block code be made available?

We're hoping this model of a library partner easily submitting code will be a model moving forward
Allow override of prevented request (UXPROD-2649) Cate & Brooks

feature would allow staff to create a request even though not allowed by current policies
getting high ranking, so Cate wants clarification on what is desired
can loan policy override be used as a model/guide for handling request overrides? modal pop up that requires a comment, for example
overrides should be flagged as such for reporting, audit trail, etc.
action type is tracked in loan action history (Emma) "checked out with override" so something similar could be used for requests
but there is no request action history (would be non-trivial), perhaps could be captured in circ log (more general solution), then window to a filtered view of circ log
andrea - a flag for override for staff wihthout permissions to view circ log history would be a nice secondary feature per Andrea Loigman, but not as high priority
possible also instead of a flag that override could be a staff note comment (as a workaround), if window to circ log is not possible
Cheryl-make sure that recall notices are configured under notice policies so that an override for a recall request will include a notice in the notice policy, and possibly some kind of error message warning staff that recall notice will not be sent out (if recall notice is not configured)