You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In its public details, a cheffed channel shows a 'Primary Language' pulled from the channel itself which differs from its 'Languages' which is aggregated from the channel content
Public channel card
Public channel details
Expected behavior
This is manually correctable, but worth considering whether during channel publishing we should validate that the 'Primary Language' is one of the content languages.
Proposal
We could add the ability to update/validate the channel's 'primary' language in the publishing modal, giving only options as defined by content with those languages, and defaulting to the previous selection if content with that language still exists in the channel.
User-facing consequences
How is the channel language used in Kolibri?
Is making sure the channel's language accurately reflects the content something that's important beyond display on Studio?
The channel language is used in filtering for import, so this is a fairly important piece of metadata. This feels like a validation failure first in ricecooker and then in the Studio internal API endpoints, where the only language of resources is Magyar, but the overall channel language is set to English.
Yeah, I agree that we should validate this in ricecooker and its API endpoints. Although, @laurenlichtman raised a point about having some general validation on this during publishing, which could handle non-cheffed and private channels too. It does seem meaningful for all users, and would protect against this discrepancy beyond solely for our own purposes.
@bjester@rtibbles would the below be the intended direction to take for this task?
Also, as long as the previously selected language still exists in the content, it should be the one selected, else no selection?
Observed behavior
In its public details, a cheffed channel shows a 'Primary Language' pulled from the channel itself which differs from its 'Languages' which is aggregated from the channel content
Expected behavior
This is manually correctable, but worth considering whether during channel publishing we should validate that the 'Primary Language' is one of the content languages.
Proposal
We could add the ability to update/validate the channel's 'primary' language in the publishing modal, giving only options as defined by content with those languages, and defaulting to the previous selection if content with that language still exists in the channel.
User-facing consequences
Additional information
https://learningequality.slack.com/archives/C0LK8QS9J/p1671559303563319
The text was updated successfully, but these errors were encountered: