<?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>02227nam a22002657a 4500</leader>
  <controlfield tag="005">20231030112046.0</controlfield>
  <controlfield tag="008">231030b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">0021-9584</subfield>
  </datafield>
  <datafield tag="037" ind1=" " ind2=" ">
    <subfield code="b">RIEBPL Library</subfield>
  </datafield>
  <datafield tag="082" ind1=" " ind2=" ">
    <subfield code="a">540.7</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a"> Ryan L. Stowe and Brian J. Esselman</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a"> The Picture Is Not the Point: Toward Using Representations as Models for Making Sense of Phenomena</subfield>
    <subfield code="b">(Journal Article) </subfield>
    <subfield code="c"> </subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Washington, United States</subfield>
    <subfield code="b">:American Chemical Society</subfield>
    <subfield code="c">,January 10, 2023</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a"> 15-21 p.</subfield>
  </datafield>
  <datafield tag="490" ind1=" " ind2=" ">
    <subfield code="a">American Chemical Society, Volume 100, Issue 1</subfield>
  </datafield>
  <datafield tag="505" ind1=" " ind2=" ">
    <subfield code="a">***______{For Hard Copy, Please visit Library.}________***</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">Abstract-

 Organic chemistry students are routinely bombarded with an array of specialized representations (e.g., electron-pushing mechanisms, Newman projections, chair conformations). For practicing chemists, the purpose of representing aspects of a system is to enable prediction or explanation of phenomena. For students, the purpose of drawing and translating between representations is often much less clear. Commonly, &#x201C;draw the thing&#x201D; is treated as the end-goal of instruction and assessment. We agree with a chorus of science education scholars that learning science should not be materially different from doing science. With respect to representations, that means that students should use representations for the purpose of attending to and visualizing the components of a system salient to a productive explanation or prediction. Here, we encourage the community to reflect on how and why representations are integrated into their organic chemistry courses. Are drawing and translating between representations treated as ends unto themselves, or are they part of an ensemble of activities directed at understanding why phenomena unfold as they do? We are hopeful that the conversations this commentary provokes help us move toward using representations as models for sensemaking.




</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Amides,</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Energy,</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Organic chemistry,</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Students,</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Testing and assessment</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u"> https://pubs.acs.org/doi/epdf/10.1021/acs.jchemed.2c00464</subfield>
  </datafield>
  <datafield tag="942" ind1=" " ind2=" ">
    <subfield code="c">PER</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">RIEBPL</subfield>
    <subfield code="b">RIEBPL</subfield>
    <subfield code="d">2023-10-30</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">540.7</subfield>
    <subfield code="r">2023-10-30 00:00:00</subfield>
    <subfield code="w">2023-10-30</subfield>
    <subfield code="y">PER</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">44644</subfield>
    <subfield code="d">44643</subfield>
  </datafield>
</record>
