We do something very similar in Waterloo.  We modified the league table to
include an 'inactive' leagues tag.  While we need to create new teams and
rosters for each season, it allows us to keep historical data in the
'inactive leagues' section.  The tradeoff of recreating rosters vs holding
historical data was important for us.  Repeat teams often have to 'append'
something to their team name as LeagueRunner requires a unique team name
(never dug enough to determine if that was necessary but will someday -
perhaps then hack to automagically append the season and year to the team
name when it is displayed).  Since we only allow league coordinators /
admins to create teams (another mod), it is fairly easy to manage.

Now the 'autopopulate roster' from another team is an interesting concept.
Will have to look further in to that.

The problem we run in to now is that our LR is so heavily modified (I think
there are some references to 'WODSisms' in the comments for the Drupal login
module) that we can't easily update to the latest versions without a
significant investment of time.  But then again, the current incarnation is
working very well for our needs.

Steve

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Greg Schmidt
Sent: Tuesday, September 08, 2009 2:56 PM
To: 'Development discussion for the Leaguerunner league managementsystem'
Subject: Re: [Leaguerunner] Clear league standings

For a little different perspective, TUC keeps all historical data online (I
made some changes a while back to support this).  Players can see their
entire team history, including rosters, schedule, game results, etc.
Because of this, we require that new teams be created for each new season.
This is tied into the registration system; when someone registers a team,
the team record is automatically created for them.  Also, I made an
enhancement to the "add player to roster" that allows the captain to invite
people in bulk from former rosters, which greatly simplifies their
roster-building process at the beginning of the season.

Greg.

-----Original Message-----
From: [email protected] [mailto:[email protected]] On
Behalf Of Dave O'Neill
Sent: Tuesday, September 08, 2009 2:44 PM
To: Development discussion for the Leaguerunner league management system
Subject: Re: [Leaguerunner] Clear league standings

On Tue, Sep 08, 2009 at 02:25:39PM -0400, Peter McAlpine wrote:
> That is more extensive than I had considered, but would cover some 
> cases I had not thought of. I simply figured that teams would serve as 
> what you named a club - effectively making them a grouping of players. 
> Your suggestion would cover cases where there is the same team but 
> different roster playing on different nights in the same season, and 
> would serve as
a
> better way to archive league standings (preserving team rosters).

For OCUA, it's fairly infrequent that the same team wants to play multiple
nights with a slightly different roster (though we do have a few of those).
The main time we encounter problems with team re-use is at the end of summer
season, when captains are trying to firm up their rosters for the upcoming
fall league, but are still actively playing in summer league.

The other time it's an issue is each spring, during summer league
registration, when coordinators are trying to seed their leagues.  At that
time, it would be useful to be able to compare the previous year's roster to
the current one, and make adjustments if necessary.  For example, a team
that had an average player rating of 6 last year may have a lower average
this year and need to be seeded below their final ranking for the coming
season.

As for archiving, keeping stats within LR would be great.  For years OCUA
has been exporting them as sportsml using the script shipped with
Leageurunner because it's been too much work to even contemplate preserving
results in the database forever.  Perhaps with the club/roster structure it
might be a bit easier.

> I think I'll probably end up just updating the standings generator to 
> take an optional season parameter, and filter out everything else in 
> the set of scores. It looks like I can do this by adjusting the sql 
> select in calculate_standings. I can't really think of a case where 
> I'd have a
league
> that has the scores from other leagues included in the standings.

In case you're curious, the reason it works the way it does is because years
ago, OCUA ran multiple tiers for a given night as separate leagues in
Leaguerunner (so Tier 1 Monday, Tier 2 Monday, etc, were separate).
Then, when a team moved up or down to a different tier mid-season, we needed
the record to follow that team to the new league.  Now with the ladder
system, we don't really need that behaviour very often, but nobody's gotten
around to fixing it.

Cheers,
Dave
_______________________________________________
Leaguerunner mailing list
[email protected]
http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner

_______________________________________________
Leaguerunner mailing list
[email protected]
http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner

_______________________________________________
Leaguerunner mailing list
[email protected]
http://www.dmo.ca/cgi-bin/mailman/listinfo/leaguerunner

Reply via email to