2021 10 21 Meeting with Cheryl

4. Backend thoughts on a relational-style DB instead of the jsonb blobs?
   • Agreed with our opinion, relational is better
5. Where to develop?
   • Branch and continuous PRs on folio-org repo? (Push access?), or
   • Entirely on fork and one big PR for rewrite
   • Left up to us
6. Where should user documentation go for how to use the tool?
   • https://docs.folio.org/
7. Can I ask Dmitri and/or Alex questions on Slack regarding workflows/code if needed?
   • Dmitri would be best

Looking at the proposed mockups (https://docs.google.com/presentation/d/1o_hMdULtPxS4yK1zJ_kqwlegJyX3Xw8ghBlxJyJySto/edit ), I'd like to propose a few differences:

1. On slide 6, remove the "Closed" option for regular hours and only have defined openings.
   • This greatly reduces confusion of what needs to be explicitly vs implicitly marked as closed (e.g. if open from 9-5, does midnight-9 and 5-midnight need to be specifically marked closed? Only full days? etc).
   • Much more user-friendly IMO to only provide open hours and have the rest default closed.
   • Leave explicitly marking whole days as closed
2. On the first view of the pane (slide 2), I'd like to separate out calendars and the service points they apply to.
   • This would make things much cleaner (especially as the list of calendars grow; ten service points and calendars across eight semesters results in 80 entries)!
   • Allow the creation of calendars separately and then apply them to multiple service points (I believe intended design, just not well-conveyed with current mockups)
   • Drilldown on calendars allow editing, drilldown on service points shows current detailed hours and previous/upcoming calendars
   • Re-evaluate after mock-ups