<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13288" 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/13288?output=omeka-xml" accessDate="2026-05-19T16:52:06+00:00">
  <collection collectionId="5">
    <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="64">
                <text>Articles</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="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82951">
              <text>Twitter sentiment analysis on online food services based on elephant herd optimization with hybrid deep learning technique</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82952">
              <text>Deep learning; Elephant herd optimization; Online food service; Pseudoinverse learning autoencoder; Swiggy; Twitter sentiment analysis; Zomato</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82953">
              <text>Twitter is a social media stage, making it a valuable resource for learning about peoples opinions, feelings, and thoughts. For this reason, experts came up with methods to analyse the tone of tweets and determine whether they were favourable or negative. This article aims to assist businesses, and especially app-based meal delivery businesses, in conducting competitive research on social broadcasting and transforming social broadcasting data into data production for decision-makers. In this analysis, we compared Swiggy, Zomato, and UberEats. Customers tweets about all these brands are obtained using R-Studio, and a deep learning-based sentiment examination approach is functional on the retrieved tweets. The pseudo-inverse learning autoencoder is able to provide feature extraction in the form of an analytic solution after pre-processing, without resorting to many iterations. In this research, we suggest framework for combining the Convolutional Neural Network (CNN) and Bi-directional Long Short Term Memory (Bi-LSTM) models. ConvBiLSTM is used, which is a word embedding model that uses numerical values to represent tweets. The CNN layer takes the feature implanting as input and outputs lower features. In this instance, elephant herd optimization is used to fine-tune the Bi-LSTM weights. Among the three firms, the results indicate that Zomato got the most positive feedback (29%), followed by Swiggy (26%), and UberEats (25%). Zomato also had fewer bad reviews than Swiggy and UberEats, with only 11% of users having a poor experience. In addition, tweets were evaluated for unfavourable views against all three meal delivery services, and suggestions for improvement were offered.  The Author(s), under exclusive licence to Springer Science+Business Media, LLC, part of Springer Nature 2023.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82954">
              <text>Vatambeti R.; Mantena S.V.; Kiran K.V.D.; Manohar M.; Manjunath C.</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="82955">
              <text>Cluster Computing, Vol-27, No. 1, pp. 655-671.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="82956">
              <text>Springer</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="82957">
              <text>2024-01-01</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="82958">
              <text>&lt;a href="https://doi.org/10.1007/s10586-023-03970-7" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/s10586-023-03970-7&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85147314813&amp;amp;doi=10.1007%2Fs10586-023-03970-7&amp;amp;partnerID=40&amp;amp;md5=7f7c62d98b6fc3a7c357514ebaab4f6c" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85147314813&amp;amp;doi=10.1007%2fs10586-023-03970-7&amp;amp;partnerID=40&amp;amp;md5=7f7c62d98b6fc3a7c357514ebaab4f6c&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82959">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="82960">
              <text>ISSN: 13867857</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="82961">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82962">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="82963">
              <text>Article</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="82964">
              <text>Vatambeti R., School of Computer Science and Engineering, VIT-AP University, Vijayawada, India; Mantena S.V., Department of Computer Science and Engineering, SRKR Engineering College, Bhimavaram, 534204, India; Kiran K.V.D., Department of CSE, Koneru Lakshmaiah Education Foundation, AP, Vaddeswaram, India; Manohar M., Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India; Manjunath C., Computer Science and Engineering, CHRIST (Deemed to be University), Bangalore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
