• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
Cambridge e admin
 

Cambridge e admin

on

  • 553 views

 

Statistics

Views

Total Views
553
Views on SlideShare
553
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • I will provide an overview of Teaching Office Database software developed within University of Cambridge Will include: Examples of Departmental Institutional Change Practice of Teaching Allocation and its effect on Curriculum and Teaching Intro Demo Discussion Links to Generic system
  • TODB links teaching staff (people) to teaching jobs. Teaching staff are assigned to particular teaching jobs. Jobs may have different weightings – time, popularity etc History : Engineering Department saw a need Address questions: What jobs are being done by a particular member of staff ? Who is in charge of this task ? SW: On-line Configurable php/MySQL Open source
  • Demo System: Front page Access to different views Help Admin user can create new year
  • Jobs Filtering mechanism Use to allocate people to jobs Special filter - Show unallocated jobs
  • Demo: People Filter by Department/Subject Group Columns configurable Show jobs for person Show timetable Show breakdown
  • Timetable Overall
  • Points Summary report Customised to fit institution Shows totals for each person by Job type
  • Where departments had existing systems tended to be unwieldy spreadsheets with access limited to administrator Now: Teaching Staff and Committee can access and query info on-line.
  • Would have been very controversial to introduce points at start Once people were familiar with system they were happier to see points - can be gradual process as admin only could see at first Discussion Points for number of students taking module, number answering question May decide to abandon points completely COs Something interesting to do Stepping stone to more IT based admin within Dept
  • Customisations Shows participating departments and project status
  • Variation and overlap of specific features
  • More detailed breakdown of who wanted which functionality What has been incorporated into Generic
  • Engineering – detected that disproportionate amount of teaching time assigned to Year 2 Some roll over jobs and people from year to year, Others want to start with ‘clean slate’ - same jobs diff people. Some have courses that change significantly from year to year and need to reassign and rebalance Engineering and JBS share courses and staff TODBs can communicate with each other and give jobs from both depts for a given person Have Jobs and people which could be fed into a fuller timetabling system with venue and timeslots
  • Add link to demo version

Cambridge e admin Cambridge e admin Presentation Transcript

  • Cambridge e-Admin Teaching Office Database (TODB)
  •  
  •  
  •  
  •  
  •  
  •  
  • TODB Administrator Administrator Teaching Staff Teaching Committee
  • Observations
    • Engineering did not use points at first
    • Introduced later
      • Still do not want direct comparison of totals
    • Transparency can help process
    • Using points
      • Can start a discussion
      • Can be used in different ways
    • Computer Officers happy
  •  
  •  
  •  
  • How does TODB support Curriculum and Teaching ?
    • Highlight areas with high level of teaching
    • Can carry over previous years allocations
      • Conversely may need to reassign
    • Shared courses between departments
    • Linkage to full timetabling
  • Summary
    • Allocating teaching load is a complex and political task
      • Using points is one way to address this
    • Everyone does things in their own way
      • Unless overall institutional method
    • Can allow comparison of how much time is spent v. how much time should be spent
  • What Next ?
    • Tie into other systems
      • e.g. Timetabling
    • Generic TODB
      • Open Source
      • Demo version http://todb-demo.caret.cam.ac.uk/
      • Google Code http://code.google.com/p/todb/