Sometimes instructors perform a citation search in Leganto and just add the first result that comes up in the search results; often this is actually a book review or other format that isn't logical for reserves. Additionally, most instructors are searching and expecting the latest edition to appear first in the list. Other faculty from certain departments want to choose a particular edition, and so need edition information prominently surfaced in the search result.

This results in processing delays as staff must check with instructors to clarify what items they really intended to place on reserve.

One possible solution may be to offer an option for faculty to specially indicate that the submitted citation must be filled as specified (format/edition). Something could indicate that by default, any available edition can be substituted for the one added to the list as a result of search.

The Leganto UI supports multiple languages, which is very helpful. It is however not possible to translate individual texts of reading lists, such as their titles, into different languages.

Please enable the following:

1. A way to easily input in multiple (at least two) languages a) reading list titles, b) section names, c) citation public notes, d) section notes, and e) possibly other such reading list related texts that are not part of the bibliographic metadata.




2. That the relevant translated text (as per above) be displayed depending on what language the user has selected for the UI in the Leganto language menu.

To be clear: a kind of multi language support for reading lists may already be implemented by creating duplicate lists, one for each language, but that approach has at least the following drawbacks:

1. When working with a rolled-over list, the very same changes (e.g. adding new citations) must be made to several lists, which is error prone and somewhat tedious.




2. The user changing the language setting for the Leganto UI does not affect which language version of the reading list is displayed.




3. Data integrity is weaker, because even though the different language versions are supposed to reflect the very same list, their actual content is not interlinked and may well differ in reality (something that could occur as a result of failing to reproduce the very same changes when working with a rolled-over list, as mentioned under (1)).

Oh, and all such translations should of course be readable and writeable via the API:s.

(This suggestion focuses in particular on the ability to translate texts in reading lists but is somewhat related to this idea: https://ideas.exlibrisgroup.com/forums/395697-leganto/suggestions/39034405-display-templates-and-other-elements-in-the-interf)

Physical (print) and electronic (ebook) availability cannot be added as columns in these Analytics subject areas. This would be hugely beneficial for most of our daily reports and workflows as we try to ensure that a certain number of copies or electronic versions are available for resources added to reading lists.

An additional requirement is for availability to be shown for records related to the citation. This is because we have separate title records for physical (print) holdings and electronic (ebook) portfolios, and use the related_records parameter in Leganto Customer Settings to display availability for all available formats at citation level.

We have three kinds of content:
* copyrighted material - should never be OA
* teacher-created content that they want to keep to their class only
* teacher-created content that they'd like to share with other teachers and/or use to promote their class

To accommodate this third group, we'd like functionality that would let teachers tag content they've uploaded to be made open access. Functionality should:

• make teachers confirm they (or the university as their employer) own the IP




• let them choose a Creative Commons license




• provide a permalink for the item where it's accessible publically




• provide a platform where the public can search and browse all the institution's open access content




• provide a platform where teachers can search and browse materials from the whole the Leganto community, and easily add to their own class reading lists




• provide a machine-readable way for other OER/content aggregators to harvest metadata about the content (eg DigitalNZ harvests OA teaching materials from our Equella repository using OAI-PMH)

In today's interface, if you want the same template in different languages, you have to either create one for each language, or remember to have both languages in the section title when creating the template.

EX: Section 1: Obligatorisk/Mandatory

Templates consist of a name, description and section names. The person creating the template could be given the option to translate these fields when creating the template. Of course, it would be an advantage if templates could be edited later on.

All templates should be visible regardless of the interface language, but the template should be shown in the same language as the interface language, if available. Later on, the section names, based on the chosen template, could also be shown to students in the chosen interface language.

A step further would be to allow instructors to translate list titles and section names (when the section names are not based on a template).