<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="25290" 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/25290?output=omeka-xml" accessDate="2026-06-18T16:19:12+00:00">
  <collection collectionId="7">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3139">
                <text>Faculty Publications</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="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="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="248101">
              <text>Reddy, Jaya Bharath; Sagar, Ragha; Lahari, Lakshmi; Namitha, N.; Murthy, Nishitha N.; Pillai, Vinay Jha</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="248102">
              <text>AI-SECURED VISITOR MANAGEMENT SYSTEM</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="248103">
              <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="248104">
              <text>Attacks on Artificial Intelligence: The New Facets of Cyber Ecospace;pp.235-252</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="248105">
              <text>&lt;a href="https://www.scopus.com/pages/publications/105018260815?origin=resultslist" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/pages/publications/105018260815?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="248106">
              <text>Reddy J.B., Department of Electronics and Communication Engineering, School of Engineering and Technology, Christ University, Kengeri Campus, Bengaluru, India; Sagar R., Department of Electronics and Communication Engineering, School of Engineering and Technology, Christ University, Kengeri Campus, Bengaluru, India; Lahari L., Department of Electronics and Communication Engineering, School of Engineering and Technology, Christ University, Kengeri Campus, Bengaluru, India; Namitha N., Department of Electronics and Communication Engineering, School of Engineering and Technology, Christ University, Kengeri Campus, Bengaluru, India; Murthy N.N., Department of Electronics and Communication Engineering, School of Engineering and Technology, Christ University, Kengeri Campus, Bengaluru, India; Pillai N.N., Department of Electronics and Communication Engineering, School of Engineering and Technology, Christ University, Kengeri Campus, Bengaluru, India</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="248107">
              <text>In general, there are so many organizations using the conventional paper log book to record the access of the visitors. This conventional method takes longer time if the number of visitors exceeds the limit. Meanwhile, security issue should be a main concern if there is an increase in the number of visi tors. This is mainly due to the operators who take a long time to verify the identification of each and every visitor when there is huge number of visi tors entering the premises. Moreover, paper log is inadequate to efficiently retrieve and archive the data after several years. This report mainly discusses about the design and implementation of Visitor Management System using Internet of Things (IoT) and Artificial Intelligence (AI). Visitor management system is a security system which is used to track visitors activities in an organization or public building. ESP32 AI Thinker is used to collect the live stream video. Face detection and identification of visitors can be achieved through Artificial Intelligence (AI). With the help of IoT, we can remote access the system for visitor monitoring. The visitors information gets stored into a cloud server which helps the user to view the visitors details on mobile phone at any time. With the help of an API, the user can control the access of a visitor into the premises through notification alerts. A website has been created in order to store the details of visitors such as photograph, arrival time with the help of dijango web application frame work and bootstrap for user interface. DigitalOcean is the cloud server which is used to store the database. To get the notifications on mobile phone, a Telegram BoT API has been created in Telegram app. This BoT also saves the arrival time and photo of the visitor. With the help of this, the user will also be notified whenever a suspicious activity occurs in the premises. This IoT networked contact less security system offers improved security. AI secured Visitor Management System is the best solution to overcome the problems existing in the conventional method as it is the easy way to identify and record the information of a visitor.  2026 by Apple Academic Press, Inc.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="248108">
              <text>Apple Academic Press</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="248109">
              <text>ISBN: 978-104009235-4; 978-177491622-3;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="248110">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="248111">
              <text>Book chapter</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="248112">
              <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="248113">
              <text>online</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
