Date
Attendees
@Christine Tobias
Discussion Items
Time | Item | Who | Description | Goals/Info | ||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
2min | Administrivia |
| ||||||||||
30Min | Present and discuss new calendar UI design | Present and discuss new calendar UI design - Kimie and Cheryl | 30Min | Review | Review the outstanding Loans and Requests features, bugs, tasks, etc. to see what should be given priority
| |||||||
30Min | Finalize two balance fees/fines reports: 'Cash Drawer Reconciliation Report' and 'Financial Transactions Detail Report' |
|
Meeting Outcomes
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 |
| e.g. mock-up, JIRA issue | |
Notes
Kimie and Cheryl showed a mock-up of the new calendar UI. Discussion centered on the best way to show 'wrap-around' times, i.e. how best to display situations where the library is open Friday 8:00 AM - 2:00 AM on Saturday, and then opens at 8:00 AM on Saturday. One way to show this would be to have one line for Friday showing opening at 8:00 AM and closing at 2:00 AM. There would be a pop-up to verify that this is what was wanted and not an error. Many in the group felt this would be an easier approach vs. having Friday 8:00 AM - 11:59 PM and then two lines for Saturday: Saturday 12:00 AM - 2:00 AM & Saturday 8:00 AM - 11:59 PM. It was pointed out that the case of 8:00 AM on Friday to 3:00 PM on Saturday would be confusing with the first approach. Mark suggested that leaving the closing time blank, or using a dash, could be easiest. Or alternately, having the closing time of 'Midnight'.
Day | Open | Close |
---|---|---|
Friday | 8:00 am | 2:00 am |
Saturday | 8:00 am | 10:00 pm |
Day | Open | Close |
---|---|---|
Friday | 8:00 am | 11:59 pm |
Saturday | 12:00 am | 2:00 am |
Saturday | 8:00 am | 10:00 pm |
Day | Open | Close |
---|---|---|
Friday | 8:00 am | - |
Saturday | - | 2:00 am |
Saturday | 8:00 am | 10:00 pm |
For the first option above, it was suggested using an icon to indicate that the closing time was for the following calendar day.
It was agreed to have further discussion on this when Kimie and Cheryl have time.
Holly displayed the Fee / Fine reports and invited comments and suggestions. There are two reports – the Cash Drawer Reconciliation Report has a summary of transactions for a service point over a date range and will include payments made at that service point within the chosen date range. It was agreed the the extra information in columns G-K would be nice to keep in this report. All reports have separate permissions, so it will be possible to block users without permission from opening the link to the Financial Details Report. It was also decided that it would be good to add an extra summary at the end of the report to view total payments by source. To deal with the cases of libraries that have multiple cash drawers at the same service point, it was decided that it would be good to add the option of choosing Source when creating the report (in addition to the options of choosing date range and service point). It was deemed helpful to have the report be exported as a pdf as well as a csv, to make it more difficult for the report to be manipulated via deleting a row.
The Financial Details Report would be used when it is necessary to research particulars of fees/ fines. The Details Reports has some of the same information as the Reconciliation Report, with additional information about the patron, the item, and the loan type. There are links to Item Info, Patron, and Loan Details. The loan does not include any information about waivers – should this information be included here, or is the Circulation Log adequate for that? It was decided that the SIG members should look at the report for further discussion on Monday, Feb. 8. Specifically, is there anything else we would like the report to contain? Is the column order OK? What should the sort order be?