2021-02-15 Resource Access Meeting Notes

2021-02-15 Resource Access Meeting Notes

Date

Feb 15, 2021

Attendees

@Joanne Leary

@(OLD ACCOUNT) Erin Nettifee

@lisa perchermeier

@Mark Canney

@Brooks Travis

@Martina Tumulla

@christine Tobias

@Stephanie Buck

@Andrea Loigman

@Erin Weller

@Kimie Kester

@Cheryl Malmborg

@brigdet Hornyak

@Cornelia Awenius

@patty Kishman-Smith

@Jana Freytag

@Rameka Barnes

 

 

 

Discussion Items

Time

Item

Who

Description

Goals/Info

Time

Item

Who

Description

Goals/Info

2min

Administrivia

@Jana Freytag

 

  • Notetaker: @Christine Tobias

30Min

New Calendar Design

@Cheryl Malmborg @Kimie Kester

Present revision of new calendar design having discussed it with developers

 

 

Meeting Outcomes

Functional Area

Product Owner

Planned Release (if known)

Decision Reached

Reasoning

Link to supporting materials

Comments

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

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Notes

   

Revised Mockups:

  • New default view for calendar

    • Now - Drop down for open date and closed date; these dates can be the same; fill in hours for each date.

    • Option for closing time to be on a different day than the open date.

    • Continuous operations: Open and closing times can cross the Midnight boundary to show being continuously open for several days. Example in slides.

    • Exceptions 

      • Date - Holidays  - special hours for a specific date (i.e., Veteran’s Day)

      • Period - special hours for a period of time (i.e., Thanksgiving break, semester break)

      • May have Exception dates within Exception Period. For example, Summer hours may be shortened, but may have dates within the period that have special hours(i.e., Closed on the 4th of July).

        • Questions from the group: Do we need both exception date and exception period? How does calendar prioritize period/date? If exception date falls within exception period, will system know to prioritize the exception date? How does the logic work currently? Answer: We need to do some testing to see how this will work!

      • Each service point has its own calendar; set exceptions for individual service point only; but can copy calendar, rename it, and revise appropriately and apply to other service points.

    • Continuous Hours display

      • Across several dates - closed field shows a dash. 

      • Closing the next day (crossing the midnight boundary); an * next to the selected closing time indicates closing on next day (i.e., 2AM)

  • Takeaway - positive response from the group...we like the revisions! :)

    • For now, we can revise our work flows to accommodate one service point per calendar; at least we have the option to copy calendar and revise/apply to another service point.

    • Possible future enhancement request - allow multiple service points on one calendar

 

Next meeting on Thursday, 2/18/21 - Documentation (Erin N. suggested generating a list of what documentation we need