[325] in ad-lib
Geo whiz!
daemon@ATHENA.MIT.EDU (sbyrd@MIT.EDU)
Wed Apr 12 18:11:57 1995
From: sbyrd@MIT.EDU
To: opac-lib@MIT.EDU
Date: Wed, 12 Apr 1995 18:11:46 EDT
1. GeoNina seems to be totally right about the searches that don't work.
2. GeoNina said she couldn't get 11.2.3.3 (combined search) to work--I
think you can, using the Command option and combining keyword searches--I used
Advance search keys, and they seemed to work--
ex.: COMMAND SEARCH: (aw=faulkner) and (tw=sound)
so I think it _does_ do this----(of course, I had to guess at all
this, the help screens are AWFUL, and a search like (tw=nuclear) and
(nw=nuclear) seems to blow the system up. Oh well.)
3. 11.3.5--
Right, I couldn't either--I have a feeling though that it's not
because it can't but just because the way they've set it up, they've
chosen not to. I don't know enough about geopac setups yet, but I
suspect that we can set up which fields display in the full display.
4. GeoNina, you've covered it all!
5. As far as "help" goes, I'd like to see a lot more in the help
screens in the way of explaining "command" searches (like, what are
they? which commands work?) or "BLCN" search (we know what it means,
but I couldn't find a definition of it anywhere), or the whole search
mechanism. I tried to read the help stuff to figure out just what
fields were indexed for each kind of search, and rapidly got nowhere.
6. Ditto on the windows thing that Bill C. pointed out.
--Sam
