Leganto

Your feedback matters to us. Help us improve Leganto by telling us what you’d like to see using the message areas below. You can also can support something already posted.

We would love to be able to respond to every idea that is submitted, but this is not feasible. We are, however, committed to responding to the most popular ideas—those that have received the most points.

For more information please review our FAQ and guidelines. Thank you.

  1. Improvement and development of the Leganto broken link handling

    At the moment Alma offers very little to properly handle Leganto broken links via the task-list menu. Once a Broken Link Alert is removed, the information is gone from Alma entirely. The functionality is inadequate as a workflow for library staff when investigating and recording details of our progress in fixing the problem, keeping students informed and statistical reporting.

    We would like to see additional functionality :
    • Broken Link Alerts to have a more permanent record in Alma and Analytics
    • Introduction of additional fields to capture information about the Broken Links - for example broken link status (e.g.…

    138 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. When adding citations to a list via search, prioritize latest edition and owned item first

    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…

    101 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We are exploring options for this idea. The priority of the results is set by either Primo or Summon, so we cannot simply show the newest edition first unless the discovery ranking changes. However, we could potentially develop an option using the Questions feature in which the system could recognize that the instructor has added something which has other editions. The library could then configure a question for the instructor to understand if they want that edition, any edition, or the newest edition, for example. Would this help meet the need?

  3. Stopping list creation from Leganto interface

    Allow libraries to configure an option to stop academics creating new reading lists from the Leganto interface, but still allow them to edit lists created by the library.

    49 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. Hide locations from Resource Locate

    Hide locations from Resource Locate

    We would like an option to filter out specific locations for the resource locate functionality in Leganto.

    For legal reasons we can't purge lost/discarded items, they have to remain in Alma where they are collected in locations that are suppressed from discovery so they don't show up in Primo. Unfortunately that doesn't exclude them from being used as positive results for resource locating even though they are not actually available.

    We also have several collections that are not accessible to people but (some of them) show up in Primo. Those are also items we wouldn't…

    21 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)
    Under Review  ·  1 comment  ·  Admin →

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. Automatic enrichment (update) of reading list citations

    We are looking at using Rialto and ordering from Leganto looks to be a good option as Academics can place requests (Purchase requests) through the system. Ideally we would like the entry in Leganto to update the citation and status automatically once a bib is attached to the citation.

    15 votes
    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    You have left! (?) (thinking…)

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  • Don't see your idea?

Leganto

Categories

Feedback and Knowledge Base
https://ideas.exlibrisgroup.com/forums/395697-leganto/status/1582690
ideas.exlibrisgroup.com
crawl=CC-MAIN-2022-21
182834
application/http; msgtype=response
sha1:J2B6LMDBS7QQDFPAAITD7B5D425HC3A5
<urn:uuid:51e97bd4-dded-4420-962b-4791cc177043>
2022-05-16T08:13:46Z
104.17.27.92
text/html
sha1:OBD2IGBGSQETZHBQPMMF7CNQDGCII6HQ
<urn:uuid:5ca9a1a5-c1fc-4608-842d-ec9226db4041>
https://ideas.exlibrisgroup.com/forums/395697-leganto/status/1582690
response
<urn:uuid:f0113be0-6458-48fb-976b-638ac2edecde>
isPartOf: CC-MAIN-2022-21
publisher: Common Crawl
description: Wide crawl of the web for May 2022
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-76
software: Apache Nutch 1.18 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.3-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: https://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/