JiscMail Logo
Email discussion lists for the UK Education and Research communities

Help for ADMIN-STUDENT Archives


ADMIN-STUDENT Archives

ADMIN-STUDENT Archives


Admin-Student@JISCMAIL.AC.UK


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

ADMIN-STUDENT Home

ADMIN-STUDENT Home

ADMIN-STUDENT  October 2007

ADMIN-STUDENT October 2007

Options

Subscribe or Unsubscribe

Subscribe or Unsubscribe

Log In

Log In

Get Password

Get Password

Subject:

Re: Students repeating part time on a full time course

From:

Mike Milne-Picken <[log in to unmask]>

Reply-To:

Admin-student <[log in to unmask]>

Date:

Fri, 26 Oct 2007 12:53:57 +0100

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (165 lines)

 
Sorry just reread it - the sentence in para 6 that goes:
"The R stage contains the data that we use in our returns to HEFCE ...
and flags the student as full time" should have read "and flags the
student as PART time".

Ooops - should have read it more closely before posting!

Apols

Mike
-----Original Message-----
From: Mike Milne-Picken
Sent: 26 October 2007 12:46
To: 'Admin-student'
Subject: RE: Students repeating part time on a full time course

I've also been working out how to solve this problem, with a new system
too!

We are now using SITS FE "sister" system, EBS, which has quite a
flexible system of 'course codes'/'module codes' that can be joined
together in various ways (these are called 'Registration Units') and all
components of a curriculum occupy the same data table but use relational
database technology to create complex curriculum structures. The
registration units table contains a field called 'unit type' that
enables us to identify and join various components of courses together,
with infinite flexibility, so modules, stages and courses all sit in the
same table.

This system is designed to work for the much more complex 'multiple
concurrent registration' structures with subcomponents that are required
for FE courses, such as GCE AS/A2 Levels, and Cambridge ESOL
qualifications, that would defeat most HE systems I have worked with! A
side effect of the greater systems flexibility you need for FE, is that
it gives us a system that we can use to record some of the complexity of
our HE programmes too. (this is definitely a case example that FE is in
advance of HE in creating systems for every purpose).

We have set up our HE courses so that each one has a 'Header' code that
sets out the target award and duration, eg BA Business Studies 3 years
full time 0710. This 'course' then has joined to it a set of three
'stages' (for undergraduate courses) each of 120 credits corresponding
to the levels of full time study (Cert/Dip/Deg or levels 4/5/6 on the
new NQF, though we currently call these "Stage 1", "Stage 2" or "Stage
3"), eg "BA Business Studies Stage 1" 0708. Each 'stage' then has the
modules attached to it, eg "Introduction to Accounting", 15 Credits,
Level 1, 0708.

What we are doing with part time repeaters is that we have created a
'part time stage code', with an R postscript in the code that has the
'repeat' modules that the student takes in their repeat year. We join
to this both the modules the student is taking as 'repeat', and the
modules the student passed on previous relevant stages of the course.

So, a student who entered full time BA Business Studies 0609 will have a
header code reflecting that, and would have had joined to it a stage
code for 'level 1' 0607 with 120 credits of modules attached. If they
passed 60 credits of these modules and failed the other 60 credits
(following reassessment), their stage result is 'fail repeat' and they
would have to repeat 60 credits part time.

Here's our solution. What we are doing this year is adding a new stage
code 'R1' 0708 to the student's registration units, joining to it the
modules they will take in 0708 together with the modules they passed in
0607, to make a stage that has 120 credits across 2 years (0607 and
0708). The R stage contains the data that we use in our returns to
HEFCE etc(HEIFES equivalent to HESES, and ILR equivalent to HESA) and
flags the student as full time (their fte is based on the number of 0708
module credits joined to the R stage code ie 0.5 for 60 credits). It
should also allow us to monitor at our exam boards how many 'repeat'
opportunities students have had, as these are limited under our degree
regulations. Assuming the student passes their 60 repeat credits, the
stage result calculates the 120 credits they have now passed as "Pass
Proceed" and the next year the go on to stage 2 0809 full time stage
code. (or "Pass Award" if it is the final stage of an award and
graduation).

That's the theory - there's a lot of detail I've skimmed over, as you
will have gathered if you are following me thus far like most we have
also built in to the system rules tables to assist with exam board
decision-making to track the academic regulations, and a complex
subsystem for handling assessment marks at component and up to module
levels.

In practice, however, it's quite a task setting up the codes and making
sure each student's programme is correct - we are a widening
participation instution with a lot of students who need every
opportunity available to get through and therefore have a fair few
students in this category. It is complicated to explain to both
administrative and academic staff and train them in doing it and we've
only just started checking everything, but we think it will work and
provide for accurate reporting internally and to HEFCE and other bodies,
and programme management. The main issue for us is therefore the
resources required to manage the data in the system, rather than that
the system cannot cope with such flexibility.

Mike Milne-Picken
Bradford College

-----Original Message-----
From: Admin-student [mailto:[log in to unmask]] On Behalf Of
Kennedy, Margaret
Sent: 26 October 2007 11:16
To: [log in to unmask]
Subject: Re: Students repeating part time on a full time course

Hi David

We use SITS too. What we do for students repeating a year of study
part-time on a full-time (or sandwich) course is to keep the student on
the full-time/sandwich course details and change the mode of attendance
on the relevant SCE (this is the enrolment screen for the student for
the academic year for non SITS users) only.

Regards
Margaret Kennedy

**************************************************
Margaret Kennedy
Student Records Administrator
Academic Registry
University of Teesside
Middlesbrough
TS1 3BA

email [log in to unmask]
telephone +44 (0) 1642 384238
Fax +44 (0) 1642 384201



-----Original Message-----
From: Admin-student [mailto:[log in to unmask]] On Behalf Of
David Ealey
Sent: 26 October 2007 10:17
To: [log in to unmask]
Subject: Students repeating part time on a full time course

Dear all

We are looking at how we formally record those students who are deemed
to be part time repeating on a full time course for student funding
purposes. At the moment we do not distinguish these in the mode of
attendance field on our student records system, (we use SITS), but this
causes a variety of complications in different areas.

We have always thought that trying to distinguish in this way was more
trouble than it was worth but I have been asked to see what practice is
elsewhere in the sector.

Happy to collate responses if there is sufficient interest.

Regards

David

Companies Act 2006 : http://www.londonmet.ac.uk/companyinfo


Email from Bradford College is subject to a disclaimer, the full
contents of which are available for viewing at the following link:

http://www.bradfordcollege.ac.uk/emaildisclaimer.htm

Top of Message | Previous Page | Permalink

JiscMail Tools


RSS Feeds and Sharing


Advanced Options


Archives

February 2024
January 2024
December 2023
October 2023
August 2023
July 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
July 2022
June 2022
February 2022
January 2022
August 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
November 2020
October 2020
July 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
November 2017
October 2017
September 2017
June 2017
April 2017
March 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
April 2016
March 2016
February 2016
January 2016
December 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
2006
2005
2004
2003
2002
2001
2000
1999
1998


JiscMail is a Jisc service.

View our service policies at https://www.jiscmail.ac.uk/policyandsecurity/ and Jisc's privacy policy at https://www.jisc.ac.uk/website/privacy-notice

For help and support help@jisc.ac.uk

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager