<?xml version="1.0" encoding="UTF-8"?>
<itemContainer xmlns="http://omeka.org/schemas/omeka-xml/v5" 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://repository.horizon.ac.id/items/browse?collection=696&amp;output=omeka-xml&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-04-14T20:21:47+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>1</pageNumber>
      <perPage>10</perPage>
      <totalResults>5</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="9229" public="1" featured="1">
    <fileContainer>
      <file fileId="9254">
        <src>https://repository.horizon.ac.id/files/original/2d841befa8d4835c7cc9b092630eb6af.pdf</src>
        <authentication>2395e0264fea89d796879ebfc78ae3df</authentication>
      </file>
    </fileContainer>
    <collection collectionId="696">
      <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="99017">
                  <text> VOL 3 NO 3 DECEMBER 2020</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="99045">
                <text>A High-Performance Data Accessing and Processing System for Campus&#13;
Real-time Power Usage</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99046">
                <text>Internet of Things; Big data warehouse; Real-time processing; Spark; Hive; Impala;&#13;
1.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99047">
                <text>With the flourishing of Internet of Things (IoT) technology, ubiquitous power data can be linked to the Internet and be analyzed for real-time&#13;
monitoring requirements. Numerous power data would be accumulated to even Tera-byte level as the time goes. To approach a real-time power&#13;
monitoring platform on them, an efficient and novel implementation techniques has been developed and formed to be the kernel material of this&#13;
thesis. Based on the integration of multiple software subsystems in a layered manner, the proposed power-monitoring platform has been&#13;
established and is composed of Ubuntu (as operating system), Hadoop (as storage subsystem), Hive (as data warehouse), and the Spark MLlib&#13;
(as data analytics) from bottom to top. The generic power-data source is provided by the so-called smart meters equipped inside factories&#13;
located in an enterprise practically. The data collection and storage are handled by the Hadoop subsystem and the data ingestion to Hive data&#13;
warehouse is conducted by the Spark unit. On the aspect of system verification, under single-record query, these software modules: HiveQL&#13;
and Impala SQL had been tested in terms of query-response efficiency. And for the performance exploration on the full-table query function.&#13;
The relevant experiments have been conducted on the same software modules as well. The kernel contributions of this research work can be&#13;
highlighted by two parts: the details of building an efficient real-time power-monitoring platform, and the relevant query-response efficiency&#13;
for reference.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99048">
                <text>Sheng-Cang Chou 1,*, Chao-Tung Yang</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="99049">
                <text>2020</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99050">
                <text>peri irawan</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="99051">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99052">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99053">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9230" public="1" featured="1">
    <fileContainer>
      <file fileId="9255">
        <src>https://repository.horizon.ac.id/files/original/bbfc12c3271f07b2252da26622d23e1e.pdf</src>
        <authentication>c7a24e5ad21a96c8557e3037853a7a94</authentication>
      </file>
    </fileContainer>
    <collection collectionId="696">
      <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="99017">
                  <text> VOL 3 NO 3 DECEMBER 2020</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="99054">
                <text>Boosting Purchase Intention and Online Participation Through Passion</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99055">
                <text>Passion; engagement; social commerce;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99056">
                <text>This study analyzes the role of passion in engaging users and how it affects purchase intention and participation in social commerce contexts.&#13;
Based on marketing research, the engagement generation process is studied through the interactions among social presence,interactivity,&#13;
enjoyment, sPassion, purchase intention and spread of sWOM. The results have empirically confirmed that social interactions and information&#13;
exchange derived from the process boost user participation and the intention to purchase. At the core of the process, sPassion positively affects&#13;
the spreading of sWOM. The introduction of the new concept sPassion brings new challenges and opportunities to marketing research, helping&#13;
to develop the concept of engagement and furthering research on WOM valence. Knowing how sPassion is formed and what factors are key to&#13;
its creation enable companies to understand the necessary steps to enhance user participation in social commerce contexts.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99057">
                <text>Carolina Herrando 1,*, Julio Jiménez-Martínez 2, María José Martín De Hoyos</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="99058">
                <text>2020</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99059">
                <text>peri irawan</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="99060">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99061">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99062">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9228" public="1" featured="1">
    <fileContainer>
      <file fileId="9253">
        <src>https://repository.horizon.ac.id/files/original/39bcc95d49f876d7d67c2c454ae510ac.pdf</src>
        <authentication>5334ed1166622c323359c5e911a9afa7</authentication>
      </file>
    </fileContainer>
    <collection collectionId="696">
      <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="99017">
                  <text> VOL 3 NO 3 DECEMBER 2020</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="99036">
                <text>Effect of Textual Errors on The Evaluation of a Foreign Online Store</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99037">
                <text>Cross-border electronic commerce; Consumer behavior; Trust; Ease of use; Ease of communication;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99038">
                <text>We conducted an experimental study among Japanese consumers to investigate the impact of textual errors on the perception and evaluation of&#13;
