bcgov / bcgov/foi-flow

Search Applicant Profile

Open
#4,758 13 comments 0 reactions 1 assignee Claimed by @richard-aot View on GitHub
Story
Dominant language
Python
Stars
8
Forks
2
Avg merge
14h 34m
Merged PRs (30d)
46

Description

* As an IAO analyst
* I want to search for an applicant profile
* so that I can match an applicant to an existing applicant profile

**Assumptions & Scope**
What are the assumptions for this story?

Applicant profiles from AXIS will need to be migrated into FOI Mod

Every applicant will require a profile.

Updating an applicant profile will not update the applicant contract details for Closed requests.

When an analyst updates an applicant profile, they will have the option of updating the contact details for other Open requests.

Only IAO analysts can view, search, match, create and update Applicant Profiles.

When an applicant makes a request they will provide their name and contact information. Upon review of the request, the IAO Intake analyst will need to search and check if the applicant previously has made FOI request(s) and if they already have an applicant profile in the system. The IAO Intake analyst will attempt to match the applicant name and contact information manually with existing applicant profiles and contact information already in the system. If there is no match, the Intake analyst will create a new applicant profile for the applicant.

Searches will match the information provided by the applicant when making the request ( First Name; Middle Name; Last Name; Date of Birth; Email; Primary Phone) with the same data fields for applicant profiles already on file.

Closest matches will be displayed at the top of the search results.

Assumption - searches in the Search Applicants profile will be client side and only search existing results to narrow the existing search, rather than start a new search. Confirm with team that is correct?

What is IN scope?
Searching for an applicant profile

What is NOT in scope?
View and select existing Applicant Profile #4761
Creating a new applicant profile
Searching and selecting profiles for On Behalf of requests
Adding an additional applicant category profile (i.e. different applicant type) #4763
Updating an existing applicant profile
Request History for an applicant
Applicant Contact History

**Acceptance Criteria**

**Scenario 1: Search Applicant Profile from Request View**
* GIVEN an IAO analyst is on a Request View
* AND an Applicant Profile has not been selected for the request
* WHEN the IAO analyst opens Address and Contact Details
* THEN the 'Search Applicant Profile' link will be there
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/663873000

**Scenario 2: Click on 'Search Applicant Profile - No match**
* GIVEN no Applicant Profile has not been selected for the request
* AND there are no matches
* WHEN the IAO analyst clicks on the 'Search Applicant Profile' link will be there
* THEN the Search Applicants modal will open
* AND there will be no results returned in the search
* AND there will be a search bar and buttons to 'Create New Profile' and 'Cancel'
* And columns for: First Name; Middle Name; Last Name; Date of Birth; Email; Primary Phone
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/987389728

**Scenario 3: Click on 'Search Applicant Profile - 1 or more matches**
* GIVEN no Applicant Profile has not been selected for the request
* AND there are matches
* WHEN the IAO analyst clicks on the 'Search Applicant Profile' link will be there
* THEN the Search Applicants modal will open
* AND the results will be returned in the search
* AND there will be a search bar and buttons to 'Create New Profile' and 'Cancel'
* And columns for: First Name; Middle Name; Last Name; Date of Birth; Email; Primary Phone
* AND these columns will be filled if that data has been captured in the profile
* AND the existing Applicant Profile with the most matches (First Name; Middle Name; Last Name; Date of Birth; Email; Primary Phone) will be displayed at the top of the results
* AND the existing Applicant Profile with the least matches (First Name; Middle Name; Last Name; Date of Birth; Email; Primary Phone) will be displayed at the bottom of the results
https://jacklyn808742.invisionapp.com/console/share/3W2O64AP5C/987389727

**Scenario 4: Cancel 'Search Applicant Profile' modal **
* GIVEN the IAO analyst is on the the Search Applicants modal will open
* WHEN the IAO analyst clicks on the 'Cancel' button
* THEN the modal will close
* AND the IAO analyst will remain on the Request View
* AND no Applicant Profile will be matched with the Request

**Scenario 5: Search from 'Search Applicant Profile' modal **
* GIVEN the IAO analyst is on the the Search Applicants modal
* https://jacklyn808742.invisionapp.com/console/FOI---Intake-ckpq19frj032r013q6gpm8t1m/clp8r0umw0g3m016n9wh9gobi/play
* WHEN the IAO analyst enters information in the Search Bar (e.g. DOB, Primary Phone, Email, etc.)
* THEN search will update with the refined results

...

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team´s backlog)**

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.