learningequality
Resource metadata not properly synced (hotfixes)
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
Hi @radinamatic syncing of activity type, category or level is working correctly for me today. Did you observe that issue for any particular resource type?
After having played a bit more with various workflows for this, I can confirm that syncing metadata works correctly, but with some caveats that we (I) may not have (understood and) documented completely.
What most probably prompted my previous misunderstanding was that the resources in question were originally imported from a public channel to my channel A, some metadata added there, and then imported in my channel B. So when I was editing metadata in channel A, and trying to sync them on the channel B, the sync operation was actually being performed with the state of the resources on their original public channel, and not with my edited copy in channel A.
I'm not saying that that the behavior is wrong, just that if I was operating under that misapprehension, it's not out of the realm of possibility that some users might too.
All in all it's good this was punted to the next major release, as we'll have to think about some UX considerations and some new strings most probably, to clarify the conditions under which the sync is performed.
cc @jtamiace