Hi Both , Thanks !

Yes they are iRods meta data. But they are printed on screen and I don't want to push them to a file and create more overhead. I was trying something along like this: 

foreach my $re(@results){                            
next if $re =~/^AVUs defined/; 
warn $re; 
my $attribute= $1 if($re =~ /^attribute:\s+(.*)/);                    
+                         
my $value = $1 if($re =~ /^value: (.*)/);                             
+                          |  warn $attribute,$value;

[download]
And I get 
attribute: md5

EVAL_ERROR: Use of uninitialized value $value in warn at Access.pl lin
+e 125.

A problem occurred at /nfs/users/nfs_a/aj6/CGP/Fluidigm/perl/scripts/L
+oadGenotypingResults.pl line 61.

[download]

In reply to Re^3: parsing metadata by Anonymous Monk
in thread parsing metadata by Anonymous Monk

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.