Paisley s portal production process Tony Shaw Anne Strachan

Paisley’s portal production process Tony Shaw, Anne Strachan Network and Information Systems Management University of Paisley Portals – an institutional imperative 1

History/plan 1996 1998 2000 2001 2002 (se pt) emphasis on intranet Staff Intranet Co-ordinator post created Portal strategy document published (continued to be revised/published) Portal purchased/prototyped produced VC directly involved/briefed period of deployment and limited development replaces existing intranet site Portals – an institutional imperative 2

Staff intranet Portals – an institutional imperative 3

Preparatory activities u Tracking commercial sector products, prices and projects u Anticipating some possible problems hype surrounding VLE/MLE faculty developments significant organisational changes taking place Portals – an institutional imperative 4

Lessons from elsewhere u focus on business benefits u importance of executive sponsorship u invest in planning u invest in education/awareness u focus on process not technology u take care with integration and expectations Portals – an institutional imperative 5

The portal strategy u separate services for staff and students u common technology for above u remote access as part of model u gateway concept not ambitious integration u sub projects to drive initial content and ownership Portals – an institutional imperative 6

Some tactics employed u involvement of VC confirms strategic nature of project, gets into plans u content contributor clarity continued u partner with others e. g. faculty web site connector u broaden ‘ownership’ e. g. manager channel u restrict involvement Portals – an institutional imperative 7

objectives u portal as framework for information architecture u emphasis as strategic project for the institution u provide flexible approach able to accommodate other developments Portals – an institutional imperative 8

some technical issues u ensuring a consistent technical framework u anticipating integration requirements u design relates to organisational structure u incorporating information strategy and planning issues Portals – an institutional imperative 9

some people issues u anticipating risks/reasons for failure u establishing appropriate management and project structures u complexity of overall project u how to raise awareness in context of business Portals – an institutional imperative 10

practical aims u emphasis on business benefits from outset u making appropriate and cost effective use of what exists/will exist u caution and pragmatism on integration Portals – an institutional imperative 11

practical steps u ensuring ‘group’ membership reflects business requirements u early communication of portal strategy u rapid production of prototype to aid process u reference to other sources/experience u careful initial involvement at various levels u VC involvement Portals – an institutional imperative 12

initial focus u you as a member of the University community (Corporate Comms) u you as an employee of the University (HR) u access to key information services/resources u you as a member of a faculty/dept/etc Portals – an institutional imperative 13

Portals – an institutional imperative 14

initial components and channels basics - sign-on, email, University calendar, phone directory, bookmarks University news and information employee news and information resources faculty/local management communication user defined bookmarks research funding news Portals – an institutional imperative 15

gateway to resources Portals – an institutional imperative 16

faculty site integration Portals – an institutional imperative 17

“ownership” for managers Portals – an institutional imperative 18