Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Opening Up Academic Planning Information

A presentation about how SFU is working with Student Services to open up access to student planning information.

  • Be the first to comment

  • Be the first to like this

Opening Up Academic Planning Information

  1. 1. Opening up Academic Planning informationTo promote reusability
  2. 2. • About SFU• Challenges• Public Data Flow – Academic Calendar – Course Outlines• Lessons LearnedOverviewCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 2
  3. 3. • One University - Three campuses – Burnaby – Surrey – Vancouver• 32,000 students• 900 faculty• 1600 staff• 100,000 alumni About SFU
  4. 4. • Information distributed across websites – Out of date – Question validity – Trapped in HTML• Varied web technologies – Difficult to update – Staff turnover leaves gaps – Information depends on technical skills• Consistency Needed for AccreditationChallengesCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 4
  5. 5. Data in Master SourcesData in CMS or otherDistributed on WebsitesPublic Data FlowCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 5
  6. 6. • Current Academic Calendar – 500+ static web pages – All Program Requirements – All Course Descriptions• Hosted Data Source – Curricunet – Auto generates HTML – HTML cut and paste in CMS• Data is not reusableAcademic CalendarCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 6
  7. 7. • Automated Academic Calendar – SOAP calls from Curricunet – Data stored in CMSwww.sfu.ca/program-requirements/2012/fall/engl/major.xml www.sfu.ca/program-requirements/2012/fall/engl/major.xmlwww.sfu.ca/program-requirements/current/current/engl/major.xml www.sfu.ca/program-requirements/current/current/engl/major.xml• CMS Integration – Reusable CMS Components – Exposed via REST – Dynamically updatedAcademic CalendarCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 7
  8. 8. • Current Course Outlines – Mandated by University policy – Represents a contract with the student – Generated by instructors – Wide variation in process • MS Word documents • PDFs • Static departmental websites • Niche departmental applications • Dead treesCourse OutlinesCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 8
  9. 9. • Course Outlines Application – Consistent Schema – Form based input – Draws from Academic Calendar – Draws from SIS – Draws from Room Data – Reusable CMS Components – Accessible REST Interfacewww.sfu.ca/course-outlines/2012/fall/engl/201/d100.xml www.sfu.ca/course-outlines/2012/fall/engl/201/d100.xmlwww.sfu.ca/course-outlines/current/current/engl/201/d100.xml www.sfu.ca/course-outlines/current/current/engl/201/d100.xml Course Outlines CANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 9
  10. 10. • Big Data is no longer Big – Entire Student DB is 250 Gigabytes – Walmart’s DB is 2,500,000 Gigabytes• Friends don’t let Friends scrape screens – If data is published, it should be machine readable• Set it free and it will return – No IT department can match the resources of a million API developersLessons LearnedCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 10
  11. 11. Thank You jeremy_rosenberg@sfu.caThank YouCANHEIT 2012 - SFU IT Services - Jeremy Rosenberg 11

×