OK, a slightly tangential take...

Source code is, in my mind, a record, but a very different kind of monster:
- There are three flavors of each piece of source code: the code, the applications compiled from that code, and the install files created to put that application somewhere.  (Huge quantities of duplicate files)
For RM purposes, code should probably reside on something OTHER than a shared network drive because:
	* The files created as a result of the development effort should be managed and retained as a single unit, because if you purge one wrong thing, the whole set is useless.  
	* A revision to one piece of the set of files represents a change to the version and therefore retention of all the files.
	* Access to these files should be severely restricted, compared to most other content.
	* If these files are intermingled with business records such as contracts, memos, claims, etc.  Retention of those files will become just that more difficult. 
	* None of these files will provide any business value if stored within a document management system, since they would all need to be checked-out in order to function. SharePoint, by default, blocks many of these files from ever being loaded in the first place. 

Hopefully some practical thoughts...

Brian Tuemmler
Director, Gimmal
[log in to unmask]
(925) 253 5689

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]