<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Automated Metareviewing: A Classifier Approach to Assess the Quality of Reviews</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Ravi K. Yadav</string-name>
          <email>rkyadav@ncsu.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Edward F. Gehringer</string-name>
          <email>efg@ncsu.edu</email>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science Department, North Carolina State University</institution>
          ,
          <addr-line>Raleigh, NC</addr-line>
          ,
          <country country="US">USA</country>
        </aff>
      </contrib-group>
      <abstract>
        <p>A review's quality can be evaluated through metric-based automated metareview. But not all the metrics should be weighted the same when it comes to evaluating the overall quality of reviews. For instance, if a review identifies specific problems about the reviewed artifact, then even with a low score for other metrics it should be evaluated as a helpful review. To evaluate the usefulness of a review, we propose a use of decision-tree based classifier models computed from the raw score of metareview metrics, instead of using all the metrics, we can use a subset of them.</p>
      </abstract>
      <kwd-group>
        <kwd>Automated metareview</kwd>
        <kwd>Decision tree classifier Peer-review systems</kwd>
        <kwd>Education artifacts</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>1. Introduction</title>
      <p>
        MOOC-based education platforms as well as face-to-face
classrooms are increasingly adopting peer assessment. Peer
reviewing increases students’ participation and fosters
collaborative learning. Students are encouraged to review their
peers’ work and provide formative feedback. High-quality
feedback can help the reviewee improvise his/her work.
Reviewing (or evaluating) a review is known as metareviewing.
For best results, a review should be metareviewed before being
presented to the reviewee. Usually this is a manual task [
        <xref ref-type="bibr" rid="ref1">1, 2</xref>
        ] for
the teaching staff, which becomes more demanding when the
metareview is needed quickly. Automated metareviewing [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ] is a
technique of using a smart tool to evaluate the quality of a review
using certain textual properties of the submitted feedback. These
properties include tone, volume, content type, relevance,
coverage, and plagiarism. Content type is further divided into
problem identification, advisory, or summative evaluation of
reviewed work. These properties are the metrics used by
automated metareviewer to evaluate the usefulness of a review.
Though a good review may contain all of these properties, we
found that a good review need not contain all.
      </p>
    </sec>
    <sec id="sec-2">
      <title>2. Metrics to assess a review</title>
      <p>As mentioned above, a metareview evaluates a review based on
certain textual properties, otherwise known as metrics. Below
are the metrics used by our metareview evaluator.</p>
      <p>Review relevance: A relevant review should discuss the work
reviewed and try to identify problems/issues in author’s work.
Review content: This metric is further divided into three
metrics, such as: Summative, Problem Detection and Advisory.
Summative: A summative review provides either positive
feedback or a summary of the author’s work.</p>
      <p>Problem detection: A review can detect one or more specific
problems in the reviewed artifact.</p>
      <p>Advisory: A reviewer can provide specific advice to the author,
which can be used by the author to improve the artifact.
Coverage: Coverage is a measure of review’s ability to cover the
main points of the artifact.</p>
      <p>Tone: Tone refers to the semantic orientation of a text. Tone is
divided into three categories: positive, negative and neutral. A
single review can contain various measures of positive, negative
and neutral tone.</p>
      <p>Volume: Volume measures the quantity of textual feedback
provided by the reviewer.</p>
      <p>Plagiarism: This metric is based on the originality of a review.
If a review is copied, then it is marked as plagiarized. A review
is compared against artifact, rubrics used and the internet search
results based on the review text.</p>
    </sec>
    <sec id="sec-3">
      <title>3. Experiments</title>
      <p>
        Our automated metareview system is a Ruby on Rails-based
web service [
        <xref ref-type="bibr" rid="ref10">10</xref>
        ]. All the statistical calculations are performed
using packages available in R. The metareview web service
generates quantitative scores, but to determine the overall quality
of a review based on this score, we need a statistical model. This
model, once trained, can be used to classify a review as a good or
a bad one. To train this model, we performed an experiment in
the form of a survey. We selected a collection of student artifacts
from Expertiza [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ]. We used the reviews they received from the
other students in the class. These reviews were rated manually
by survey participants, explained in next section. The
questionnaire used to evaluate the reviews by survey participants
was based on metareview metrics. Table 1 lists all the questions
used in the questionnaire. Survey participants were asked to
answer the questions by selecting a response on the scale of 1–5,
where 1 is the lowest score and 5 as the highest. In this
experiment, we ignored the Plagiarism metric, hence no question
was asked related to this metric. The question on “Overall
quality” was used to generate the class identifier for each review.
      </p>
      <sec id="sec-3-1">
        <title>Experiment participants</title>
        <p>Participants were former and current TAs from different
departments of Engineering, Science and Business. We trained
them by explaining the essence of each metareview metric used
in automated metareviewing. Multiple participants were asked
to rate the same reviews to generate a holistic model. We created
an anonymous system to prevent the reviewers from knowing the
identity of the authors of the artifact and the reviews.</p>
        <p>The artifacts selected for this experiment were taken from
the articles created by Spring 2016 students in CSC 517 course
at NC State University. As a part of this course, students wrote
Wikipedia articles which were then given to other students in
class for reviewing. Each student was required to review two
articles. They were given an option to review two more articles
to receive extra points.</p>
        <p>Table 1: Questionnaire for the survey</p>
      </sec>
      <sec id="sec-3-2">
        <title>Question text</title>
        <sec id="sec-3-2-1">
          <title>How well does the review adequately reflect (summarize) the artifact?</title>
        </sec>
        <sec id="sec-3-2-2">
          <title>How well is the problem identified by the reviewer about the artifact?</title>
        </sec>
        <sec id="sec-3-2-3">
          <title>How specific is the advice provided by the</title>
          <p>reviewer to the author to improve the artifact?</p>
        </sec>
        <sec id="sec-3-2-4">
          <title>How relevant is the review to the artifact?</title>
        </sec>
        <sec id="sec-3-2-5">
          <title>Does the review cover all the parts of the artifact?</title>
        </sec>
        <sec id="sec-3-2-6">
          <title>What do you think about the tone used by</title>
          <p>reviewer? (1: strongly negative, 2: negative, 3:
neutral, 4: positive, 5: strongly positive</p>
        </sec>
        <sec id="sec-3-2-7">
          <title>How satisfied are you with the quantity of</title>
          <p>comments provided by reviewer?</p>
        </sec>
        <sec id="sec-3-2-8">
          <title>How would you rate the overall quality of the review?</title>
        </sec>
      </sec>
      <sec id="sec-3-3">
        <title>Associated</title>
        <p>metareview
metric
(scale of 1–
5)</p>
        <sec id="sec-3-3-1">
          <title>Summative</title>
        </sec>
        <sec id="sec-3-3-2">
          <title>Problem detection</title>
        </sec>
        <sec id="sec-3-3-3">
          <title>Advisory</title>
        </sec>
        <sec id="sec-3-3-4">
          <title>Relevance</title>
        </sec>
        <sec id="sec-3-3-5">
          <title>Coverage</title>
        </sec>
        <sec id="sec-3-3-6">
          <title>Tone</title>
        </sec>
        <sec id="sec-3-3-7">
          <title>Volume</title>
        </sec>
        <sec id="sec-3-3-8">
          <title>Overall quality</title>
        </sec>
      </sec>
    </sec>
    <sec id="sec-4">
      <title>4. Data model &amp; Results</title>
      <sec id="sec-4-1">
        <title>Preprocessing data</title>
        <p>A total of 119 reviews were surveyed in this experiment. Since
more than one survey participant reviewed the same artifact,
each review was assigned the average of the scores it received
from all the participants.</p>
        <p>All the questions were answered on a scale of 1–5, with 5 being
the “best” score. For the tone metric, we found that only two
surveys assigned a score of 1 (highly negative) to a review,
whereas about 60% reviews received a score of 4 (positive).
About 10% received a score of 5 (highly positive). We
normalized the survey score for tone and grouped them into three
categories. A score less than 3 (&lt;3) was translated to –1
(Negative), whereas 3 was translated to 0 (Neutral) and a score
greater than 3 (&gt;3) was converted to 1 (Positive). The survey
question associated with the overall quality of the review was
normalized as well. A score higher than 3 was translated to good
review (1), otherwise it was marked as bad review (0). We used
this metric as class identifier for our data modeling. This was
done to create a holistic model.</p>
        <p>Figure 1 shows the distribution of surveys scores for each metric
individually. We can see from this figure that not all the metrics
are dispersed equally, which correlates with the idea that each
metric is not equally important for evaluating the overall quality
of the review.</p>
        <p>Each review used in the survey was evaluated using the
automated metareviewer, which generated metareview score for
each review. The metareview web service evaluates each
sentence of a review and tries to identify positive or negative
words used in it from a collection of word list. If the count is
same, then it is marked as neutral. An aggregated score of all the
sentences is calculated for the review. So if a review contains
positive and negative sentences, then the overall score can have a
score for positive metric as well as negative metric. But for our
experiment, we scaled the overall tone score. If the overall
positive score for a review was higher than the negative score,
then it was translated to 1 (overall positive review). If overall
negative score was higher than positive score, then it was
translated to –1 (overall negative review), else it was converted
to 0 (overall neutral review).</p>
        <p>
          The survey participants had an absolute agreement (zero
tolerance) of 38.8% with inter-rater reliability, calculated using
weighted kappa [
          <xref ref-type="bibr" rid="ref5">5</xref>
          ], of 0.13. Inter-rater agreement increased to
80% when the tolerance was relaxed by one point (±1). For
reviews surveyed by more than one person, an average score was
used to represent the final score. For some of the metrics in
Figure 1, such as coverage, summative, and problem
identification, the distribution is concentrated toward the center
axis of graph. This explains the sudden increase of inter-rater
agreement when the tolerance is relaxed by 1 point. Other
metrics such as volume, relevance, and advisory shows a fair
distribution cross the rating scale.
        </p>
        <p>
          Sixty-five percent of reviews were rated as good whereas others
were marked as bad by the survey experts. Table 2 lists the
Pearson Correlation matrix between the score of the questions
based on metareview metrics to the overall quality of the review
as rated by survey participants. It can be easily inferred from
Table 2, that each metric is highly correlated with the overall
quality of the review, except tone. As per figure 1, volume and
advisory are two most dispersed metrics and they also show
greater correlation with the overall grade of a review, which
makes them two most important metrics for data modelling.
review as per surveys experts. This translates to similar results,
which we derived from Table 2. Based on the experiment and the
data collected from automated metareviewing, volume,
summative, and advisory are better suited metrics on which to
create a model to categorize the quality of a review. Other
metrics like tone, and problem identification should be used in
modeling as well. But metrics such as relevance, and coverage
are not performing well, so these metrics cannot be used for data
modeling.
While selecting the model that can be used to differentiate
between a good and a bad review, we investigated various
modeling methodologies. We wanted a model that is inexpensive
to construct, which can be retrained, and is extremely fast in
classifying unknown reviews. Also since, we are ignoring two
metrics in this modeling, we wanted a model that is flexible to
incorporate these variables at a later stage. One modeling
technique that looks ideal for these cases is a decision tree.
To create a decision tree, we started with Classification and
Regression Trees (CART) modeling using the rpart [
          <xref ref-type="bibr" rid="ref6">6</xref>
          ] library
in R. This library provides various ways to generate trees, such
as classification and regression. The classification method is
used in this experiment to generate the tree.
        </p>
        <p>To find an optimal tree, a first attempt was made with volume,
summative, advisory, problem identification and tone metrics.
The summary function in rpart library shows that volume is a
very important metric when generating the classification tree.
Table 5 shows the result of the summary function, which states
that the tone and problem identification were the least preferred
metrics for classification
From table 2, 3 and 4, Volume shows a stronger correlation with
the class identifier (overall quality). Figure 2 shows that the
volume metric alone can construct a classification tree to identify
review quality. This decision tree can be used to identify whether
the review is good or bad on the basis of the volume score
received from the automated metareview metric. For instance, if
the volume metric score is greater than 68, then it is a good
review, or if score is less than 26, that is a bad review. This is
not pruned at the moment. Another algorithm discussed later
generates a more pruned tree.</p>
        <p>Node 1 divided the sample space into two sets containing 42 and
77 observations respectively. A review with a score of 68.5 for
metareview metric volume is used as the first split criterion.
Each node number is marked in Figure 2, with split criteria and
class probabilities.</p>
        <p>
          Though volume can be a good classifier, volume alone should not
be used to identify the quality of a review. We found in another
study [
          <xref ref-type="bibr" rid="ref7">7</xref>
          ] that review volume may be related to the rubrics used
in review phase. Some rubrics can ask for more feedback from
reviewers than others. The volume metric can often be
misleading and can result in higher number of false positives. A
reviewer can provide gibberish comments which can result in a
good metareview score for volume. We should consider other
metrics as well to evaluate the overall quality of such a review.
This calls for another decision tree based on other metrics. Then,
we can use both of these decision trees to classify a review. If
any one tree classifies a review as a bad review, then that
information can be shown to the reviewer as a guidance. This
information can help the reviewer to correct issues with the
review.
According to the tree in Figure 3, if a review receives a score in
excess of 0.25 for advisory, then it is a good review, else we can
check the score it receives for summative metric. If a review
receives a score less than 0.25 for advisory and a review score in
excess of 0.25 on summative, it is classified as a good review,
else it is a bad review. As we can see that once the decision tree
is created, process of classification of a review becomes easy.
In order to validate the results received from the rpart library,
another method of tree construction was explored. One such
method is C5.0 [
          <xref ref-type="bibr" rid="ref8">8</xref>
          ], which is an extension to C4.5 [
          <xref ref-type="bibr" rid="ref9">9</xref>
          ]. C50 is the
package implemented in R, which is used to generate the tree
based on the automated metareview score. 10-fold validation was
used in decision tree construction. Figure 4 shows the final tree
which includes all the metrics. As was noticed earlier in the tree
constructed using the rpart classification method, the volume
metric dominates the tree, and root node partition is based on
volume “&gt; 68”. This tree is shorter than tree in figure 2, because
C5.0 uses tree pruning to create a shorter tree. Sometimes this
pruning in result in increased classification error rate. The
classification error rate for this tree is 22.7%. The majority class
probability for this classifier tree is 80.7%, which is higher when
compared to the baseline and the classification tree generated in
Figure 3. One more tree was constructed without the volume
metric, as is shown in Figure 5. The classification error rate for
the tree is 29.4% which is higher than the similar CART based
tree. The majority class probability using this tree comes to
87.4%, which is again higher compared to the baseline score and
the other classification tree generated in Figure 3. This shows
that the tree generated using rpart fits the data better than the
similar tree generated using C5.0. C5.0 seems to generate a more
pruned tree, which is smaller in size, but with an increased
classification error rate.
Table 6 compares the performance for majority class prediction
using different classification methods. Higher majority class
probability compared to baseline probability means more false
positives. C5.0 generates shorter trees compared to CART, at the
cost of reduced accuracy at times. We found that CART based
classification tree is better at classification than C5.0.
        </p>
        <sec id="sec-4-1-1">
          <title>Classification method</title>
        </sec>
        <sec id="sec-4-1-2">
          <title>Base line (based on experiments)</title>
        </sec>
        <sec id="sec-4-1-3">
          <title>CART (Metareview)</title>
        </sec>
        <sec id="sec-4-1-4">
          <title>CART (Metareview without volume)</title>
        </sec>
        <sec id="sec-4-1-5">
          <title>C5.0 (Metareview)</title>
        </sec>
        <sec id="sec-4-1-6">
          <title>C5.0 (Metareview without volume)</title>
          <p>Majority class
probability
64.7%
72%
88%
80.7%
87.4%</p>
        </sec>
      </sec>
    </sec>
    <sec id="sec-5">
      <title>5. Discussion and conclusions</title>
      <p>Metareviewing is an essential tool, which can improve the
quality of reviewing. A reviewer can write a good review if
timely feedback can be provided on the review before he/she
submits it to the author.</p>
      <p>As part of this work, we created a decision-tree data classifier
based on the score a review receives from the automated
metareviewer. Decision trees are fast and efficient classifiers for
peer review metrics. We found that certain metrics, such as
volume, dominate the decision trees. But reliance on the volume
metric alone can generate false positives. We also created a
decision tree excluding the volume metric. That decision tree
uses content advisory, content summative, tone and problem
detection metrics. We suggest the use of a hybrid model that
includes use of both the trees. Each review is rated on both trees
from Figure 2 and Figure 3. A good review should score well on
both.</p>
    </sec>
    <sec id="sec-6">
      <title>5.1 Future work</title>
      <p>We used Wikipedia artifacts and reviews written for them in this
experiment. To make the model more robust, more similar
experiments can be done to include artifacts from other
educational domains. We used supervised learning to create this
model. Natural language processing (NLP) is becoming more and
more efficient in determining the semantics of a text. The
relevance metric generator should be updated to make it more
robust, so that it can also be used in the classification decision
tree.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <given-names>K.</given-names>
            <surname>Cho</surname>
          </string-name>
          ,
          <article-title>"Machine classification of peer comments in physics,"</article-title>
          <source>in Educational Data Mining</source>
          ,
          <year>2008</year>
          , pp.
          <fpage>192</fpage>
          -
          <lpage>196</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          <string-name>
            <given-names>W.</given-names>
            <surname>Xiong</surname>
          </string-name>
          and
          <string-name>
            <given-names>D.</given-names>
            <surname>Litman</surname>
          </string-name>
          ,
          <article-title>"Empirical analysis of exploiting review helpfulness for extractive summarization of online reviews,"</article-title>
          <source>Proceedings of 6th International Conference on Educational Data Mining (EDM)</source>
          ,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <given-names>L.</given-names>
            <surname>Ramachandran</surname>
          </string-name>
          ,
          <article-title>"</article-title>
          <source>Automated Assessment of Reviews," in PhD Dissertation</source>
          at North Carolina State University, Raleigh,
          <year>2013</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <given-names>E. F.</given-names>
            <surname>Gehringer</surname>
          </string-name>
          ,
          <article-title>"Expertiza: Managing feedback in collaborative learning," in Monitoring and Assessment in Online Collaborative Environments: Emergent Computational Technologies for E-Learning Support</article-title>
          , IGI Global Press,
          <year>2010</year>
          , pp.
          <fpage>75</fpage>
          -
          <lpage>96</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <given-names>J.</given-names>
            <surname>Cohen</surname>
          </string-name>
          ,
          <article-title>"Weighted kappa: Nominal scale agreement with provision for scaled disagreement or partial credit,"</article-title>
          <source>in Psychological Bulletin</source>
          ,
          <year>1968</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          [6]
          <string-name>
            <given-names>T.</given-names>
            <surname>Therneau</surname>
          </string-name>
          ,
          <string-name>
            <given-names>B.</given-names>
            <surname>Atkinson</surname>
          </string-name>
          and
          <string-name>
            <given-names>B.</given-names>
            <surname>Ripley</surname>
          </string-name>
          ,
          <article-title>"rpart: Recursive Partitioning and Regression trees</article-title>
          ,
          <year>" 2015</year>
          . [Online]. Available: https://cran.rproject.org/web/packages/rpart/index.html.
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          [7]
          <string-name>
            <given-names>R. K.</given-names>
            <surname>Yadav</surname>
          </string-name>
          and
          <string-name>
            <given-names>E. F.</given-names>
            <surname>Gehringer</surname>
          </string-name>
          ,
          <article-title>"Metrics for Automated Review Classification: What Review Data Show," in Stateof-the-Art and Future Directions of Smart Learning</article-title>
          , Springer Singapore,
          <year>2016</year>
          , pp.
          <fpage>333</fpage>
          -
          <lpage>340</lpage>
          .
        </mixed-citation>
      </ref>
      <ref id="ref8">
        <mixed-citation>
          [8]
          <string-name>
            <given-names>M.</given-names>
            <surname>Kuhn</surname>
          </string-name>
          ,
          <string-name>
            <given-names>S.</given-names>
            <surname>Weston</surname>
          </string-name>
          ,
          <string-name>
            <given-names>N.</given-names>
            <surname>Coulter</surname>
          </string-name>
          and
          <string-name>
            <given-names>M.</given-names>
            <surname>Culp</surname>
          </string-name>
          ,
          <article-title>"C5.0 Decision Trees</article-title>
          and
          <string-name>
            <surname>Rule-Based</surname>
            <given-names>Models</given-names>
          </string-name>
          ,
          <source>" CRAN</source>
          ,
          <fpage>08</fpage>
          <lpage>03</lpage>
          2015. [Online]. Available: https://cran.rproject.org/web/packages/C50/C50.pdf.
        </mixed-citation>
      </ref>
      <ref id="ref9">
        <mixed-citation>
          [9]
          <string-name>
            <surname>Q. R</surname>
          </string-name>
          ,
          <year>C4</year>
          .
          <article-title>5: Programs for Machine Learning</article-title>
          ., Morgan Kaufmann Publishers,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref10">
        <mixed-citation>
          [10]
          <string-name>
            <surname>R. K</surname>
          </string-name>
          . Yadav “
          <article-title>Web Services for Automated Assessment of Reviews”</article-title>
          , in MS Thesis at North Carolina State University, Raleigh,
          <year>2016</year>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>