bcgov / bcgov/entity

Colin Reports Migration of Historical Companies: Decision/Strategy

Open
#33,841 4 comments 0 reactions 1 assignee Claimed by @TVWerdal View on GitHub
Entities - Data Migration
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

Colin reports migration uses colin ui screen scraping to request ledger history filing reports from the colin report service. This approach only works with active, non-frozen companies. We need a decision on whether filing reports for companies in a historical state need to migrate. If so, are reports for all companies migrating, or is there some filter criteria? The follow up question is how? With the current approach, companies need to be temporarily unfrozen and changed to an active state in the colin database. Database access requires VPN running, so these updates are manual.

Assumption: no code changes to colin are allowed to open up access to ledger filings in a frozen or historical state.

Filtering may be on how recently the company became historical. For example, within the last 10 years.

An alternate approach may be to migrate the historical busiinesses to TEST without de-identifying the data, change the state in the database to active/non-frozen, and create or open up a TEST colin application url to work without running a VPN (currently required).

If using the active company solution, small batches of companies would temporarily be set to active for a period of up to 1 hour.

Oge verified in PROD colin that staff can view the ledger history for companies in a historical state:
colin_ledger_historical_staff_example.png

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.