James (ODSC)

Results 24 issues of James (ODSC)

The description is the same as the description on link_id and seems incorrect.

http://docs.openreferral.org/en/1.1.1/hsds/reference/#eligibility has a "eligibility" column. (v1.1.1) http://docs.openreferral.org/en/latest/hsds/reference/#eligibility does not. (all v2's and latest)

This is currently optional - should it be required? http://docs.openreferral.org/en/latest/hsds/reference/#schedule (location_id is not required but that makes sense because a service may be virtual , by phone, etc)

We have database schemas in https://github.com/openreferral/specification/tree/master/database but nothing in the docs mentions that - we should add a page/section somewhere. From https://github.com/openreferral/specification/issues/235 Things to include: The Mysql one is for...

documentation

``` "type": "date", "format": "%Y", ``` https://www.w3.org/TR/tabular-data-model/#formats-for-dates-and-times lists formats that implementers must manage. Crucially, they are all complete formats - ie all components are represented. There is no support for...

eg. See http://docs.openreferral.org/en/v2.0/hsds/reference/#other_attribute link_type does have a lot of enum's set in https://github.com/openreferral/specification/blob/v2.0/datapackage.json#L410 but these don't show on the web page. If they showed up, the meaning of other_attribute /...

documentation
schema

"organisation" is used 3 times - we should standardise on "organization" and maybe put a note in the README on which spellings we use.

Currently has unique=true - is that right? That means each organisation can only have one program.

When this was tried before we found a breakage - The + and - things in the side menu break, and are just shown as a button with no label....