search

MAPC / youth-match-v2

App to match youth to summer jobs in Boston using Gale-Shapley
2 stars 1 forks source link

Consolidate All Offers into Offers Table #167

Open mzagaja opened 6 years ago

mzagaja commented 6 years ago

In order to streamline our process and tracking offers made through direction selection and lottery should occur in the offers table. We may want to add an Enum to indicate whether it was a direct selection or lottery offer.

mzagaja commented 6 years ago

After talking with @ericyoungberg we decided that conceptually it makes sense to break this into two models instead of the current three. The two models can be "requisitions" which is the model that describes the relationship created when a young person selects a job and is interested in it from the job picker dashboard. The other model would be the "offer" which describes either an offer made by the lottery or by direct selection from the CBO. This way any time an offer is made it will exist in the offer table regardless of its genesis.

mzagaja commented 6 years ago

Completed today:

  1. If a user picks a job then a request can be sent to the API to associate them with the job through the requisitions table.

  2. If a user then subsequently unpicks a job then a request to the API can be sent to unassociate them with the job.

Still to do:

Send a request to make them an offer from the CBO dashboard. I think this is already set on the backend. But let me know @ericyoungberg if you need more on this.