[115] in Tooltime
Scopus Implementation Meeting May 28, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue May 28 11:53:30 1996
Date: Tue, 28 May 1996 11:54:47 -0400
To: tooltime@MIT.EDU, tarnett@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Scopus Implementation Meeting May 28, 1996
Attending: Lane, Pakulat, Saylor, Sousa, Wade, Willis
Agenda
1. Roundtable
2. Planning
3. Next steps
1. Roundtable
Wade:
- Announcement of availability of Scopus Solaris clients
on AFS.
- To invoke, use either
"add tooltime; start_scopus" (for Scopus client) or
"add tooltime; start_design" (for DesignTEAM)
NOTE: It is NOT recommended that you make changes
using DesignTEAM as it may interfere with on-
going development.
- Announcement of availability of Windows 16 bit client
via AFS. (/mit/tooltime/dist/win/scopus-ins.exe)
- Thanks Ray and John for the installer.
- Installer available from Scopus Project Notebook via
Web (http://web/tooltime/www/scopus_notebook.html),
then click on the release section.
- Needs more work, e.g. release notes, win 32 bit
binary, error handling.
- Scopus announcement on Reeng. Home page
- If you had not noticed, for the Month of May, there
is a line in the Reeng. milestone section that MIT
acquired Scopus to be used first for the MIT Help
Desk. If you have not seen it, there's two more
days before the May milestones are removed. Check
it out.
- Will pursue conversation with Open Horizon, middleware
vendor with Kerberos 5.0 SQL*Net compliant drivers
(Windows, Unix, signing an agreement with Bear River
for Macintosh driver). Can be used with Scopus to
obtain secure login. Evaluation hopefully to be
conducted during the Summer.
- Attempting to complete Requisition for new production
machine by end of this week, possible order by early
next week. Should have more information to report at
next week's meeting.
- Scopus project notebook updated, see web url (stated
above). Is anyone interested in writing documents for
project notebook e.g. procedure to setup accounts, etc?
Look at notebook to get an idea of how the documents we
are producing fit into the overall project.
- There seems to be interest in email to some database
tracking (FileMaker, Scopus, Discuss), using the Web to
format the data prior to sending via email. Need to
stay on top of this and determine if there is a common
solution. If we evaluate this in July for Scopus, will
we be too late for what others at MIT may start doing?
Tom, Al and John have interest in this area.
- Does someone want to attend the Repair & Maintenance
Scopus demo this afternoon 1:00 - 4:00 pm? Arrive at 3:00 pm.
- If anyone is interested in learning about Scopus development,
now is the time (short of going to a class). Technology
transfer with the consultant during the development phase is
as important as producing the application.
Lynne
- Has supported product list from Al, this will be used to fill
in code tables.
- Has comments on Design Specification, e.g. required fields.
Talked about MIT (Lynne) making the change to the design spec,
need to talk to Terry on how to proceed.
- Noted that others (e.g. transmission group, mainframe) need
access to Scopus.
Harold
- Furnished list of reports to Peter (see last week's meeting notes).
(Waiting for Peter to collate report information and send out)
- Question: How much time is needed for resources? Need to know who
is working on Scopus and how much time from Help Desk personnel.
2. Planning:
- Prioritized screens/functions for development:
1. Main Help Screen
2. Status
3. NetInstall
4. Secondary Information
5. Housecalls
6. mainframe
7. ADSM
8. MIDAS
- Items 1 through 5 are required for release 1 delivery.
3. Next Steps:
- Lynne to check with Terry on updating Design Specification.
- Lynne and Al to work on Filemaker field layout as we begin the
process to migrate a small amount of legacy data to Scopus.
- Peter (last week's action items) to send draft storybook and
report listing.
Next Meeting
June 4, 1996
10:00 am
11-124A
Main agenda item: Progress on development