Feature: As an Operator, I should be able to capture the biometric data of the Resident during new registration

Description

Feature: As an Operator, I should be able to capture the biometric data of the Resident during new registration

Purpose: New Registration - Bio Metric details

Disclaimer: This feature should be functional in online and offline mode.

Basic Flow:

  1. Once the Operator has duly filled the demographic details, he should be taken to the biometric capture page.

  2. Biometric page should be rendered from the UI spec followed by registration client document upload page. It should render the Fields, Date format, Radio button and asterisk symbol from the UI spec. (For more details please refer UI spec video - Registration Client UI Specification - YouTube)

  3. The Operator will be able to capture BioMetric details like:

    1. All fingers (Can have exceptions)

    2. Both Iris (Can have exceptions)

    3. Face Photograph (Cannot have exceptions)

    4. Exception photo

  4. The operator can also choose the type of exceptions which will accept the below two values:

    1. Temporary

    2. Permanent

  5. The Operator should also be able to add comments for the exception type (if any). Saving this data is not in the current scope of work.

Note : If the applicant has multiple exceptions then the operator should be able to take a photo with all the exceptions in it.

Acceptance Criteria

  • The attempt count will only be increasing when the biometrics captured is saved.

  • In a scenario where biometrics have been captured atleast once with or without exception and in the later biometric captures, there is a change in exception (say biometrics was captured earlier with exception and later without exception or vice versa), the count will go back to being 0 and it will start afresh from 1.

  • To cater to “fat finger” issue, the Operator should be able to mark exceptions for fingers by zooming in using the magnifier icon.

  • BioMetric page should be rendered from the UI spec followed by registration client. It should drive the Fields, Date format, Radio button and asterisk symbol from the UI spec.

  • All the biometric attribute should be mandatory. In case of exception, biometric will not be captured. So for any biometric attribute there has to be some input - either the biometric is duly captured or an exception is marked.

  • The percentage of clarity of each capture should be clearly mentioned on the screen.

  • The Operator should be able to mark exceptions by clicking on the relevant biometric segment.

  • The attempt with highest clarity should be chosen by default and there should be some distinction between the biometric chosen and not chosen (underline in our case)

  • One should be able to know the attempt of which the percentage is being displayed of.

  • The number of attempts should also be configurable.

  • The threshold should be chosen by the Operator prior to the biometrics capture procedure begins. The threshold value should be configurable.

Updated UXD: https://xd.adobe.com/view/ea45ab2e-eb04-4643-8a57-5d0622a30705-bf16/screen/9dc1b761-3ffe-4dd3-8a7a-8a85d7ad2e2c

causes

Activity

Show:

Chaitanya Kesiraju February 1, 2024 at 5:15 AM

Verified the story in qa-platfor.mosip.net environment 1201 version and observed that the functionality is working as expected, but there are few issues that are linked. The issues will be tracked separately.

Closing the story as functionality is working as expected.

G Famuda Mubashira December 5, 2023 at 12:29 PM
Edited

Verified the story in qa-trinity environment 1201 version and observed that there are critical issues linked in the story.
Re-Opening the story as there are few critical issues.

Unresolved

Details

Assignee

Reporter

Severity

Major

Resolved by

Sprint

Fix versions

Priority

Created June 8, 2023 at 6:14 AM
Updated June 28, 2024 at 4:47 AM

Flag notifications