Consumed NRs Validation in Affiliations
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
## What is the problem?
* Currently in Auth-db prod, There are over 30k Name Requests (NRs) that have already been consumed (i.e., associated with active businesses or have business numbers) from the years 2020 to 2022. These are legacy entries that existed prior to the implementation of the stale NR deletion workflow during the business affiliation process. As a result, they contribute to increased response times for the /affiliation/search API call used by the Business Registry Dashboard (BRD).
## What is the impact?
* Longer wait times for users in loading BRD
## Proposed solution
1. Setting the 'is_lear_loaded' flag false in entities table in auth can automatically ignores these rows for querying.
2. Deletion of these records from entities table (which is happening in current workflow)
## Approvals Required:
- [ ] Olga / Mihai
- [ ] Omid/Eve
- [ ] Travis
- [ ] Argus/Vysakh
- [ ] Severin
## Pre-Requisites:
- [ ] Validate the existing workflows , if any, using consumed NRs from endpoint **/affiliations/search** [namex/lear]
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.