[123] in iswork
Re: Notes on IS Work database
daemon@ATHENA.MIT.EDU (Kris Nyzio)
Tue Oct 10 09:43:28 2000
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a0bb608ccb826f7@[18.152.0.126]>
In-Reply-To: <4.3.2.7.2.20001008124328.00b24ca0@po9.mit.edu>
Date: Tue, 10 Oct 2000 09:43:25 -0400
To: Robert Ferrara <rferrara@mit.edu>
From: Kris Nyzio <knyzio@MIT.EDU>
Cc: tjm@mit.edu, iswork@mit.edu, kcunning@mit.edu
Hi Bob,
I have answers to some of your questions, and will set up a meeting with
Kevin to go over the ones that I can't address immediately.
>This is now real production data, and we'll have to treat it that way. How
>frequent are backups?
-Backups will occur once a week via ADSM while the data still resides on
fiji. Once the data is moved to the training db, Kevin will have to
provide backup details.
>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.
-We will address this in our meeting this week.
>To properly describe Terminated projects, I think we need another Phase
>value - "cancelled", to go along with planned, discovery, delivery, and
>operational.
-done
>I think Practice should come from a pick list and not be free form.
-We will address this in our meeting this week.
>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?
-I can delete them once they are ready to go. If this isn't the method you
would prefer, I can discuss other options with Tim and Kevin
>The "hierarchy report" will be very useful.
-We will address this in our meeting this week.
Thanks for your continued patience while we work through the final details.
Kris
