<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/">
<channel>
<title>1978: Problems and failures in library automation</title>
<link>http://hdl.handle.net/2142/950</link>
<description>15th Clinic on Library Applications of Data Processing (1978). Edited by F.W. Lancaster.</description>
<items>
<rdf:Seq>
<rdf:li resource="http://hdl.handle.net/2142/1094"/>
<rdf:li resource="http://hdl.handle.net/2142/1093"/>
<rdf:li resource="http://hdl.handle.net/2142/1092"/>
<rdf:li resource="http://hdl.handle.net/2142/1091"/>
<rdf:li resource="http://hdl.handle.net/2142/1090"/>
<rdf:li resource="http://hdl.handle.net/2142/1089"/>
<rdf:li resource="http://hdl.handle.net/2142/1088"/>
<rdf:li resource="http://hdl.handle.net/2142/1087"/>
<rdf:li resource="http://hdl.handle.net/2142/1086"/>
<rdf:li resource="http://hdl.handle.net/2142/953"/>
</rdf:Seq>
</items>
</channel>
<item rdf:about="http://hdl.handle.net/2142/1094">
<title>What hath technology wrought?</title>
<link>http://hdl.handle.net/2142/1094</link>
<description>What hath technology wrought?

Veaner, Allen B.

I believe it was Adlai Stevenson who said: "Man does not live by words&#13;
alone, but he sometimes has to eat them." No one wants to be reminded&#13;
of anything but his successes! So, I sense that in putting together their&#13;
papers for these proceedings, my colleagues have squirmed at least as&#13;
uncomfortably as I. Librarians know that the inventory of failures in&#13;
library automation is long and dismal. However, this is not intended to be&#13;
a series of obituaries; rather, my purpose is to review the period of transition&#13;
from completely manual to nearly fully automated systems, to try to&#13;
see what can be learned from analyzing the failures, and to extract some&#13;
general observations in answer to the question: what hath technology&#13;
wrought?

Libraries --Automation

Library science --Data processing

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1093">
<title>So you want to build a network</title>
<link>http://hdl.handle.net/2142/1093</link>
<description>So you want to build a network

Kunkel, Douglas F.

WARNING: Building a network may be hazardous to your health. Depending&#13;
on network philosophy and guidelines, networking may demand&#13;
unparalleled cooperation and communication among libraries. If&#13;
cooperation within a region is "unnatural," dissension and frustration&#13;
are likely to discourage any efforts to develop a network promoting&#13;
such ideas as resource-sharing and coordinated purchasing. Success&#13;
depends on selecting objectives acceptable to the expected participants.&#13;
When designing a network it must be clearly understood from the&#13;
beginning which capabilities will eventually be provided, so that the&#13;
basic design is compatible with the long-term evolution of the system.&#13;
Many problems stem from differing interpretations of network direction&#13;
and philosophy. Network participants may be shocked or unhappy&#13;
to discover either that their desires run counter to those of the network,&#13;
or that the architecture of the computer system precludes certain&#13;
capabilities. A common understanding from the very beginning&#13;
will alleviate many subsequent confrontations.&#13;
This paper reviews some of the problems associated with selecting&#13;
system characteristics, establishing a governance structure and managing&#13;
the project, financing, and computer technology. Each section is&#13;
headed by questions indicating the type of issues which must be solved.&#13;
Examples are based on experiences with the Washington Library Network&#13;
(WLN).

Libraries --Automation

Library science --Data processing

Networks

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1092">
<title>Problems of government bureaucracy when contracting for turnkey computer systems</title>
<link>http://hdl.handle.net/2142/1092</link>
<description>Problems of government bureaucracy when contracting for turnkey computer systems

Kountz, John C.

There is no single or best approach to portray the idiosyncrasies, real&#13;
and imaginary, involved in contracting in most organizations. However,&#13;
all this is simplified when the scope of discussion is narrowed to state&#13;
bureaucracies, and becomes "duck soup" when the state is identified&#13;
which in this case is California. Furthermore, in the state of California if&#13;
those goods and services relate to data processing, massive amounts of&#13;
unnecessary research are replaced by massive amounts of wasted time&#13;
interspersed with concentrated effort. This will not be a brief statement of&#13;
experience, bracketed by remarks and followed by three questions from&#13;
the floor and a smiling retreat. Instead, the following is a somewhat fictionalized&#13;
account of real events, of things done by real people to each&#13;
other. These people are still plying their trades, and many of these real&#13;
events have yet to become history.

Libraries --Automation

Library science --Data processing

Government bureaucracy

California state government

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1091">
<title>Problems of teaching library automation</title>
<link>http://hdl.handle.net/2142/1091</link>
<description>Problems of teaching library automation

Divilbiss, J.L.

I will not pretend that the sentiments expressed here are anything&#13;
other than personal views arising from my teaching certain courses in the&#13;
Graduate School of Library Science at the University of Illinois. It would&#13;
be presumptuous to declaim on the problems of higher education in general,&#13;
and boring to delineate problems specific to this particular school.&#13;
Between those extremes, however, there are problems likely to be shared&#13;
by other instructors at other schools, problems of some consequence to&#13;
the library field in general. To deal with these problems candidly, I have&#13;
not limited myself to "safe" topics such as the need for more money. If&#13;
some of the "unsafe" topics give offense they should be understood in&#13;
terms of bringing important issues to light.

Libraries --Automation

Library science --Data processing

