[9] in Project_DB
scope of work by 2/15 seems doable
daemon@ATHENA.MIT.EDU (Bruce R. Lewis)
Fri Jan 31 17:28:40 1997
Date: Fri, 31 Jan 1997 22:28:28 GMT
From: "Bruce R. Lewis" <brlewis@MIT.EDU>
To: project-db@MIT.EDU
My analysis of the project-db code that currently exists vs. the changes
wdc talked about is that the changes targeted for 2/15 (a Saturday, by
the way), are reasonable. Here are some notes I took re. wdc's
comments, sorting them by the WWW page they affect.
>Things to change in the design:
(1) PROJECT SUMMARY (list of projects)
>Make projects summary page be the first page people see.
Easy. People can bookmark the frontpage page. The menu.html page can
be changed to contain only a pointer to the start page.
>CHanges to summary page:
> add Search button
Done.
> add Add project button-- if possible conditional on
>director/leader status
In progress...depends on "Create project" form.
> Add go to IS home page button
Done.
(2) PROJECT DISPLAY (individual project)
>Changes to project display page
> add modify button -- if possible conditional
Done (by delgado), conditional.
> add button to show project documents
Should show them on project display.
> add button to show team
Miki said earlier that we should have this, but changed her mind after
looking at the schema.
>Documents that exist for a project are currently not displayed on the
>project page. They should.
I agree. User shouldn't have to press a button.
(3) CREATE PROJECT
>Multiple project creation web forms consolidated into one.
This should not be terribly complicated. They are already consolidated
as a procedure with a conditional on whether or not it's a discovery
project. Can simply modify existing code; possibly add one small
procedure.
(4) SUBMIT STATUS (page shown after "create project")
>Submit status display adds:
> button to create another project
> button to go back to summary page. (DONE)?
These are easy, and I will do them. However, I recommend people use the
Back button on their browser if they want to keep their history list and
back button usable. (This is a general WWW navigation tip.)
(5) MODIFY PROJECT
>Modify screen is the same form as create, with the fields filled in from
>the db allowing the user to modify all.
I believe this is done. (pdb_tl.project_menu). (Eliminate mod_plist).
(6) IDEAS
>Separate pages for:
> Ideas -- view ideas; view an idea; submit a new idea; delete an
>idea; submit comment. Note: Idea manager is postponed until project
>page up.
I don't see what functionality is proposed here that doesn't exist with
an archived mailing list. Unless there's a proposed way to
systematically convert ideas into projects, I think it would be best to
scrap the "idea" database and use a mailing list instead.
