[481] in Tooltime
Re: Scopus GUI progress
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Fri Nov 7 08:31:30 1997
In-Reply-To: <v03110701b0880431987d@[18.81.0.181]>
Date: Fri, 7 Nov 1997 08:35:08 -0500
To: Peter Ragone <pragone@MIT.EDU>, tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
Peter,
Thanks for the update on the Find Open and Clipboard. Glad to hear that
you were able to fix the problem.
As you said in the first paragraph, I would work on some of the easier
items. For example, it would be good to complete - "When creating a new
record, fill in modified by user and timestamp with same information that
is used for creation date." This will keep the data consistent with both
the email and web interface.
I added the mit_hostname field to the mit_ni table. This would allow you
to add this field to the network screen.
Regarding the Find Open, maybe there are other options than Tcl. My
understanding from previous mail is that we ran into a limit on the size of
the SQL statement. I wonder if we could compress the SQL statement by
using a view.
Good luck,
..Steve
At 6:45 PM -0500 11/6/97, Peter Ragone wrote:
>Hi,
>
>Brief:
>-------
>1) Find Open button still not allowing to find by Category.
>2) Clipboard button in main Helpdesk window works now.
>
>Details:
>--------
>1) David and I are still plugging away, trying to get the Find Open to
>include a category. We will be able to get it to work if we hard-code the
>categories into a "switch" statement in TCL, but I didn't want to do
>something that will break if we alter the categories in the future. We may
>do that if time gets too tight. We'll continue to work on other stuff
>simultaneously.
>
>2) We fixed the global trouble with the Clipboard button in the main
>Helpdesk Log window. It was referring to a field named "Call Queue" or
>something like that which had been removed a while ago, so a silent error
>was halting the procedure. When we commented out the code referring to that
>field, the Clipboard button began working properly. I didn't investigate
>whether it works on the Mac or not; the manual indicates that it won't. I'm
>considering that low priority since it seems to have been investigated
>already.
>
>-Peter
