Year of Entry or Year group naming for OU

[Shadow_Walker]

Juts inherited a school and some of the year group OUs are setup using year of entry and some are set up by actual year group. I need to go one way or the other so how would you say to do it. In my previous two schools one was set up YOE and the other was by year group.

[Rob_D]

We use year of entry and have OU follows the students up the school.

I guess the question is: Do you have any year specific GPO settings?

If yes, then it might be better to go with year group OUs and just remember to move the students up each summer.

If no (or if you're using user groups to filter settings), then I'd say, save yourself the hassle of having to move the accounts or rename the OUs each year and use year of entry based names.

 

However you do it, you really want to be consistent.

[Andy2789]

I go YOE, then you aren't moving things around all the time. We just have a table on our board in the office that each year we move the numbers along one next to the year groups so we know. Then you aren't messing about with moving students, as sometimes students are held back a year and things start to get messy!

[ass17]

We have a senior and junior school so we use year of entry into year 7. So for example our current year 6 is prefixed 17, so that when they become year 7 in September the YOE will match up 17 = 2017.

 

Here is our full list:

Reception = 24

Year 1 = 23

Year 2 = 22

Year 3 = 21

Year 4 = 20

Year 5 = 19

Year 6 = 18

Year 7 = 17

Year 8 = 16

Year 9 = 15

Year 10 = 14

Year 11 = 13

Year 12 = 12

Year 13 = 11

[Bedders]

We had a group for each Intake Year (Intake 2017, Intake 2016...) and a folder structure for work areas that matched. It meant no faffing around moving students around, and if changes were made such as disk quotas etc. then it was a batch job on an intake, as that was easier than moving students.

[markwilfan]

Yoe every time! We get salamander to create year specific sec groups too

[6Foot2]

We have OUs named as Year Of Entry (this Year will be 2017) and student usernames follow the format YOESurnameFirstInitial, so Paul Jones in Year 7 this year will be 17JonesP. Duplicate usernames are eliminated by using the next initial, or the next letter of the forename.

[Edu-IT]

Definately YOE. Makes life easier.

[forkies]

We have year groups rather than yoe. Same for the documents folders so staff that have access to them can find it easily. No too much of an issue here as we wrote it into the scripts when we moved away from our LA accounts which did the same.

[sparkeh]

YoE for sure, reasons above.

[gaz350b]

Always been year of entry..... we took on a local primary that does it by year group, I laughed so hard at their year end process for each year group!

[mullet_man]

Yoe every time! We get salamander to create year specific sec groups too

 

Same here.

[aidenbran2000]

We use Year group and just change them during the summer holiday. Am i missing something as we never seem to run into any problems

[markwilfan]

We use Year group and just change them during the summer holiday. Am i missing something as we never seem to run into any problems

Just makes work for the sake of it imo

[chrisakak9]

I have mine setup in year of entry then my GPOs are linked to outer Key stage and year group OUs. then i can just move them up at the end of the year.

 

Sent from my SM-A510F using EduGeek mobile app

[Davit2005]

We used to OU this on age basis, what intake year would of being if student started in year 7. So if student started at our school at year 9 they would still be in the OU with the other students of the same age.

[6Foot2]

We used to OU this on age basis, what intake year would of being if student started in year 7. So if student started at our school at year 9 they would still be in the OU with the other students of the same age.

Same here.

[Arcolite]

Year of Entry here, kind of.

 

We tend to us the theoretical Year of Entry for Year 1, a cohort more than anything - so any Year 1 students joining this year will be in the 2017 OU, but Year 7 joiners will be in the 2011 OU (which is when they would have joined Year 1).

Student Documents are stored in the same structure too.

 

Our 2017 Years look like...

 

Year 1 = 2017

Year 2 = 2016

Year 3 = 2015

Year 4 = 2014

Year 5 = 2013

Year 6 = 2012

Year 7 = 2011

Year 8 = 2010

Year 9 = 2009

Year 10 = 2008

Year 11 = 2007

Year 12 = 2006

Year 13 = 2005

 

I only ever have to archive off one OU and one Folder on the File Shares (not including early leavers).

Edited July 31, 2017 by Arcolite

[PotNoodleTech]

Year of entry every time. Your group and folder structure should not need to chance once it has been created. Doing it by year group is a bit insane as it means the goalposts are constantly shifting every year!

[6Foot2]

Year of entry every time. Your group and folder structure should not need to chance once it has been created. Doing it by year group is a bit insane as it means the goalposts are constantly shifting every year!

Yeah, just don't chance it.

 

[jthompson]

Year of entry (as a cohort) here too. When I inherited it, that was how it was but it was all a bit ambiguous as my predecessors had decided to name the OUs Year09 (2009 intake), Year10 (2010 intake) which got confusing fast in an upper school (years 9 to 13). I changed them to Intake2009, Intake2010, etc. to clarify things.

 

I've always found it strange that nobody else in the school ever distinguishes between 'year group' and 'cohort', they all just use 'year group' interchangeably.