13 results found

1. Improve Authority Records Search with a “Return to Results”

   Current user experience shows a gap in the Authority Records search flow. After running an authority search in Leap and opening an individual record, users are unable to return to the original results list. The only available option is to close the record, which also closes the search, forcing users to re‑enter and re‑run the query. This creates unnecessary repetition and slows cataloging work.

   Proposed Enhancement (User‑Journey View):

   Add a “Results” button to Authority Record views—mirroring what already exists in Bibliographic Records.
   This allows catalogers to:

   Move seamlessly between multiple authority records that appear in a single search (for example, multiple “Laura Martin” entries).
   Maintain their place in the search journey without having to repeat steps.
   Minimize workflow interruption and reduce duplicated searching.

   Desired Outcome:
   A smoother, more consistent user journey across both Bibliographic and Authority Record searches, reducing friction, saving time, and aligning behaviors across record types.

   Current user experience shows a gap in the Authority Records search flow. After running an authority search in Leap and opening an individual record, users are unable to return to the original results list. The only available option is to close the record, which also closes the search, forcing users to re‑enter and re‑run the query. This creates unnecessary repetition and slows cataloging work.

   Proposed Enhancement (User‑Journey View):

   Add a “Results” button to Authority Record views—mirroring what already exists in Bibliographic Records.
   This allows catalogers to:

   Move seamlessly between multiple authority records that appear in a single search (for example,… more

   10 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  2 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

2. Polaris 8.1 - Leap Search Filter Returning to Default Search After Return to Search Results

   If you have a search filter saved as a default search (such as assigned branch saved, for example), but temporarily remove it for a search, then open a bib/item record, then go back to the search results, LEAP will go back to your default search with the filter applied instead of the one you just did with the filter removed. This doesn't appear to happen the other way around. If you don't have a filter saved as your default search, but apply one for a search and then go back to search results, your filter will still be present. Is it possible to work the same regardless of your search parameters to go back to the same search you just did?

   If you have a search filter saved as a default search (such as assigned branch saved, for example), but temporarily remove it for a search, then open a bib/item record, then go back to the search results, LEAP will go back to your default search with the filter applied instead of the one you just did with the filter removed. This doesn't appear to happen the other way around. If you don't have a filter saved as your default search, but apply one for a search and then go back to search results, your filter will still be present. Is… more

   6 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  0 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

3. Polaris 8.1 - Leap Find Tool Window Expansion

   It would be nice if the Leap Find Tool window could be enlarged to full screen.

   •  

   43 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  5 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

4. Polaris 8.1 - Support Custom TOMs / TOM Override

   While there are many advantages to way that Polaris calculates TOMs, there are currently some significant limitations for differentiating between formats. 4K BluRays, Playaways/Yotos, and video game systems are all very difficult to distinguish from one another when using only the MARC fixed fields. Additionally, many libraries are expanding their collections with Libraries of Things that are usually coded as "Kit" or "Three Dimensional Object" rather than describing what it actually is. These bib TOMS are also now featured prominently in Vega Discover's rollups.

   Over on the Sierra side, the options for bibliographic format can be customized. If a library wants to add a specific format, they can add those options to a drop-down list. This approach wouldn't transfer over to Polaris perfectly, but it could lead to a hybrid system where Polaris still calculates TOMs, but certain conditions would allow a custom TOM to be used in place of the calculated one.

   There are a couple different ways that this could potentially work, but I'm currently leaning towards something like a TOM override drop down box that is configured in SA and displays in the bibliographic record. When an option is selected, the bib's Primary TOM will be them term that is selected. If it's left blank, Polaris will calculate the TOM as normal. Since it's configured in SA, libraries will still be able to control the terminology used and can supply the necessary format icons in the PAC files. Ideally, when records are exported, this gets converted to a MARC tag so that it can be reimported.

   Other options could be a designated MARC tag that contains specific wording. When the TOM is calculated, the system will look within this MARC tag just as it looks in the fixed fields. Another option could be some kind of calculated logic that determines custom TOMs based on the attached item's Material Types. ("If all items are X then display Bib as Y").

   Polaris' current approach for TOMs works really well for traditional library items because that info is readily available in the MARC fixed fields. But this process starts to break down with newer, non-traditional library items that MARC does not account for. And now with Vega Discover, the format rollups (arguably the most popular feature) highlight many of these issues that we've been ignoring.

   While there are many advantages to way that Polaris calculates TOMs, there are currently some significant limitations for differentiating between formats. 4K BluRays, Playaways/Yotos, and video game systems are all very difficult to distinguish from one another when using only the MARC fixed fields. Additionally, many libraries are expanding their collections with Libraries of Things that are usually coded as "Kit" or "Three Dimensional Object" rather than describing what it actually is. These bib TOMS are also now featured prominently in Vega Discover's rollups.

   Over on the Sierra side, the options for bibliographic format can be customized. If a library… more

   134 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  14 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

5. Polaris 7.6 - Adhoc item bulk change from find tool and bib record

   Support the ability to perform adhoc bulk change on item records from the item record find tool and bibliographic record items view.

   19 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  1 comment  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

6. Polaris 7.7 - OAI-PMH harvesting from Polaris to Trove

   OAI-PMH harvesting from Polaris to Trove, now that this is in process for sierra we would like to see this for Polaris.

   3 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  0 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

7. Polaris 7.7/7.8 - Duplicate detection as separate action for bibs and authorities in Leap

   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.

   43 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  1 comment  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

8. Polaris 7.7 - View recent search history in Leap find tool

   It would be great to have an option to go back and view recent search history or search results in the find tool in Leap. I often close out of a search too soon and realize I need to go back for more information, or realize that I actually had the results I needed two searches ago.
   Being able to quickly view recent search results rather than constructing the whole search again would save a lot of time.

   82 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  5 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

9. Polaris 7.6 - Add ISBN to columns in Leap find tool for bibliographic and item record searches

   Our Collection Development librarians would like to be able to quickly look down the list of bibliographic and item search results and see ISBNs. Right now, this is not available as a column so they have to click on each record and open it to see the ISBN.
   If there are multiple ISBNs in a record, the find tool could just display the first one.
   This would save our Collection Development staff a lot of time in their searches.

   35 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   COMPLETED  ·  2 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

10. Polaris 7.7 - Improve selecting and record set functionality in Leap

    In the same way that you can bulk select multiple non-sequential emails in web email services and right click to take action, Leap should allow users more flexibility to bulk select records to be added to a record set. This is something that is useful in the windows staff client and should be available in the web Leap interface. Also, please add a Load All option at the top of Leap retrieval/record sets to take place of the karate chop, instead of having to scroll to the bottom of the results to access the Load More button.

    Idea Value
    Improves Leap's utility for collection maintenance, reducing tendency of staff to revert to staff client.

    In the same way that you can bulk select multiple non-sequential emails in web email services and right click to take action, Leap should allow users more flexibility to bulk select records to be added to a record set. This is something that is useful in the windows staff client and should be available in the web Leap interface. Also, please add a Load All option at the top of Leap retrieval/record sets to take place of the karate chop, instead of having to scroll to the bottom of the results to access the Load More button.

    Idea Value
    Improves… more

    69 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    COMPLETED  ·  2 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

11. Polaris 7.6 - Improve efficiency for editing bib records in Leap

    We just updated to 7.0 and now have the ability to edit bib records in Leap. However, we have found that we need to click a box and then a button in order to edit a field, and then make edits. In addition, it's not possible (as far as I have found), to change the actual tag, only the contents of the field.
    Efficiency of Leap cataloging would be improved by allowing in-line editing as is done in the client.
    If the concern is that leaving it open to in-line editing would result in more errors, more changes that aren't intended, include a single Edit button for the entire record.

    Idea Value
    Having to click a box then click a button to edit a field, or having to create an entirely new field to change a tag, then delete the old field are significant hits to cataloging efficiency. I really want my staff to use Leap cataloging, but that won't happen as long as their work is more efficient in the client.

    We just updated to 7.0 and now have the ability to edit bib records in Leap. However, we have found that we need to click a box and then a button in order to edit a field, and then make edits. In addition, it's not possible (as far as I have found), to change the actual tag, only the contents of the field.
    Efficiency of Leap cataloging would be improved by allowing in-line editing as is done in the client.
    If the concern is that leaving it open to in-line editing would result in more errors, more changes that aren't… more

    49 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    COMPLETED  ·  4 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

12. Polaris 8.0 - Fix the Leap Bibliographic Find Tool Search to use Initial Articles like the Polaris Client

    Currently in Leap there is no equivalent Bibliographic Title search to the "Exact match (implicitly truncated)" in the Polaris Client. The Leap search "Bibliographic>BasicSearch>Title>Exact ()" doesn't utilize the Initial Articles entries in the Bib record so any title search with a "The" or "A" or "An" in the title are not returned in the search results. This has caused a push back to adoption since the very real perception is that Leap has inferior search capabilities. I'm not sure why the the "Bib Exact ()" search requires staff to strip out the A, An & The initial article to return results when that hasn't been the standard method of searching in the Polaris Client.

    Idea Value
    To provide a Bibliographic Title search in Leap that is equivalent to the extremely functional "Exact match (implicitly truncated)" that has been in the Polaris Client. This is needed to remove the obstacle for staff to implement Leap. Having to retrain all staff to drop the initial article to achieve a successful title search just doesn't make sense to me. Currently there is no client parity in this area.

    Currently in Leap there is no equivalent Bibliographic Title search to the "Exact match (implicitly truncated)" in the Polaris Client. The Leap search "Bibliographic>BasicSearch>Title>Exact ()" doesn't utilize the Initial Articles entries in the Bib record so any title search with a "The" or "A" or "An" in the title are not returned in the search results. This has caused a push back to adoption since the very real perception is that Leap has inferior search capabilities. I'm not sure why the the "Bib Exact ()" search requires staff to strip out the A, An & The initial article… more

    74 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    COMPLETED  ·  7 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →

13. Polaris 7.7 - Ability to select multiple items/chunks of items in LEAP

    When working with a list of bibs, items or patrons, ability use ctrl and shift keys to select a chunk of sorted records (without having to checkmark each item) to add them to a record set. If other web tools like gmail can do this for email deletions, it seems we could do this with LEAP too.

    Idea Value
    Saves time.

    85 votes

    Vote Vote Vote Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    Vote

    We’ll send you updates on this idea

    COMPLETED  ·  4 comments  ·  Cataloging & Metadata Management  ·  Delete…  ·  Admin →