Course Reserves
(UXPROD-791)
|
|
| Status: | Closed |
| Project: | UX Product |
| Components: | None |
| Affects versions: | None |
| Fix versions: | None | Parent: | Course Reserves |
| Type: | New Feature | Priority: | TBD |
| Reporter: | Erin Nettifee | Assignee: | Erin Nettifee |
| Resolution: | Done | Votes: | 0 |
| Labels: | courses | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original estimate: | Not Specified | ||
| Epic Link: | Course Reserves |
| Development Team: | Other dev |
| PO Rank: | 0 |
| Rank: Cornell (Full Sum 2021): | R3 |
| Description |
|
Please note that Duke will develop this additional functionality - this feature does not need to be ranked and is not part of capacity planning. We are only recording it here for communication purposes. Current situation or problem: The Courses app has an optional LTI feature that can allow you to connect external systems that support LTI (like Canvas or Sakai) to FOLIO, in order to display items that are on reserve for a specific course. In its initial implementation, we assumed that all items that would be displayed through LTI would be visible in a library's discovery layer. This turns out to not be the case. Libraries often put items on course reserve that are not discoverable, such as faculty member personal copies, print course packs, or course equipment. This feature is meant to incorporate additional work for the LTI module so that items where the instance is suppressed, and there is no electronic access information, present in LTI without an associated link. That way students won't be presented with a discovery layer link that does not work. In scope
Out of scope
Use case(s)
Proposed solution/stories
Links to additional info Questions |
| Comments |
| Comment by Erin Nettifee [ 12/Jul/21 ] |
|
Duke has work on this happening in progress. |