You didn't tell us, if your data is nested or just flat.

Perl doesn't allow to change keys in place, you either need to copy to new a hash, or delete and recreate every single key to be transformed. If the hashes are nested you need to walk thru the tree.

If I were you I would just check if the JSON string has a pretty format which allows a simple regex to translate keys only.

update

proof of concept:

  DB<100> use JSON

  DB<101> $hoH = {
             nested => { crossReference => 42, incidentAbstract => "st
+ring" },
           }

  DB<102> $str = (new JSON)->pretty(1)->encode($hoH)
{
   "nested" : {
      "incidentAbstract" : "string",
      "crossReference" : "42"
   }
}

  DB<103> %translate= ( 
                      'crossReference' => 'cross_reference' ,
                      "incidentAbstract" => 'abstract',
                      )

  DB<104> $or_keys = join "|", keys %translate
 => "incidentAbstract|crossReference"

  DB<105> $str =~ s/^(\s+")($or_keys)("\s+:)/$1$translate{$2}$3/gm
 => 2

  DB<106> $str
{
   "nested" : {
      "abstract" : "string",
      "cross_reference" : "42"
   }
}

[download]

of course this can also be done with Data::Dumper ...

Cheers Rolf

( addicted to the Perl Programming Language)

In reply to Re: Translate or morph hash keys to different names by LanX
in thread Translate or morph hash keys to different names by rmcgowan

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.