<?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://www.ali-omeka.rguclass.com/items/browse?output=omeka-xml&amp;page=2&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-09-09T08:25:44+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>2</pageNumber>
      <perPage>10</perPage>
      <totalResults>17</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="10" public="1" featured="0">
    <fileContainer>
      <file fileId="10">
        <src>https://www.ali-omeka.rguclass.com/files/original/c7ca71f675223d04a0b8e77ab2877ae0.pdf</src>
        <authentication>727132ff69735ea0dad8c87465e49303</authentication>
      </file>
    </fileContainer>
    <collection collectionId="21">
      <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="105">
                  <text>Digital Library Software</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="106">
                  <text>Library and Information Science</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107">
                  <text>Books and research Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="108">
                  <text>Akhtarul Ali</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Research Paper</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="120">
                <text>OPEN SOURCE DIGITAL LIBRARY SOFTWARE: A Literature Review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="121">
                <text>Library and Information Science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="122">
                <text>Digital Library initiatives are gaining momentum and many open source digital library software emerged. These developments necessitate universal standard for digital library software. Conforming the software to universal standard means compromising local requirements. No matter how general the software may be, suitability of the digital library software to specific requirements of digital library project will differ from software to software. These variations in digital library software allow ample room for librarians to assess the digital library softwares with the local requirement criterion. To ease assessment/selection process, this paper attempts to evaluate four most popular open source digital library software. Various features of the softwares are comparatively tabled for ready reference.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="123">
                <text> Warr, Hanadashisha</text>
              </elementText>
              <elementText elementTextId="124">
                <text>Hangsing, P </text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="125">
                <text>Elsevier</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="126">
                <text>13 December, 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="127">
                <text>English</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="128">
                <text>https://papers.ssrn.com/sol3/papers.cfm?abstract_id=1639383</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <elementSet elementSetId="4">
        <name>VRA Core</name>
        <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
        <elementContainer>
          <element elementId="53">
            <name>Title</name>
            <description>The title or identifying phrase given to a Work or an Image.</description>
            <elementTextContainer>
              <elementText elementTextId="129">
                <text>OPEN SOURCE DIGITAL LIBRARY SOFTWARE: A Literature Review</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date</name>
            <description>Date or range of dates associated with the creation, design, production, presentation, performance, construction, or alteration, etc. of the work or image. Dates may be expressed as free text or numerical.  In format yyyy-mm-dd yyyy-mm-dd.</description>
            <elementTextContainer>
              <elementText elementTextId="130">
                <text>19 December, 2019</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="57">
            <name>Description</name>
            <description>A free-text note about the Work, Collection, or Image, including comments, description, or interpretation, that gives additional information not recorded in other categories.</description>
            <elementTextContainer>
              <elementText elementTextId="131">
                <text>Digital Library initiatives are gaining momentum and many open source digital library software emerged. These developments necessitate universal standard for digital library software. Conforming the software to universal standard means compromising local requirements. No matter how general the software may be, suitability of the digital library software to specific requirements of digital library project will differ from software to software. These variations in digital library software allow ample room for librarians to assess the digital library softwares with the local requirement criterion. To ease assessment/selection process, this paper attempts to evaluate four most popular open source digital library software. Various features of the softwares are comparatively tabled for ready reference.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="23">
        <name>Library Software</name>
      </tag>
      <tag tagId="24">
        <name>Open Source</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="13" public="1" featured="0">
    <fileContainer>
      <file fileId="13">
        <src>https://www.ali-omeka.rguclass.com/files/original/420b8f760aeee2ac1c509d3e5c385f42.pdf</src>
        <authentication>90590ba8382dec469b2689249a1af6b6</authentication>
      </file>
    </fileContainer>
    <collection collectionId="21">
      <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="105">
                  <text>Digital Library Software</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="106">
                  <text>Library and Information Science</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107">
                  <text>Books and research Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="108">
                  <text>Akhtarul Ali</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Research Paper</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="155">
                <text>Open Source Software for Creation of Digital Library: A Comparative Study of Greenstone Digital Library Software &amp; DSpace</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="156">
                <text>Library and Information Science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="157">
                <text>Softwares now-a-days have become the life line of modern day organizations. Organizations cannot think of doing their tasks effectively and efficiently without softwares. The extremely competitive environment, zero deficiency and enhanced productivity has made it mandatory for the organizations to carefully choose the appropriate software after comprehensive needs assessment. Softwares simply their tasks and saves a lot of precious time which can be utilized in managing other important issues. Libraries also need softwares if they want to create a parallel digital library with features which we may not find in a traditional library. There are several open source softwares available to create a digital library. For this, firstly the library professionals should be aware of the advantages of open source software and should involve in their development. They should have basic knowledge about the selection, installation and maintenance. Open source software requires a greater degree of computing responsibility than commercial software. Digitization involves huge money to create and maintain and the OSS appears to be a means to reduce it. Among these, DSpace and Greenstone are becoming more popular in India and abroad. This paper deals with the comparison of these two popular OSS from various points of view. The comparative table may help the professionals who are planning to create a digital library.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="158">
                <text> Randhawa, Sukhwinder</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="159">
                <text>Red Flower Publication Pvt. Ltd.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="40">
            <name>Date</name>
            <description>A point or period of time associated with an event in the lifecycle of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="160">
                <text>December, 2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="161">
                <text>English</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="162">
                <text>http://hdl.handle.net/10150/299576&#13;
