Skip to content
Idea Exchange

ILS - Polaris

JUMP TO ANOTHER FORUM

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback

5 results found

  1. For collection development purposes, we need to know how popular an item is. Right now, renewals from the same patron counts as a circ. It would help to have renewals counted separately so that we can have an accurate circulation stat. For example, our YA Manga (33090005890258) shows that lifetime circulation is 5 but it's actually 2 patron checkouts with 3 renewals. This number makes it seem that this manga is more popular than it is. New items are easier to count right now but as time passes, looking at the history will become more time consuming.

    Idea Value
    Time…

    79 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  2. Currently printing receipts from the Leap web app is unideal, requiring either significant manual intervention from the user or extensive browser tweaks to get it operable. A background desktop client (similar to JSPrintManager) could handle the printing far better than the browser does natively.

    78 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  3. In the client, duplicate detection for MARC records is triggered by (re)saving the record, but can also be triggered separately as an action under the Tools menu. In Leap, resaving the record is the only way to trigger the function. This means cataloguers have to do a fake edit in order to un-grey-out the save button and click past any other functions, such as MARC validation, before they can get to the matching record(s).

    Having duplicate detection as a separate function (maybe under Actions or as a button in the MARC view) would save cataloguers time and extra clicking.

    39 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  4. When dealing with missing/damaged/canceled orders, we start at the Bib record and link over to the attached POs/Invoices. Right now in LEAP we have to start with the PO or Invoice, which we often don't know when we have the book in hand. I'd like to be able to link from the Bib Record to either Purchase Orders or Invoices or both.

    17 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
  5. At the demonstration of Leap at IUG, we learned that PO line item duplicate check action is not available in Leap from the PO workform. We need to be alerted to existing items in our systems if we own them, to attach add copy orders to existing bibs. Please add this functionality.

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    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?