With bikubo you can use a PC or laptop to validate tickets or accreditations. You can attach a barcode reading scanner and / or QR codes, and after reading the data is sent to the server or validated against the internal PC database, showing the result of the validation, and making the relevant changes in the database, regarding validated ticket / accreditation. You can also validate manually by entering the locator.
To obtain the link to the web page for validations, you must click on Menu => Events => Active => Title of the event in question => List of ticket categories / accreditations => ticket / accreditation in question (option - Advanced configuration). The screen where you can access three links is displayed: the first link, allows validating all events and all categories of tickets and accreditations, the second link allows validating the event and all categories of tickets and accreditations of that event, and by last, the third link allows validating only the event and the selected category.
Once you access that link and open it in a browser, the web page with the validation options is displayed.
You can validate against the database of the server, or download the tickets and validate against the internal database of the browser once the tickets have been downloaded.
Validation against the server means that the checks to be carried out regarding the readings of the QRs / barcodes and / or the pagers, are looked at in the bikubo server databases, so that this database is unique for all the validators. Thus, if the 'validator A' validates a ticket, it is put as delivered, so if you try to access with that ticket again by the same validator or by 'validator B' (if you are also validating online), it will appear as delivered and the app will show you the error. With the validation against the server, when having to access the bikubo server, it is necessary to have a good internet connection so that the process is carried out correctly.
The validation against internal database makes that the verifications to be made regarding the readings of the QRs / barcodes and / or the locators, are looked at in the databases downloaded from the browser, so that there are as many databases as validators. Thus, if the 'validator A' validates a ticket, it is put as delivered, so if it tries to regain access with that ticket by the same validator it will appear as DELIVERED, but by the 'validator B' it will not appear as delivered, giving it as correct. In this type of validation, 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 connected site, so that they are in the browser's internal database.
The data of the validations against the internal database remain in the validator's browser, and do not appear on the server, so the tickets / accreditations do not appear as validated in the server (they can be delivered successively), nor will the statistics appear . However, in the validation web page you have the function 'Send validations to the server', so that when you click on this button, the validated ticket data and the validation time are uploaded, so that the server processes those validations, and make the relevant changes in the status of the tickets, and in the statistics.
The third validation option consists of validating against server and internal database, simultaneously, and thus the verifications to be made regarding the readings of the QRs / barcodes and / or the locators, are looked at in the databases of the server of bikubo, and also in the browser's internal database. The advantages and possibilities of this option are described in the following link for the validation with the bikubo app, which can be applied to the web validation: app simultaneous validation
It is advised that the validator select the option of the event and category of ticket that interests him, since when validating a ticket, if the validation is valid, directly the delivery and the next time the ticket / accreditation is validated will be shown as previously delivered.
The result of the validation is shown on the right side of the web browser screen, the green color being the correct result, the red one for an error result in the validation, and blue if the result is correct but it is showing the the assistant's output (in the validations previously configured), and the corresponding information is also displayed (assistant name, ID, observations or cause of the error). In the upper part of the right part of the browser, it is shown if the validation has been made against the browser's database or against the server.
Finally, we must indicate that if you are not going to validate with a QR code or barcode reader, you can select the option to manually enter the pagers, enabling the checkbox.
You can change the web validation links by simply changing the password of the app in menu => my data.