<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" 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/browse/page/227?output=omeka-xml&amp;page=228&amp;sort_field=added" accessDate="2026-04-22T05:29:50+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>227</pageNumber>
      <perPage>10</perPage>
      <totalResults>20655</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="2269" public="1" featured="0">
    <fileContainer>
      <file fileId="2269">
        <src>https://www.socictopen.socict.org/files/original/ec786d2e12c9b6a27928ed1d65e6f9d2.pdf</src>
        <authentication>e1550892a961aaf2975b691cbb50775a</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="21809">
                <text>Oral Delivery of Probiotics Expressing Dendritic Cell-Targeting Peptide Fused with Porcine Epidemic Diarrhea Virus COE Antigen: A Promising Vaccine Strategy against PEDV</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21810">
                <text>Xiaona Wang, Li Wang, Xuewei Huang, Sunting Ma, Meiling Yu, Wen Shi, Xinyuan Qiao, Lijie Tang, Yigang Xu, Yijing Li</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21811">
                <text>Porcine epidemic diarrhea virus (PEDV), an enteric coronavirus, is the causative agent of porcine epidemic diarrhea (PED) that damages intestinal epithelial cells and results in severe diarrhea and dehydration in neonatal suckling pigs with up to 100% mortality. The oral vaccine route is reported as a promising approach for inducing protective immunity against PEDV invasion. Furthermore, dendritic cells (DCs), professional antigen-presenting cells, link humoral and cellular immune responses for homeostasis of the intestinal immune environment. In this study, in order to explore an efficient oral vaccine against PEDV infection, a mucosal DC-targeting oral vaccine was developed using Lactobacillus casei to deliver the DC-targeting peptide (DCpep) fused with the PEDV core neutralizing epitope (COE) antigen. This probiotic vaccine could efficiently elicit secretory immunoglobulin A (SIgA)-based mucosal and immunoglobulin G (IgG)-based humoral immune responses via oral vaccination in vivo. Significant differences (p &amp;lt; 0.05) in the immune response levels were observed between probiotics expressing the COE-DCpep fusion protein and COE antigen alone, suggesting better immune efficiency of the probiotics vaccine expressing the DC-targeting peptide fused with PEDV COE antigen. This mucosal DC-targeting oral vaccine delivery effectively enhances vaccine antigen delivery efficiency, providing a useful strategy to induce efficient immune responses against PEDV infection.</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="21812">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21813">
                <text>Lactobacillus, PEDV COE antigen, dendritic cell-targeting peptide, Oral Vaccine</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="21814">
                <text>DOI: 10.3390/v9110312</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="21815">
                <text>Viruses</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21816">
                <text>MDPI AG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21817">
                <text>Microbiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21818">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2270" public="1" featured="0">
    <fileContainer>
      <file fileId="2270">
        <src>https://www.socictopen.socict.org/files/original/c02ce2a26e5c9872f36d3e78a7296639.pdf</src>
        <authentication>bd6e19ce300ef761877edfeafe1ecfbe</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="21819">
                <text>A Review of Recent Advances towards the Development of (Quantitative) Structure-Activity Relationships for Metallic Nanomaterials</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21820">
                <text>Guang-Chao-Chen, Martina G. Vijver, Yinlong Xiao, Willie J. G. M. Peijnenburg</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21821">
                <text>Gathering required information in a fast and inexpensive way is essential for assessing the risks of engineered nanomaterials (ENMs). The extension of conventional (quantitative) structure-activity relationships ((Q)SARs) approach to nanotoxicology, i.e., nano-(Q)SARs, is a possible solution. The preliminary attempts of correlating ENMs’ characteristics to the biological effects elicited by ENMs highlighted the potential applicability of (Q)SARs in the nanotoxicity field. This review discusses the current knowledge on the development of nano-(Q)SARs for metallic ENMs, on the aspects of data sources, reported nano-(Q)SARs, and mechanistic interpretation. An outlook is given on the further development of this frontier. As concluded, the used experimental data mainly concern the uptake of ENMs by different cell lines and the toxicity of ENMs to cells lines and Escherichia coli. The widely applied techniques of deriving models are linear and non-linear regressions, support vector machine, artificial neural network, k-nearest neighbors, etc. Concluded from the descriptors, surface properties of ENMs are seen as vital for the cellular uptake of ENMs; the capability of releasing ions and surface redox properties of ENMs are of importance for evaluating nanotoxicity. This review aims to present key advances in relevant nano-modeling studies and stimulate future research efforts in this quickly developing field of research.</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="21822">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21823">
                <text>nano-(Q)SARs, metallic nanomaterials, Risk assessment, cellular uptake, toxicity</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="21824">
                <text>DOI: 10.3390/ma10091013</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="21825">
                <text>Materials</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21826">
                <text>MDPI AG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21827">
                <text>Technology, Engineering (General). Civil engineering (General), Electrical engineering. Electronics. Nuclear engineering, Microscopy, Descriptive and experimental mechanics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21828">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2271" public="1" featured="0">
    <fileContainer>
      <file fileId="2271">
        <src>https://www.socictopen.socict.org/files/original/d6fc396ee9dfc88497e55655f3a751c6.pdf</src>
        <authentication>31dd58905aebb06e8d4f8ceb9c3eaac9</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="21829">
                <text>Recombinant Chimeric Transmissible Gastroenteritis Virus (TGEV)—Porcine Epidemic Diarrhea Virus (PEDV) Virus Provides Protection against Virulent PEDV</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21830">
                <text>Alejandro Pascual-Iglesias, Carlos M. Sanchez, Zoltan Penzes, Isabel Sola, Luis Enjuanes, Sonia Zuñiga</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21831">
                <text>Porcine epidemic diarrhea virus (PEDV) is an enteric coronavirus causing high morbidity and mortality in porcine herds worldwide. Although both inactivated and live attenuated vaccines have been extensively used, the emergence of highly virulent strains and the recurrent outbreaks even in vaccinated farms highlight the need of effective vaccines. Engineering of genetically defined live attenuated vaccines is a rational approach for novel vaccine development. In this line, we engineered an attenuated virus based on the transmissible gastroenteritis virus (TGEV) genome, expressing a chimeric spike protein from a virulent United States (US) PEDV strain. This virus (rTGEV-RS-SPEDV) was attenuated in highly-sensitive five-day-old piglets, as infected animals did not lose weight and none of them died. In addition, the virus caused very minor tissue damage compared with a virulent virus. The rTGEV-RS-SPEDV vaccine candidate was also attenuated in three-week-old animals that were used to evaluate the protection conferred by this virus, compared with the protection induced by infection with a virulent PEDV US strain (PEDV-NVSL). The rTGEV-RS-SPEDV virus protected against challenge with a virulent PEDV strain, reducing challenge virus titers in jejunum and leading to undetectable challenge virus RNA levels in feces. The rTGEV-RS-SPEDV virus induced a humoral immune response specific for PEDV, including neutralizing antibodies. Altogether, the data indicated that rTGEV-RS-SPEDV is a promising vaccine candidate against virulent PEDV infection.</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="21832">
                <text>2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21833">
                <text>PEDV, modified-live vaccine, attenuated virus, protection, enteric virus</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="21834">
                <text>DOI: 10.3390/v11080682</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="21835">
                <text>Viruses</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21836">
                <text>MDPI AG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21837">
                <text>Microbiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21838">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2272" public="1" featured="0">
    <fileContainer>
      <file fileId="2272">
        <src>https://www.socictopen.socict.org/files/original/86776dad79666da20a57e72f11e050f4.pdf</src>
        <authentication>2e0fc4e85d1f44205ca04a025ed866f5</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="21839">
                <text>Physicochemical property distributions for accurate and rapid pairwise protein homology detection</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21840">
                <text>Oehmen Christopher S, Ratuiste Kyle G, Webb-Robertson Bobbie-Jo M</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21841">
                <text>Abstract Background The challenge of remote homology detection is that many evolutionarily related sequences have very little similarity at the amino acid level. Kernel-based discriminative methods, such as support vector machines (SVMs), that use vector representations of sequences derived from sequence properties have been shown to have superior accuracy when compared to traditional approaches for the task of remote homology detection. Results We introduce a new method for feature vector representation based on the physicochemical properties of the primary protein sequence. A distribution of physicochemical property scores are assembled from 4-mers of the sequence and normalized based on the null distribution of the property over all possible 4-mers. With this approach there is little computational cost associated with the transformation of the protein into feature space, and overall performance in terms of remote homology detection is comparable with current state-of-the-art methods. We demonstrate that the features can be used for the task of pairwise remote homology detection with improved accuracy versus sequence-based methods such as BLAST and other feature-based methods of similar computational cost. Conclusions A protein feature method based on physicochemical properties is a viable approach for extracting features in a computationally inexpensive manner while retaining the sensitivity of SVM protein homology detection. Furthermore, identifying features that can be used for generic pairwise homology detection in lieu of family-based homology detection is important for applications such as large database searches and comparative genomics.</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="21842">
                <text>2010</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="21843">
                <text>DOI: 10.1186/1471-2105-11-145</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="21844">
                <text>BMC Bioinformatics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21845">
                <text>BMC</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21846">
                <text>Biology (General), Computer applications to medicine. Medical informatics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21847">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2273" public="1" featured="0">
    <fileContainer>
      <file fileId="2273">
        <src>https://www.socictopen.socict.org/files/original/321010d38580f58cfb998fd874fa3872.pdf</src>
        <authentication>8582a83c6a015a989cadc7f2be733b9c</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="21848">
                <text>Hospice utilization during the SARS outbreak in Taiwan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21849">
                <text>Lin Ming-Hwai, Chen Tzeng-Ji, Chou Li-Fang, Hwang Shinn-Jang</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21850">
                <text>Abstract Background The severe acute respiratory syndrome (SARS) epidemic threw the world into turmoil during the first half of 2003. Many subsequent papers have addressed its impact on health service utilization, but few have considered palliative (hospice) care. The aim of the present study was to describe changes in hospice inpatient utilization during and after the SARS epidemic in 2003 in Taiwan. Methods The data sources were the complete datasets of inpatient admissions during 2002 and 2003 from the National Health Insurance Research Database. Before-and-after comparisons of daily and monthly utilizations were made. Hospice analyses were limited to those wards that offered inpatient services throughout these two years. The comparisons were extended to total hospital bed utilization and to patients who were still admitted to hospice wards during the peak period of the SARS epidemic. Results Only 15 hospice wards operated throughout the whole of 2002 and 2003. In 2003, hospice utilization began to decrease in the middle of April, reached a minimum on 25 May, and gradually recovered to the level of the previous November. Hospices showed a more marked reduction in utilization than all hospital beds (e.g. -52.5% vs. -19.9% in May 2003) and a slower recovery with a three-month lag. In total, 566 patients were admitted to hospice wards in May/June 2003, in contrast to 818 in May/June 2002. Gender, age and diagnosis distributions did not differ. Conclusion Hospice inpatient utilization in Taiwan was indeed more sensitive to the emerging epidemic than general inpatient utilization. A well-balanced network with seamless continuity of care should be ensured.</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="21851">
                <text>2006</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="21852">
                <text>DOI: 10.1186/1472-6963-6-94</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="21853">
                <text>BMC Health Services Research</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21854">
                <text>BMC</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21855">
                <text>Public aspects of medicine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21856">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2274" public="1" featured="0">
    <fileContainer>
      <file fileId="2274">
        <src>https://www.socictopen.socict.org/files/original/7aaf4a2957082e2c33dbe913e641b94e.pdf</src>
        <authentication>847a777f9f085f6eb8fbe0b6f46547ba</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="21857">
                <text>Sea Cucumber Glycosides: Chemical Structures, Producing Species and Important Biological Properties</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21858">
                <text>Muhammad Abdul Mojid Mondol, Hee Jae Shin, M Aminur Rahman, Mohamad Tofazzal Islam</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21859">
                <text>Sea cucumbers belonging to echinoderm are traditionally used as tonic food in China and other Asian countries. They produce abundant biologically active triterpene glycosides. More than 300 triterpene glycosides have been isolated and characterized from various species of sea cucumbers, which are classified as holostane and nonholostane depending on the presence or absence of a specific structural unit γ(18,20)-lactone in the aglycone. Triterpene glycosides contain a carbohydrate chain up to six monosaccharide units mainly consisting of d-xylose, 3-O-methy-d-xylose, d-glucose, 3-O-methyl-d-glucose, and d-quinovose. Cytotoxicity is the common biological property of triterpene glycosides isolated from sea cucumbers. Besides cytotoxicity, triterpene glycosides also exhibit antifungal, antiviral and hemolytic activities. This review updates and summarizes our understanding on diverse chemical structures of triterpene glycosides from various species of sea cucumbers and their important biological activities. Mechanisms of action and structural–activity relationships (SARs) of sea cucumber glycosides are also discussed briefly.</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="21860">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21861">
                <text>holostane, nonholostane, Cucumarioside, cytotoxic, antifungal, Glycosides</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="21862">
                <text>DOI: 10.3390/md15100317</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="21863">
                <text>Marine Drugs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21864">
                <text>MDPI AG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21865">
                <text>Biology (General)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21866">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2275" public="1" featured="0">
    <fileContainer>
      <file fileId="2275">
        <src>https://www.socictopen.socict.org/files/original/aa3c3d8119241ce7519f0c1d29a4cef0.pdf</src>
        <authentication>a07dded4ea6cf3ce2999959ef65d7e5f</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="21867">
                <text>Deep-learning: investigating deep neural networks hyper-parameters and comparison of performance to shallow methods for modeling bioactivity data</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21868">
                <text>Alexios Koutsoukas, Keith J. Monaghan, Xiaoli LI, Jun Huan</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21869">
                <text>Abstract Background In recent years, research in artificial neural networks has resurged, now under the deep-learning umbrella, and grown extremely popular. Recently reported success of DL techniques in crowd-sourced QSAR and predictive toxicology competitions has showcased these methods as powerful tools in drug-discovery and toxicology research. The aim of this work was dual, first large number of hyper-parameter configurations were explored to investigate how they affect the performance of DNNs and could act as starting points when tuning DNNs and second their performance was compared to popular methods widely employed in the field of cheminformatics namely Naïve Bayes, k-nearest neighbor, random forest and support vector machines. Moreover, robustness of machine learning methods to different levels of artificially introduced noise was assessed. The open-source Caffe deep-learning framework and modern NVidia GPU units were utilized to carry out this study, allowing large number of DNN configurations to be explored. Results We show that feed-forward deep neural networks are capable of achieving strong classification performance and outperform shallow methods across diverse activity classes when optimized. Hyper-parameters that were found to play critical role are the activation function, dropout regularization, number hidden layers and number of neurons. When compared to the rest methods, tuned DNNs were found to statistically outperform, with p value</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="21870">
                <text>2017</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21871">
                <text>deep learning, SARS, Cheminformatics, machine learning, Data mining, random forest</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="21872">
                <text>DOI: 10.1186/s13321-017-0226-y</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="21873">
                <text>Journal of Cheminformatics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21874">
                <text>BMC</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21875">
                <text>Chemistry, Information technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21876">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2276" public="1" featured="0">
    <fileContainer>
      <file fileId="2276">
        <src>https://www.socictopen.socict.org/files/original/c0c004711d02a3cb6d8e9cd82a28d9c3.pdf</src>
        <authentication>740453661e2e92e660e1085e9bf3703f</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="21877">
                <text>Morphology of the nervous system of monogonont rotifer Epiphanes senta with a focus on sexual dimorphism between feeding females and dwarf males</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21878">
                <text>Ludwik Gąsiorowski, Anlaug Furu, Andreas Hejnol</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21879">
                <text>Abstract Background Monogononta is a large clade of rotifers comprised of diverse morphological forms found in a wide range of ecological habitats. Most monogonont species display cyclical parthenogenesis, where generations of asexually reproducing females are interspaced by mixis events when sexual reproduction occurs between mictic females and dwarf, haploid males. The morphology of monogonont feeding females is relatively well described, however data on male anatomy are very limited. Thus far, male musculature of only two species has been described with confocal laser scanning microscopy (CLSM) and it remains unknown how dwarfism influences the neuroanatomy of males on detailed level. Results Here, we provide a CLSM-based description of the nervous system of both sexes of Epiphanes senta, a freshwater monogonont rotifer. The general nervous system architecture is similar between males and females and shows a similar level of complexity. However, the nervous system in males is more compact and lacks a stomatogastric part. Conclusion Comparison of the neuroanatomy between male and normal-sized feeding females provides a better understanding of the nature of male dwarfism in Monogononta. We propose that dwarfism of monogonont non-feeding males is the result of a specific case of heterochrony, called “proportional dwarfism” as they, due to their inability to feed, retain a juvenile body size, but still develop a complex neural architecture comparable to adult females. Reduction of the stomatogastric nervous system in the males correlates with the loss of the entire digestive tract and associated morphological structures.</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="21880">
                <text>2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21881">
                <text>Gnathifera, Neuroanatomy, Sexual dimorphism, CLSM, meiof auna, male dwarfism</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="21882">
                <text>DOI: 10.1186/s12983-019-0334-9</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="21883">
                <text>Frontiers in Zoology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21884">
                <text>BMC</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21885">
                <text>Zoology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21886">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2277" public="1" featured="0">
    <fileContainer>
      <file fileId="2277">
        <src>https://www.socictopen.socict.org/files/original/2bc9707a501b91c36b7d790ac79dca53.pdf</src>
        <authentication>ebbc501984739537fab88def4f227d86</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="21887">
                <text>Shoelaces: an interactive tool for ribosome profiling processing and visualization</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21888">
                <text>Åsmund Birkeland, Katarzyna ChyŻyńska, Eivind Valen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21889">
                <text>Abstract Background The emergence of ribosome profiling to map actively translating ribosomes has laid the foundation for a diverse range of studies on translational regulation. The data obtained with different variations of this assay is typically manually processed, which has created a need for tools that would streamline and standardize processing steps. Results We present Shoelaces, a toolkit for ribosome profiling experiments automating read selection and filtering to obtain genuine translating footprints. Based on periodicity, favoring enrichment over the coding regions, it determines the read lengths corresponding to bona fide ribosome protected fragments. The specific codon under translation (P-site) is determined by automatic offset calculations resulting in sub-codon resolution. Shoelaces provides both a user-friendly graphical interface for interactive visualisation in a genome browser-like fashion and a command line interface for integration into automated pipelines. We process 79 libraries and show that studies typically discard excessive amounts of quality data in their manual analysis pipelines. Conclusions Shoelaces streamlines ribosome profiling analysis offering automation of the processing, a range of interactive visualization features and export of the data into standard formats. Shoelaces stores all processing steps performed in an XML file that can be used by other groups to exactly reproduce the processing of a given study. We therefore anticipate that Shoelaces can aid researchers by automating what is typically performed manually and contribute to the overall reproducibility of studies. The tool is freely distributed as a Python package, with additional instructions, tutorial and demo datasets available at https://bitbucket.org/valenlab/shoelaces.</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="21890">
                <text>2018</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21891">
                <text>ribosome profiling, Bioinformatics, Genomics, python, tool</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="21892">
                <text>DOI: 10.1186/s12864-018-4912-6</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="21893">
                <text>BMC Genomics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21894">
                <text>BMC</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21895">
                <text>Genetics, Biotechnology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21896">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2278" public="1" featured="0">
    <fileContainer>
      <file fileId="2278">
        <src>https://www.socictopen.socict.org/files/original/d77fb389bf32bafb173dfd258ffe2c14.pdf</src>
        <authentication>1e61786c9e78372b3b679e73c90be271</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="21897">
                <text>Nosocomial Transmission of Emerging Viruses via Aerosol-Generating Medical Procedures</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21898">
                <text>Seth D. Judson, Vincent J. Munster</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21899">
                <text>Recent nosocomial transmission events of emerging and re-emerging viruses, including Ebola virus, Middle East respiratory syndrome coronavirus, Nipah virus, and Crimean&amp;#8722;Congo hemorrhagic fever orthonairovirus, have highlighted the risk of nosocomial transmission of emerging viruses in health-care settings. In particular, concerns and precautions have increased regarding the use of aerosol-generating medical procedures when treating patients with such viral infections. In spite of increasing associations between aerosol-generating medical procedures and the nosocomial transmission of viruses, we still have a poor understanding of the risks of specific procedures and viruses. In order to identify which aerosol-generating medical procedures and emerging viruses pose a high risk to health-care workers, we explore the mechanisms of aerosol-generating medical procedures, as well as the transmission pathways and characteristics of highly pathogenic viruses associated with nosocomial transmission. We then propose how research, both in clinical and experimental settings, could advance current infection control guidelines.</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="21900">
                <text>2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21901">
                <text>aerosols, Viruses, cross infection, infection control, Risk, Health personnel, Virus Diseases, Hemorrhagic Fevers, Viral, Ebola virus</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="21902">
                <text>DOI: 10.3390/v11100940</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="21903">
                <text>Viruses</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="21904">
                <text>MDPI AG</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="38">
            <name>Coverage</name>
            <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
            <elementTextContainer>
              <elementText elementTextId="21905">
                <text>Microbiology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21906">
                <text>EN</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
