[276] in Tooltime
Re: Scopus 1.0b6 testing comments
daemon@ATHENA.MIT.EDU (bdrosen@MIT.EDU)
Fri Oct 4 09:43:34 1996
From: bdrosen@MIT.EDU
To: plee@MIT.EDU
Cc: tooltime@MIT.EDU, tooltime-bugs@MIT.EDU
Reply-To: bdrosen@MIT.EDU
Date: Fri, 04 Oct 1996 09:43:10 EDT
On Fri, 04 Oct 96 04:29:09 -0400 Peter Lee <plee@MIT.EDU> writes
...
|>
|> 4) Problems with searching (Productivity loss)
...
|> b) History and Summary Find clears search string regardless of
|> results. Retaining search string is useful when you make a
|> mistake and you want to edit it.
This should be easy to fix.
|>
|> c) With History and Summary Find, putting an carriage return at
|> the end of the search string and clicking on Find results in
|> search failure. This is easy to do, and mysterious to
|> figure out why search failed.
I am not sure why this is a problem. The search is on the search
string. If the search string contains a carriage return, then the search
is going to look for a carriage return. Would you rather have the search
ignore all carriage returns (or other commonly used non alphanumeric
characters) ?
|>
|> d) Question: Is there any special syntax for History and
|> Summary field search string? E.g. wild cards, regular
|> expressions, etc.
|>
The search used is the same as the Oracle search. So Oracle
rules apply. This means that % stands for any number of spaces or
characters and _ represents one space. There is no regular expression
syntax.
|> e) After a find, it would be desirable that the result set
|> update automatically when the records get updated. For
|> example, when a log's status changes, it would be good if
|> the the row of result set updated to reflect the record's
|> new status.
|>
|> If automatic update is not possible, would it be possible
|> to have an "update" button on the result set window that will
|> do this manually?
I would guess that the automaticate update would not be
feasible. As for the update button, I believe that the result sets have
a modify result set button which lets you modify the search
clause, run the result set again or both. (Solaris client)
The run the result set again button should allow you to "update" the
result sets.
|> h) In result set windows, can the default widths for category,
|> last name, and phone fields be reduced in size?
This should be easy enough to do if people think it is
desirable.
|>
|> i) Can History and Summary Find search string windows be
|> horizontal instead of vertical as they are now? (Especially
|> since we can't put a carriage return in the search string
|> any way?
This should be easy enough to change as well. However making it
horizontal probably won't ensure that carriage returns aren't in the
string. Also, putting carriage returns in the search string should work
well in cases where the text you are searching against has the carriage
returns as well. (however our filemaker data does not have the carriage
returns due to some complications with loading the data.
I would like to add a "bug report" of my own at this point. When
I started up the Solaris client, I noticed that the helpdesk screen
still has the overlapping fields that have been reported as well. I
realize that the unix client has the least priority of the three
clients, However I think that completely ignoring its problems is
wrong. Are you really sure that nobody is going to want to use it?
Also, it is wrong to assume that fixing the problems with the mac client
fixed the problems with the unix client (since the problems looked
similar)
Brett Rosen
