Joss-reviews: [PRE REVIEW]: A News Verification Browser for the Detection of Clickbait, Satire, and Falsified News
Submitting author: @VictoriaRubin (Victoria Rubin)
Repository: https://github.com/litrl/litrl_code
Version: v0.12.0.0
Editor: @danielskatz
Reviewers: @lrasmus, @CBenghi
Author instructions
Thanks for submitting your paper to JOSS @VictoriaRubin. The JOSS editor (shown at the top of this issue) will work with you on this issue to find a reviewer for your submission before creating the main review issue.
@VictoriaRubin if you have any suggestions for potential reviewers then please mention them here in this thread. In addition, this list of people have already agreed to review for JOSS and may be suitable for this submission.
Editor instructions
The JOSS submission bot @whedon is here to help you find and assign reviewers and start the main review. To find out what @whedon can do for you type:
@whedon commands
whedon
All 74 comments
Hello human, I'm @whedon, a robot that can help you with some common editorial tasks.
For a list of things I can do to help you, just type:
@whedon commands
What happens now?
This submission is currently in a pre-review state which means we are waiting for an editor to be assigned and for them to find some reviewers for your submission. This may take anything between a few hours to a couple of weeks. Thanks for your patience :smile_cat:
You can help the editor by looking at this list of potential reviewers to identify individuals who might be able to review your submission (please start at the bottom of the list). Also, feel free to suggest individuals who are not on this list by mentioning their GitHub handles here.
whedon
on 13 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1127 with the following error:
Can't find any papers to compile :-(
whedon
on 13 Dec 2018
@whedon generate pdf
arfon
on 14 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1127 with the following error:
/app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:377:in parse': (tmp/1127/paper.md): mapping values are not allowed in this context at line 11 column 44 (Psych::SyntaxError)
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:377:inparse_stream'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:325:in parse'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:252:inload'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:473:in block in load_file'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:472:inopen'
from /app/vendor/ruby-2.4.4/lib/ruby/2.4.0/psych.rb:472:in load_file'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-443822f01563/lib/whedon.rb:68:ininitialize'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-443822f01563/lib/whedon/processor.rb:32:in new'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-443822f01563/lib/whedon/processor.rb:32:inset_paper'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-443822f01563/bin/whedon:52:in prepare'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.0/lib/thor/command.rb:27:inrun'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.0/lib/thor/invocation.rb:126:in invoke_command'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.0/lib/thor.rb:387:indispatch'
from /app/vendor/bundle/ruby/2.4.0/gems/thor-0.20.0/lib/thor/base.rb:466:in start'
from /app/vendor/bundle/ruby/2.4.0/bundler/gems/whedon-443822f01563/bin/whedon:113:inload'
from /app/vendor/bundle/ruby/2.4.0/bin/whedon:23:in
whedon
on 14 Dec 2018
@whedon generate pdf
brogly
on 20 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
PDF failed to compile for issue #1127 with the following error:
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
100 16 0 16 0 0 289 0 --:--:-- --:--:-- --:--:-- 290
Error reading bibliography ./paper.bib (line 115, column 9):
unexpected "l"
expecting space, ",", white space or "}"
Error running filter pandoc-citeproc:
Filter returned error status 1
Looks like we failed to compile the PDF
whedon
on 20 Dec 2018
@whedon generate pdf
brogly
on 20 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 20 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@jasonclark - would you be willing to edit this submission for JOSS?
arfon
on 21 Dec 2018
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
@whedon generate pdf
brogly
on 21 Dec 2018
Attempting PDF compilation. Reticulating splines etc...
👋 @jasonclark - ping... (re: editing request, see https://github.com/openjournals/joss-reviews/issues/1127#issuecomment-449369691)
danielskatz
on 28 Dec 2018
Hi, maybe ejolly, shivam11, or arokem could review if Jason is busy? Although I'm guessing he is just on vacation or AFK given the holidays. Thanks!
brogly
on 3 Jan 2019
@danielskatz - Hi Daniel, can I send the requests to the other potential reviewers? (only asking because I'm not sure if we need to wait or not)
brogly
on 13 Jan 2019
Hi @brogly - we need an editor before we can assign reviewers...
danielskatz
on 14 Jan 2019
@arfon @danielskatz @labarba @kyleniemeyer Request to Explain further procedures
Dear Editor-In-Chief, Associate and Associate Editors,
Could someone please explain to us how your peer-review process works?
My RA @brogly has been trying to get this simple 2 page manuscript into your peer-review pipeline for the past month, but in exactly a month nothing seems to have happened. Obviously the Holiday season is partly to blame, but there seems to be no clear path to what we are supposed to be doing next.
@danielskatz seems to imply that we need to find a editor. How do you exactly envision this? We've requested reviewers that we thought might be interested.
Is there a communication break down here? Or is our paper not conforming with any requirements to get someone to look at it please?
As much as we like the bot-enabled chat commands, I would very much appreciate some clarity from a human.
[email protected]
Dr. Victoria L. Rubin, Associate Professor, Faculty of Information & Media Studies (FIMS)
Director, Language & Information Technology Research Lab (LiT.RL)
FNB 4046, Western University, London, Ontario, Canada N6A 5B7
Tel: (519) 661-2111 x 88479, Fax: (519) 661-3506
VictoriaRubin
on 14 Jan 2019
I apologize on behalf on JOSS - this has been a problem on our side, not your side. The process is that a submission can request a specific editor, who then works with the author to find reviewers and carry out the review process. If a submission does not request an editor, we are supposed to assign one.
In this case, our process broke: the editor who we suggested has not responded, and to some extent, blaming the holiday break, we didn't follow-up. I will go ahead and assign myself as editor, and start the process.
danielskatz
on 14 Jan 2019
@whedon assign @danielskatz as editor
danielskatz
on 14 Jan 2019
OK, the editor is @danielskatz
whedon
on 14 Jan 2019
👋 @ejolly, @shivam11 - would one (or ideally both) of you be willing to review this for JOSS?
danielskatz
on 14 Jan 2019
@brogly & @VictoriaRubin - can you suggest any other potential reviewers from the wider community?
danielskatz
on 14 Jan 2019
@danielskatz - Thanks for clarifying. Re outside reviewers: perhaps, Martin Potthast, who ran the CLickbait Challenge (https://webis.de/data/webis-clickbait-17.html)? Or anyone from his team or the other dataset group?
@brogly Chris, please stay on this, to make sure no further glitches occur. You had Martin Potthast's e-mail somewhere when we asked for permissions to use his set, right? Just in case @danielskatz asks for it Thanks again to both of you!
See 2 references below from our GitHub:
[CLICKBAIT DATASET 1] Abhijnan Chakraborty, Bhargavi Paranjape, Sourya Kakarla, and Niloy Ganguly. "Stop Clickbait: Detecting and Preventing Clickbaits in Online News Media”. In Proceedings of the 2016 IEEE/ACM International Conference on Advances in Social Networks Analysis and Mining (ASONAM), San Fransisco, US, August 2016. (URL: https://github.com/bhargaviparanjape/clickbait)
[CLICKBAIT DATASET 2] Martin Potthast, Tim Gollub, Kristof Komlossy, Sebastian Schuster, Matti Wiegmann, Erika Patricia Garces Fernandez, Matthias Hagen, and Benno Stein. Crowdsourcing a Large Corpus of Clickbait on Twitter. In Proceedings of the 27th International Conference on Computational Linguistics (COLING 2018), pages 1498–1507, August 2018. The COLING 2018 Organizing Committee.
VictoriaRubin
on 14 Jan 2019
👋 @potthast - would you be willing to review this submission for JOSS? Or perhaps you can suggest someone from your group/team? (See the JOSS review guidelines in case you are not familiar with how JOSS works)
danielskatz
on 14 Jan 2019
👋 @ejolly, @shivam11 - would one (or ideally both) of you be willing to review this for JOSS?
Unfortunately, I don't have easy access to a Windows computer (OSX and Linux only), so I'm not sure I'll be able to review this submission. Looks really interesting though!
ejolly
on 14 Jan 2019
👋 @lrasmus - you said in email you are willing to review this - please confirm here.
danielskatz
on 14 Jan 2019
👋 @lrasmus - you said in email you are willing to review this - please confirm here.
I am willing and happy to review. Thank you!
lrasmus
on 14 Jan 2019
Thanks - I want to get one more reviewer, then we will start the review
danielskatz
on 14 Jan 2019
@whedon assign @lrasmus as reviewer
but note that we are not starting the review yet...
danielskatz
on 14 Jan 2019
OK, the reviewer is @lrasmus
whedon
on 14 Jan 2019
@danielskatz Thanks for clearing everything up. I don't think I e-mailed @VictoriaRubin about this so I guess she was wondering too...
@danielskatz - from the list of reviewers, perhaps @cbenghi, @xirdneh, @nmullins, @dredamonsta1 ? From the broader community, @potthast, or anyone from the Webis group might be interested @bmst, @johanneskiesel, @kleinfreund, @phoerious
brogly
on 15 Jan 2019
👋 @CBenghi, @xirdneh, @nmullins, @dredamonsta1 - would one of you be interested in being the second reviewer for this submission on JOSS?
danielskatz
on 15 Jan 2019
👋 @bmst, @johanneskiesel, @kleinfreund, @phoerious - would one you be willing to review this submission for JOSS? Or perhaps you can suggest someone from your group/team? (See the JOSS review guidelines in case you are not familiar with how JOSS works)
danielskatz
on 15 Jan 2019
Thanks for the invitation.
Apart from me, only @bmst has been doing research on clickbait detection lately. Unfortunately, at present, we are both overwhelmed with other commitments, so that we will have to pass.
Sorry for the inconvenience!
potthast
on 15 Jan 2019
👋 @felixhenninger or @jaynanavati - would you be willing to review this for JOSS?
danielskatz
on 17 Jan 2019
👋 @theBrianCui or @rahulkapoor90 - would one of you be willing to review this for JOSS? (See the JOSS review guidelines in case you are not familiar with how JOSS works)
danielskatz
on 18 Jan 2019
👋 Hi - what is this? I've never heard of JOSS before. How can I help?
theBrianCui
on 21 Jan 2019
@lrasmus - Thanks for agreeing to review.
@theBrianCui - We are looking for a second reviewer for the Litrl Browser software and associated paper for submission to JOSS. Links to these are above and @danielskatz (Editor) posted review guidelines right above your reply if you are interested.
@danielskatz - The following reviewers may also be interested, chkoar, sirsharpest, rljacobson, lindemann09, adammichaelwood (omitting the @ as I'm not sure how many people I'm supposed to ask all at once...)
brogly
on 21 Jan 2019
Hi @theBrianCui - sorry for my delay in responding. JOSS is an open journal for short articles that also contain open source research software. Review is of both the article and the software. Once a submission is reviewed successfully (which means the reviewers point out problems and the authors fix them), the submission is published and the authors can then use this publication for academic credit (by asking users to cite the publication). Here are the review guidelines. The journal home page is http://joss.theoj.org and there's an about "tab" at the top, too.
Are you willing to review this submission? (this issue overall, and this article draft in particular)?
danielskatz
on 22 Jan 2019
@chkoar, @sirsharpest, @rljacobson, @lindemann09, @adammichaelwood would you be interested in reviewing this submission? We are looking for a second reviewer.
brogly
on 24 Jan 2019
@danielskatz, @brogly,
apologies for the delay, I have only just noticed the thread, as I have had to ignore github for a while.
I'm happy to help with the review if still needed.
CBenghi
on 27 Jan 2019
Yes, thanks very much @CBenghi - I'll go ahead and start the review now with you as one of the reviewers.
danielskatz
on 27 Jan 2019
@whedon add @CBenghi as reviewer
danielskatz
on 27 Jan 2019
OK, @CBenghi is now a reviewer
whedon
on 27 Jan 2019
@whedon start review
danielskatz
on 27 Jan 2019
OK, I've started the review over in https://github.com/openjournals/joss-reviews/issues/1208. Feel free to close this issue now!
whedon
on 27 Jan 2019
Related issues
whedon
·
12Comments
whedon
·
12Comments
whedon
·
9Comments
whedon
·
10Comments
whedon
·
12Comments
Most helpful comment
Thanks for the invitation.
Apart from me, only @bmst has been doing research on clickbait detection lately. Unfortunately, at present, we are both overwhelmed with other commitments, so that we will have to pass.
Sorry for the inconvenience!