RECMGMT-L Archives

Records Management

RECMGMT-L@LISTSERV.IGGURU.US

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

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

Print Reply
Subject:
From:
Christian Meinke <[log in to unmask]>
Reply To:
Records Management Program <[log in to unmask]>
Date:
Tue, 1 Jul 2008 11:38:54 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (53 lines)
A wiki is just a tool like any other, so retention is going to based on
content and how the wiki is used. The nice thing about wikis is they can
preserve the editorial process and make prior versions available - of
course that can be a potential liability as well. Much like web pages,
you'll have to assess when the information needs to be captured and
preserved as a record, or if it ever becomes a record (i.e. maybe it's used
to generate some final, blessed document that is the "official" record). So
really the question is how is it being used, are business decisions being
made based on this content, and what laws, regulations, or business
requirements will be impacted by those decisions.

                           Christian Meinke, CRM
                        Southern California Edison
                       Enterprise Resource Planning
                            Operations Support
                       Document & Records Management
                         (626) 543-7260/PAX 39260
                           Mobile (818) 414-9515
                         [log in to unmask]


Records Management Program <[log in to unmask]> wrote on 07/01/2008
11:23:49 AM:

> Internal wiki's for organizations are getting very popular.  The good
> news is that you can share a lot of information very quickly.  The bad
> news is that, like the internet, not everything is accurate or
> appropriate for publication and anything can be changed on the fly.
>
> Anybody have any experience doing retention scheduling for wiki's?  Much
> like blogs, it is impossible to classify any of it as a record until
> after you know what the content is...so a one size fits all policy would
> be impossible to defend.  I was thinking that one strategy might be to
> ask the initial creator of the web page to classify the posting in
> advance by selecting a Record Category that could have some business
> rules attached.
>
> Can anybody think of a different approach?
>
>
>
> 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]

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