bcgov / bcgov/entity

Entity BN - Update dissolution or put back on flows to work with alternate names

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

Description

Update bn processor such that we are able to work with alternate_name entries where required. With the new data model, SPs will need to use alternate_name similar to the way we use a legal_entity record.

**TODOs**
Do following for bn processor(s) relevant to this ticket:
- [ ] Do work in legal name branch
- [ ] Update to work with alternate names and legal entities
- [ ] Update versioning logic where required. May be still using versioning approach used in old data model
- [ ] There may be some other misc updates required to get processor working. Update as appropriate.
- [ ] Update LegalEntity, AlternateName and Filings model manually in common models to match with legal api models as required
- [ ] Update worker.py as required
- [ ] Update tests relevant to this bn processor

Contributor guide

No contributing guide indexed for this repository

Research direction

Locate the relevant bn processor, worker.py, and the common LegalEntity, AlternateName, and Filings models. Review the legal name branch and existing processor tests first, then compare the common models with the legal API models and inspect versioning behavior. Done means the processor handles alternate names and legal entities, uses the required versioning, and its relevant tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
postgres, python
Domain
api, backend, database
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.