[2343] in Enterprise Print Delivery Team
RE: Request for New Web Interface Function Etc.
daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Tue Feb 26 22:18:34 2002
Mime-Version: 1.0
Message-Id: <p05010401b8a1ff52959f@[192.168.1.101]>
In-Reply-To: <OFE312398D.B3E2859A-ON87256B6C.007B4F4A@boulder.ibm.com>
Date: Tue, 26 Feb 2002 22:18:29 -0500
To: "Dave Dow" <davedow@us.ibm.com>
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Cc: "Daniel Cogswell" <danutek@us.ibm.com>,
Enterprise Printing Delivery Team <PRINTDEL@MIT.EDU>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
Hi Dave,
I'm glad you asked. I definitely want logical destination rather
than queue name. I was mixing terms due to moving back and forth
between the IPM world and the LPR world. For each queue I want to
store exactly the same information that I would normally store for a
userid: cost object (i.e. account number), building, and room number.
For example:
userid rclarke 7777777 N42 250L
ldest central-letter 9999999 W91 109
Based on your estimate and the 33 hours we have left on our service
contract for this fiscal year, I want to go forward with this
enhancement. Can you have it ready in two weeks?
Rocklyn
--------
At 4:27 PM -0700 2/26/02, Dave Dow wrote:
>Rocklyn,
>A couple more questions...
>1. When storing a record of type Queue, can you give me a real-life
>example of what you want in the database?
>I thoroughly understand the user information data, but I need a
>real-life example of one of your queue records.
>2. Do you really mean "queue name" for the key value or logical
>destinations - like you had in parens in your note?...hopefully this
>will be apparent via your example.
>
>My "new and improved" estimate:
>1. Create an entirely separate page for the administrators and
>implement it on our system (7-9 hours)
>2. Thoroughly unit test it/correct bugs/re-test/etc. (2-3 hours)
>3. Migrate the code to your development system and update the
>useraccts file (.5 hour)
>4. Have your people test it on the development system
>5. Put in a few minor changes as a result of your testing (if
>necessary) and re-test (1.0-3.0 hours)
>6. Have your people re-test it on the development system (if necessary)
>7. Migrate the code into production and update the useraccts file (.5 hour)
>Bottom line: minimum: 11 hours, maximum: 16 hours
>
>If you decide to go with this, please let me know when you'd like this by.
>Thanks,
>Dave
