1. Building StudentNET portal is my day job Josef Lapka Corporate Information Services Canterbury Christ Church University

3. By 2007, five in-house built online services in StudentNET.

4. During 2008 CCCU’s major focus on student services and resources.

6. sense of belonging from early on.

7. transparency of data and processes.

8. gateway to external online applications including Facebook, Mail Clients (Google/Hotmail)

9. advertised concept (the vision) over 10 months to various stakeholders

10. students

11. academics

12. support departments

13. management

15. potential choices included Sharepoint (MOSS) and complete in-house development

16. built on DropThings technology. Open Source on CodePlex BUT not production ready.

17. contracted an external company [BallardChalmers] to prove that this framework could work in a production environment.

18. in-house development used to integrate proof of concept into CCCU’s production environment.

19. built with C#.NET 3.5, LINQ, jQuery library, CSS 2.0+

20. actively supported in Internet Explorer 7+, Firefox 3+, Safari, Chrome.

22. user can have one or multiple pages (currently limited to one)Each page contains ...

24. currently fixed to 4 columns.Each column contains ...

26. there are three types of zones in our framework.

27. App area zone

28. Side area zone

29. Regular widget zoneEach zone can contain ...

32. fixed widgets

33. loose widgets

34. app widgets

35. WebNote widget

36. widgets are .NET user controls (ascx).

38. fixed widget.

39. personalised messages

40. able to send message to student’s homepage

41. or send a message to a specific group of students

42. send mechanisms

43. admin interface for staff

45. widget to service mappings.

47. current integration includes

48. call management

49. data warehouse

50. knowledge base

51. content management system

52. file storage

53. RSS data (simple)

54. investigating future integration of

55. timetabling

56. BlackBoard

57. Facebook

58. external mail clients

59. CampusM