Skip to content
This repository has been archived by the owner on Dec 12, 2023. It is now read-only.

Schema definition and fixture json #2

Closed
kencheeto opened this issue Mar 31, 2013 · 1 comment
Closed

Schema definition and fixture json #2

kencheeto opened this issue Mar 31, 2013 · 1 comment

Comments

@kencheeto
Copy link
Contributor

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.

@kencheeto
Copy link
Contributor Author

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant