Publisher responses to serial claims (2 messages)
Birdie MacLennan 03 Oct 1995 20:29 UTC
2 messages, 53 lines:
------------------------
Date: Tue, 3 Oct 1995 11:13:31 CST
From: Ginny Pinkerton <PINKERTON@LIBRARY.UTA.EDU>
Organization: UTA Libraries
Subject: Re: Publisher responses to serial claims
Genevieve Clay <LIBCLAY@ACS.EKU.EDU> wrote:
> My check-in clerk is having an annoying problem with publisher responses
> to claims sent from our vendor as our NOTIS Acquisitions module
> generates the claims.
>
> One of the claims we use daily reads, "Our records indicate the next
> issue on our subscription is overdue. The last issue received was...
> Please send the next and following issues."
>
> The claim letter is worded clearly - right? Apparently not! More and
> more often we get the last issue as listed in the letter. It's a
> duplicate, of course ... is
It sounds like you are using the code "suli=". We have been using
the code "sumi=" which translates "Our records indicate we regularly
receive the above title on our subscription. We have not yet
received _________. Please send or advise."
This seems to avoid the problem you mentioned, since whoever fills
the claims obviously doesn't take the time to actually read them.
They just scan for the issue number and send it.
Ginny Pinkerton <PINKERTON@LIBRARY.UTA.EDU>
--------------------------
Date: Tue, 3 Oct 1995 12:00:16 -0700
From: Serials Unit <serials@SCILIBX.UCSC.EDU>
Subject: Re: Publisher responses to serial claims
Genevieve,
We discovered some time ago on our manual claim forms that utilizing the
"Hasn't been received since....", where we typed in the last issue
received, caused the same problem you've discovered. I no longer use it.
Our automated claim forms only list the issue we believe is due. It has
cut back on this problem of acquiring duplicates, and having to issue a
another claim.
Rosemary Bryan,
Serials Claims Coordinator
Serials Section
The University Library
University of California
Santa Cruz, CA 95064
email: serials@scilibx.ucsc.edu