Email list hosting service & mailing list manager


Re: Dynix serials module (Marie Murphy) Stephen Clark 27 Feb 1998 19:33 UTC

---------- Forwarded message ----------
Date: Fri, 27 Feb 1998 13:59:44 -0900
From: Marie Murphy <mamm1@NSH.LIBRARY.NS.CA>
Subject: Re: Dynix serials module (Mary Oswalt)

As yet we are not on version 170 but I have read an article on it and
it's enhancements.  I cannot help you with the first item but the second
item has to do with claiming, I will quote from the article:

CLAIMS NOW INDICATED ON THE SCKI EXPECTED ISSUE SCREEN
On the Expected Issue screen a "C" now displays beside each issue that
has one or more claims attached.  If the person viewing the issues is
authorixed to receive them, the "C" is in uppercase.

Hope this helps.

Marie D. Murphy
Serials Supervisor
Technical Services
Halifax Regional Library
mamm1@office.nsh.library.ns.ca
Phone (902)-869-4425

On Fri, 27 Feb 1998, Stephen Clark wrote:

> ---------- Forwarded message ----------
> Date: Fri, 27 Feb 1998 09:33:07 -0700
> From: Mary Oswalt <moswalt@LIBRIS.CI.WESTMINSTER.CO.US>
> Subject: Dynix serials module
>
> This message is for anyone out there who uses the Dynix serials module. We
  are on version 170 and have been using the serials module for about two
  months. We have yet to get a user's guide for it, although we have
  requested one. A few things have come up that we can't figure out, and
  we would appreciate any insights from those who are more familiar with
  the module than we are.
> (1) We have a weekly publication which has no enumeration info, just
  chronology. On the subscription summary, instead of being summarized
  with a range of dates, the issues that we have checked in are listed in
  a column, with a comma at the end of each line. We are missing one
  issue; could this gap be the reason for this form of display?
> (2) We have noticed that on our expected-issues screens, many issues have
  either a lower-case or upper-case "c" in front of them. In some cases
  they are issues that we have not yet received, but many times we have
  received the issue. What do these "c"'s mean, and how are they generated?
>
> TIA for any help you can give us.
>