[2376] in Enterprise Print Delivery Team
Re: Interesting thought/conumdrum around FSS1
daemon@ATHENA.MIT.EDU (Lynne E. Durland)
Tue Mar 5 13:15:48 2002
Message-Id: <5.0.2.1.2.20020305131024.03dcad38@hesiod>
Date: Tue, 05 Mar 2002 13:18:19 -0500
To: David F Lambert <LAMBERT@MITVMA.MIT.EDU>,
"Lynne E. Durland" <durland@MIT.EDU>,
Enterprise Printing Delivery Project Team <printdel@MIT.EDU>
From: "Lynne E. Durland" <durland@MIT.EDU>
In-Reply-To: <200203042026.PAA23115@fort-point-station.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Hey Gang,
My questions yesterday were partly founded in a grey area, I missed a
decision, but Dave's point is also valid. We figured out that we were sort
of coming at the same issue from different angles. So just to make we are
all on the same page:
A couple of weeks ago we agreed to have Rocklyn request a software change
to allow us to have a "blanket" co and delivery address for a logical
destination, primarily a restricted "queue" (logical destination).
This also makes sense for the fss1 queue which I honestly can't remember if
it is restricted or not, but is hidden, used by FSS to develop new stuff
for glmp, and is not in our 'space', so it also makes sense to apply this
new code change to this logical destination, so that users in FSS won't
have to go the web pages etc.
The activity to the logical destinations with the code applied would still
be in the accounting report, but would not require the users to go the web
page or risk rejected output.
Right?
Lynne
At 03:23 PM 3/4/2002, David F Lambert wrote:
>Lynne,
>
>Independent of where it prints or DOST's delivery involvement, yes,
>I do think we care. What if someone pumps 1M pages daily to FSS1?
>Would we want to know the CO for usage tracking? Me thinks so.
>And, I don't think we want to make more exceptions (this printer/queue
>requires the CO but not the delivery address).
>
>-Dave
>
>On Mon, 04 Mar 2002 13:51:25 -0500 you said:
> >Hey gang,
> >
> >One of the people with the missing information was printing to FSS1. I
> >copied the information from Rocklyn's testing over the weekend and edited
> >it appropriately, then stopped and read through the mail before sending
> >it. We have absolutely no control over the delivery of the out put, this
> >is the small printer in W92.
> >
> >DOST is not providing the paper, toner or other supplies for this printer.
> >
> >Do we really need the information and or to include this printer in the
> >accounting information?
> >
> >I will add a little more wording to the mail before I send it to Barry, but
> >thought I would also send mail to the team for thought. Anything I think
> >should be done as part of the follow-on/production work.
> >
> >I am back!!!!
> >
> >Lynne
> >
> >Lynne E. Durland
> >Information Systems
> >Database Services
> >W91-109
> >O: 617-258-5857
> >C: 617-293-8091
> >H: KB1FEM
> >
> >"When one door of happiness closes, another opens; but often we look so
> >long at the closed door that we do not see the one which has been opened
> >for us."
> >
> > --Helen Keller
> >
Lynne E. Durland
Information Systems
Database Services
W91-109
O: 617-258-5857
C: 617-293-8091
H: KB1FEM
"When one door of happiness closes, another opens; but often we look so
long at the closed door that we do not see the one which has been opened
for us."
--Helen Keller
