On-demand report generation

[parthpandey1]

Based on the original requirements #65

Implement on-demand report generation for:

• total amount of food donated measured by quantity/weight
• total amount of food checked-out by students
• total number of different students who checked out food
• total number of checkouts

• Backend PR -- On-Demand Report backend #226

[jayrevolinskyjr]

Update - 05/05/2023

The Summary page is very similar to what we planned for option F3.) meaning that we can hitch the backend for the on-demand report feature to the Summary frontend.

I will keep the rest of the plan intact (shown below) for posterity, but it is likely that all we will need to do is stitch the On-Demand Report backend to Summary's frontend.

The above tasks can be broken-down into sub-tasks:

1. Total amount of food donated measured by quantity/weight
   a. Sequelize function to findAll on Items in inventory and calculate total items
2. Total amount of food checked-out by students
   a. Sequelize function to findAll on Transactions with type 'purchase' and calculate total items
3. Total number of different students who checked out food
   a. Sequelize function to findAll on Transactions with type 'purchase' and unique 'person_id' values and then calculate total unique people found.
4. Total number of checkouts
   a. Sequelize function to findAll on Transactions with type 'purchase'

All of these functions will be very similar to one another, so I see the frontend and backend implementation going two ways.

Possible backend implementations:

B1.) Filtering the results from sub-task 1a. to generate different final reports.
B2.) Creating four separate functions to handle the separate functionalities.

Possible frontend implementations:

F1.) Creating a 'Report' page that is updated with the results found from the filtered/separate functions.
F2.) Creating four separate pages for each function that generates a report.
F3.) Potentially mixing F1. and F2. by loading a report in a component that is all on the same page?

Thoughts:

Personally, I am leaning towards B2. and F2. and then building the functionality from there. What are other's thoughts on this? I'll start working on a design tomorrow depending on what people think.

[parthpandey1]

@jayrevolinskyjr I think building B2 and F2 first sounds reasonable. We can always add new features on the FE like charts and visualizations later.

[jayrevolinskyjr]

@jayrevolinskyjr I think building B2 and F2 first sounds reasonable. We can always add new features on the FE like charts and visualizations later.

Looks like there is a massive amount of overlap between this issue and #152. So, option F3 seems mostly finished, all that really needs to be done is update/implement the backend. Updating and implementing the frontend can be a separate issue with it's own tasks.