</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <elementSet elementSetId="4">
        <name>VRA Core</name>
        <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
        <elementContainer>
          <element elementId="53">
            <name>Title</name>
            <description>The title or identifying phrase given to a Work or an Image.</description>
            <elementTextContainer>
              <elementText elementTextId="163">
                <text>Open Source Software for Creation of Digital Library: A Comparative Study of Greenstone Digital Library Software &amp; DSpace</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date</name>
            <description>Date or range of dates associated with the creation, design, production, presentation, performance, construction, or alteration, etc. of the work or image. Dates may be expressed as free text or numerical.  In format yyyy-mm-dd yyyy-mm-dd.</description>
            <elementTextContainer>
              <elementText elementTextId="164">
                <text>December, 2012</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="57">
            <name>Description</name>
            <description>A free-text note about the Work, Collection, or Image, including comments, description, or interpretation, that gives additional information not recorded in other categories.</description>
            <elementTextContainer>
              <elementText elementTextId="165">
                <text>Softwares now-a-days have become the life line of modern day organizations. Organizations cannot think of doing their tasks effectively and efficiently without softwares. The extremely competitive environment, zero deficiency and enhanced productivity has made it mandatory for the organizations to carefully choose the appropriate software after comprehensive needs assessment. Softwares simply their tasks and saves a lot of precious time which can be utilized in managing other important issues. Libraries also need softwares if they want to create a parallel digital library with features which we may not find in a traditional library. There are several open source softwares available to create a digital library. For this, firstly the library professionals should be aware of the advantages of open source software and should involve in their development. They should have basic knowledge about the selection, installation and maintenance. Open source software requires a greater degree of computing responsibility than commercial software. Digitization involves huge money to create and maintain and the OSS appears to be a means to reduce it. Among these, DSpace and Greenstone are becoming more popular in India and abroad. This paper deals with the comparison of these two popular OSS from various points of view. The comparative table may help the professionals who are planning to create a digital library.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="30">
        <name>DSpace</name>
      </tag>
      <tag tagId="29">
        <name>Open Source Software</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="8" public="1" featured="0">
    <fileContainer>
      <file fileId="8">
        <src>https://www.ali-omeka.rguclass.com/files/original/4fce46e0fcb8407594344ea04b594eb4.pdf</src>
        <authentication>b0fd855c9fa069baaa314262f8734f95</authentication>
      </file>
    </fileContainer>
    <collection collectionId="20">
      <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="75">
                  <text>Business Management</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="76">
                  <text>Commerce</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Research Paper</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="92">
                <text>The Influence of Business Managers' IT Competence on Championing IT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="93">
                <text>Commerec</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="94">
                <text>With the increased importance of IT in organizations, business managers are now expected to show stronger leadership in regard to its deployment of IT in organizations. This requires greater focus on their capability to understand and use IT resources effectively. This paper explores the concept of IT competence of business managers as a contributor to their intention to champion IT within their organizations. Based on the knowledge literature, IT competence is defined as “ the set of IT-related knowledge and experience that a business manager possesses.”&#13;
