Skip to content

add-doi: confirm the Zenodo website link, accept the community request, and output the data availability text (after washr 1.3.0) #99

Open

Description

@larnsce

Follow-up from the guluswm 1.0.0 release (3 November 2026) and two washr changes planned for washr 1.3.0.

Changes to skills/add-doi/SKILL.md once washr 1.3.0 is the floor (pkgreview-core/WASHR_FLOOR):

  1. Step 7, Zenodo record review. With write_zenodo_json(): link the package website in the Zenodo description and related identifiers washr#154 (PR feat: link the package website in .zenodo.json washr#156), .zenodo.json carries the website link in the description and as an isDocumentedBy related identifier, and the repository as isSupplementTo. The prompt then only confirms these instead of asking the maintainer to add them by hand.
  2. Community request. guluswm's .zenodo.json listed the openwashdata community, yet the record appeared without it until it was added by hand in the Zenodo editor. The GitHub integration submits a community request that a curator has to accept. Step 7 should say so and point to the community's request inbox, so the record does not stay outside the community.
  3. Text for the article authors. With data_availability_statement(): draft the citation and data availability text for the article that uses a data package washr#155, add a last step that calls washr::data_availability_statement() and shows the reference entry and the data availability statement for the email to the authors (written by hand for guluswm).

Until washr 1.3.0 is released, the current manual prompt stays.

Activity

  1. larnsce commented on Nov 3, 2026

    @larnsce
    ContributorAuthor

    Two deviations from the issue text in the coming PR:

    • The data availability text is not the last step of add-doi. It is the new Step 9, before the dev sync and the development version (now Step 10). Run after Step 10, washr::data_availability_statement() would read the x.y.z.9000 version from DESCRIPTION and name an unreleased version. The step runs on main and first asks for the opening words of the statement, with "The data" as the default.
    • The floor bump to 1.3.0 also covers the /washr skill preflight, which needs only 1.2.1 by itself, so that all skills share one floor as in 1.8.0.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions