openedx / openedx/openedx-core
Dynamic content backcompat for `<item_bank>`, `<library_content>`
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 12
Description
Background
Note: <item_bank> AKA "Problem Bank" is the new thing. It's implemented as the base class of <library_content> AKA "Randomized Content Module" (distinct from <randomize>), which adds in support for legacy library syncing. Will need to think about how this plan works alongside the legacy libraries migration.
Sources:
- New: https://github.com/openedx/edx-platform/blob/master/xmodule/item_bank_block.py
- Legacy: https://github.com/openedx/edx-platform/blob/master/xmodule/library_content_block.py
Docs:
- New: https://edx.readthedocs.io/projects/edx-partner-course-staff/en/latest/exercises_tools/randomized_content_blocks.html
- Legacy: https://docs.openedx.org/en/latest/educators/how-tos/course_development/add_a_problem_bank_to_your_course.html#add-a-problem-bank-to-your-course-for-randomization
Plan
TBD
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
Start by comparing xmodule/item_bank_block.py with xmodule/library_content_block.py and reviewing the linked documentation for new and legacy behavior. Read the legacy libraries migration issue before defining how dynamic-content backcompat should work; the issue is complete when the compatibility plan is resolved and its required implementation and documentation changes are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100