&#13;
The relationship between IT knowledge, IT experience, and championing IT is tested empirically using Structural Equation Modeling with LISREL. Four hundred and four business managers from two large insurance organizations were surveyed. Specific areas of IT knowledge and IT experience were first identified and the first half of the data set was utilized to assess the measurement properties of the instrument in a confirmatory analysis. The contribution of IT knowledge and IT experience to their intention to champion IT was assessed using the second half of the data set. The results show that IT knowledge and IT experience together explain 34% of the variance in managers' intentions to champion IT. Recommendations are given as to how organizations can enhance their business managers IT knowledge and experience to achieve stronger IT leadership from line people.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="95">
                <text>Bassellier, Geneviève</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="96">
                <text>Inform Pubs Online</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="37">
            <name>Contributor</name>
            <description>An entity responsible for making contributions to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="97">
                <text> Benbasat, Izak</text>
              </elementText>
              <elementText elementTextId="98">
                <text>  Reich, Blaize Horner</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="99">
                <text>English</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="100">
                <text>https://pubsonline.informs.org/doi/abs/10.1287/isre.14.4.317.24899</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="72">
            <name>Abstract</name>
            <description>A summary of the resource.</description>
            <elementTextContainer>
              <elementText elementTextId="101">
                <text>With the increased importance of IT in organizations, business managers are now expected to show stronger leadership in regard to its deployment of IT in organizations. This requires greater focus on their capability to understand and use IT resources effectively. This paper explores the concept of IT competence of business managers as a contributor to their intention to champion IT within their organizations. Based on the knowledge literature, IT competence is defined as “ the set of IT-related knowledge and experience that a business manager possesses.”&#13;
&#13;
The relationship between IT knowledge, IT experience, and championing IT is tested empirically using Structural Equation Modeling with LISREL. Four hundred and four business managers from two large insurance organizations were surveyed. Specific areas of IT knowledge and IT experience were first identified and the first half of the data set was utilized to assess the measurement properties of the instrument in a confirmatory analysis. The contribution of IT knowledge and IT experience to their intention to champion IT was assessed using the second half of the data set. The results show that IT knowledge and IT experience together explain 34% of the variance in managers' intentions to champion IT. Recommendations are given as to how organizations can enhance their business managers IT knowledge and experience to achieve stronger IT leadership from line people.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <elementSet elementSetId="4">
        <name>VRA Core</name>
        <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
        <elementContainer>
          <element elementId="53">
            <name>Title</name>
            <description>The title or identifying phrase given to a Work or an Image.</description>
            <elementTextContainer>
              <elementText elementTextId="102">
                <text>The Influence of Business Managers' IT Competence on Championing IT</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date</name>
            <description>Date or range of dates associated with the creation, design, production, presentation, performance, construction, or alteration, etc. of the work or image. Dates may be expressed as free text or numerical.  In format yyyy-mm-dd yyyy-mm-dd.</description>
            <elementTextContainer>
              <elementText elementTextId="103">
                <text>December 01, 2003</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="57">
            <name>Description</name>
            <description>A free-text note about the Work, Collection, or Image, including comments, description, or interpretation, that gives additional information not recorded in other categories.</description>
            <elementTextContainer>
              <elementText elementTextId="104">
                <text>With the increased importance of IT in organizations, business managers are now expected to show stronger leadership in regard to its deployment of IT in organizations. This requires greater focus on their capability to understand and use IT resources effectively. This paper explores the concept of IT competence of business managers as a contributor to their intention to champion IT within their organizations. Based on the knowledge literature, IT competence is defined as “ the set of IT-related knowledge and experience that a business manager possesses.”&#13;
