bcgov / bcgov/entity

SP/GP data migration - Transform Data

Open
#10,976 0 comments 0 reactions 0 assignees View on GitHub
Dependency ENTITY - DO NOT USE Epic
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

Now that we have extracted a copy of the firm info from Oracle database, we need to transform so that we can load it into Legal database.

- [ ] Determine how to deal with addresses - if the address transforms are too hard to reliably automate, we can do things like combine lines 2&3 into the address_additional line, leave country and region empty. The Address component would need to handle that data coming in, and we then require the user to reformat the address to be correct before updating it. We would “relax” the constraints on loading of the data, and then enforce the constraints going forward for things like Country being a mandatory field

- [ ] Things to get started on at the same time is Testing/Verification … how to best automate a quality control check that the transforms put data into a useable state
- [ ] Determine whether we need to build new 'historical' outputs
- [ ] Determine whether we need to bring over historical filings with historical filing type codes
- [ ] Anything we need to do special about DBA data?

Google Spreadsheet and Google Doc created to help with keeping track of the data loading issues/questions. Introduced to make things easier to communicate and streamline the process of dealing with the little issues that we will need to work through during the data loading process.

The spreadsheet is meant to give a high level view of the issues and issues requiring more conversation, info, screenshots etc will have an entry in the google doc.

Google Spreadsheet - https://docs.google.com/spreadsheets/d/1NWB5JobM5LNKC3NldcUTbY4omMomqYdZt9Ozy5fPaS8/edit?usp=sharing
Google Doc - https://docs.google.com/document/d/1WPC5zEj8sKvMnzXubr2CrjsAEnqcpGnyfUvj2TUhKa8/edit?usp=sharing

Contributor guide

No contributing guide indexed for this repository

Research direction

No repository files, tests, or entry points are identified. Start by reviewing the linked Google Spreadsheet and Google Doc alongside the migration checklist, then determine the scope for address transformation, verification, historical data, filings, and DBA records. Done means the open decisions are resolved and a validated transformation process is defined.

Written by the indexing model from the issue text.

Assessment

Domain
data-engineering, databases
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.