2018-09-27 Resource Access Meeting Notes

Date

27 Sep 2018

Attendees

• Andrea Loigman

• Schwill, Carsten

• Jana Freytag
• Sharon Wiles-Young
• Tania Hewes
• Kimie Kester
• Emma Boettcher
• Darcy Branchini
• Cate Boerema (Deactivated)
• David Bottorff
• sthomas (Deactivated)
• Holly Mistlebauer
• Joanne Leary
• William Weare
• Adam Shire
• David Larsen
• Rameka Barnes

Discussion items

Notes

• Service Point and Shelving Location relationships
• which service point should be primary triggered the discussion
• every location should have a service point? The answer seems to be yes
• we should add service points to a location
• can we handle this via inheritance? the answer right now is no
• The manual setup of hundreds of locations and assigning at least one service point will be onerous. Could this be a migration issue in the future?
• the ability to clone a location for moving forward as a step moving forward?
• issues surrounding operating hours, fees, postal addresses, etc.
• table for now and do a loan refresher and pickup locations on Monday
• Patron block
• manual for Chalmers
• optional message to patron
• option to block different actions - borrowing - renewing - requests (possibly others)
• future release should include blocks like ILL, electronic resources
• need to have the ability to get reports that combine both automatic blocks and manual patron blocks
• Is there a need to put in blocks that are specific to a given library or location? Optional. Default is all, and then the ability to block multiple libraries. not v1
• expiration date and patron message should be optional
• Is there any benefit to have a "block all" option now? Maybe instead have yes block for each one by default
• manual patron blocks should block proxy acting as the blocked sponsor
• patron blocks section will allow manual added, automated ones will also dynamically display in the same section
• pop up about block on loan screen, requests screen (needs a way to navigate), renewing, etc.
• user screen has blocks expanded and a red alert at the top of the screen in very visible place
• automatic needed as well but will work next quarter
• transfers may be discussed at next meeting,but maybe not
• notices needs to be moved into its own thing - notice policies
• would reporting tools be a way to pull all notices logic out
• reporting sig would be a good place to ask the question
• but generally reporting should not be considered for notices, due to need for real time data and the impact this would have on potential adopters, given how key notices are to what we do
• Item status Availability, Needed for, Process
• how does these get displayed on various screens?
• screens with a fair amount of real estate (like inventory) v. screens (like loans) with limited real estate
• screens where simplicity is helpful, like check-in screen?
• Are there apps that own a process? vs a one stop shop for multiple processes?
• vocabulary questions
• look at these slides over the next week to discuss next Thursday
• https://docs.google.com/presentation/d/1OjtRf4Cad5lBgSZNFmHnH4h7Gmv8xxy65S2c4uNU3kY/edit#slide=id.g42cf361830_1_179
• User information page
• fee fines display proposal to display the totals of open and closed fines, then a link view fee fines history to view all and that text should be View all fee/fines
• we would rather not see the total for closed fines, both because we don't know how many were our mistake and because one could misread which amount is the one that's outstanding