You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have some situations where the database has manually entered data for provider locations, and we have to be very careful not to accidentally overwrite it. Instead, we should be tracking a list of manually overridden
We could track manual overrides in a new DB table as part of #202, but it might be better (especially in the short term) to simply keep them in a file in our source code. Storing them in a source code file means they are easy to see, review, and update (and we multiple eyes on them via PRs). We don’t have any GUI that gives us a similarly clear window into overrides we might store in the database. (Props to @janovergoor for pointing this out.)
The text was updated successfully, but these errors were encountered:
We have some situations where the database has manually entered data for provider locations, and we have to be very careful not to accidentally overwrite it. Instead, we should be tracking a list of manually overridden
One example of this is that NJVSS has some bad 4-digit zip codes, and they are manually fixed in our database. The NJVSS loader has to be very careful to check for bad zip codes so as not to overwrite what’s in that field in the DB: https://github.com/usdigitalresponse/appointment-availability-infra/blob/ce4c936107d2a449d530d41e7d24b5e32f68dffe/loader/src/sources/njvss/index.js#L402-L407
We could track manual overrides in a new DB table as part of #202, but it might be better (especially in the short term) to simply keep them in a file in our source code. Storing them in a source code file means they are easy to see, review, and update (and we multiple eyes on them via PRs). We don’t have any GUI that gives us a similarly clear window into overrides we might store in the database. (Props to @janovergoor for pointing this out.)
The text was updated successfully, but these errors were encountered: