Document "aging" report....anyone?

Has anyone created an "aging" report to give visibilty to Livelink documents/files that have not been download in [90, 120, etc.] days? We're wanting to get a list of inactive documents - ones that are taking up valuable disk space but not being used.Any info is welcome. Thanks in advance.Regards,-Jeff Gfroerer NIKE, Inc. jeff.gfroerer@nike.com

Find more posts tagged with

Comments

eLink User

Message from Sean M Alderman via eLinkThat's an interesting idea, potentially challenging, and probably veryuseful to many admins. We're about to embark on the road to an externalstorage migration... for which this could potentially be a usefulreport.I'll take a look at the options available for conditional selection inSQL and see if I can't put something together. A more flexible methodmight be to use perl DBI. I have this setup on our system (solaris) butAFAIK it can be installed to work with perl on NT as well.Is that something you could handle?eLink Discussion: Livelink LiveReports Discussion wrote:> > Document "aging" report....anyone?> Posted by NikeUSA on 09/26/2001 02:08 PM> > Has anyone created an "aging" report to give visibilty to Livelink documents/files that have not been download in [90, 120, etc.] days?> > We're wanting to get a list of inactive documents - ones that are taking up valuable disk space but not being used.> > Any info is welcome. Thanks in advance.> Regards,> -Jeff Gfroerer> NIKE, Inc.> jeff.gfroerer@nike.com> > [To reply to this thread, use your normal e-mail reply function.]> > ============================================================> > Discussion: Livelink LiveReports Discussion> https://knowledge.opentext.com/knowledge/livelink.exe?func=ll&objId=2249677&objAction=view> > Livelink Server:> https://knowledge.opentext.com/knowledge/livelink.exe-- Sean M. AldermanITRACK Systems AnalystPACE/NCI - NASA Glenn Research Center(216) 433-2795

Julie_Witmer_(jwitmer_-_(deleted))

A couple of thoughts:As much as the old stuff is an issue, even bigger (for us) is large files that have many versions.I run reports that list largest and most versioned docs, then contact the owner to see if they can be pruned. 10 copies of an 18 meg file saves more space then 100 copies of 6 month old 10k docs, goes the rationale.Also, you can use the Event Audits to view content that has been viewed. If you could review that SQL, probably not too difficult to get the inverse -- all of the objects that are documents that haven't got fetch, download events attached that are a certain size.