Katherine Lambacher

service_category table: Linked Taxonomy Terms and IDs

2

Regarding the service_taxonomy table, the taxonomy_details field describes allowing linked Terms (two terms used together to make a compound term) but still implies a single Taxonomy ID from the service_taxonomy...

Alternate name structures

3

We have a highly structured alternate name system that includes individual entries for multiple alternate names (AKAs), former names with dates of change, and legal names. I wouldn't necessarily argue...

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

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

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

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