<?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=749&amp;output=omeka-xml&amp;page=3" accessDate="2026-04-25T21:45:39+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>3</pageNumber>
      <perPage>10</perPage>
      <totalResults>25</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="9829" public="1" featured="1">
    <fileContainer>
      <file fileId="9842">
        <src>https://repository.horizon.ac.id/files/original/942d0bf2433303e90df657403e4a5cb5.pdf</src>
        <authentication>358deca40b095063de9bd081b155868f</authentication>
      </file>
    </fileContainer>
    <collection collectionId="749">
      <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="105044">
                  <text>VOL. 22, NO.1 2024</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="105131">
                <text>Automatic detection, report, and alert of faults in 220 volts electric power distribution parts</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105132">
                <text>Cable grid&#13;
Distribution transformer&#13;
Electric power grid&#13;
Fault detection&#13;
Global system for mobile modems&#13;
Global system for mobile network</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105133">
                <text>The electrical power distribution parts include the distribution transformer responsible for reducing high voltage (HV) 11 Kv to low voltage (LV) 416/240 volts, and the power distribution lines (PDLs), which are the source of electrical power supply for residential neighborhoods. Any malfunction of these parts, result in a power outage. Currently, any faults are reported, detected, and alert in a primitive way, and this mechanism certainly takes a lot of time and effort. In this paper, an automatic approach for detection, report and alert has been suggested. This approach process is carried out by continuously checking the status of the three output feeders (power distribution lines), which is the low voltage side of the distribution transformer, when a malfunction occurs in any one or more of these feeders, it will generate an alert signal in the form of a text message using short message service (SMS). The maintenance center is notified by receiving this SMS via SIM900 modem through the global system for mobile (GSM) communications network. The SMS text message includes feeder number, fault type and location address (street number and distribution transformer number). In this design, time and effort are shortened and the maintenance center enables fully automatic monitoring of electric power distribution parts within the sector of responsibility.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105134">
                <text>Jabbar Shatti Jahlool1, Mohammed Abdulla Abdulsada2, Majid S. Naghmash1</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="105135">
                <text>Journal homepage: http://telkomnika.uad.ac.id</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="105136">
                <text>Nov 15, 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105137">
                <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="105138">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105139">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105140">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12556">
        <name>Cable grid Distribution transformer Electric power grid Fault detection Global system for mobile modems Global system for mobile network</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="9827" public="1" featured="1">
    <fileContainer>
      <file fileId="9840">
        <src>https://repository.horizon.ac.id/files/original/b05b90bc46995be676e3fef7745510e0.pdf</src>
        <authentication>041e36177486b60987ee470bc9ddd4a8</authentication>
      </file>
    </fileContainer>
    <collection collectionId="749">
      <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="105044">
                  <text>VOL. 22, NO.1 2024</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="105109">
                <text>Neural network with k-fold cross validation for oil palm fruit ripeness prediction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105110">
                <text>Artificial neural network&#13;
Hyperspectral images&#13;
K-fold cross validation&#13;
Oil palm fresh fruit bunch&#13;
Ripeness prediction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105111">
                <text>The combination of hyperspectral imaging and artificial neural network (ANN) can predict fruit ripeness. This work investigated the application of hyperspectral imaging and ANN models with the k-fold cross-validation method for ripeness prediction of oil palm fresh fruit bunches (FFB) for in-line sorting and grading machine vision. Crude palm oil (CPO) is an exporting commodity for countries such as Indonesia and Malaysia. Oil palm FFB ripeness determines the quality of CPO. The unique shapes and colors of FFBs need innovative methods to substitute tedious and cumbersome manual sorting and grading. The oil palm FFB samples used in this study were categorized previously based on color and loosed fruits. We applied the Savitzky-Golay (SG) smoothing filter and 7-fold cross-validation for hyperspectral datasets before being used for the ANN models and a confusion matrix to find the ANN model accuracies. We obtained 72 data points after SG filter and data selection from 523 data points. The prediction results showed an average accuracy of 79.48%, in which three folds with k of 2, 5, and 7 gave the highest accuracy of 90%. The results confirmed the potential use of hyperspectral imaging, with k-fold cross-validation and ANN models for ripeness prediction of oil palm FFBs.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105112">
                <text>Minarni Shiddiq1, Feri Candra2, Barri Anand2, Mohammad Fisal Rabin1</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="105113">
                <text>Journal homepage: http://telkomnika.uad.ac.id</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="105114">
                <text>Sep 27, 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105115">
                <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="105116">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105117">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105118">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12548">
        <name>Artificial neural network Hyperspectral images K-fold cross validation Oil palm fresh fruit bunch Ripeness prediction</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="9826" public="1" featured="1">
    <fileContainer>
      <file fileId="9839">
        <src>https://repository.horizon.ac.id/files/original/baef6acb7d8705b66dc5a7dbc1702692.pdf</src>
        <authentication>036797820d1657d7310a9e5d490240af</authentication>
      </file>
    </fileContainer>
    <collection collectionId="749">
      <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="105044">
                  <text>VOL. 22, NO.1 2024</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="105099">
                <text>Towards a simple and efficient vehicular delay tolerant&#13;
networks routing protocol for data collection in smart cities</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105100">
                <text>Data collection&#13;
Intelligent transportation systems&#13;
Routing protocol&#13;
Smart city&#13;
Vehicle-to-everything&#13;
Vehicular delay tolerant networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105101">
                <text>Smart cities today can utilize vehicular delay tolerant networks (VDTN) to collect&#13;
data from connected-objects in the environment for various delay-tolerant&#13;
applications. They can take advantage of the available intelligent transportation&#13;
systems (ITS) infrastructures to deliver data to the central server. The system&#13;
can also exploit multiple and diverse mobility patterns found in cities, such as&#13;
privately owned cars, taxis, public buses, and trams, along with their vehicle-toeverything&#13;
(V2X) communications capabilities. In the envisioned convergence&#13;
between the ITS and V2X, we believe that a simple and efficient routing protocol&#13;
can be deployed for the delay-tolerant data delivery, contrary to the implementation&#13;
of optimized solutions that might be resource-demanding and difficult to&#13;
standardize. In this paper, we analyzed the performances of four baseline VDTN&#13;
routing protocols, namely: direct delivery, first contact, epidemic, and spray and&#13;
wait, to understand their strengths and weaknesses. Our simulation results highlighted&#13;
the trade-off between distinct approaches used by those protocols and&#13;
pointed out some gaps that can be refined. This study provides new interesting&#13;
ideas and arguments towards developing a simple, efficient, and high-performing&#13;
routing protocol for data collection in smart cities.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105102">
                <text>Ngurah Indra Er1, Kamal Deep Singh2,3, Christophe Couturier4,5, Jean-Marie Bonnin4,5</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="105103">
                <text>Journal homepage: http://journal.uad.ac.id/index.php/TELKOMNIKA</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="105104">
                <text>Sep 26, 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105105">
                <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="105106">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105107">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105108">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12547">
        <name>Data collection Intelligent transportation systems Routing protocol Smart city Vehicle-to-everything Vehicular delay tolerant networks</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="9825" public="1" featured="1">
    <fileContainer>
      <file fileId="9838">
        <src>https://repository.horizon.ac.id/files/original/b1bd26e9fce2adb100643f307c1a1318.pdf</src>
        <authentication>a04c2e1c3b2c4fd013881786ab5323d3</authentication>
      </file>
    </fileContainer>
    <collection collectionId="749">
      <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="105044">
                  <text>VOL. 22, NO.1 2024</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="105089">
                <text>Classification of Solo Batik patterns using deep learning convolutional neural networks algorithm</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105090">
                <text>Accuracy&#13;
Batik Solo motif&#13;
Convolutional neural networks&#13;
Dropout&#13;
Image processing</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105091">
                <text>The ideology of the Solo Batik pattern has not been conveyed to the public. In addition, a lot of people are unaware that batik contains particular patterns that are also used for particular activities. This study uses a convolutional neural network model to categorize 9 different Solo Batik patterns according to their use of elaborate geometric shapes, complicated symbols, patterns, dots, and natural designs. With 1 to 4 hidden layers, we aim to select the number of hidden layers that yields the highest accuracy. A 100×100 pixel image is used as the input. The feature extraction process then makes use of 3×3 feature maps from three convolution layers. The dropout regularization is then added, with settings ranging from 0.1 to 0.9. The Adam algorithm is also used in this model to perform optimization. The 3-layered convolutional neural networks (CNN) with a dropout value of 0.2, run in 20 epochs, produced accuracy results of 97.77%, which was the highest. Additionally, it can be inferred that applying a certain number of hidden layers and adding right dropout regularization values has an impact on raising the accuracy score.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105092">
                <text>Dimas Aryo Anggoro1, Assyati Amadjida Tamimi Marzuki1, Wiwit Supriyanti2</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="105093">
                <text>Journal homepage: http://telkomnika.uad.ac.id</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="105094">
                <text>Aug 15, 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105095">
                <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="105096">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105097">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105098">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12546">
        <name>Accuracy Batik Solo motif Convolutional neural networks Dropout Image processing</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="9822" public="1" featured="1">
    <fileContainer>
      <file fileId="9835">
        <src>https://repository.horizon.ac.id/files/original/f86dec38182dd3faeba7959dfd1f8b4d.pdf</src>
        <authentication>808f758f83a6e599d0b40ad2f327ae82</authentication>
      </file>
    </fileContainer>
    <collection collectionId="749">
      <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="105044">
                  <text>VOL. 22, NO.1 2024</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="105057">
                <text>Internet of things system for lime planting in Maha Sarakham community</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105058">
                <text>Internet of things&#13;
Lime planting&#13;
Maha Sarakham&#13;
Smart farm&#13;
Thailand</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105059">
                <text>The objectives of this research were: i) to study components of the internet of things (IoT) system to support community lime planting (CLP); in Maha Sarakham Province; ii) to develop IoT-CLP; and iii) to transfer IoT-CLP to the target community in Maha Sarakham Province. The research tools were: i) IoT-CLP system suitability assessment form; ii) IoT-CLP efficacy evaluation form; iii) a questionnaire to assess the effectiveness of the community lime planting; and iv) a survey of community satisfaction towards IoT-CLP. The research results showed that i) components of IoT-CLP consist of: (1.1) data receivers: soil moisture, temperature, soil pH, fertilizer/nutrient; (1.2) control units: water supply, water spraying, soil pH control, and processing, fertilizer/nutrients; (1.3) operating systems: water supply, water spraying, soil pH communication and distribution system of fertilizer/soil nutrients water; (1.4) mobile application; ii) the effectiveness of IoT-CLP was evaluated at the highest level; and iii) the results of lime cultivation using IoT-CLP showed a higher yield than the traditional practices in terms of the amount of lime, size, and weight. The community was satisfied with IoT-CLP at the highest level.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105060">
                <text>Tharach Arreerard1, Woraphapa Arreerard1, Naphattanon Thongpan1, Niraj Ruangsan2</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="105061">
                <text>Journal homepage: http://telkomnika.uad.ac.id</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="105062">
                <text>Aug 30, 2023</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105063">
                <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="105064">
                <text>pdf</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105065">
                <text>english</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="105066">
                <text>text</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="12541">
        <name>Internet of things Lime planting Maha Sarakham Smart farm Thailand</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
