[247] in Information Retrieval
Printing from Mosaic
daemon@ATHENA.MIT.EDU (jamess@MIT.EDU)
Mon Jul 25 17:32:36 1994
From: jamess@MIT.EDU
To: patf@MIT.EDU, ps-lib@MIT.EDU, elibdev@MIT.EDU
Date: Mon, 25 Jul 94 17:31:39 EDT
I was going to answer this only to Pat, but I realize that others may
have the same problem or questions.
Pat asked:
> ... I'm not aware of any way to print Mosaic information. This is some-
> thing I've been meaning to investigate. Awkward printing capability or in-
> ability to print would make a Mosaic catalog much less desirable.
The viewers (Mosaic, Cello, lynx) offer different mechanisms to save/
print the results. On the workstation, X-Windows Mosaic allows you to save
it as Plain text, HTML (marked up), or PostScript. The last of these lets
you print out the screens exactly as you see them--graphics and all. To use
this feature, you click on the "Save ..." box at the bottom. The PC Mosaic
version *currently deployed* cannot print. It *can* save the HTML file. This
is probably not a good option. Lynx also lets you print the text. It cannot
display/incorporate the pictures. But using the print option allows you to
get an ascii copy.
> I also have no problem with Willow. I liked what I saw of it in the demon-
> stration, particularly the automatic browse feature. As for a Mosaic cata-
> log, would searching operate exactly the same way if accessed via lynx?
> Pat Antin
Yes the searching by lynx is similar. Since lynx is text-based, it can
be a bit frustrating using the cursor keys. The version of lynx installed
at MIT supports forms. I have searched HyperPALS from home using lynx. It
still is much nicer be able to click and link and not *lose* your old record.
I find it a frustration of GEAC to hit IND instead of CIT and lose everything.
Or need to write down everything and then go to a new index. There is little
loss of functionality between Lynx and Mosaic as regards HyperPALS.
A nice feature of many WWW servers is user authentication. It provides
a measure of how often, when, and from where the requests are coming. This
can provide not only statistics of who the users are but also provide some
control over access to resources. For example, our catalog/guides might be
public, ilb/rsc requests might be local (MIT), processing files might be re-
stricted access (Processng Unit). Just another point.
-- John Mess
