chaphasilor / digitalhourbook Goto Github PK

In it there will be dates and hours much like the default object store, but those hours will be combined and then subtracted from the total required hours (because there were no working hours but they still need to be accounted for)

Add an option to export and import the user's weekly hours, as those are quite fiddly to set up again and can't be synced yet.

• Export hours as text/JSON file to preserve data through resets etc.
• Implement option to automatically import said data back into a new instance of the database

The current file input seems to default to a media/image input on mobile, this probably confuses users...

Proz Helper accepts .csv-files. Add an option to export the most recent month from the first of the month to the current day of the month as a .csv- text (and copy it to the clipboard).

Works when manually importing...

• show a loading indicator while syncing events
• remove 'data copied' message after a few seconds or if another month is exported
• show the year next to the month on the export page (or let the user select a year?)
• add a back button on the export page

Don't use weekends in the calcluation, this will make implementing auto-holidays easier...

The month selection on the export page is a bit broken, selecting December will output January, selecting November will output December and so on.
This is most likely just an offset problem and easily fixable.

Create at least two more object stores:

• weeklyHours, which contains dates and the corresponding amount of working hours per week from that date on
• daysOff, which containg all dates where you don't have to work (holidays, etc.)
• hourlyPay, which contains dates and the corresponding hourly pay from that date on

Filter events with leave in the description so they are not included with the other working days and instead add all of their hours to the hoursOff object store

This is part of #1

Up until now, the weekly hours are hard-coded as 7 hours per week.
Change this, so that you can specify a date and a number of weekly hours and from that date on until the current day or another date specifying different weekly hours, use these weekly hours to calculated required hours.

Example:

This would result in the program calculating the required hours as #days since day X until day Y*x1 + #days since day Y until today*1.

The first entry should be the day the contract started.

Setup the weekly schedule in a dedicated object store, where you can specify the planned hours for each day of the week.
Use this information when calculating the required hours by checking the weekday for every day. This also applies to days off, where weekdays with 0 planned hours are ignored.

Currently it's a bit ill-formatted on mobile...

It seems like overtime might not be calculated correctly recently.

Check the calculations and fix any bugs.

Implement an overview over all hours in the database as well as all hours of the last month

Add a button to start a sync, this overwrites the database content by default

Use labels for better styling of the input elements (especially the date picker) and hide the actual inputs where useful.

• add an option to export the data as text/a text file.
• add an option to export the data to a server (see #8)

Set up a NodeJS server to handle user backups.

• on first visit of the site (or after site data is deleted) there's no data, so the user is asked if they are new or already have a token. if they are new a unique token is requested from the server and saved in local storage or as a cookie and also presented to the user. they need to take note of the token for later reference.
  if they already have a token, they are prompted for it, then the data is requested from the server and the token is saved again
• POST: user sends their data, along with the token (no password). the server creates a file with the token and the current date and dumps the user's data into it
• GET: the user requests data using the token, the server checks if there are files for that token, if yes it sends back the content of the latest file

on some days there are multiple entries at different times, those should be merged to calculate the total hours for that day.

This is (probably - check how days are counted) not an issue for the app itself but is important for exporting to Proz Helper