search

DeltaO3 / UWAttend---3200_27

Repository for CITS3200 group 27
1 stars 0 forks source link

Sprint 2 - local database storage & sync implementation #50

Open DeltaO3 opened 3 weeks ago

DeltaO3 commented 3 weeks ago

As per the requirements, some level of data (mainly attendance records, any others please discuss) should be stored locally in some form of temporary database before being manually added to the main database by pressing the sync button. For this issue, do not worry about making this database function fully locally if it is too hard, that is more in scope of #33. However, some consideration of this eventuality should be considered.

Please discuss ideas of implementation with the team / via comments in this issue.

Some initial thoughts include: a seperate database that holds data that is in some way or another mapped to each particular login + unit + session combination - this will likely cause largely inflated data. Did the professor want this local data to automatically clear after a set time?

DeltaO3 commented 2 weeks ago

local database/temp database (however we do it) is important for managing storing to large database- "sync" could also be called "finish session"(?), syncs the attendance data to the proper database, with the selected session (to allow changing) - we likely want to utilise local storage somehow for this (browser storage), not server storage. Look into authenticating this data is from a valid user?