Difference between revisions of "Talk:LotteryProcess"

From TBSPedia
Jump to: navigation, search
Line 1: Line 1:
 +
=== Generalized TodoList ===
 +
 +
# Add secondary email addresses. Index on ANY email address.
 +
# Need cookie login feature
 +
# write wiki auth cookie as well?
 +
# rss feed for avalanche reports!
 +
 +
 
=== Comments ===
 
=== Comments ===
  

Revision as of 23:12, 24 November 2007

Generalized TodoList

  1. Add secondary email addresses. Index on ANY email address.
  2. Need cookie login feature
  3. write wiki auth cookie as well?
  4. rss feed for avalanche reports!


Comments

--13:09, 7 September 2007 (PDT)

  • I wanted to say to the database was that on January 21st I either wanted a patrol day or a boreal day. If I could't get it as a boreal day then I still wanted it as a patrol day. Same with the instructor day. Apparently it won't let you enter any date twice.
* This is an excellent idea. I will make this happen, with the disclaimer that 
  "patrol days take precedence over other activities, so if you want to instruct/boreal on a given date, 
  do not select a patrol day for then." --GregMarsden 13:09, 7 September 2007 (PDT)
* DONE --GregMarsden 13:38, 7 September 2007 (PDT)
  • Also, is there anyway that your ranking can be resorted like the que

in netflix? You know, you change the priority and all the rankings after that change?

* This is a great idea but beyond my meager abilities! --GregMarsden 13:09, 7 September 2007 (PDT)




1. Determine the planning calendar and set some key dates and get some from others. The TBSP training dates are determined so that: - Avy 1 is before the overnight, but preferably no earlier than the 3rd weekend of January due to the possibilities of a low snow pack before that. - Overnight falls on or just before a full moon. Better to have moonrise before dusk than later. - Banquet is on the weekend with a lot of people up, like candidate evaluation, near the end of the season. - Set the Board meetings (so Board members can plan on attending) for the weekends with instruction or other events (but not the overnight).

2. Determine how many patrollers there are returning, which then means you can determine how many total patroller-days there will be. This gives you the minimum patrollers per day. For example, 40 returning patrollers is quite different from 20. You’ll also need to know the size of the Candidate class so you can plan for about 1 instructor for every 4 patrollers (including Avy 1 Class). If you don’t know, you could use last year’s numbers as a good guess.

3. Minimum number of patrollers is 2 full patrollers plus candidates. In the past our approach was to have the minimum on Sundays, but then more on Saturdays, especially January to end of March so we could cover Tahoe Meadows as per our agreement with Toiyabe NFS (I believe our agreement is to cover those months – not the Saturday part). You could also just see how they fall and adjust with those who are late – there are always some who don’t pick in the time-frame, or decide to stay another year after much peer pressure).

4. Rules for credit should be published before the picking of the days. During past sign-ups, as the picking progresses, the credit may be liberalized to encourage more volunteers – such as we did recently with the dryland instruction.

5. For the last 2 reasons cited above, I would recommend that people pick in waves, so that some of the restrictions can be in place for the 1st wave of say 6 days (with say 8 choices), and then the last 2 days (with 4 choices). Alternatively, let the instructors and mountain managers pick first, then they get their bonus round before the rest of the patrollers. I think once the lottery is opened up, the mtn mgrs and instructors should have their remaining choices ranked starting with the number after their credit days already signed up (for example, I sign up for 4 instructor days, then my lottery days start with #5).

6. The administrator always needs to read over all the days on the complete calendar, to make sure there are no mistakes. No matter how well Mike or I or Lorrie think we did to set up the days, it seems there’s something we didn’t predict. Plus we always check that everyone has there minimum number of days. And the requirements are different for 4 groups – Full patrollers, Associate patrollers, Returning-Non OEC candidates, (and incomplete candidates), and candidates.

7. Is it possible to have some blackout days? For example, I have vacation plans around my wife’s teaching schedule and vacation plans, but I can generally patrol any of the remaining days. I only care about my first 6 days, and after that could take any day other than March 2nd/3rd and March 9th/10th. Perhaps if people don’t submit 10 days but only 6, then they would be assigned the days where it’s needed.

8. To accommodate the people that want to patrol/carpool together, maybe we could have a round of changes at the end, say only 1 day at a time. As long as by removing yourself from a day the patrol doesn’t fall below 2, I don’t see why we can’t be more flexible.

FUNCTIONS: After the days have been assigned, here’s the things would be nice for the calendar to do: - viewable for a weekend at a time so the Mtn Mgr can print their roster (with latest changes). - people can be added or subtracted by an administrator(s) - viewable sorted by each person and by date for the whole year. - Patrol roster with contact viewable/printable (to be submitted to Forest Services), and the cell phone numbers exported so I can make the cell phone contact list that goes into the radio pouches. These rosters should probable have some kind of Revision Date, so we know what/who is on the roster we give to the Forest Service. We usually are adding people (such as for Ski-alongs) so we have submit updated rosters during the season. I don’t think they care what the roster print-out or format looks like, but they need names and addresses in order to cover us for Workers Comp. - Lorrie has also used the Access database to record attendance after the patrol – who showed up, who didn’t but had a good excuse, and who didn’t show up with no notice. We should bring her into the beta testing to make sure we can gedo all the things she was doing.


Validation problems on the the information page:

  • get page expired error when clicking back to fix validation errors
* DONE
  • not checking valid date, just format (ie. 12/36/2000) works
* DONE
  • phone number (just checking numeric) not validating use this regular exp .

. . ^(?:\([2-9]\d{2}\)\ ?|[2-9]\d{2}(?:\-?|\ ?))[2-9]\d{2}[- ]?\d{4}$

* DONE
  • Zip not validating use this . . ./^\d{5}([\-]\d{4})?$/
* DONE

Picking Patrol Dates:

  • on the 'Almost Done' page, put error messages at the top
* DONE
  • put duplicate entry validation errors next the duplicate dates chosen,
* DONE



Personal tools
Namespaces

Variants
Actions
Tools
Resources
Toolbox