<?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://igi.indrastra.com/items?output=omeka-xml&amp;page=75&amp;sort_field=Dublin+Core%2CTitle" accessDate="2026-05-04T00:13:30+00:00">
  <miscellaneousContainer>
    <pagination>
      <pageNumber>75</pageNumber>
      <perPage>10</perPage>
      <totalResults>3575</totalResults>
    </pagination>
  </miscellaneousContainer>
  <item itemId="2996" public="1" featured="0">
    <collection collectionId="42">
      <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="59641">
                  <text>Indiana International &amp; Comparative Law Review</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="61963">
                <text>Plogstedt, Antoinette</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="61964">
                <text>2013-01-03</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="61965">
                <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="61966">
                <text>https://journals.iupui.edu/index.php/iiclr/article/view/17883</text>
              </elementText>
              <elementText elementTextId="61967">
                <text>10.18060/17883</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="61968">
                <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="61969">
                <text>Indiana University Robert H. McKinney School of Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="61970">
                <text>https://journals.iupui.edu/index.php/iiclr/article/view/17883/17850</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="61971">
                <text>Indiana International &amp; Comparative Law Review; Vol. 23 No. 3 (2013); 371-428</text>
              </elementText>
              <elementText elementTextId="61972">
                <text>2169-3226</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="61973">
                <text>Citizen Judges in Japan: A Report Card for the Initial Three Years</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="61974">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="61975">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="604" public="1" featured="0">
    <collection collectionId="28">
      <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="11779">
                  <text>Journal of Open Access to Law</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="12877">
                  <text>Cornell University</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12115">
                <text>Curtotti, Michael</text>
              </elementText>
              <elementText elementTextId="12116">
                <text>Weibel, Wayne</text>
              </elementText>
              <elementText elementTextId="12117">
                <text>McCreath, Eric</text>
              </elementText>
              <elementText elementTextId="12118">
                <text>Ceynowa, Nicolas</text>
              </elementText>
              <elementText elementTextId="12119">
                <text>Frug, Sara</text>
              </elementText>
              <elementText elementTextId="12120">
                <text>Bruce, Tom R</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="12121">
                <text>2015-03-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12122">
                <text>This papers sits at the intersection of citizen access to law, legal informatics and plain language. The paper reports the results of a joint project of the Cornell University Legal Information Institute and the Australian National University which collected thousands of crowdsourced assessments of the readability of law through the Cornell LII site. The aim of the project is to enhance accuracy in the prediction of the readability of legal sentences. The study requested readers on legislative pages of the LII site to rate passages from the United States Code and the Code of Federal Regulations and other texts for readability and other characteristics. The research provides insight into who uses legal rules and how they do so. The study enables conclusions to be drawn as to the current readability of law and spread of readability among legal rules. The research is intended to enable the creation of a dataset of legal rules labelled by human judges as to readability. Such a dataset, in combination with machine learning, will assist in identifying factors in legal language which impede readability and access for citizens. As far as we are aware, this research is the largest ever study of readability and usability of legal language and the first research which has applied crowdsourcing to such an investigation. The research is an example of the possibilities open for enhancing access to law through engagement of end users in the online legal publishing environment for enhancement of legal accessibility and through collaboration between legal publishers and researchers.</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="12123">
                <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="12124">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/34</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12125">
                <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="12126">
                <text>Journal of Open Access to Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="12127">
                <text>https://ojs.law.cornell.edu/index.php/joal/article/view/34/54</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="12128">
                <text>Journal of Open Access to Law; Vol. 3 No. 1 (2015)</text>
              </elementText>
              <elementText elementTextId="12129">
                <text>2372-7152</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12130">
                <text>readability</text>
              </elementText>
              <elementText elementTextId="12131">
                <text>legislation</text>
              </elementText>
              <elementText elementTextId="12132">
                <text>legal informatics</text>
              </elementText>
              <elementText elementTextId="12133">
                <text>corpus linguistics</text>
              </elementText>
              <elementText elementTextId="12134">
                <text>machine learning</text>
              </elementText>
              <elementText elementTextId="12135">
                <text>natural language processing</text>
              </elementText>
              <elementText elementTextId="12136">
                <text>readability metrics</text>
              </elementText>
              <elementText elementTextId="12137">
                <text>cloze testing</text>
              </elementText>
              <elementText elementTextId="12138">
                <text>crowdsourcing</text>
              </elementText>
              <elementText elementTextId="12139">
                <text>citizen science</text>
              </elementText>
              <elementText elementTextId="12140">
                <text>artificial intelligence</text>
              </elementText>
              <elementText elementTextId="12141">
                <text>natural language processing</text>
              </elementText>
              <elementText elementTextId="12142">
                <text>legal informatics</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12143">
                <text>Citizen Science for Citizen Access to Law</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="12144">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="12145">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="12146">
                <text>Peer-reviewed article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2776" public="1" featured="0">
    <collection collectionId="41">
      <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="57791">
                  <text>Canadian Journal of European and Russian Studies</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="58877">
                <text>Jacob, Maria</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="58878">
                <text>2017-05-20</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58879">
                <text>After 2000, a profound liberalization of naturalization criteria in Germany was followed by culturalist setbacks: language requirements were tightened, a civics test, a pledge of allegiance, and citizenship ceremonies were introduced. Can these developments be termed a liberal assimilationist turn in what it means to be a citizen or is this a revival of the old notion of a German cultural identity as Kulturnation (cultural nation)? The qualitative study of German citizenship ceremonies presented herein, provides an in-depth analysis of the logics of “liberal assimilation” and the nexus between culture, citizenship, and national belonging. At the ceremonies, “culture” is referenced as a universally human feature that binds people together. Conversely, culture is also presented as an individual folkloristic asset that can be used for profit and for contributing to the value of diversity. This twofold conceptual specification of “culture” is then discussed as an adaptation of the originally universalist Kulturnation idea and as a modern solution to the problem of societal integration.
Full text available at: https://doi.org/10.22215/rera.v11i1.256</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="58880">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/2501</text>
              </elementText>
              <elementText elementTextId="58881">
                <text>10.22215/cjers.v11i1.2501</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="58882">
                <text>Centre for European Studies, Carleton University</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="58883">
                <text>Canadian Journal of European and Russian Studies; 2017: RERA V11:1 Transatlantic Perspectives on Citizenship and Diversity: Changing Trends (backfile abstracts)</text>
              </elementText>
              <elementText elementTextId="58884">
                <text>2562-8429</text>
              </elementText>
              <elementText elementTextId="58885">
                <text>10.22215/cjers.v11i1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58886">
                <text>Citizenship Ceremonies in Germany: A More Universalist Kulturnation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58887">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="58888">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="58889">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2710" public="1" featured="0">
    <collection collectionId="41">
      <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="57791">
                  <text>Canadian Journal of European and Russian Studies</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="58006">
                <text>Auvachez, Élise</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="58007">
                <text>2006-09-01</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58008">
                <text>Objet politique pas toujours identifié, mais souvent controversé, la citoyenneté européenne, près de 15 ans après son introduction dans le Traité de Maastricht, continue de susciter le débat : quelle citoyenneté pour quelle Europe ? Quelle autonomie pour une citoyenneté européenne dont l’acquisition reste soumise à des règles nationales ? Finalement, la citoyenneté européenne est-elle possible ? La présente communication propose de lire la problématique de la citoyenneté européenne à la lumière d’un prisme élargissant l’intégrant dans un questionnement dépassant le débat spécifiquement européen, celui de la gouvernance supranationale. Les dynamiques de globalisation et de fragmentation qui caractérisent le contexte contemporain se traduisent dans la sphère politique par la multiplication des paliers de régulation. La sphère nationale n’est plus dans cette perspective le seul locus de la vie politique ; les enjeux et les rapports de force politiques se jouent à des échelles multiples. Ce constat a donné naissance à une prolifération d’analyses concernant la dimension de plus en plus européenne, post/trans/supra-nationale, voire globale, de la citoyenneté. Celles-ci constituent néanmoins un corpus théorique un corpus théorique marqué par une compréhension à la fois fractionnée et diluée de la notion de citoyenneté supranationale et caractérisé par une perspective statique conférant au débat entre les partisans d’une citoyenneté au-delà de l’État et les avocats d’une citoyenneté par essence nationale une circularité stérile. La démarche théorique proposée consiste alors moins à tenter de caractériser les changements contemporains à la lumière des critères de la citoyenneté dans une perspective dichotomique pour savoir si « la » citoyenneté est nationale ou postnationale mais plutôt à comprendre la « citoyennisation », la construction et la définition d’une citoyenneté au-delà de l’État-nation, en relation avec la constitution et la consolidation d’entités politiques supranationales.
&amp;nbsp;
Full text available: https://doi.org/10.22215/rera.v2i3.173</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="58009">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/2420</text>
              </elementText>
              <elementText elementTextId="58010">
                <text>10.22215/cjers.v2i3.2420</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="58011">
                <text>Centre for European Studies, Carleton University</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="58012">
                <text>Canadian Journal of European and Russian Studies; 2006: RERA V2:3 What kind of Europe: Multiculturalism, Migration and Political Community – Lessons from Canada (backfile abstracts)</text>
              </elementText>
              <elementText elementTextId="58013">
                <text>2562-8429</text>
              </elementText>
              <elementText elementTextId="58014">
                <text>10.22215/cjers.v2i3</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58015">
                <text>Citoyenneté européenne, transnationale ou globale : penser la citoyenneté au-delà de l’État. Analyse critique d’un débat</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58016">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="58017">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="58018">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="3074" public="1" featured="0">
    <collection collectionId="43">
      <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="63031">
                  <text>University of South Australia Law Review</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63046">
                <text>Spyrou, Peta</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="63047">
                <text>2015-11-23</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63048">
                <text>Cyberbullying is a form of covert bullying that affects the lives of young people and adults alike. Empirical evidence suggesting that the effects of cyberbullying may lead to protracted mental harm highlights the need for schools to take a proactive stance against this form of bullying. This article looks specifically at the effectiveness of the anti-bullying policies implemented by South Australian school authorities in order to comply with their legal duty of care in negligence. Part I introduces the topic of cyberbullying, while Part II explains a school’s legal liability for instances of cyberbullying and identifies the requisite need for anti-bullying polices. In addition, Part III highlights the need for a multifaceted approach to reduce the occurrence of cyberbullying that recognises the important roles played by parents and student bystanders. This section concludes by providing specific recommendations on how anti-bullying policies should be implemented. The article argues that while school authorities may bear legal liability for instances of cyberbullying, schools cannot effectively implement anti-bullying policies without forming a partnership with the whole school community.</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="63049">
                <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="63050">
                <text>https://ojs.unisa.edu.au/index.php/uslr/article/view/1246</text>
              </elementText>
              <elementText elementTextId="63051">
                <text>10.21913/USLRunisaslr.v1i0.1246</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63052">
                <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="63053">
                <text>University of South Australia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="63054">
                <text>https://ojs.unisa.edu.au/index.php/uslr/article/view/1246/806</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="63055">
                <text>University of South Australia Law Review; Vol. 1 (2015): UniSA Student Law Review</text>
              </elementText>
              <elementText elementTextId="63056">
                <text>2206-1398</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63057">
                <text>CIVIL LIABILITY FOR NEGLIGENCE:  AN ANALYSIS OF CYBERBULLYING POLICIES IN SOUTH AUSTRALIAN SCHOOLS</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="63058">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="63059">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="2760" public="1" featured="0">
    <collection collectionId="41">
      <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="57791">
                  <text>Canadian Journal of European and Russian Studies</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="58663">
                <text>Inkina, Svetlana</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="58664">
                <text>2013-10-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58665">
                <text>Public administrative and civil service reforms have widely been used as a popular strategy to bring about systemic changes in entrenched bureaucracies. The general tendency that occurred in Post-Communist states was to adopt comprehensive policy measures dealing with the efficiency and effectiveness of state apparatus. This paper examines the process of an attempted civil service reform in Russia starting from the first term of Putin's Presidency. Based upon interviews with experts and senior public officials, it elaborates on the role of leadership, or the willingness of the national political elite to improve the system of public administration; the impact of path-dependency upon the course of institutional transformation; and finally, the role of reform strategy in the policy implementation process. The article concludes that the case of civil service reform in Russia may be explained by a combination of policy-making variables listed above. In addition, it highlights the transformation of the Russian policy-making system during the years of political centralization.
