[REVIEW]: Web-based text anonymization with Node.js: Introducing NETANOS (Named entity-based Text Anonymization for Open Science)

[whedon]

Submitting author: @ben-aaron188 (Bennett Kleinberg)
Repository: https://github.com/ben-aaron188/netanos
Version: v1.1.5
Editor: @acabunoc
Reviewer: @RichardLitt
Archive: 10.5281/zenodo.817892

Status

Status badge code:

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

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) 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 questions

Conflict of interest

• As the reviewer I confirm that there are no conflicts of interest for me to review this work (such as being a major contributor to the software).

General checks

• Repository: Is the source code for this software available at the repository url?
• License: Does the repository contain a plain-text LICENSE file with the contents of an OSI approved software license?
• Version: Does the release version given match the GitHub release (v1.1.0)?
• Authorship: Has the submitting author (@ben-aaron188) made major contributions to the software?

Functionality

• Installation: Does installation proceed as outlined in the documentation?
• Functionality: Have the functional claims of the software been confirmed?
• Performance: Have any performance claims of the software been confirmed?

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 function 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

• Authors: Does the paper.md file include a list of authors with their affiliations?
• A statement of need: Do the authors clearly state what problems the software is designed to solve and who the target audience is?
• References: Do all archival references that should have a DOI list one (e.g. papers, datasets, software)?

[whedon]

Hello human, I'm @whedon. I'm here to help you with some common editorial tasks for JOSS. @RichardLitt it looks like you're currently assigned as the reviewer for this paper 🎉.

⭐ Important ⭐

If you haven't already, you should seriously consider unsubscribing from GitHub notifications for this (https://github.com/openjournals/joss-reviews) repository. As as reviewer, you're probably currently watching this repository which means for GitHub's default behaviour you will receive notifications (emails) for all JOSS reviews 😿

To fix this do the following two things:

1. Set yourself as 'Not watching' https://github.com/openjournals/joss-reviews:

2. You may also like to change your default settings for this watching repositories in your GitHub profile here: https://github.com/settings/notifications

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

@whedon commands

[RichardLitt]

Version: The GitHub release does not match, and the npm release is now ahead of the release for this review (as it is 1.1.3, instead of 1.1.0). I don't know how to best suggest moving forward; perhaps committing and tagging a GitHub release as 1.1.3, and then updating this submission here?

[RichardLitt]

Opened issues for Version and References. Otherwise, this is all good. Note: not sure what to do about versions. See above.

[RichardLitt]

Note: I am happy with the changes I suggested in #283. These have now been fixed.

[ben-aaron188]

@RichardLitt Thanks for pointing that versioning issue out. We've tried to address this as follows:

1. Latest version is in the GitHub repo
2. Latest version is in the npm release with v1.1.4
3. On the GitHub repo, we created a release tag to the master branch with v1.1.4 and refer to the npm link in the release description

Does this sound like an option? We would need to change the version for the JOSS submission then though.

[RichardLitt]

Sounds good to me! Changing the version in the JOSS submission also seems like a smart move. @arfon that's the last thing that needs to be done, and then I consider this to be worthy of accepting as is.

[RichardLitt]

@whedon commands

[whedon]

Here are some things you can ask me to do:

# List all of Whedon's capabilities
@whedon commands

# Assign a GitHub user as the reviewer of this submission
@whedon assign @username as reviewer

# List the GitHub usernames of the JOSS editors
@whedon list editors

# List of JOSS reviewers together with programming language preferences and domain expertise
@whedon list reviewers

# Change editorial assignment
@whedon assign @username as editor

# Set the software archive DOI at the top of the issue e.g.
@whedon set 10.0000/zenodo.00000 as archive

# Open the review issue
@whedon start review

🚧 Important 🚧

This is all quite new. Please make sure you check the top of the issue after running a @whedon command (you might also need to refresh the page to see the issue update).

[RichardLitt]

@arfon Looks like we need to have an 'Update version' command, and an 'accept paper' command.

[arfon]

@arfon Looks like we need to have an 'Update version' command, and an 'accept paper' command.

👍 yep, that's next on my todo list.

[arfon]

@ben-aaron188 - Could you move the references you currently have in the paper.md file into a paper.bib file and cite them directly please? (You can read how to do that here)

I've also made a small fix to your paper meta data here: ben-aaron188/netanos#7

After fixing these two items up, could you make an archive of the reviewed software in Zenodo/figshare/other service and update this thread with the DOI of the archive? I can then move forward with accepting the submission.

[ben-aaron188]

@arfon The references are updated and the pull request is merged. To avoid any versioning inaccuracies with npm, we’ve updated the npm release with these changes (which unfortunately implied that we needed to provide a new version in the package.json).
If possible, could you update the JOSS version to v1.1.5?

We’ve linked the v1.1.5 tree in the master branch to Zenodo. Here’s the DOI 10.5281/zenodo.817892

The bagde is here (already included at the top of the readme):

[RichardLitt]

Small note: thanks @ben-aaron188 for being so receptive to changes and fixes!