Randy,
"Sharepoint should not be used as an ERM.  It does not have the
appropriate functionality."

Do you think you might be able to amplify your statement? Why not? What
are the limits?   It has been marketed as having retention rule
establishment, workflow, reporting, security, access, audit features,
version control, indexing and other RM program features. 

Thnaks for your help


Stephen Shalagan
Records Manager, HPOPS

ph.  (713) 869-8734
fax. (713) 869-7657 
-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On
Behalf Of Cooper, Randy
Sent: Friday, June 15, 2007 10:23 AM
To: [log in to unmask]
Subject: Re: [RM] Sharepoint...

Sharepoint should not be used as an ERM.  It does not have the
appropriate functionality.

-----Original Message-----
From: Records Management Program [mailto:[log in to unmask]] On
Behalf Of Steve Shalagan
Sent: June 15, 2007 11:22 AM
To: [log in to unmask]
Subject: Sharepoint...

 A quick query....

Are there any public sector agencies (small to mid level 10 - 100+
employees) utilizing Sharepoint as their primary/only records management
system? 

I am interested in knowing if you find it does the basic job of
declaring a record,(version control, metadata, etc..)  storage
(security, access, auditing)  and eventual destruction (reporting) as
well as, worse than or better than a comparable system. 

Also, were you using it OTB (out of the box) or did you have to have it
customized?  Do you use the workflow and collaborative functions and how
well are they managed in the context of your RM program?

I am interested in any and all comments/success/horror stories 

Thanks  

Steve

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

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