RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Content-Type:
text/plain; charset=UTF-8
Sender:
Records Management Program <[log in to unmask]>
Subject:
From:
mwhaider <[log in to unmask]>
Date:
Thu, 29 Dec 2016 17:31:54 -0500
In-Reply-To:
MIME-Version:
1.0
Reply-To:
Records Management Program <[log in to unmask]>
Parts/Attachments:
text/plain (27 lines)
It seems to me that the easy answer is to NOT record the information sent
or received through ECHO.  Once you record it you must treat it as a
"record" and set policies for managing that information.  Unfortunately the
user may not want it recorded but ECHO may automatically record it
regardless of the users request and this is where the problem lies - in the
hands of the "providers".  Why do they want to record it?  What is the
purpose?  Does Google charge by the number of answers?  My opinion - if
Google records it must be discoverable!  So choose your poison.

We constantly talk about the volume of data accumulating and this is why -
it seems to be easier to record than let the "noise" disappear.  I suppose
that every Google search I've made is probably stored by Google in the
cloud. When these clouds break we will have a global flood:)


Mary

Mary W. Haider, MBA, CRM
Records & Information Manager and Consultant
[log in to unmask]
865-983-1371

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]

ATOM RSS1 RSS2