<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="6657" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.socictopen.socict.org/items/show/6657?output=omeka-xml" accessDate="2026-04-20T10:51:34+00:00">
  <fileContainer>
    <file fileId="6657">
      <src>https://www.socictopen.socict.org/files/original/15ff047cf063831166624b64f584e50f.pdf</src>
      <authentication>22d16367f24025537f1d774e4709c706</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="58897">
              <text>Comparative Perturbation-Based Modeling of the SARS-CoV-2 Spike Protein Binding with Host Receptor and Neutralizing Antibodies: Structurally Adaptable Allosteric Communication Hotspots Define Spike Sites Targeted by Global Circulating Mutations.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="58898">
              <text>Gennady M Verkhivker, Steve Agajanian, Deniz Yazar Oztas, Grace Gupta</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="58899">
              <text>In this study, we used an integrative computational approach to examine molecular mechanisms and determine functional signatures underlying the role of functional residues in the SARS-CoV-2 spike protein that are targeted by novel mutational variants and antibody-escaping mutations. Atomistic simulations and functional dynamics analysis are combined with alanine scanning and mutational sensitivity profiling of the SARS-CoV-2 spike protein complexes with the ACE2 host receptor and the REGN-COV2 antibody cocktail(REG10987+REG10933). Using alanine scanning and mutational sensitivity analysis, we have shown that K417, E484, and N501 residues correspond to key interacting centers with a significant degree of structural and energetic plasticity that allow mutants in these positions to afford the improved binding affinity with ACE2. Through perturbation-based network modeling and community analysis of the SARS-CoV-2 spike protein complexes with ACE2, we demonstrate that E406, N439, K417, and N501 residues serve as effector centers of allosteric interactions and anchor major intermolecular communities that mediate long-range communication in the complexes. The results provide support to a model according to which mutational variants and antibody-escaping mutations constrained by the requirements for host receptor binding and preservation of stability may preferentially select structurally plastic and energetically adaptable allosteric centers to differentially modulate collective motions and allosteric interactions in the complexes with the ACE2 enzyme and REGN-COV2 antibody combination. This study suggests that the SARS-CoV-2 spike protein may function as a versatile and functionally adaptable allosteric machine that exploits the plasticity of allosteric regulatory centers to fine-tune response to antibody binding without compromising the activity of the spike protein.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="58900">
              <text>2021</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="58901">
              <text>10.1021/acs.biochem.1c00139</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="58902">
              <text>Biochemistry</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
