Skip to content

Adding metrics to the research impact section #274

Description

@Armavica

Hi, as part of the review that I am doing for JOSS openjournals/joss-reviews#10580 I have to evaluate the following point:

Research Impact Statement (required section): Does the paper include a "Research Impact Statement" section providing evidence of realized impact (publications, external use, integrations) or credible near-term significance (benchmarks, reproducible materials, community-readiness signals)? Is the evidence presented compelling?

I am finding the phrasing of this section a bit unclear but if I understand it correctly (this is also what I saw in the Cargo.toml files of the different packages), pharmsol is a Rust dependency of PMcore, which is a Rust package that Pmetrics, a popular R package, has been relying on since its version 3.
If this is correct, and if pharmsol is responsible for a substantial amount of the Pmetrics functionalities, then I think that sharing a few metrics of the v3 of Pmetrics could strengthen your case for the research impact. Perhaps the number of weekly (or monthly) downloads of Pmetrics if you have access to it, or the estimated number of publications external to your group that used Pmetrics v3 --I found several ones with a quick literature search.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions