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
We need to handle Labor participation in events. There is not a firm conclusion as to how. We could handle it at the event level, with a Labor/Non-Labor toggle, either exclusive or not (resulting in two separate events if labor students need to be recorded), or at the hours level, with each volunteer getting a Labor checkbox to indicate whether or not the hours ‘count’ towards service totals (or a Service checkbox that defaults to true on service events, showing whether the hours should be on service transcript). The latter option would be the most flexible but result in a number of changes to places where we show service hours. We could also have a separate place in the UI for labor students, as they are not really ‘volunteers’, and then handle the management of a service or labor flag on the backend. As an example of the problem, the Better Together and Empty Bowls events have both labor students working and student volunteers who are getting service hours, so we would either need two separate events for each (a labor and nonlabor), or one event but track labor and service hours separately. Another option could be having Labor as a program that is available only for labor students.
The text was updated successfully, but these errors were encountered:
We need to handle Labor participation in events. There is not a firm conclusion as to how. We could handle it at the event level, with a Labor/Non-Labor toggle, either exclusive or not (resulting in two separate events if labor students need to be recorded), or at the hours level, with each volunteer getting a Labor checkbox to indicate whether or not the hours ‘count’ towards service totals (or a Service checkbox that defaults to true on service events, showing whether the hours should be on service transcript). The latter option would be the most flexible but result in a number of changes to places where we show service hours. We could also have a separate place in the UI for labor students, as they are not really ‘volunteers’, and then handle the management of a service or labor flag on the backend. As an example of the problem, the Better Together and Empty Bowls events have both labor students working and student volunteers who are getting service hours, so we would either need two separate events for each (a labor and nonlabor), or one event but track labor and service hours separately. Another option could be having Labor as a program that is available only for labor students.
The text was updated successfully, but these errors were encountered: