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
Sender:
Records Management Program <[log in to unmask]>
Date:
Wed, 11 Apr 2007 12:02:25 -0400
Reply-To:
Records Management Program <[log in to unmask]>
Subject:
MIME-Version:
1.0
Content-Transfer-Encoding:
7bit
Content-Type:
text/plain; charset=utf-8
From:
Don Lueders <[log in to unmask]>
Comments:
cc: Nolene Sherman <[log in to unmask]>
Parts/Attachments:
text/plain (51 lines)
Nolene,

Applying retention schedules to MOSS 2007 can be difficult, but things should get easier with the new DoD certified solution coming out soon.  (Testing is next month.)  See Russ Stalters' ECM blog for more details on that: http://betterecm.wordpress.com/.  Read 'Take A Peek Behind The Curtain - SharePoint and DoD 5015.2 Parts 1 & 2'. 

Also read the article Russ wrote in Document magazine called 'Are You Ready for SharePoint 2007' for help with your content type issues.  There's a link to it here: http://betterecm.wordpress.com/2007/02/09/hot-off-the-presses-are-you-ready-for-sharepoint-2007/.  

Hope this helps,
Don

---- Nolene Sherman <[log in to unmask]> wrote: 
> It appears as our IT department is moving forward with MOSS 2007 and are
> building collaboration sites. Luckily they are thinking ahead to those
> shared spaces eventually creating company records and have asked me to
> help them define appropriate content types with an eye on applying
> retention to them. IT has looked at our Retention Schedule but is having
> some difficulty applying it to their SharePoint structure -- I don't
> blame them because I have some difficulty applying it to our paper
> records, so I am working on aligning it better with what folks actually
> do everyday ... it's just not there yet.
>  
> As we really only do one thing -- build houses -- and the vast majority
> of our records can realistically be grouped into "community records," I
> am trying to move more toward the big-bucket approach with the retention
> schedule. I see the content types as possibly being a way to put more
> detail back into the bucket. e.g. Sure all "community records" are kept
> for x-number of years, but exactly what is a particular record ... a
> contract, a warranty item, an escrow item, etc. In my research, I came
> across one reference to a company wanting to be able to have 300+
> content types. I can't imagine that being manageable -- what employee is
> really going to peruse a list of 300 items to chose which one they
> need?!
>  
> So my question is ... how have others defined content types in their RIM
> systems. How are they used? What should I keep in mind when I start my
> list? Where is the tipping points between too few, enough and too many?
> Is my thought process totally screwed up and I have it all wrong -- are
> content types synonymous with record series?
>  
> Nolene
>  
> Nolene Sherman | Director of Records Management | Standard Pacific Homes
> | 949-727-9360 | FAX 949-789-3379 | [log in to unmask]
> <mailto:[log in to unmask]> 
>  
> 
> 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

ATOM RSS1 RSS2