oss-slu / oss-slu/DigitalBoneBox
Sort bone data into directories by boneset
Nobody has claimed this yet.
- 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?
Bone data in the app is organized by "boneset," sets of related bones based on individual PowerPoint files where we're getting our data. But they are currently all pooled into the same parent folder, making the data hard to browse through and modify in case adjustments are needed.
✅ Tasks to be Completed
A checklist of the specific, actionable steps required to complete this issue. This helps track progress.
- Sort data by boneset in data folder
- Refactor data extraction to work with the new structure
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the data folder and the existing data-extraction code to identify how bonesets are currently located and loaded. Organize the data by boneset, update extraction to use the new structure, then run the repository workflow checks and confirm the application still runs without errors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-engineering
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100