oss-slu / oss-slu/DigitalBoneBox

Refactor mapping of text labels and bone IDs

Open
#389 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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?

[!IMPORTANT]
Prerequisite issue: #352

Text annotations on an image can be clicked to navigate there. This is being handled by mapping the label text to a bone or bone part ID, in templates/js/imageAnnotationToDropdownMap.js. Preferably this would not be done in the front-end, though, so this mapping should be refactored to be stored directly in the data itself.


✅ Tasks to be Completed

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


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

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.

Research direction

First review prerequisite issue #352 and inspect templates/js/imageAnnotationToDropdownMap.js to understand how text labels map to bone or bone-part IDs. Trace where this mapping is consumed and where the related data is stored. Done means the mapping is stored in the data rather than the front end, with the application running cleanly and repository workflow checks passing.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.