<?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=476&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-06-30T07:58:02+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>476</pageNumber>
      <perPage>20</perPage>
      <totalResults>16481</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="20870" 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="187668">
                <text>IOT Based Smart Agriculture System</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187669">
                <text>IOT WSN Smart Agriculture Gateway Sensors</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187670">
                <text>Smart agriculture is an emerging concept, because IOT sensors are capable of providing information about agriculture fields and then act upon based on the user input. In this Paper, it is proposed to develop a Smart agriculture System that uses advantages of cutting edge technologies such as Arduino, IOT and Wireless Sensor Network. The paper aims at making use of evolving technology i.e. IOT and smart agriculture using automation. Monitoring environmental conditions is the major factor to improve yield of the efficient crops. The feature of this paper includes development of a system which can monitor temperature, humidity, moisture and even the movement of animals which may destroy the crops in agricultural field through sensors using Arduino board and in case of any discrepancy send a SMS notification as well as a notification on the application developed for the same to the farmer's smartphone using Wi-Fi/3G/4G. The system has a duplex communication link based on a cellularInternet interface that allows for data inspection and irrigation scheduling to be programmed through an android application. Because of its energy autonomy and low cost, the system has the potential to be useful in water limited geographically isolated areas.  2018 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187671">
                <text>Sushanth G.; Sujatha 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="187672">
                <text>2018 International Conference on Wireless Communications, Signal Processing and Networking, WiSPNET 2018</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="187673">
                <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="187674">
                <text>2018-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="187675">
                <text>&lt;a href="https://doi.org/10.1109/WiSPNET.2018.8538702" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/WiSPNET.2018.8538702&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85059438120&amp;amp;doi=10.1109%2FWiSPNET.2018.8538702&amp;amp;partnerID=40&amp;amp;md5=e6990cabd517a03fe06f5758e17a3462" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85059438120&amp;amp;doi=10.1109%2fWiSPNET.2018.8538702&amp;amp;partnerID=40&amp;amp;md5=e6990cabd517a03fe06f5758e17a3462&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="187676">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="187677">
                <text>ISBN: 978-153863624-4</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="187678">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187679">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="187680">
                <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="187681">
                <text>Sushanth G., Department of ECE, Christ University, Bangalore, India; Sujatha S., Department of ECE, Christ University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2471" public="1" featured="0">
    <fileContainer>
      <file fileId="2110">
        <src>https://archives.christuniversity.in/files/original/780a734dc66d018be9e390989ca8655f.png</src>
        <authentication>ae8597b1fb62da5294ca14f6fc0ece85</authentication>
      </file>
    </fileContainer>
    <collection collectionId="9">
      <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="12354">
                  <text>Patents</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12355">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12356">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="23">
      <name>Patent</name>
      <description>Patents</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="15690">
                <text>IOT based smart energy theft detection and power monitoring system for smart homes /</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15691">
                <text>Physics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15692">
                <text>Patent Number: 202141035598, Applicant: Dr. Poornima G.&#13;
Energy is the essential utility needed. Thus, the management of energy use is a significant priority, as the enormous growth changes are sweeping the globe, and doing so is the best answer, beginning domestically. There are numerous difficulties in the existing home energy meter reading systems, such as construction problems, too little bandwidth, poor real-time, no fast two-way communication, etc. Therefore, based on wireless internet technology, a smart meter is suggested. An Arduino microcontroller and raspberry pi CPU are used for the suggested smart energy meters for house management.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15693">
                <text>N, Arul Kumar.</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="15694">
                <text>&lt;a href="https://drive.google.com/file/d/1jHhYmQ2ZEzyZVJS7U3mPaCI-jAcxCM63/view" target="_blank" title="IOT based smart energy theft detection and power monitoring system for smart homes /" rel="noreferrer noopener"&gt;https://drive.google.com/file/d/1jHhYmQ2ZEzyZVJS7U3mPaCI-jAcxCM63/view&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="15695">
                <text>Intellectual Property India</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="15696">
                <text>2021-04-10</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15697">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15698">
                <text>Patent</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2490" public="1" featured="0">
    <fileContainer>
      <file fileId="2129">
        <src>https://archives.christuniversity.in/files/original/9bfddac214b54b15bed55c2d0391e077.jpg</src>
        <authentication>96e0cb74b7edc75db27cde5309115286</authentication>
      </file>
    </fileContainer>
    <collection collectionId="9">
      <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="12354">
                  <text>Patents</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12355">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12356">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="23">
      <name>Patent</name>
      <description>Patents</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="15861">
                <text>IOT based smart green house system /</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15862">
                <text>Computer Science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15863">
                <text>Patent Number: 202111031077, Applicant: Dr. Vikas Kumar.&#13;
