Note: merge the 'fix date picker' PR before this one.
The old method of bootstrapping the matched table wasn't going to work under the new regime of the matcher table being updated instead of replaced. So I simplified things by removing the distinction between the matched table and the master table: there is only the master table, which may or may not have useful matches. So quite a bit of code is gone now.
For some reason, the output that matcher was giving wasn't working with smart_open, so i switched to s3fs. I'd like to keep it agnostic to storage medium, but smart_open is just giving endless problems. I think the triage/skills_ml storage abstractions are needed here, but that's for another day.
Note: merge the 'fix date picker' PR before this one.
The old method of bootstrapping the matched table wasn't going to work under the new regime of the matcher table being updated instead of replaced. So I simplified things by removing the distinction between the matched table and the master table: there is only the master table, which may or may not have useful matches. So quite a bit of code is gone now.
For some reason, the output that matcher was giving wasn't working with smart_open, so i switched to s3fs. I'd like to keep it agnostic to storage medium, but smart_open is just giving endless problems. I think the triage/skills_ml storage abstractions are needed here, but that's for another day.