Open bradenmacdonald opened 4 months ago
@ormsbee any updated thoughts on whether we can use LearningPackage.description to store the "description" of content libraries? Or would you prefer we store it on the ContentLibrary
model directly?
I think it's currently hooked up to use LearningPackage.description
. I lean slightly towards keeping it in openedx-learning's publishing
app, but I go back and forth on whether it should be a field that's deferred by default or an entirely separate 1:1 model–since LearningPackage
is going to be pulled back as part of join operations by almost everything.
OK, well for the purposes of this project, we'll just stick with whatever the current approach in openedx-learning is, if that's ok - either way works.
CAN_EDIT_THIS_CONTENT_LIBRARY
permission; for read-only users, the Description field should be read-only.