Skip to end of banner
Go to start of banner

2020-08-10 Resource Access Meeting Notes

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

Date

Attendees

Joanne Leary

Emma Boettcher

Elizabeth Chenette

Brooks Travis

Cornelia Awenius

Mark Canney

Cheryl Malmborg

David Bottorff

Kimie Kester

Holly Mistlebauer

Andrea Loigman

Monica Arnold

Darcy Branchini

Laurence Mini

Molly Driscoll
Cornelia Davis

Donna Minor

Schwill, Carsten

Jana Freytag


Discussion Items

TimeItemWhoDescriptionGoals/Info
2minAdministrivia 
30minCirculation logFollow up on: Decide what actions and what information about those actions relevant to requests is worth recording in circ log
20minNotices & Circ logDecide how to display notices that were sent for multiple items in the circulation log


Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

e.g. loans, fees/finesNamee.g. Q4 2018, Q1 2019Clearly stated decision
  • Because...
  • Because...
e.g. mock-up, JIRA issue




























Notes 

Emma Boettcher

  • Needs more feedback related to the circulation log.
  • Related to requests, which information should be included in the circulation log?
    • Created: can choose from type, expiration date, position in queue, fulfillment preference, pickup service point/address type
      • David Bottorff : thinks fulfillment preference and type would give vital information to discern whether or not he needs to click into the request for more information.
      • Andrea Loigman : agrees with those information points, add to that the pickup service point/address type. Would love all information, but thin thread would be type (hold/page/recall), pickup service point/address type (can help infer fulfillment preference), fulfillment preference.
      • Expiration date and position in queue are less essential because many institutions set expiration date far in the future and current queue position is typically more useful than snapshot queue position at creation.
    • Cancelled: should reason for cancellation and additional information be included in the log or just a click away?
      • Andrea Loigman : thin thread should be reason for cancellation; additional information can be a click away. What is the information I need to see in a group (sorting, etc.) versus what do I need to know about a single request?
      • Joanne Leary : agrees that cancellation reason is most important info point here. 
      • David Bottorff : is there a distinction between a cancelled request before it's on the hold shelf versus after? Emma doesn't think there is, but will check with Cate.
      • Emma Boettcher : what's needed for thin thread: cancellation request, type, pickup service point/address type
    • Moved: when viewing the circulation log, do you want to see the requests moved to a particular item or moved from a particular item?
      • Emma Boettcher : whichever item displays in the item ID column (new or old), potentially the opposite item ID (new or old) could be displayed as information in the log description itself.
      • Brooks Travis : is there an option to drill down to a specific request ID to see all actions on that particular request? - Emma will check.
  • No labels