<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="15534" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/15534?output=omeka-xml" accessDate="2026-04-06T11:47:51+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114223">
              <text>An efficient privacy-preserving model based on OMFTSA for query optimization in crowdsourcing</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114224">
              <text>crowdsourcing; moth flame-based tunicate swarm algorithm; query; select and join queries</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114225">
              <text>Crowdsourcing is now one of the most important and transformative paradigms, with great success in a variety of application tasks. Crowdsourcing obtains knowledge and information to solve cognitive or intelligence-intensive tasks from an evolving group of participants via the Internet. Unfortunately, providing a hard privacy guarantee and query optimization is incompatible when a higher task acceptance rate needs to be accomplished and this case is common in most existing crowdsourcing solutions. The state of art systems suffered from different complexities such as lack of crowdsourcing optimization techniques, increased cost, latency, security, and scalability issues. In this paper, we have proposed a crowdsourcing model to optimize the cost and latency, issues that occur while query optimization using the Moth Flame and Tunicate Swarm Algorithm (MF-TSA). The TSA algorithm is added to the MF algorithm to enhance its exploitation capability and yield fast convergence. The data privacy concerns of the worker and the requestor are addressed using homomorphic encryption that simultaneously enhances the efficiency of the crowdsourcing framework. The main aim of this work is to optimize the cost and latency for query plan selection along with security. Initially, the homomorphic encryption model is used to encrypt the data. In query design, two kinds of crowd-controlled administrators, that is, Crowd Powered Selection (CSelect) and Crowd Powered Join (CJoin) are connected for assessing query. The proposed framework utilizes MF-TSA to optimize the selection and join queries with low cost and latency. Finally, the experimental results demonstrate better query optimization performance than other existing algorithms such as sequential, parallel, and CrowdOp.  2021 John Wiley &amp;amp; Sons Ltd.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114226">
              <text>Renukadevi M.; Anita E.A.M.; Mohana Geetha D.</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="114227">
              <text>Concurrency and Computation: Practice and Experience, Vol-33, No. 24</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="114228">
              <text>John Wiley and Sons 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="114229">
              <text>2021-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="114230">
              <text>&lt;a href="https://doi.org/10.1002/cpe.6447" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1002/cpe.6447&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85109413408&amp;amp;doi=10.1002%2Fcpe.6447&amp;amp;partnerID=40&amp;amp;md5=287f53542d164da307755f889245bb4b" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85109413408&amp;amp;doi=10.1002%2fcpe.6447&amp;amp;partnerID=40&amp;amp;md5=287f53542d164da307755f889245bb4b&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114231">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="114232">
              <text>ISSN: 15320626; CODEN: CCPEB</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="114233">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114234">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="114235">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="114236">
              <text>Renukadevi M., Department of CSE, S.A. Engineering College, Chennai, India; Anita E.A.M., Department of CSE, School of Engineering and Technology, CHRIST University, Bengaluru, India; Mohana Geetha D., Department of Electronics and Communication Engineering, Sri Krishna College of Engineering and Technology, Coimbatore, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
