<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="21875" 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://archives.christuniversity.in/items/show/21875?output=omeka-xml" accessDate="2026-06-20T06:15:54+00:00">
  <collection collectionId="7">
    <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="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</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="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201434">
              <text>Geetha, P.; Padmavathy, T.; Vinodha, D.; Abirami, G.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201435">
              <text>Resource allocation in cloud auction-based market by hybrid optimization algorithm</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="201436">
              <text>01-01-2026</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="201437">
              <text>Cluster Computing;Volume;29;Issue;1;Article No.;34;</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="201438">
              <text>&lt;a href="https://doi.org/10.1007/s10586-025-05767-2" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/s10586-025-05767-2&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105021945715?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105021945715?origin=resultslist&lt;/a&gt;</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="201439">
              <text>Geetha P., Department of Computational Intelligence (CINTEL), School of Computing, SRM Institute of Science and Technology (KTR Campus), Tamil Nadu, Chennai, India; Padmavathy T., Department of Database Systems, School of Computer Science and Engineering, Vellore Institute of Technology, Tamil Nadu, Vellore, India; Vinodha D., Department of AIML and DS, School of Engineering and Technology, CHRIST (Deemed to be University), Bangalore, India; Abirami G., Department of Computer Science and Engineering, B.S.Abdur Rahman Crescent Institute of Science &amp;amp; Technology, GST Road, Tamil Nadu, Vandalur, Chennai, 600 048, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201440">
              <text>Effective resource allocation is essential in the rapidly changing cloud computing landscape to maximize provider revenue and user satisfaction. Through competitive bidding procedures, the auction-based market model has become a potent tool for allocating cloud resources among users. In this paper, a new method for cloud computing environments is presented: Double Auction-based Resource Allocation (DARA). The auction model and optimal resource allocation are the two main parts of the DARA methodology. The Double Auction mechanism is used as the auction model in the suggested DARA framework. In this model, resource prices and allocations are decided through a competitive auction process that involves both buyers and sellers.The highest price that buyers are willing to pay for resources is expressed in bids, and the lowest price that sellers are willing to accept is expressed in asks. There are many intricate tasks involved in this two-way auction process, including matching bids and asks, determining market prices, and handling transactions. Finding the equilibrium price requires the method to solve complex optimization problems in order to balance supply and demand. In order to overcome these obstacles, the study suggests the Hippopotamus Updated Pufferfish Optimization (HUPO) algorithm for the best possible resource distribution. The HUPO algorithm is made to handle limitations like truthfulness, resource density, execution time, and operating expenses. In order to ensure that users pay fair prices and service providers make the most money, it is crucial to implement effective resource allocation strategies that balance the cost of resources with their availability. According to the mean statistical metric, the resource density for the HUPO model is 17.862, which is greater than the values of all other traditional approaches, including BES at 14.960, AOA at 12.546, ACO at 14.274, COA at 13.693, SMO at 13.452, HOA at 13.686, and POA at 13.907.  The Author(s), under exclusive licence to Springer Science+Business Media, LLC, part of Springer Nature 2025.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201441">
              <text>Bid-Ask matching; Cloud computing; Double auction; HUPO algorithm; Resource allocation</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="201442">
              <text>Springer</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="201443">
              <text>ISSN: 13867857;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201444">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201445">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201446">
              <text>Restricted Access; Hardcopy may be available in the library</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="201447">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
