Event

8/12/2009: New upcfield module is now on drupal.org. This module will be used in the first sign-in driver module for this project: http://drupal.org/project/upcfield

7/6/2009 8:07PM CST: The draft documentation is up at: #512078: Drafts of documentation and design with pseudo code.

About

This module is being developed and maintained by DANEnet (http://danenet.org/), a non-profit located in Madison, WI. It provides a simple and powerful way for organizations to track attendees of events/activities using on-site kiosks and a central server running Drupal. The server can either be restricted to a local network or be open to the internet to allow off-site sign-ins.

The concept is simple. In our use-case, the system provides each non-admin user a 12-digit UPC barcode printed on ID cards. They can then use the sign-in form to scan this ID card and then select an activity they are attending. Their barcode is associated with a node and is recorded, along with the activity node and a timestamp, after successfully completing the sign-in form. Admin users can then sign-in to the system using the normal Drupal user form and generate reports of attendees which can be broken down by time and activity.

This module allows users to submit incident reports from a Drupal site. It was designed with the emergency services / public safety workforces in mind, although it can easily be modified to accommodate whichever industry might be in need of such a content type.

This is for Ubercart. If you are using Ubercart to sell tickets or entries to an event or perhaps a race, it's very helpful to have a list, per item, of who bought what. For a competition, this will become an entry list. For a performance, this may become your will-call attendance list.

You may simply want to know who bought what! Who are the purchasers of a given item can be useful in any of a number of instances... recalls, promotions, and the like.

This module collects and displays relevant information about purchases, including purchaser name, quantity, payment status, and all attributes.

Finally, the result may be downloaded as a csv so you can do whatever you want with it.

Version 2.5 introduces url-level functionality. Add '?pid=xxx' to the url and (assuming you have permissions) you will see who bought that.

UC_Signup provides integration between Signup.module and Ubercart, allowing users to purchase signups for events.

Signup-enabled nodes are configured as Ubercart products.

The customer can purchase signups for herself and/or other people.

Example use cases:

- 1 User signs up for 1 or more events
- 1 User signs up 2 people for the same event
- 1 User signs up 4 people for 3 different events

If those people do not have accounts on the site, the customer is prompted to create a new account for that person, entering any core user profile fields that are enabled on the site. If there are matching user accounts for the email addresses entered, then UC_Signup does not ask for their profile information.

See it in action in the UC_Signup screencast.

When the order is submitted, temporary signups are created to ensure that the customer is only charged if space is available in the event(s). Once checkout is complete, if the order balance is not cleared, the signups are cancelled. If the balance is cleared, the signups are converted from temporary to final signups. UC_Signup stores this distinction in the uc_signup_log database table.

Webcam trigger is a trigger:) It gives you a page showing your webcam. If the cam recognizes a pattern (which is currently the Druplicon logo) it fires the trigger. You can assign any actions to it. It ships with a built in action that logges in with a given account and redirect to a custom page.

Installation

• Enable modules on admin/build/modules/list page
• Create action(s) for the trigger:
  • "Login with a user"
  • "Redirect to URL"
• Assign action to the trigger on the admin/build/trigger/webcam_trigger page
• Create a menu item pointing to webcam page with the url of: webcam_trigger
• Don't forget about the permissions: webcam trigger access
• That's it. Print out the webcam_trigger.pdf file (states in the module's directory), load the url: YOURSITE/webcam_trigger and concentrate:)

Customizing

[Actionscript source in cvs!]

Custom page

Edit the webcam_trigger_page.tpl.php

Custom pattern

If you are interested in this technology there are some blog posts:
Mikko Haapoja: http://www.mikkoh.com/blog/?p=182
Lee Brimelow: http://gotoandlearn.com/play?id=105
The main AIR application that makes patterns:

This module is a simple todo with sub-task.