2018-10-11 Resource Access Meeting Notes

Date

11 Oct 2018

Time	Item	Who	Description	Goals
5min	Housekeeping	Andrea Loigman	Note-taker - Holly Mistlebauer
5min	Opening time offset - UI mockup	sthomas (Deactivated)	Opening_time_offset_UI.pdf	Approval: UI mock-up
20min	Skip closed days in due date calculations	sthomas (Deactivated)	Scenarios: Skipped closed dates desk	Decision: logic for long/short-term loans; Discussion: surfacing critical gaps (if any)
10min	Notice Logic	Darcy Branchini	Moved notice logic to a separate notice policy	Approval: to move forward with logic in notice policies
20min	Loans: overrides	Emma Boettcher	con't. discussion from previous meeting	Confirm columns for renewal override modal. Include predicted due date?
5min	User record - requests section	Cate Boerema (Deactivated)		Approval of layout for requests section of user screen

Functional Area	Product Owner	Decision Reached	Reasoning	Link to Supporting Materials	Comments
e.g. loans, fees/fines	Name	Clearly stated decision	Because... Because...	e.g. mock-up, JIRA issue
Loans	Emma Boettcher	Moved toward consensus on override modal with predicted due dates, <em>except</em> for behavior when the user wants to treat several selected items differently. Additional information field will be required, and override & information about override will be reflected in loan details.	Preferable to have system predict line by line and not enter due dates for each line

Opening time offset - UI mockup (see Opening_time_offset_UI.pdf)

Taking about Settings>Circulation>Loan Policies
Want to have setting that only appears when you select Move to the beginning of the next open day
Open time offset setting has a number value and then a pulldown for selecting what that number value represents (minutes, hours)
Default will be zero
This was approved by the RA SIG

Skip closed days in due date calculations (see Scenarios: Skipped closed dates desk)

Slide 3: For generating a due date/time, Check-outs and Check-ins are only concerned with open-closed hours for Service Points, not Locations? Correct, this was already decided.
Slide 4: We discussed this before and decided end of day is 11:59:59 PM for long-term loans regardless of Service Point hours. (Andrea remembers that there may be a post-v1 feature where the library could set this for themselves.)
Slide 5: Long-term loans are due at 11:59:59 PM on the day they are due. Short-term loans are due at the latest closing time of the Service Point for the specified due date.
Slide 6: Does Skip closed days in intervening period only apply to day calculations, not hour/min calculations? RA SIG says that we can skip this.
Sean ran out of time to go over use cases, but needs to redo them anyway based on decision from Slide 6.

Notice Logic

Have had many conversations about where notices should sit–have decided on Notice Policies (which Darcy showed us a mock-up) divided up by functional area.
Actual notices reside elsewhere.
Discussed that it doesn't make sense to have all of the notices together as one policy. It makes sense to have Loan and Fee/Fine notices together.
It seems like recalls could be part of Loan notices rather than Request notices.
Need to discuss this further.

Loans: overrides (con't. discussion from previous meeting)

Discussed why you might need to enter a renewal date when you override a failed renewal
- Item isn't renewable
- Item hasn't reached maximum number of renewals
- Patron blocked
- Patron expired
User will uncheck the items they don't want to override
Should Additional information be required? Yes–at some point could make this an institution setting but for now leave it as required
What if there are multiple due dates for a batch of 130 items? Do a batch for one date, then a batch for another date, etc.
Need to discuss this further. Emma will send out flowchart and slides–discussion will continue on Thursday.

User record - requests section