- Creates a judging team for each special award
- Assigns judges to special awards based on the number of students self
nominated.
- Obeys the judges special award preferences (if enabled), and also
judges that specify if they are a judge for a specific special award
(if enabled).
- Add 2 new config variables.
- Enable the special award scheduler
- Specify the max. number of projects each special award judge can
handle (default: 20)
- Delete an extra blank line in register_participants_students.php
- Overhauled the report generator.. It's more versatile now
- Added 'filter' option to the generator, so you can filter any column by (=,
<=, >=, <, >, IS, IS NOT, LIKE, NOT LIKE). It doesn't support AND or OR
combinations, but that should cover what we need for now. Example: We can
filter "Award Name" LIKE "%Gold%" to generate a report of just the Gold medal
projects.
- Wipe out the report database, and create it again from scratch.
update.48.sql contains an example of how to add additional reports to the
system without knowing the report_ids, because after regions start adding
their own reports, we won't be able to just wipe out the whole report system
to add one.
- We handle more reports now, specifically nametags and table labels, so remove
those files, and update the reports.php file to link the old links to the new
report generator (so people don't get too confused in this transition).
- Beginnings of moving the report generator to proper LEFT JOIN style
constructs instead of just one big massive EQUALS JOIN.
- Change the fair title font to 13pt (from 14pt), it was spilling over onto the
second line for many fairs (Waterloo-Wellington, Greater Vancouver, Quinte,
Fraser Valley) Actually, the size of that should probably be proportinal to
the size of the label.. that'll come later...
- Add committee member generator
- It is now possible to generate ALL nametags the old system could generate
(needs a DB update before that happens... actually, the report generator
isn't as stable as I hoped.. I'll probably just nuke the report tables the
next upgrade and recreate them all.. I'm probably the only one who has tried
generating a custom report. :)
- This also changes the newlabel function, so just thinking about it, I think
there's a 0.15 missing in the alignment that was moved inside a conditional
for labels... All labels will be replaced soon anyway. :p
enough.. Currently we can't produce both a list of judges and a list of awards for each
team with the generator (how the heck would we express that with an SQL statement)
- Add an editor for that generator.. it's not flawless, but it's not hard to
use either.
- Add 19 default reports
- Replace several reports on the report page with the new generator versions
(they pretty much look the same, same info, same sort order, same pagination)
- Add a pulldown menu to the report pages so any report can be generated
- Allow the addTable array to contain an 'option' array, with one supported
option 'allow_multiline' => if true, it allows cell data to spill into
mutliple rows, instead of just printing ... if the text doesn't fit.
- Ignore the addText2 function, it is for label generation and isn't finished
yet.
- Hardcode add a special award to the top of the list "I do not wish to
nominate for any special awards". Allow the
project_specialawards_link.award_awards_id field to become NULL, and set it
to NULL if the student selects this award.
- Fix the display of the award status based on whether the student has or has
not specified that they do not wish to nominate for special awards.
registration sections are complete.
- Display a warning in the special awards that selection is only available
after the project and student information is complete. Since some awards
check this information, we can't let students in until it is completed.
- Add an option to the project editor to regenerate the project number
- Fix a bug in the project number generation. Include YEAR in the project
number check (and in the number generation) so we don't find a project from
last year (that already has a number), and decide not to generate one for a
project from this year. The $checkNumQuery was returning 2 rows.. one from
2006, one from 2007. Two projects from different years had the same
registrations.num (665983) in my test.. about 10% of the projects at the VDSF
collided with numbers from previous years.
