<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="15069" 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/15069?output=omeka-xml" accessDate="2026-05-03T09:21: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="107754">
              <text>JP-DAP: An Intelligent Data Analytics Platform for Metro Rail Transport Systems</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="107755">
              <text>Big data analytics; Hadoop; intelligent transport systems; machine learning; metro rail; TestDFSIO</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="107756">
              <text>This paper deals with an intelligent data analytics platform-Jaison-Paul Data Analytics Platform (JP-DAP)-for metro rail transport systems. JP-DAP is intended to ensure smooth functioning, improved customer experience, ridership forecasting, and efficient administration of metro rail transportation systems by integrating and analysing its many data sources. It consists of a middleware which is built on the top of a Hadoop Distributed File System (HDFS) and Spark framework, along with a set of open-source software tools like Apache Hive, Pandas, Google TensorFlow and Spark ML-lib for real-time and legacy data processing. The benchmarking of JP-DAP was conducted using TestDFSIO and have found that it performs well according to industry standards. The specific use case for this project is Kochi Metro Rail Limited (KMRL). The analysis of Automated Fare Collection data from KMRL on JP-DAP framework have produced descriptive statistics visualisation of inflow and outflow analysis, travel patterns during weekdays and weekends, origin-destination matrix, etc.. Moreover JP-DAP framework is capable of producing short term passenger flow predictions using SVR machine learning algorithm with linear, radial basis function and polynomial kernels. Our experiments have shown that SVR linear kernel gives the most accurate results with the least errors in predicting the next day's passenger count using the previous five weekdays data. The station usage (one-to-all) prediction using Long Short-Term Memory (LSTM) is also integrated to this framework. The visualisation as well as analytical outcomes of JP-DAP framework have also been made available to the external world using a rich set of REST APIs and are projected on to a web-dashboard.   2000-2011 IEEE.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="107757">
              <text>Mulerikkal J.; Thandassery S.; Dixon K D.M.; Rejathalal V.; Ayyappan B.</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="107758">
              <text>IEEE Transactions on Intelligent Transportation Systems, Vol-23, No. 7, pp. 9146-9156.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="107759">
              <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="107760">
              <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="107761">
              <text>&lt;a href="https://doi.org/10.1109/TITS.2021.3091542" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1109/TITS.2021.3091542&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85113196240&amp;amp;doi=10.1109%2FTITS.2021.3091542&amp;amp;partnerID=40&amp;amp;md5=1491387c02b153ac72ea7f197f0f88fd" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85113196240&amp;amp;doi=10.1109%2fTITS.2021.3091542&amp;amp;partnerID=40&amp;amp;md5=1491387c02b153ac72ea7f197f0f88fd&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="107762">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="107763">
              <text>ISSN: 15249050</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="107764">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="107765">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="107766">
              <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="107767">
              <text>Mulerikkal J., The Department of Computer Science, Rajagiri School of Engineering and Technology, Kochi, 682039, India; Thandassery S., The Department of Computer Science, Rajagiri School of Engineering and Technology, Kochi, 682039, India, The Department of Computer Science, Christ-Deemed to Be University, Bengaluru, 560029, India; Dixon K D.M., The Department of Computer Science, Jyothi Engineering College, Thrissur, 679531, India; Rejathalal V., The Department of Computer Science, Jyothi Engineering College, Thrissur, 679531, India; Ayyappan B., The Department of Information Technology, Rajagiri School of Engineering and Technology, Kochi, 682039, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
