The license should be read closely.  It may not discuss retention per se but
you should get a good idea of what the retention requirement might be. If
you cannot discern a retention requirement after reading the license, then
I'd recommend linking the retention of the software configurations and
source code to the retention requirement of the license itself.  Example:
Destroy 2 years after license expiration/termination.

Hope this helps.

Tony Laino, CRM, CDIA
Manager, Consulting Services
TAB Professional Services
1-800-243-6547 x.264
www.tab.com


-----Original Message-----
From: Richard D Reilly [mailto:[log in to unmask]]
Sent: Monday, March 21, 2005 11:42 AM
To: [log in to unmask]
Subject: Is there Retention for software configurations and source code?


Anyone have an informed opinion about retention for software configurations
and/or source code?  My IT group asked me this question.

Regards,

Richard Reilly
Information Analyst
Information Asset Management (IAM)

Seagate Technology LLC
4585 Scotts Valley Drive
Building 15, MailStop: SV15A1
Scotts Valley, CA 95066
Fax: 831-438-7132
Phone: 831-439-5775

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance