[PRE REVIEW]: LISC: A Python Package for Scientific Literature Collection and Analysis

[whedon]

Submitting author: @TomDonoghue (Thomas Donoghue)
Repository: https://github.com/lisc-tools/lisc
Version: v0.1.0
Editor: @danielskatz
Reviewers: @timClicks, @linuxscout

Author instructions

Thanks for submitting your paper to JOSS @TomDonoghue. Currently, there isn't an JOSS editor assigned to your paper.

@TomDonoghue 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]

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

For example, to regenerate the paper pdf after making changes in the paper's md or bib files, type:

@whedon generate pdf

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 😸

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]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[danielskatz]

👋 @TomDonoghue - thanks for this submission. I'm going to assign myself as editor, and while I'll be slower than normal to respond over the next 2 weeks, I think we'll be able to make progress.

For your part, please look at this list of potential reviewers and identify individuals who might be able to review your submission (please start at the bottom of the list). Also, please suggest individuals who are not on this list by mentioning their GitHub handles here. I also have some ideas for reviewers...

[danielskatz]

@whedon assign @danielskatz as editor

[whedon]

OK, the editor is @danielskatz

[danielskatz]

👋 @pgroth - would you be willing to review this submission for JOSS? (If you haven't done this before, which I think is the case, you might want to take a look at the JOSS review guidelines and specifically JOSS review criteria)

[TomDonoghue]

@whedon generate pdf

[whedon]

Attempting PDF compilation. Reticulating splines etc...

[whedon]

👉 Check article proof 📄 👈

[TomDonoghue]

Hey @danielskatz - thanks for editing this submission!

I re-generated the PDF to fix some bullet lists that I hadn't quite formatted right.

In terms of reviewers, from the list of JOSS reviewers, the most relevant listings seem to me to be:

• Petar Maric (https://bitbucket.org/petar/)
• @\bagheria
• @\adammichaelwood
• @\linuxscout
• @\timClicks
• @\crew102

These aren't people I know personally, just the ones on the list for Python, who seemed to have the most related topic interests.

[danielskatz]

Hi - I'm on vacation, so this will happen a little slower than normal (but still faster than a traditional journal), and thanks in advance for your patience

[danielskatz]

👋 @bagheria, @adammichaelwood, @linuxscout, @timClicks, @crew102 - Would a couple of you be willing to review this submission for JOSS?

[timClicks]

Sure :)

…

On Wed, 21 Aug 2019, 01:05 Daniel S. Katz ***@***.*** wrote: 👋 @bagheria <https://github.com/bagheria>, @adammichaelwood <https://github.com/adammichaelwood>, @linuxscout <https://github.com/linuxscout>, @timClicks <https://github.com/timClicks>, @crew102 <https://github.com/crew102> - Would a couple of you be willing to review this submission for JOSS? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1658?email_source=notifications&email_token=AAAGZ4OWZTVZVEWHOHJQ5VLQFPTZ7A5CNFSM4IMPKZFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4WGZZQ#issuecomment-523005158>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAAGZ4L3C5DSNPSVF3UH4ETQFPTZ7ANCNFSM4IMPKZFA> .

[danielskatz]

Thanks @timClicks - I'll add you, but we won't start the review until we get another reviewer as well.

[danielskatz]

@whedon assign @timClicks as reviewer

[whedon]

OK, the reviewer is @timClicks

[danielskatz]

👋 @dgarijo - would you be willing to review this submission for JOSS? (If you haven't done this before, which I think is the case, you might want to take a look at the JOSS review guidelines and specifically JOSS review criteria)

[dgarijo]

Hi @danielskatz,
unfortunately my review pipeline is full at the moment. Sorry.
Thanks for considering me!

[linuxscout]

Salam,
I can review it.

[danielskatz]

Thanks @linuxscout - I'll add you, and we'll get started in the review issue that will be created shortly

[danielskatz]

@whedon add @linuxscout as reviewer

[whedon]

OK, @linuxscout is now a reviewer

[danielskatz]

@whedon start review

[whedon]

OK, I've started the review over in #1674. Feel free to close this issue now!

[crew102]

Hi @danielskatz , I could review if you guys need/want another.

[danielskatz]

I think we're set with 2 reviewers, but thanks. If you want to anyhow, I can add you.

[crew102]

K, I'll sit this one out then.