Closed chrisshaw closed 7 months ago
There is some missing context here on how the proposal relates to the current status. When a user configures a VitalSource assignment, we currently display a flat list of table-of-contents entries for them to choose from. This worked OK in our initial tests, but I guess there are books where not having the full hierarchical structure is a problem. See https://github.com/hypothesis/lms/pull/3098 for a screenshot / video clip of what the current UI looks like.
This is now done in a minimal sense. See https://github.com/hypothesis/lms/issues/5821.
As an instructor creating an assignment, I want to see the same table of contents hierarchy I see in VitalSource in Hypothesis, so I can more quickly find and select the exact book segment I want to use as my assignment.
Why
The table of contents VitalSource provides nesting for publishers:
Meanwhile, the current assignment entry point selector shows a flat list. This makes it hard for assignment creators to find the segment they're looking for.
Flow
As an instructor...
Questions