Using BioRegistra is easy and to get started, here is a definition of some of the concepts on BioRegistra.
Use cases are those activities that you can do on your created projects on the platform. As the platform grows, we continually add more use cases to ensure it becomes a full suite which can be used for other activities asides data capture. Listed below are the use cases on BioRegistra:
This use case is strictly used for enrolment of fresh records into the BioRegistra system. The information captured during enrollment is based on the configuration (Textual, fingerprint, and picture) done during project setup.
This use case enables re-enrollment/update of the already registered record. Here, the already captured data is retrieved by the client using the unique ID and the agent/user can then update the record. For records updated/re-enrolled, there are modes of validation;
Fingerprint validation – This strictly applies to captures that have fingerprints. A match of the new fingerprint is done against the already/previously captured fingerprint. Once the match is successful, the record is retrieved to the client and agent can proceed with the update.
OTP Validation – Here, an OTP is sent to the mobile number tied to the previously captured data, and once the valid OTP is inputted into the client and there is a match, the captured information can then be updated successfully.
ID validation – This mode implies that there is no need for validation before updating captured data. The data is retrieved to the client directly using any of the IDs of the record and an agent can proceed with the update.
This use case is broken down into two sub-categories;
Biometric Verification – Here, a one-to-one (1:1) fingerprint matching between the previously captured fingerprint and the newly supplied fingerprint is done. The system handles this process and returns an output to the end user – Match found or Match not found.
Textual Data Verification – Here, two textual information are supplied, the primary identifier and any other parameter. The system does a check to confirm whether the values passed exist as a pair (together) on the system.
This use case is a One-to-many (1: N) match where the system does a match of the fingerprint provided against all records enrolled under the user’s project. This BioRegistra system has an extremely high processing capacity which enables it to handle such core computing at fast speed.
This use case is a many to many (N: N) scan of your full database to help flag duplicates. This is used in situations where you need to fish out people with multiple registrations. This is particularly useful in ghost workers elimination exercises.
This use case is for users who will like to get their data exported in XL format.
A project is a created capture form that consists of defined related fields that are of interest to a user. An example of a project can be Government worker enumeration project; such project will capture the basic details of employees, educational details, work details, salary details, etc. and can also contain a picture of these staff and 2-4 of their fingerprints. BioRegistra allows you to create unlimited number of projects and allows all users to specify what their own capture project should look like when they login on a capture device.
After data has been captured and saved, it automatically attempts to sync this record to the BioRegistra backend without needing any intervention from the agent.
Do not worry if your device has no internet connection during capture. The device will continually attempt to connect to the backend if the device is on and the app is launched.
The data synchronization happens in five steps
Step 1 – Data is captured and saved on the capture client
Step 2 – Capture client sends the information to the BioRegistra backend to save if it has network
Step 3 – Backend checks account to see if it has sufficient balance to sync record
Step 4 – Backend saves record and removes the charge of syncing from the user’s wallet
Step 5 – A notification is displayed on the capture client to inform if sync was successful
Most users prefer that agents are only able to capture a defined set of pre-populated records. In that case, during capture, system checks to ensure a part of what is captured has been pre-provided in the system before the agent can proceed to capture. This set of details provided before the capture even commences is called Pre-identifier. An example, imagine a company wants to capture all her employees, and wants to ensure nobody outside the workforce is captured. All that needs to be done is to first identify that unique thing that will distinguish each staff – Staff number in this case. Then the staff numbers would be uploaded to the system first. When the capture is about to commence, the system will automatically validate the unique id provided by the agent against the database to be sure that pre-identifier exists before allowing the agent capture. This way, agent cannot capture anyone not in the pre-uploaded list.
During Project creation, users need to ensure that this is turned on, if they will require their project to have that behavior.
– You will be taken to a screen where you can upload a list.
– Click the Upload New List button. This will show a modal where you can download a template, and then upload your result. This will delete any one that has already been uploaded, and replace with the new one just uploaded
– Click on the Add More IDS button if you will like to add more to the existing pre-identifiers already added
– In the excel sheet, you can specify an email address for any of the IDs. Specifying this means you want the agent with that email address to be the only person authorized to capture that pre-identifier
– If the agent email address column is left unspecified, then any agent can capture the record tied to that pre-identifier.
You can also upload your pre-identifiers to your project using our set of APIs. Access our API documentation here to understand how this can be used: www.bioregistra.api-docs.io
Pre-identifiers can either be global or specific to agents. Global Pre-identifiers are those that can be captured by any agent assigned to that project, while Specific ones can only be captured by specified email addresses. To specify/assign an email address to a pre-identifier, ensure that the email address has been added in the email address column in the excel used in populating the pre-identifiers.
A Pre-identifier can be deleted. However, it can only be deleted when it has not been captured yet. To delete a pre-identifier, do the following:
– Locate the project on the Home Page
– Hover on the project to reveal options
– Click on More and click on Upload Pre-identifier
– On the card with number of Uploaded IDs, click on View full list
– Locate the one to be deleted and click on the Delete button in the Action column
In a project, the Unique ID field is that field that must be unique for all records that is captured. This is usually done to ensure that duplicate entries are not captured. An example of a Unique ID field if I was creating a Project to capture employees of a company will be Employee Number.
When creating a project, you can specify which of the text fields will be the Unique field. If any is selected, the system will ensure that same value cannot be captured more than once for records for that field.