I have just uploaded beta-5 of wp-SwimTeam v1.40. This is a minor update, the only fix is to the generation of the USS Number when used as swimmer labels. Previously the USS Number was being computed in YYMMDD format where as the USS Swimming SDIF specification calls it out in MMDDYY format.wp-SwimTeam Beta (1022 downloads)
Tonight I posted an early build of wp-SwimTeam v1.34. You can download it and manually install it if you would like to try it. This build introduces the ability to export Meet Entries in Hy-tek HY3 format which can be imported directly into Team Manager and Meet Manager.
This build also addresses a number of bugs I’ve encountered, the most notable being the inability to generate a single swimmer roster export in SDIF and HY3 formats. Instead of just one swimmer, the entire roster was exported. This has been fixed. The CSV export was not affected by the bug.
Please let me know if you run into any issues. I plan to release this later today after some more testing.
If you run into any problems, please let me know. I’d like to release this update in the next day or so.
After a day of testing on the MacDolphins site without any issues, I have released v1.33.949. There are no changes between this build and the v1.33 beta build except the version number and the removal of the beta tag.
This build fixes a number of problems related to swimmer and user data which surfaced after I changed the database queries I was using in v.1.32.
- Fixed bug which prevented generating roster report.
- Fixed bug which prevented scratching swimmers from Meet tab.
- Added additonal table to Meet Report when operating in Stroke mode which reports number of swimmers Opting In or Opting Out per age group.
- Completed first phase Meet Entries export in Hy-tek HY3 format. Not exposed on the GUI yet.
- Fixed bug which prevented Job Reminder emails from being sent.
Over the last few days I have been working the Hy-tek HY3 equivalent of exporting SDIF meet entries. For the most part the logic is largely the same but the Hy-tek Meet Entries format is different enough that it isn’t a simple port. In particular, relay entries have me a bit stumped.
In SDIF it is possible to assign any number of swimmers to a relay event as an “Alternate” using the “A” designation in the leg field of the F0 record. As near as I can tell, the Hy-tek equivalent doesn’t exist. A relay team can be defined in the HY3 F1 record and the heat and lane assignment can be set in the F2 record. Swimmers are designated in the F3 record. So I am somewhat stumped – do I just define the relay teams and then let the assignment of swimmers to the relay teams happen within either Team Manager or Meet Manager or do I keep track of the number of potential swimmers and create the maximum number of relay teams and simply assign swimmers to each team so they can be sorted out later?
The other dilemma I face has to do with the swimmer id field which is not the same as the registration number field. The swimmer id field is an internal database field which connects D1, E1, and F3 records to the same swimmer. Within my plugin I have unique swimmer ids in the form of database record identifiers that I know will be unique. Should I use them or is simply starting at 1 and sequencing the number of swimmers as using that as an id sufficient?
My guess is the answer to both of these questions will be “it depends” and I’ll need to experiment. Life would be so much easier if Hy-tek would simply support the SDIF format correctly instead of the half assed way they do it now.
This morning I released an update for wp-SwimTeam. This version addresses a few issues and completes the Hy-tek Team Manager Roster Import functionality. You can find it on the Download and Installation page or through the WordPress Dashboard and the Plugin Repository.
- Completed Hy-tek Roster export. All fields that can be mapped into some sort of logical Hy-tek Team Manager field are now supported. TM supports up to three custom fields in the roster import file, if optional swimmer fields are enabled, the first three (or fewer) will be mapped into the corresponding TM custom field.
- Fixed bug where in some instances, the first name would be blank.
- Fixed alignment (right instead of left) of Swimmer Id field on SDIF F0 records in entries export.
- Fixed minor white space issue in PHP source code which in some cases seems to cause the Job Commitment Report to hang.
In the processes of getting ready for our first meet I found some swimmers who had scratched still appeared in the entries SDIF file. Odd, this isn’t supposed to be. Looking into the problem I found that only Freestyle was being processed correctly, all other strokes were not being recognized for Opt-In or Opt-Out.
I have fixed this bug and uploaded a new version as well as pushed it to the WordPress plugin repository.
This afternoon I released an update to wp-SwimTeam. This update, v1.25.865, fixes a number of issues and adds some new features. Key in this build are a number of fixes to allow wp-SwimTeam to work under WordPress Multi-Site.
- Fixed issue with missing users when running under Multi-Site.
- Fixed User Drop Down select lists to work when running under Multi-Site.
- Fixed display of swim meet date in several locations eliminating PHP warning message.
- Updated SDIF profile success message presentation.
- Added support for Swimmer Labels in SDIF Roster export.
- Added support for Swimmer Labels in SDIF Meet Entries export.
- Fixed default sort order on Age Groups so it is predictable.
This afternoon I posted an update to wp-SwimTeam. This release, v1.24.846, addresses a couple of issues.
- In ability to add a new season to a new installation. Made it kind of hard to get started! This bug was introduced when I added action checking and the action checking on the Seasons had a flaw in it.
- Added B1 and B2 records to the SDIF export of Meet Entries. These records are required and I had simply overlooked them. The Meet Entries successfully import into WinSwim, I hope to validate with Team Manager in the next day or two.
WordPress multi-site is not functional at this time. I’ve been alerted to a bug which I am chasing which prevents the Users from being displayed. Access to the user tables is critical and multi-site handles it differently than regular WordPress does so I need to account for it.
I have fixed the bugs I noted over the weekend and also re-implemented the SDIF LSC Registration Pyramid export. The new export validates with the WinSwim SDIF Checker and I have successfully imported the MacDolphins’ 2012 summer roster into WinSwim with it. I fixed a few other bugs I found including one which prevented updating User Profiles.
As always, if you run into any issues, let me know!
This evening I committed v.122 of wp-SwimTeam to the WordPress plugin repository. This update completes the work I started about a month ago to overhaul the Event Model and add the ability to Export Meet entries in SDIF format such that they can be imported directly into any of the Meet Management applications.
I have made a lot of changes while working on this new functionality. If you run into anything unusual, please let me know ASAP so I can fix it.
- Added new Team Profile field to identify Coach by WordPress username.
- Fixed numerous potential issues when either Swimmer or User option count was set to zero. The comparison was not accounting for the difference between zero and non-existant which resulted in using the default value of 5 in many instances.
- Initial support for Meet Entries SDIF export. The current implementation makes some assumptions which will eventually be under user control via a form. The exported SDIF validates with the WinSwim SDIF Checker application but has not been tested extensively with any of the Hy-tek tools nor with WinSwim itself.
- Added checking and error messages for all Actions to ensure something is selected when required.
- Added GUI for Meet Entries Export.