oss-slu / oss-slu/DigitalBoneBox

Clean up and validate Bony Pelvis dataset data

Open
#327 0 comments 0 reactions 1 assignee View on GitHub

@Joishee05 is already working on this.

Since Apr 6, 2026.

enhancement
Dominant language
JavaScript
Stars
8
Forks
18
Avg merge
8h 17m
Merged PRs (30d)
4

Description

🎯 Goal / Objective

A clear and concise description of what this task aims to achieve. Why is this task important?

There are some lingering errors in the Bony Pelvis dataset, such as errors in text labels, descriptions, etc.


✅ Tasks to be Completed

A checklist of the specific, actionable steps required to complete this issue. This helps track progress.

  • Run the web app alongside the Bony Pelvis slideshow and follow along. Fix any discrepancies between the data displayed in the app and what is in the slideshow.

Acceptance Criteria

A checklist of conditions that must be met for this task to be considered complete. How will we verify that it's done correctly?

  • The new feature is implemented as described.
  • All related code passes the repository's workflow checks (linting, tests).
  • The application runs without errors after the changes are made.
  • (If applicable) New automated tests have been added to cover the changes.
  • Any related documentation has been updated, including JSDoc comments or docstrings

Additional Context

Add any other context, notes, screenshots, or links that might be helpful for completing this task.

[!IMPORTANT]
Though not a strict prerequisite, it may be easier to complete this task if #374 is completed first.

One example of a problem that needs to be fixed: the "auricular surface" bone part should not have any text labels over it, but it currently shows the labels that should only be overlaid over the "ilium" bone.

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.