<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="20266" 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/20266?output=omeka-xml" accessDate="2026-05-07T15:57:15+00:00">
  <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="179312">
              <text>Customer Behavior Analysis Using Unsupervised Clustering and Profiling: A Machine Learning Approach</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="179313">
              <text>Affiliation rule mining model; Agglomerative Clustering; Customer Behavior Prediction Model Analysis; Customer Segmentation; Hierarchical Clustering</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="179314">
              <text>Now-a-days, client conduct models are reliably established on information mining of client information, and each model is supposed to answer one solicitation at one point on schedule. Anticipating client conduct is a problematic and irksome task. Thus, making client conduct models requires the right strategy and approach. Right when an estimate model has been fabricated, it is challenging to restrict it for the motivations driving the advertiser, to pick the very thing displaying moves to make for every client or for the party of clients. Notwithstanding the multifaceted nature of this arrangement, most client models are completely fundamental. As the need might arise, most client conduct investigation models ignore such endless proper factors that the gauges they make are overall not altogether strong. This paper plans to encourage a connection rule mining model to expect client conduct using a typical electronic retail store for data combination and concentrate critical examples from the client conduct data. In this undertaking, a solo grouping of information on the customer's records from a regular food item company's data set will be played out. Customer segmentation is the act of clustering customers into bunches that reflect likenesses among customers in each group. Customers are separated into sections to advance the meaning of every customer to the business. To change items as indicated by unmistakable requirements and practices of the customers. It additionally assists the business with obliging the worries of various kinds of customers. Customers were clustered using a technique known as agglomerative clustering, which is a type of hierarchical clustering. Agglomerative clustering is a method for clustering data in a hierarchical order. It entails merging cases until you reach the appropriate number of clusters. The number of clusters to be produced is determined using the Elbow Method.  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="179315">
              <text>Gopal A.C.; Jacob L.</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="179316">
              <text>2022 2nd International Conference on Advance Computing and Innovative Technologies in Engineering, ICACITE 2022, pp. 2075-2078.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="179317">
              <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="179318">
              <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="179319">
              <text>&lt;a href="https://doi.org/10.1109/ICACITE53722.2022.9823646" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/ICACITE53722.2022.9823646&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85135447402&amp;amp;doi=10.1109%2FICACITE53722.2022.9823646&amp;amp;partnerID=40&amp;amp;md5=1bfb6e2376bac2a811baa70682750e0a" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85135447402&amp;amp;doi=10.1109%2fICACITE53722.2022.9823646&amp;amp;partnerID=40&amp;amp;md5=1bfb6e2376bac2a811baa70682750e0a&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="179320">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="179321">
              <text>ISBN: 978-166543789-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="179322">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="179323">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="179324">
              <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="179325">
              <text>Gopal A.C., Christ University, Department of Data Science, India; Jacob L., Christ University, Department of Data Science, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
