8000 SEAB-7184: Generate DOI for workflow with existent-but-empty author name by svonworl · Pull Request #6120 · dockstore/dockstore · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

SEAB-7184: Generate DOI for workflow with existent-but-empty author name #6120

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conversation

svonworl
Copy link
Contributor
@svonworl svonworl commented Jun 6, 2025

Description
This PR makes a couple of changes to the webservice's DOI-related code:

  1. Changes the DOI creation code to filter out (not use) empty author names, which cause the following Zenodo error:
io.swagger.zenodo.client.ApiException: 
{
    "status": 400,
    "message": "A validation error occurred.",
    "errors": [
        {
            "field": "metadata.creators.0.person_or_org.family_name",
            "messages": [
                "Family name cannot be blank."
            ]
        }
    ]
}
  1. Ignores archived workflows in the query that determines the workflows that are eligible for an automatic DOI. This change doesn't relate to the "empty name" problem, I piggybacked it here to save some time.

Note that although I am a not a fan of the 8-space continuation indent style, I used it in this PR, so as to maintain consistency with the adjacent code.

Review Instructions
After this change is deployed to prod and the retroactive auto DOI creation script has been run, confirm that an automatic DOI was generated for https://dockstore.org/workflows/github.com/aryeelab/topology-tools/preprocess_microc, which contains author: '' in its wdl metadata.

Issue
https://ucsc-cgl.atlassian.net/browse/SEAB-7184

Security and Privacy

If there are any concerns that require extra attention from the security team, highlight them here and check the box when complete.

  • Security and Privacy assessed

e.g. Does this change...

  • Any user data we collect, or data location?
  • Access control, authentication or authorization?
  • Encryption features?

Please make sure that you've checked the following before submitting your pull request. Thanks!

  • Check that you pass the basic style checks and unit tests by running mvn clean install
  • Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
  • Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
  • If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
  • Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
  • Do not serve user-uploaded binary images through the Dockstore API
  • Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
  • Do not create cookies, although this may change in the future
  • If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.

@svonworl svonworl self-assigned this Jun 6, 2025
@svonworl svonworl requested review from denis-yuen and kathy-t June 6, 2025 23:10
@svonworl svonworl changed the title SEAB-7184: Generate doi for workflow with empty author SEAB-7184: Generate doi for workflow with existent-but-empty author name Jun 6, 2025
@svonworl svonworl changed the title SEAB-7184: Generate doi for workflow with existent-but-empty author name SEAB-7184: Generate DOI for workflow with existent-but-empty author name Jun 6, 2025
@denis-yuen
Copy link
Member

Note that although I am a not a fan of the 8-space continuation indent style, I used it in this PR, so as to maintain consistency with the adjacent code.

I actually don't mind a separate PR/commit to reformat things. I find github's blame interface pretty powerful

Copy link
Member
@denis-yuen denis-yuen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(re-ran build, looks unrelated gpg issue?)

Copy link
sonarqubecloud bot commented Jun 9, 2025

Copy link
codecov bot commented Jun 9, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.18%. Comparing base (eaf6245) to head (897a2ae).

Additional details and impacted files
@@                 Coverage Diff                 @@
##             hotfix/1.17.1    #6120      +/-   ##
===================================================
- Coverage            74.22%   74.18%   -0.05%     
+ Complexity            5663     5660       -3     
===================================================
  Files                  389      389              
  Lines                20329    20331       +2     
  Branches              2100     2100              
===================================================
- Hits                 15090    15083       -7     
- Misses                4237     4245       +8     
- Partials              1002     1003       +1     
Flag Coverage Δ
bitbuckettests 25.93% <0.00%> (-0.01%) ⬇️
hoverflytests 27.63% <100.00%> (+<0.01%) ⬆️
integrationtests 56.08% <0.00%> (-0.01%) ⬇️
languageparsingtests 10.82% <0.00%> (-0.01%) ⬇️
localstacktests 21.34% <0.00%> (-0.01%) ⬇️
regressionintegrationtests ?
toolintegrationtests 29.90% <0.00%> (-0.01%) ⬇️
unit-tests_and_non-confidential-tests 26.32% <100.00%> (+<0.01%) ⬆️
workflowintegrationtests 37.36% <0.00%> (-0.01%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@svonworl svonworl merged commit 250dd06 into hotfix/1.17.1 Jun 10, 2025
23 of 24 checks passed
@svonworl svonworl deleted the feature/seab-7184/generate-doi-for-workflow-with-empty-author branch June 10, 2025 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0