Course Data Project Blackpool and The Fylde College Peter Greenall, Robert Hooper, Scott Smith & Laura Whitaker
Implementation Overview http://www.blackpool.ac.uk
Tribal EBS Course File & Content Ownership
Student Records
XCRI-CAP User Synchronisation
Key Benefits
Workflow
• Complete review of processes relating to the internal collection and publication of course information • Alignment of the programme validation/revalidation process, identifying trigger points where EBS and Drupal should be updated
1
• Improved communication between internal stakeholders resulting in a clearer understanding of course data processes and change implications
Key Challenges
• User synchronisation with Active Directory to ensure all users exist for the allocation of content ownership • Course data import from EBS student records system
2
• User Authenticates • User views owned and editable content • Updates are version controlled in a ‘revision node’ • Editing always linked to the latest version, even if not published
3
• Managing competing external demands (e.g. KIS, HEFCE Audit, QAA Review, Funding/SNC changes)
4
• Managing competing internal demands (e.g. staffing changes, software and hardware upgrades, new website launch) • Underestimation of the scale/scope of course data management • Complexity of interfacing the various business processes involved in course data management Poster template by ResearchPosters.co.za
5
• Content update triggered – content owner notification • Verification at least every 12 months to check web and prospectus information • Major or Minor Amendment • Programme Validation/Re-validation
• Moderator notified of content update • Content is either approved or referred back to the owner • Content owner notification
• Approved content is published on the College website and within the XCRI-CAP feed