Part 1: Intranets

Introduction

The presence of the Internet has unquestionably and permanently altered the library environment. It has dramatically altered how libraries interact with one another, how people who manage and use these institutions conduct their business, and how information of all types is managed. The Internet's dominance in electronic communication has arrived in full force and its influence on the operation of libraries has presented the field with an important question: what is next?

Intranets are internal versions of the Internet. They are a form of private, secure electronic networks that function almost exactly as their larger antecedent. Intranets can use the Internet to connect remote libraries within an organization, but they can also be strictly internal and run completely on a Local Area Network (LAN). The objective here is to assist those librarians who find themselves in the position of not only managing the organization of information and its retrieval, but also in the planning, developing and implementing of Intranets in library environments so that information retrieval is effective and efficient. A brief examination of Intranet philosophy and structure will provide a foundation for further discussion on Intranet installation, infrastructure, publishing, and security. There will also be an emphasis on the technical aspects of Intranet architecture and management. I believe that it has become apparent to many librarians that Intranets are an essential tool, not only for its internal users, but also as a means for justifying the profession's existence within any library, especially corporate.

Intranets: What is an Intranet? Zorn describes Intranets as "internal corporate networks set up to take advantage of popular Internet communication protocols such as Transmission Control Protocol/Internet Protocol (TCP/IP) and HyperText Transport Protocol (HTTP), and other Internet tools such as web browsers, web servers, and HyperText Markup Language (HTML)" (Zorn, 1997, 31). Griffith describes the Intranet as

a network that uses Web software to create an "internal Internet" for an organization, regardless of the organization's size or geographic diversity. The technology can make use of an organization's existing network infrastructure (cabling, workstations, etc.) making it in many instances an extremely low-cost information solution (Griffith, 1996, 10).

Another definition of similar note is Harrison's description;

An intranet (is something) which provides a similar range of communication and information services to that on the Internet. An intranet uses the same sort of software tools but operates within a secure and controlled environment (Harrison, 1997, 36).

A final definition expands on the internal aspect of Intranets and blurs the boundary of their functionality.

An Intranet uses Internet protocols--TCP/IP-- and Internet tools on an organization's Local Area Network or Wide Area Network (LAN or WAN). The structure uses Web-style pages of information. users within the organization can post information and can access posted information. Although usually intended for internal use, sometimes the enterprise allows the outside world access to part or all of the Intranet (Flohr, 1997, 69).

How will Intranets influence libraries? Libraries are organizations that conduct business like any other institution. There are administrative functions, acquisitions and purchasing transactions, human resource management issues, public service issues, and the training of staff. The list of possibilities is only limited by those who implement them. An Intranet is a medium for delivering information to all employees within the organization. Internal web sites allow managers the ability to communicate in an effective and timely manner with their employees. With this easy dissemination of information there is a better expression of future goals, strategies, and vision to the staff.

Contents

Table of Contents

Part 1: Intranets Philosophy Structure Part 2: Intranet Installation Basic Network Configuration Server Client Publishing Applications Security Conclusion References