<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="13150" 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/13150?output=omeka-xml" accessDate="2026-04-18T02:00:16+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="81031">
              <text>Linking supply chain resilience with knowledge management for achieving supply chain performance</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="81032">
              <text>Dynamic capability theory; Knowledge management; MSMEs; SC performance; SC resilience; Strategies</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="81033">
              <text>Purpose: Supply chain (SC) and knowledge management (KM) have been studied; still, there is a need to understand how KM can be used for SC resilience and improving the firms performance. The purpose of the paper is to study and analyze SC resilience strategies based on KM processes to enhance SC performance considering six SC strategies: SC reengineering, collaboration, SC innovation, SC integration, SC agility and SC risk management. Design/methodology/approach: By adopting the dynamic capability theory, the empirical research is conducted on a sample of 312 Indian micro, small to medium enterprises. To evaluate 312 samples, the structural equation modeling approach is adopted. Findings: The study found a is a positive relationship between SC reengineering, SC collaboration, SC integration, SC agility, SC risk management and KM. Nevertheless, the relationship between SC innovation and KM is not significant. This study also found the mediating effect of KM on SC performance, and the results shows that SC reengineering, SC collaboration, SC agility and SC risk management are having complementary mediation, while SC innovation and SC integration did not show any mediation. Originality/value: This is the only research that integrates resilience strategies and KM for improving SC performance. Using KM, SC reengineering will improve SC performance by enhancing readiness and recovery strategies to avoid SC disruption. KM will improve SC collaboration. It will enhance the SC process overall visibility, transparency and so on. Agility leads to increased speed, visibility and flexibility, which aids in dealing with uncertainty in the environment. SCRM entails investments and additional resources (such as equipment and labor) to navigate uncertainty and risks in the SC and improve SC performance.  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="81034">
              <text>Mukherjee S.; Nagariya R.; Mathiyazhagan K.; Scuotto 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="81035">
              <text>Journal of Knowledge Management, Vol-28, No. 4, pp. 971-993.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="81036">
              <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="81037">
              <text>2024-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="81038">
              <text>&lt;a href="https://doi.org/10.1108/JKM-12-2022-0985" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1108/JKM-12-2022-0985&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85168536913&amp;amp;doi=10.1108%2FJKM-12-2022-0985&amp;amp;partnerID=40&amp;amp;md5=16f6ec7a9031271a21bf375e3a1479d8" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85168536913&amp;amp;doi=10.1108%2fJKM-12-2022-0985&amp;amp;partnerID=40&amp;amp;md5=16f6ec7a9031271a21bf375e3a1479d8&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="81039">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="81040">
              <text>ISSN: 13673270</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="81041">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="81042">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="81043">
              <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="81044">
              <text>Mukherjee S., Department of Operations, GITAM School of Business, GITAM (Deemed to be University), Visakhapatnam, India; Nagariya R., School of Business and Management, CHRIST (Deemed to be University), Bangalore, India; Mathiyazhagan K., Thiagarajar School of Management, Madurai, India; Scuotto V., Pole Universitaire Leonard de Vinci, Paris, France and Department of Economia, University of Naples Federico II, Naples, Italy</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
