Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature Request] Dashboard metrics as data tables #551

Closed
alexsaagi opened this issue Jul 3, 2024 · 2 comments
Closed

[Feature Request] Dashboard metrics as data tables #551

alexsaagi opened this issue Jul 3, 2024 · 2 comments
Assignees
Labels
pending release fix in place, pending release

Comments

@alexsaagi
Copy link

For years I have maintained a similar data structure for manual spreadsheets. One of the outputs I miss with LubeLogger is the ability to see cost breakdowns as simple numbers in a table. Let me provide an example of my old spreadsheet for context:
image

To adapt the key info from this to LubeLogger I'd suggest a table like this:
image

The end goal being to capture the true cost of vehicle ownership from the data being collected, both in terms of per km (distance driven) and time (months/years).

We would still be missing some estimate of future scrap value at a certain time to establish estimates for depreciation (you can see this in my spreadsheet example) but I'd consider that a secondary concern.

@hargata hargata self-assigned this Aug 20, 2024
@hargata
Copy link
Owner

hargata commented Aug 31, 2024

@alexsaagi will be included in the next release.

Clicking on the pie chart will bring up this data table:
image

Instead of Monthly cost, I opted for days because it's a lot easier/cheaper to calculate the number of days between two dates than the number of months. The number of days reflects the days of ownership for a specific vehicle. If purchase and sold date are both provided then that is what will be used. If only purchase date is provided then it will calculate the number of days between the current date and the purchase date.
Otherwise, it will fall back to the earliest record(e.g.: first service/repair/upgrade/fuel/odometer/tax records) to establish the initial date of ownership and today's date to establish the length of ownership, this isn't the most ideal way as it's only an approximation of length of ownership so it's highly recommended that users set the purchase date in the Vehicle details itself.

Number of miles driven is based on the min odometer reading and max odometer reading of all records, unless a year is selected from the dropdown instead of All Time, then it will use the min and max odometer reading of records within that year ONLY. This allows the user to narrow down the ownership costs for a particular year instead of over time.

This data table shows the following:
Cost Per Day - The total cost over the ownership length of the vehicle.
Cost Per Mile - The total cost over the miles driven during the life of the vehicle OR the year selected.
Total Cost - self-explanatory

@hargata hargata added the pending release fix in place, pending release label Sep 1, 2024
@alexsaagi
Copy link
Author

That looks great, thanks for the follow-up. Looking forward to the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending release fix in place, pending release
Projects
None yet
Development

No branches or pull requests

2 participants