search

fishbaugher / WAweb-Issues

A repository to track issues with WAweb usage. This includes problems, work arounds, shortcuts, and workflow suggestions
0 stars 0 forks source link

Uploading Clients(Accounts)/Contacts/Audits/Standalones from FacsPro #5

Open fishbaugher opened 10 months ago

fishbaugher commented 10 months ago

In v8.x the CSV file import feature is used to interface with files generated by the MN FacsPro system in order to coordinate identifiers, transmit addresses, names and create skeletal Clients/Accounts, Audits, and Work Orders (e.g. Standalone work).

Untitled

This process assigns the primary key for the account to the household (HH) number established outside the WA system and creates a tblClient record with that primary key. The state system also feeds the contact information, residence address, and assigns an identifier for the audit (if performed).

Without an automated process for importing this information, all the data would have to be re-keyed with serious potential for data entry error.

fishbaugher commented 8 months ago

A similar issue exists for the agency contact list. There are hundreds of records in the existing system that would have to be double entered. Lots of work, lots of possible errors. Just need an import feature here.

fishbaugher commented 8 months ago

We need two new import feature similar to the Help/Load Economic Parameters existing feature. One for Account/contact/work order, and the other for agency/contact.

fishbaugher commented 7 months ago

The workaround (manual, error prone data entry) get a Poor rating in the label.

eckmanwe commented 7 months ago

Please clarify. Is this a request for: 1) Conversion of existing WAv8 database data into WA-MNarchive data 2) One-time request to import external data directly into WA-MN 3) A new feature in WAweb to directly import external data into a secure database?

fishbaugher commented 7 months ago

Bill,

Hopefully the following will clarify:

This is a request for an import feature to create current accounts, audits and work orders. In the current workflow, the v8.x CSV file import feature is used to create new records that are sourced from another state system called FacsPro. That system creates a tblClient.csv file, an associated tblNJob.csv or tblMJob.csv record and in the case where standalone work is ordered (no audit) then tblWorkOrder.csv is also included.

Since the WA v8.x CSV import feature can work on a sub set of fields, these CSV files are really pretty skeletal, with just the primary keys, and contact information filled in, as well as assigning unique names for the households (HH number), audits, and work orders across the state.

So, this is the third option "a new feature" to import/create skeletal account, contact, audit, and work order records from a CSV file input. I am sure the exact set of columns in the CSV could be adjusted from the MNDOC side as well as the file format (JSON?) .

So, a single JSON input with just a few PK fields would suffice, mostly to eliminate duplicate data entry for crucial things like

1) Unique names. 2) Contact information. 3) Dwelling type, demographics, and address