creating anomaly_db_transfer

[BradleySappington]

Created transfer script from postgres anomaly database to django models.
Add fields to anomalies model

[BradleySappington]

This script should only need to be run once on production to transfer the existing postgres anomaly database over to models.

This code will need to be run after code to access anomaly information from the model database is implemented

[mfixstsci]

@BradleySappington sounds good, so if I understand correctly, this will transfer our information gathered in the anomaly table on production over to dev and test?

[melanieclarke]

This looks good to me, and I think it will be very helpful to have this info in the models instead of the postgres table.

Spot checks with my local models and the dev db look good on test files with known anomalies look good -- I see the new entries in the Anomalies table and updating them via the app, rerunning the update, and checking again updates them appropriately.

[BradleySappington]

@BradleySappington sounds good, so if I understand correctly, this will transfer our information gathered in the anomaly table on production over to dev and test?

@mfixstsci we have separate test, dev, and production postgres databases. This will transfer the existing DB information into the related django db. So if we run on Dev (which I did), it will update the dev server models with dev data (not production).

[BradleySappington]

@mfixstsci ready for merge

[BradleySappington]

closes #1187

[BradleySappington]

@mfixstsci SERVER UPDATE AFTER MERGE:
run
$python manage.py makemigrations
$python manage.py migrate
$python anomaly_db_transfer.py

[mfixstsci]

Thank you @BradleySappington

[mfixstsci]

@BradleySappington with my comments addressed and @melanieclarke's review, I am rebasing and merging. Then I will go ahead and run the commands on the servers!

[mfixstsci]

@BradleySappington I merged the PR and then ran the commands on the develop branch on both production and dev. Thank you!