<?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="http://unsyiana.usk.ac.id/items/browse?output=omeka-xml&amp;page=551&amp;sort_field=added" accessDate="2026-07-29T23:17:59+07:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>551</pageNumber>
      <perPage>10</perPage>
      <totalResults>15608</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="7963" public="1" featured="0">
    <collection collectionId="26">
      <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="31035">
                  <text>e-Journal USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74940">
                <text>Masrizal, Masrizal</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="74942">
                <text>2014-10-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74944">
                <text>This study examines how negotiation of meaning contributes to second language interaction. The discussion  in  this  study  is  based on Michael H. Long’s 1996 Interaction Hypothesis suggesting that environment contributes to the development of second language acquisition. Long proposes that environmental contributions to acquisition are mediated by selective attention and the learner’s processing capacity during negotiation for meaning. To support this belief, recent empirical studies are also presented in this article. Three negotiation for meaning strategies are discussed in this study to mirror and provide evidence  for  Long’s proposal, including several  excerpts from  conversations  collected from daily natural conversations  and other recorded sources. The strategies include (1) clarification requests, (2) confirmation checks, and (3) comprehension checks. The study has been able to prove that learner’s L2 acquisition takes advantage  of environmental contributions mediated by selective attention and the learner’s developing L2 processing capacity brought together during negotiation of meaning.</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="74946">
                <text>application/pdf</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="74947">
                <text>http://jurnal.unsyiah.ac.id/SiELE/article/view/1829</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74948">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="74950">
                <text>University of Syiah Kuala</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="74952">
                <text>http://jurnal.unsyiah.ac.id/SiELE/article/view/1829/1725</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="74954">
                <text>Studies in English Language and Education; Vol 1, No 2 (2014); 107-116</text>
              </elementText>
              <elementText elementTextId="74956">
                <text>2355-2794</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74957">
                <text>Negotiation of meaning; Long's Interaction Hypothesis; Interaction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74958">
                <text>The Role of Negotiation of Meaning in L2 Interactions:An Analysis from the Perspective of Long’s Interaction Hypothesis</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74960">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="74962">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="142050">
                <text/>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="142049">
                <text/>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7964" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74949">
                <text>Said Hafiz</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74951">
                <text>Sistem Kartu Rencana Studi (KRS) online pada Universitas Syiah Kuala (Unsyiah) menyediakan beberapa fitur didalamnya seperti : isi KRS, melihat Kartu Hasil Studi (KHS), transkrip nilai, upload TA dan lain-lain. Pada KRS online tidak terdapat modul untuk melihat jadwal kuliah. Sebelum membuat sebuah aplikasi yang nyata maka harus dilakukan pengujian terlebih dahulu pada sebuah prototype. Web service yang digunakan pada penelitian ini adalah restful yang mendukung dua format data XML dan JSON. Pengaksesan data didalam web service terdapat proses parsing data saat mengakses data base pada aplikasi. Pada penelitian ini penulis ingin melihat kecepatan proses parsing data dari kedua format data tersebut yang akan diterapkan pada prototype aplikasi jadwal kuliah di emulator android. Dari pengujian ini diharapkan akan didapat format data yang lebih cepat antara XML dan JSON saat di akses dengan menggunakan prototype emulator android dan diharapkan dapat menjadi acuan sebagai pengembangan aplikasi jadwal kuliah berbasis android. Setelah penelitian dilakukan maka hasil perbandingan yang didapat adalah eksekusi waktu dari XML dan JSON tidak memiliki perbedaan yang signifikan saat memparsing data.</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="74953">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7449</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74955">
                <text>PERBANDINGAN WAKTU PARSING FORMAT DATA XML DAN JSON MENGGUNAKAN RESTFUL WEB SERVICE UNTUK PENGAMBILAN DATA JADWAL MATA KULIAH BERBASIS EMULATOR ANDROID</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7965" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74959">
                <text>Aziz Fahlafi</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74961">
                <text>Sistem pembayaran SPP host to host merupakansebuah sistem pembayaran SPP yang di rancang untuk menghubungkan sistem keuangan sebuah perguruan tinggi dengan beberapa sistem transaksi perbankan untuk memudahkan jalannya pembayaran SPP. Beberapa universitas terkemuka yang sudah menerapkanSistem SPP host to host ini terlebih dahulu seperti, UI, UIN Malang, UGM, dan UNPAD.Pada UNSYIAH sendiri sistem pembayaran SPPhost to host merupakan sistem yang baru diterapkan, dan belum ada pengujian terhadap kinerja sistem pembayaran SPP host to host oleh karena itu pada tugas akhir ini dilakukan pengujian terhadap aplikasi webservice yang terdapat dalam sistem SPP host to hostUNSYIAH. Metode yang digunakan untuk menguji adalah menghitung waktu dari transfer data antara apliaksi web service dengan aplikasi bank unsyiah yang dibangun. Kemudian waktu dari proses ini akan dianalisis dengan standar waktu transfer data. Dari hasil pengujiansistem layanan pembayaran SPP host to host dengan menggunakan restfull web service yang dibangun oleh Universitas Syiah Kuala,terbukti efektif  dilihat dari waktu rata-rata yang tercatat tidak ada waktu transfer di atas batas waktu 0,7 ms dengan akses internet 1 Mbps. Sistem pembayaran SPP host to host yang dibangun oleh UNSYIAH telah dapat bekerja dengan baik, hal ini dapat dilihat dari waktu pengujian yang tidak berada di atas batas kecepatan retrieval data.</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="74963">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7450</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74964">
                <text>ANALISIS PENGAMBILAN DATA UNTUK SISTEM HOST TO HOST PEMBAYARAN SPP UNSYIAH DENGAN MENGGUNAKAN RESTFUL WEB SERVICE</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7966" public="1" featured="0">
    <collection collectionId="26">
      <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="31035">
                  <text>e-Journal USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74965">
                <text>Eridafithri, Eridafithri</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="74966">
                <text>2015-03-16</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74968">
                <text>Portfolios are one of the alternatives that can be used for writing assessment. Portfolios are not common in the curriculum. The lack of dissemination to language teachers have made portfolios disregarded. In order to encourage teachers to use portfolios for assessment of writing, they need to have adequate information about portfolios, how they can be used for assessment as well as the benefits of using them for assessment. This study discusses why teachers do not use portfolios for assessing writing done by senior high school students. It focuses on English teachers at Islamic senior high schools in Banda Aceh and Aceh Besar, and also looks at alternatives to help teachers use portfolios for assessment. The 26 teachers who participated in this study were given a questionnaire in order to find out their background knowledge related to portfolios and the difficulties they faced as teachers. Data from the questionnaire was supported by observations made by the researcher whilst monitoring their teaching. The results of this study showed that a large percentage of teachers found it difficult to design a rubric/set of instructions for using portfolios for writing assessment, whilst from the observation it was revealed that the complexities of correcting portfolios discouraged them from using portfolios as one of their means of assessment.  </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="74970">
                <text>application/pdf</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="74972">
                <text>http://jurnal.unsyiah.ac.id/SiELE/article/view/2231</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74974">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="74975">
                <text>University of Syiah Kuala</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="74976">
                <text>http://jurnal.unsyiah.ac.id/SiELE/article/view/2231/2160</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74978">
                <text>Copyright (c) 2015 Studies in English Language and Education</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="74980">
                <text>Studies in English Language and Education; Vol 2, No 1 (2015); 1-16</text>
              </elementText>
              <elementText elementTextId="74982">
                <text>2355-2794</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74984">
                <text>Portfolios; classroom assessment; competency based learning; school based syllabus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74985">
                <text>The Application of Portfolios to Assess Progress in Writing of EFL Students at Secondary Schools in Banda Aceh</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74986">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="74988">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="142083">
                <text/>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="142082">
                <text/>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7967" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74967">
                <text>Rifki Asmana</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74969">
                <text>Alumni merupakan salah satu aset untuk meningkatkan mutu sistem dan reputasi lembaga pendidikan. Di Jurusan Teknik Elektro Universitas Syiah Kuala telah ada wadah alumni IKATEKTRO (Ikatan Alumni Teknik Elektro), untuk meningkatkan efektifitas, efisiensi dan partisipasi alumni maka perlu dirancang sistem informasi pendataan alumni yang interaktif berbasis web sesuai kebutuhan pengguna. Penerapan salah satu pemanfaatan user centered design (UCD) yaitu metode contextual design mengutamakan pengguna sebagai pusat perancangan, pembuatan sampai pengujian sistem. Pendekatan dengan pengguna melalui tahapan proses user analysis, contextual interview dan visioning. Kemudian sistem diimplementasikan dengan perancangan prototipe dan dilakukan pengujian task analysis. Hasilnya sistem informasi pendataan yang telah dirancang bersifat dinamis seiring keinginan user, memenuhi kebutuhan user, meningkatkan mutu sistem lebih efektif dan efisien dengan nilai ketuntasan task sebesar 92.7 %, waktu pengerjaan yang sedang yakni 23.4 detik, kesalahan dan perulangan task yang sedikit, terutama tujuan sistem yang dirancang dapat memudahkan proses pendataan IKATEKTRO, dan juga area pendataan menjadi lebih luas karena berbasis web serta dapat mendukung sistem yang telah ada.Kata kunci: Sistem informasi pendataan, Alumni, Contextual Design, Web, User Centered Design</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="74971">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7451</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74973">
                <text>PENERAPAN METODE CONTEXTUAL DESIGN PADA PERANCANGAN SISTEM INFORMASI PENDATAAN ALUMNI BERBASIS WEB (STUDI KASUS JURUSAN TEKNIK ELEKTRO UNIVERSITAS SYIAH KUALA)</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7968" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74977">
                <text>Miftahul Jannah</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74979">
                <text>Pasien dengan tuberkulosis sering menjadi sangat lemah karena penyakit kronis yang berkepanjangan yang menyebabkan gangguan status nutrisi. Anoreksia, penurunan berat dan malnutrisi umum terjadi pada pasien dengan tuberkulosis. Kepatuhan pengobatan yang tidak baik merupakan faktor penyebab kegagalan dalam mencapai kesembuhan. Penelitian ini bertujuan untuk mengetahui faktor perilaku dengan kepatuhan menjalani pengobatan Directly Observerd Treatment Shortcourse (DOTS) pada pasien TB Paru di Poliklinik Paru RSUD dr. Zainoel Abidin Banda Aceh tahun 2014. Jenis penelitian yang digunakan adalah deskriptif korelatif dengan desain cross sectional study. Populasinya adalah pasien TB Paru. Metode pengambilan sampel adalah purposive sampling dengan jumlah 75 sampel. Alat pengumpulan data berupa kuesioner dalam bentuk dichotomous choice. Data dianalisis dengan perangkat komputer menggunakan uji chi-square dengan confidence interval 95% dan ? = 0.05. Pengumpulan data dilakukan tanggal 20 Mei sampai dengan 06 Juni 2014 di Poliklinik Paru RSUD dr. Zainoel Abidin Banda Aceh. Hasil uji statistik diketahui bahwa ada hubungan yang signifikan antara pengetahuan (p-value 0.004), sikap (p-value 0.004), pendidikan (p-value 0.004), penghasilan (p-value 0.001), jarak ke pelayanan kesehatan (p-value 0.005), sikap petugas (p-value 0.003), dan dukungan keluarga (p-value 0.004) pasien TB paru dengan kepatuhan menjalani pengobatan DOTS. Diharapkan pasien dan keluarga lebih memperhatikan dan patuh dalam menjalani pengobatan DOTS untuk penyembuhan penyakit tuberkulosis paru yang dideritanya dan perawat lebih meningkatkan promosi kesehatan yang berhubungan dengan tuberkulosis.</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="74981">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7452</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74983">
                <text>HUBUNGAN FAKTOR PERILAKU DENGAN KEPATUHAN MENJALANI PENGOBATAN DIRECTLY OBSERVED TREATMENT SHORTCOURSE RN(DOTS) PADA PASIEN TUBERKULOSIS PARU DI POLIKLINIK PARU RNRUMAH SAKIT UMUM DAERAH DR. ZAINOEL ABIDIN BANDA ACEH RNTAHUN 2014RNHUBUNGAN FAKTOR PERILAKU DENGAN KEPATUHAN MENJALANI PENGOBATAN DIRECTLY OBSERVED TREATMENT SHORTCOURSE (DOTS) PADA PASIEN TUBERKULOSIS PARU DI POLIKLINIK PARU RUMAH SAKIT UMUM DAERAH DR. ZAINOEL ABIDIN BANDA ACEH TAHUN 2014RN(DOTS) PADA PASIEN TUBERKULOSIS PARU DI POLIKLINIK PARU RNRUMAH SAKIT UMUM DAERAH DR. ZAINOEL ABIDIN BANDA ACEH RNTAHUN 2014RNHUBUNGAN FAKTOR PERILAKU DENGAN KEPATUHAN MENJALANI PENGOBATAN DIRECTLY OBSERVED TREATMENT SHORTCOURSE RN(DOTS) PADA PASIEN TUBERKULOSIS PARU DI POLIKLINIK PARU RNRUMAH SAKIT UMUM DAERAH DR. ZAINOEL ABIDIN BANDA ACEH RNTAHUN 2014RNHUBUNGAN FAKTOR PERILAKU DENGAN KEPATUHAN MENJALANI PENGOBATAN DIRECTLY OBSERVED TREATMENT SHORTCOURSE RN(DOTS) PADA PASIEN TUBERKULOSIS PARU DI POLIKLINIK PARU RNRUMAH SAKIT UMUM DAERAH DR. ZAINOEL ABIDIN BANDA ACEH RNTAHUN 2014RNHUBUNGAN FAKTOR PERILAKU DENGAN KEPATUHAN MENJALANI PENGOBATAN DIRECTLY OBSERVED TREAHTMENT</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7969" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74987">
                <text>ikhsan facri</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="74989">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7453</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7970" public="1" featured="0">
    <collection collectionId="26">
      <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="31035">
                  <text>e-Journal USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74990">
                <text>Yasin, Burhanuddin</text>
              </elementText>
              <elementText elementTextId="74992">
                <text>Qamariah, Hijjatul</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="74994">
                <text>2014-03-26</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74996">
                <text>This research attempts to suggest an alternative solution for writers in general and graduate students in particular in writing a proper research article introduction. In order to do so, the authors explored how the Swales’ model is applied in writing a research article introduction. The exploration was approached through a library study on the Swales model application. Some previous studies applying Swales Model were gathered and categorized into three categories − application of Swales model on different types of genre besides the research article introduction, different discipline or field and the last is the application of Swales’ on the research article introduction across languages. Another three articles written by professional writers were also collected as samples of introductions that have successfully presented three obligatory moves – establishing a territory (Move 1), establishing a niche (Move 2) and occupying the niche or presenting the present work (Move 3) − proposed by Swales’ model. Those introductions were segmented into those three moves and analyzed based on a communication purpose in every step derived from each move. In order to add more comprehension about the model, an analysis was also conducted on introductions for seven articles in the English Education Journal (EEJ) published by the Graduate Program in English Language Education at Syiah Kuala University. The purpose of the analysis was to show the differences in structure of introductions organized without following the CARS Swales model. Conclusions are that the CARS Swales model is relevant for the teaching of introductions for research writing and it can be a guideline to teach students the moves and steps of this model for communication purposes.</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="74997">
                <text>application/pdf</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="74998">
                <text>http://jurnal.unsyiah.ac.id/SiELE/article/view/1118</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="75000">
                <text>eng</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="75002">
                <text>University of Syiah Kuala</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="75004">
                <text>http://jurnal.unsyiah.ac.id/SiELE/article/view/1118/1035</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="75005">
                <text>Studies in English Language and Education; Vol 1, No 1 (2014); 31-44</text>
              </elementText>
              <elementText elementTextId="75006">
                <text>2355-2794</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="75008">
                <text/>
              </elementText>
              <elementText elementTextId="142101">
                <text>Swales’ model; Create a Research Space (CARS); Writing; Research Article Introduction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="75010">
                <text>The application of Swales’ model in writing a research article introduction</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="75012">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="75014">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="142102">
                <text/>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="142100">
                <text/>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7971" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74991">
                <text>Wanelfi Nst</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="74993">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7456</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74995">
                <text>PENGARUH POSISI MENYUSUI FOOTBALL HOLD (MENGEPIT) TERHADAP NYERI PERSALINAN PASCA SECTIO CAESAREA DI RUANG SEURUNEE 3 RUMAH SAKIT UMUM DAERAH DR. ZAINOEL ABIDIN BANDA ACEH TAHUN 2014</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="7972" public="1" featured="0">
    <collection collectionId="27">
      <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="31496">
                  <text>ETD USK</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="74999">
                <text>Ramadhanus</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="75001">
                <text>http://etd.unsyiah.ac.id//index.php?p=show_detail&amp;id=7458</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="75003">
                <text>TRANSKRIP NILAI RAMADHANUS</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
