-
In there is no "categories" table mentioned http://docs.openreferral.org/en/latest/hsds/reference/
but https://github.com/openreferral/specification/blob/master/database/hsda_core.sql
has such a t…
-
I have been implementing the Open Referral API and would like to question the approach taken in the HSDA Specification to returning objects. For example, as single /services/{id} request returns the f…
-
Version 1.1 of HSDS did not have LOCATION_ID as a field in SERVICE.
Version 1.2 of HSDA (re)introduces LOCATION_ID as a field in SERVICE at line 6748 of https://github.com/openreferral/api-specifi…
-
The /locations/complete endpoint shows "regular_schedule" and "holiday_schedule", as does the "/services/complete" endpoint.
The schema, however, does not have a flag for "regular" or "holiday".
…
-
The HSDA v 1.2 no longer has a description for a SERVICE_AT_LOCATION entity, though multiple entities reference a SERVICE_AT_LOCATION_ID field. I just want to make sure the absence is appropriate in t…
-
I would also recommend holding off on the API for the metadata portion of the schema - https://openreferral.readthedocs.io/en/latest/reference/#metadata
This area needs some additional considering …
-
So [we have a reference implementation here](http://developer.open.referral.adopta.agency/), and the [HSDA documentation site points users to it](http://docs.openreferral.org/en/latest/hsda/#reference…
-
I'm starting a read for aggregating conversations at the granular level. The looseness or strictness of how the JSON schema interprets HSDS or HSA.
-
This has been migrated from Ohana (https://github.com/codeforamerica/ohana-api/issues/417#issuecomment-295782865), and worth considering as part of specification:
As part of Code for Miami's involv…
-
The phone and contact entities are child records of several different kinds of parent entities. This is implemented by these entities having multiple foreign keys, most of which will be NULL.
Pres…