[44] in ad-lib
Re: Advance points
daemon@ATHENA.MIT.EDU (Eric Celeste )
Fri Feb 24 14:22:02 1995
To: steps@MIT.EDU
Cc: ad-cat@MIT.EDU, rschmidt@MIT.EDU, rchall@MIT.EDU, hkennett@MIT.EDU
Date: Fri, 24 Feb 95 14:21:35
From: efc@MIT.EDU (Eric Celeste )
A few days ago Stephanie sent me the following questions. I thought it
might be helpful to answer them on the list...
> Keep dashes for LC card #/issn? (doesn't seem to matter)
Dashes are turned into spaces for most searches. We were told in Geac
training to leave dashes out of ISBN/ISSN searches, but those searches work
with the dashes, feel free to use them. (See my next message about a bigger
problem with I= searches.)
> Will "Return to Master Menu" option eventually work?
> Will all the modules be linked and what kind of access
> will we have to serials for instance?
No. I doubt the "Return to Master Menu" will be the route we choose to
allow cross-functional activity (the way Advance is designed, this just
won't do most users much good, as far as I can tell). But, YES, we will be
adding access to parts of the other modules--serials is a good example of
the kind of cross-module work we need to support. Let the list know of
keywords from other modules you think we need to support in cataloging.
> Brief definitions of options in the menu bar
> (e.g., what does "copy cataloging" mean here?)
Take a look at the Cataloging Users Manual for these kinds of descriptions.
Just don't expect too much!
> Will we be editing the 866s or the 930s for holdings?
> Has this been decided?
No, this has not been decided. The 930 is _not_ the likely answer. It's
probably the 866 or editing copy set records. What do you think would be
the best approach?
> Explain "Extended search options (title, author, subject...)"?
Don't bother learning this search screen... it will be changed. Instead I
would concentrate on the search keys that are going to be available no
matter what the screen eventually says. (A training sheet is available on
Athena for printing. "add efc;lpr /mit/efc/advance/sheet/search.ps")
> Searching GRSNs--"GLIS" is case-sensitive
Yup. To search GRSN #234000 we have to type "CN=GLIS00234000". Note both
the upper-case GLIS and the two leading zeros.
...Eric
Eric Celeste / MIT Libraries / 14E-210A / 617-253-0633 / efc@mit.edu
