<?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>02594nam a22002057a 4500</leader>
  <controlfield tag="005">20240116145858.0</controlfield>
  <controlfield tag="008">240116b           ||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">0021-9584</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Wolfe, Amanda L. </subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Generating Publishable Data from Course-Based Undergraduate Research Experiences in Chemistry </subfield>
    <subfield code="b">(Journal Article)</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Washington DC </subfield>
    <subfield code="b">: American Chemical Society </subfield>
    <subfield code="c">, 2023</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">3419&#x2013;3424p.</subfield>
  </datafield>
  <datafield tag="440" ind1=" " ind2=" ">
    <subfield code="a">Journal of Chemical Society </subfield>
    <subfield code="v">, Volume 100: Number 9, September 2023</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: Embedding Course-based Undergraduate Research Experiences (CUREs) into chemistry curricula has become a best practice due to the overwhelming evidence that these experiences deepen students&#x2019; content comprehension, improve students&#x2019; problem-solving skills, and increase retention within the major. For these reasons, faculty are often encouraged to develop CUREs for their courses, which typically take a substantial amount of effort and administrative/financial support. To justify these efforts, one of the most cited benefits of CURE development for faculty specifically is that they can pilot research projects and publish data produced during CUREs in scientific publications. However, there is less evidence in the literature that these benefits commonly occur. Based on direct upper-level, interdisciplinary CURE development experience and a national survey of faculty across institution types, it is clear that translating CURE data into publishable science is quite challenging due to several common barriers. Barriers identified include the need for follow up data that must be generated by either the faculty or a research student, the lack of reproducibility of data generated by novice students, and the lack of faculty time to write the manuscripts. Additionally, institution type (private vs public non-PhD granting; non-PhD granting vs PhD granting), faculty rank, and CURE level (lower vs upper-level courses), among other factors, impacted the likelihood of publication of CURE data. Based on these results and experiences, best practices for maximizing positive outcomes for both students and faculty with regard to CURE design and implementation have been developed.</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">Upper-Division Undergraduate| Curriculum| Interdisciplinary/Multidisciplinary| Laboratory Instruction| Inquiry-Based/Discovery Learning| Undergraduate Research</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="a">Steed, P. Ryan </subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://doi.org/10.1021/acs.jchemed.3c00354</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">2024-01-16</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2024-01-16 00:00:00</subfield>
    <subfield code="w">2024-01-16</subfield>
    <subfield code="y">PER</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">45272</subfield>
    <subfield code="d">45271</subfield>
  </datafield>
</record>