The Smart Green House concept has been brought into the agricultural area to promote plant development in a short period of time. With an IoT-enabled framework controlled by a Smart Green House Intelligence Decision Support System, the system's quality can be improved. The system uses multiple sensors strategically positioned throughout a greenhouse to make decisions about actions such as water supply and nutrition level. All of the sensors and control systems operate in an automated setting, allowing small farmers to benefit from the greenhouse technology.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15864">
                <text>N, Jayapandian.</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="15865">
                <text>&lt;a href="https://drive.google.com/file/d/1y8x4eL9HQ8Y-ZMIdLmkOCGYw9jAEo5j0/view" target="_blank" title="IOT based smart green house system /" rel="noreferrer noopener"&gt;https://drive.google.com/file/d/1y8x4eL9HQ8Y-ZMIdLmkOCGYw9jAEo5j0/view&lt;/a&gt;</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="15866">
                <text>2021-05-06</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15867">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="15868">
                <text>Patent</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20144" 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="177608">
                <text>IoT based Smart Poultry to Produce a Healthy Environment</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="177609">
                <text>Cloud. Poultry; Fire; Firebase; Notification; Sensor; Temperature</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="177610">
                <text>According to studies, there are approximately 850 million poultry birds across India, with an average of 30 million farmers working in the sector. In other words, a poultry farm is a trustworthy and long-term way to make money in India. However, managing a poultry farm is labour intensive due to the need for constant surveillance and control over a wide range of environmental factors. The actual implementation of this is significantly more complicated, expensive, and time-consuming. The paper suggested a smart poultry system that tries to provide the solution for all the issues. The health of poultry birds heavily relies on environmental parameters, so variables like temperature and humidity are measured and monitored continuously. The website was made so that poultry keepers may get reliable information about their birds' health and use that information to take the appropriate measures. Moreover, in the event of a crisis, such as a fire or the illness of a single bird, the owner will receive a notification. It is also possible to gather information about the poultry in the specified timespan. The Firebase cloud is used for wireless monitoring and managing the poultry system. The suggested automatic smart poultry system will make the birds healthy and it indirectly helps the owners to increase their profit with minimal human effort.   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="177611">
                <text>Sandhiya R.; Vamshi Mohana T.; Jothi B.; Agarwal J.; Kulshrestha N.; Sandhiya 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="177612">
                <text>6th International Conference on I-SMAC (IoT in Social, Mobile, Analytics and Cloud), I-SMAC 2022 - Proceedings, pp. 150-156.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="177613">
                <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="177614">
                <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="177615">
                <text>&lt;a href="https://doi.org/10.1109/I-SMAC55078.2022.9987330" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/I-SMAC55078.2022.9987330&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85146437463&amp;amp;doi=10.1109%2FI-SMAC55078.2022.9987330&amp;amp;partnerID=40&amp;amp;md5=42c2b8173d1fab0776a987f61fff4cea" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85146437463&amp;amp;doi=10.1109%2fI-SMAC55078.2022.9987330&amp;amp;partnerID=40&amp;amp;md5=42c2b8173d1fab0776a987f61fff4cea&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="177616">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="177617">
                <text>ISBN: 978-166546941-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="177618">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="177619">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="177620">
                <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="177621">
                <text>Sandhiya R., R M K College of Engineering and Technology, Department of Computer Science and Engineering, Tamil Nadu, Thiruvallur, 601206, India; Vamshi Mohana T., R B v R R Women's College, Department of Computer Science, Telangana, Hyderabad, 500027, India; Jothi B., Srm Institute of Science and Technology, Department of Computational Intelligence, Tamil Nadu, Kattankulathur, 603203, India; Agarwal J., Vardhaman College, Affiliated to M. J. P Rohilkhand University, Bijnor, Department of Zoology, Uttar Pradesh, Bareilly, 246701, India; Kulshrestha N., Christ Deemed to Be University-Delhi Ncr, Department of Commerce Finance and Accountancy, Uttar Pradesh, Ghaziabad, 201003, India; Sandhiya S., Panimalar Engineering College, Department of Information Technology, Tamil Nadu, Chennai, 600123, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20774" 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="186333">
                <text>IoT Based Water Management Using HC-12 and Django</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="186334">
                <text>IoT; Relational Database; WSN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="186335">
                <text>Water is one of the important needs for a human being. Life on Earth is possible due to the presence of water on its surface. Even though 71% of Earth's surface is covered with water, the availability of water in certain areas is very less. So, the people in these areas must reserve water for ensuring a steady availability. These problems can be rectified with the help of Internet of Things (IOT). IOT is a global infrastructure with certain standards and communication protocols by which virtual and physical things can interact and exchange data by connecting to each other. In this paper, we propose a system for monitoring the availability of water, based on the water level in the storage system. Water level is measured with the help of a waterproof ultrasonic sensor and when the level reaches a threshold value, a notification is sent to the user or to the vendor to take the necessary action. The live feed data is sent to a relational database for storing and analyzing the data to predict when the water will run out, and to make sure that the water storage system gets refilled before that point of time. After processing the raw data from the sensors, the system can generate a fusion chart that can show or indicate the amount of water inside each storage system. With this, the user can have an idea of how much water is left in each of the storage system. The main aim of the proposed system is to showcase the functionalities and uses of different sensors and modules used in an IOT based system with the application of Wireless Sensor Network (WSN). In this present scenario, the world is filled with data both relevant and irrelevant, wherein the data for predicting a water crisis is less. So, through the proposed system we are generating a dataset for the prediction of a water crisis in an organization or a community.  2019 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="186336">
                <text>Jose D.P.; Dsouza A.L.; Thomas A.A.; Daniel D.</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="186337">
                <text>2019 International Conference on Data Science and Communication, IconDSC 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="186338">
                <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="186339">
                <text>2019-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="186340">
                <text>&lt;a href="https://doi.org/10.1109/IconDSC.2019.8816917" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/IconDSC.2019.8816917&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85072778915&amp;amp;doi=10.1109%2FIconDSC.2019.8816917&amp;amp;partnerID=40&amp;amp;md5=ae05a6272726449a749f7e4e94039d8f" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85072778915&amp;amp;doi=10.1109%2fIconDSC.2019.8816917&amp;amp;partnerID=40&amp;amp;md5=ae05a6272726449a749f7e4e94039d8f&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="186341">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="186342">
                <text>ISBN: 978-153869319-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="186343">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="186344">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="186345">
                <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="186346">
                <text>Jose D.P., Department of Computer Science and Engineering, CHRIST, Deemed to be University, Bangalore, India; Dsouza A.L., Department of Computer Science and Engineering, CHRIST, Deemed to be University, Bangalore, India; Thomas A.A., Department of Electronics and Communication, CHRIST, Deemed to be University, Bangalore, India; Daniel D., Department of Computer Science and Engineering, CHRIST, Deemed to be University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="23755" 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="227603">
                <text>Reddy, D. Ramesh; Praveenraj, D. David Winster; Chandramowleeswaran, G.; Karnan, C.; Vallikkannu, M.; Murthy, A. Ganesa</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="227604">
                <text>IoT Behavioural Analytics for Retail Engagement</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="227605">
                <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="227606">
                <text>International Academic Journal of Science and Engineering;Volume;12;Issue;4;pp.166-175</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="227607">
                <text>&lt;a href="https://doi.org/10.71086/IAJSE/V12I4/IAJSE1286" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.71086/IAJSE/V12I4/IAJSE1286&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105036517087?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105036517087?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="227608">
                <text>Reddy D.R., Department of Electronics and Communication Engineering, Vallurupalli Nageswara Rao Vignana Jyothi Institute of Engineering and Technology, Telangana, Hyderabad, India; Praveenraj D.D.W., School of Business and Management, Christ University, Karnataka, Bangalore, India; Chandramowleeswaran G., Vel Tech Rangarajan Dr. Sagunthala R&amp;amp;D Institute of Science and Technology, Tamil Nadu, Chennai, India; Karnan C., Department of Mathematics, K. Ramakrishnan College of Engineering, Tamil Nadu, Tiruchirappalli, India; Vallikkannu M., Vel Tech Rangarajan Dr. Sagunthala R&amp;amp;D Institute of Science and Technology, Tamil Nadu, Chennai, India; Murthy A.G., Library and Information Science, Vels Institute of Science, Technology and Advanced Studies (VISTAS), Pallavaram, Chennai, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="227609">
                <text>The modern-day retailing world is struggling to provide real-time and hyper-personalised customer interaction in the context of fragmented behavioural data, sluggish analytics, and in-store interventions that are generic. Current Internet of Things (IoT) retail systems are mainly focused on inventory and transactional insights and do not capture more in-depth behavioural and emotional indicators that affect purchase intent and satisfaction. In this context, this paper will suggest an Internet of Things (IoT)-Based Behavioural Analytics Platform to Hyper-Personalised Consumer Engagement in Retail Management (IBAPS-RM). The framework incorporates multimodal Internet of Things (IoT) sensing, edge computing, and cloud intelligence in creating Multimedia Behavioural Digital Twins (Behavioural Digital Twin (BDT) that dynamically change in response to contextual, environmental, and Interaction-driven information. One of the most notable novelties is the Behavioural Fusion Neural Unit (BFNU) (Behavioural Fusion Neural Unit (BFNU)), that conducts real-time sensor fusion between gaze movement, dwell time, gestures, proximity, and purchase latency to determine behavioural intent and launch micro-personalised interventions in the form of adaptive light, context sensitive offers and personalised digital content. Reinforcement learning also enhances engagement policies through continuous optimisation based on feedback. Experimental analysis shows that IBAPS-RM has better engagement intelligence, with over 93% of personalisation accuracy, 73% shorter decision latency, and 64% higher conversion rate than traditional Internet of Things (IoT) retail systems. The suggested solution improves responsiveness, consumer experience, and operational effectiveness, and promotes privacy-conscious behavioural modelling. In general, IBAPS-RM creates a dynamic, proactive retail intelligence paradigm that dedicates behavioural inference to real-time engagement delivery.  2025, International Academic Institute for Science and Technology. All rights reserved.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="227610">
                <text>Behavioural Analytics; Behavioural Digital Twins (BDTs); Behavioural Fusion Neural Unit (BFNU); Edge Computing; Hyper-Personalisation; IoT-Driven Retail Analytics; Real-Time Consumer Engagement; Reinforcement Learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="227611">
                <text>International Academic Institute for Science and Technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="227612">
                <text>ISSN: 24543896;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="227613">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="227614">
                <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="227615">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="42">
            <name>Format</name>
            <description>The file format, physical medium, or dimensions of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="227616">
                <text>online</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="20004" 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="175657">
                <text>IoT Cloud Systems: A Survey</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="175658">
                <text>Cloud Computing; IoT; Survey</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="175659">
                <text>IoT has gained a massive prevalence in the last decade. Various businesses are leveraging IoT Applications for industrial and commercial use cases. IoT also presents use cases in research and academia. However, setting up IoT Systems is complex due to the distributed and multi-disciplinary nature of IoT Systems. As a direct consequence of this complexity, the entire service industry has emerged that assists users to deploy and manage IoT systems. This paper aims to survey some of the Cloud management systems that help simplify and shorten the deployment process of IoT Systems.   2023 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="175660">
                <text>Nagendran G.A.; Raj R.J.S.; Priya C.S.R.; Singh 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="175661">
                <text>Proceedings - 5th International Conference on Smart Systems and Inventive Technology, ICSSIT 2023, pp. 415-418.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="175662">
                <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="175663">
                <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="175664">
                <text>&lt;a href="https://doi.org/10.1109/ICSSIT55814.2023.10060983" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICSSIT55814.2023.10060983&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85150683096&amp;amp;doi=10.1109%2FICSSIT55814.2023.10060983&amp;amp;partnerID=40&amp;amp;md5=80b90132e383cab3d946ba67b557a671" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85150683096&amp;amp;doi=10.1109%2fICSSIT55814.2023.10060983&amp;amp;partnerID=40&amp;amp;md5=80b90132e383cab3d946ba67b557a671&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="175665">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="175666">
                <text>ISBN: 978-166547467-2</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="175667">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="175668">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="175669">
                <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="175670">
                <text>Nagendran G.A., Dept. Of. Ise, Cmr Institute of Technology, Bengaluru, India; Raj R.J.S., Dept. of Engineering, Design, Information and Communications Technology, Bahrain Polytechnic, PO BOX 33349, Isa Town, Bahrain; Priya C.S.R., Dept. of Computer Science and Engineering, Christ (Deemed to Be University), Bangalore, India; Singh H., Dept. Of. Ise, Cmr Institute of Technology, Bengaluru, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18493" 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="154687">
                <text>IOT Contribution in Construct of Green Energy</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154688">
                <text>Biogas; Energy efficiency; Geothermal energy; Green energy; Internet of Things; IoT applications; Natural resources; Solar energy; Wind energy; Wireless sensor</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154689">
                <text>Energy derived from natural sources, such as sunlight, wind, and water, is called green energy. Green energy is a source of energy derived from clean sources such as solar, wind, geothermal, and biomass. The environment benefts from green energy because green energy replaces the harmful effects of fossil fuels with more environmentally friendly options. Green energy sources release far fewer greenhouse gases, as well as little or no air pollutants when looked at in their full life cycle. Taking steps to reduce air pollution benefts not only the planet but also human and animal health. Increasing reliance on the Internet of Things (IoT) has helped modernize the energy industry. Sensor attached to generation, transmission, and distribution equipment is used in IoT applications in green energy production. Alternative energy offers several benefts over traditional energy options. As the demand for clean energy grows and environmental prudence becomes the norm, Internet of Things solutions for energy management keep developing. Using the Internet of Things today benefts green energy, enabling companies in this sector to make the most of their data, and improves effciency and safety.  The Author(s), under exclusive license to Springer Nature Switzerland AG 2023.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154690">
                <text>Nanjundan P.; Jaisingh W.</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="154691">
                <text>Power Systems, pp. 119-145.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="154692">
                <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="154693">
                <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="154694">
                <text>&lt;a href="https://doi.org/10.1007/978-3-031-15044-9_6" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-031-15044-9_6&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85152470463&amp;amp;doi=10.1007%2F978-3-031-15044-9_6&amp;amp;partnerID=40&amp;amp;md5=b2420f6398ff99f8835d8892914c9792" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85152470463&amp;amp;doi=10.1007%2f978-3-031-15044-9_6&amp;amp;partnerID=40&amp;amp;md5=b2420f6398ff99f8835d8892914c9792&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="154695">
                <text>All Open Access; Hybrid Gold Open Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="154696">
                <text>ISSN: 16121287</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="154697">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154698">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154699">
                <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="154700">
                <text>Nanjundan P., Department of Data Science, Christ University, Pune, Lavasa, India; Jaisingh W., School of Computing Science and Engineering, VIT Bhopal University, Madhya Pradesh, Bhopal, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2684" public="1" featured="0">
    <fileContainer>
      <file fileId="2323">
        <src>https://archives.christuniversity.in/files/original/059c53f2ac23a40b5063e1441a4bc2b1.jpg</src>
        <authentication>0b6dfeeadbd8dbf97f5aef738454f6b9</authentication>
      </file>
    </fileContainer>
    <collection collectionId="9">
      <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="12354">
                  <text>Patents</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12355">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="12356">
                  <text>Patent</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="23">
      <name>Patent</name>
      <description>Patents</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="17599">
                <text>IOT driven automated water quality monitoring and removal of unpleasant smell from wastewater system for smart city /</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17600">
                <text>Chemical</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17601">
                <text>Patent Number: 202241015394, Applicant: Geetha V.&#13;
Water pollution has become one of the most serious threats in recent years, as drinking water has become contaminated and polluted. Polluted water can cause a variety of diseases in humans and animals, affecting the ecosystem's life cycle. If water pollution is detected early on, appropriate measures can be implemented, and critical situations can be avoided. To ensure a steady supply of pure water, the water's quality should be monitored in real time. With advancements in sensors, communication, and Internet of Things (IoT) technology, smart solutions for monitoring water pollution are becoming increasingly important.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17602">
                <text>M, Balamurugan.</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="17603">
                <text>&lt;a href="https://drive.google.com/file/d/1nbW0uFMJARTJs5RfFwITzuykOQuhb1PB/view" target="_blank" title="IOT driven automated water quality monitoring and removal of unpleasant smell from wastewater system for smart city /" rel="noreferrer noopener"&gt;https://drive.google.com/file/d/1nbW0uFMJARTJs5RfFwITzuykOQuhb1PB/view&lt;/a&gt;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="17604">
                <text>Intellectual Property India</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="17605">
                <text>2022-05-19</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17606">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="17607">
                <text>Patent</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18354" 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="152816">
                <text>IoT Enabled Energy Optimization Through an Intelligent Home Automation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152817">
                <text>Automation; IoT; Optimization; Wi-Fi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152818">
                <text>The benefit of IoT devices is that they allow for automation; nevertheless, billions of connected devices connected with one another waste a substantial amount of energy. IoT systems will have difficulty in wide adoption if the energy requirements are not adequately managed. This study proposes a solution for IoT devices to regulate their energy consumption. Both hardware and software aspects are taken into consideration. Using a mobile computer or smartphone with Internet connectivity to interact with actual scenarios has grown more prevalent as technology has advanced over the years. An intelligent home automation system based on android applications has been developed to save electricity and human energy. This study aims to create comprehensive Energy optimization through intelligent home automation utilizing widely available mobile applications and Wi-Fi technologies. The devices are turned on and off using Wi-Fi. Intelligent home, in the area of electronics, automation is the most purposely misused term. Numerous technological revolutions have occurred as a result of this demand for automation. These were more essential than any other technologies due to their ease of use. These can be used in place of household current switches, resulting in sparks and, in rare instances, such as fires. A unique energy optimization system was developed to control household appliances while taking advantage of Wi-Fi benefits.  2023, Bentham Books imprint.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152819">
                <text>Chitra Kiran N.; Viswanatha Rao J.; Aurelia S.; Skanda M.G.; Lakshminarayana 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="152820">
                <text>Pragmatic Internet of Everything (IOE) for Smart Cities: 360-Degree Perspective, pp. 108-124.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="152821">
                <text>Bentham Science Publishers</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="152822">
                <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="152823">
                <text>&lt;a href="https://doi.org/10.2174/9789815136173123010008" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.2174/9789815136173123010008&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85210839980&amp;amp;doi=10.2174%2F9789815136173123010008&amp;amp;partnerID=40&amp;amp;md5=950f65831a129b07ffeb355a361177d1" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85210839980&amp;amp;doi=10.2174%2f9789815136173123010008&amp;amp;partnerID=40&amp;amp;md5=950f65831a129b07ffeb355a361177d1&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="152824">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="152825">
                <text>ISBN: 978-981513617-3; 978-981513619-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="152826">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152827">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="152828">
                <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="152829">
                <text>Chitra Kiran N., Department of Electronics and Communication Engineering, Alliance University, Karnataka, Bengaluru, India; Viswanatha Rao J., VNR Vignana Jyothi Institute of Engineering and Technology, Hyderabad, India; Aurelia S., Department of Computer Science, CHRIST University, Karnataka, Bengaluru, India; Skanda M.G., Department of Industrial &amp;amp; Production Engineering, JSS S&amp;amp;T University, SJCE, Mysore, India; Lakshminarayana M., Department of Medical Electronics Engineering, M S Ramaiah Institute Of Technology, Karnataka, Bengaluru, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="14712" 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="102791">
                <text>IoT enabled lung cancer detection and routing algorithm using CBSOA-based ShCNN</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102792">
                <text>cancer detection; Internet of Things; routing; shepherd convolutional neural network; social optimization algorithm</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102793">
                <text>The Internet of Things (IoT) has tremendously spread worldwide, and it influenced the world through easy connectivity, interoperability, and interconnectivity using IoT devices. Numerous techniques have been developed using IoT-enabled health care systems for cancer detection, but some limitations exist in transmitting the health data to the cloud. The limitations can be accomplished using the proposed chronological-based social optimization algorithm (CBSOA) that effectively transmits the patient's health data using IoT network, thereby detecting lung cancer in an effective way. Initially, nodes in the IoT network are simulated such that patient's health data are collected, and for transmission of such data, routing is performed in order to transmit the health data from source to destination through a gateway based on cloud service using CBSOA. The fitness is newly modeled by assuming the factors like energy, distance, trust, delay, and link quality. Finally, lung cancer detection is carried out at the destination point. At the destination point, the acquired input data is fed to preprocessing phase to make the data acceptable for further mechanism using data normalization. Once the feature selection is done using Canberra distance, then the lung cancer detection is performed using shepard convolutional neural network (ShCNN). The process of routing as well as training of ShCNN is performed using the CBSOA algorithm, which is devised by the inclusion of the chronological concept into the social optimization algorithm. The proposed approach has achieved a maximum accuracy of 0.940, maximum sensitivity of 0.941, maximum specificity of 0.928, and minimum energy of 0.452.  2022 John Wiley &amp;amp; Sons Ltd.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102794">
                <text>Gnanasigamani Samuel Raj E.S.; Diana Jeba Jingle I.; Maram B.; Ananth J.P.</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="102795">
                <text>International Journal of Adaptive Control and Signal Processing, Vol-37, No. 1, pp. 224-243.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="102796">
                <text>John Wiley and Sons 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="102797">
                <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="102798">
                <text>&lt;a href="https://doi.org/10.1002/acs.3518" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1002/acs.3518&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85142271210&amp;amp;doi=10.1002%2Facs.3518&amp;amp;partnerID=40&amp;amp;md5=836bc98d730fdaad1d4d8d387d52e80e" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85142271210&amp;amp;doi=10.1002%2facs.3518&amp;amp;partnerID=40&amp;amp;md5=836bc98d730fdaad1d4d8d387d52e80e&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="102799">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="102800">
                <text>ISSN: 8906327; CODEN: IACPE</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="102801">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102802">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="102803">
                <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="102804">
                <text>Gnanasigamani Samuel Raj E.S., Department of Computer Science and Engineering, Thiagarajar College of Engineering, Tamil Nadu, Madurai, India; Diana Jeba Jingle I., Department of Computer Science and Engineering, Christ University, Karnataka, Bengaluru, India; Maram B., Department of Computer Science and Engineering, Chitkara University School of Engineering and Technology, Chitkara University, Himachal Pradesh, Baddi, India; Ananth J.P., Department of Computer Science and Engineering, Sri Krishna College of Engineering and Technology, Tamil Nadu, Coimbatore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26944" 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="270322">
                <text>Ganachar, Sanjana R; Sharon Roji Priya, C.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270323">
                <text>IoT Enabled Patient Monitoring System with Fall 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="270324">
                <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="270325">
                <text>Proceedings of 2025 6th International Conference on Communication, Computing and Industry 6.0, C2I6 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="270326">
                <text>&lt;a href="https://doi.org/10.1109/C2I666499.2025.11366952" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/C2I666499.2025.11366952&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105034385519?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105034385519?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="270327">
                <text>Ganachar S.R., Christ University, School of Engineering and Technology, Department of CSE, Bengaluru, India; Sharon Roji Priya C., Christ University, School of Engineering and Technology, Department of CSE, Bengaluru, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270328">
                <text>The growth in demand for remote and prolonged healthcare monitoring has led to a strong growth in adoption of wearable technologies and Internet of Things -based solutions. These technologies are meant to help solve real-time health supervision challenges, particularly for older adults and those suffering from long-term conditions, through reduced need for constant onsite medical care. Here, we describe the design and deployment of an intelligent health monitoring system that utilizes low-cost sensors and wireless communication to enable real-time, continuous monitoring of important physiological and environmental parameters. The suggested system combines an array of sensors: the DHT11 sensor to measure environmental temperature and humidity, the MAX30102 sensor for heart rate and SpO2 monitoring in real-time, and the MPU6050 sensor to sense body posture, orientation, and motion. The sensors are connected to an ESP8266 Wi-Fi MCU, which serves as the hub node for data sensing and transmission. Sensor data that is aggregated is processed locally and then sent to a cloud-based platform for analysis, storage, and visualization. To improve the functionality of the system, the system utilizes a cloud-hosted rule-based Artificial Intelligence (AI) engine for interpreting physiological patterns, identifying signs of abnormal health conditions at an early stage, and offering context-aware, personalized health suggestions. The platform provides dual output modes for added accessibility and reliability: an OLED display for local feedback, and an offdevice cloud dashboard for caregivers and health workers to view patients in real time. This study demonstrates the potential for the integration of embedded systems, cloud computing, and light AI methods to make predictive health analytics and facilitate proactive healthcare interventions possible. Through emphasizing modular design, low power, and scalability, the system is particularly suitable for deployment in elderly care, post-surgery recovery, and chronic disease management. Experimental assessments suggest that the system offers a credible, cost-efficient alternative.  2025 IEEE.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270329">
                <text>chronic disease management; cloud computing; DHT11; elderly care; ESP8266; Internet of Things (IoT); MAX30102; MPU6050; real-time health analytics; remote patient monitoring; rule-based AI; wearable health monitoring</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="270330">
                <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="270331">
                <text>ISBN: 979-833150240-9;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270332">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="270333">
                <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="270334">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18699" 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="157507">
                <text>IoT Framework, Architecture Services, Platforms, and Reference Models</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157508">
                <text>Actuators; Architecture; Connected devices; Frameworks; Internet of things (IoT); Platforms; Sensors</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157509">
                <text>Internet of things (IoT) is spawning a twirl in the world of connected devices by aiding the devices to connect, compute, and coordinate with each other. While the concept of IoT is still embryonic, its outcomes are trailblazing. IoT acts as a facilitator in creating a smart world by connecting devices through sensors and actuators to the Internet. The acceptance of IoT in various sectors indicates that the partakers in an IoT ecology are diverse. This demands common functionalities, interoperability standards, and network protocols across sectors. But there exists an extremity of incongruency in devices, capabilities, and network protocols, and therefore it is imperative to have a complete reference architecture model that necessitates the existing diversities and defines a new monody for the IoT environment. The lack of standard and uniform architectural knowledge, frameworks, and platforms is presently resisting the researchers to reap the benefits that the Internet of things (IoT) offers. This chapter summarizes various Internet of things frameworks, architectures, platforms, and reference models and thereby paves way for businesses to build IoT on it.  2022, The Author(s), under exclusive license to Springer Nature Switzerland AG.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157510">
                <text>Mahalakshmi S.; Desai K.</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="157511">
                <text>EAI/Springer Innovations in Communication and Computing, pp. 37-59.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="157512">
                <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="157513">
                <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="157514">
                <text>&lt;a href="https://doi.org/10.1007/978-3-030-77528-5_2" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-030-77528-5_2&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85120530821&amp;amp;doi=10.1007%2F978-3-030-77528-5_2&amp;amp;partnerID=40&amp;amp;md5=161e5ecff7ce1de37eebe9a4aa5e01b2" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85120530821&amp;amp;doi=10.1007%2f978-3-030-77528-5_2&amp;amp;partnerID=40&amp;amp;md5=161e5ecff7ce1de37eebe9a4aa5e01b2&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="157515">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="157516">
                <text>ISSN: 25228595</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="157517">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157518">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157519">
                <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="157520">
                <text>Mahalakshmi S., CMS Business School, Jain University, Bangalore, India; Desai K., Department of Professional Studies, CHRIST (Deemed to be University), Bengaluru, Karnataka, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="17964" 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="147587">
                <text>IoT in schools: Revolutionizing education through smart technology</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147588">
                <text>The Internet of Things (IoT) is rapidly transforming various sectors, and education is no exception. This chapter explores the potential and applications of IoT technology in the education sector, shedding light on how it can revolutionize teaching, learning, and overall school management. By seamlessly integrating smart devices and applications into the classroom environment, IoT creates an interconnected and efficient learning ecosystem. The discussion covers the current state of IoT adoption in education, highlighting the benefits, challenges, and future prospects of this technological integration.  2025 selection and editorial matter, Adesh Kumar, Surajit Mondal, Gaurav Verma, and Prashant Mani; individual chapters, the contributors.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147589">
                <text>Kaushik P.</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="147590">
                <text>Embedded Devices and Internet of Things: Technologies and Applications, pp. 230-241.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="147591">
                <text>CRC Press</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="147592">
                <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="147593">
                <text>&lt;a href="https://doi.org/10.1201/9781003510420-13" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1201/9781003510420-13&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85205168454&amp;amp;doi=10.1201%2F9781003510420-13&amp;amp;partnerID=40&amp;amp;md5=7424baf65361f012f20bae0606eaf8d5" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85205168454&amp;amp;doi=10.1201%2f9781003510420-13&amp;amp;partnerID=40&amp;amp;md5=7424baf65361f012f20bae0606eaf8d5&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="147594">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="147595">
                <text>ISBN: 978-104011389-9; 978-103260600-2</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="147596">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147597">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="147598">
                <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="147599">
                <text>Kaushik P., CHRIST (Deemed to be University), Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18497" 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="154742">
                <text>IoT Infrastructure to Energize Electromobility</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154743">
                <text>Battery electric vehicles; Charging capabilities; Cloud platform; Communication technology; Edge computing; Electromobility; Energy consumption; Energy production; Information; IoT architecture; Power grid</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154744">
                <text>Mobile technology is becoming more sophisticated as it advances. A comparison of different mobility scenarios was conducted. This chapter examined how electric vehicles interact with local energy systems in Stuttgart. Utilizing a travel demand model, a charging profle based on mobility patterns was generated for electric vehicles. During a quarter, charging demand and standard household load profles were used to analyze peak hour load fow for 349 households. Considering that peak loads and charging capacity are usually separated in time, greater charging capacity might lead to lower utilization of transformers. Furthermore, a study was conducted to determine if the existing infrastructure was adequate for future demand, focusing on substation transformer reserves. Electromobility is a rapidly growing and evolving application domain of the Internet of Things, with a huge market potential in various areas. It incorporates many stakeholders  from manufacturers to the players of the energy market  with all sorts of physical and virtual resources. It is essential to allow these devices and systems to collaborate to create advanced e-mobility services.  The Author(s), under exclusive license to Springer Nature Switzerland AG 2023.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154745">
                <text>Jaisingh W.; Nanjundan P.</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="154746">
                <text>Power Systems, pp. 75-97.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="154747">
                <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="154748">
                <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="154749">
                <text>&lt;a href="https://doi.org/10.1007/978-3-031-15044-9_4" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-031-15044-9_4&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85152403905&amp;amp;doi=10.1007%2F978-3-031-15044-9_4&amp;amp;partnerID=40&amp;amp;md5=b8c62db0dcdbde968d85fbb2f52813d8" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85152403905&amp;amp;doi=10.1007%2f978-3-031-15044-9_4&amp;amp;partnerID=40&amp;amp;md5=b8c62db0dcdbde968d85fbb2f52813d8&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="154750">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="154751">
                <text>ISSN: 16121287</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="154752">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154753">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="154754">
                <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="154755">
                <text>Jaisingh W., School of Computing Science and Engineering, VIT Bhopal University, Madhya Pradesh, Bhopal, India; Nanjundan P., Department of Data Science, Christ University, Pune, Lavasa, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18216" 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="150986">
                <text>IoT innovation in COVID-19 crisis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150987">
                <text>Agriculture; Artificial intelligence; Cardiovascular; Computed tomography; Contact tracing; COVID-19 pandemic; Deep learning; Digital technology; Global positioning system; Healthcare data; IoT robots; IoT technology; Machine learning; Magnetic resonance imaging; Perception layer; Random forest; Respiration rate; Support vector machine; Temperature</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150988">
                <text>The COVID-19 pandemic is a current global threat that surpasses provincial and radical boundaries. Due to the onset of the pandemic disease, the whole world turned entirely in a couple of weeks. Its consequences have come across the personal and professional life of human beings. The current situation focuses on precautions such as wearing a mask, maintaining social distancing, and sanitizing hands regularly. An innovative platform, and smart and effective IoT technology may be applied to follow these steps. This platform fulfills all critical challenges at the time of lockdown situations. IoT technology is more helpful in capturing real-time patient data and other essential information. IoT allows the tracing of infected people and suspicious cases and helps diagnose and treat patients remotely. It also paves the way to deliver essential medical devices and medicines to quarantined places. In the present ongoing crisis, IoT technology is inevitable in monitoring patients infected with COVID-19 through sensors and intertwined networks. The consultations are given to the patients digitally through video conferencing without meeting the medical expert in person. After the diagnosis is made digitally, IoT devices are used to track health data. Smart thermometers are used instead of traditional ones to collect valuable health data and share it with experts. The IoT robots are now a proven technology used for cleaning hospitals, disinfecting medical devices, and delivering medicines, thus giving more time to healthcare workers to treat patients.  2023 Bentham Science Publishers. All rights reserved.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150989">
                <text>Genish T.; Vijayalakshmi 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="150990">
                <text>The Role of AI, IoT, and Blockchain in Mitigating the Impact of COVID-19, pp. 48-68.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="150991">
                <text>Bentham Science Publishers</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="150992">
                <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="150993">
                <text>&lt;a href="" target="_blank" rel="noreferrer noopener"&gt;&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85205744294&amp;amp;partnerID=40&amp;amp;md5=1da2d1a6327e0dd0e7daad148ce4b4b4" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85205744294&amp;amp;partnerID=40&amp;amp;md5=1da2d1a6327e0dd0e7daad148ce4b4b4&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="150994">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="150995">
                <text>ISBN: 978-981508065-0; 978-981508066-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="150996">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150997">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="150998">
                <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="150999">
                <text>Genish T., KPR College of Arts, Science and Research, Coimbatore, India; Vijayalakshmi S., Department of Data Science, CHRIST (Deemed to be University), Pune Lavasa Campus - The Hub of Analytics, Maharashtra, 412112, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="17535" 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="141906">
                <text>IoT networks: Integrated learning for privacy-preserving machine learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141907">
                <text>Financial fraud is a persistent problem for consumers and financial institutions worldwide. It loses billions of dollars annually. Consequently, a strong fraud detection system (FDS) is essential to minimizing damage to financial institutions as well as clients. One common technique for spotting fraud is to use machine learning algorithms, which analyze large volumes of data to help with pattern detection and future prediction. It is difficult for a centralized FDS to detect fraud trends when these problems are coupled. To train a fraud detection model, this work presents a framework for federated learning, a machine-learning environment in which several entities collaborate to solve a machine-learning problem under the guidance of a central server or service provider. Also, the chapter examines how combined learning can be used to protect privacy in machine learning in Internet of Things systems. It focuses on four main calculations: federated averaging (FedAvg), secure aggregation, holomorphic encryption-based federated learning, and differential privacy in combined learning. Extensive experiments were carried out to evaluate these computations in terms of proving accuracy, conserving protection, and computing efficiency. The findings are shown in the results, with FedAvg achieving the highest accuracy of 92.5% and secure conglomeration demonstrating competitive precision levels of 91.8%. Calculations for differential privacy and holomorphic encryption demonstrated strong security conservation with very little data leakage and security parameters of 2.5 and 1.0, respectively. With little communication overhead and the ability to alter accuracy and conserve protection, secure aggregation emerged as a potential configuration. The computational productivity assessments revealed that secure accumulation produced little communication overhead despite its strong security conservation, which makes it suitable for IoT scenarios with limited resources. By using this tactic, financial institutions may avoid sharing datasets and benefit from a shared model that has seen more fraud than any one bank has on its own. Thus, the sensitive data of the user is protected. The results of the chapter indicate that the federated model (federated averaging) may be as good as or better than the central model (multi-layer perceptron) in detecting financial fraud. This chapter adds to the growing conversation around mixed learning in the Internet of Things by providing insights into the trade-offs between accuracy, security, and efficacy and by laying the groundwork for future developments in privacy-preserving machine learning standards.  2025 selection and editorial matter, Ahmed A. Elngar, Diego Oliva and Valentina E. Balas. All rights reserved.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141908">
                <text>Singh K.; Yadav M.; Singh Y.; Malik P.S.; Siwach V.; Khurana D.; Kumar B.; Yadav R.K.; Elngar A.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="141909">
                <text>Artificial Intelligence Using Federated Learning: Fundamentals, Challenges, and Applications, pp. 250-275.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="141910">
                <text>CRC Press</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="141911">
                <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="141912">
                <text>&lt;a href="https://doi.org/10.1201/9781003482000-13" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1201/9781003482000-13&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85213193126&amp;amp;doi=10.1201%2F9781003482000-13&amp;amp;partnerID=40&amp;amp;md5=add35c01ce0aecd7eb7db57455aa4dcf" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85213193126&amp;amp;doi=10.1201%2f9781003482000-13&amp;amp;partnerID=40&amp;amp;md5=add35c01ce0aecd7eb7db57455aa4dcf&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="141913">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="141914">
                <text>ISBN: 978-104026669-4; 978-103277164-9</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="141915">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141916">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="141917">
                <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="141918">
                <text>Singh K., Department of Computer Science and Engineering, University Institute of Engineering and Technology, Maharshi Dayanand University, Haryana, India; Yadav M., Department of Mathematics, University Institute of Sciences, Chandigarh University, Mohali, India; Singh Y., Department of Computer Science and Engineering, University Institute of Engineering and Technology, Maharshi Dayanand University, Haryana, India; Malik P.S., Computer Science and Engineering, Guru Jambheshwar University of Science and Technology, Haryana, India; Siwach V., Computer Science and Engineering, UIET, MDU, Rohtak, India; Khurana D., Department of Computer Science and Engineering, Symbiosis Institute of Technology (SIT), Pune, Maharashtra, India; Kumar B., Department of Chemistry, Guru Jambheshwar University of Science and Technology, Haryana, India; Yadav R.K., Department of Data Science, Christ University, Bengaluru, India; Elngar A.A., Faculty of Computers and Artificial Intelligence, Beni-Suef University, Beni-Suef City, Egypt</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="18040" 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="148625">
                <text>IoT Security with Blockchain Technology in the Financial Sector</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148626">
                <text>Blockchain technology is to create immutable device IDs to stop identity faking whereas Internet of Things (IoT) is used in payment automation and to create smart payment systems. Both are evolving technologies, and their integration offers promising results in financial sector across the globe. Their combination holds a great deal of potential and is going to represent the next generation of smart finance technologies. But the major weaknesses that are present in IoT technologies includes those related to data security, privacy, device authentication, secure communication, and smart contract administration. This chapter focuses on the use of blockchain networks to regulate access and improve security in financial transactions, boost automation and improve efficiency of IoT applications. Blockchain and IoT integration in the financial industry provides a pathway to a more integrated, efficient, and secure financial environment. The chapter discusses the advantages of integrating IoT and Blockchain technologies in the financial sector and the challenges in its applications, and the regulatory mechanism thereof.  2025 Taylor &amp;amp; Francis Group, LLC.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148627">
                <text>Divyashree K.L.; Mishra 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="148628">
                <text>Internet of Things Vulnerabilities and Recovery Strategies, pp. 166-182.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="148629">
                <text>CRC Press</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="148630">
                <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="148631">
                <text>&lt;a href="https://doi.org/10.1201/9781003474838-9" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1201/9781003474838-9&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85199174195&amp;amp;doi=10.1201%2F9781003474838-9&amp;amp;partnerID=40&amp;amp;md5=441a5166b513f62c20c0a9873fa58676" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85199174195&amp;amp;doi=10.1201%2f9781003474838-9&amp;amp;partnerID=40&amp;amp;md5=441a5166b513f62c20c0a9873fa58676&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="148632">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="148633">
                <text>ISBN: 978-104002562-8; 978-103247331-4</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="148634">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148635">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="148636">
                <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="148637">
                <text>Divyashree K.L., Christ University, Bangalore, India; Mishra A., Christ University, Bangalore, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="26491" 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="264449">
                <text>Ajesh, F.; Philip, Felix M.; Jims, Anupama; Alapatt, Bosco Paul</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264450">
                <text>IOT Wearable Medical Device for Heart Disease Recognition Based ML and DL: A Classification Approach</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="264451">
                <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="264452">
                <text>Lecture Notes in Networks and Systems;Volume;1243 LNNS;pp.353-363</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="264453">
                <text>&lt;a href="https://doi.org/10.1007/978-3-031-81080-0_32" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1007/978-3-031-81080-0_32&lt;/a&gt; &lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/pages/publications/105004252580?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105004252580?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="264454">
                <text>Ajesh F., Department of Computer Science and Engineering, Sree Buddha College of Engineering, Kerala, Alappuzha, India; Philip F.M., Department of CS &amp;amp; IT Jain (Deemed-to-be University), Bangalore, India; Jims A., Department of Computer Science and Engineering, CVV Institute of Science and Technology, Kerala, India; Alapatt B.P., CHRIST (Deemed to be University), Delhi-NCR, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264455">
                <text>In the past few years, heart disease has become the foremost worldwide contributor to mortality. This ailment, with a profound effect on the functioning of the heart, leads to issues such as infections in the coronary arteries and diminished blood vessel performance. These complications can culminate in severe unlikely events like heart attacks and strokes. In India alone, approximately one person succumbs to heart disease every minute. To curb the fatalities stemming from cardiac disorders, there is an urgent need for a swift and efficient detection strategy. IoT sensors are utilized in conjunction with Machine Learning (ML) and Deep Learning (DL) techniques to identify heart disease. In this research, we have successfully applied IoT devices and a sensor network to detect heart diseases. This study introduces a medical IoT device designed to gather heart data from patients both before and after the onset of heart disease. This continuously transmitted data is processed using RBF, MLP, and Bi-LSTM models for predicting heart disease. The deep learning approach utilizes past analyses to learn critical features related to heart disease, achieving efficiency in handling complex data. After conducting a series of experiments, we evaluate the systems performance using metrics such as f-measure, sensitivity, specificity, loss function, and Receiver Operating Characteristic (ROC) curves. The HDRBi-LSTM method, in combination with IoT-based analysis, achieves an impressive accuracy rate of 99.5% with minimal time complexity (5 s), effectively reducing heart disease mortality by simplifying the diagnosis of this condition.   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="264456">
                <text>deep learning; Heart Disease prediction; IoT; long short-term memory; Supervised learning</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="264457">
                <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="264458">
                <text>ISSN: 23673370; ISBN: 978-303181079-4;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264459">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="264460">
                <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="264461">
                <text>Restricted Access; Hardcopy may be available in the library</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="17667" 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="143638">
                <text>IoT-Based automated dust bins and improved waste optimization techniques for Smart City</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143639">
                <text>Effective waste management systems are essential for maintaining sustainability, environmental health, and cleanliness in the age of smart cities. This chapter provides a thorough analysis of the combination of cutting-edge waste minimization techniques with the deployment of an internet of things-based automatic dust bin. The suggested system optimizes garbage collection, lowers operating costs, and has a less environmental effect by combining the creative use of proximity sensors, real-time data analytics, and smart bin technologies. Remote monitoring and administration are made possible by the linked ecosystem that is created by the integration with the internet of things (IoT). In order to further promote environmentally friendly urban life, the study also examines waste-to-energy technology, circular economy ideas, and sustainable waste management techniques. The results provide insightful information for scholars, decision-makers, and urban planners looking for ground-breaking waste management solutions for today's cities.  2024, 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="143640">
                <text>Singh K.; Yadav M.; Yadav R.K.</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="143641">
                <text>Revolutionizing Automated Waste Treatment Systems: IoT and Bioelectronics, pp. 167-194.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="143642">
                <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="143643">
                <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="143644">
                <text>&lt;a href="https://doi.org/10.4018/979-8-3693-6016-3.ch012" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.4018/979-8-3693-6016-3.ch012&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85196589005&amp;amp;doi=10.4018%2F979-8-3693-6016-3.ch012&amp;amp;partnerID=40&amp;amp;md5=9f3f4610b53b6647f84983b23829f55a" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85196589005&amp;amp;doi=10.4018%2f979-8-3693-6016-3.ch012&amp;amp;partnerID=40&amp;amp;md5=9f3f4610b53b6647f84983b23829f55a&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="143645">
                <text>Restricted Access</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="143646">
                <text>ISBN: 979-836936018-7; 979-836936016-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="143647">
                <text>Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143648">
                <text>English</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="143649">
                <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="143650">
                <text>Singh K., University Institute of Engineering and Technology, Maharshi Dayanand University, India; Yadav M., University Institute of Sciences, Chandigarh University, India; Yadav R.K., Christ University, India</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
