1. It is now possible to export a single swimmer’s record to CSV of SDIF.  When a single swimmer is selected, the exported file will contain the information for just that swimmer.  When no swimmers are selected, the entire roster will be exported.  Single swimmer SDIF export is useful for importing late additions into WinSwim which is something I’ve had to do a few times this week.
2. The LSC Registration Pyramid (SDIF) can now be generated using the Age Group Age (computed base on cut off date) instead of the swimmer’s true age.  By default the real age is exported which is what wp-SwimTeam has done traditionally.  If you want to use the computed Age Group Age, change the setting on the SDIF Profile tab from the Options menu.

A new version, v0.2.486, of wp-SwimTeam is available for download from the Download page.

1. Define a job – title, description, duration, etc.
2. Allocate a job to a season or to one or more swim meets.  This action connects a job to a specific season or meet and defines the number of positions required.
3. Assign job ownership.  This can be done by either the administrator or by end users themselves.  End users cannot assign themselves jobs which are already assigned to another user.  An administrator can change the assignment of a job from one person to another.  Job assignment can be performed in couple different ways:
• Full or Partial Season long jobs can be assigned from the Seasons tab.
• Full or Partial Meet long jobs can be assigned from the Swim Meets tab.
• A specific job can be assigned from the Jobs tab.

The Swim Meet Report has been enhanced to include a Job Assignment section and a new short code has been defined to allow a meet specific job report to be added to a page or post easily.  The wp-SwimTeam demo site will be updated shortly to show some of the new features.

While I may not care for Hy-Tek or their products, the fact is they have a dominant market share and a lot of teams use Team Manager, Meet Manager, or both.   I was  contacted this week by a high school coach who was looking for some SDIF assistance in getting his roster into Meet Manager.  Now I don’t have access to Meet Manager but I do have pretty good understanding of the SDIF specification so I was able to help him out with some example SDIF files.

In the process of helping him out I came across an old e-mail regarding importing a roster into Meet Manager.  At the time I was interested in Team Manager so didn’t give it a lot of thought.  Looking at the old e-mail I realized that if it worked, I could export the file format very easily from wp-SwimTeam.  I went ahead an implemented it, now I am looking for someone to try it out.

Sample Reports

The zip file above contains three versions of the same roster – CSV, SDIF (.sd3), and Meet Manager Registration (.re1).  Extract the Meet Manager Registration file from the zip file.  It is an ASCII file that contains swimmers records, one per line with the following fields delimited by semicolons:

1. Registration number
2. Last name
3. First name
4. Middle initial
5. Sex
6. Birthdate
7. Club abbreviation
8. Club name
9. Preferred first name
10. ?? – unknown what this last field is; it’s always “N” in the examples provided

To import the file into Meet Manager, follow these steps:

1. Set up a new meet database.  You only need to go through the first setup screen, the one where you put in the meet name, date, and length of course.  To make my particular file work, select “USA Swimming” for the ID format.  If you have something other than USA Swimming numbers for swimmer labels, select “Other”.  Normally, for a kids’ meet, you’d select “USA Swimming” for the ID format or “Other” if you are not using USA Swimmer numbers for simmer labels.
2. From the main Meet Manager menu, select “FILE”
3. Select “IMPORT”
4. Select “REGISTRATION FILE”
5. Locate and choose the .RE1 file that contains the roster.

After completing these steps, go to the “Athletes” screen in Meet Manager.  The swimmers contained int he RE1 file should bYou should see all of the athletes’ names that you saw in the RE1 file.

If this works for you, please leave a comment!

At this point I am able to define jobs, allocate a job and quantity required against a swim meet and make some refinements of the allocation. I also have the beginning of the assignment to a specific user GUI done but not the backend functionality. I am optimistic that I may finish a first pass this weekend.

The underlying data is fairly easy to manage but how to present the jobs, associate them with a season or swim meet, and then assign people to fill them has been a challenge.  I think the reason I am struggling with this is I am not happy with the terminology I am using.  There are three aspects to the Jobs functionality:

1. Definition of jobs:  Titles, descriptions, duration, etc. 
2. Allocation of jobs:  Jobs are allocated to either a season or a swim meet or multiple meets.  The number of positions for each job will vary.  For example, the number of timers needed is dependent on the number of lanes the host pool  has.  You might need four timers one week and then three the next.
3. Assignment of jobs:  Connecting a name to a particular job.  The Lane 2 timer at meet XYZ will be Betty Jones.  The Announcer at meet ABC will be Tom Burns.

I am ok with the “Definition” of jobs and the “Assignment” of jobs but I don’t like the term “Allocation” but I can’t think of anything better.  If you have a suggestion, drop me a comment!

It turns out that turning DocBook into PDF isn’t as easy as I thought it would be.  I have yet to find a good solution.  I may have to buy the full version of XMLeditor.

I personally prefer “real” documentation and by “real” I mean something you can print and read away from the computer.  I’ve always like the model that used by Version Control with Subversion has used.  The source is in DocBook format which means it can easily be produced as web pages, a PDF file, or an actual book.

Right now I am leaning toward using the DocBook format.  At a minimum I am going to try it and see how it goes.  Stay tuned!

I personally prefer “real” documentation and by “real” I mean something you can print and read away from the computer.  I’ve always like the model that used by Version Control with Subversion has used.  The source is in DocBook format which means it can easily be produced as web pages, a PDF file, or an actual book.

Right now I am leaning toward using the DocBook format.  At a minimum I am going to try it and see how it goes.  Stay tuned!

If you are using an Optional Swimmer Field (OSF) to track something like “Fees Paid” as a “Yes-No” field, you can use the new Global Update to reset them all to the “No” state.  This functionality may be applied to Optional User Fiends (UOU) as well but right now it is limited to only OSF fields.  Additionally, the “Results” field currently is displayed but changing it has no effect.

There are a few other changes that I fixed as I run into things and I also fixed the situation with the Swim Team Profile labels Michael Hale ran into recently.  The issue there was if the label was only numeric it was invalid HTML for the field name.  There is now a check to ensure that whatever text is specified for the label will now be valid for an HTML attribute.

This version also changes how the Status field is determined.  It is now derived based on the Active Season.  There is an issue sorting on the Status field on the All Swimmers tab so it is currently disabled.

You can find v0.1.450 on the Download page.  I strongly recommend backing up your database before installing this version.