-
Notifications
You must be signed in to change notification settings - Fork 89
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I want to select a whole collection in a problem bank [needs design] #1599
Comments
@jmakowski1123 The challenge here is what happens if a new problem is added to the collection after the author does this and creates the Problem Bank? If we need to make the Problem Bank update to include that new problem as an option, it makes this much more complicated. CC @kdmccormick |
Just to be clear, this is not on a Teak timeline. |
@bradenmacdonald I think it would be easier if problem bank components were always mapped to collections instead of components. If users want to use just a portion of a collection, they can create a new collection to store that portion of questions. |
That was one of the ideas we had originally discussed, but it does have some drawbacks for certain simple workflows which may be why we didn't go with that option for now. It also doesn't really make it any easier for us to implement a solution to the challenge of needing to update the problem bank whenever the collection is updated. I'm not opposed to it though. |
I don't know details about the backend, but I think it would make the frontend design easier. |
As a content author, I may choose to use a collection for a set of problems I'd like to randomize from. I'd like an option to be able to select an entire collection in the problem bank block, rather than having to select multiple problems one by one.
[needs design]
The text was updated successfully, but these errors were encountered: