Part 2)As a trail-chaser, I want to scan a QR code and checkpoint the landmarks I’ve visited on seperate trails to track my progress.
Follow-up of issue #49 (closed). Following our discussion during the Scrum Meeting on 01/11/12 (see relevant minutes). This issue has been split into two parts.
The first issue involved the implementation of a QR scanner in isolation.
This second issue involves the integration of the QR code scanner, designed and implemented in isolation within issue #49 (closed) . After installing the feature, it is now required to combine the backend with a user checkpoint system. This system must be independent to each user, they must be able to update and save their progress within a session. I do not expect persistence per session.
Assessment Criteria
-
The scanner should scan a QR code and update a users progress within a trail by marking a landmark off. -
The code-base should hold a couple of mock-QR codes associated with internal landmark points. -
The scanner should be able to successfully scan these QR-codes
Tasks
-
Ensure that QR-codes related to a small number of locations within two or three trails are implemented. -
Attempt to test the scanner using these QR codes -
Ensure that each user has a table within the database that can track their landmark progress. ( If the table has not been completed and the task is greater than the current weighting, please consult with me so that we may either provide more hands or change working priorities.) -
- [ ] Replace the simple variable implemented in #49 (closed) that changes when scanned with a connection between the scanned QR code and the above table.( Removed after discussion during 05/12/23 scrum meeting) -
Create a connection between the above table and the scanner. -
Have the scanning of 'mock' QR codes change an applicable variable within the table -
Have the scanning of these mock QR codes change values within the users above progress table -
The users progress should only be able to be changed once per QR code scanned per session