Open francois-travais opened 4 months ago
The service directories we produce using the ORServices and HSDS Airtable templates also link services directly to address so we don't use service_at_location table. For ORServices exports we have generate data for an service_at_location table to pass validation and move data to other HSDS systems.
It might be worth considering making service_at_locations table optional in a future release of the standard.
Context
In my profile I would like to remove the
service_at_location
because I've no use for it. In Soliguide our services are always linked to a physical location, therefore all the information that may live inservice_at_location
is either inservice
orlocation
.Problem
hsds_schema.py
is expecting aservice_at_location
, otherwise it fails to compile the schema. I had to comment these lines.Question
I'm wandering maybe the problem is that I shouldn't remove
service_at_location
in the first place. I can have one for sure, it's just that it would be a useless piece linking services and locations.