<?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://archives.christuniversity.in/items/browse?output=omeka-xml&amp;page=477&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-06-30T08:58:55+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>477</pageNumber>
      <perPage>20</perPage>
      <totalResults>16481</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="14185" public="1" featured="0">
    <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="95448">
                <text>IOT-BASED cyber security identification model through machine learning technique</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="95449">
                <text>Cyber security; Internet of things; Machine learning algorithms; Meta-classifier methods; Repositories; Security</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="95450">
                <text>Manual vulnerability evaluation tools produce erroneous data and lead to difficult analytical thinking. Such security concerns are exacerbated by the variety, imperfection, and redundancies of modern security repositories. These problems were common traits of producers and public vulnerability disclosures, which make it more difficult to identify security flaws through direct analysis through the Internet of Things (IoT). Recent breakthroughs in Machine Learning (ML) methods promise new solutions to each of these infamous diversification and asymmetric information problems throughout the constantly increasing vulnerability reporting databases. Due to their varied methodologies, those procedures themselves display varying levels of performance. The authors provide a method for cognitive cybersecurity that enhances human cognitive capacity in two ways. To create trustworthy data sets, initially reconcile competing vulnerability reports and then pre-process advanced embedded indicators. This proposed methodology's full potential has yet to be fulfilled, both in terms of its execution and its significance for security evaluation in application software. The study shows that the recommended mental security methodology works better when addressing the above inadequacies and the constraints of variation among cybersecurity alert mechanisms. Intriguing trade-offs are presented by the experimental analysis of our program, in particular the ensemble method that detects tendencies of computational security defects on data sources.  2023 The Authors</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="95451">
                <text>Lal B.; Ravichandran S.; Kavin R.; Anil Kumar N.; Bordoloi D.; Ganesh Kumar R.</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="95452">
                <text>Measurement: Sensors, Vol-27</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="95453">
                <text>Elsevier Ltd</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="95454">
                <text>2023-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="95455">
                <text>&lt;a href="https://doi.org/10.1016/j.measen.2023.100791" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.measen.2023.100791&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85159550720&amp;amp;doi=10.1016%2Fj.measen.2023.100791&amp;amp;partnerID=40&amp;amp;md5=0b3e4993e4256d13a2f57747dc17b17c" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85159550720&amp;amp;doi=10.1016%2fj.measen.2023.100791&amp;amp;partnerID=40&amp;amp;md5=0b3e4993e4256d13a2f57747dc17b17c&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="95456">
                <text>All Open Access; Gold Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="95457">
                <text>ISSN: 26659174</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="95458">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="95459">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="95460">
                <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="95461">
                <text>Lal B., Dept. of Computer Science and Engineering, Koneru Lakshmaiah Education Foundation, Vaddeswaram, Guntur Dist, A.P, India; Ravichandran S., Department of Computer Science and Engineering, School of Technology, GITAM University, Rudraram, Telangana, Hyderabad, 502 329, India; Kavin R., Department of Electrical and Electronics Engineering, Sri Krishna College of Engineering and Technology, Tamil Nadu, Coimbatore, 641008, India; Anil Kumar N., Department of Electronics &amp;amp; Communication Engineering, School of Engineering &amp;amp; Technology, Mohan Babu University (Erst while Sree Vidyanikethan Engineering College), Andhra Pradesh, Tirupati, India; Bordoloi D., Computer Science and Engineering, Graphic Era Hill University, Dehradun, India, R/S, CSE, Graphic Era Deemed To Be University, Uttarakhand, Dehradun, 248002, India; Ganesh Kumar R., Department of Computer Science and Engineering, CHRIST (Deemed to be University), School of Engineering and Technology, Kengeri Campus, Kumbalgodu, Bangalore, 560074, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="23237" public="1" featured="0">
    <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="220373">
                <text>Suhana, Syed; Prathap, Boppuru Rudra; Narang, Kavish; Anto, Ivin</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="220374">
                <text>IoT-Based Emergency Vehicle Detection Using YOLOv8</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="220375">
                <text>01-01-2025</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="220376">
                <text>Journal of Automation, Mobile Robotics and Intelligent Systems;Volume;19;Issue;2;pp.79-88</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="220377">
                <text>&lt;a href="https://doi.org/10.14313/jamris-2025-018" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.14313/jamris-2025-018&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105009935330?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105009935330?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="220378">
                <text>Suhana S., Department of Computer Science and Engineering, CHRIST (Deemed to Be University), India; Prathap B.R., Department of Computer Science and Engineering, M. S. Ramaiah University of Applied Sciences, India; Narang K., Department of Computer Science and Engineering, CHRIST (Deemed to Be University), India; Anto I., Department of Computer Science and Engineering, CHRIST (Deemed to Be University), India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="220379">
                <text>The rapid response of emergency services plays a critical role in saving lives and minimizing the impact of emergencies. However, identifying and locating emergency vehicles in real-Time can be challenging, especially in congested urban areas. This paper focuses on the emergency vehicle identification using the You Only Look Once version 8 (YOLOv8) algorithm and is focused on Internet of Things (IoT). The goal of this research is to develop a real-Time and precise emergency vehicle detection system using You Only Look Once version 8 (YOLOv8) algorithm, trained and tested with a dataset from a camera placed on a busy road, to enhance emergency service response times. The findings demonstrate the suggested system's ability to recognize emergency vehicles at a speed of 31 frames per second and with a 95% accuracy rate. Modern object identification algorithms include the You Only Look Once version 8 (YOLOv8) algorithm, which has shown promising results in various applications. The proposed system is built on a Raspberry Pi, which acts as an edge device and processes the video stream in realtime. The system consists of an Internet of Things (IoT) device with a camera that captures the live video stream, which is then fed into the algorithm for object detection. Once an emergency vehicle is detected, the system sends an email notification to the nearby emergency services, like a police station, using Simple Mail Transfer Protocol (SMTP), who can then take appropriate action. The results of this investigation show that the Internet of Things and You Only Look Once version 8 (YOLOv8) algorithms have great promise for creating effective and dependable emergency vehicle detection systems. The proposed system possesses the capacity to save lives and improve the effectiveness of emergency response by speeding up response times for emergency services. The suggested solution is also inexpensive, simple to implement, and adaptable to existing infrastructure. Through the development of intelligent transportation systems, emergency services can operate more safely and effectively. More sophisticated machine learning algorithms may be incorporated into the proposed system, and further sensors can be added to utilize alternative methods beyond camera-based detection to identify emergency vehicles. Overall, this research shows the potential of Internet of Things (IoT) and machine learning in creating creative emergency services solutions.   2025 Syed Suhana et al.Published by Sciendo.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="220380">
                <text>email notifications; emergency vehicles; Internet of Things (IoT); Pi Camera; Raspberry Pi; simple mail transfer protocol (SMTP); You Only Look Once (YOLOv8)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="220381">
                <text>Sciendo</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="220382">
                <text>ISSN: 18978649;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="220383">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="220384">
                <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="220385">
                <text>All Open Access; Gold Open Access</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="220386">
                <text>online</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15429" public="1" featured="0">
    <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="112760">
                <text>IoT-Based Response Time Analysis of Messages for Smart Autonomous Collision Avoidance System Using Controller Area Network</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112761">
                <text>Many accidents and serious problems occur on the road due to the rapid increase in traffic congestion in all sections of the country. Autonomous vehicles provide a solution to successfully and cost-effectively avoid this problem while minimizing user disruption. Currently, more engaging electromechanical elements with an analog interface are used to develop affordable automobiles for efficient and cost-effective operation for a smart driving platform with a semiautonomous automobile, strengthening the vehicle involvement of the driver while increasing safety. As a result, it takes longer for various car elements to respond, which causes more problems during message transmission. This project aims to create a Controller Area Network (CAN) for analyzing message response times by incorporating a few application nodes on the IoT platform, such as an antilock braking system, flexible cruise control, and seat belt section, for some real-time control system applications. These application nodes are car analytical parts that are linked to IoT modules to prevent collisions. An autonomous device for collision avoidance and obstacle detection in a vehicle can impact road accidents if the CAN protocol is implemented.  2022 Anil Kumar Biswal et al.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112762">
                <text>Biswal A.K.; Singh D.; Pattanayak B.K.; Samanta D.; Banerjee A.; Seteikin A.Y.; Samusev I.G.</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="112763">
                <text>Wireless Communications and Mobile Computing, Vol-2022</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="112764">
                <text>Hindawi Limited</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="112765">
                <text>2022-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="112766">
                <text>&lt;a href="https://doi.org/10.1155/2022/1149842" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1155/2022/1149842&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85128682086&amp;amp;doi=10.1155%2F2022%2F1149842&amp;amp;partnerID=40&amp;amp;md5=cb195d35ecebe66ef6e5d2ae849d0e71" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85128682086&amp;amp;doi=10.1155%2f2022%2f1149842&amp;amp;partnerID=40&amp;amp;md5=cb195d35ecebe66ef6e5d2ae849d0e71&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="112767">
                <text>All Open Access; Gold Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="112768">
                <text>ISSN: 15308669</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="112769">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112770">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="112771">
                <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="112772">
                <text>Biswal A.K., Department of CSE, ITER, SOA Deemed to Be University, India; Singh D., Department of Ca, ITER, SOA Deemed to Be University, India; Pattanayak B.K., Department of CSE, ITER, SOA Deemed to Be University, India; Samanta D., Department of Computer Science, Christ University, India; Banerjee A., Physics Department, Bidhan Chandra College, Asansol, 713 303, India; Seteikin A.Y., Immanuel Kant Baltic Federal, University, Kaliningrad, 236000, Russian Federation, Amur State University, Blagoveshchensk, 675027, Russian Federation; Samusev I.G., Immanuel Kant Baltic Federal, University, Kaliningrad, 236000, Russian Federation, Amur State University, Blagoveshchensk, 675027, Russian Federation</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="16070" public="1" featured="0">
    <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="121674">
                <text>IoT-based smart alert system for drowsy driver detection</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="121675">
                <text>In current years, drowsy driver detection is the most necessary procedure to prevent any road accidents, probably worldwide. The aim of this study was to construct a smart alert technique for building intelligent vehicles that can automatically avoid drowsy driver impairment. But drowsiness is a natural phenomenon in the human body that happens due to different factors. Hence, it is required to design a robust alert system to avoid the cause of the mishap. In this proposed paper, we address a drowsy driver alert system that has been developed using such a technique in which the Video Stream Processing (VSP) is analyzed by eye blink concept through an Eye Aspect Ratio (EAR) and Euclidean distance of the eye. Face landmark algorithm is also used as a proper way to eye detection. When the drivers fatigue is detected, the IoT module issues a warning message along with impact of collision and location information, thereby alerting with the help of a voice speaking through the Raspberry Pi monitoring system. Copyright  2021 Anil Kumar Biswal et al. This is an open access article distributed under the Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="121676">
                <text>Biswal A.K.; Singh D.; Pattanayak B.K.; Samanta D.; Yang M.-H.</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="121677">
                <text>Wireless Communications and Mobile Computing, Vol-2021</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="121678">
                <text>Hindawi Limited</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="121679">
                <text>2021-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="121680">
                <text>&lt;a href="https://doi.org/10.1155/2021/6627217" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1155/2021/6627217&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85102518105&amp;amp;doi=10.1155%2F2021%2F6627217&amp;amp;partnerID=40&amp;amp;md5=5472c79a7eda55f40e4dc6fbdb9325e3" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85102518105&amp;amp;doi=10.1155%2f2021%2f6627217&amp;amp;partnerID=40&amp;amp;md5=5472c79a7eda55f40e4dc6fbdb9325e3&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="121681">
                <text>All Open Access; Gold Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="121682">
                <text>ISSN: 15308669</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="121683">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="121684">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="121685">
                <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="121686">
                <text>Biswal A.K., Department of CSE, ITER, SOA Deemed to be University, India; Singh D., Department of CSIT, ITER, SOA Deemed to be University, India; Pattanayak B.K., Department of CSE, ITER, SOA Deemed to be University, India; Samanta D., Department of Computer Science, CHRIST Deemed to be University, India; Yang M.-H., Department of Computer Science and Info. Engineering, National Central University, Taiwan</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15043" public="1" featured="0">
    <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="107393">
                <text>IoT-based smart healthcare video surveillance system using edge computing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107394">
                <text>Ambient assistive living; Edge computing; Elderly people fall detection; Healthcare application; Smart video surveillance</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107395">
                <text>Managing distributed smart surveillance system is identified as a major challenging issue due to its comprehensive aggregation and analysis of video information on the cloud. In smart healthcare applications, remote patient and elderly people monitoring require a robust response and alarm alerts from surveillance systems within the available bandwidth. In order to make a robust video surveillance system, there is a need for fast response and fast data analytics among connected devices deployed in a real-time cloud environment. Therefore, the proposed research work introduces the Cloud-based Object Tracking and Behavior Identification System (COTBIS) that can incorporate the edge computing capability framework in the gateway level. It is an emerging research area of the Internet of Things (IoT) that can bring robustness and intelligence in distributed video surveillance systems by minimizing network bandwidth and response time between wireless cameras and cloud servers. Further improvements are made by incorporating background subtraction and deep convolution neural network algorithms on moving objects to detect and classify abnormal falling activity monitoring using rank polling. Therefore, the proposed IoT-based smart healthcare video surveillance system using edge computing reduces the network bandwidth and response time and maximizes the fall behavior prediction accuracy significantly comparing to existing cloud-based video surveillance systems.  2021, The Author(s), under exclusive licence to Springer-Verlag GmbH Germany, part of Springer Nature.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107396">
                <text>Rajavel R.; Ravichandran S.K.; Harimoorthy K.; Nagappan P.; Gobichettipalayam K.R.</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="107397">
                <text>Journal of Ambient Intelligence and Humanized Computing, Vol-13, No. 6, pp. 3195-3207.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="107398">
                <text>Springer Science and Business Media Deutschland GmbH</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="107399">
                <text>2022-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="107400">
                <text>&lt;a href="https://doi.org/10.1007/s12652-021-03157-1" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/s12652-021-03157-1&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85103277065&amp;amp;doi=10.1007%2Fs12652-021-03157-1&amp;amp;partnerID=40&amp;amp;md5=9a05db2020151d770b1dcc15e1a6fa8d" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85103277065&amp;amp;doi=10.1007%2fs12652-021-03157-1&amp;amp;partnerID=40&amp;amp;md5=9a05db2020151d770b1dcc15e1a6fa8d&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="107401">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="107402">
                <text>ISSN: 18685137</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="107403">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107404">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="107405">
                <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="107406">
                <text>Rajavel R., Department of CSE, Galgotias University, Uttar Pradesh, Greater Noida, India; Ravichandran S.K., Department of CSE, Christ University, Bangalore, India; Harimoorthy K., Department of CSE, Christ University, Bangalore, India; Nagappan P., Department of CSE, Galgotias University, Uttar Pradesh, Greater Noida, India; Gobichettipalayam K.R., Wireless Networks, Springer Asia Ltd, Chennai, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19359" public="1" featured="0">
    <collection collectionId="16">
      <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="51377">
                  <text>Conference Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="166651">
                <text>IoT-Based Smart Indoor Navigation System with Voice Assistance for Museums</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166652">
                <text>Bluetooth low energy; Internet of Things; Navigation system; Smart indoor systems</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166653">
                <text>In the current era of smart heterogenous devices, the surrounding environment too needs to be smarter to match the gravity of such devices. Such advanced environment can be built with the technology called Internet of Things (IoT). Due to the presence of such vivid thing devices in the Internet of Things (IoT) environment, the task of automatically predicting the end users desires can play an important role when it comes to match the pace of modern society with too much diverse aspects. Since last decade, people have deviated their attention towards Indian ancient culture and Museums are eye catching attraction where our ancient cultural heritage exist. To improvise the slow pace growth of the tourism sector, there is the crucial requirement of technological improvement especially due to the restrictions on installations of external hardware within the close proximity. One prominent way of improving tourists experience at museums is to renovate existing museums with IoT-based smart devices which is programmed such a way to automatically navigate the user indoor and briefs the associated information about artwork without any user intervention. In this paper, we propose an IoT-based smart indoor navigation system along with voice assistance which can enhance the tourists experience in a museum. In addition, the proposed design also delivers the very personalized cultural contents related to the visited artworks.  The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd. 2024.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166654">
                <text>Manju; Singh S.; Kumar S.</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="166655">
                <text>Lecture Notes in Networks and Systems, Vol-967 LNNS, pp. 449-457.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="166656">
                <text>Springer Science and Business Media Deutschland GmbH</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="166657">
                <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="166658">
                <text>&lt;a href="https://doi.org/10.1007/978-981-97-2053-8_34" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-981-97-2053-8_34&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85199482500&amp;amp;doi=10.1007%2F978-981-97-2053-8_34&amp;amp;partnerID=40&amp;amp;md5=92a654bbe7ceeb5d63749e238ddd94ec" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85199482500&amp;amp;doi=10.1007%2f978-981-97-2053-8_34&amp;amp;partnerID=40&amp;amp;md5=92a654bbe7ceeb5d63749e238ddd94ec&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="166659">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="166660">
                <text>ISSN: 23673370; ISBN: 978-981972052-1</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="166661">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166662">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166663">
                <text>Conference paper</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="166664">
                <text>Manju, Department of Computer Science &amp;amp; Engineering and Information Technology, Jaypee Institute of Information Technology, Noida, India; Singh S., Department of Computer Science and Engineering, Dr. B. R. Ambedkar National Institute of Technology Jalandhar, Jalandhar, India; Kumar S., Department of Computer Science and Engineering, School of Engineering and Technology, CHRIST (Deemed to be University), Kengeri Campus, Karnataka, Bangalore, 560074, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="15670" public="1" featured="0">
    <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="116116">
                <text>IoT-based traffic prediction and traffic signal control system for smart city</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116117">
                <text>Improved beetle swarm optimization (IBSO); Intel 80,286 microprocessor; Internet of Things (IoT); Optimized weight elman neural network (OWENN); Smart city</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116118">
                <text>Because of the population increasing so high, and traffic density remaining the same, traffic prediction has become a great challenge today. Creating a higher degree of communication in automobiles results in the time wastage, fuel wastage, environmental damage, and even death caused by citizens being trapped in the middle of traffic. Only a few researchers work in traffic congestion prediction and control systems, but it may provide less accuracy. So, this paper proposed an efficient IoT-based traffic prediction using OWENN algorithm and traffic signal control system using Intel 80,286 microprocessor for a smart city. The proposed system consists of 5 phases, namely IoT data collection, feature extraction, classification, optimized traffic IoT values, and traffic signal control system. Initially, the IoT traffic data are collected from the dataset. After that, traffic, weather, and direction information are extracted, and these extracted features are given as input to the OWENN classifier, which classifies which place has more traffic. Suppose one direction of the place has more traffic, it optimizes the IoT values by using IBSO, and finally, the traffic is controlled by using Intel 80,286 microprocessor. An efficient OWENN algorithm for traffic prediction and traffic signal control using a Intel 80,286 microprocessor for a smart city. After extracting the features, the classification is performed in this step. Hereabout, the classification is done by using the optimized weight Elman neural network (OWENN) algorithm that classifies which places have more traffic. OWENN attains 98.23% accuracy than existing model also its achieved 96.69% F-score than existing model. The experimental results show that the proposed system outperforms state-of-the-art methods.  2021, The Author(s), under exclusive licence to Springer-Verlag GmbH Germany, part of Springer Nature.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116119">
                <text>Neelakandan S.; Berlin M.A.; Tripathi S.; Devi V.B.; Bhardwaj I.; Arulkumar N.</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="116120">
                <text>Soft Computing, Vol-25, No. 18, pp. 12241-12248.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="116121">
                <text>Springer Science and Business Media Deutschland GmbH</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="116122">
                <text>2021-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="116123">
                <text>&lt;a href="https://doi.org/10.1007/s00500-021-05896-x" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/s00500-021-05896-x&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85107334797&amp;amp;doi=10.1007%2Fs00500-021-05896-x&amp;amp;partnerID=40&amp;amp;md5=204cec12651367d9360b723b4f87c7c8" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85107334797&amp;amp;doi=10.1007%2fs00500-021-05896-x&amp;amp;partnerID=40&amp;amp;md5=204cec12651367d9360b723b4f87c7c8&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="116124">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="116125">
                <text>ISSN: 14327643</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="116126">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116127">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="116128">
                <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="116129">
                <text>Neelakandan S., Department of IT, Jeppiaar Institute of Technology, Chennai, India; Berlin M.A., Department of CSE, R.M.D Engineering College, Chennai, India; Tripathi S., Department of Computer Science &amp;amp; Engineering, Birla Institute of Applied Sciences, Bhimtal, India; Devi V.B., Department of Information Technology, Sri Sai Ram Institute of Technology, Chennai, India; Bhardwaj I., Galgotias University, Greater Noida, India; Arulkumar N., Department of CS, CHRIST (Deemed To Be University), Banglore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19358" public="1" featured="0">
    <collection collectionId="16">
      <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="51377">
                  <text>Conference Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="166637">
                <text>IoT-Driven Credit Scoring Models: Improving Loan Decision Making in Banking</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166638">
                <text>Banking analytics; financial inclusion; IoT data in lending; IoT-driven credit scoring; Loan approval optimization; Loan decision-making; Risk assessment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166639">
                <text>By the game-changing possibilities of credit scoring models driven by the Internet of Things, this hopes to shed light on how the banking sector may enhance its loan decision-making procedures. Financial organisations are putting more and more faith in Internet of Things technologies to improve their risk assessment and lending processes. These IoT-driven models provide a more accurate and thorough assessment of creditworthiness by including real-time and detailed data on borrowers' activities, spending habits, and asset utilisation. This research examines the practicality and accuracy of Internet of Things (IoT) credit scoring by comparing it to conventional methods, looking closely at case researches, and analysing empirical data. The findings shed light on potential ways to enhance the loan approval and risk prediction procedures while also addressing concerns and considerations related to data privacy, security, and regulatory compliance. It is possible that decision-making frameworks could be altered by IoT-driven credit scoring algorithms, which could lead to a more inclusive and informed lending atmosphere. The contributes to the growing area of banking credit evaluation by showing that these models have promise.  2024 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166640">
                <text>Thirumagal P.G.; Das T.; Das S.; Vinit Sikka C.S.; Amit Kumar C.S.; Kusuma T.</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="166641">
                <text>5th International Conference on Recent Trends in Computer Science and Technology, ICRTCST 2024 - Proceedings, pp. 193-197.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="166642">
                <text>Institute of Electrical and Electronics Engineers Inc.</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="166643">
                <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="166644">
                <text>&lt;a href="https://doi.org/10.1109/ICRTCST61793.2024.10578365" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICRTCST61793.2024.10578365&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85199413840&amp;amp;doi=10.1109%2FICRTCST61793.2024.10578365&amp;amp;partnerID=40&amp;amp;md5=52342c58eb0c6b8a2b32178234259043" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85199413840&amp;amp;doi=10.1109%2fICRTCST61793.2024.10578365&amp;amp;partnerID=40&amp;amp;md5=52342c58eb0c6b8a2b32178234259043&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="166645">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="166646">
                <text>ISBN: 979-835035137-8</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="166647">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166648">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="166649">
                <text>Conference paper</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="166650">
                <text>Thirumagal P.G., VISTAS, Department of MBA, Tamil Nadu, Chennai, India; Das T., Christ University, Department of School of Business Management, Delhi NCR Campus, UP, Ghaziabad, India; Das S., Christ University, Department of School of Commerce, Finance &amp;amp; Accountancy, UP, Ghaziabad, India; Vinit Sikka C.S., School of Leadership and Management, Manav Rachna International Institute of Research and Studies, Department of UG Management Studies, Haryana, Faridabad, India; Amit Kumar C.S., School of Leadership and Management, Manav Rachna International Institute of Research and Studies, Department of UG Management Studies, Haryana, Faridabad, India; Kusuma T., Sree Vidyanikethan Engineering College, Department of Commerce, Andhra Pradesh, Tirupati, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26497" public="1" featured="0">
    <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="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="264527">
                <text>Srinivasan, R.; Vimala Devi, K.; Praveenraj, David Winster; Venkatasuvrananian, S.; Subramani, K.; Prasanth, V.S.; Gaddala, Babu Rao</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264528">
                <text>IoT-Driven Dynamic Behavior Intervention Model for Sustainable Hygiene Practices: Insights from Household Water Consumption</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="264529">
                <text>01-01-2025</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="264530">
                <text>Communications in Computer and Information Science;Volume;2308 CCIS;pp.136-154</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="264531">
                <text>&lt;a href="https://doi.org/10.1007/978-3-031-84394-5_11" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-031-84394-5_11&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105001272363?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105001272363?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="264532">
                <text>Srinivasan R., Department of Mechanical Engineering, Sri Krishna College of Technology, Kovaipudur, Coimbatore, 641042, India; Vimala Devi K., School of Computer Science and Engineering, Vellore Institute of Technology, Vellore, 631014, India; Praveenraj D.W., CHRIST (Deemed to be) University, Bangalore, India; Venkatasuvrananian S., CSBS, Saranathan College of Engineering, Trichy, India; Subramani K., School of Business and Management, CHRIST (Deemed to be University), Bangalore Yeshwanthpur Campus, Bangalore, 560 073, India; Prasanth V.S., Department of Electronics and Communication Engineering, Madanapalle Institute of Technology and Science, Andhra Pradesh, Madanapalle, 517 325, India; Gaddala B.R., Department of Chemical Engineering, University of Technology and Applied Sciences (Higher College of Technology Muscat), Muscat, Oman</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264533">
                <text>IoT-enabled technologies have advanced so that smart sensor systems can observe and recognize human behavior in various contexts, including energy consumption and healthcare, with remarkable efficiency and effectiveness. One example is using the Internet of Things (IoT) technology to better comprehend human water consumption behavior and establish and maintain clean environments. Static models have typically been used to model the behavior intervention process throughout time. While these static approaches perform adequately when predicting general human behavior, they fall short when tracking and reacting to shifts in behavior in IoT settings. The authors of this study proposed a dynamic behavior intervention model to forecast the hygiene-related water-use habits of individual households. This model takes its cues from the structure equation model method and the notion of control engineering, which originated in the expanded theory of planned behavior (ETPB). The current ETPB dynamic behavior model with system parameter estimation using an artificial neural network (ANN)is assessed for its intervention trend using a residential water use case study. It has been shown that the ETPB dynamic model helps the process of intervening in peoples behavior.  The Author(s), under exclusive license to Springer Nature Switzerland AG 2025.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264534">
                <text>artificial neural network (ANN); dynamic behavior; ETPB; Internet of Things (IoT)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="264535">
                <text>Springer Science and Business Media Deutschland GmbH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="264536">
                <text>ISSN: 18650929; ISBN: 978-303184393-8;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264537">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264538">
                <text>Conference paper</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264539">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="17931" public="1" featured="0">
    <collection collectionId="15">
      <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="44496">
                  <text>Book Chapter</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="27">
      <name>Book Chapter</name>
      <description>Faculty Publications- Book Chapter</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="147134">
                <text>IoT-Enabled Analysis of COVID Data: Unveiling Insights from Temperature, Pulse Rate, and Oxygen Measurements</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147135">
                <text>COVID-19; Health monitoring systems; IoT-enabled analysis; Measurements; Sensors; Temperature-pulse rate-oxygen</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147136">
                <text>The COVID-19 pandemic has forced unparalleled transformation on healthcare systems around the world, demanding new and improved approaches for effective monitoring and diagnosis. In this context, we present a study titled IoT-Enabled Analysis of COVID Data: Unveiling Insights from Temperature, Pulse Rate, and Oxygen Measurements. The global impact of COVID-19, with millions of confirmed cases and fatalities, underscores the urgency of finding efficient monitoring solutions. To address this crisis, IoT-Enabled Health Monitoring Systems have emerged as a promising tool for remote patient monitoring and infection risk reduction. These systems leverage sensors to collect real-time data on the temperature, pulse rate, and oxygen saturation levels of the subject. The integration of a mobile application enables immediate access to this critical health information. In this study, we explore the use of IoT systems, which have demonstrated accuracy comparable to other devices on the market. By leveraging these technologies, we aim to provide healthcare professionals with valuable insights into patients health status, aiding in early detection, monitoring, and timely intervention. Our research contributes to the efforts to battle the COVID-19 pandemic by highlighting the potential of IoT-enabled monitoring systems in enhancing healthcare delivery, reducing infection risks, and ultimately saving lives.  2024 Scrivener Publishing LLC.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147137">
                <text>John J.; Kumar K.P.; Murthy H.</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="147138">
                <text>Internet of Things in Bioelectronics: Emerging Technologies and Applications, pp. 297-310.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="147139">
                <text>wiley</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="147140">
                <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="147141">
                <text>&lt;a href="https://doi.org/10.1002/9781394241903.ch14" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1002/9781394241903.ch14&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85208311870&amp;amp;doi=10.1002%2F9781394241903.ch14&amp;amp;partnerID=40&amp;amp;md5=d1aab72927d0255ee294912ae7e89722" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85208311870&amp;amp;doi=10.1002%2f9781394241903.ch14&amp;amp;partnerID=40&amp;amp;md5=d1aab72927d0255ee294912ae7e89722&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="147142">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="147143">
                <text>ISBN: 978-139424190-3; 978-139424187-3</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="147144">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147145">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147146">
                <text>Book chapter</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="147147">
                <text>John J., Computer Science and Engineering, School of Engineering and Technology, CHRIST (Deemed to be University), Kengeri Campus, Karnataka, Bangalore, India; Kumar K.P., Computer Science and Engineering, School of Engineering and Technology, CHRIST (Deemed to be University), Kengeri Campus, Karnataka, Bangalore, India; Murthy H., Electronics and Communication Engineering, School of Engineering and Technology, CHRIST (Deemed to be University), Kengeri Campus, Karnataka, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26572" public="1" featured="0">
    <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="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="265501">
                <text>Kodavathungal Mohammed, Isha Fathima; Mathew, Joswin Joseph; Nagaraju, Shamanth</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="265502">
                <text>IoT-Enabled Smart Breath Analyzer for Real-Time Monitoring of Ammonia, Alcohol, and VOC Biomarkers for Early Disease Detection</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="265503">
                <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="265504">
                <text>Lecture Notes in Networks and Systems;Volume;1829 LNNS;pp.1-13</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="265505">
                <text>&lt;a href="https://doi.org/10.1007/978-3-032-18141-1_1" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-032-18141-1_1&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105031908808?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105031908808?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="265506">
                <text>Kodavathungal Mohammed I.F., Department of Information Technology, CHRIST University, Bangalore, India; Mathew J.J., Department of Information Technology, CHRIST University, Bangalore, India; Nagaraju S., Department of Computer Science and Engineering, CHRIST University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="265507">
                <text>Real-time monitoring of breath biomarkers such as ammonia, alcohol, and volatile organic compounds (VOCs) is important for early disease diagnosis of metabolic and organ-related diseases. Traditional disease diagnosis techniques are invasive, time-consuming, expensive and not suitable for using in remote areas. To overcome these limitations, this paper proposes the design and development of an IoT-based Smart Breath Analyzer for real-time monitoring and analysis of ammonia, alcohol, and volatile organic compounds (VOC) concentration present in exhaled human breath. The system consists of different kinds of gas sensors connected to an ESP32 microcontroller for measuring gas concentration, which is processed and sent to Blynk application via Wi-Fi for visualization and disease prediction. A trained machine learning model is used in the system which classifies biomarker patterns that may be associated with conditions such as kidney disorders, respiratory issues, or alcohol influence, based on literature-derived thresholds. The system is presented as a proof-of-concept screening tool rather than a clinical diagnostic solution. The results are showed on an OLED display and accessed via a mobile app developed using the Blynk IoT platform. This non-invasive, affordable, and scalable solution improves continuous health monitoring and early diagnosis.  The Author(s), under exclusive license to Springer Nature Switzerland AG 2026.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="265508">
                <text>Ammonia; Breath Biomarkers; Disease Prediction; Internet of Things; Real-Time Monitoring; Smart Healthcare; VOCs</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="265509">
                <text>Springer Science and Business Media Deutschland GmbH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="265510">
                <text>ISSN: 23673370; ISBN: 978-303218140-4;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="265511">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="265512">
                <text>Conference paper</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="265513">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26979" public="1" featured="0">
    <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="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="270776">
                <text>Varghese, Nisha; Shereef, Shafi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270777">
                <text>IoT-Enabled Smart Security Surveillance System for Farmland and Livestock Monitoring Using Computer Vision</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="270778">
                <text>01-01-2025</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="270779">
                <text>2025 IEEE International Conference on Electronics, Computing and Communication Technologies, CONECCT 2025;</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="270780">
                <text>&lt;a href="https://doi.org/10.1109/CONECCT65861.2025.11306883" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/CONECCT65861.2025.11306883&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105032663995?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105032663995?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="270781">
                <text>Varghese N., Christ University, Department of Computer Science, Bangalore, India; Shereef S., Jain University, Department of Cs &amp;amp; It, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270782">
                <text>Agriculture is the main source of income of every country and agriculture plays a critical role in sustaining human civilization by providing food, fuel, and other essential resources. Even though, the conflict between farmers and wildlife remains a significant challenge even today. It is essential to arrange the protection of fields and farms by deterring wild animals and predators without making harm to the wildlife. This study proposes a framework that can detect and classify animals or intruders or any natural calamities. The novelty of the study is deterring the wild animals using innocuous devices and chemical components instead of the harmful electric fences and other methods. Based on the classification it will take preventive measures and will send an alert to the Farmer. The preventive measures are ensuring that will not make any harm to the wild animals. The framework incorporated four major components PIR (Passive Infrared) Sensor, Raspberry Pi Camera, Scarecrow and GSM (Global System for Mobile Communications) Module. PIR Sensor detects an object, Raspberry Pi Camera captures the images and images classify the specific object, later based on the type of the animal the scare tactics will be applied by the scarecrow and if any unusual incident is happening like the presence of an intruder, fire or tornado the alert will send to the Farmer with the help of a GSM Module.  2025 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270783">
                <text>Computer Vision; GSM; IoT Scarecrow; Livestock Monitoring; PIR Sensor</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="270784">
                <text>Institute of Electrical and Electronics Engineers Inc.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="270785">
                <text>ISBN: 979-833150236-2;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270786">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270787">
                <text>Conference paper</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270788">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="19171" public="1" featured="0">
    <collection collectionId="16">
      <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="51377">
                  <text>Conference Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="164025">
                <text>IOT-Enabled Supply Chain Management for Increased Efficiency</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164026">
                <text>Artificial intelligence; Big Data; IoT; Supply chain management; Technology; Traditional supply chain</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164027">
                <text>Deep learning methods have demonstrated potential Supply chain is a set or group of people as well as companies responsible for producing goods and getting it to their consumers. The producers of the raw materials are the first links in the chain, and the vehicle that delivers the finished goods to the client is the last. Lower costs and higher productivity are the benefits of an efficient supply network, which emphasizes the importance of management of supply chain. The internet of things, or IoT, is a network of mechanical and digital technology that can communicate with one another and send data without the need for human contact. Smart items were included into the conventional supply chain system to increase intelligence, automation potential, and intelligent decision-making. The existing supply chain system is offering previously unforeseen chances to increase efficiency and reduce cost. The aim and motive of our research is to analyze the methods of supply chain management where the main elements of IoT in management of supply chain will be highlighted.   2024 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164028">
                <text>Nanjundan P.; James B.V.; George J.P.; Tiwari A.</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="164029">
                <text>TQCEBT 2024 - 2nd IEEE International Conference on Trends in Quantum Computing and Emerging Business Technologies 2024</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="164030">
                <text>Institute of Electrical and Electronics Engineers Inc.</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="164031">
                <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="164032">
                <text>&lt;a href="https://doi.org/10.1109/TQCEBT59414.2024.10545070" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/TQCEBT59414.2024.10545070&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85204479192&amp;amp;doi=10.1109%2FTQCEBT59414.2024.10545070&amp;amp;partnerID=40&amp;amp;md5=a96e756cb9fdf771f738697e811e2102" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85204479192&amp;amp;doi=10.1109%2fTQCEBT59414.2024.10545070&amp;amp;partnerID=40&amp;amp;md5=a96e756cb9fdf771f738697e811e2102&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="164033">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="164034">
                <text>ISBN: 979-835038427-7</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="164035">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164036">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="164037">
                <text>Conference paper</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="164038">
                <text>Nanjundan P., Christ (Deemed to Be University), Department of Data Science, India; James B.V., Christ (Deemed to Be University), Department of Commerce, India; George J.P., Christ (Deemed to Be University), Department of Data Science, India; Tiwari A., Christ (Deemed to Be University), Department of Commerce, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="23581" public="1" featured="0">
    <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="225182">
                <text>Kalva, Yamini; Babu, R. Ganesh; Sindhu, V.; Pran, S. Gokul; Srilakshmi, Garaga; Kavitha, C.T.; Shanmugam, Sathish Kumar; Bhoopathy, V.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="225183">
                <text>IoT-Integrated CNN Deep Learning for Automated Breast Cancer Detection and Diagnosis</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="225184">
                <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="225185">
                <text>Journal of Computer Science;Volume;22;Issue;4;pp.1218-1230</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="225186">
                <text>&lt;a href="https://doi.org/10.3844/jcssp.2026.1218.1230" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.3844/jcssp.2026.1218.1230&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105038163531?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105038163531?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="225187">
                <text>Kalva Y., Sri Ramachandra Faculty of Engineering and Technology, Sri Ramachandra Institute of Higher Education and Research, Chennai, India; Babu R.G., Department of Electronics and Communication Engineering, Koneru Lakshmaiah Education Foundation, Andhra Pradesh, Guntur, India; Sindhu V., Department of Computer Science, Christ University, Karnataka, Bangalore, India; Pran S.G., Department of Computer Science and Engineering, Vel Tech Rangarajan Dr. SagunthalaR&amp;amp;D Institute of Science and Technology, Avadi, Chennai, India; Srilakshmi G., Department of Electronics and Communication Engineering, Aditya University, Andhra Pradesh, India; Kavitha C.T., Department of ECE, St. Joseph's Institute of Technology, Chennai, India; Shanmugam S.K., Department of EEE, M.Kumarasamy College of Engineering, Tamilnadu, Karur, India; Bhoopathy V., Department of Computer Science and Engineering, Sree Rama Engineering College, Tirupathi, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="225188">
                <text>Breast cancer continues to be a primary cause of death in women, requiring prompt and accurate diagnosis to enhance treatment results. Traditional diagnostic techniques depend on manual assessment, which leads to possible misclassification, significant inter-observer variability, and delays in decision-making. Current deep learning models, including CNNs, frequently experience feature loss, gradient declining and restricted adaptability to real-time data. To overcome these restrictions, we present a hybrid framework combining CNN and ResNet that merges deep learning-based feature extraction with real-time data collecting from IoT devices. The proposed approach utilises CNNs for preliminary feature extraction, ResNet for hierarchical learning with residual connections, and IoT for real-time patient monitoring and automatic notifications. The dataset undergoes preprocessing through normalisation, augmentation, and histogram equalisation to improve image quality and learning efficacy. The model is trained with cross-entropy loss and the Adam optimiser, guaranteeing stability and excellent performance. The evaluation results indicate a substantial enhancement compared to baseline models, with an accuracy of 97, an F1-score of 95.3, and a recall rate of 96.4%, exceeding traditional deep learning (90 accuracy) and CNN-based models (80% accuracy). The suggested model similarly minimises mistakes, with RMSE and MSE values declining to 1.2 and 1.6, respectively, signifying reduced misclassification rates. The inclusion of IoT facilitates instantaneous data transmission with little latency, hence improving clinical decision-making and minimising diagnostic delays. This advanced system facilitates automated and precise breast cancer detection, providing an innovative method for early diagnosis, optimised treatment planning, and improved patient outcomes, while ensuring data privacy and security through encryption and commitment to healthcare regulations.  2026 Yamini Kalva, R. Ganesh Babu, Sindhu V, S. Gokul Pran, Garaga Srilakshmi, Kavitha C T, Sathish Kumar Shanmugam and V. Bhoopathy. This open-access article is distributed under a Creative Commons Attribution (CC-BY) 4.0 license.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="225189">
                <text>Breast Cancer Detection; Convolutional Neural Network (CNN); Enhanced Cancer Classification; Health Automation; Internet of Things (IoT); Residual Neural Network (ResNet)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="225190">
                <text>Science Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="225191">
                <text>ISSN: 15493636;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="225192">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="225193">
                <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="225194">
                <text>All Open Access; Hybrid Gold Open Access</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="225195">
                <text>online</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26854" public="1" featured="0">
    <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="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="269163">
                <text>Singh, Jagendra; Saraswat, Mala; Upreti, Kamal; Agrawal, Gaurav; Hasan, Dler Salih; Shaik, Nazeer</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="269164">
                <text>IoT-Powered Health Monitoring System for Protecting Vital Organs Through Cloud-Based Diagnosis</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="269165">
                <text>01-01-2025</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="269166">
                <text>Lecture Notes in Electrical Engineering;Volume;1269;pp.169-181</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="269167">
                <text>&lt;a href="https://doi.org/10.1007/978-981-97-9515-4_13" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-981-97-9515-4_13&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105003894939?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105003894939?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="269168">
                <text>Singh J., School of Computer Science Engineering and Technology, Bennett University, Greater Noida, India; Saraswat M., School of Computer Science Engineering &amp;amp; Technology, Bennett University, Greater Noida, India; Upreti K., Department of Computer Science, CHRIST (Deemed to be University), Delhi-NCR, Ghaziabad, India; Agrawal G., Department of Computer Science Engineering (AI), KIET Group of Institution, Ghaziabad, India; Hasan D.S., Department of Computer Science &amp;amp; Information Tech., University of Salahaddin-Erbil, Erbil, Iraq; Shaik N., Department of Computer Science &amp;amp; Engineering, Srinivasa Ramanujan Institute of Technology Autonomous, Anantapur, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="269169">
                <text>The main objective of this research was the development and evaluation of an IoT- and machine learning-based health monitoring system capable of protecting patients vital organs through cloud diagnosis. This could be achieved by connecting a set of sensors, including temperature, pressure, heart rate, and oxygen sensors, to the patient and allowing them to communicate with the cloud to transmit real-time data via IoT technologies. The data could be further analyzed and predicted using cloud-based machine learning algorithms. This study investigated the performance of different machine learning models, including Artificial Neural Networks (ANN), Support Vector Machines (SVM), Naive Bayes (NB), and Negative Decision Trees (DT), for the purpose of patients health prediction based on the sensor data. After experimentation and evaluation, we found that the ANN model demonstrated the best predictive ability, with an accuracy level of 99.45%. The SVM, NB, and DT models also demonstrated good performance, with the accuracies of 96.5%, 94.34%, and 91.2%, respectively. Therefore, this research demonstrated that IoT and machine learning technologies could be successfully employed in healthcare for remote patient monitoring and timely prediction. The created system allows for real-time monitoring, which enables early prediction, potentially leading to improved patient outcomes, cost savings, and higher efficiency of provided care.  The Author(s), under exclusive license to Springer Nature Singapore Pte Ltd. 2025.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="269170">
                <text>Cloud-based diagnosis; Health monitoring; IoT; Machine learning; Sensor technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="269171">
                <text>Springer Science and Business Media Deutschland GmbH</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="269172">
                <text>ISSN: 18761100; ISBN: 978-981979514-7;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="269173">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="269174">
                <text>Conference paper</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="269175">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18960" public="1" featured="0">
    <collection collectionId="16">
      <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="51377">
                  <text>Conference Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="161083">
                <text>IoT-Powered Innovations in Renewable Energy Generation and Electric Drive</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161084">
                <text>This review explores the growing impact of the Internet of Things (IoT) on the energy sector, particularly in the context of renewable energy generation and electric drive systems. IoT technology has rapidly expanded into various sectors, including energy, smart cities, and industrial automation, revolutionizing monitoring, control, and management processes. In this paper, we examine the existing literature on IoT applications in energy systems, with a focus on smart grids. We also delve into the core IoT technologies, such as cloud computing and data analysis platforms, that underpin these innovations. Additionally, we address challenges associated with IoT implementation in the energy sector, notably privacy and security concerns, and suggest potential solutions, such as blockchain technology. Our findings provide valuable insights for energy policy-makers, economists, and managers, offering a comprehensive overview of how IoT can optimize energy systems. Furthermore, we highlight IoT's expanding role in renewable energy and electric drive applications, enhancing performance monitoring, management, and energy savings while also advancing research and education in engineering.  The Authors, published by EDP Sciences, 2024.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161085">
                <text>Mohammed Al-Nafei A.A.; Sharanya M.; Saxena A.; Janakiraman V.; Gehlot A.; Maheshwari A.</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="161086">
                <text>E3S Web of Conferences, Vol-540</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="161087">
                <text>EDP Sciences</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="161088">
                <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="161089">
                <text>&lt;a href="https://doi.org/10.1051/e3sconf/202454002018" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1051/e3sconf/202454002018&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85198117223&amp;amp;doi=10.1051%2Fe3sconf%2F202454002018&amp;amp;partnerID=40&amp;amp;md5=4d8da1c972b938f3b583018382dc1245" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85198117223&amp;amp;doi=10.1051%2fe3sconf%2f202454002018&amp;amp;partnerID=40&amp;amp;md5=4d8da1c972b938f3b583018382dc1245&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="161090">
                <text>All Open Access; Gold Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="161091">
                <text>ISSN: 25550403</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="161092">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161093">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161094">
                <text>Conference paper</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="161095">
                <text>Mohammed Al-Nafei A.A., Department of Nursing, Al-Zahrawi University College, Karbala, Iraq; Sharanya M., School of Business and Management, CHRIST(Deemed to Be University) Bannerghatta Road Campus, Bangalore, India; Saxena A., Department of Electronics and Communication Engineering, IES College of Technology, IES University, Madhya Pradesh, Bhopal, 462044, India; Janakiraman V., Department of Mech, Prince Shri Venkateshwara Padmavathy Engineering College, Chennai, 127, India; Gehlot A., Department of Electronics and Communication Engineering, Uttaranchal Institute of Technology, Uttaranchal University, Dehradun, 248007, India; Maheshwari A., Department of BCA, K.S.Rangasamy College of Arts and Science (Autonomous), Tiruchengode, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18298" public="1" featured="0">
    <collection collectionId="15">
      <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="44496">
                  <text>Book Chapter</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="27">
      <name>Book Chapter</name>
      <description>Faculty Publications- Book Chapter</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="152075">
                <text>IoVST: Internet of vehicles and smart traffic - Architecture, applications, and challenges</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152076">
                <text>The internet of things (IoT) is the network of sensors, devices, processors, and software, enabling connection, communication, and data transfer between devices. IoT is able to collect and analyze large amounts of data which can then be used to automate daily tasks in various fields. IoT holds the potential to revolutionise and create many opportunities in multiple industries like smart cities, smart transport, etc. Autonomous vehicles are smart vehicles that are able to navigate and move around on their own on a well-planned road.  2023, IGI Global.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152077">
                <text>Rajamohan K.; Rangasamy S.; Pinto N.A.; Manoj B.E.; Mukherjee D.; Shukla J.</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="152078">
                <text>Handbook of Research on Machine Learning-Enabled IoT for Smart Applications Across Industries, pp. 292-315.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="152079">
                <text>IGI Global</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="152080">
                <text>2023-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="152081">
                <text>&lt;a href="https://doi.org/10.4018/978-1-6684-8785-3.ch015" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.4018/978-1-6684-8785-3.ch015&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85168066871&amp;amp;doi=10.4018%2F978-1-6684-8785-3.ch015&amp;amp;partnerID=40&amp;amp;md5=a6169433eebffb100b71fdc63c0221fe" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85168066871&amp;amp;doi=10.4018%2f978-1-6684-8785-3.ch015&amp;amp;partnerID=40&amp;amp;md5=a6169433eebffb100b71fdc63c0221fe&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="152082">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="152083">
                <text>ISBN: 978-166848787-7; 1668487853; 978-166848785-3</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="152084">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152085">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152086">
                <text>Book chapter</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="152087">
                <text>Rajamohan K., CHRIST University (Deemed), India; Rangasamy S., CHRIST University (Deemed), India; Pinto N.A., CHRIST University (Deemed), India; Manoj B.E., CHRIST University (Deemed), India; Mukherjee D., CHRIST University (Deemed), India; Shukla J., CHRIST University (Deemed), India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18008" public="1" featured="0">
    <collection collectionId="15">
      <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="44496">
                  <text>Book Chapter</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="27">
      <name>Book Chapter</name>
      <description>Faculty Publications- Book Chapter</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="148192">
                <text>IPR in Stem Cell Research, Therapy, and Regenerative Medicine</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148193">
                <text>According to the World Trade Organization, intellectual property rights are rights given to persons over the creations of their minds. They usually give the creator an exclusive right over the use of his or her creation for a certain period. There is a critical need for fresh developments in the existing medical diagnostic techniques, therapy, pharmaceutical medications, and research, in a world where such a sizable number of people are afflicted with various ailments, some of which are fatal and still incurable. Pharmaceutical companies are developing novel and cutting-edge ways to treat diseases at an increasing rate. The major pharmaceutical corporations in the world, including Pfizer, Miltenyi, Biotec, AstraZeneca, and Mesoblast Limited are pursuing research in the area of stem cell and regenerative medicine. Regenerative medicine, stem cell research, and therapy are currently regarded as groundbreaking developments in the medical sciences. Understanding their intellectual property rights and the legal means through which these businesses can safeguard their discoveries becomes crucial. This paper will analyze the meaning of stem cell and regenerative medicines, the eligibility of IPR in Stem cell research under the Indian Patents Act, of 1970 and the morality and public issues related to the same.  2024 Taylor &amp;amp; Francis.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148194">
                <text>Doyil D.; Sharma M.</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="148195">
                <text>Intellectual Property Rights and Competition Law in India, pp. 30-41.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="148196">
                <text>Taylor and Francis</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="148197">
                <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="148198">
                <text>&lt;a href="https://doi.org/10.4324/9781003471523-3" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.4324/9781003471523-3&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85202115579&amp;amp;doi=10.4324%2F9781003471523-3&amp;amp;partnerID=40&amp;amp;md5=99179b03d4739ba8756dcbddf6c1e408" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85202115579&amp;amp;doi=10.4324%2f9781003471523-3&amp;amp;partnerID=40&amp;amp;md5=99179b03d4739ba8756dcbddf6c1e408&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="148199">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="148200">
                <text>ISBN: 978-104011327-1; 978-103273325-8</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="148201">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148202">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148203">
                <text>Book chapter</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="148204">
                <text>Doyil D., CHRIST (Deemed to be University), Delhi-NCR, India; Sharma M., School of Law, Justice, and Governance, Gautam Buddha University, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14922" public="1" featured="0">
    <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="105711">
                <text>IPWM Based IBMSC DC-AC Converter Using Solar Power for Wide Voltage Conversion System; [Convertisseur DC-AC IBMSC bassur l'IPWM et utilisant l'ergie solaire pour un syste de conversion large tension]</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105712">
                <text>This article proposes isolated bidirectional micro dc-ac single phase controlled (IBMSC) converter based on in-phase-voltage pulsewidth modulation (IPWM). This resonant IPWM converter, ratio of voltage conversion can be controlled from 0 to ?. So, this converter is highly referred for huge range voltage conversion. However, voltage conversion ratio determines power transfer direction and duty ratio. Power flow direction and duty cycle value can be varying smoothly, so it is suitable for dc-ac bidirectional power conversion application. Inverter mode and also rectifier mode are possible from bidirectional operation, which is controlled by a unified current controller. The proposed solution can achieve smooth switching grid operation with high efficiency. Working principle, design procedure, control strategy, and characteristics of the proposed converter are implemented with a prototype model of power rating 500 W with a voltage range of 20-50 V to test the ability of withstanding. Performance, feasibility, and effectiveness of the proposed converter are tested with this hardware test-bench model.  2022 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105713">
                <text>Suresh K.; Parimalasundar E.</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="105714">
                <text>IEEE Canadian Journal of Electrical and Computer Engineering, Vol-45, No. 4, pp. 394-400.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="105715">
                <text>IEEE Canada</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="105716">
                <text>2022-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="105717">
                <text>&lt;a href="https://doi.org/10.1109/ICJECE.2022.3207873" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICJECE.2022.3207873&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85152801358&amp;amp;doi=10.1109%2FICJECE.2022.3207873&amp;amp;partnerID=40&amp;amp;md5=6ed32111baa1638c718bb6bb7141e49b" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85152801358&amp;amp;doi=10.1109%2fICJECE.2022.3207873&amp;amp;partnerID=40&amp;amp;md5=6ed32111baa1638c718bb6bb7141e49b&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="105718">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="105719">
                <text>ISSN: 26941783</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="105720">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105721">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105722">
                <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="105723">
                <text>Suresh K., The Department of EEE, Christ (deemed to be university), Bengaluru, 517102, India; Parimalasundar E., The Department of EEE, Sree Vidyanikethan Engineering College, Tirupati, 517102, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20191" public="1" featured="0">
    <collection collectionId="16">
      <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="51377">
                  <text>Conference Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="28">
      <name>Conference Paper</name>
      <description>Faculty Publications- Conference Papers</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="178266">
                <text>IRIS Data Classification using Genetic Algorithm Tuned Random Forest Classification</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178267">
                <text>Random Forest; Randomized CV</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178268">
                <text>Optimising hyper-parameters in Random Forest is a time-consuming undertaking for several academics as well as professionals. To acquire greater performance hyper-parameters, specialists should explicitly customize a series of hyper-parameter settings. The best outcomes from this manual setting are then modelled and implemented in a random forest algorithm. Several datasets, on the other side, need various prototypes or hyper-parameter combinations, which may be time-consuming. To solve this, we offered various machine learning models and classifiers for correctly optimising hyper-parameters. Both genetic algorithm-based random forest and randomised CV random forest were assessed on performance measures such as sensitivity, accuracy, specificity, and F1-score. Finally, when compared to randomised CV random forest, our suggested model genetic algorithm-based random forest delivers more incredible accuracy.   2022 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178269">
                <text>Athithan S.; Bhola A.; Mittal S.; Sambandam R.K.; Thaiyalnayaki S.; Swapna I.</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="178270">
                <text>Proceedings of International Conference on Technological Advancements in Computational Sciences, ICTACS 2022, pp. 321-326.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="178271">
                <text>Institute of Electrical and Electronics Engineers Inc.</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="178272">
                <text>2022-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="178273">
                <text>&lt;a href="https://doi.org/10.1109/ICTACS56270.2022.9987868" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICTACS56270.2022.9987868&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85146369274&amp;amp;doi=10.1109%2FICTACS56270.2022.9987868&amp;amp;partnerID=40&amp;amp;md5=9e6c7028299fb05a269eec5cc7b8f2c5" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85146369274&amp;amp;doi=10.1109%2fICTACS56270.2022.9987868&amp;amp;partnerID=40&amp;amp;md5=9e6c7028299fb05a269eec5cc7b8f2c5&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="178274">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="178275">
                <text>ISBN: 978-166547657-7</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="178276">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178277">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="178278">
                <text>Conference paper</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="178279">
                <text>Athithan S., Koneru Lakshmaiah Education Foundation, Department of Computer Science and Engineering, Andhra Pradesh, Vaddeswaram, India; Bhola A., Koneru Lakshmaiah Education Foundation, Department of Computer Science and Engineering, Andhra Pradesh, Vaddeswaram, India; Mittal S., Rd Engineering College, Department of Computer Science and Engineering, U.P, Ghaziabad, India; Sambandam R.K., Christ (Deemed to Be University), Department of Computer Science and Engineering, Bengaluru, India; Thaiyalnayaki S., Bharat Institute of Higher Education and Research, Department of Computer Science and Engineering, Chennai, India; Swapna I., Princeton Institute of Engineering and Tech for Women, Department of CSE, Telangana, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
