openedx / openedx/openedx-platform
Import to Library (Modulestore Migrator) Analysis overestimates # of components
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 8.2k
- Forks
- 4.4k
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 42
Description
When importing a very small course, it's easy to see that the "import analysis" of modulestore migrator shows the wrong number of components to import into a library.
- Create a small course with only a couple of components.
- Create an empty library. Go Tools > Import > select the course from step 1.
The analysis shows:
But the final result is:
The difference of 9 blocks is likely due to the type@about+block@subtitle, type@about+block@duration, type@about+block@description, type@about+block@short_description,type@about+block@overview, type@about+block@entrance_exam_enabled, type@about+block@entrance_exam_id, type@about+block@entrance_exam_minimum_score_pct, type@about+block@about_sidebar_html metadata XBlocks that every course has.
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
Reproduce the issue by creating a small course and empty library, then using Tools > Import to compare the analysis count with the final imported result. Trace the Modulestore Migrator import-analysis entry point and verify that the nine listed metadata XBlocks are handled consistently; done means the analysis count matches the components actually imported.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100