Initial attempt at a data model and API for capturing availability.

[nschiefer]

This is a first attempt at representing appointment availability in our data model/API. It is meant to be half-prototype and half-discussion piece.

• Models for representing availability reports and availability windows.
• REST API endpoint for writing those availability reports.
• Basic test that the API endpoint works.

To see an example of how this API interacts with a prototype scraper (for Curative), see https://github.com/CAVaccineInventory/vaccinebot/pull/74.

[nschiefer]

Tests are failing because I'm not sure how to set environment variables in our CI system.

[obra]

Are you thinking that we're going to want to show exact, specific appointment windows on the website in the near future? Or is the goal more of ">x appointments available in y timeframe, last verified 27 minutes ago"?

[nschiefer]

For the website, I think that we should do something like the latter (probably binned by day or maybe even week?). But, I would like the data recorded in the highest fidelity that we can (for analysis, and so that we can change our minds, and to make the job of the scraper easier), and the binning to be done on the data-publication side.

[nschiefer]

Or, put another way, I want x and y to be determined by the data-publication team, rather than the scraper team.

[obra]

That is a very reasonable choice :)

Are you thinking that availability reports are the representation of availability or that we would eventually be creating our own representation of appointment availability and that the 'reports' would feed into that? (Does that question even make sense?)

[nschiefer]

My plan was to use the availability reports as the representation of availability and then generate the relevant view with a query. I don't have any objection to materializing some objects for this (akin to PublishedReport) but I don't see a reason to do that so far.

[obra]

One possible reason is that there's a very good chance we'll end up with multiple sources of availability info for a given provider.

…

On Thu, Mar 4, 2021 at 6:21 PM Nicholas Schiefer ***@***.***> wrote: My plan was to use the availability reports as the representation of availability and then generate the relevant view with a query. I don't have any objection to materializing some objects for this (akin to PublishedReport) but I don't see a reason to do that so far. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#50 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAALC2GJI4HJD4G7UO6YJHLTCA535ANCNFSM4YUIKBYQ> .