Library and information science education

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1090">
<title>Problems of library automation in India</title>
<link>http://hdl.handle.net/2142/1090</link>
<description>Problems of library automation in India

Dasgupta, Kalpana

The major activites of the different categories of Indian libraries are&#13;
mainly routine work, such as acquisition, circulation, management,&#13;
processing, reference and bibliographic service, periodical holdings, information&#13;
retrieval, inventory, and so on. The services and techniques&#13;
utilized in the different libraries, however, tend to make these activities&#13;
very cumbersome and slow. The acquisitions of most libraries are done&#13;
independently, and involve unnecessary duplication of work and lengthy&#13;
procedures. Cataloging and classification methods differ from one library&#13;
to another and are generally time-consuming and labor-oriented. This is&#13;
very confusing for the users as they must thus switch from one classification&#13;
and cataloging system to another when using more than one library.&#13;
There is also a lack of bibliographic control at the national level. The&#13;
Indian National Bibliography suffers from a large time lag. Almost all&#13;
library activities involve long hours of manual work, tending to make&#13;
library service very unpopular. Therefore, users still cannot envisage a&#13;
librarian as a giver of information but consider him or her a custodian of&#13;
books. In order to improve the services of libraries, application of newer&#13;
methods, such as information, computer and communication technologies,&#13;
will be needed. I am only concerned here with computer applications&#13;
in libraries and believe that for efficient functioning of our library systems,&#13;
we will need automated services at some point. But serious thought&#13;
must first be given to which areas will be automated, while keeping in&#13;
mind the national need.

Libraries --Automation

Library science --Data processing

Libraries in India

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1089">
<title>The ups, downs, and demise of a library circulation system</title>
<link>http://hdl.handle.net/2142/1089</link>
<description>The ups, downs, and demise of a library circulation system

Corey, James F.

The automated circulation system discussed in this paper was in&#13;
existence in the spring of 1978 when the fifteenth annual Clinic on Library&#13;
Applications of Data Processing was held. The system was not a failure in&#13;
the sense that it never succeeded in becoming an operational system. It did&#13;
become operational and had functioned in the Undergraduate Library at&#13;
the University of Illinois at Urbana-Champaign for two and one-half years&#13;
(from May 1976 to December 1978). The system was stopped because it&#13;
was replaced by a larger computer system that could perform known item&#13;
searching by author, title and author/title, in addition to performing circulation&#13;
functions. The university agreed to replace the Undergraduate Library&#13;
system with the larger system as part of the negotiations for hiring a&#13;
new director of the University Library.

Libraries --Automation

Library science --Data processing

Library circulation

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1088">
<title>Reactions to failures in library automation</title>
<link>http://hdl.handle.net/2142/1088</link>
<description>Reactions to failures in library automation

Brodman, Estelle

I know of at least three other contributing reasons&#13;
which might explain the dearth of reports telling of the demise or required&#13;
reconstruction of library automation systems. These are: (1) the emotion&#13;
of the newly-converted, (2) the attitude of librarians and others dealing&#13;
with libraries concerning funds, and (3) the difficulty many librarians&#13;
seem to have in understanding exactly what is subsumed under the words&#13;
"research and development."

Libraries --Automation

Library science --Data processing

Failure

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1087">
<title>Automation of the catalog: The transition from cards to catalog</title>
<link>http://hdl.handle.net/2142/1087</link>
<description>Automation of the catalog: The transition from cards to catalog

Braithwaite, R.J.

I wondered if my being asked to speak at this conference on "Problems&#13;
and Failures in Library Automation" was perhaps a 2-sided compliment,&#13;
as the University of Toronto Library Automation System&#13;
(UTLAS) is one of the more successful projects in library automation in&#13;
North America. However, in any automation project, no matter how&#13;
successful, there are always some problems which can serve as lessons&#13;
to others.

Libraries --Automation

Library science --Data processing

Library catalog

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/1086">
<title>The anatomy of failure in library applications of computer technology</title>
<link>http://hdl.handle.net/2142/1086</link>
<description>The anatomy of failure in library applications of computer technology

Axford, H. William

Axford, Lavonne Brady

This paper is an analysis of a community college district's attempt to&#13;
introduce computer technology into the operation of its five libraries. In&#13;
spite of the fact that the conversion from the Dewey Decimal Classification&#13;
system to the Library of Congress Classification (LCC) system,&#13;
which initiated the effort, began about nine years ago, the basic causes of&#13;
failure are as relevant today as they were then because they are rooted in&#13;
the minds of those responsible for them: librarians, computer specialists&#13;
and institutional executives. Involved in the project were five libraries&#13;
serving the district's five campuses, a centralized acquisitions and&#13;
processing unit (referred to here as library technical services or LTS)&#13;
responsible for ordering and cataloging materials for the district's five&#13;
libraries, and the district's computer center.

Libraries --Automation

Library science --Data processing

Failure

Community college libraries

</description>
</item>
<item rdf:about="http://hdl.handle.net/2142/953">
<title>Front matter including Foreword and Table of Contents to Problems and failures in library automation: Papers presented at the 1978 Clinic on Library Applications of Data Processing, April 23-26, 1978</title>
<link>http://hdl.handle.net/2142/953</link>
<description>Front matter including Foreword and Table of Contents to Problems and failures in library automation: Papers presented at the 1978 Clinic on Library Applications of Data Processing, April 23-26, 1978

Table of Contents

</description>
</item>
</rdf:RDF>
