learningequality / learningequality/studio
Add contentnode deduplication to import from other channel search
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
In https://github.com/learningequality/studio/pull/3399 we removed deduplication of content nodes from import from other channel search due to https://github.com/learningequality/studio/issues/1055 a long standing bug on studio where in two contentnodes with different content can have the same content_id.
We need to re-think our approach on how we treat equality of two contentnodes. Once that's done, we can implement deduplication.
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 reviewing pull request #3399 and issue #1055 to understand why content-node deduplication was removed and how duplicate content_id values arise. Define a reliable equality approach for content nodes before implementing deduplication in the import-from-other-channel search; done means distinct content is preserved while equivalent nodes are deduplicated.
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