Print

---

Thanks to everyone who has sent me comments on Intranets and Extranets.  It
seems that there is much interest in this subject.  The main area of
interest expressed in the replies has been in authentication - although
clearly there are many other interesting aspects.

I'm now intending to run a session on Intranets and Extranets at the web
management workshop.  I've like to hear from anyone who would be willing to
give a brief case study, or lead a discussion on anything relevent.

The subject of Intranets (for use in academic libraries) has ben discussed
recently on the lis-link Mailbase list.  Here is a summary of the
discussion.

Brian

> Thank you to all those who responded to my appeal for information on
> academic library intranets.  It is clearly an area in which many of us are
> feeling our way at the moment.  Here is my summary...
>
> CONTENT
> Common examples of intranet material reported were minutes of meetings,
> staff training information, rotas, diaries, directories of staff,
> university information and bulletin boards.  Several respondents mentioned
> the difficulty of ensuring that material posted on the intranet is kept up
> to date and that it may be necessary to assign the responsibility for this
> to named individuals within each section of the library.  In other cases
> though, this did not appear to present a problem and one or two people
> were able to oversee the entire (albeit perhaps relatively small)
> intranet.
>
> STRUCTURE
> A clear directory structure planned beforehand was considered important.
> In the case of a small intranet it is possible to make all material
> accessible from the top page via drop-down menus.  However, as the
> intranet grows this approach may no longer be workable.
>
> LOCATION & SECURITY
> Most respondents had opted to locate the intranet on their main university
> server.  This seems to present fewer difficulties from a technical point
> of view and means that the security measures on the university server can
> be utilised.  On the other hand, if the intranet is not linked to the
> university's web pages then the university web search engine cannot be
> used.  One respondent suggested that locating the intranet on the
> university server had also hindered the development of certain interactive
> features.
>
> Most respondents reported the use of username/password protection to
> restrict access.  The use of IP addresses is another option though this
> has implications for staff wishing to gain access from home.
>
> ENCOURAGING USE
> The key to a healthy intranet is widespread use which in turn depends upon
> simple procedures for submitting material.  It seemed all too easy for the
> intranet to be perceived as a management tool or the plaything of a few
> library 'techies'.  Those libraries reporting good levels of usage tended
> to be those where some formal training of staff had taken place, for
> example as regards converting files to html format and creating links.
>
> To encourage use, plenty of 'what's new' type material as opposed to
> purely archival material was considered important.
>
> GENERAL COMMENTS
> In many cases it was reported that the intranet had succeeded in reducing
> the amount of paperwork being circulated although there frequently existed
> a residual demand for information in print form from those without access
> to a PC.  Another potential benefit resulting from an intranet was that it
> encouraged standardisation in routine administration e.g. the use of
> templates for minutes to meetings.
>






%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%