<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="23237" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/23237?output=omeka-xml" accessDate="2026-06-18T05:33:04+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="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>
