Skip to content
Innovative Idea Exchange

ILS - Polaris

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

6 results found

  1. In Leap, when editing a bib from the record or in the compare tool, it would be helpful to copy/paste an entire tag or multiple tags, including the indicators, delimiters, tag numbers, subfields, etc.

    2 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

  2. Currently in Leap, fields containing multiple lines of text (for example, often 520s, 505s, etc.) display the whole field until one clicks into it, when it collapses to one line. After this point, it will only display one line of text at a time, requiring either mousing or excessive use of arrow keys to move around within the field. Would it be possible to keep the field expanded, displaying all text within the field at once? We often need to see an entire field at once, rather than only a small part of it.

    4 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

  3. Currently, the quick search bar does not do allow ISBN searching. It would be helpful to be able to scan an ISBN in the quick search bar and have the bib record pop-up, like what happens with item records when a barcode is scanned.

    20 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

  4. Make full-screen editing more easily usable. One example: deleting multiple fields at once.

    Make it possible to add fields ANYWHERE, not only after a similar type of field (i.e. fixed fields--why can't I add them anywhere?).

    14 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

  5. Catalogers have been waiting since January 2020 for MARC field 532 - Accessibility Note to be included in the MARC bibliographic validation table. This MARC change was approved by LC in 2018 and has been showing up in AV records ever since. Catalogers see a "not defined" error message when saving a record which includes an unvalidated field.

    Currently we may only add a local MARC tac to the validation table (eg 9XX, X9X or XX9). Otherwise, it must wait for the LC MARC bibliographic update to be implemented by Polaris development in a new Polaris version. We now hear…

    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

    We rely on the MARC updates from LC to notify us of changes to the standard that need to be incorporated into the code. I can't speak to why LC approved this particular example in 2018 but didn't include it officially until 2023.

    But I can say that because all of our MARC validation rules are stored in the database, it's possible for you to get patches of the latest MARC updates at any time. After seeing this request, we setup a process with our Support team to ensure they know the location of the latest MARC update scripts and can apply them to your server on request.

    We process MARC updates at the start of each Polaris release, and you do not need to wait for the release to be GA to receive a patch for those updates. For example, we currently have patches available for Updates 39 &…

  6. When downloading a record, have a setting that automatically removes certain lines (like 650s with a second indicator of 6).

    10 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

  • Don't see your idea?