&#13;
The relationship between IT knowledge, IT experience, and championing IT is tested empirically using Structural Equation Modeling with LISREL. Four hundred and four business managers from two large insurance organizations were surveyed. Specific areas of IT knowledge and IT experience were first identified and the first half of the data set was utilized to assess the measurement properties of the instrument in a confirmatory analysis. The contribution of IT knowledge and IT experience to their intention to champion IT was assessed using the second half of the data set. The results show that IT knowledge and IT experience together explain 34% of the variance in managers' intentions to champion IT. Recommendations are given as to how organizations can enhance their business managers IT knowledge and experience to achieve stronger IT leadership from line people.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="20">
        <name>Influence of Business</name>
      </tag>
      <tag tagId="21">
        <name>IT Competence</name>
      </tag>
      <tag tagId="22">
        <name>IT in Business</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="17" public="1" featured="0">
    <fileContainer>
      <file fileId="17">
        <src>https://www.ali-omeka.rguclass.com/files/original/9a710cf7df6986c054595b4b81b41eb5.jpg</src>
        <authentication>12fb12fecd580e5063c22ef2e40f9af2</authentication>
      </file>
    </fileContainer>
    <collection collectionId="22">
      <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="166">
                  <text>RGU Gallery</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="167">
                  <text>Gallery</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="168">
                  <text>Images and Videos</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
        <elementSet elementSetId="4">
          <name>VRA Core</name>
          <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
          <elementContainer>
            <element elementId="53">
              <name>Title</name>
              <description>The title or identifying phrase given to a Work or an Image.</description>
              <elementTextContainer>
                <elementText elementTextId="169">
                  <text>RGU Gallery</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="207">
              <text>JPG</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="10">
          <name>Physical Dimensions</name>
          <description>The actual physical size of the original image</description>
          <elementTextContainer>
            <elementText elementTextId="208">
              <text>552 x 800</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="200">
                <text>The Notre-Dame Cathedral in Art (1460–1921)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="201">
                <text>Photography</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="202">
                <text>Like many around the world, we were so sad and shocked to see the Notre-Dame burning — to witness such history in flames. But also relieved to learn now that so much was saved, including the main structure and many of its stunning stained-glass windows. We spent the day yesterday picking out highlights from the many centuries of artworks to feature the iconic building — from its illuminated punctuation of medieval skylines to grainy detailed studies at the birth of photography. We are presenting them here in rough chronological order, which we hope gives a sense of how this magnificent building — more than eight centuries old — has inspired and outlasted so many epochs and lives and, thanks to the dedication of another generation…</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="203">
                <text>Paris: Photographs in Colour</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="204">
                <text>Rijksmuseum</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="205">
                <text>ca. 1910</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="206">
                <text>https://pdimagearchive.org/images/f2694c5d-690c-4105-b241-68eeb9648bd6/</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <elementSet elementSetId="4">
        <name>VRA Core</name>
        <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
        <elementContainer>
          <element elementId="53">
            <name>Title</name>
            <description>The title or identifying phrase given to a Work or an Image.</description>
            <elementTextContainer>
              <elementText elementTextId="209">
                <text>The Notre-Dame Cathedral in Art (1460–1921)</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date</name>
            <description>Date or range of dates associated with the creation, design, production, presentation, performance, construction, or alteration, etc. of the work or image. Dates may be expressed as free text or numerical.  In format yyyy-mm-dd yyyy-mm-dd.</description>
            <elementTextContainer>
              <elementText elementTextId="210">
                <text>ca. 1910</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="57">
            <name>Description</name>
            <description>A free-text note about the Work, Collection, or Image, including comments, description, or interpretation, that gives additional information not recorded in other categories.</description>
            <elementTextContainer>
              <elementText elementTextId="211">
                <text>Like many around the world, we were so sad and shocked to see the Notre-Dame burning — to witness such history in flames. But also relieved to learn now that so much was saved, including the main structure and many of its stunning stained-glass windows. We spent the day yesterday picking out highlights from the many centuries of artworks to feature the iconic building — from its illuminated punctuation of medieval skylines to grainy detailed studies at the birth of photography. We are presenting them here in rough chronological order, which we hope gives a sense of how this magnificent building — more than eight centuries old — has inspired and outlasted so many epochs and lives and, thanks to the dedication of another generation…</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="16" public="1" featured="0">
    <fileContainer>
      <file fileId="16">
        <src>https://www.ali-omeka.rguclass.com/files/original/bd3b151a67443067e08a2fea0efca216.jpg</src>
        <authentication>bf73d03d4d7be73edf7af6f2de3b9a62</authentication>
      </file>
    </fileContainer>
    <collection collectionId="22">
      <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="166">
                  <text>RGU Gallery</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="167">
                  <text>Gallery</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="168">
                  <text>Images and Videos</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
        <elementSet elementSetId="4">
          <name>VRA Core</name>
          <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
          <elementContainer>
            <element elementId="53">
              <name>Title</name>
              <description>The title or identifying phrase given to a Work or an Image.</description>
              <elementTextContainer>
                <elementText elementTextId="169">
                  <text>RGU Gallery</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="6">
      <name>Still Image</name>
      <description>A static visual representation. Examples include paintings, drawings, graphic designs, plans and maps. Recommended best practice is to assign the type Text to images of textual materials.</description>
      <elementContainer>
        <element elementId="7">
          <name>Original Format</name>
          <description>The type of object, such as painting, sculpture, paper, photo, and additional data</description>
          <elementTextContainer>
            <elementText elementTextId="195">
              <text>JPG</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="10">
          <name>Physical Dimensions</name>
          <description>The actual physical size of the original image</description>
          <elementTextContainer>
            <elementText elementTextId="196">
              <text>601 x 800</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="190">
                <text>The Right Hand of God Protecting the Faithful against the Demons</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="191">
                <text>Photography</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="192">
                <text>Like many around the world, we were so sad and shocked to see the Notre-Dame burning — to witness such history in flames. But also relieved to learn now that so much was saved, including the main structure and many of its stunning stained-glass windows. We spent the day yesterday picking out highlights from the many centuries of artworks to feature the iconic building — from its illuminated punctuation of medieval skylines to grainy detailed studies at the birth of photography. We are presenting them here in rough chronological order, which we hope gives a sense of how this magnificent building — more than eight centuries old — has inspired and outlasted so many epochs and lives and, thanks to the dedication of another generation…</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="193">
                <text>The Metropolitan Museum</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="194">
                <text>ca. 1460</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="212">
                <text>Hours of Étienne Chevalier</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <elementSet elementSetId="4">
        <name>VRA Core</name>
        <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
        <elementContainer>
          <element elementId="53">
            <name>Title</name>
            <description>The title or identifying phrase given to a Work or an Image.</description>
            <elementTextContainer>
              <elementText elementTextId="197">
                <text>The Right Hand of God Protecting the Faithful against the Demons</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date</name>
            <description>Date or range of dates associated with the creation, design, production, presentation, performance, construction, or alteration, etc. of the work or image. Dates may be expressed as free text or numerical.  In format yyyy-mm-dd yyyy-mm-dd.</description>
            <elementTextContainer>
              <elementText elementTextId="198">
                <text>ca. 1460</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="57">
            <name>Description</name>
            <description>A free-text note about the Work, Collection, or Image, including comments, description, or interpretation, that gives additional information not recorded in other categories.</description>
            <elementTextContainer>
              <elementText elementTextId="199">
                <text>Like many around the world, we were so sad and shocked to see the Notre-Dame burning — to witness such history in flames. But also relieved to learn now that so much was saved, including the main structure and many of its stunning stained-glass windows. We spent the day yesterday picking out highlights from the many centuries of artworks to feature the iconic building — from its illuminated punctuation of medieval skylines to grainy detailed studies at the birth of photography. We are presenting them here in rough chronological order, which we hope gives a sense of how this magnificent building — more than eight centuries old — has inspired and outlasted so many epochs and lives and, thanks to the dedication of another generation…</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1" public="1" featured="0">
    <fileContainer>
      <file fileId="1">
        <src>https://www.ali-omeka.rguclass.com/files/original/52541c032a295df0518e708cb0466ef9.pdf</src>
        <authentication>f807e441d9d694df384bb05244365322</authentication>
      </file>
    </fileContainer>
    <collection collectionId="1">
      <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="1">
                  <text>Library and Information Science</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="23">
                  <text>Research Papers-Library Science</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Research Paper</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="3">
                <text>Towards mapping library and information science</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="4">
                <text>In an earlier study by the authors, full-text analysis and traditional bibliometric methods were combined to map research papers published in the journal Scientometrics. The main objective was to develop appropriate techniques of full-text analysis and to improve the efficiency of the individual methods in the mapping of science. The number of papers was, however, rather limited. In the present study, we extend the quantitative linguistic part of the previous studies to a set of five journals representing the field of Library and Information Science (LIS). Almost 1000 articles and notes published in the period 2002–2004 have been selected for this exercise. The optimum solution for clustering LIS is found for six clusters. The combination of different mapping techniques, applied to the full text of scientific publications, results in a characteristic tripod pattern. Besides two clusters in bibliometrics, one cluster in information retrieval and one containing general issues, webometrics and patent studies are identified as small but emerging clusters within LIS. The study is concluded with the analysis of cluster representations by the selected journals.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="5">
                <text>Frizo Janssens </text>
              </elementText>
              <elementText elementTextId="6">
                <text>Jacqueline Leta</text>
              </elementText>
              <elementText elementTextId="7">
                <text>Wolfgang Glänzel</text>
              </elementText>
              <elementText elementTextId="8">
                <text>Bart L.R. de Moor</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="9">
                <text>Elsevier</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="10">
                <text>Digital</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="11">
                <text>English</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="12">
                <text>https://doi.org/10.1016/j.ipm.2006.03.025</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="3">
        <name>Epistemological</name>
      </tag>
      <tag tagId="1">
        <name>Information Science</name>
      </tag>
      <tag tagId="2">
        <name>Library Science</name>
      </tag>
    </tagContainer>
  </item>
  <item itemId="11" public="1" featured="0">
    <fileContainer>
      <file fileId="11">
        <src>https://www.ali-omeka.rguclass.com/files/original/271b460013f1818383900a8462868870.pdf</src>
        <authentication>8dc5678f7c3e3b6e1d458e9009f155f0</authentication>
      </file>
    </fileContainer>
    <collection collectionId="21">
      <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="105">
                  <text>Digital Library Software</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="49">
              <name>Subject</name>
              <description>The topic of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="106">
                  <text>Library and Information Science</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="41">
              <name>Description</name>
              <description>An account of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="107">
                  <text>Books and research Papers</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="39">
              <name>Creator</name>
              <description>An entity primarily responsible for making the resource</description>
              <elementTextContainer>
                <elementText elementTextId="108">
                  <text>Akhtarul Ali</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="18">
      <name>Research Paper</name>
      <description/>
    </itemType>
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="132">
                <text>Utilization of Alkin-WP-Based Digital Library Evaluation&#13;
