<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="23770" 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://socictopen.socict.org/items/show/23770?output=omeka-xml" accessDate="2026-04-22T05:06:51+00:00">
  <fileContainer>
    <file fileId="23767">
      <src>https://socictopen.socict.org/files/original/9a392c771f2dd2b337e132f28de463c4.pdf</src>
      <authentication>3301c6fbc6980c79dc0cf069db6f92b0</authentication>
    </file>
  </fileContainer>
  <collection collectionId="2">
    <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="88121">
                <text>Agricultura sostenible</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="88122">
                <text>Dominio científico: Agricultura sostenible</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="205090">
              <text>Assessing the effect of fish size on species distribution model performance in southern Chilean rivers</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="205091">
              <text>Daniel Zamorano, Fabio A. Labra, Marcelo Villarroel, Shaw Lacy, Luca Mao, Marcelo A. Olivares, Matías Peredo-Parada</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="205092">
              <text>Despite its theoretical relationship, the effect of body size on the performance of species distribution models (SDM) has only been assessed in a few studies, and to date, the evidence shows unclear results. In this context, Chilean fishes provide an ideal case to evaluate this relationship due to their short size (fishes between 5 cm and 40 cm) and conservation status, providing evidence for species at the lower end of the worldwide fish size distribution and representing a relevant management tool for species conservation. We assessed the effect of body size on the performance of SDM in nine Chilean river fishes, considering the number of records, performance metrics, and predictor importance. The study was developed in the Bueno and Valdivia basins of southern Chile. We used a neural network modeling algorithm, training models with a cross-validation scheme. The effect of fish size on selected metrics was assessed using linear models and beta regressions. While no relationship between fish size and the number of presences was found, our results indicate that the model specificity increases with fish size. Additionally, the predictive importance of Riparian Vegetation and Within-Channel Structures variables decreases for larger species. Our results suggest that the relationship between the grain of the dataset and the home range of the species could bias SDM, leading in our case, to overprediction of absences. We also suggest that evolutionary adaptation to low slopes among Chilean fishes increases the relevance of riparian vegetation in the SDMs of smaller species. This study provides evidence on how species size may bias SDM, which could potentially be corrected by adjusting the model grain.</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="205093">
              <text>2019</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="205094">
              <text>Anthropogenic variables, Chilean fishes, Riparian vegetation, Structures within the channel, neural networks, specificity</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="205095">
              <text>10.7717/peerj.7771</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="205096">
              <text>PeerJ</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="205097">
              <text>PeerJ Inc.</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="205098">
              <text>Medicine</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="205099">
              <text>&lt;a href="https://peerj.com/articles/7771/" target="_blank" rel="noreferrer noopener"&gt;https://peerj.com/articles/7771/&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
