openedx / openedx/openedx-core
Can we efficiently represent a Taxonomy as a PublishableEntity with Dependencies?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 10
- Forks
- 32
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 12
Description
I've said in the past that the way we model versions for things like containers would be inefficient for very large things like Taxonomies, because it would require rewriting all the parent/child relations on every version. But I belatedly realized that we could model Taxonomies reasonably efficiently if there are many levels of hierarchy and only a few of them are changing at a time. We'd use the same tricks for when we have unpinned parent/child dependencies.
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
No files, tests, or entry points are named. Start by clarifying the proposed PublishableEntity and dependency model for Taxonomies, including how versions and changing parent/child relations should work; done requires an agreed design rather than a defined code change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- django, python
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100