Software as Evaluation Tool of Digital Library Effectiveness</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="133">
                <text>One source of learning in universities is a digital library. In the era of industry 4.0, most universities have implemented digital libraries in supporting the learning process. However, the reality shows that digital library management is still ineffective. Therefore, the implementation of digital libraries needs to be evaluated for determining the digital library effectiveness used as learning resources in supporting the learning process in universities. Many evaluation tools are used to evaluate the effectiveness of digital libraries but have not provided accurate recommendation results to support decision-making. This research presents an innovation in the form of an evaluation tool that can be used to evaluate the digital library effectiveness in universities. That evaluation tool is called the Alkin-WP-based digital library evaluation software. This software is a desktop platform that contains aspects of measuring the digital library effectiveness by referring to the components of the Alkin evaluation model and the WP (Weighted Product) method. This research aimed to show the effectiveness level of the utilization of Alkin-WP-based digital library evaluation software. This research method was R &amp; D (Research &amp; Development) which refers to the ten development stages of the Borg and Gall model. In this research, development was focused only on a few stages, included: usage trials, final product revision, dissemination, and implementation. The subjects involved in assessing the implementation/utilization of the Alkin-WP-based digital library evaluation software were 35 people, in the usage trials were six people, in product revision were three people, and at the stage of dissemination were 15 people. The tools used to collect data were questionnaires and interview guidelines. The data analysis technique used was descriptive quantitative. The effectiveness level of utilizing the Alkin-WP-based digital library evaluation software was 88.34%. It showed that the evaluation software had effective. The impact of this research results on the scientific field of educational evaluation is being able to show the existence of a new evaluation tool based on educational evaluation and artificial intelligence. That evaluation tool can easier for library heads to make policies for revamping digital library services based on accurate recommendations.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="134">
                <text> Divayana, Dewa Gede Hendra</text>
              </elementText>
              <elementText elementTextId="135">
                <text>Ariawan,  I Putu Wisna</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="136">
                <text>Emerging Science Journal</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="137">
                <text>01 October, 2021</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="138">
                <text>English</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="139">
                <text>http://dx.doi.org/10.28991/esj-2021-01308 </text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
      <elementSet elementSetId="4">
        <name>VRA Core</name>
        <description>VRA Core standard for artistic pieces and cultural heritage artifacts.
                                The first input will be treated as a &lt;display&gt; element. More detailed
                                VRA Core metadata is available below that input.
                             </description>
        <elementContainer>
          <element elementId="53">
            <name>Title</name>
            <description>The title or identifying phrase given to a Work or an Image.</description>
            <elementTextContainer>
              <elementText elementTextId="140">
                <text>Utilization of Alkin-WP-Based Digital Library Evaluation&#13;
