Offline validation of tickets and capacity with the bikubo app

The bikubo app can be installed on iOS and Android devices. The download links for both repositories are:

• iOS
• Android

Offline validation means that the checks to be performed regarding QR / barcode readings and/or localizadores are looked up in the databases of each reading device, so that there are as many databases as validators. Thus, if 'validator A' validates a ticket, it is set as delivered, so if you try to access again with that ticket through the same validator it will appear as DELIVERED, but through 'validator B' it will not appear as delivered, giving it as correct.

Offline validation means that the capacity data is different for each validator, showing as DELIVERED only the tickets that have been validated by that device. The sum of validations from all devices would correspond to the capacity at that time.

By not having to access the bikubo server for validation, it is not necessary to have an internet connection for the process to be carried out correctly. However, prior to validation, it is required to download the tickets from a place with connection, so that they are in the internal database of the device.

The validation data remains on the validator's device, and is not recorded on the server, so the tickets are not recorded as validated on the server (and can be delivered successively), and the statistics will not appear either. However, the bikubo app has the 'Send validations to server' function, so that by clicking that button, the data of the validated tickets and the validation time are uploaded, so that the server processes those validations, and makes the relevant changes in the status of the tickets, and in the statistics.

The steps to perform offline validation at the door are as follows:

• Open the app on the device.
• Log in with the username and password. This data is displayed in the bikubo intranet, on the 'My data' screen.
• If you have previously downloaded tickets on that device, click on 'Clean Database'.
• With an internet connection, click on 'Download tickets'.
• Select 'Validate against internal DB' on the main screen.
• To scan a QR/barcode, click on 'Open scanner', and the camera is activated to proceed to focus it towards the QR/barcode.
• After scanning, if the ticket is valid, the ticket information associated with it is displayed (Event name, ticket category, ID and/or name of the attendee if applicable). There is also an identifying OK sound. At the moment that information is displayed, the ticket is already considered delivered, so the next time it is scanned, it will be indicated that it has been delivered previously. If the ticket contains identifying data of the attendee (name and/or ID), the validator action is required, pressing the button to exit the ticket information screen. If no attendee information is displayed, the ticket information remains displayed for less than three seconds and returns to the scanning position so that the validation process is agile.
• You can also validate a ticket by manually entering the localizador, after clicking on 'Enter reader' and then on 'Check reader code'.
• If the ticket has been canceled, or is not valid for the user, or has been delivered previously, a message is displayed indicating the information. There is also an identifying error sound.
• You can see the list of validated tickets by clicking the 'Capacity' tab. It lists the events with their ticket categories, and the validated tickets with reference to the printed and electronic tickets generated. The format of what is shown is of the following type:
  Event name
  Ticket name
  Validated tickets / Generated tickets

If you click on a ticket category, the list of generated tickets is displayed, ordered by most recent to oldest validation date, and after the validated ones, the non-validated ones are displayed.

The data of each ticket displayed is:

• The localizador. It is not displayed in full for attendee security, showing the first 3 and last 3 characters.
• Validation status: DELIVERED, PENDING DELIVERY.
• Validation date: the date and time of the ticket validation