Locations and Projects

Locations are used to partition a single kind of activity into multiple analogous activities. Imagine an art show for both adults and children where you wanted to define separate activities for judging the kids and judging the adults. One way to do this would be to:

Projects are used to group together different kinds of activities. For example, if you had a Write Brochure activity, a Contact Local Businesses activity, a Do Town-Wide Mailing activity, and a Publicity Chair activity, you might want to give them all the same project name, say Publicity.

How Locations and Projects Can Enhance Ease-of-use

Planning ahead to define locations and projects requires a little extra work. The ease-of-use benefits from that extra work are:

Category Requests and Locations

You use the Category Request signup style when you want people to request a job category and then have an admin assign them to a specific job in that category. Also this feature is designed to make it easy to keep tentative schedule assignments private until you are ready to share them.

More specifically, after someone signs up for a job category and you have used the admin-signup page to *move* her to a specific job, the signup is still shown at the job category in her Your Signups list and when a List All Signups is done. It is only after you have *approved* the request that the specific job is shown in these places. (Self-signup schedules always show signups and signup counts just at the job category).

Creating Categories and Specific Jobs

When you do a Create Activity with the Category Request signup style, there is special support for creating its specific jobs. Setting its Location field to a comma-separated list of locations will cause Create Activity to create a location-suffixed activity for each location in the list. Additionally each such specific job will have its Self-Signups property set to Not Allowed, and its Signup Style property set to Immediate. For example:

Note that you can create more involved shift schedules "manually". For instance, you can expose specific schedule items to senior people via conditional activities.

Spot/Signup Counts and Sub-Categories

The number of signups for a Category Request schedule item is the sum of the signup requests and approved signups anywhere within the category. On the other hand, the true # of Spots for such an item is the sum of its specific-item spots. To allow unapproved requests + approved signups to be greater than this, simply set the category item's # of Spots greater than the specific-spots total. (Of course, once the category really is full, you may want to Close Signups or reduce its # of Spots so you don't keep getting requests you need to reject).

You can create sub-category request schedule items in a category (e.g. Election Official, North and Election Official, South). The specific items of a sub-category are those whose Locations start with the sub-category's Location. That is, if a sub-category's location is ABC, its specific items are those whose locations start with ABC. Sub-category counts work like category counts. For example, suppose Election Official, North&South Precinct 1&2 are your four specific items, and each has 2 spots with 1 filled. Also suppose there are 2 pending requests at Election Official, North. Then:

Conditional Activities

Definition and Applicability

You create a conditional activity by setting Self-Signups to Matches Role. A conditional activity will be included on a person's self-signup page only if the person's registration info contains a matching role:

  1. A role of xxx matches any activity whose Base Name is xxx.
  2. A role of the form ^xxx matches any activity whose Base Name starts with xxx.
  3. A role of the form xxx^yyy matches any activity whose Base Name is xxx and whose Location starts with yyy.
  4. A role of the form xxx^yyy$ matches any activity whose Base Name is xxx and whose Location is yyy.

In general, you should consider using conditional activities only if your group manages people in terms of roles in the real world. Otherwise in practice, you will not be able to maintain accurate Roles data inside PRESTO.

A Fancy Example, and a Simplified Version

Suppose you are signing up ushers for a performance series and have 2 kinds of ushers: Ushers and Senior Ushers. Suppose as well that Senior Ushers can signup for both jobs, but Ushers should not signup as Senior Ushers. Thus you want the self-signup page of ushers to not include any Senior Usher schedule items.

To accomplish this, you could:

In this basic case, you could achieve the same effect by setting up Usher as an unconditional activity — since everyone can signup for it. That is, you could:

Judged Contests

A judged contest is one in which an entrant's result is determined by evaluation. (Note that the Judged Contest feature can be applied to situations other than contests. For example, it could be used to tabulate employee-performance evaluations).

Setting Up and Using a Judged Contest

To create1 a judged contest (say an essay-writing contest):

A person, say Tom Jefferson, would enter the contest by clicking on the event's Author Signup link on Self-Signup Home, and then signing up for the Essay Contest activity. Judges would later score Tom Jefferson's entry by clicking on the event's Judge Essay Contest link, and then signing up for the Tom Jefferson, Essay Contest activity4.

Notes:

  1. When you create your own contest, you can choose whatever names you want for the elements you create. And except for the names shown in green, you can edit the names of the elements PRESTO creates for you.
  2. An example of another field might be: Entrant's Age. (You might also want to setup an anonymous entry name, as described in the next section).
  3. The value of a Computed field is the average of the scores that judges entered into their scorecards for that field.
  4. This kind of activity is called a Scorecard. A Scorecard and its schedule item are automatically created when an entrant signs up, and automatically deleted if an entrant withdraws. You cannot directly create or delete them.

Customizing a Contest

By default, the Scorecard activity for scoring a contest entry is named person's name, contest's name (as in Tom Jefferson, Essay Contest). If you want judging to be anonymous, include a required field in Essay Contest Form whose name2 starts with E:. For example, suppose that Tom Jefferson typed "Declaration of Independence" into the E:Essay Title field, then the scorecard for his entry would be named Declaration of Independence, Essay Contest.

When you created the Essay Contest activity, PRESTO automatically created 4 elements for you. These elements influence what judges see. Thus before a contest is judged, you should look over these 4 elements and make any updates needed to fit your situation.

These elements are:

Notes:

  1. If you later want to rename or add Computed fields to Essay Entry Form, you must make the matching changes to Essay Contest Scorecard yourself.
  2. When a contest form is displayed by a non-administrator, the labels for any E: and J: fields will not include these prefix characters.
  3. If you want a judge to score only certain entries, set the *** SCORING RULES *** activity's Self-Signups field to Matches Role and put the entry names of each entry she should judge into the Roles field of her registration form.

Viewing the Results of a Contest

To view an entrant's scores so far, click on the entrant's Essay Contest signup on the Admin-Signup page. You can also create and view contest reports. Note that people with Observer or Agent privilege can also view contest scores and any contest reports you create.

To create a contest report (say Essay Results Summary):

To generate this report:

If you had multiple contests with the same scoring columns and wanted to view results of just one of them, the Current Event scope would not suffice. You would have to: