is this a high priority issue?
It is still going on.
I don’t think it’s considered a high priority compared to things that prevent an event from being rated.
Can you point to a specific event, or give us upload files that have fields that are not being included?
Yes, the one I entered this morning:
202511110303
I manually added the section tds. let me know if you want me to send files somewhere
Send them to me and I’ll pass them on to the developers. mnolan@uschess.org
Email sent. Thank you
This information is available in the S_CTD_ID and S_ATD_ID fields of the TSEXPORT.DBF file.
There are three TD fields in the tournament header file and 2 in the section header, so a total of 5 that could be picked up. Events like SuperNationals may have 25 TDs on site.
Leago now has several samples of DBF file sets that include all 5 TD fields to work on.
Some implementations of the DBF files have erroneously treated the H_OTHER_TD field in the header file as a memo field rather than a variable length character field. Unfortunately, those files don’t work on MUIR (and didn’t fully work on TD/A, either) because there’s no way to upload the memo file separately. TD/A just ignored the error and didn’t include any ‘other’ TDs, MUIR is currently throwing an error on those file sets because there’s no memo file. I don’t know if Leago will be able to work around that.
Tracking backwards I found over 500 sets of upload files over the last 2+ years with memo files. They claimed to have been generated by SwissSys, but both the SwissSys folks and I are a bit skeptical of that. Exactly how many affiliates and TDs sent those files is not clear, because except for one file that claimed to come from a different pairing program, over 500 files all had the same TD and one of two different affiliate IDs in the header file. That TD is not currently a certified TD and there’s no record of that TD having directed an event since 2021, so we’re not sure just what’s going on, perhaps someone is using a old ‘borrowed’ copy of SwissSys or they’re building their own DBF files using a copy of a DBF header file from 4 or 5 years ago that just happened to come from SwissSys. The current SwissSys owners are not aware of any version of SwissSys that tried to generate memo files, the recent versions definitely do not.
It has always surprised me how people will go to extreme lengths to avoid buying or upgrading their pairing software. Personally, just having the version that uses the current rules for pairing seems worth the upgrade price.
the H_OTHER_TD field used to be automatically loaded into the Other TD field in MSA
This is on the list of things to fix, but not a very high priority because it doesn’t keep events from being ratable, affect rerates, or the ratings supplement process, all of which are mission-critical tasks.