[REVIEW]: WSKNN - Weighted Session-based K-NN recommender system

[editorialbot]

Submitting author: !--author-handle-->@SimonMolinsky<!--end-author-handle-- (Szymon Moliński) Repository: https://github.com/nokaut/wsknn Branch with paper.md (empty if default branch): paper Version: 1.2.0 Editor: !--editor-->@AoifeHughes<!--end-editor-- Reviewers: @inpefess, @svchb Archive: 10.5281/zenodo.8414247

Status

Status badge code:

HTML: <a href="https://joss.theoj.org/papers/afc237f4ed493a260006780394ddc3ba"><img src="https://joss.theoj.org/papers/afc237f4ed493a260006780394ddc3ba/status.svg"></a>
Markdown: [![status](https://joss.theoj.org/papers/afc237f4ed493a260006780394ddc3ba/status.svg)](https://joss.theoj.org/papers/afc237f4ed493a260006780394ddc3ba)

Reviewers and authors:

Please avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the target repository and link to those issues (especially acceptance-blockers) by leaving comments in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)

Reviewer instructions & questions

@inpefess & @svchb, your review will be checklist based. Each of you will have a separate checklist that you should update when carrying out your review. First of all you need to run this command in a separate comment to create the checklist:

@editorialbot generate my checklist

The reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @AoifeHughes know.

✨ Please start on your review when you are able, and be sure to complete your review in the next six weeks, at the very latest ✨

Checklists

📝 Checklist for @svchb

📝 Checklist for @inpefess

[editorialbot]

Done! archive is now 10.5281/zenodo.8414247

[AoifeHughes]

@editorialbot generate pdf

[editorialbot]

:point_right::page_facing_up: Download article proof :page_facing_up: View article proof on GitHub :page_facing_up: :point_left:

[AoifeHughes]

@editorialbot check references

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1007/978-3-030-72113-8_43 is OK
- 10.1007/s11257-018-9209-6 is OK
- 10.1145/2792838.2798723 is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.5281/zenodo.3509134 is OK
- 10.5281/zenodo.8233425 is OK

MISSING DOIs

- 10.1016/j.ins.2021.05.048 may be a valid DOI for title: Session-aware Recommendation: A Surprising Quest for the State-of-the-art

INVALID DOIs

- None

[AoifeHughes]

@editorialbot recommend-accept

[editorialbot]

Attempting dry run of processing paper acceptance...

[editorialbot]

Reference check summary (note 'MISSING' DOIs are suggestions that need verification):

OK DOIs

- 10.1007/978-3-030-72113-8_43 is OK
- 10.1007/s11257-018-9209-6 is OK
- 10.1145/2792838.2798723 is OK
- 10.1038/s41586-020-2649-2 is OK
- 10.5281/zenodo.3509134 is OK
- 10.5281/zenodo.8233425 is OK

MISSING DOIs

- 10.1016/j.ins.2021.05.048 may be a valid DOI for title: Session-aware Recommendation: A Surprising Quest for the State-of-the-art

INVALID DOIs

- None

[editorialbot]

:wave: @openjournals/dsais-eics, this paper is ready to be accepted and published.

Check final proof :point_right::page_facing_up: Download article

If the paper PDF and the deposit XML files look good in https://github.com/openjournals/joss-papers/pull/4663, then you can now move forward with accepting the submission by compiling again with the command @editorialbot accept

[arfon]

@editorialbot accept

[editorialbot]

Doing it live! Attempting automated processing of paper acceptance...

[editorialbot]

Ensure proper citation by uploading a plain text CITATION.cff file to the default branch of your repository.

If using GitHub, a Cite this repository menu will appear in the About section, containing both APA and BibTeX formats. When exported to Zotero using a browser plugin, Zotero will automatically create an entry using the information contained in the .cff file.

You can copy the contents for your CITATION.cff file here:

CITATION.cff

``` cff-version: "1.2.0" authors: - family-names: Moliński given-names: Szymon orcid: "https://orcid.org/0000-0003-3525-2104" doi: 10.5281/zenodo.8414247 message: If you use this software, please cite our article in the Journal of Open Source Software. preferred-citation: authors: - family-names: Moliński given-names: Szymon orcid: "https://orcid.org/0000-0003-3525-2104" date-published: 2023-10-09 doi: 10.21105/joss.05639 issn: 2475-9066 issue: 90 journal: Journal of Open Source Software publisher: name: Open Journals start: 5639 title: WSKNN - Weighted Session-based K-NN recommender system type: article url: "https://joss.theoj.org/papers/10.21105/joss.05639" volume: 8 title: WSKNN - Weighted Session-based K-NN recommender system ```

If the repository is not hosted on GitHub, a .cff file can still be uploaded to set your preferred citation. Users will be able to manually copy and paste the citation.

Find more information on .cff files here and here.

[editorialbot]

🐘🐘🐘 👉 Toot for this paper 👈 🐘🐘🐘

[editorialbot]

🚨🚨🚨 THIS IS NOT A DRILL, YOU HAVE JUST ACCEPTED A PAPER INTO JOSS! 🚨🚨🚨

Here's what you must now do:

0. Check final PDF and Crossref metadata that was deposited :point_right: https://github.com/openjournals/joss-papers/pull/4666
1. Wait a couple of minutes, then verify that the paper DOI resolves https://doi.org/10.21105/joss.05639
2. If everything looks good, then close this review issue.
3. Party like you just published a paper! 🎉🌈🦄💃👻🤘

Any issues? Notify your editorial technical team...

[arfon]

@inpefess, @svchb – many thanks for your reviews here and to @AoifeHughes for editing this submission! JOSS relies upon the volunteer effort of people like you and we simply wouldn't be able to do this without you ✨

@SimonMolinsky – your paper is now accepted and published in JOSS :zap::rocket::boom:

[editorialbot]

:tada::tada::tada: Congratulations on your paper acceptance! :tada::tada::tada:

If you would like to include a link to your paper from your README use the following code snippets:

Markdown:
[![DOI](https://joss.theoj.org/papers/10.21105/joss.05639/status.svg)](https://doi.org/10.21105/joss.05639)

HTML:
<a style="border-width:0" href="https://doi.org/10.21105/joss.05639">
  <img src="https://joss.theoj.org/papers/10.21105/joss.05639/status.svg" alt="DOI badge" >
</a>

reStructuredText:
.. image:: https://joss.theoj.org/papers/10.21105/joss.05639/status.svg
   :target: https://doi.org/10.21105/joss.05639

This is how it will look in your documentation:

We need your help!

The Journal of Open Source Software is a community-run journal and relies upon volunteer effort. If you'd like to support us please consider doing either one (or both) of the the following:

• Volunteering to review for us sometime in the future. You can add your name to the reviewer list here: https://reviewers.joss.theoj.org/join
• Making a small donation to support our running costs here: https://numfocus.org/donate-to-joss

[SimonMolinsky]

@AoifeHughes thank you for leading this review!

@inpefess @svchb thank you again for your help and invaluable comments during the review.

Thank you all for your time and volunteering with the publication! :rocket: