General scheduling application - Revision history

Rfs at 18:23, 14 June 2011

2011-06-14T18:23:24Z

Rfs: /* Path forward */

2011-06-14T18:22:52Z

Path forward

Jhiggins at 19:24, 25 May 2011

2011-05-25T19:24:06Z

Ryan52: /* Suggested features */

2011-04-09T19:07:56Z

Suggested features

Ryan52: /* Remaining Todos */

2011-04-02T22:08:26Z

Remaining Todos

Ryan52: /* Remaining Todos */ done

2011-04-02T20:42:30Z

Remaining Todos: done

Ryan52: done

2011-03-26T18:56:57Z

done

Ryan52: /* Remaining Todos */ fixed

2011-03-23T18:32:12Z

Remaining Todos: fixed

Ryan52: /* Remaining Todos */ some of my todo list is now done too

2011-03-23T05:11:17Z

Remaining Todos: some of my todo list is now done too

Ryan52: /* Suggested features */ done

2011-03-23T04:55:04Z

Suggested features: done

← Older revision		Revision as of 18:23, 14 June 2011
Line 1:		Line 1:
−	~~{{Hours Change}}~~
−
−
	{{RightTOC}}		{{RightTOC}}
	Free Geek has many scheduling needs. These are currently being handled in several different ways.		Free Geek has many scheduling needs. These are currently being handled in several different ways.

@@ Line 33: / Line 33: @@
 This application would be developed in parallel with [[FGdb]] with the intention that it would be merged into that project. The first step would be to computerize the paper schedule for the build program. Once done, the functionality should exist to port the paper class schedules and all of the volunteer intern schedules into the same system. (See Milestone One below.)
-Integrating the adoption program volunteer schedule would be the next step. The shifts in this schedule can be filled by several people over the day. For example, the receiving area is open from 11-7. There are a few volunteers there at any given time. But one might show up at 11, work until 2 and then be replaced by someone arriving at 2. Another might start at noon and work the rest of the day. Contrast this to the build, prebuild, and advanced build schedules, as well as the classes, where a shift is defined with a start and end time, and is filled with just one volunteer. (See Milestone Two below.)
+Integrating the adoption program volunteer schedule would be the next step. The shifts in this schedule can be filled by several people over the day. For example, the receiving area is open from 10-6. There are a few volunteers there at any given time. But one might show up at 11, work until 2 and then be replaced by someone arriving at 2. Another might start at noon and work the rest of the day. Contrast this to the build, prebuild, and advanced build schedules, as well as the classes, where a shift is defined with a start and end time, and is filled with just one volunteer. (See Milestone Two below.)
 After that, the next step would be to implement support for events that do not happen each week. So far all the events scheduled happen on a regular weekly schedule. Once we can schedule events that happen on a monthly and/or twice monthly basis, we will be able to accurately deal with meetings and more of the classes. Tracking vacations (time ranges when people are removed from schedule, leaving their shifts empty) and holidays would also be done at this point.  (See Milestone Three below.)

← Older revision		Revision as of 19:24, 25 May 2011
Line 1:		Line 1:
		+	{{Hours Change}}
		+
		+
	{{RightTOC}}		{{RightTOC}}
	Free Geek has many scheduling needs. These are currently being handled in several different ways.		Free Geek has many scheduling needs. These are currently being handled in several different ways.

@@ Line 584: / Line 584: @@
 From Recycling:
 * "No Work" entry = volunteer #84691, but - we need a way to stop folks from turning this into "available" just because "No Work" did not change to "arrived" within 30 minutes.  Training might work....
 * "!" = Add some # of extra lines for when we want to be overbooked with volunteers, but prevent volunteer being signed up in those slots without recycling's approval (similar to the "No Walkins" flag).  This may mean only letting Recycling enter the volunteer in?

@@ Line 558: / Line 558: @@
 == Remaining Todos ==
 * volunteer_events creating/editing interface sucks
 ** needs some way to do multiple slots in a single line, real quick like.

@@ Line 569: / Line 569: @@
 * rework the hours logging to be like the staff hours, and to preseed based on assigned shifts
 ** this will probably close #12482
 * restrict time range widget on assignments
 ** limit to the range that is within the shifts range unless extendable? (ex: printers can be extended past two with intructor permission)

@@ Line 563: / Line 563: @@
 ** is otherwise buggy, I think
 * interns can be scheduled for things that there are volunteer slots for, and then it gets a high up slot id or displaces the normal volunteer slot ids. intern and staff shouldnt even have slot numbers.
 * default_assignments skedjul view
 * copy function have option to include {default_,}assignments too

@@ Line 571: / Line 571: @@
 * rework the hours logging to be like the staff hours, and to preseed based on assigned shifts
 ** this will probably close #12482
-* make generate do resources too
+* checkboxes for generating resources or shifts or both on the generate widget
 * restrict time range widget on assignments
 ** limit to the range that is within the shifts range unless extendable? (ex: printers can be extended past two with intructor permission)
@@ Line 579: / Line 577: @@
 * have a select_visibility for type that allows selection of volunteer tasks id or selection of class_type_id (new table, class_types)
 ** will eventually be used for job_id, etc for staff
 * fancy: ajax filter_criteria, ajax form opening (rather than popup), reload schedule display (or relevant parts) on save

@@ Line 594: / Line 594: @@
 Also:
 * Some comments on contacts are not appropriate for presenting on the schedule. I printed out 100 recent comments and am asking for types of notes people actually take, so we can set up different types of comments, some of which should show up on the vol schedule, and some of which should not.
 [[Category:FGdb]]