Filer - Update filing processors to work with alternate name changes (admin freeze, agm extension, agm location change)
- 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 by locating the filing processors, worker.py, and the common LegalEntity, AlternateName, and Filings models mentioned in the issue. Compare each processor's legal-entity handling with the legal API data model, then run the relevant processor tests. Done means processors persist and retrieve legal entities and alternate names correctly, with updated tests passing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- flask, postgres, python
- Domain
- api, backend, database, testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100