[251] in Tooltime
Scopus Implementation Meeting Sep 17, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Thu Sep 19 14:23:33 1996
Date: Thu, 19 Sep 1996 14:24:32 +0100
To: tooltime@MIT.EDU
From: Steven Wade Neiterman <wade@MIT.EDU>
<fontfamily><param>Times</param><bigger><bigger>
Scopus Implementation Meeting September 17, 1996
Attending: Ragone, Saylor, Smyser, Sousa, Wade
Agenda:
1. Training Document Review
2. Roundtable
3. Next Meeting
-----
1. Training Document
Rob handed out a revised copy (version 3) of the Training document.
It has updated content and an easier to read format. New document
evaluates issues with changing the screen/font size and has lots
of screen images to help with the reading.
The team reviewed the document and discussed changes.
Release 2.0 item may be to convert the MSWORD document into
Windows
Help (which Scopus uses - don't know about Unix or Mac?). Release
1.0 will have web access to the document.
We also need to get Esther back involved to review the document
after the base information has been gathered.
The 9/10 meeting brought up issues related to:
- Who's responsible for long term maintenance of the document?
- Can we link the document to the Consultants Web page?
ACTION ITEMS:
- Agreed to add information on Housecalls, Netinstsall, and a
table of
contents. Additionally, an appendix (e.g. FAQ) will be
included.
- Peter Ragone will perform a Quality Assurance review on Tuesday
9/17
- Rob will produce a version 4 and give Wade a copy for the
Web project notebook. Agreed that this would be done by
Thursday 9/19.
2. Roundtable
-----
Wade:
- Test machine lost /u2 disk, which contained Scopus development
tools. The outage lasted from 8:00 am Monday 9/16 through 10:00
am
on 9/17. Replaced the 2Gig drive with a 1Gig drive and restored
files.
- Export/Import on schedule for this week. As changes occur,
development team needs to capture extent of changes to determine
if
we make same change to both machines or request another
export/import.
- Need to make following database changes:
- Netinstall table - room number field too small
- New data warehouse feed to correct department name
- mit_lk_hardware field too small in mit_logs table
- Phone numbers in warehouse need hyphens
- Filemaker data has lastname, firstname switched, need reload
- Reload data for software, missing column in database
(next two items may have been stated in other meetings)
- Would like to complete project with a post-mortem, located
facilitator
from IS to lead discussion.
- Evaluating additional development resources for the hand-off
between
development work and the service process.
- Production machine proceeding, this week will load scopus
software.
Test machine will need to be upgraded on both the OS and
database
after we migrate to production.
ACTION ITEMS:
- Check with Scopus on availability of fixed Macintosh client
- Complete database changes needed for release 1.0b6
- Coordinate with Facilities Management on database backup
procedures
for the test database.
- Coordinate with database services for export/import of test
database
to production database, expected prior to end of week 9/20.
- Project admin stuff: resources (service migration), adjust
schedule
- Refine SLA with Facilities Management on production machine and
coordinate loading of Scopus software on the production
machine.
- Confer with database services on existing user account script
review
-----
Rosen (via Wade):
- Submitted response to Scopus on InformTEAM issues (8/29). Brett
sent a clarification of the Scopus response, but Scopus closed
the
log.
ACTION ITEMS::
- Follow up on InformTEAM, if Scopus wants to close the log, I
guess we should submit a new log/transaction.
-----
Sousa:
- Working on task list for 1.0b6 (see motd for updates), priority
includes problem with backfill, issues with lock and fix oracle
error message in Housecall screen.
- Lynne conveyed concerns of the Help Desk staff with regards to
the timing of the production release. There have been
discussions
at the help desk staff meetings with regards to a spike in the
current 540 (approx.) open queue due to the implementation of a
new system.
ACTION ITEMS:
- Complete release 1.0b6 - see enclosed notes
- Lynne will complete the Programmer's Guide with the latest
1.0b5
changes and send back to Esther. It should then be complete
and
ready for the Web.
-----
Ragone:
- Installed Brio Query and connected to database. Beginning to
learn tool and compare it's functionality against the list of
reports generated during the requirements phase.
ACTION ITEMS:
- Continue exploring Brio Query, report progress to team,
including
a demo on 9/24.
- Help with QA on training document
- Continue with QA on the 1.0b6 application changes from Lynne
-----
Smyser:
- Currently working on training document, see additional notes in
this document.
ACTION ITEMS:
- Helping out with training document.
- Continue with QA on the 1.0b6 changes from Lynne
- Test Scopus Windows over Tether
3. Next Meeting:
Tuesday September 24
10:00 am
16-720
-------------------------------------------------------------------------
Status of on-going tasks - last updated Monday September 16, 1996
This should be the only agreed upon work currently underway for
release 1.0b6
DETAIL OF ACTION ITEMS AND COMMENTS:
2. The Secondary Information fields are a waste of screen space.
Added issue is the font size, greatly affects near-sighted people.
ACTION: Remove secondary information from the screen,
leaving the database untouched for revisit of this
function in release 2.0
Assigned: Lynne (1/2 hour effort)
9/16 STATUS: Mostly done, problem with callback
ACTION: The main help screen will be rearranged (required with
the removal of the secondary info) to allow more white
space between fields, and a smaller window frame.
Assigned: Lynne - 3 hours.
9/16 STATUS: DONE
ACTION: Larger font will be researched to determine solution.
Two options: 1. Test using the Scopus options settings
for fonts and screen real estate. 2. Evaluate machine
resolution, changing from 1024 to 800x600.
Assigned: Rob and Peter R. - deadline Thursday 9/12 for
research and next steps determination (Friday 9/13
meeting)
9/19 STATUS: DONE, Rob to include findings in training
doc,
determined that font can be changed for log history,
otherwise, use 800 X 600.
4. "op-update-rel: dbsqlexec failed" and "ORA-01401: inserted value
too large
for column"
Tooltime team comments: Need to further identify which field is
having
the problem.
Assigned: Wade to send mail to originator the the bug report.
9/19 STATUS: Still need to locate which fields have problems
5. Clicking in the "History Entries" box, then pressing [Tab] puts an
entry into the Summary box then *two error messages* appear.
Assigned: Lynne to research and report. Effort - 1/2 hour.
9/19 STATUS: Decided to remove automatic save to eliminate errors
6. In the Housecalls section, clicking "Save" resulted in the error:
"op_get_field_update_info: key field mit_log_id may not be
updated"
Assigned: Wade to send mail to originator for more information.
Estimated possible 1 hour to fix based on understanding of Tcl
code.
9/19 STATUS: Lynn to work, estimated 3 hours, broken Tcl code
7. Scopus repeated error messages often. That is, an
error dialog box would appear, I would dismiss it by clicking
"okay", then
the exact same error box would pop up again. Clicking "okay" once
more
dismissed it for good.
Assigned: Rob and Peter R. will investigate to determine sequence
of
when this occurs. Report by end of day Thursday.
9/19 STATUS: Rob and Peter were able to recreate problem.
Determined
to be problem with not using items in pick list for constrained
fields.
Decided to identify (via a label change) those fields that are
constrained.
8. In the Mainframe Maintenance section: the MITVMA and MITVMC fields
are
not totally visible. The last letter of each word is mostly cut
off.
Assigned: Lynne Effort - 20 minutes
9/19 STATUS: ???
9. The % (wild card) symbols for blank fields are confusing and
unnecessary when doing a search.
Tooltime team comments: The % sign is used by scopus to determine
the field is used for searching. This may be a Scopus design
feature/limitation. Options were discussed, including a.
training,
b. user types an asterick (another internal scopus feature) on
each
field used for searching, c. user issues a clear primary.
Assigned: Lynne to evaluate mail from Terry Arnett on possible
options/solution. After information gathering, decision to be
made
at Friday meeting.
9/19 STATUS: Mail sent, reply received. Decided not to take any
action. Will evaluate usage and problems after release 1.0,
specifically if % signs are being stored in the database.
12. Department name is missing on data from warehouse (item added by
wade).
Assigned: Wade to revise data feed from warehouse and reload data
Effort 45 minutes.
9/19 STATUS: Discussed problem with data warehouse team, change
made to warehouse data to allow access to department number.
Next
step is to populate Scopus with this information.
13. Locks may still be an issue (item added by wade)
There was a desciption during the feedback meeting regarding using
the View Hits button and causing an item to be locked. If there
is
no workaround, this is identified as a training issue.
Issue may be more complex if existing code for locks is not
working.
9/19 STATUS: Lynne will evaluate work arounds via the callback
routine and report progress to team. Specifically, check for
issue Clear as well as check for unsaved changes.
14. Mac model list is incomplete (item added by wade)
Assigned: Wade to evaluate reloading data, Effort: 30 - 45
minutes
9/19 STATUS: Completed. Determined there is a problem with a
missing
field. The load will need to be redone.
15. Eudora to Scopus copy and paste (item/concern added by wade)
Assigned: Lynne will do a quick test to copy an eudora mail
message
into Scopus and show that it works.
9/19 STATUS: ???
16. Lastname and Firstname from Filemaker data appear switched in
Scopus
9/19 STATUS: Peter Lee informed, need to load new Filemaker data
17. Problem with inconsistent edit masks in phone field. Warehouse
data
does not use a hypen, default phone field stored in logs table
displays
a hyphen.
9/19 STATUS:
Lynne to confirm that the Tcl code does not strip out hypens
prior to
any change being made.
Wade Agreed to make a change to the warehouse to store hyphens in
the
phone field if the Tcl code acts as expected. Waiting on
answer.
</bigger></bigger></fontfamily>
