[TO-DO] Detect date of receipt and handle time ranged summary

[Sing-Li]

Combine the upload date/time of the receipt, and the receipt's own date/time and produce daily, weekly, and monthly reports. Until the user explicitly "closes" a report via slash command.

Then produce a final report (for this closing).

[sushen123]

My appraoch is for the daily report, app should show the summary at the end of each day by grouping and summing receipts that share the same date. For the weekly report, it aggregate receipts on saturday, grouping them by week and calculating the total. similarly, for the monthly report, we will generate the report at the end of each month by grouping receipts within the same month and summing up the totals. These reports will automatically update until the user explicitly closes them using /receipt close, at which point a final report will be generated.

Let me know if this works. I am happy to contribute.

[4shb0rne]

Combine the upload date/time of the receipt, and the receipt's own date/time

want to clarify this part, since we're saving both upload date and receipt's own date(i assume this is the one that is written in the receipt), when generating report based on date which date should we use to group the receipts ?

i don't really get what "combining upload date/time of the receipt, and the receipt's own date/time" mean as well 🤔

[SinghaAnirban005]

By combining the user upload date/time and the receipts date/time , do you mean handling cases where lets say today i upload a receipt that's few months old . Thereby the receipts original date/time would be taken into account and that would prevent it from adding it to the daily report ?

[Kaif9999]

I think we should take account into the date on which the user uploads the receipts rather than, using the original receipts date

[Sing-Li]

It is analogous to the "total on the receipt" vs "total as reported by the LLM". I saw the discussion in the idea channel and thought that you've got a great design to ensure reliability.

Here we also have a "somewhat reliable" output -- the date on the receipt (as reported by the LLM) AND the user upload date (totally reliable date). Depending on the exact use-case you're programming for - the combination of the two will ensure the app is more reliable overall.

Hope that is clear.

[SinghaAnirban005]

Should we use a scheduler or slash commands like /report-daily /report-weekly ?

[Sing-Li]

The goal here is to leave things flexible as much as possible, enabling the maximum possibility of design and final proposed implementations.

And I'd like to encourage everyone to think --- should I implement this IN THE PROMPT or hard-code it in Typescript?? instead of which App Engine mechanism to concretely implemented it.

[Sing-Li]

So use App Settings and slash command options to make this configurable and optional.

Looking for implementation. Welcoming PRs.