<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="15885" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/15885?output=omeka-xml" accessDate="2026-04-08T18:21:31+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="119108">
              <text>An effective face recognition system based on Cloud based IoT with a deep learning model</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="119109">
              <text>Cloud; Deep learning; Deep neural network; Edge computing; IoT</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="119110">
              <text>As of late, the Internet of Things (IoT) innovation has been utilized in applications, for example, transportation, medical care, video observation, and so on. The quick appropriation and development of IoT in these segments are producing an enormous measure of information. For instance, IoT gadgets, for example, cameras produce various pictures when utilized in medical clinic reconnaissance sees. Here, face acknowledgement is one of the most significant instruments that can be utilized for clinic affirmations, enthusiastic discovery, and identification of patients, location of fake gadgets. patient, and test clinic models. Programmed and shrewd face acknowledgement frameworks are profoundly precise in an overseen climate; notwithstanding, they are less exact in an unmanaged climate. Additionally, frameworks must keep on running on numerous occasions in different applications, for example, insightful wellbeing. This work presents a tree-based profound framework for programmed face acknowledgement in a cloud climate. The inside and out pattern have been proposed to cost less for the PC without focusing on unwavering quality. In the model, the additional size is isolated into a few sections, and a stick is made for each part. The tree is characterized by its branch area and stature. The branches are spoken to by a leftover capacity, which comprises of a twofold layer, a stack game plan, and a non-direct capacity. The proposed technique is assessed in an assortment of generally accessible information bases. An examination of the method is likewise finished with top to bottom craftsmanship models for the eye to eye connection. The aftereffects of the tests indicated that the example was considered to have accomplished a precision of 98.65%, 99.19%, and 95.84%.  2020</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="119111">
              <text>Chauhan D.; Kumar A.; Bedi P.; Athavale V.A.; Veeraiah D.; Pratap B.R.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="119112">
              <text>Microprocessors and Microsystems, Vol-81</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="119113">
              <text>Elsevier B.V.</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="119114">
              <text>2021-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="119115">
              <text>&lt;a href="https://doi.org/10.1016/j.micpro.2020.103726" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.micpro.2020.103726&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85098459051&amp;amp;doi=10.1016%2Fj.micpro.2020.103726&amp;amp;partnerID=40&amp;amp;md5=6b75cb583d66dd2a3b45ac8179d0ee80" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85098459051&amp;amp;doi=10.1016%2fj.micpro.2020.103726&amp;amp;partnerID=40&amp;amp;md5=6b75cb583d66dd2a3b45ac8179d0ee80&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="119116">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="119117">
              <text>ISSN: 1419331; CODEN: MIMID</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="119118">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="119119">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="119120">
              <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="119121">
              <text>Chauhan D., Department of Computer Science &amp;amp; Engineering, Shivajirao Kadam Institute of Technology &amp;amp; Management, Indore, Madhya Pradesh, India; Kumar A., Assistant Professor &amp;amp;Director (Hon.), P.G. Department Of Law, Centre for Cyber Law and Policy Research, SRNCT, Faculty of Legal Studies, M.J.P. Rohilkhand University, Bareilly, Uttar Pradesh, India; Bedi P., Associate Professor, Department of Computer Science and Engineering, Graphic Era Hill University, Dehradun, Uttarakhand, India; Athavale V.A., Department of Computer Science and Engineering, Panipat Institute of Engineering &amp;amp; Technology, Panipat, Haryana, India; Veeraiah D., Department of Computer Science and Engineering, Lakireddy Bali Reddy College of Engineering (A), Mylavaram, Krishna Dt., Andhra Pradesh, India; Pratap B.R., Department of Computer Science &amp;amp; Engineering, CHRIST (Deemed to be University), Bengaluru, Karnataka, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
