Conference System Screen Shots

Since I am concerned that the running code may in future be decommissioned, I captured most of the major parts of the interface. As of August 2005, it is still used for the Flash Forward conference registration.

  1. Initial signup: what you see when starting to register.
  2. Incomplete data: a small part of the error handling system.
  3. Adding a badge: adding a person for the conference.
  4. Adding more badges: you can add more than one person to a single invoice.
  5. Payment: paying for the registration. The phone people had more options, including payment via cheque.
  6. Receipt: the receipt you get after completing registration. This particular receipt comes from a test invoice in the database, and so is irregular in many ways; it doesn't have any badges, for example.
  7. Main administration page: the backend interface to the database. Most users were only interested in the search options.
  8. Badge class editor: close to when the conference would run, we would be besieged by requests for VIP or Press or Staff badges; badge classes provided an easy way to keep track of all that.
  9. Events editor: many events we ran (although this example conference is an exception) would have optional workshops that people could opt to sign up for, in addition to the conference proper. This affected pricing among a large number of other things, and this editor was the primary way to edit events.
  10. Locations editor: the road show was handled as a conference going on in many different locations at the same time--while this is underused in this example conference, it was very helpful for the road show.
  11. Badge types editor: the badge type determined how much the badge cost. Here we can see the badge type that people who register through the web interface come in using. Special treatment refers to workshop only badges, and class has to do with which sorts of questions can be asked on the main registration form; neither are used in this example conference.
  12. Pricing matrix: across the left edge are badge types, and the top edge is combinations of events; so you can set different prices depending on how much of the conference they will see.
  13. Automated mailings: in the example conference, this is just the confirmation email sent out to all registrants. Sometimes this also includes last minute notifications of conference details.
  14. Searching: this pokes through all the badges and invoices for the given word. By far Search by everything was the most popular way to search; it looks the query term up in every one of the different subqueries. This could be slow, but we had a fairly small database and so things would go reasonably quickly.
  15. Search results: invoices and badges are both broken out, with the field that matched the search term highlighted. Clicking on the edit link will take you to the main invoice editing page.
  16. Invoice editor: this page shows, among other things, the last three things that happened in the database, the data entered for each badge and invoice, and the invoice status. The example invoice has been voided, as it was for testing.
  17. Transactions log: this shows all transactions that were applied to the example invoice; it also illustrates what I jokingly called the six-fingered man accounting system, after the six accounts.
  18. Anomalous invoices report: this searched through the database for invoices that were odd for one reason or another; overpaid, unpaid, voided and the like.

Graham Hughes
Last modified: Wed, 17 Aug 2005 12:28:45 -0700