I
I
I
UNION DIANNE
ELLSWORTH
collection
management
resources
LISTS & A U T O M A T I O N IIF
I
I
The PHILSOM Automated Serials Control System: An Introduction Stephen Van Houten PHILSOM is an automated serials control system, developed at the Washington University School of Medicine Library in St. Louis, which provides automated support for the full range of serials control activity within the libraries participating in the PHILSOM networks. The PHILSOM III system, run at WUSML with a distributed processing node at Himmelfarb Library, George Washington University in Washington, DC, is both a batch and online system containing the bibliographic data for approximately 15,000 titles and the local data for 16 biomedical libraries. The PHILSOM East system, run at the Medical Library Center o f New York, contains the bibliographic data for approximately 10,000 titles and the local data for 12 biomedical libraries. PHILSOM East uses an earlier version, PHILSOM II, which runs only as a batch system. One nonmedical library in Wisconsin also uses the PHILSOM II system. The PHILSOM system attempts to predict the issues which will be received by the various participating libraries and to provide them with records describing each of these issues. The records for checked-in issues automatically update the holdings data, and interact with previously coded data to produce claims and binding notifications. The PHILSOM system also produces additional outputs to aid in serials control. PHILSOM was originally developed and implemented at the Washington University School of Medicine Library in 1962 and 1963. It has since undergone several major modifications which have increased the complexity of the individual record and which have made use of the developing computer and telecommunications technology. The earliest version o f the system was designed to be used only in a single library. It ran on both an IBM 1401 and an 7072 computer. The file was updated quarterly. The major products of the system consisted of a list of serials holdings by title, as well as a list of titles arranged by subject. Each list was updated and produced semiannually. Prepunched IBM cards representing expected issues were used both for automated check-in and claims notification. Additional products included a monthly cumulated list of received items, a daily lists of receipts, and bindery notification. 1 Automated check-in was possible, at first, only for the most recent issues. A later modification allowed for the automatic check-in of past issues. 2 In 1968 other libraries expressed interest in participating in an automated serials control network to be run by WUSML. The PHILSOM system was revised to allow for this capability. The unit record was divided into two parts. One was a bibliographic file (basic data) to be shared by all participating libraries, and the other was for location data that would be specific to each library's holdings. Additional data fields and outputs Stephen Van Houten is PHILSOM Librarian at The Medical Library Center of New York. That institution now operates its serials activities through the PHILSOM II system.
provided enhanced fiscal and binding control, subscription renewal capability, and a redesigned claims notification feature. In 1970 two libraries joined the system, and three more soon followed.3 The Medical Library Center of New York replicated this system, PHILSOM I, and brought additional libraries into the PHILSOM East network in 1973 and 1974. At the same time, the PHILSOM programming was completely revised at Washington University to provide more efficient processing b y the computer. The resulting system, PHILSOM II, programmed in ANSI standard COBOL and run on IBM 360 equipment, was implemented in 1974 and replicated by MLCNY in January 1975. 4 At this point, the emerging mini-computer and telecommunications technology offered the possibility of overcoming some of the limitations of the operation of the PHILSOM system. A monthly batch update for all libraries allowed each library to share economically the cost of automated processing. The operation of such a system, however, created a monthly bottleneck for the processing center and the participating libraries, especially as the system grew in size. The design of a new system, which would provide a cost-effective and more flexible automated serials control system, was undertaken at Washington University School of Medicine Library. 5 PHILSOM III Batch and Online
The resulting PHILSOM III system is a hybrid batch/online system. Within the batch system, which runs on IBM 360 equipment, a participating library's serials records are updated monthly in a single computer run. The computer processes the records of issues in the previous month and other data pertinent to the library's local records, updates the library's location data file, and produces several outputs. The PHILSOM I1! data record (shown in figure 1) consists of two linked components, a basic bibliographic record and the individual library's location data. The basic data include fields for a full title and for bibliographic history notes. Various codes deo scribe the frequency of the journal and anticipate the current issues for which receipt cards are produced. Subject, language, and "indexed-in" codes, beginning and ending dates, and ISSN are also included in the basic data. The bibliographic authority for PHILSOM III is the Union Catalog of Medical Periodicals, compiled at the Medical Library Center of New York. Each participating library contributes location data which include holdings data, last issue received fields, date of receipt, and local notes. Location data also include binding and fiscal data. A list of PHILSOM III basic and location data fields is shown in table 3. Following the monthly update, each library participating in the batch system receives several outputs. Some
SERIALS REVIEW
JULY/SEPTEMBER 1981
93
OOS~Pooo3
&C=TJ),_.P~H_ZS~LSCANS_ 1940IS,~-N,/~OSZO-1-~-6~72.~-. ACTA P H Y S I O L O G I O A S O A N D I N A V I C A SUPERSEDES $ K A N D I N A V I S D H E S A R D ~ I V FUER P H Y S I O L O G I E IN 1940. v: OO±Q~00~G3 P; O~.JJ_V~_OO4_.P-/-LL-J30 ~ S ' O O ~ _ S Z L T _ ~ S ; 1 FP.EO_¢A_A~C.LLD1 FREQUENCY J A FE MR AP MY JN J L AO $ P OC NV CC * T P B ~ 1NO ~ : x ~ S U 3 J E C T S * * ~ * ~**LAtIGUAGE**** **~**INOEXED IN*~*~ *CAT BY* .......... 01 01 O1 01 01 01 01 01 01 O] 01 01 0 0 658 270 320 350 1 4 9 5 10 UCMP LOCSET~ADT RT V O L U H / I S S U E / P T DATE I L SDD ~ S U B J E C T S * ~ x ~ BC BNDR RUB NUMBER* CLOTH LNS T R M S t Z L E T COL FAD STR BOY ADS TP I PR1 FR2 .-95 1 ~ 4__& 10~I'Q9 1178 A O ] &O 0860g 1 - / 1 OS £ • 4 1041-00 117~ S 0 t 00 0660S 7 - / 1
05 4 * $ SOURCE ~7 $ 87 $
OPR]CE O.OO O.O0
$ $
O-O0
O' L
AMT P A I D HAJ. O,OO 0 . 0 0 - -
INV,
OlD PMTS 0 O
ENCUMBERED $ O,o0 $ 0.00
EXP DATE CLS 120074 01 120074 O]
$ $
AMT-YR1 G3.00 63.00
$ $
- I AMT-YR2 O,OO
COMMENT
o-7o0
(1940-1978)/I-90191Nl-OI92-98/99N1,O-4/lOO-lO3/lOzlN1/ SHELVED W I T H CURRENT JOURNALS SET NO 0 2
ON D I S P L A Y .
(1953-1976)I28-33135"gO/91N1"G/g2"lO3/104N1/ SET NO
04
(1968-1975)/72-95/ MICROFILM EDITION. SHELVED I N THE O F F I C E
OF THE M E D I A L I B R A R I A N .
FIGURE 1. PHILSOM III Record as Displayed on the Location Work Printout (Batch Mode).
Source: PHILSOM Newsletter No. 291 (15 December 1978).
. . . . . . . . . . . . . . . . . . BASIC DATA ALPR~ NL~ER:73480003 S H O R T : P E D I A T R R E S YI:1967 ISSE:0031-3998 FULLI:PEDIATRIC RESEARCH BIB 1:SUPERSEDES A ~ A L E S PAEDIATRICI IN 1967. STATUS:I V : I 3 I:i0 IV:f2 FREQ CLASS:I SUBI:623 L~Xl:270 L A N 2 : 3 2 0 L ~ 3 : 3 5 0 INDI:I lh~D2:4 I N D 3 : 3 IND4:5 lh~5:lO TPB:0 CAT BY:UCI-~ FREQ: J A N = I FEB=I ~ R = I APR=I ~%Y=I JUN=I JUL=I AuG=I SEP=I OCT=I N O V = I D E C = I L O C A L DATA L A S T U P D A T E D BY G I S E L A ON M O N D A Y I-OCT-79 8:29 AM. A C T : 4 V O L U M : I 3 I S S U E : I O DATE:I079 RT:S IL: S BC:2 CLOTH:380 L E T : 2 SOURCE:07 EAR~ D A T E : f 2 3 1 7 9 H O L D 1 : 1 1967 1 9 7 9 / I - 1 2 / 1 3 N I - I 0 / CO.WJ~I:ALL H O L D I N G S S H ~ V E D IN GENERAL STACKS. NOTEI:V.2 B A C K F I L E
FIGURE 2. PHILSOM III Record as Displayed by the Online System.
Source: User's Manual for PHILSOM III On-line System (Preliminary text), by Patricia Kane, Serials Librarian (St. Louis, MO, Washington University School of Medicine Library, 1979), p. 35. 94
SERIALS
REVIEW
JULY/SEPTEMBER
1981
TABLE 1 List of PHILSOM III Batch Outputs
Location Work Copy - a list of the full data record in PHILSOM of every title and set for a participating library, in alphabetical order.
ranged by source, showing every subscription needing renewal as of the previous month, the current month, and the following month.
2. Location Desk Copy - a list of the serials information for the library patron, in alphabetical order by title. Three versions of this list are available: one listing all titles held by a participating library, one listing only the titles it actively collects, and one listing titles not actively collected.
11. Current Titles by Source - a list arranged by source of all titles actively collected by a participating library.
3.
13. Binding Control - forms notifying a library that particular issues may be ready for binding, and which include pertinent information for the binder. A binding form is generated when the PHILSOM program, in processing the receipt cards for a particular title, determines that a physical volume is ready for binding. These forms may be designed according to specifications provided by the participating library.
Receipt Cards - punched cards which represent expected issues in a participating library.
4. Master Title List - a list of the status frequency, and current publishing information of each title in the PHILSOM file. 5. Union Work Copy - a work copy which includes all basic data and location in the PHILSOM file. Produced on microfiche. 6. Claims by Source List - a list of issues skipped in the check-in process, arranged by the source (vendor, publisher, gift, etc.). 7. Inactive Warning Report - a list of titles, arranged by source, which have exceeded their stated periodicity without a current issue being checked in. 8.
Update Diagnostics - a list of warnings and messages, in alpha number order, generated by location data submitted to the monthly update and which: was not processed because of irregularities of either the data themselves or of data on the master file; or was processed although the PHILSOM program noted a condition requiring attention. An additional list is produced of input data that do not pass through a preliminary data editing program. (See no. 17.)
9. Monthly Fiscal Report - a list arranged by source of the total fiscal actions since the previous monthly update.
12. Current Titles by Alpha Number a list in alphabetical order of all titles actively collected by a participating library.
14. Current Titles by Subject a list, arranged by subject, of titles actively collected by a participating library. The participant may accept subject codes assigned by the network headquarters, or may supplement or replace these codes. 15. Location Language List - a list arranged by language code of titles actively collected by a participating library. 16. Internal Location List - a list of titles held by a participating library arranged by the shelving location within the library. Multiple sets of the same title may each have a different location code. 17. Location Data Detail List - a list of all location data sub-mitted by a participating library for the current monthly update. Data are flagged which fail to meet certain edit ° ing specifications and which are consequently eliminated from the update.
a list of titles ar-
Source: PHILSOM IlL" Documentation Manual and Guide to the System (St. Louis, MO, Washington University School of Medicine Library, 1976).
of these are produced each month while others are produced as requested. A list of the batch mode outputs is shown in Table 1. A participating library may list the data for several sets of the same title. Both PHILSOM networks include locations which list data for several libraries, including local hospital libraries. For example, one location in the PHILSOM East network represents the East Tennessee Medical Library Consortium. 6 The PHILSOM III online record (shown in figure 2) consists of linked basic and location data files. The online system is programmed in the MUMPS language and runs on a PDP 11 minicomputer. It allows the participating library to perform several serials control functions at the computer terminal. A list of the functions is shown in table 2. Besides providing the immediacy of updating the file through individual transactions at the computer terminal, the online system allows the par-. ticipating library to use certain management functions. Mere-
bers of the library's serials staff may each be assigned various functions by the location manager. The management functions also allow the location manager to monitor time spent on the several online functions. A printed record of operations per formed at the terminal may be produced. The paper backup function also allows the network headquarters to monitor the work of new participants to assist in the training of the serJa!s staff. The online libraries may also have some lists produced in the batch mode. The PHILSOM system shows a consistent development over nearly 20 years of the application of automated processes to serials control. Originally designed to support the serials operation of a single library, it now provides automated serials control to approximately 30 biomedical libraries in two networks. During this period of growth, the PHILSOM staff at Washington University School of Medicine Library has give~ considerable attention to the design and development of a flexible and cost-effective serials control system. Althougi~
10.
Subscription Renewals by Source -
SERIALS REVIEW
JULY/SEPTEMBER 1981
95
TABLE 2 PHILSOM III Online Functions BL
Basic List Data
To retrieve a basic data record by alpha number, ISSN, or search key.
LB
Local Binding Slips
To print and delete the stored binding information. Appropriate forms must be mounted at the printer.
LC
Local Check-in
To update holdings statements and location counters. To generate and store claims and binding information.
LD
Local Daily List
To retrieve data about checked-in issues for printing. To delete these data, either in part or in full, when necessary.
LF
Local Fix Data
To add, change, or delete the value of a field of the location data. Separate fines of a multi-fine field may be updated separately.
LG
Local Find Gaps in Holdings Strings
To print a list of issues missing from all the volumes or only the latest volumes of the holdings statements of every title (active or dead) in the particular location's data base in either alpha order or source order.
LK
Local Claims
To print and delete the stored claims list.
LL
Local List Data
To list the basic and location data of a title in the particular location's data base.
LM
Local Modify Data
To change every occurrence of a specified value of any field in the location data to another specified value.
LP
Local Produce Subject/ Language/Internal Location List
To add, change, or delete basic and location subject codes, language codes, and internal location codes and their translations. To print titles held by a particular location by subject, language, or internal location.
E
Edit List
P
Produce List
LS
Local Search
To search on a field or combination of fields of the basic and location data and have the alpha number of those titles whose data meet the specifications set in the search string print.
LU
Local Utilities
To add titles and sets to the particular location's data base. To delete titles, sets, and general data of a title of the particular location's data base. To provide a paper copy of the location data of those alpha numbers that received activity in a specified time range.
AS
Add Set to an Existing Alpha
To add a new title (as set 1) or add an additional set to an already existing title in the particular location's data base.
ML
Modify List
To add or delete fields from the list of location data fields listed in Function Local Utilities, Sub-function AS.
DJ
Delete All Location Data for an Alpha Number
To delete all the location data (all location data for all sets) of a title.
DS
Delete One Set for an Alpha Number
To delete the location of a set of a title.
DG
Delete General Data from an Alpha Number
To delete the fields (field abbreviations and values) VOLUM, ISSUE, DATE, RT, and all fields relating to binding information. (In changing from active set to inactive.)
PB
Paper Backup
To produce the "paper backup" list: a list of all data changes over a specified period of time.
LW
Late Issue Warning
To print tile Late Issue Warning Report for a set whose next expected volume/issue has not been checked in in a defined period of time.
ME
Message Function
To send messages to users at other location or PHILSOM Headquarters.
MG
Manager Functions
To provide a statistical sheet showing system use, to add and delete users from the PHILSOM system, and to provide a list of the basic, location, and accounting variables.
L
List Logon/Logoff
To produce the Logon/Logoff list, showing system activity.
E
Edit Allowed User List
To add a user as an authorized operator of the system. To delete a user from the list of authorized users. To change the functions and/or passwords assigned to a user.
D
Delete Logon/Logoff List
To delete the Logon/Logoff fist.
V
Variable List
To produce the Variable List, which shows a list o f basic data, local data, and accounting data variables and their specifications.
ON
List Users On System
To show the number of users on the computer at the moment and to list, by user code, the users of all locations logged on to the PHILSOM system.
XL
List Local Data For
To provide a union list of all the libraries in the PHILSOM III online system, for a particular title.
Sources: User's Manual for PHILSOM III On-line System (Preliminary text ); Update I to the User"sManual for PHILSOM Ill On-line System (Preliminary text), by Patricia Gunn, Serials Librarian (St. Louis, MO, Washington University School o f Medicine Library, 1980); Update H to the User's Manual for PHILSOM llI On-line System (Preliminary text), by Patricia Gunn, Serials Librarian (St. Louis, MO, Washington University School o f Medicine Library, 1980); Update III to the User's Manual for PHILSOM III On-line System (Preliminary text), by Patricia Gunn, Serials Librarian (St. Louis, MO, Washington University School o f Medicine Library, 1980).
96
SERIALS REVIEW
JULY/SEPTEMBER 1981
many of the original design features still obtain, the PHILSOM system has been altered radically during this period of development to provide expanded automated serials control and also to make use of rapidly emerging technologies.
pHILSOM in Constant Development The original PHILSOM consisted of a master file updated periodically by means of check-in records on IBM cards which provided several outputs for various serials control functions. As the system developed the number of fields increased to allow for fuller specification of the serials record. A comparison of the fields in the successive PHILSOM systems is shown in table 3. In the PHILSOM II system, the bibliographic data were conceptually separated from the local data to allow for the networking capability as well as for the listing of several sets of data for a particular library. Fields were added to automate the claims and routing functions and to provide inactive warnings. The fiscal and binding data were expanded to provide fuller automation of these two serials functions. The PHILSOM III system shows a continuation of this trend. Several descriptive fields were added to the basic data. The frequency fields were expanded to provide a more completely automated receipt card production. The addition of a current part field allows for three levels of subdivision of the received issues. The binding data and fiscal data were expanded even further. In the PHILSOM III system, the basic data are both conceptually and physically separated from the location data. This greatly enhances the flexibility of the PHILSOM III system since it allows for the updating of the file in various modes and at different times. The basic data are updated online and the location data files of the various participants are updated individually. This allows each participant to choose the batch or online systems to maintain its own serials data, or to establish a distributed processing node. One such node has been established for two Washington, DC libraries. This flexibility is also based upon the use of various types of computer technology. The batch mode runs on IBM 360 equipment, and the online system on a PDP 11 minicomputer, with telecommunications connections.7 The possibility of using a microcomputer to support the online system within an individual library has been investigated.8 The automation of any library function should be more than merely the mechanization of a manual function. Drucker lists "the four principles of automation": First, the entire process is seen as a system. There is, so to speak, no beginning and no end. Everything is integrated. Second, the system is based on the assumption that phenomena of the natural universe fall into discernible patterns and can be routinized on the basis of a probability distribution. Third, the system controls itself through feedback. Finally, the human worker does not work. He programs. He makes decisions based on judgment within the range of patterns the system is designed to handle. 9 The design of an effective automated system should be based upon the definition of desired results, and not the operations previously used to achieve these results. Indeed, the previous operation should need to be restructured based upon the desired results and the technology used to support these results. Library work often includes the maintenance of large files and the performance of repetitive operations, a factor which makes much of this work amenable to automation. It is this author's opinion that automation has generally been applied to library functions as a means of mechanizing the manual function, and not as a means of redefining the individual
operations to provide effective and systematic processing and control. The benefits accruing from automation, therefore, have been ad hoc benefits, but not necessarily those which had been expected. Comparison of manual versus automated serials control have been made. Paul concludes that manual systems can be efficient, and that Automation of serials processing can produce extra benefits . . . . Provision of the extra services or the benefits to be obtained from creating a total system or joining a network may be valid reasons for automating serials processing. 10 Riddick has compared manual versus automated check-in and concluded, Possibly the most prudent judgment that can be made at this time is that a high quality manual check-in system for the present is cost and time effective within a fairly narrow context. 1 1 To this author, PHILSOM represents a serials control system that provides a view of the wider context in which benefits can be obtained from effective automation of a library function.
The Check-In Record A central feature of the operation of the PHILSOM sys-~ tem is the check-in record. It is produced based upon certain codes in the basic data and location data. When an issue is checked in, the record interacts with the previously coded location data to automatically update holdings data and to produce necessary claims or binding reports. The system can identify the failure to check in the current issue and can automatically provide a notification when the issue is overdue. The serials control personnel provide the initial coding which relates an individual subscription to predefined patterns of publication, performs the check-in operation, and follows up on the PHILSOM reports based on the check-in or other transactions. The variety of lists and online functions of PHILSOM are another important feature. A manual system results in only one master file showing the full information relating to each item. This file must be referred to whenever a single operation is performed: to check in an issue; to record a claim; to record a fiscal transaction; or to determine if a recent issue has been received. The PHILSOM batch system produces separate lists which relate to these various functions. The master file is reproduced monthly as the location work printout. The receipt card is the check-in record. The claims by source list and the inactive warnings report relate to skipped or missing issues, and allow for more efficient check-in and claiming by separating these functions. The monthly fiscal report and the current titles by source list information about fiscal transactions. The location desk list provides the information to answer patron inquiries. The design of these lists facilitates the performance of the individual functions. For example, the claims, inactive warnings, and subscription renewals lists are arranged by source (vendor, publisher, and so on), and contribute to rational organization of the individual operations. The PHILSOM III system extends the feature of lists appropriate to in= dividual functions by allowing the individual library to have lists designed to their own specifications. The online system offers the advantage of accessing and updating the file online. The master file can show up-to-theminute infolanation and can be accessed wherever a terminal may be located. The online functions serve similar purposes as the lists in the batch system. However, the online system allows the individual functions to be performed on a more flexi.ble schedule which may be more appropriate to the individual operations. The networking feature of an automated system allows
SERIALS REVIEW
JULY/SEPTEMBER 1981
97
TABLE 3 Comparison of Fields in PHILSOM, PHILSOM II, and PHILSOM III PHILSOM
PHILSOM II
PHILSOM III
Alpha number
Alpha number
Alpha number
Abbreviated title
Abbreviated title
Abbreviated title
PHILSOM
Title status Frequency
Frequency class
PHILSOM III
(Fiscal data) Source
Beginning and ending dates ISSN Status
PHILSOM II
Source
Source
Price action
+/-Amount paid in current transaction Fund
Frequency
Transaction date Monthly frequency cod es Current volume
Current volume
Current volume
Current issue
Current issue
Current issue
Price
Price paid
Price Amount paid in current fiscal year No. of payments
Current part of issue Amount Issues per volume Issues per volmne
Amount year 1 (previous year)
Parts per issue
Index Medicus code
Issues this volume
Issues this volmne
Index Medicus code
Indexed in code
Amount year 2 (two years previously) Renewal date
Expiration date
Cataloged by code
Subscription type
Fiscal class
Title page availability (MARC)
Invoice number
Invoice number
Index availability (MARC) Language
Language
Language codes (4)
Subject codes (4) Subject codes (5)
Subject codes (4)
Full title
Full title
Full title
History statement Bibliographic history
Bibliographic history
Page no.
of invoice
Line no.
of invoice
Local purchase order number Fiscal accumulation comment (Binding data) Binding code
Cross references Cross references (3) Cross references (4) (coded separately)
Extra sets
encumbered
Issues per volume
Binding code Binder
Location number
Location number
Set code
Set code
Action code
Action code
Circulating code
Routing code
Routing code
Position
Rub number
Internal location
Internal location
Cloth color
Cloth color
Subject code usage
Trim size
Trim size
Local subject codes (4)
Collation
Collation
Last received volume
Letter color
Letter color
Lines (on spine)
Lines (spines lines top/ spine lines bottom)
Last received vol.
Last received issue Last received issue
Title page/index
Title page binding code Index binding code
Last received part Fabric Holdings
Month of receipt
Month of receipt
Holdings
Holdings
Series holdings History
Stripes top/stripes bottom Cover binding
Location statement Location comment Notes (online system only)
Bind advertising code Free field 1 Free field 2
98
SERIALS REVIEW
JULY/SEPTEMBER 1981
the participating libraries to share the cost of development and maintenance of an automated system. The shared cost is, however, still an add-on cost. The automated system should provide additional benefits that justify the add-on cost. One such benefit is that machine readable data are easily copied and communicated. The PHILSOM system has been used to support this union listing capability. More importantly, the PHILSOM system provides a rational and functionally oriented framework that assists an individual library in maintaining its own serials records and in controlling its serials collection. NOTES
Control." In Advances in Librarianship. Volume 2, edited by Melvin J. Voight, p. 103--164. New York, Seminar Press, 1971. 4. Bowden, Virginia M. "The PHILSOM System - One User's Experience." Bulletin o f the Medical Library Association 64, no.2(April 1976):219-223. 5. Brodman, Estelle. "Backing into Network Operations." In Proceedings of the 1973 Clinic on Library Applications of Data Processing: Networking and Other Forms of Cooperation, p. 9--23. Urbana-Champaign, IL, University of Illinois, 1973.
1. Irwin Pizer, Donald R. Franz and Estelle Brodman, "Mechanization of Library Procedures in the Mediumsized Medical Library: I. The Serial Record,"-Bulletin o f the Medical Library Association 51(July 1963):313-338.
6. Brodman, Estelle and Millard Johnson. "Medical Serials Control Systems by Computer - A State of the Art Review." Bulletin o f the Medical Library Association 64, no. l(January 1976):12-19.
2. Evelyn A. Moore and Estelle Brodman, "Communications to the Editor: Record System Changes," Bulletin o f the Medical Library Association 53( 1965):99-101.
7. Falvey, Neil. "The PHILSOM Network: A Programmer/ Analyst's Viewpoint." In Proceedings o f the LARC Institute on Automated Serials Systems, pp. 59--63.
3. Estelle Brodman, "Preface," in PHILSOM III: Documentation Manual and Guide to the System (St. Louis, MO, Washington University School of Medicine Library, 1976).
8.
4. Spencer S. Marsh, "PHILSOM - The Move East." Paper presented at the Medical Library Association annual meeting, Cleveland, OH, Jun 4, 1975. 5. Millard F. Johnson, "A Design for a Mini-computer Based Serials Control Network," Special Libraries 67(August 1976):386-390. 6. Doris Bolef and Janet S. Fisher, "Health Sciences Libraries Consortium in a Rural Setting," Bulletin o f the Medical Library Association 66(April 1978): 185--189. 7. Johnson, "A Design for a Mini-computer Based Serials Control System." 8. Telephone conversation between Millard F. Johnson and author. 9. Peter F. Drucker, Management: Tasks, Responsibilities, Practices (New York, Harper & Row, 1974), p. 227. 10. Huibert Paul, "Serials Processing: Manual Control vs. Automation," Library Resources & Technical Services 21, no. 4(Fall 1977):345--353. 11. John Riddick, "Manual vs. Automated Check-in: A Comparative Study of Two Academic Libraries," Serials Review 6, no. 4(October/December 1980):49--51. BIBLIOGRAPHY
Feagler, Virginia. "The PHILSOM Network: The C o ordinator's Viewpoint." In Proceedings of the LARC Institute on Automated Serials Systems, pp. 51--57.
9. Johnson, Millard F. "A Design for a Mini-computer Based Serials Control Network." Special Libraries 67(August 1976):386-390. 10. Johnson, Millard. "The PHILSOM Network: Maintenance and Design." In Proceedings o f the LARC Institute on Automated Serials Systems, pp. 65-69. 11. Marsh, Spencer S. "PHILSOM - The Move East." Paper presented at the Medical Library Association annual meeting, Cleveland, OH, June 4, 1975. 12. Mayden, Priscilla. "The Problems of Entering a Computerized Serials Network; or the Validity of Murphy's Law." In Proceedings o f the LARC Institute on Automated Serials Systems, edited by H. William Axford, p. 43-49. Tempe, AZ, The LARC Association, 1973. 13. Moore, Evelyn A. and Estelle Brodman. "Communica tions to the Editor: Serial Record System Changes." Bulletin o f the Medical Library Association 53(1965):99101. 14. Pizer, Irwin H., Donald R. Franz and Estelle Brodman. "Mechanization of Library Procedures in the Medium sized Medical Library: I. The Serial Record." Bulletin of the Medical Library Association 51(July 1963):313-33& 15. Schmidt, Dean. "The PHILSOM Network; A User Li° brary Viewpoint." In Proceedings of the LARC Insti~ute on Automated Serials Systems, pp. 71-75.
Beckwith, Helen. "Mechanization of Library Procedures in the Medium-sized Medical Library: IX. Holdings Statements in PHILSOM." Bulletin o f the Medical Library Association 58, no. 2(April 1970): 120--125. 2. Bolef, Doris and Janet S. Fisher. "Health Sciences Library Consortium in a Rural Setting." Bulletin of the Medical Library Association 66(April 1978): 185--189. 3. Bosseau, Don L. "The Computer in Serials Processing and
SERIALS REVIEW
JULY/SEPTEMBER 1981
99