<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="21791" 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/21791?output=omeka-xml" accessDate="2026-04-16T07:18:58+00:00">
  <fileContainer>
    <file fileId="21788">
      <src>https://socictopen.socict.org/files/original/62aa45121798f8e421e203a91c5c12a3.pdf</src>
      <authentication>fec5de337450bfa54861ee5987fd2ea9</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="186755">
              <text>Modelling soil water content and grapevine growth and development with the stics crop-soil model under two different water management strategies</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="186756">
              <text>Iñaki García de Cortázar-Atauri, Héctor Valdés-Gómez, Florian Celette, Francisco Jara-Rojas, Samuel Ortega-Farías, Christian Gary</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="186757">
              <text>Background and aims: Many models have been developed to evaluate crop growth and development, but few are capable of simulating grapevine systems. The present study was carried out to evaluate the ability of the STICS model to represent grapevine phenology, biomass production, yield and soil water content in two situations differing with respect to rainfall distribution and water management strategies. Methods and results: Simulations were performed for an irrigated vineyard in Chile and an irrigated and a non-irrigated vineyard in France. The crop model gave a good estimation of the main stages of grapevine phenology (less than six days difference between simulated and observed values). Soil water content was the best simulated variable (R2 = 0.99), whereas grapevine evapotranspiration observed only in Chile (R2 = 0.43) and leaf area index observed only in France (R2= 0.80) were the worst simulated variables. Biomass production, yield and their components were correctly simulated (within the 95 % Student confidence interval around the mean observed value). A comparison of the fraction of transpirable soil water and vine water potential measurements with the water stress indices calculated by the STICS model showed that the time and duration of the grapevine water stress period was correctly estimated. Conclusions: Therefore, the STICS model was reasonably successful in simulating vine growth and development, and identifying critical periods concerning the vine water status. Significance of the study: The STICS model can be used to evaluate various water management strategies and their impacts on grape production.</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="186758">
              <text>2009</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="186759">
              <text>Vitis vinifera L, irrigation, model evaluation, phenology, water deficit</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="186760">
              <text>10.20870/oeno-one.2009.43.1.806</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="186761">
              <text>OENO One</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="186762">
              <text>International Viticulture and Enology Society</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="186763">
              <text>Agriculture, Botany</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="186764">
              <text>&lt;a href="https://oeno-one.eu/article/view/806" target="_blank" rel="noreferrer noopener"&gt;https://oeno-one.eu/article/view/806&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
