This project is read-only.

Code Camp Room Planner Documentation


Using CCRPlanner

Each box represents a room, each row a day. The first number after the room name is the number of blocks available in that for room that day. The last number is the number of conflicts in that room.

In the list of sessions, the first number is the number of votes the session received, followed by the number of conflicts, and last the number of blocks the session lasts.

The buttons below each room let you move a session earlier or later in the day, view the sessions causing the conflicts, and add or remove sessions from the room.

At the bottom right is the display of total conflicts, buttons to save and load the plan, and a button to export a simplified XML document that can be loaded into Excel or other spreadsheet application for formatting and sharing.


  • Block The length of the average session, i.e. if sessions are 70 minutes long, 1 would mean a 70 minute session and 2 would mean a 140 minute session
  • Vote Prior to using CCRPlanner, attendees should be surveyed as to which sessions they would ideally like to attend (more on this below)
  • Conflict Each conflict represents an instance where an attendee cannot attend a session because a session the attendee also wanted to attend is planned at the same time. Lower conflict values are better.

Getting Vote Data

In short, you're on your own to collect the raw data. Once you have it, the data need to be in the following XML format (see the file ExampleSessionStats.xml for an example):

<?xml version="1.0" encoding="utf-8"?>
    <Title>Session Title Here</Title>
    <Speaker>Speaker Name</Speaker>

{code:xml}<AttendeeID />{code:xml} should be unique for each attendee, occur a max of once per session but can appear in multiple sessions (for example, the CodeStock 2009 survey allowed attendees to select a max of 8 sessions).

Last edited Jun 7, 2009 at 4:33 AM by neelm, version 6


No comments yet.