[122] in iswork
Notes on IS Work database
daemon@ATHENA.MIT.EDU (Robert Ferrara)
Sun Oct 8 13:34:12 2000
Message-Id: <4.3.2.7.2.20001008124328.00b24ca0@po9.mit.edu>
Date: Sun, 08 Oct 2000 12:53:01 -0400
To: tjm@mit.edu
From: Robert Ferrara <rferrara@MIT.EDU>
Cc: iswork@mit.edu, kcunning@mit.edu
In-Reply-To: <39CC0BAA.48041DCC@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Tim, Kris,
Here's some comments from my recent work with IS work.
First, it's very good.
This is now real production data, and we'll have to treat it that way. How frequent are backups?
The only bug I found was the one I mentioned in the other message: If you assign an Initiative to a Project, it "deselects" the currently assigned Process/Performing Organization, setting to blank. To get it right, you now have to do a more cumbersome, two step operation.
To properly describe Terminated projects, I think we need another Phase value - "cancelled", to go along with planned, discovery, delivery, and operational.
I think Practice should come from a pick list and not be free form.
A number of the "test" projects and "9**" Initiatives will have to be deleted. I can see NOT having a delete function, but then will one of us will have to do this with SQL?
The "hierarchy report" will be very useful.
Cheers, Bob
