[436] in Tooltime

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

Re: debi/steve thing

daemon@ATHENA.MIT.EDU (Debi Fuchs)
Fri Oct 24 09:59:35 1997

In-Reply-To: <v03007800b06007cfd971@[18.177.1.22]>
Date: Fri, 24 Oct 1997 09:59:57 -0500
To: Steven Wade Neiterman <wade@MIT.EDU>
From: Debi Fuchs <debi@MIT.EDU>
Cc: tooltime@MIT.EDU

Hi Steve,

Here's more stuff.  I will be checking out the Scopus data today.

------------------------------
>One more comment, I think we should make the default consultant search on
>the main screen be something other than Any.  The Any search takes the
>longest time as compared to search within the last week, 30 days or 60
>days.  How about a 60 day search as the default?

Sounds good.


------------------------------
>I quickly added the ability for a consultant to send mail (via a checkbox)
>when updating a customer log message via the web.
>
>There are a number of questions, e.g. what should be the "From" field (as
>well as the "reply-to" field).  Where should bounced mail messages go?
>
>Anyway, give it a test drive.

I did...works great.

What will be the eventual email address for the email interface (I assume
it's not going to be blue...has it been decided?)  I think that is what
should be in the from and reply-to fields, with the name "MIT Computing
Help Desk".



-------------------------------
>2.  The query screen does say, "Found 224 records" "Only first 100
>    records will be shown".
>
>    I presume you want me to change "Only first ...." to "Showing
>    first xx matching entries".


Yup, sounds good.  How about"Found 224 matching entries.  Displaying first
100 records only."


-------------------------------
>I added a Next and Previous function to the log screen.  These functions
>appear when you select a record from the query results screen.  Once in the
>log screen, you can now navigate through the query results.  It's really
>cool, check it out.
>

Great!    Very fast...   Can we put them at the bottom of the screen, too?


-------------------------------
>As follows:
>
>  Network installation records: 235 Rows successfully loaded
>
>  Help Desk records: 2975 Rows successfully loaded
>
>The data represents questions through October 1, 1997.
>
>IT'S REALLY IMPORTANT to check this out in the Scopus GUI.  Finding
>records, making changes, saving the record, etc.
>
>We are looking for any errors (e.g. improper lookup field data will show an
>error on save as well as missing required fields), missing data from the
>conversion, etc.

Okay. Glad the conversion was successful.



-------------------------------
>>-How does find on name work...only on last?  If so, can we label it as such?

>It's possible that we lost some rules in the Filemaker script from when we
>did this last Summer.
>
>I did some minimal testing in Scopus and found some problems.  For example,
>I could not issue a search on lastname and locate an existing record.  I
>believe that we had agreed that names would be stored in upper case in
>Oracle, thus whatever the consultant typed, we would find the name by
>converting it to uppercase and then doing the match.
>
>If we lost this from the script, I wonder what else may be going on.
>
>Can you tell me have any feedback you have from testing Scopus?


I'm using a wholly different process than Peter did to do the conversion.
It took a while to set up, but will allow for pretty quick conversion of
new data. Are you saying I should be converting the names before I export
them.  I can do that if necessary.

Can I ask why it is necessary to store names as uppercase?  The scopus
command for a find "by example" on last name seems to be:
  SELECT mit_log_id "Log", substr(mit_status,1,10) "Status",
         mit_category "Category", mit_pri_lastname "Last Name",
         mit_pri_firstname "First Name" ,
         substr(to_char(mit_created_ts,'YYYY/MM/DD HH24:MI:SS'),1,20)
         "Created On",  substr(mit_summary,1,80) "Summary"
   WHERE  0 = 0 and  mit_pri_lastname  LIKE upper('fuchs')
   order by mit_log_id asc

Is it, for some reason, not possible to set up the find "by example" to
have the WHERE clause as follows:
   WHERE  0 = 0 and  upper(mit_pri_lastname)  LIKE upper('fuchs')

If it is not possible, could you explain to me why? Is it a limitation of
Scopus, of Oracle, of our implementation of Scopus, of doing finds by
example in Scopus?

Also, in the Web interface I can do a query on 'fuchs' but not on 'deborah'
or 'deborah fuchs' or 'fuchs, deborah'.  Could we do a query behind the
scenes something like this:

   SELECT mit_log_id, mit_pri_lastname || ', '|| mit_pri_firstname,
          mit_summary FROM mit_logs WHERE
     upper(mit_pri_lastname)=upper('&1') OR
     upper(mit_pri_firstname)=upper('&1') OR
     upper(mit_pri_lastname || ', ' || mit_pri_firstname)=upper('&1') OR
     upper(mit_pri_firstname || ' ' || mit_pri_lastname)=upper('&1');


---------------
That's all for now.

-Debi





>>-I'm still not able to create users yet with my password.
>Done.  Your all set.


Yes, it seems to work. Thanks!




>Something I thought after I left you, when you type "add tooltime", also
>type "add oracle" so that you have access to SQL*Net.

Hmm...when I telnet to jenseits, I get:

   ~% add tooltime; add oracle; cd /mit/tooltime; sqlplus;
   sqlplus: Command not found.

   /mit/tooltime%

When I am logged in directly to shim-sham, I get:

   ~% add tooltime; add oracle; cd /mit/tooltime; sqlplus;

   Message 133 not found; No message file for product=SQLPlus, facility=SP2:
   Release 3.1.3.5.1 - Production on Fri Oct 24 09:24:33 1997

   Copyright (c) Oracle Corporation 1979, 1994.  All rights reserved.

   Message 231 not found; No message file for product=SQLPlus, facility=SP2
   Message 428 not found; No message file for product=SQLPlus, facility=SP2
   Message 231 not found; No message file for product=SQLPlus, facility=SP2
   Message 428 not found; No message file for product=SQLPlus, facility=SP2
   Message 231 not found; No message file for product=SQLPlus, facility=SP2
   Message 428 not found; No message file for product=SQLPlus, facility=SP2
   Message 157 not found; No message file for product=SQLPlus, facility=SP2

   /mit/tooltime%

I am able to use sqlplus on my Mac for now.


-------------
Debi Fuchs, Consultant
MIT Information Systems
Computing Help Desk Group
77 Massachusetts Avenue, 11-319
Cambridge, MA  02139
(617) 253-7812
debi@mit.edu



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