<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="1250" public="1" featured="1" 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/1250?output=omeka-xml" accessDate="2026-05-13T15:48:59+00:00">
  <fileContainer>
    <file fileId="1110">
      <src>https://archives.christuniversity.in/files/original/ed12641196017cba35f8f691a892368b.pdf</src>
      <authentication>8a9c50e2ffbe909b6631dfbab5c822e8</authentication>
    </file>
  </fileContainer>
  <collection collectionId="23">
    <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="64989">
                <text>MPHIL</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="18">
    <name>Mphil</name>
    <description>Mphil Thesis</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="5963">
              <text>An Autonomic Systems approach to Online Retail Systems

</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5964">
              <text> Kurian   Devasia</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="5965">
              <text>2010</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="5966">
              <text>Computer Science</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="5967">
              <text>In 2003, IBM released a document presenting its vision of autonomic computing. In this article, the author observes that the ever increasing complexity of computing systems will cross the borders of human capabilities, leading to systems that are too complex to be administrated by human beings. System administrators will no longer be able to install, configure, maintain and optimize these computing systems of the future. The solution to this problem is developing a  technology  that  allows  computing  systems  to  manage  themselves.  This solution is referred to as autonomic computing.

In today??s economic scenario, Online Retail Systems are gaining prominence and day by day increasing in size, leading to complexities difficult to be managed by human beings. E-Commerce Shops with thousands of articles are becoming the rule of the day. With hundreds of articles being added everyday, the administration required for efficient management of these articles, especially display selection, rejection etc are becoming a mind boggling task for human beings to manage. Parallel developments in study of buying behaviors based on various techniques like data mining, decision trees, neural networks etc are gaining significant practical ground, which also increases the complexity to be managed.

The basic idea is lay foundation for creation of autonomic systems based on the outputs from behavioral study, inventory management, etc to autonomically handle management of display, inventory predictions etc.   The efficiencies achieved should in turn result in higher revenue as well as profits.

In short, the study intends to explore the feasibility of applying autonomic techniques for efficient display organization in online retail contexts by borrowing the intelligence from techniques evolving from data mining, artificial intelligence.

This paper will address the development of a taxonomy, a model framework for

??autonomic online retail?? systems and the application of related standards. It will also delve into the theoretical background of specific techniques, which can be applied in this scenario. A basic model of the framework is also implemented.

The  complete  implementation  of  the  framework  and  measurement  of  the efficiency gains and other effects will be continued in the doctoral research. The design  of  the  framework  and  also  the  measurement  framework  is  being discussed in this document.

</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
