Re: [IUG] Centralized item record deletions
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
We have done some similar things, although not with item deletions.
1) mending: repairs are a low priority and we often have backlogs. So
items are checked out to a patron card: Mending/Book Prep. This record
has its own patron type so that we can exclude it from regular
circulation statistics (something you will need to watch out for if you
create a Deletion patron) and so that it does not get overdue notices.
Items can, however, be recalled from Mending. This works well for
2) withdrawal review: for this we use an item status code. If the
item is withdrawn, it goes through our regular process (which involves
suppression rather than deletion); if it gets retained, the status is
removed and a retention decision note added in the record. We used a
code because we may pull several thousand titles at once and that does
not work well with a patron record checkout.
So if your deletions are no more than a few hundred, having a deletion
card should work fine, but watch out for your circulation statistics.
If possible, create a patron type specifically for such processes, and
then you can also set up its own loan rule. However, if you use a
deletion card, you will have to check the books back in before you can
delete the record. The system will not allow a checked-out item to be
Systems Librarian and Cataloging Specialist
Library, Calif. State Univ., Los Angeles
scard at calstatela dot edu
From: innopac-bounces at innopacusers dot org
[mailto:innopac-bounces at innopacusers dot org] On Behalf Of Seden, Ali
Sent: Friday, December 05, 2008 12:03 PM
To: innopac at innopacusers dot org
Subject: [IUG] Centralized item record deletions
We're planning to centralize and simplify item record deletions, and
reduce staff work load. Centralization will also enable us to maintain
better control over our collection and generate more accurate
One of the options we're considering is to have staff check out items to
be discarded on to a DELETION card.
1) Have branch supervisors keep an eye on what's being removed from the
collection, prior to deletion. (Branch staffs are not allowed to create
2) Prevent item record editing errors.
3) Give staff time to reverse a discard decision without having to
contend with a ON-THE-FLY record.
Have any of you tried doing this? If so, what has been your experience?
Thanks in advance,
Enterprise Applications Department
Office of Library Technology
Brooklyn Public Library
Grand Army Plaza
Brooklyn, NY 11238
This message was distributed through the Innovative Users Group INNOPAC
Public replies: INNOPAC at innopacusers dot org
Update your subscription options: