Skip to main content

8.1.0.0 (2015.04.28)

RunScore Team

This version is a merge of RunScore Results, Version 8.0.0.3 and RunScore Version 7.5.5.7 to create RunScore Version 8.1.0.0. What does this mean? It means that from now on, whenever you use RunScore to interact with the RunSignUp site, you will be using the RunScore Results. Also, uploading and downloading registrations at both RunSignUp and ChronoTrack Live have gotten easier. We eliminated “Sync with server” and replaced it with a very easy way to download changes from the system and upload changes made in RunScore to the system. The RSRServer and RSRClient (RunScore Results server and client) have been retired. The new modules have the same name as the old ones. If you think you may want to go back to Version 7.5.5.7, save it. Or you can do a complete download using RunScoreSetup.exe to revert to 7.5.5.7. View the short video on the main RunScore page: www.runscore.com which highlights features of this new integration. Also on the main page is a document showing how to allow each runner to see themselves crossing the finish line on a YouTube video.

  • You no longer need to have a field “registration_id” in your database. The registration_id information is kept in a separate file (race.ini) in the race folder.
  • Also in the race.ini file are time stamps for each record that has been changed. This is used for upload of changed records.
  • “Sync with server” has been removed due to problems. In its place you can do an “Incremental download” to get changed online records. Likewise, you can upload new and changed RunScore records with one click. This works for both ChronoTrack Live and RunSignUp.
  • You can take advantage of these features without making changes to your normal RunScore setup.
  • Results are extremely easy to post. You merely right click on a listing button and instead of sending to a printer or the editor, you send it online. Handles overall results, award listing, and team results. With one more click you can view the results online.
  • Set up for e-mail and text notifications. Once set, a runner or his friends can go to the RunSignUp site and ask for e-mail and/or text messages for selected runners.
  • Provide links for each finisher to the specific person in a YouTube video showing that person finishing. This is all done from RunScore.
  • You can download from RunSignUp to get the participants or, if you have another way to obtain participants you can put them in RunScore and with one click upload them to RunSignUp.
  • Not using the RunSignUp site for registrations for this race? You can still take advantage of the above features. There is a nominal cost for posting results. There is also a cost for text messages. If you ARE using RunSignUp for registrations, these services are free.
  • At request of Troy Rebert, added External/Custom Report capability to Team Relay.
  • At request of Fred Dunn and Les Morelles, made Division Place and Division Total headers in a “RunScore Results” of “ChronoTrack Live External” posting more meaningful. For example, for sex place and sex total they would now read “Sex place” and “Sex Total”.
  • The headers of reports are always produced in proper case (e.g. “Name” instead of “NAME”). Sid Steinweg asked for a way to control the the capitalization of headers. This can be done with the new command: “Header case (tab) None”. The default is “Head case (tab) proper”. “Upper” and “Lower” are not supported but could be if the need arose.
  • The “RunScore Open Interface” for external bib/tag systems, has been extended so RunScore knows if the data being set is chip data or bib data. You use “RSBI” for a bib-tag and “RSCI” for a chip-tag. These improvements came about from working with Thorsten Voegel, Race Result, Germany.
  • Fixed a bug that kept the registration_ids from getting uploaded to RunSignUp or RunScore Results.
  • Changed the simulate feature so you will no longer get the “Unregistered Runner Number” in the results produced by simulate.
  • Doug Cleavenger reported that Importing a CSV file that had CR/LFs within a field caused a problem. This problem had been fixed some time ago for internal imports such as downloads from a registration system. It is now fixed for imports from File/Import.
  • The logos on the main page of RSServer and RSClient have been changed to reflect the fact that RunScore Results is part of the module. They now read, respectively:
  • RunScore RunScore Results/RSServer Results/RSClient
  • When uploading a large custom/external result set, the upload is now done in pieces of 1000 results per piece.
  • New command “Output Format” allows you to create the output in any of the following formats: Text (default), XML, JSON, or HTML.
  • The new entries.ini command “Modified Field” now works from RSClient. It previously only worked from RSServer.
  • If you change a RunSignUp entrant to a different event online, a new registration_id is assigned. On the next incremental download, RunScore will notice that it is a new registration_id. It will then look for the bib number. If the bib number in the new record also exists in the RunScore database, the new record will replace the old but preserve fields that are not in the download.
  • “Sync with server” function has been removed because it has not been robust. It is replaced with the, already existing, “Incremental download” in conjunction with the new “Upload modified registrations”.
  • New command: “Team Total” can be used in an Event to Database to send the team total for each individual’s team to a field. It can also be used in an overall listing to produce, next to the “Team place” column a “Team Score” column which shows the team score for each individual’s team.
  • Improvements have been made to the criteria which determine if a field has changed. This is useful when uploading changed registrations.
  • Can now handle USAT (USA Triathlon) and USATF (USA Track and Field) membership numbers when downloaded from RunSignUp.
  • Doug Liversidge pointed out that the “Divide” and “Divide By” commands did not work for time fields. Fixed.
  • Preliminary support has been added for the DirectAthletics TFRRS-XC site. This will be final once more testing is done. The support allows timers to upload collegiate cross-country results to the DirectAthletics site.