<?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>02274nam a22001937a 4500</leader>
  <controlfield tag="005">20240409104750.0</controlfield>
  <controlfield tag="008">240409b        |||||||| |||| 00| 0 eng d</controlfield>
  <datafield tag="022" ind1=" " ind2=" ">
    <subfield code="a">0002-7685  </subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="a">Morar, Vikash </subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">Simplifying Biology Vocabulary via Morphology   </subfield>
    <subfield code="b">(Journal Article) </subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">United States </subfield>
    <subfield code="b">:National Association of Biology Teachers (NABT) </subfield>
    <subfield code="c">,2023</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">464&#x2013;467p.</subfield>
  </datafield>
  <datafield tag="440" ind1=" " ind2=" ">
    <subfield code="a">American Biology Teacher </subfield>
    <subfield code="v">Volume 85: Issue 8, October 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: In all fields of biology, understanding technical terminology is a challenge for students. In many cases, this may distract them from focusing on fundamental processes and concepts. Across the biology subfields, much of the vernacular shares similar etymology and morphology. However, students lack the exposure necessary to identify these key features, which often explain the meaning of terms without requiring any context at all. Therefore, instead of encouraging students to memorize many terms independently, it could be more beneficial to show them how words are constructed. Here, I propose an activity designed to help students recognize terms that may be connected, understand how vocabulary is often constructed to reflect its idea, and develop comfortability using these terms themselves in discussions. Through a guided group activity, students will have a chance to break down terms they have previously encountered and to draw connections between novel words. If students are capable of relating words to each other before even knowing what they mean, they may learn more effectively. Without being intimidated by enigmatic vocabulary, they can focus on broader concepts. In addition, when students understand how biological terminology is constructed, they may even dissect new words without needing the context surrounding them. This activity is applicable to courses in any specialty of biology, as various molecules, tissues, and processes follow general naming principles.

</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2=" ">
    <subfield code="a">biology| morphology| terminology| vocabulary| etymology| anatomy| physiology| biochemistry| metabolism</subfield>
  </datafield>
  <datafield tag="856" ind1=" " ind2=" ">
    <subfield code="u">https://doi.org/10.1525/abt.2023.85.8.464</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-04-09</subfield>
    <subfield code="l">0</subfield>
    <subfield code="r">2024-04-09 10:44:58</subfield>
    <subfield code="w">2024-04-09</subfield>
    <subfield code="y">PER</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="c">45684</subfield>
    <subfield code="d">45683</subfield>
  </datafield>
</record>
