Support presentation of reading lists in an iFrame within VLE / LMS
Ex Libris currently do not recommend integrating Leganto reading lists within a VLE / LMS using an iframe, as there is an issue with cookies.
We would like to ask for this issue to be re-investigated by Ex Libris and an alternative proposed for roadmap development that fixes the issue without inelegant workarounds such as manually altering browser cookie policies or using a different web browser - noting that these workarounds are not always possible for users depending on local security policies.
At Imperial College London we have been using Blackboard LTI integration with Leganto within an iframe since launch. This is based on our academics' view that it is particularly important to ensure reading lists are presented in the same place students go for all other aspects of online learning, rather than directing students over to another campus system.
We believe this issue is a widely felt one, therefore we ask sites that agree to up-vote this idea.
The attached screenshot demonstrates how the iframe integration appears within Blackboard using LTI.
Paul Harding commented
This issue is now being reported on a daily basis as we roll Leganto out across the institution, so I'll definitely be adding my support.
I agree with Blake that this should be classed as a bug.
Blake Galbreath commented
Honestly, this is not an enhancement.
This is a bug.
ExL should fix this immediately. I answered a helpdesk ticket about this just yesterday.
Chris Jones commented
This issue is a very important one given the widespread use of BlackBoard and Canvas, and of course Safari for end users.
Since there is some leganto and institution information in the URL, the illegal institution message itself should be addressed as a high priority as it will only become a bigger issue for a wider number of customers.
In addition, Ex Libris should focus on mitigation of the poor error message, to mitigate/improve the UX if the error is still happening and likely to take a long time to resolve more completely.
e.g. why not redirect to the Public "Find Lists" page, or to the default Leganto landing page (prompting for the SAML or Local log-in, as per the configuration for permalinks).
The URL being submitted does not have an illegal institution code in fact so the error is too broad-brush and confusing to any end user. The referring URL contains leganto and customer institution parameters which at least could sensibly be harnessed to go to a usual alternative landing page/way back to Leganto.