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:
Records Vet <[log in to unmask]>
Date:
Mon, 23 May 2016 08:42:33 -0400
In-Reply-To:
MIME-Version:
1.0
Reply-To:
Records Management Program <[log in to unmask]>
Parts/Attachments:
text/plain (123 lines)
I might mention Bruce Miller's 2012 book on SP 2010 which also mentions a
gap between out of the box SP and DoD compliance levels.  I think Miller
discusses the features of SP 2013 in the book but obviously without
complete knowledge of it at the time.

I have used SP 2010 for some collaboration but not for RIM, and perhaps I'm
either exposing or admitting my deficiencies regarding my all around
computer fluency and capability, but I found it very difficult to use
effectively.  Having said that, sometimes I don't know if at least some of
these difficulties are the result of the particular network and server
implementation; i.e. are there settings or plug-ins that haven't been
implemented? or just the slog of trying to get things done smoothly with
the application as it actually functions?

One of my observations about a lot of software (and I'm sure this has been
heard before) is that there are just too many features and this seems to be
the case for SP.  Good for the user that knows them all AND can use them
effectively but that's not going to be me, at least for the short term, and
since I don't have that many years left in my career, I suppose that means
never.

RV


On Sat, May 14, 2016 at 5:33 PM, Andrew Warland <[log in to unmask]>
wrote:

> Thanks Fred for your response.
>
> Before implementing SharePoint where I work (a large not for profit
> Church-based organisation with almost 8,000 staff) I worked for three years
> in one of our major local government councils (hint - it's the same city I
> live in) implementing their digital recordkeeping strategy using HP TRIM,
> and have worked with that product since 1999, so I know it pretty well.
>
> I'm interested in your comment that my description seems to to confirm that
> SharePoint is not really capable of managing physical records, although I
> do note your qualification (and the organisation that you work for which
> appears to be a government agency).
>
> We use SharePoint lists to manage several thousand boxes and files in both
> onsite and offsite storage. Just last week I was working through data from
> one of our providers to add another 7,500 boxes (and around 13,000 files
> registered) to the lists. I have no difficulty using SharePoint lists to do
> this. It's very easy to define your own metadata and modify it as required.
> I use list views to show me what records are due for disposal and, then
> they are destroyed, can add the approver, retention schedule and date
> destroyed (and whatever other information I need) to the items, including
> in bulk. I can filter and group my list views anyway I want, including to
> show the contents of each box. Aside from the ability to use barcode
> readers (something we don't really need), I do the same with SharePoint
> that I did with TRIM.
>
> As with all things SharePoint, it depends on your business and possibly
> also your compliance requirements. I've always said that if you work in a
> government agency you will probably need add-ons to address the management
> of security classified information. This functionality has always been
> lacking in SharePoint but I noticed (and had confirmed by Microsoft) last
> week that they are starting to roll out a new way in SharePoint Online
> (SPO) to manage what they call 'Low', 'Medium' and 'High' business impact
> records. Microsoft themselves have used this method for a while now to
> classify business information which, alongside data loss prevention (DLP)
> and information rights management (IRM) capability, will help to address
> that at least for businesses.
>
> I'm happy to provide examples of the list metadata and/or form view if
> anyone's interested, and answer any other questions.
>
> Best wishes
>
> Andrew Warland
> Sydney, Australia
>
> On Sat, May 14, 2016 at 10:10 AM, Frederic Grevin <[log in to unmask]> wrote:
>
> > Andrew, thank you for this really detailed description.
> >
> > It does confirm for me that SharePoint is not really capable of managing
> > physical records, at least to the extent that we view that function.
> >
> > We're currently Autonomy Records Manager users, expecting to migrate to
> HP
> > Records Manager (which you may remember as Tower Software's TRIM), as ARM
> > is an "end of life" product.
> >
> > Fortunately, HP RM has a SharePoint "connector" with various approaches
> to
> > manage records in SP. We're looking forward to exploring these. Once we
> get
> > past the migration, that is (migrations are so... INTERESTING).
> >
> > Best regards, and have a great weekend.
> >
> > Fred
> > ------------------------
> > Frederic J. Grevin
> > Vice-President, Records Management
> > New York City Economic Development Corporation
> > [log in to unmask]
> > 212-312-3903
> >
> >
>
> 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]
>



-- 
Sincerely,

The Records Vet

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