learningequality / learningequality/studio
Resource metadata not properly synced (hotfixes)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
Observed behavior
While the changes in the resource title, files, and assessment details are being properly synced, metadata changes like activity type, category, level are not.
I first noticed that if I add more than one activity type, category or level on the resource in the origin channel (nokot-gihop), those were not properly synced on the destination channel (lonot-nodan).
Then just to be sure I made another channel (johug-funol), imported the same resources from the origin channel (nokot-gihop), changed activity type, category or level (just one of each), and it still would not sync properly:
https://github.com/learningequality/studio/assets/1457929/6fc4c1eb-21e6-4a5c-9a61-1f6b868af6cf
Another slightly confusing thing for me was that the sync progress is displayed in the same placeholder as the publish progress would be, and the switch back to the info Published N minutes ago after the sync completed made me wonder... Minor thing, but caught my eye.
Expected behavior
Properly synced activity type, category and level metadata.
User-facing consequences
User unable to have the full metadata updated after syncing.
Errors and logs
Nothing that I could see in the console (usual CORS errors, yes), a part from this 404 that I'm guessing has nothing to do with syncing.
Usage Details
- OS: Ubuntu 20.04
- Browser: Firefox
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 syncing a resource between the named origin and destination channels while changing activity type, category, and level, then trace the resource metadata sync path. Also inspect the sync-progress display, since the issue notes that it reuses the publish-progress placeholder. Done means all three metadata types sync correctly and the completed state is presented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100