3About Us~25,000 students (FTE: ~20,000)~2,500 full time staff.~5000 student/staff PCsPrimarily a Microsoft site, at least studentfacing.Large Linux infrastructure on the businessside.
4Data Exchange System (DES)Project started in 1999 as a tool to manage thecreation of users accounts.Went on to automate, in real time, post-user-creation tasks, previously run as nightly batchjobs.This helped to control workflow: a user musthave an account before a mailbox, and morerecently, an email address before a Blackboardaccount.
5What Does It Solve?Meanwhile, the number of systems within theUniversity was growing, and these systems allneeded information about the users.Keeping these systems up-to-date was rapidlyturning into an unmanageable spider web ofpoint-to-point links, all running jobs at differenttimes.This resulted in data discrepancies betweensystems for, occasionally, up to a month.Centralise synchronisation using DES.
6What Is It Made Of?Microsoft Active Directory acts as the centralhub for DES. We have extended to cope withor needs and use it a full directory service.DES collects these changes, hourly.Source systems must detect changes howeverthey can, and DES is written to understand.Processes and distributes them as necessary.For the distribution we use Microsoft MessageQueuing and XML (at least it does now).
8ExtensibilityThe systems are loosely coupled.Data contracts are drawn up by the integrationteam and the target system’s custodians.An integration piece is written, whichprocesses the data sent from DES andinteracts as needs be with the target system.DES is updated so that it knows that this newsystem exists, and what it needs to knowabout.
9Blackboard: What We MaintainUsers Account details (41,000); Enrolments (current/past and their states); Certain roles (used to manage access rights for tabsand building blocks);Courses “Master modules” (14,000) “Offering modules” per year / term (71,000)Programme Community Sites (125)Updated hourly
10Blackboard: How We CommunicateThrough various versions of Blackboard wehave had to revise how we interact with it:Batch files and the batch file loader;Using the Blackboard .NET API;Current: almost exclusively using theBlackboard web services API.Though we’ve also written one of our own webservices (using the Blackboard Java API), andstill make the occasional database call.
11Additional Benefits Within BlackboardQueuing the messages means that new datais always received in order (FIFO).Processing stops on serious errors and thequeue is left building up until the issue isresolved.This has proved invaluable during upgrades.Keep multiple instances up-to-date:development, upgrade testing by adding onemore queue pointing at that new instance.
12Programme Community SitesGist: Allow a space to create a sense ofcommunity shared between all levels of aprogramme.No notion of programme within our Blackboardsetup.Programme vs. Plan (Campus Solutions).Consult with programme leaders to mergeprogrammes/plans into communities.
13Programme Community Sites (cont.)Modify DES to allow programmecreates/modifies/deletes to be collected.Modify the integration piece to understand.Create them programmatically, with defaultcontent (and modify / delete).Programme information was already in theDES message, to organise course enrolmentsin the XML, but was never used.Started using it…
14The programme level community sites
16Factors identified as most likely to allow the successful transition and retention of astudent into this new learning culture are:Proactive management of student transitionEarly access to information and avoidance of information overloadDeveloping understanding of expectations of university studyA focus on integration and developing a sense of belonging (eg buildingstaff-student / student-student relationships)A supportive climate that focuses on goal-setting and developmentalfeedback in the early stages, but then sustains the focus on developmentand personal growthBetter integration of support services.Curricular structures that increase the likelihood of early academicsuccessStructured opportunities (eg groupwork) to help socialisation and developcritical peer support networksBeing alert and responsive to changing patterns of students’ engagementin higher education
23Yes No Can’tremember58% 33% 11%Did you login to Blackboard before arriving?The Programme Handbook gave mea good overview of my course0%5%10%15%20%25%30%35%40%45%50%
240%5%10%15%20%25%30%35%40%45%I had a good understanding of whatto expect during my induction andfirst few weeks at LJMUThe induction timetable providedclear details on where my inductionsessions would be taking place.0%5%10%15%20%25%30%35%40%45%
250%10%20%30%40%50%60%70%80%2/10/201202468101214Some sites having a higherpercentage of percentage ofcohort logging on and frequencyof times accessed (a staticallysignificant correlation).
27ArchitectureStudent N = 307Students visited = 61%Student logins = 6 per student