Chances are this is really just a vocabulary question...

I'm in the following situation: I've been burdened with a table, keyed on recipient, and report. That key basically defines which user has read access to which reports. OK, so far so good.

The problem comes in when years later, the table has ~16 million records in it, and administration is a nightmare. I need to programmatically divine what groups might be appropriate by looking at which reports are most commonly asssinged to which people (ie: by looking at the report-recipient relationships, make a SWAG at defining a reasonable 'Accounting' group, or maybe 'Sales', etc.). IOW, which groups should I create to efficiently reduce the greatest number of report/recipient relationships?

Coding up the group mechanism isn't so bad. I just need a way to go back and populate the new groups table. (FWIW, I looked into Debian's AutoClass package, and that doesn't seem to be quite what I need, but I don't exactly have a Masters in Math either.)

So, essentially, I believe this is a vocabulary question, or perhaps I'm asking for a 'group identification' algorithm.

Thank you for your time and kind consideration.

In reply to Group Identification by pboin

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.