<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="14811" 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/14811?output=omeka-xml" accessDate="2026-04-17T04:37:43+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="104169">
              <text>Quality enhanced framework through integration of blockchain with supply chain management</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="104170">
              <text>Agri-food supply chains; Blockchains technology; Digital data; IoT</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="104171">
              <text>Recently, there has been significant growth in the consumption of the most widely diversified Internet of Things (IoT) technological knowledge, and devices, which has resulted in an impact on not only electrical items and the agricultural and food industries (Agri-Food) supply chain networks. This has sparked intense curiosity about the development of information sharing that is reliable, traceable, and transparent, and also increased significant research and advancement efforts. Existing IoT-based trace &amp;amp; authenticity methods for agri-food distribution networks are constructed on top of centralized architectures, which creates the potential for significant issues such as data security, manipulation, and standard points of weakness. A creative and scraping methodological approach to implementing decentralized trust-free networks is represented by blockchain technologies, the decentralized blockchain technologies that underpin cryptocurrencies. The fault tolerance, data integrity, visibility, and complete tracing of saved transactional data, along with cohesive digital information of property resources and independent transactions implementations, are in fact features built into this digitalization. This study introduces Agri-BlockIoT, a completely decentralized blockchain-based traceable platform for managing a global agro-food distribution network that can seamlessly connect IoT systems that produce and consume digital information all along the distribution chain. We implemented a use caseto achieve transparency and traceability. Lastly, we analyzed and contrasted the implementations' capability in terms of delay, CPU, or network utilization.  2022 The Authors</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="104172">
              <text>Ramkumar G.; Kasat K.; Khader P R.A.; Muhammed P K N.; Raghu T.; Chhabra S.</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="104173">
              <text>Measurement: Sensors, Vol-24</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="104174">
              <text>Elsevier Ltd</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="104175">
              <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="104176">
              <text>&lt;a href="https://doi.org/10.1016/j.measen.2022.100462" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.measen.2022.100462&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85138189599&amp;amp;doi=10.1016%2Fj.measen.2022.100462&amp;amp;partnerID=40&amp;amp;md5=f2aef81d348b8b9774de89d632324667" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85138189599&amp;amp;doi=10.1016%2fj.measen.2022.100462&amp;amp;partnerID=40&amp;amp;md5=f2aef81d348b8b9774de89d632324667&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="104177">
              <text>All Open Access; Gold Open Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="104178">
              <text>ISSN: 26659174</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="104179">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="104180">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="104181">
              <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="104182">
              <text>Ramkumar G., Department of Commerce, School of Commerce, Finance and Accountancy, Christ University, Bangalore, India; Kasat K., Symbiosis School for Liberal Arts, Symbiosis International (Deemed University), Maharashtra, Pune, India; Khader P R.A., Department of Commerce, Ansar Arabic College Valavannur, Kerala, India; Muhammed P K N., Department of Commerce, Malabar College of Advanced Studies, Vengara, Kerala, India; Raghu T., Research Scholar, Department of Commerce and Management Studies, Andhra University, Andhra Pradesh, Visakhapatnam, 530003, India; Chhabra S., Research Scholar, School of Engineering and Technology, Sharda University, Greater Noida</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
