<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="14284" 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/14284?output=omeka-xml" accessDate="2026-04-04T17:22:27+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="96825">
              <text>Intentions to adopt the blockchain: investigation of the retail supply chain</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="96826">
              <text>Behavioural intention; Blockchain; Retail supply chain; Technology acceptance model; Theory of planned behaviour; Unified theory of acceptance and use of technology</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="96827">
              <text>Purpose: Blockchain can track the material from the manufacturer to the end customers. Therefore, it can ensure the product's authenticity, transparency and trust in the retail supply chain (SC). There is a need to trace and track the retail products before it reaches the customers to check the quality of the products so that expired products can be recycled and reused, which in turn will help gain customers' trust. This research aims to investigate retail employees' behavioural intention to adopt blockchain in the retail SC. Design/methodology/approach: To examine the behavioural intention of employees in the retail SC, the research uses three theories  the technology acceptance model; the unified theory of acceptance and use of technology; and the theory of planned behaviour. The technology acceptance model measures the employee's acceptance of blockchain in the retail SC. The unified theory of acceptance is used in this research to measure how blockchain adoption will improve the performance of the employees. The theory of planned behaviour is used in this research to measure whether the employees intend to adopt blockchain. A survey was carried out in the retail stores of India. Exploratory factor analysis and structural equation modelling were used for data analysis. Findings: This study found that the employees of the retail stores have a positive intention and attitude to adopt blockchain technology. Further, it was found that perceived behavioural control and effort expectancy was not promoting blockchain adoption in the retail sector. Practical implications: This study will help the retail stores' employees understand the blockchain in their operations and will motivate the top management of the retail companies to adopt this technology. The study is limited to the retail SC in India only. Originality/value: This study uses three theories technology acceptance model; the unified theory of acceptance and use of technology; and the theory of planned behaviour, which were not used in earlier studies of blockchain adoption in the retail SC.  2023, Emerald Publishing Limited.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="96828">
              <text>Mukherjee S.; Baral M.M.; Lavanya B.L.; Nagariya R.; Singh Patel B.; Chittipaka V.</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="96829">
              <text>Management Decision, Vol-61, No. 5, pp. 1320-1351.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="96830">
              <text>Emerald Publishing</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="96831">
              <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="96832">
              <text>&lt;a href="https://doi.org/10.1108/MD-03-2022-0369" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1108/MD-03-2022-0369&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85148000659&amp;amp;doi=10.1108%2FMD-03-2022-0369&amp;amp;partnerID=40&amp;amp;md5=1250d3fce724052a34133934cec08d7a" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85148000659&amp;amp;doi=10.1108%2fMD-03-2022-0369&amp;amp;partnerID=40&amp;amp;md5=1250d3fce724052a34133934cec08d7a&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="96833">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="96834">
              <text>ISSN: 251747</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="96835">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="96836">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="96837">
              <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="96838">
              <text>Mukherjee S., Department of Operations, GITAM School of Business, GITAM (Deemed to be University), Visakhapatnam, India; Baral M.M., Department of Operations, GITAM School of Business, GITAM (Deemed to be University), Visakhapatnam, India; Lavanya B.L., Department of Management, MEASI Institute of Management, Chennai, India; Nagariya R., School of Business and Management, Christ (Deemed to be University), Bengaluru, India; Singh Patel B., Department of Operations Management, Thiagarajar School of Management, Madurai, India; Chittipaka V., School of Management Studies, Indira Gandhi National Open University (IGNOU), New Delhi, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
