specification icon indicating copy to clipboard operation
specification copied to clipboard

It is unclear whether a service is unique to a location

Open dylanmccall opened this issue 8 years ago • 2 comments

In the HSDA specification, for "GET /services/", the response ID includes a single "location_id" field, which strongly implies that a service record should have a single location: http://openreferral.readthedocs.io/en/latest/hsda/hsda/#get--services-.

In the HSDS specification, there is a separate table called "service_at_location". The text doesn't say anything about service and location being unique together, so I am left to assume this table creates a many-to-many relationship: http://openreferral.readthedocs.io/en/latest/hsds/reference/#service_at_location.

So, these two seem to be at odds with each other. I would really appreciate some clarity on how this should look, and it would also help if the specifications were a bit clearer about it.

dylanmccall avatar Dec 20 '17 21:12 dylanmccall

The location_id on services was legacy artifact, that should be deprecated--didn't get caught in last release.

kinlane avatar Dec 20 '17 22:12 kinlane

Labelling api - this issue is still current

robredpath avatar Feb 17 '20 12:02 robredpath