bcgov / bcgov/entity

Alignment with other teams

Open
#15,949 2 comments 0 reactions 0 assignees View on GitHub
Entities - Data Migration ENTITY - DO NOT USE
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

We will need to determine the logistics around how we can deliver legal names changes to Prod as it relates to teams outside of Entities.

Teams that we need to consult with to determine what they need from us to integrate/test our latest changes and what timelines are feasible for them.

| Team | Updates/Testing Req'd |
| ------------- | -------------------------------------------------------------------------------------------- |
| Relationships | Auth Web UI |
| IDIM | May only require testing of updated legal api. Need to confirm. |
| OrgBook | They hook directly into LEAR db. May require a lot of work on their side. |
| Misc | Business Search SOLR Feeder |
| OCM | Confirm timing and what they need from us. |
| SRE | There are some notebooks in LEAR repo. Anything that needs to be updated in timely fashion? |

Contributor guide

No contributing guide indexed for this repository

Research direction

The issue names no files, tests, or entry points. Start by consulting Relationships, IDIM, OrgBook, OCM, SRE, and the Business Search SOLR feeder owners to document their integration and testing needs for legal-name changes. Done means the required work, owners, and feasible production timelines are agreed across teams.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, postgresql, python
Domain
api, backend, database, release
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
15/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.