[125] in iswork
Returned mail: User unknown
daemon@ATHENA.MIT.EDU (Mail Delivery Subsystem)
Fri Oct 13 14:18:22 2000
Message-Id: <4.3.2.7.2.20001013141405.00ba2480@po9.mit.edu>
Date: Fri, 13 Oct 2000 14:20:46 -0400
To: iswork@mit.edu
From: Mail Delivery Subsystem <MAILER-DAEMON@MIT.EDU> (by way of Robert Ferrara <rferrara@mit.edu>)
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
The original message was received at Fri, 13 Oct 2000 11:16:22 -0400 (EDT)
from WEST-NINETYTWO-TWO-SEVENTY-EIGHT.MIT.EDU [18.18.6.23]
----- The following addresses had permanent fatal errors -----
<is-work@mit.edu>
----- Transcript of session follows -----
... while talking to grand-central-station.mit.edu.:
>>> RCPT To:<is-work@mit.edu>
<<< 550 <is-work@mit.edu>... User unknown
550 <is-work@mit.edu>... User unknown
Reporting-MTA: dns; melbourne-city-street.MIT.EDU
Received-From-MTA: DNS; WEST-NINETYTWO-TWO-SEVENTY-EIGHT.MIT.EDU
Arrival-Date: Fri, 13 Oct 2000 11:16:22 -0400 (EDT)
Final-Recipient: RFC822; is-work@mit.edu
Action: failed
Status: 5.1.1
Remote-MTA: DNS; grand-central-station.mit.edu
Diagnostic-Code: SMTP; 550 <is-work@mit.edu>... User unknown
Last-Attempt-Date: Fri, 13 Oct 2000 11:16:23 -0400 (EDT)
Return-Path: <rferrara@mit.edu>
Received: from deena.mit.edu (WEST-NINETYTWO-TWO-SEVENTY-EIGHT.MIT.EDU [18.18.6.23])
by melbourne-city-street.MIT.EDU (8.9.3/8.9.2) with ESMTP id LAA02688;
Fri, 13 Oct 2000 11:16:22 -0400 (EDT)
Message-Id: <4.3.2.7.2.20001013110933.00b731f0@po9.mit.edu>
X-Sender: rferrara@po9.mit.edu (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Fri, 13 Oct 2000 11:18:47 -0400
To: Bil Huxley <huxley@mit.edu>
From: Robert Ferrara <rferrara@mit.edu>
Subject: Re: SAP Data-Archiving Pilot web page
Cc: ssabre@mit.edu, is-work@mit.edu, mbrody@mit.edu
In-Reply-To: <200010131152.HAA00024@melbourne-city-street.MIT.EDU>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Bil,
Good one! Who archives the archivers? You are the first to raise this issue - how long do we keep project documentation - specifically notebooks.
Up to this point, there has been no known (to me) purging of any of this material, nor is any planned. Right now, your material is in the Delivery locker in Athena, which is backed up and pretty well controlled. So we can say that - for the foreseeable future - the notebooks will be available indefinitely.
I'm cc'ing Tim McGovern and Matt Brody, who might have an idea or two on how to properly generalize and institutionalize this retention requirement.
Cheers, Bob
At 07:54 AM 10/13/2000 -0400, Bil Huxley wrote:
>Hi Bob,
>
>As discussed last Friday at SAP-Plan, there is concern for the retention of
>the documentation that we've have (and will) publish on the delivery pages
>for the 'SAP Data-Archiving Pilot' project. I think we can all grin about
>discussing the data-retention and data-archiving of the data-arching
>project notebook ;-) However, that's what I'm writing about. If the
>sponsors and SAP-Plan folks are telling us that our documentation needs to
>be 'beefed up' and will need to be available for some time to come, should
>any external auditors decide to review the process and details of what was
>done; what retention and access is provided for delivery notebooks in
>general? Presumably many projects have such retention needs and nothing
>'special' will need to be done to retain our projects documentation :)
>
>Thanks,
> Bil
