receiptoverview's Introduction

Receipt Overview

A little piece of software, to digitalize Receipts and export them as a .csv to be used in R for data analysis and statistics.

Initial Setup

The application needs a database in the following path: /Data/data.db After starting the application for the first time, an empty data.db is created. This one can be deleted. Instead, use the DB Browser for SQLite (https://sqlitebrowser.org/) to run the "create_db.sql" script which is located in the same directory (/Data/create_db.sql) The resulting database needs to be saved as "data.db" in the same directory (/Data/data.db). Afterwards, the application is ready for usage.

Shortcuts/Hotkeys:

Hotkey	Function
Ctrl+N	New position
Delete	Remove selected position
Enter	Add current entry to collection
+	Copy selected entry
-	Remove selected entry
Ctrl+S	Save current position

Take notice, that the "Delete" Button is a Hotkey and therefore should not be used to remove charactes. Use "Backspace" instead.

Made with

Avalonia UI 11.0.10 with the build-in Reactive UI MVVM Framework
Avalonia Datagrid [NuGet]
Avalonia Forst Theme (https://theme.xaml.live/)
C# & dotnet 7.0
SQLite 3 & Microsoft.Data.Sqlite [NuGet]
Icons8 (https://icons8.com/)

Build for

Fedora Linux 39 & 40 (KDE, x11)
Windows 10

(not tested on other systems, but should build and run wherever the dotnet 7.0 Runtime/SDK is installed)

For Code-Readers

The goal was fast development, with no plans to expand further than the base functionalities (which are: inserting Receipts and their entries and export everything to a csv file). Therefore, maintenance was not a priority, which results in a somewhat messy Codebase.

License

MIT

receiptoverview's People

Contributors

Watchers

receiptoverview's Issues

ToDo: Update README.md

Switch image to an up-to-date image with a couple sample positions and entries, displaying the indicator for saved/unsaved positions.

v.1.0: Full Selection on Day, Month or Year Textboxes causes bad UX

When the Focus comes on any of these TextBoxes, the text within is selected.
When entering an new value, the TextBox in question behaves unexpectedly.

Support multiple Categories

current: only one Category per Item
to implement: several categories per Item.

To Do:
DB

create "Category" Table and add it to the creation script.
adjust already existing entries: move all categories into to the new table. Add an CategoryId to the corresponding Item instead.

Code

adjust the sql scripts to support the new table
add a new Model for the new table
add CRUD to the DataAccess for the new Table
adjust the existing Entry Model, to have a CategoryId instead of a Category
adjust the EntryViewModel to convert a Entry and a Category Model into the Category String and vice versa, separated by comma - thus the UI does not need to be changed.
verify, that the Autofill can support the new feature.
adjust eh CsvExport to support the new feature.
- since the CsvExport uses models, instead of ViewModel, the Categories need to be concatenated into a string for the corresponding entry with a symbol which is support in csv (e.g. not necessarily a comma)

Users can then add several Categories to an Entry like this: Category1, Category2, Category3, ...
which is then being processed separately into the Models, and then inserted in two different Tables

Then, a new release can be build and uploaded