2017 RunSignUp Symposium Presentation Videos

We’ve been busy editing and collating the videos from this year’s RunSignUp Symposium…and while the collection is not yet complete, we wanted to share the ones that are ready!

You can find links for all completed presentation videos here: http://resources.runsignup.com/2017symposiumpresentations/

Links for individual presentations are below.

Customer/Industry Presentations

Supercharging your Sponsor Program, with Peter Abraham

Driving Registrations with Referrals and Social Media Marketing, with Erik Young

Using your Database to Enhance the Experience for Runners and Race Directors, with Healthy Kids Running Series

Motivating and Engaging Fundraisers, with Kathy Wise

Delivering a Race that is Flexible and Enjoyable for Runners, with Cherie Santiago

RunSignUp Tutorials & Presentations

RunSignUp Intro and Overview, with Bob Bickel

Quick Hits for Advanced Users, with Bryan Jenkins

Stay tuned for more videos!

Welcome Darren Wamboldt

Darren.jpgWe are happy to welcome Darren Wamboldt to the RunSignUp Team! Darren joins Jeff Kiesel and Meredith Klein as part of our User Experience Manifesto.

Darren has led the RaceIT User Experience effort for the past 5 years. Coupling his deep passion for UI design, his coding abilities and his industry knowledge will help make our offerings even better for our customers. He will be focused initially on creating additional templates for our Race Websites, along with bringing some other goodies to race websites.

Darren lives in Richmond with his wife and two boys, who might be a bit more into lacrosse than running (lacrossesignup.com anyone?)…  Darren will be working in our Richmond, VA office.

RD Scoring – Eating Our Own Alpha Dog Food

(Yes, the double entendre is intentional)

We used RD Scoring last night in a No Frills Prediction Race – and it worked!

Screen Shot 2017-08-09 at 5.48.20 PM.png

We scored it manually – entering in the participants by hand, and then entering in bib numbers and watch times. This is currently functional, but will improve quite a bit by the time we get to Beta.

The setup process is complicated right now since we only have the scoring “engine” built. This will become simpler as we get closer to a Beta with more wizards and preset options.

Below we will go thru the steps to set up and score this race.

Define Race
Currently, you have to create a race in RunSignUp and then Sync with RunSignUp. You will be able to define races in RD Scoring by the Beta.

There is a Sync Settings in RD Scoring that allows you to define fields. When syncing with RunSignUp, fields like Custom Questions will appear. For the prediction race, we asked a customer question of “Predicted Time” – that is what you will see in the last column below under the RDGo label. By the Beta this will have a lot of fields available including things like Giveaway, USAT membership, etc.

Screen Shot 2017-08-09 at 5.48.28 PM.png

Here, you can define RDGo Fields. In this case, we created a field called “predicted_time”. This will be used in our calculation of the Net Time Difference.

Scored Event
You have to set up which scored events you are working on. For this race, there was only one event.

Screen Shot 2017-08-09 at 5.48.42 PM.png

Age Groups
We set up age groups. There is now a quick start, and then this dynamic editor:

Screen Shot 2017-08-09 at 5.48.50 PM.png

Computed Fields

We set up 3 Computed Fields:

  • predicted_time_offset_ms – this was the subtraction of their predicted time from the clock time in milliseconds.Screen Shot 2017-08-09 at 5.49.00 PM.png

Note there are a number of Operations that can be done – in this case we did subtraction:Screen Shot 2017-08-09 at 5.49.07 PM.png

Note also that by the beta these UI’s will be cleaned up and there will be preset race formats that will hide all of these details.

  • Predicted_time_offset – This did a simple transformation from milliseconds into a standard time format:

Screen Shot 2017-08-09 at 5.49.19 PM.png

  • abs_predicted_time_offset_ms – This created an absolute value of the predicted_time_offset field. In other words it made negative numbers positive for placement – for example an estimate that was 5 second slower than a person ran would be -5, and the absolute value of that would be 5 seconds.

Screen Shot 2017-08-09 at 5.49.26 PM.png

Participants
I added all participant information manually into RD Scoring since it was a no frills race with paper entry. I just entered name, age, gender, bib and predicted time. Remember we set up the Predicted Time field in the Sync Settings where you can define fields (not the computed fields).

Screen Shot 2017-08-09 at 5.49.34 PM.png

Timing Devices and Locations
Now to enter times!

RD Scoring comes with default timing Start and Finish devices and locations. For this race we could leave Timing Devices alone, and then we did our manual entry of Scored Reads from a watch and paper tape:

Screen Shot 2017-08-09 at 5.49.44 PM.png

Clicking on the Scored Reads for the Finish, we entered the Clock Time option (rather than the timestamps option, which subtracts gun and chip times from start time).

Screen Shot 2017-08-09 at 5.49.51 PM.png

These can be incrementally saved, and they show in a list that allows you to edit and delete:

Screen Shot 2017-08-09 at 5.50.02 PM.png

Scoring
Scoring is done with Listings. RD Scoring has a powerful concept called Template Listings, which is defined in JSON (see end of this blog for the code). Templates read definitions like fields, computed fields, and age groups, and create scoring templates. For example, Overall, Male 20-29, Female 50-59, etc.

Screen Shot 2017-08-09 at 5.50.11 PM.png

Right now these have to be hand made. By the Beta we will have tools to create them, as well as default ones setup for certain types of races

Clicking on a Listing once times have been posted gives you the raw results:

Screen Shot 2017-08-09 at 5.50.23 PM.png

Reports
The reporting tool has a fair amount of power now, but is very raw – there will be a lot of change in this before the beta.

Creating a Report has a couple of parts to it. First, naming the report and selecting the base listing data for the report. In this case, it is for Overall Female, and it is taken from the Listing seen above. Note there is a start and end position, which allows the report to include say the top 3 finishers:

Screen Shot 2017-08-09 at 5.50.32 PM.png

You then add columns. In the example below you:

  • Set the Column header name
  • Column alignment
  • Single Field or Multi-field – Note the first one is single, and the second, Name is multi-field – concatenating the First and Last Names.
  • The field is selected from a drop-down of fields, computed fields or scored results like Placement.
  • Transformations for different formats like bold, commas, changing milliseconds to seconds, etc.

Screen Shot 2017-08-09 at 5.50.40 PM.png

Adding Columns can be done manually, or there are “quick add” buttons at the bottom of the page.

Screen Shot 2017-08-09 at 5.50.50 PM.png

Once you have added a report, you can add more. Each report can today be viewed in RD Scoring, output HTML, CSV or Text. Uploading to RunSignUp Results will be available by the Beta. This is the view:

Screen Shot 2017-08-09 at 5.51.01 PM

Final Notes

One of the coolest things about RD Scoring is that everything is real-time. If you make a change to a participant name, every report and scored listing is updated instantly.

While there is a lot of work to do on the ease of use, the core engine is working well.

 

Locked-In Pricing for Cap Priced Events

With our Participant Count price increases always has the downside of people being upset they did not get the price they wanted. The default way it works is the first X people who click Submit on the Checkout page to process their transaction. The problem with this is that we redirect the participant back to that checkout page to tell them they need to re-enter their credit card (for PCI security reasons) at the new price level.

We have added an option (on Miscellaneous Settings) to set a window for people to complete the checkout page before the price expires. This means that more than your limit would get the special pricing – so be careful on this.

Screen Shot 2017-08-09 at 2.42.10 PM.png