Content Metrics without ReportCenter

croot

Hi -

We are currently using TeamSite to manage content for a large scale web site. We have a request to create a monthly report on the number and size of items in TeamSite rolled up by branch & author.

I know this is a little vague, but does anyone know how to go about this without using ReportCenter? We do not have a license for this product and I don't believe there are any plans to purchase a license.

Thanks in advance,
Chris

Adam Stoller

Hi - We are currently using TeamSite to manage content for a large scale web site. We have a request to create a monthly report on the number and size of items in TeamSite rolled up by branch & author. I know this is a little vague, but does anyone know how to go about this without using ReportCenter? We do not have a license for this product and I don't believe there are any plans to purchase a license. Thanks in advance, Chris

SMOP - a Small Matter Of Programming - i.e. write a script that traverses your branches and retrieves the information storing it in either a nested-hash or two hashes (not sure if you meant one list that is organized by-author-by-branch, or two lists one organized by-branch and the other by-author).

nested-hash:

$hash{$branch}{$author} = ...

two hashes:

$branches{$branch} = ...; $authors{$author} = ...;

The size will be easy to get (simple stat call).
The date of the files last change is also possibly through the same stat call (assuming you only want to record information about files changed within that month - or the month prior).

The author may be a bit more difficult if you really mean someone in the Author role. Since Author's do not have the ability to actually submit files to STAGING, the submit would have happened with someone else's userid attached - meaning that the stat will not give you the proper UID, nor (I believe) will iwrlog provide the correct information either. If you really need Author information, you may have to adjust your submit process to set the actual Author's name as an EA on the file prior to performing the submit, and then you'll have to run iwextattr on each file to extract that information (a major performance hit).

If your "authors" are logged into TeamSite with the role of Editor or higher - and - if your submit process uses them as the owner of the submittask - then the stat will give you the UID - and you can either use that, or write more code to resolve the UID into a userid or even perhaps a full name.