an online store in a cross-border context. In particular, we proposed that the presence of textual errors would result in lower perceived ease of&#13;
use, ease of communication and trust in a foreign online store. The experiment considered two types of errors, related to the use of language&#13;
and to the completeness of translation. Four experimental conditions with different levels of textual errors were evaluated. We conducted a&#13;
survey in Japan, obtaining a total of 1919 responses which were analyzed using structural equation modeling. The results showed that the&#13;
presence of textual errors had a negative effect on all factors in the proposed model, compared to the absence of such errors. We discuss these&#13;
results and their implications for foreign online vendors.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99039">
                <text>Vanessa Bracamonte Lesma 1,*, Hitoshi Okada</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="99040">
                <text>2020</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99041">
                <text>peri irawan</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="99042">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99043">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99044">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9226" public="1" featured="1">
    <fileContainer>
      <file fileId="9251">
        <src>https://repository.horizon.ac.id/files/original/d36379868c0e1fa386c121c9f1b3fd75.pdf</src>
        <authentication>eeb41efe6efeaac3e278304fafd83189</authentication>
      </file>
    </fileContainer>
    <collection collectionId="696">
      <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="99017">
                  <text> VOL 3 NO 3 DECEMBER 2020</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="99018">
                <text>Framework for UX Based M-Learning Using Learning Style and&#13;
Recommendation System</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99019">
                <text>User Experience; M-learning; Learning Style;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99020">
                <text>M-learning plays the key role in the educational industry is increasingly. However, the current use of M-learning is not designed for individual&#13;
learner style. Consequently, it causes many students not to understand lessons precisely.Not only learning style which determines the course&#13;
material but also user interface and interaction called user experience (UX). Therefore, m-learning combined learning style and user experience&#13;
(UX) are also proposed to learners in order to obtain better understanding towards lessons. This study conducts sample group in basic&#13;
programming subject with pre-test and modeling students' learning style using Felder &amp; Silverman learning style. The results showed that&#13;
students' have different learning styles. This prototype of User Experience of M-learning (UXML) related to this subject was developed to&#13;
deliver the appropriate content match to each student's learning style. This courseware serves 4 patterns of derived learning style they are&#13;
Active, Sensing, Visual andSequential.Hence, the students are able to understand topic easier from recommended course material with mobility&#13;
features.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99021">
                <text>Apichaya Nimkoompai 1,*, Worapat Paireekreng</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="99022">
                <text>2020</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99023">
                <text>peri irawan</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="99024">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99025">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99026">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="9227" public="1" featured="1">
    <fileContainer>
      <file fileId="9252">
        <src>https://repository.horizon.ac.id/files/original/80676671349c2159c5e1290b86b7f5df.pdf</src>
        <authentication>9673b76380c1a315fe12fe7d2c85ec65</authentication>
      </file>
    </fileContainer>
    <collection collectionId="696">
      <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="99017">
                  <text> VOL 3 NO 3 DECEMBER 2020</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <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="99027">
                <text>The Relation Between Hiring Queuers and Emotions - A Pre-Study of&#13;
Experiment Design</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99028">
                <text>Queuing behavior; negative emotion; perception of waiting time;</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99029">
                <text>Consumers considering whether or not to queue make their decisions based on queuing size and the expecting waiting time. If a consumer is&#13;
frustrated because he / she cannot know how long will wait, he / she will quit from a Consumers who are frustrated because they do not know&#13;
how long they must wait will quit a queue or ask someone for help if the good is worthy to pay more money to own. If a good is worth waiting&#13;
to purchase, a consumer will chose waiting or buying the privilege to get the good. However, a long wait causes customers to have negative&#13;
feelings about the queue. Frustration also has a substantial effect on customer loyalty to a good. Therefore, the relationship between perceived&#13;
waiting time and paying for queuers to buy the good is worth studying. Frustration is a moderating effect that is also worth studying. In the&#13;
formal study, to make the frustrating emotion, the authors asked all participants to have a contest before they can take the tickets to enter a&#13;
queue for taking the ticket to a famous concert in Taiwan. The questions used in the contest had different levels of difficulty. However, the&#13;
difficulty of the questions must be verified before the formal experiment. Therefore, the 60 participants in this pilot study were asked 40&#13;
questions in history, mathematics, and Chinese to find the most difficult ten questions and the less difficulty ten questions for the formal test.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99030">
                <text>Ruo-Yin Liao 1,*, Chih-Chin Liang 2</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="99031">
                <text>2020</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99032">
                <text>peri irawan</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="99033">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99034">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99035">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
