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]