Full text available at: https://doi.org/10.22215/rera.v8i1.222
&amp;nbsp;</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="58666">
                <text>https://ojs.library.carleton.ca/index.php/CJERS/article/view/2481</text>
              </elementText>
              <elementText elementTextId="58667">
                <text>10.22215/cjers.v8i1.2481</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="45">
            <name>Publisher</name>
            <description>An entity responsible for making the resource available</description>
            <elementTextContainer>
              <elementText elementTextId="58668">
                <text>Centre for European Studies, Carleton University</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="58669">
                <text>Canadian Journal of European and Russian Studies; 2013: RERA V8:1 Fall 2013 (backfile abstracts)</text>
              </elementText>
              <elementText elementTextId="58670">
                <text>2562-8429</text>
              </elementText>
              <elementText elementTextId="58671">
                <text>10.22215/cjers.v8i1</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58672">
                <text>Civil Service Reform in Transition: A Case Study of Russia</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="58673">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="58674">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="58675">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="64" public="1" featured="0">
    <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="7">
                  <text>CLAWS Journal</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="45">
              <name>Publisher</name>
              <description>An entity responsible for making the resource available</description>
              <elementTextContainer>
                <elementText elementTextId="1982">
                  <text>Centre for Land Warfare Studies, New Delhi, India</text>
                </elementText>
              </elementTextContainer>
            </element>
            <element elementId="44">
              <name>Language</name>
              <description>A language of the resource</description>
              <elementTextContainer>
                <elementText elementTextId="1983">
                  <text>English</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1186">
                <text>Chakravorty, P.K.</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="1187">
                <text>2018-12-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1188">
                <text>India is a vibrant plural democracy. The Indian armed forces were inherited from the British on attaining independence. The Indian soldier who forms a part of the three Services has been involved in combat right from the formation of the nation, The Indian soldier has always followed the motto stated by Field Marshal Philip Chetwode which states that the honour, safety, and welfare of the country comes first always, and every time, the honour, safety, and welfare of the men you command comes next; and your own comforts come last, always and every time.1 Whatever be the situation, the soldiers of the three Services have placed service before self and served the nation, its elected representatives, and the nation with humility, courage, and fortitude. The soldiers have always risen to the occasion and enabled the nation to grow as the world's biggest and most vibrant democracy. At the current juncture, the Indian armed forces are professional and can execute operations with the military profession.</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="1189">
                <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="1190">
                <text>https://ojs.indrastra.com/index.php/clawsjournal/article/view/109</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1191">
                <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="1192">
                <text>Centre For Land Warfare Studies (CLAWS), New Delhi, India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="1193">
                <text>https://ojs.indrastra.com/index.php/clawsjournal/article/view/109/115</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1194">
                <text>Copyright (c) 2018  Centre For Land Warfare Studies (CLAWS), New Delhi, India</text>
              </elementText>
              <elementText elementTextId="1195">
                <text>https://ojs.indrastra.com/index.php/clawsjournal/copyright-transfer-form</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="1196">
                <text>CLAWS Journal; Vol. 11 No. 2 (2018): Winter 2018; 34-45</text>
              </elementText>
              <elementText elementTextId="1197">
                <text>2319-5177</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1198">
                <text>Civil-Military</text>
              </elementText>
              <elementText elementTextId="1199">
                <text>Relations</text>
              </elementText>
              <elementText elementTextId="1200">
                <text>Civil-Military Relations</text>
              </elementText>
              <elementText elementTextId="1201">
                <text>India</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1202">
                <text>Civil-Military Relations in the Present Context</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1203">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="1204">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="1205">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1127" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22431">
                <text>Ghnemat, Rawan</text>
              </elementText>
              <elementText elementTextId="22432">
                <text>Jaser, Edward</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="22433">
                <text>2015-09-25</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22434">
                <text>Mobile usage is witnessing a booming growth attributed to advances in smartphone technologies, the extremely high penetration rate and the availability of popular mobile applications. Telecommunication markets have been injecting huge investments to fulfil the sheer demand on wireless network and mobile services as a result. Such potentials highlights the importance of behavioral segmentation of mobile network users to target different sectors of customers with efficient marketing strategies and ensure customer retention in light of the intense competition. A major hurdle in applying this approach is the number of dimensions underlying customer preferences which makes it hard to visualize similarities among customers and formulate behavioral segments correctly and efficiently. In this paper, we use self-organizing maps, to detect different usage patterns of mobile users. The proposed system is tested using a large sample of customers’ data provided by major mobile operator in Jordan. The study detected different behavioural segments in this market and highlights the role of data users in modern mobile markets. In this context, we give detailed analysis of our results on user behavioral segmentation.</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="22435">
                <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="22436">
                <text>https://online-journals.org/index.php/i-jim/article/view/4392</text>
              </elementText>
              <elementText elementTextId="22437">
                <text>10.3991/ijim.v9i4.4392</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22438">
                <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="22439">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="22440">
                <text>https://online-journals.org/index.php/i-jim/article/view/4392/3606</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22441">
                <text>Copyright (c) 2017 Rawan Ghnemat, Edward Jaser</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="22442">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 9 No. 4 (2015); pp. 4-11</text>
              </elementText>
              <elementText elementTextId="22443">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22444">
                <text>Mobile telecommunications</text>
              </elementText>
              <elementText elementTextId="22445">
                <text>Self-Organizing Map</text>
              </elementText>
              <elementText elementTextId="22446">
                <text>Customer segmentation</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22447">
                <text>Classification of Mobile Customers Behavior and Usage Patterns using Self-Organizing Neural Networks</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="22448">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="22449">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="22450">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1072" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21265">
                <text>Vetterick, Jonas</text>
              </elementText>
              <elementText elementTextId="21266">
                <text>Garbe, Martin</text>
              </elementText>
              <elementText elementTextId="21267">
                <text>Dähn, Andreas</text>
              </elementText>
              <elementText elementTextId="21268">
                <text>Cap, Clemens H.</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="21269">
                <text>2014-01-05</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21270">
                <text>Classroom Response Systems (CRS) provide lecturers a communication channel to get feedback from their students. In lessons with large audiences, CRS allow students to ask questions or state issues as the lesson continues. During the development and usage of our new CRS "Tweedback", we observed several technical and non-technical problems, which are likely to be general CRS issues. Observed problems are caused by necessary devices, their connectivity and lecturersâ?? and studentsâ?? different ways to use CRS. In this paper, we describe our observations of technical and nontechnical problems and suggest solutions, which may be applied generically to interactive feedback systems.</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="21271">
                <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="21272">
                <text>https://online-journals.org/index.php/i-jim/article/view/3454</text>
              </elementText>
              <elementText elementTextId="21273">
                <text>10.3991/ijim.v8i1.3454</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21274">
                <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="21275">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="21276">
                <text>https://online-journals.org/index.php/i-jim/article/view/3454/2937</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21277">
                <text>Copyright (c) 2017 Jonas Vetterick, Martin Garbe, Andreas Dähn, Clemens H. Cap</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="21278">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 8 No. 1 (2014); pp. 21-25</text>
              </elementText>
              <elementText elementTextId="21279">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21280">
                <text>Classroom Response Systems</text>
              </elementText>
              <elementText elementTextId="21281">
                <text>Audience Response Systems</text>
              </elementText>
              <elementText elementTextId="21282">
                <text>Live Feedback</text>
              </elementText>
              <elementText elementTextId="21283">
                <text>Large Audiences</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21284">
                <text>Classroom Response Systems in the Wild: Technical and Non-Technical Observations</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="21285">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="21286">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="21287">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
  <item itemId="1722" public="1" featured="0">
    <collection collectionId="36">
      <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="15984">
                  <text>International Journal of Interactive Mobile Technologies (iJIM)</text>
                </elementText>
              </elementTextContainer>
            </element>
          </elementContainer>
        </elementSet>
      </elementSetContainer>
    </collection>
    <itemType itemTypeId="14">
      <name>Dataset</name>
      <description>Data encoded in a defined structure. Examples include lists, tables, and databases. A dataset may be useful for direct machine processing.</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="39">
            <name>Creator</name>
            <description>An entity primarily responsible for making the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35880">
                <text>D, Uma Nandhini</text>
              </elementText>
              <elementText elementTextId="35881">
                <text>S, Udhayakumar</text>
              </elementText>
              <elementText elementTextId="35882">
                <text>Tamilselvan, Latha</text>
              </elementText>
              <elementText elementTextId="35883">
                <text>J, Silviya Nancy</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="35884">
                <text>2020-07-31</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35885">
                <text>Computing with mobile is still in its infancy due to its limitations of computational power, battery lifetime and storage capacity. These limitations hinder the growth of mobile computing, which in-turn affects the growth of computationally intensive applications developed for the mobile devices. So in-order to help execute complex applications within the mobile device, mobile cloud computing (MCC) emerged as a feasible solution. The job of offloading the task to the cloud data center for storage and execution from the mobile seems to gain popularity, however, issues related to network bandwidth, loss of mobile data connectivity, and connection setup does not augment well to extend the benefits offered by MCC. Cloudlet servers filled this gab by assisting the mobile cloud environment as an edge device, offering compute power to the connected devices with high speed wireless LAN connectivity. Implementation constraints of cloudlet faces severe challenges in-terms of its storage, network sharing, and VM provisioning. Moreover, the number of connected devices of the cloudlet and its load conditions vary drastically leading to unexpected bottleneck, in which case the availability to server becomes an issue. Therefore, a scalable cloudlet, Client Aware Scalable Cloudlet (CASC) is proposed with linear regression analysis, predicting the knowledge of expected load conditions for provisioning new virtual machines and to perform resource migration.</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="35886">
                <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="35887">
                <text>https://online-journals.org/index.php/i-jim/article/view/14407</text>
              </elementText>
              <elementText elementTextId="35888">
                <text>10.3991/ijim.v14i12.14407</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="44">
            <name>Language</name>
            <description>A language of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35889">
                <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="35890">
                <text>International Association of Online Engineering (IAOE), Vienna, Austria</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="46">
            <name>Relation</name>
            <description>A related resource</description>
            <elementTextContainer>
              <elementText elementTextId="35891">
                <text>https://online-journals.org/index.php/i-jim/article/view/14407/7587</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="47">
            <name>Rights</name>
            <description>Information about rights held in and over the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35892">
                <text>Copyright (c) 2020 Udhayakumar S</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="35893">
                <text>International Journal of Interactive Mobile Technologies (iJIM); Vol. 14 No. 12 (2020); pp. 165-178</text>
              </elementText>
              <elementText elementTextId="35894">
                <text>1865-7923</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="49">
            <name>Subject</name>
            <description>The topic of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35895">
                <text>client aware resource scalability cloudlet</text>
              </elementText>
              <elementText elementTextId="35896">
                <text>mobile cloud computing</text>
              </elementText>
              <elementText elementTextId="35897">
                <text>resource migration</text>
              </elementText>
              <elementText elementTextId="35898">
                <text>scalable cloudlet.</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35899">
                <text>Client Aware Scalable Cloudlet to Augment Edge Computing with Mobile Cloud Migration Service</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="51">
            <name>Type</name>
            <description>The nature or genre of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="35900">
                <text>info:eu-repo/semantics/article</text>
              </elementText>
              <elementText elementTextId="35901">
                <text>info:eu-repo/semantics/publishedVersion</text>
              </elementText>
              <elementText elementTextId="35902">
                <text>Peer-reviewed Article</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </item>
</itemContainer>
