Filer - Update correction filing processor to work with alternate name changes(DO LAST)
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
Update filing processors such that we are work with alternate_name entries if required. With the new data model, SPs will need to use alternate_name similar to the way we use a legal_entity record.
If the filing processor only works with legal entity records, it may be the case that no major updates need to be made to work with alternate_names.
For each filing processor, do the following:
- [ ] Do work in legal name branch
- [ ] Update to work with alternate names and legal entities
- [ ] 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. If #19451 has been completed, this may not be required
- [ ] Update worker.py as required
- [ ] Update to ensure that everything is persisted and retrieved correctly according to new data model
- [ ] ignore alias logic. work will be done in another ticket
- [ ] Update tests relevant to this filing processor
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the correction filing processor and its legal-name branch, then inspect worker.py and the common LegalEntity, AlternateName, and Filings models. Update the processor and persistence behavior for legal entities and alternate names, and run the relevant filing-processor tests to verify retrieval and persistence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, python
- Domain
- backend, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100