When adding resources, you want to keep the description general – to make it reusable by others. But at the same time, you want to be able to give specific descriptions to your students. "Do this instead of exercise 25–30 in the book" makes perfect sense to your students, but not to anyone else.
(Thanks to @dvdndrssn for pointing this out!)
Add a description field to the reference resource list -> resource. (Holy crap, this would add *another* layer of relationships.)
Think a bit more, to see if another layer of relationships may be avoided.
Discuss with beta testers.
Try out a solution. Evaluate. Improve.
Another text field, used when adding resources to resource lists. Probably.
Maybe resource lists won't refer to resources, but to entities of "resource + comment".
Or maybe resource lists will be replaced by "resource + comment".
Who knows?
Comments
Comment #0.0
itangalo commentedAdding cred to David Andersson.
Comment #1
itangalo commentedImplemented in 2.4: Embedded resources are now stand-alone (not in lists), and each of them may have a 'contextual description' (in contrast to the title, which should be understandable out-of-context).