[PRE REVIEW]: responder test

[med-oc]

Submitting author: !--author-handle-->@max-anu<!--end-author-handle-- (Max Proft) Repository: https://github.com/max-anu/example-medportal1 Branch with paper.md (empty if default branch): Version: v1 Editor: !--editor-->@max-anu<!--end-editor-- Reviewers: !--reviewers-list-->@max-anu<!--end-reviewers-list-- Managing EiC: Max Proft

Status

Status badge code:

HTML: <a href="https://medportal-dev-6a745f452687.herokuapp.com/papers/696010b623ad0751d58e31d512ad5ff8"><img src="https://medportal-dev-6a745f452687.herokuapp.com/papers/696010b623ad0751d58e31d512ad5ff8/status.svg"></a>
Markdown: [![status](https://medportal-dev-6a745f452687.herokuapp.com/papers/696010b623ad0751d58e31d512ad5ff8/status.svg)](https://medportal-dev-6a745f452687.herokuapp.com/papers/696010b623ad0751d58e31d512ad5ff8)

Author instructions

Thanks for submitting your recipe to medportal @max-anu. Currently, there isn't a medportal editor assigned to your recipe.

The AEiC suggestion for the handling editor is @max-anu.

@max-anu if you have any suggestions for potential reviewers then please mention them here in this thread (without tagging them with an @). You can search the list of people that have already agreed to review and may be suitable for this submission.

Editor instructions

The medportal submission bot @med-oc is here to help you find and assign reviewers and start the main review. To find out what @med-oc can do for you type:

@med-oc commands

Review checklist for @max-anu

Review checklist for @max-anu

Conflict of interest

• [ ] I confirm that I have read the JOSS conflict of interest (COI) policy and that: I have no COIs with reviewing this work or that any perceived COIs have been waived by JOSS for the purpose of this review.

Code of Conduct

• [ ] I confirm that I read and will adhere to the JOSS code of conduct.

General checks

• [ ] Repository: Is the source code for this software available at the https://github.com/max-anu/example-medportal1?
• [x] License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• [x] Contribution and authorship: Has the submitting author (@max-anu) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?
• [ ] Substantial scholarly effort: Does this submission meet the scope eligibility described in the JOSS guidelines
• [ ] Data sharing: If the paper contains original data, data are accessible to the reviewers. If the paper contains no original data, please check this item.
• [ ] Reproducibility: If the paper contains original results, results are entirely reproducible by reviewers. If the paper contains no original results, please check this item.
• [ ] Human and animal research: If the paper contains original data research on humans subjects or animals, does it comply with JOSS's human participants research policy and/or animal research policy? If the paper contains no such data, please check this item.

Functionality

• [ ] Installation: Does installation proceed as outlined in the documentation?
• [ ] Functionality: Have the functional claims of the software been confirmed?
• [ ] Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)

Documentation

• [ ] A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• [ ] Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
• [ ] Example usage: Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).
• [ ] Functionality documentation: Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?
• [ ] Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?
• [ ] Community guidelines: Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support

Software paper

• [ ] Summary: Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?
• [ ] A statement of need: Does the paper have a section titled 'Statement of need' that clearly states what problems the software is designed to solve, who the target audience is, and its relation to other work?
• [ ] State of the field: Do the authors describe how this software compares to other commonly-used packages?
• [ ] Quality of writing: Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?
• [ ] References: Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper citation syntax?

[med-oc]

Hello humans, I'm @med-oc, a robot that can help you with some common editorial tasks.

For a list of things I can do to help you, just type:

@med-oc help

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

@med-oc generate pdf

[max-anu]

@med-oc add assignee: @max-anu

[med-oc]

@max-anu added as assignee.

[max-anu]

@med-oc remove assignee: @max-anu

[med-oc]

@max-anu removed from assignees.

[max-anu]

@med-oc add assignee: @max-anu

[med-oc]

@max-anu added as assignee.

[max-anu]

@med-oc add checklist for @max-anu

[med-oc]

Checklist added for @max-anu

[max-anu]

@med-oc add checklist for @max-anu

[med-oc]

There is already a checklist for @max-anu

[max-anu]

@med-oc remove checklist for @max-anu

[med-oc]

Checklist for @max-anu removed

[max-anu]

@med-oc add checklist for @max-anu

[med-oc]

Checklist added for @max-anu

[max-anu]

@med-oc assign me as editor

[max-anu]

@med-oc assign @max-anu as editor

[med-oc]

Assigned! @max-anu is now the editor

[max-anu]

@med-oc code of conduct

[med-oc]

Our CoC: https://github.com/openjournals/joss/blob/master/CODE_OF_CONDUCT.md

[med-oc]

It's adapted from the Contributor Covenant: http://contributor-covenant.org

[med-oc]

Reports of abusive or harassing behavior may be reported to reports@theoj.org

[max-anu]

@med-oc check references

[med-oc]

I'm sorry human, I don't understand that. You can see what commands I support by typing:

@med-oc help

[max-anu]

@med-oc start review

[med-oc]

Can't start a review without reviewers

[max-anu]

@med-oc add @max-anu as reviewer

[med-oc]

@max-anu added to the reviewers list!

[max-anu]

@med-oc remove @max-anu from reviewers

[med-oc]

@max-anu removed from the reviewers list!

[max-anu]

@med-oc add @max-anu as reviewer

[med-oc]

@max-anu added to the reviewers list!

[max-anu]

@med-oc start review

[med-oc]

OK, I've started the review over in https://github.com/ACCESS-NRI/med-reviews/issues/103.