You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.
A blocker for beginning concurrent working threads is deciding on a schema to build against.
Individual services rendered at each facility commonly has its own hours, notes, and supported demographics. We whiteboarded and decided on having two first class objects in our data model- facility and service.
Our schema will probably look something like this:
facility has many services
service belongs to facility
facility:
id: integer
name: string
addr: string
description: string
phone: string
hours: object (derived from aggregate services)
notes: string
geopoint: geo
demographics: array (derived from aggregate services)
category: array (derived from aggregate services)
service:
id: integer
facility_id: id
name: string
description: string
hours: object
notes: string
demographics: array
category: string
Resolution of this issue is contingent on having fixture json which we'll need to translate from the original google spreadsheet.
The text was updated successfully, but these errors were encountered:
A blocker for beginning concurrent working threads is deciding on a schema to build against.
Individual services rendered at each facility commonly has its own hours, notes, and supported demographics. We whiteboarded and decided on having two first class objects in our data model-
facility
andservice
.Our schema will probably look something like this:
Resolution of this issue is contingent on having fixture json which we'll need to translate from the original google spreadsheet.
The text was updated successfully, but these errors were encountered: