bcgov / bcgov/entity

Data verification - corp scenarios previously documented (part 5)

Open
#27,554 1 comment 0 reactions 1 assignee Claimed by @vishnup0422 View on GitHub
Entities - Data Migration
Dominant language
JavaScript
Stars
23
Forks
62
Avg merge
24m
Merged PRs (30d)
1

Description

David Roberts had previously provided a [list](https://hackmd.io/@achiu3q/Hk7b0TUvJl#Test-Scenarios) of corp business identifers that he had maintained for corps with specific scenarios.

Our intention is to data load a good chunk of these businesses and perform data verification to ensure the tombstone data has been pulled over correctly.

For the purposes of this ticket, we will select some corps from the [list](https://hackmd.io/@achiu3q/Hk7b0TUvJl#Test-Scenarios) and perform data verification activities.

**Tasks**
- [ ] Load data into QA account for following business identifiers using tombstone pipeline into Test
* conv_event.effective_dt is the dissolution date BC0000159
conv_event.effective_dt is the name change date BC0304766
conv_event.effective_dt is the restoration date BC0261945
conv_event dates not used, event_timestmp of 20040326 used BC0120911

image.png

- [ ] Verify data as per usual in Test
- [ ] Update [QA identifiers snippet](https://hackmd.io/@achiu3q/Hk7b0TUvJl#Identifier-Snippets) in migration testing doc to include data loaded business identifiers
- [ ] Updated tested status under [test scenarios](https://hackmd.io/@achiu3q/Hk7b0TUvJl#Test-Scenarios) in migration testing doc

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.