Sending Results to a Meet Site

A cross country, track and field, or road race meet can send its results to a meet or registration site that reads Open Meet Exchange, such as QuickMeet. A meet you set up from the site’s link sends results back to it on its own: the site named where results go, and creating the meet approved it. You can add other sites too, and download the whole meet as one file another product can open.

Where results go

Open the meet’s Connections page. Each site that gets the meet’s results has its own row under Results:

• its name, its address, and the Open Meet Exchange version it reads;
• a line saying how the last send went;
• Send results, which says when the site gets the meet;
• Send now, Change token, and Remove.

A meet that came from a site’s link also says so under Registration: Came from QuickMeet · www.quickmeet.run.

When results are sent

Each send carries the whole meet, so the site always has every race as 2Timer has it.

• After each race goes official. 2Timer sends the meet when a race goes official, whether you mark it official or its quiet period runs out, and again whenever you correct a race that is already official. A change to a race that is still unofficial waits for it to go official.
• When the meet is done. 2Timer sends the meet once every race with entries is official, and again after any correction.
• Send now sends the meet straight away, whatever the setting.

The site’s own wish is chosen for you, and you can change it. A site that says nothing gets When the meet is done.

2Timer sends from this browser, so the meet needs to be open on this device. A race that went official while the meet was closed is sent the next time you open it. With no internet, 2Timer waits and sends the newest copy of the meet when it is back.

What the site gets

The site gets the meet: the races, teams, athletes, entries, times, places, splits, and team scores, and whether each race is official.

• Track and field: every round with its heats and lanes, the Q and q after each qualifier’s result and why each athlete is in a later round, wind, each field athlete’s attempts, relays with their runners, a multi-event’s total and each of its events’ points, and each team’s points.
• Road races: gun and net times, waves, splits, and age group places.

It never gets athletes’ email addresses or phone numbers, and it never learns another site’s token. Timing evidence such as reads and stopwatch sessions stays in 2Timer.

When races ran as one combined race, the site gets each race as its own event, with places within that race: the first girl in a race eleven boys led is first.

What the row says

A row may also say quickmeet.run doesn’t work in a browser, so results go to www.quickmeet.run. Nothing for you to do. The site’s address works at its www. form, so 2Timer sends there and results still arrive. Copy details gives the reason, if you want to pass it on to the site.

Adding a site by hand

On the Connections page, choose Add a results destination. The list ends with Or send to a site that reads Open Meet Exchange:

• A destination card: paste the whole card the site gave you.
• Its address and token: the address must start with https://.

The token is kept on this device, with this copy of the meet. It is never in a backup, so a meet restored from a backup as a new meet starts with no sites to send to.

Download the meet as a file

From the meet dashboard, choose Export → Open Meet Exchange (.omx.json). The page says what the file holds and what it leaves out, and Download .omx.json saves it, in Open Meet Exchange 0.9.

The file is not a backup: it leaves out timing evidence, connection settings, and which races ran as one combined race. Keep a backup (.2t) for those; Importing a .2T Backup explains restoring one.