Text::xSV was built for exactly this kind of situation. (Why don't people use it more often?!?) 
use Text::xSV;

my $parser = Text::xSV->new;
$parser->open_file( $datafile );

my @headers = $parser->read_header;
shift @headers; # Remove the # field.
my $user_header = shift @headers;

my $data;
while ( $parser->get_row ) {
    my $user = $parser->extract( $user_header );
    $data->{ $user }{ @headers } = [ $parser->extract( @headers ) ];
}

[download]

Update: Obviously, use tilly's corrections to my suggestion as he wrote the module in question. Plus, he's right. :-)

My criteria for good software:
  1. Does it work?
  2. Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: Parsing CSV into a hash by dragonchild
in thread Parsing CSV into a hash by McDarren

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.