FCLMID@NERVM.BITNET (Michele I. Dalehite 904-392-9020) (02/03/90)
At FCLA, we have moved collections based in the call number several times. Before we had libraries using Circulation, the process was fairly simple: examine the call number, if it met the criteria, change the loc/subloc in the copy statement. Of course, it is important that your location tables be changed if the new loc/subloc is actually new to the system. After libraries came up on circulation, we learned the hard way of the problems with changing locations. If item records are attached to the copy, both the loc/subloc code and the location number in the item record have to be changed in sync or else ABENDS occur whenever the record is displayed (again be sure the tables know about the new location number). If the item is in circulation at the time the change is taking place, DO NOT change the loc/subloc or the location number via a batch program as this will upset the circulation history file. The online system knows how to reconcile such changes to loc/subloc codes in copy statements. It automatically changes the item location number to match the new loc/subloc. If the item is in circulation, it places a temporary location in the item until the item is returned. Batch programs must be taught to do all of this also or else great discrepancies will occur. Maggie Hogue, FCLA's table guru, knows more of the gory details of this process if anyone wants more detail. She can be reached at FCLMAH@NERVM. Michele Dalehite, FCLA