Emailer - update affiliation processor to work with alternate name changes
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Update email processor(s) 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 email 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 worker.py as required
- [ ] Update tests relevant to this email processor
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by locating the email processor(s), their legal name branch, worker.py, and the related tests. Read how legal_entity and alternate_name are represented, then trace the existing versioning logic; done means the processor handles both alternate names and legal entities and the relevant tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100