Software as Evaluation Tool of Digital Library Effectiveness</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="56">
            <name>Date</name>
            <description>Date or range of dates associated with the creation, design, production, presentation, performance, construction, or alteration, etc. of the work or image. Dates may be expressed as free text or numerical.  In format yyyy-mm-dd yyyy-mm-dd.</description>
            <elementTextContainer>
              <elementText elementTextId="141">
                <text>01 October, 2021</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="57">
            <name>Description</name>
            <description>A free-text note about the Work, Collection, or Image, including comments, description, or interpretation, that gives additional information not recorded in other categories.</description>
            <elementTextContainer>
              <elementText elementTextId="142">
                <text>One source of learning in universities is a digital library. In the era of industry 4.0, most universities have implemented digital libraries in supporting the learning process. However, the reality shows that digital library management is still ineffective. Therefore, the implementation of digital libraries needs to be evaluated for determining the digital library effectiveness used as learning resources in supporting the learning process in universities. Many evaluation tools are used to evaluate the effectiveness of digital libraries but have not provided accurate recommendation results to support decision-making. This research presents an innovation in the form of an evaluation tool that can be used to evaluate the digital library effectiveness in universities. That evaluation tool is called the Alkin-WP-based digital library evaluation software. This software is a desktop platform that contains aspects of measuring the digital library effectiveness by referring to the components of the Alkin evaluation model and the WP (Weighted Product) method. This research aimed to show the effectiveness level of the utilization of Alkin-WP-based digital library evaluation software. This research method was R &amp; D (Research &amp; Development) which refers to the ten development stages of the Borg and Gall model. In this research, development was focused only on a few stages, included: usage trials, final product revision, dissemination, and implementation. The subjects involved in assessing the implementation/utilization of the Alkin-WP-based digital library evaluation software were 35 people, in the usage trials were six people, in product revision were three people, and at the stage of dissemination were 15 people. The tools used to collect data were questionnaires and interview guidelines. The data analysis technique used was descriptive quantitative. The effectiveness level of utilizing the Alkin-WP-based digital library evaluation software was 88.34%. It showed that the evaluation software had effective. The impact of this research results on the scientific field of educational evaluation is being able to show the existence of a new evaluation tool based on educational evaluation and artificial intelligence. That evaluation tool can easier for library heads to make policies for revamping digital library services based on accurate recommendations.</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
    <tagContainer>
      <tag tagId="25">
        <name>Alkin</name>
      </tag>
      <tag tagId="26">
        <name>Digital Library</name>
      </tag>
      <tag tagId="28">
        <name>Effectiveness</name>
      </tag>
      <tag tagId="27">
        <name>Evaluation Software</name>
      </tag>
    </tagContainer>
  </item>
</itemContainer>
