Skip to content
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

YDA-5829 troubleshooting tool for published data packages #517

Merged
merged 44 commits into from
Oct 23, 2024

Conversation

FuHsinyu
Copy link
Member

@FuHsinyu FuHsinyu commented Aug 30, 2024

New Shell Script

  • Added troubleshoot_published_data.sh: This script troubleshoots packages based on user input. It provides options to either troubleshoot a single package or all published packages.

New Python Rule

  • Task 1: Retrieve all published data packages from the vault.
  • Task 2: Conduct four types of verification for each published data package:
    • Metadata Schema Check: Ensures all data packages comply with the predefined metadata schema.
    • AVU Check: Checks for the presence and correctness of expected AVU pairs.
    • Data Cite Registration: Verifies registration with Data Cite through versionDOI and baseDOI.
    • File Integrity Checks: Checks the MD5 of landing page and combi JSON files against those on the public server.

Pending Task

  • Output to Terminal: Implementing a feature to output results directly to the terminal (stdout) is pending and would enhance usability. Completed!

Continuation

  • Sirjan and Claire may pick it up from here for changes due to my holiday leaves

@claravox claravox force-pushed the YDA-5829-diagnose-tool-for-data-packages branch 3 times, most recently from 9bd8fd8 to 2bbc8b5 Compare September 4, 2024 13:55
@claravox
Copy link
Contributor

claravox commented Sep 6, 2024

Would it be okay for vault-metadata-schema-report.r to print to standard out (or standard error) any errors instead of rodsLog?

@claravox claravox force-pushed the YDA-5829-diagnose-tool-for-data-packages branch 2 times, most recently from 9c2656a to 4e6f83d Compare September 9, 2024 14:30
@claravox claravox force-pushed the YDA-5829-diagnose-tool-for-data-packages branch 5 times, most recently from 7b49cf8 to ce9d988 Compare October 3, 2024 11:24
@claravox claravox force-pushed the YDA-5829-diagnose-tool-for-data-packages branch from 8567eb4 to 550f2eb Compare October 14, 2024 11:57
@claravox claravox force-pushed the YDA-5829-diagnose-tool-for-data-packages branch from 550f2eb to 9345d2c Compare October 14, 2024 12:07
@claravox claravox marked this pull request as ready for review October 14, 2024 12:19
@claravox claravox marked this pull request as draft October 15, 2024 08:10
@claravox claravox marked this pull request as ready for review October 16, 2024 09:03
util/log.py Show resolved Hide resolved
troubleshoot_data.py Outdated Show resolved Hide resolved
Copy link
Member

@lwesterhof lwesterhof left a comment

Choose a reason for hiding this comment

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

LGTM!

@lwesterhof lwesterhof merged commit 076ca8f into development Oct 23, 2024
15 checks passed
@lwesterhof lwesterhof deleted the YDA-5829-diagnose-tool-for-data-packages branch October 23, 2024 11:50
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.

4 participants