We do recommend you watch the short video (under 15 minutes) to get a quick introduction to MUIR. This is an updated version of the presentation that was given by Bryan Tillis at the US Open site.
Feedback on the beta system should be made through these two forms:
It is worth noting that the events and member information in the database that is being used for the beta test is from August 4th, so more recent events or membership changes are not shown on the beta test pages.
When we do the live conversion, we will convert all current memberships and all events up to the cutoff date/time.
Advance notice of the conversion date will be given, so TDs will know that they need to finish the events they’ve got in the current TD/Affiliate Support Area ahead of the cutoff or completely redo them on the MUIR system once the conversion is complete.
What happens to events submitted in this beta system? Are they rated in the beta database only? I just want to make sure before I resubmit some things just to practice.
No data entered into the beta system will become part of the live system, this is strictly a sandbox for exploring and learning the new interfaces as well as helping us find problems and make improvements to the new programming before it goes live.
I’m not sure if it is currently set to run ‘submitted’ events (bypassing the payment step) through the new program for computing ratings. (We have been separately testing the new ratings computation code against the current code.)
I have recommended that once the Leago system goes live that we leave a sandbox system in place for those who just want to test things, including developers who want to create upload files or use an API (when that becomes available) for transferring events from their software into the Leago system. (It would need to make it clear that it is a testing-only environment and that there’s no path from the sandbox system to the live system.)
It’s also picking up a fairly random affiliate (probably the first one in the list by ID). In this case, though, I can search by ID and choose an affiliate and have the whole thing work.
…Ah, I can only choose myself as the chief TD, which wasn’t accurate for the tournament I’m recreating, that’s the issue.
…separately I should be able to use my full name to search rather than only firstname lastname.
I’m noticing some new options too. e.g. Format → Other, Team event toggle…is there a new dbf file mapping for all the changes?
Very nice that we don’t have to re-enter the chief td for no reason any longer. Also, good to do away with the internal name
The floating chess pieces on the main landing page are clutter imo. I’d love it if they were removed
The checkboxes next to the TDs are a confusing UI choice. Checkboxes imply multi-select but in this case, you can only select 1 which is more like a radio button choice
At this point it isn’t pre-populating the list of affiliates that the submitting TD is eligible to direct for, that’s probably coming, but the ability to pull the list of affiliates a TD is authorized by is part of the information we get from Drupal/CIVI-CRM at sign-in, and that wasn’t working until very recently. (I need to ask Leago how they’ll check on updates to the list of authorized TDs for an affiliate.)
Only the chief TD and the submitting TD (if different from the chief TD) need to be authorized to direct events for the submitting affiliate. The other TDs all need to be current TDs, of course, so they need current membership, current TD certification and current SafeSport training.
In this instance, they are; I submitted this particular tournament last Saturday. Nothing relevant changed with the chief TD in the last few days (I did the second refresher, but I would still be in the 30 day grace period), but I can’t pick them as the chief TD to submit that same tournament today in the beta site; I can only pick myself (or possibly the first TD listed for the affiliate, since they are pre-populating).
I’m not sure what the team toggle is for, whether or not an event is a team event (either aggregating individual scores or team-on-team pairing) has no impact on ratings.
There are no plans to create a new DBF format at this time to support additional fields (like the flag for online events, which does affect which rating system is involved) or drop ones that no longer have any meaning.
There will be an API at some point that developers can use to upload events directly rather than going through the 3 DBF files, but I don’t know the timing or the mechanics for its usage.
One of the things the new system enables us to do (some might say forces us to do) is to revisit the integration between the various components of the US Chess environment.
Membership is in CIVI-CRM.
Ratings and Tournaments will be on Leago.
Forums are on DIscourse.
The member dashboard and affiliate information is through Drupal, which is also where the US Chess home page and CLO articles are hosted.
TLAs are (I believe) on the same server as CIVI-CRM, but I don’t know how tightly integrated the TLA system is with the CIVI-CRM system. Will Leago be able to access the list of TLAs using an API so that we can tie rated events to the TLA(s) for them? We need to do that for processing Grand Prix standings, but it would be great if it worked for all events.
Currently, MSA uses a standalone database that has to be refreshed from the live tournament/ratings system, something that happens throughout the day. That will no longer be necessary under Leago. Yay!
We can currently send out emails letting players know when an event they played in has been rated or when they’ve achieved a milestone or norms-based title That will (probably) not be part of the initial rollout of Leago, but should already be on the list of enhancements.
A feature that would be nice would be if publications could create a link in the crosstable of an event (on Leago) to any CLO or CL articles on that event (on the Drupal server) so that someone looking at the crosstable could go read the article.
There has been some discussion with TDAC (formerly TDCC) about changes to the way TD hierarchies and duties are entered and listed, so the current selection protocol may not be the final one.
In practice, I believe both WinTD and SwisSys convert all events to (single) swiss coding. I know in reviewing over 500K sections submitted since 2004, I could only find 3 events that were in true RR format (results but not player info in each column/round) and NO double RR or Double Swiss events.
Double Swiss events created problems because at least one of the programs allowed reporting results by score (0, 1/2, 1, 1 1/2, 2) rather than indicating the result of each game. This messed up things like the milestones for ‘total wins’ because you don’t know if a 1.0 score is WL, LW or DD.
Could Leago be changed to allow entry/display of double-swiss or double-RR events? Possibly, but that’s not part of the current scope of the project.
I’m happy to answer questions here as I have the time and knowledge to do so, but you should also send in reports using the two survey forms so they get into the list of open issues for staff/Leago to look at.
The event I am trying to resubmit was originally related here:
…but it doesn’t seem to be saving in the back end of the beta site; I have no events there in any state. UPDATE: Man, that took forever to load up. 20250923pcyvd3, HAMMOND QUICK SWISS. The director of the single section, Kevin Apper, shows up correctly for the section but not at the tournament level.
I’m happy to answer questions here as I have the time and knowledge to do so, but you should also send in reports using the two survey forms so they get into the list of open issues for staff/Leago to look at.
The description suggested that I should only use each survey form once:
…so I was noting issues to add to the survey later. If there’s a separate individual issue report option, I’d be happy to use that, or if the survey can be taken as many times as desired I can do that too.