Thanks kcott. I've gone ahead and abstracted htis into a function. Now, I'm going to try to solve it at the level of 'items' instead of at the parent level. 
use strict;
use warnings;

use Data::Rmap qw(:all);
use Data::Dumper;

my $initial_lol = [ note => [ shopping => [ item => 'sample' ] ] ];

#  In $initial_lol, the new child of shopping is shopping_items
my $new_lol = newchild($initial_lol, shopping => shopping_items());

warn Dumper($new_lol);



sub newchild {
  my ($lol, $parent_arrayref_label, $new_child)=@_;

  my ($mapresult) = rmap_array {
 

  if ($_->[0] eq $parent_arrayref_label) {
    $_->[1] = $new_child;
    cut($_);
  } else {
    $_;
  }

  } $lol;

  $mapresult;

}

sub shopping_items {
  my @shopping_items;
  for my $item qw(bread butter beans) {
    push @shopping_items, [ item => $item ];
  }
  \@shopping_items;
}

[download]




The mantra of every experienced web application developer is the same: thou shalt separate business logic from display. Ironically, almost all template engines allow violation of this separation principle, which is the very impetus for HTML template engine development.

-- Terence Parr, "Enforcing Strict Model View Separation in Template Engines"

In reply to Re^2: Data::Rmap to modify an arrayref of arrayrefs by metaperl
in thread Data::Rmap to modify an arrayref of arrayrefs by metaperl

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.