Import Names Data pre 2018 into NameX postgres database

***** Spoke to Thor and Greg, should move that data into the datalake instead of blowing up postgres.**

### Background:
In 2018 there was a data migration for names history but anything before that isn’t available in NameX. Having this information provides the following business value:
-Names Examiners needs to access this historical information when examining new names as examination is very subjective and based on past precedences.
- It's to help us research and to see who approved it in the past. For example at the end of a specific employment of an examiner they didn't care and was giving names to everyone. Even names that should not have been approved.
-to see if at one time a name was approved ( but never used) which creates precedence that we can approve it.
- this info is very helpful to get clarification and provide consistent info to the submitter when a name was previously submitted, especially when it is hte same client.

### What data is required?

BCOL account number are used to see if the same law firm has requested
Maybe we can use BC Registry account number
Or even the BC Registry account name

Want comments - outside of decision
Want to know the examiner’s name
Additional information field within decision (macro and the free form text they can add)
Any upgrades
Need whole history
Applicant information - but not fax
Consents rec'd (date and text)

**Staff need basically every little thing that we collect right now. There is not one piece of data that they don’t use.**

**Payment!!** Something we don’t have in NameX now, but we have it in the databases (NRO payments and name request payments). Can we display it in NameX?

How often do we look at old things?
* Might just need to see the history of a name, that happens frequently.
* If a name is closely related, we look at all the old ones (might be super old) to see if it was requested by the same person, if there was consent required
* Appeals are super intense and always look at old data

Make this as seamless as possible. Import into transaction history or have link to data lake report in Names.
Don't need to print anthing off. They use info and make comment in NameX.

### Tasks:
Option 1 - datalake

Option 2 - import tables (not feasable due to database size and storage costs)
It should not be too difficult the data is in DB2 tables. There are 1030930 NR; the oldest is 2001. If Bob remembers correctly there was an archive job run at the end of each year. So the data older than 2001 if needed should be in files on the mainframe.

- [ ] create 2 tables in your NameX database. One for the NR and the other for the names. @bfbowles can provide the data definitions for the tables.
- [ ] Once those are created just need to export the DB2 data into a file then import into your postgres tables. Siddharth (home team) or Bob can do the export/import. Who ever does it will need access to the Namex database.
- [ ] Verify in NameX that the transaction history displays correctly for these NRs

**Question: is there any work needed in NameX API to search these new tables?**

**Note: If we want Siddharth to do the actual importing we'll need to send an email to IT Ops or open up an Ops ticket.**