Youth Soccer Rankings ?

[sigmabody]

If you name it by grad year, then you'll have parents who think their older kid can play in a younger division. "But he's in 8th grade...." No one working the signup table wants to deal with that ten times every hour.

My guess is we refer to them by the pair of years, same as we did 10 years ago. "14/15" means kids born the second half of 2014 or the first half of 2015.

Yep, agree with this. YY/YY is the least confusing representation, and users will know how to parse this.

I know "red shirted" kids who are a year behind in school from the start, even before rarer (but possible) grade movements. Additionally, the cutoff point doesn't 100% align with school enrollment cutoffs points anyway. School year would be far more confusing.

 

[Carlsbad7]

Yep, agree with this. YY/YY is the least confusing representation, and users will know how to parse this.

I know "red shirted" kids who are a year behind in school from the start, even before rarer (but possible) grade movements. Additionally, the cutoff point doesn't 100% align with school enrollment cutoffs points anyway. School year would be far more confusing.

Totally doable and not confusing...

 

[sigmabody]

Totally pedantic, but short category ordering from least to most confusing, in my entirely subjective opinion:
- YY/YY
- U-[Age]
- "School" year

Spelling out the date ranges explicitly is the least confusing overall, but not really "app column header" or "short team name postfix" compatible. I'd guess most people on this forum could parse/understand any of them, but it might be more challenging for average soccer parents.

 

[Code]

If you name it by grad year, then you'll have parents who think their older kid can play in a younger division. "But he's in 8th grade...." No one working the signup table wants to deal with that ten times every hour.

My guess is we refer to them by the pair of years, same as we did 10 years ago. "14/15" means kids born the second half of 2014 or the first half of 2015.

For the very rare player who was held back or graduated early I think the registration table could handle.

 

[jasportsdad]

If you name it by grad year, then you'll have parents who think their older kid can play in a younger division. "But he's in 8th grade...." No one working the signup table wants to deal with that ten times every hour.

My guess is we refer to them by the pair of years, same as we did 10 years ago. "14/15" means kids born the second half of 2014 or the first half of 2015.

Yep, agree with this. YY/YY is the least confusing representation, and users will know how to parse this.

I know "red shirted" kids who are a year behind in school from the start, even before rarer (but possible) grade movements. Additionally, the cutoff point doesn't 100% align with school enrollment cutoffs points anyway. School year would be far more confusing.

Totally pedantic, but short category ordering from least to most confusing, in my entirely subjective opinion:
- YY/YY
- U-[Age]
- "School" year

Spelling out the date ranges explicitly is the least confusing overall, but not really "app column header" or "short team name postfix" compatible. I'd guess most people on this forum could parse/understand any of them, but it might be more challenging for average soccer parents.

Agreed. Now how do we make YY/YY happen lol

 

[RandomSoccerFan]

As of 8/1, the start of the new season, the new age groups are now properly represented in SR. I imagine it will take a little while to get everything sorted out, as a number of teams seem to have some of their results tied to the older or younger team. Also, quite a number of teams that are now listed with the "12/11" type of naming scheme, aren't attached to their prior season team results. As more and more results come in over time with the new names, everything will work itself out one way or another, whether or not people are joining unlinked results.