[449] in Tooltime

home help back first fref pref prev next nref lref last post

Re: Scopus questions

daemon@ATHENA.MIT.EDU (Peter Ragone)
Wed Oct 29 08:57:42 1997

In-Reply-To: <v03007809b07c0b030d1c@[18.177.1.22]>
Date: Wed, 29 Oct 1997 08:41:11 -0500
To: Steven Wade Neiterman <wade@MIT.EDU>
From: Peter Ragone <pragone@MIT.EDU>
Cc: goguen@MIT.EDU, tooltime@MIT.EDU

1) Yes, sounds right to have David and me re-enable the MOTD feature on the
Mac as long as it won't cause a crash. We shall also check for that.

2) I am a little curious why hitting save should revert the log to new if
the hardware field is empty. Seems to me that we should fix that rather
than resorting to a kludge such as filling in "hardware" in the hardware
field (btw, "phone" and "email" as strings seem odd too, but that's only my
opinion. I'll do the fix whichever way you like). Filling in "unknown"
makes some sense, though. We'll take a look at it.

3) I believe we're not allowing 'quickies' any longer. I'll talk with
Alicia our protocol guru about how the Scopus interface should behave and
what it should allow regarding quickies.

-Peter

>At 4:11 PM -0500 10/28/97, Barbara Goguen wrote:
>>Hi Steve.  As I am playing with Scopus in preparation to do a student
>>training session next week, I am coming up with questions.
>>
>>Do we plan to use the Message of the Day feature?  From what I recall, it
>>works fine on the Windows and unix platforms, was just problematic on the
>>Mac.  Is this true?  If we are going to use it, how does one go about
>>putting up a message?
>
>David and Peter, can you re-enable the motd (my understanding is that we
>disabled it on both the test and production database while the Macintosh
>was crashing).  Please then test the Macintosh client to see if the motd
>has been resolved.
>
>Regarding updating, consultants with maintenance access can use the MOTD
>screen to update the message.
>
>>
>>The NEW button does fill in text defaults for all required fields EXCEPT
>>hardware.  It seems to me that it may make sense to be consistent, even if
>>somewhat goofy, and fill in a default text string of "hardware" in that
>>field too.  That way at least the status wouldn't chage back to NEW upon
>>hitting SAVE without filling in something for Hardware.
>
>Ok, let's add it to the list.  David and Peter, this item is yours.  Seems
>simple enough, as we default the phone and email field (e.g. PHONE and
>EMAIL respectively), let's add a default.
>
>Question for the help desk staff, could we use "unknown" instead of
>"hardware"?
>
>>
>>In the training doc that Esther did, she documents the process for quickie
>>logs.  She writes, "In the email field type quickie".  Why did we decide to
>>indicate the "quickiness" of a log in the email field?!
>>
>
>Gee, does this work?, It sure sounds strange.  The design document says
>that the quick button performs a "quick close" on a log.  I believe the
>quick button was removed at one point (if we really care, this should be
>documented in meeting notes on the web).
>
>It's also possible that I am spacing on this item, maybe someone from the
>team remembers.
>
>..Steve




home help back first fref pref prev next nref lref last post