<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>00991pab a2200133 454500</leader>
  <controlfield tag="008">180718b   xxu||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Kramer Fred A.</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Using the classics to expand public administrative thought: an exhortory note</subfield>
  </datafield>
  <datafield tag="362" ind1=" " ind2=" ">
    <subfield code="a">22(4), Dec 1992, p.301-06</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Public administrators - both practitioners and academics need to develop critical thinking skill. The mental exercise required to assess the validity of myths and metaphors can help develop this capacity to think beyond boundarics of problems. Drawing from the work of diverse authors such as Perey Bysshe Shelley, the early nineteenth. century port, and more current works of the philosopher Neeson Goodman, this article shows how the conflict inherent in metaphors can be an exercise in creativity. Examples particluary relevant to public administration are drawn from Homer's Odyssey.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Public Administration</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="a">American Review of Public Administration</subfield>
  </datafield>
  <datafield tag="909" ind1=" " ind2=" ">
    <subfield code="a">27550</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">27550</subfield>
    <subfield code="d">27550</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">0</subfield>
    <subfield code="a">IIPA</subfield>
    <subfield code="b">IIPA</subfield>
    <subfield code="d">2018-07-19</subfield>
    <subfield code="p">AR27652</subfield>
    <subfield code="r">2018-07-19</subfield>
    <subfield code="w">2018-07-19</subfield>
    <subfield code="y">AR</subfield>
  </datafield>
</record>
