specification

specification copied to clipboard

eligibility constraints

5

The eligibility table allows a string with includes a constraint with a set of enums. This does not fit any of our data for any client and the values are...

klambacher

accessibility_for_disabilities enums

3

The enums in this field are constraining values in a way that make it challenging for people to follow good guidelines for describing accessibility (https://www.fs.fed.us/eng/toolbox/acc/acc17.htm). Strongly recommend removing these enums,...

klambacher

payment_accepted enums; capacity for more detail

2

Rather than an enum, would prefer these as suggested values in the description of the field. These values are non-comprehensive and also US-centric. I would also like to see an...

klambacher

language details

2

I would like to see the capacity to provide additional detail on languages. This is a strong requirement. For example: French: not available at all times; please call ahead In...

klambacher

Allow organization and service_at_location to be categorised with taxonomy

4

At present service_taxonomy is used to related `service` objects to `taxonomy` objects, classifying a service. From #154 via @klambacher: > To my knowledge, categories would not be required to describe...

timgdavies

Introducing a flag for confidential data

3

From the API thread at https://github.com/openreferral/api-specification/issues/21 There are cases when addresses, locations (and contact details?) should not be disclosed to protect a service or service users. Whilst this information may...

timgdavies

Synchronising HSDS and HSDA documentation generation

2

At the moment HSDS is defined via a [datapackage.json document](https://github.com/openreferral/specification/blob/master/datapackage.json). The [HSDA API](https://github.com/openreferral/api-specification) uses JSON Schema for definitions, manually created from HSDS. We want to move towards a situation in...

timgdavies

Multiple opens_at / closes_at times within schedule?

4

via @derekfidler's [comment on our ReadTheDocs](https://hyp.is/Ly5K-ox5EeehvRtgW_FIow/docs.openreferral.org/en/latest/reference/): > We've found from working with shelters and other services for the homeless that many services have multiple opens_at and closes_at times within a...

greggish

Key schemes for regular_schedule and holiday_schedule

1

I'm looking at the three foreign key fields in each of the two schedule tables. Would it make sense to have a service_schedule table with the schedule (however that is...

rasmus-storjohann-PG

It is unclear whether a service is unique to a location

2

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...

dylanmccall