1 Portals – an institutional imperative Paisleys portal production process Tony Shaw, Anne Strachan Network and Information Systems Management University.

1Portals – an institutional imperative

Paisley’s portal production process

Tony Shaw, Anne Strachan

Network and Information Systems Management

University of Paisley

2Portals – an institutional imperative

History/plan

1996

1998

2000

2001

2002

2002(

sept)

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/briefedperiod of deployment and limited development

replaces existing intranet site

3Portals – an institutional imperative

Staff intranet

4Portals – an institutional imperative

Preparatory activities

Tracking commercial sector products, prices and projects

Anticipating some possible problemshype surrounding VLE/MLE

faculty developments

significant organisational changes taking place

5Portals – an institutional imperative

Lessons from elsewhere

focus on business benefits importance of executive sponsorship invest in planning invest in education/awareness focus on process not technology take care with integration and expectations

6Portals – an institutional imperative

The portal strategy

separate services for staff and students common technology for above remote access as part of model gateway concept not ambitious integration sub projects to drive initial content and

ownership

7Portals – an institutional imperative

Some tactics employed

involvement of VCconfirms strategic nature of project, gets into plans

content contributor clarity continued partner with others

e.g. faculty web site connector

broaden ‘ownership’e.g. manager channel

restrict involvement

8Portals – an institutional imperative

objectives

portal as framework for information architecture

emphasis as strategic project for the institution

provide flexible approach able to accommodate other developments

9Portals – an institutional imperative

some technical issues

ensuring a consistent technical framework anticipating integration requirements design relates to organisational structure incorporating information strategy and

planning issues

10Portals – an institutional imperative

some people issues

anticipating risks/reasons for failure establishing appropriate management and

project structures complexity of overall project how to raise awareness in context of

business

11Portals – an institutional imperative

practical aims

emphasis on business benefits from outset making appropriate and cost effective use of

what exists/will exist caution and pragmatism on integration

12Portals – an institutional imperative

practical steps

ensuring ‘group’ membership reflects business requirements

early communication of portal strategy rapid production of prototype to aid process reference to other sources/experience careful initial involvement at various levels VC involvement

13Portals – an institutional imperative

initial focus

you as a member of the University community (Corporate Comms)

you as an employee of the University (HR) access to key information services/resources

you as a member of a faculty/dept/etc

14Portals – an institutional imperative

Portal

15Portals – an institutional imperative

initial components and channels

basics - sign-on, email, University calendar, phone directory, bookmarks

University news and information

employee news and information

information resources

faculty/local management communication

user defined bookmarks

research funding news

16Portals – an institutional imperative

gateway to resources

17Portals – an institutional imperative

faculty site integration

18Portals – an institutional imperative

“ownership” for managers