<node id="668339">
  <nid>668339</nid>
  <type>news</type>
  <uid>
    <user id="36437"><![CDATA[36437]]></user>
  </uid>
  <created>1688416482</created>
  <changed>1688420008</changed>
  <title><![CDATA[Keynote Speaker Ashok Goel Explores AI’s Impact on Education at Duke’s Emerging Pedagogies Symposium]]></title>
  <body><![CDATA[]]></body>
  <field_subtitle>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_subtitle>
  <field_dateline>
    <item>
      <value>2023-07-03T00:00:00-04:00</value>
      <timezone><![CDATA[America/New_York]]></timezone>
    </item>
  </field_dateline>
  <field_summary_sentence>
    <item>
      <value><![CDATA[AI-ALOE director, Ashok Goel, speaks on the impacts of AI on education and learning.]]></value>
    </item>
  </field_summary_sentence>
  <field_summary>
    <item>
      <value><![CDATA[<p>Duke Learning Innovation recently organized the “Emerging Pedagogies Symposium: Teaching and Learning in the Age of AI”, which featured a keynote address from Ashok Goel. As the director of AI-ALOE and a prominent professor of computer science and human-centered computing at the Georgia Institute of Technology, Goel discussed the far-reaching implications of artificial intelligence for teaching, learning, and educational research.</p>

<p>You can learn more about this exciting event at&nbsp;<a href="https://www.dukechronicle.com/article/2023/05/duke-university-duke-learning-innovation-emerging-pedagogies-symposium-keynote-speaker-artificial-intelligence-chatgpt" rel="noopener" target="_new">https://www.dukechronicle.com/article/2023/05/duke-university-duke-learning-innovation-emerging-pedagogies-symposium-keynote-speaker-artificial-intelligence-chatgpt</a>.</p>

<p>You can also watch the video of Ashok Goel’s keynote address at the following link:&nbsp;<a href="https://duke.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=2f9ab6c7-b891-4df8-abb6-afea01122d0a" rel="noopener" target="_new">https://duke.hosted.panopto.com/Panopto/Pages/Viewer.aspx?id=2f9ab6c7-b891-4df8-abb6-afea01122d0a</a>.</p>
]]></value>
    </item>
  </field_summary>
  <field_media>
      </field_media>
  <field_contact_email>
    <item>
      <email><![CDATA[]]></email>
    </item>
  </field_contact_email>
  <field_location>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_location>
  <field_contact>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_contact>
  <field_sidebar>
    <item>
      <value><![CDATA[]]></value>
    </item>
  </field_sidebar>
  <field_boilerplate>
    <item>
      <nid><![CDATA[]]></nid>
    </item>
  </field_boilerplate>
  <!--  TO DO: correct to not conflate categories and news room topics  -->
  <!--  Disquisition: it's funny how I write these TODOs and then never
         revisit them. It's as though the act of writing the thing down frees me
         from the responsibility to actually solve the problem. But what can I
         say? There are more problems than there's time to solve.  -->
  <links_related> </links_related>
  <files> </files>
  <og_groups>
          <item>612072</item>
      </og_groups>
  <og_groups_both>
          <item>
        <![CDATA[Education]]>
      </item>
          <item>
        <![CDATA[Special Events and Guest Speakers]]>
      </item>
      </og_groups_both>
  <field_categories>
          <item>
        <tid>42911</tid>
        <value><![CDATA[Education]]></value>
      </item>
          <item>
        <tid>133</tid>
        <value><![CDATA[Special Events and Guest Speakers]]></value>
      </item>
      </field_categories>
  <core_research_areas>
          <term tid="39501"><![CDATA[People and Technology]]></term>
      </core_research_areas>
  <field_news_room_topics>
      </field_news_room_topics>
  <links_related>
      </links_related>
  <files>
      </files>
  <og_groups>
          <item>612072</item>
      </og_groups>
  <og_groups_both>
          <item><![CDATA[Global Leadership]]></item>
      </og_groups_both>
  <field_keywords>
      </field_keywords>
  <field_userdata>
      <![CDATA[]]>
  </field_userdata>
</node>
