49 results found

1. 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

   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 →

2. Polaris 7.8 - Improve Receipt Printing from Leap

   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.

   86 votes

   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  ·  15 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →

3. Polaris 7.7 - Provide a Load All option for record sets in Leap

   I cannot think of a situation where, if I have a record set containing more than 250 items, it would be okay to proceed with doing things in that record set without loading in all of the items. It is typical to need to take a similar action on all items in large record sets but very challenging due to the 250 at a time limit. I just had to scroll and click more 27 times before I could embark on a bulk change. There should be a load all button.

   8 votes

   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  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →

4. Polaris 8.0 - Dated patron notes

   It would be very useful for patron notes to automatically include date and time - this would allow us to track "updates" to progressive situations with patrons that multiple staff are addressing.

   102 votes

   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  ·  11 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →

5. Polaris 7.8 - Duplicate detection action on PO in LEAP

   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.

   19 votes

   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  ·  Acquisitions, Serials & Inventory Management  ·  Delete…  ·  Admin →

6. 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

   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 →

7. Polaris 7.6 - Printing workslips in Leap

   Please add the ability to print workslips for purchase order line items in Leap. Right now they can only be printed in Polaris client. Our Acquisitions staff would love to be able to do everything in Leap, rather than having to switch back to the client to print workslips.

   • 

   28 votes

   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  ·  6 comments  ·  Acquisitions, Serials & Inventory 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

   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

   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 - Enter tax and discounts on invoices as an amount rather than a percentage in LEAP

    In the Polaris client, we have the ability to enter taxes and discounts on invoices as a dollar amount. In Leap there is no way to do this and taxes and discounts can only be entered as a percentage. Many of our vendors list taxes and discounts as a dollar amount on the invoice, it would be much simpler to be able to enter in those numbers directly rather than trying to calculate the correct percentage. Our Acquisitions staff have been entering and paying invoices in Polaris client rather than in Leap solely for this reason.

    This would save our Acquisitions staff time and allow them to use Leap to enter invoices.

    In the Polaris client, we have the ability to enter taxes and discounts on invoices as a dollar amount. In Leap there is no way to do this and taxes and discounts can only be entered as a percentage. Many of our vendors list taxes and discounts as a dollar amount on the invoice, it would be much simpler to be able to enter in those numbers directly rather than trying to calculate the correct percentage. Our Acquisitions staff have been entering and paying invoices in Polaris client rather than in Leap solely for this reason.

    This would save our… more

    20 votes

    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  ·  Acquisitions, Serials & Inventory Management  ·  Delete…  ·  Admin →

11. 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

    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 →

12. Polaris 7.7 - Accessibility Shortcuts in Leap

    Many of the keyboard shortcuts that are in the Polaris client are not found in Leap. This is harder for people with difficulties switching between the keyboard and mouse. We have a user who would love to have access to these keyboard shortcuts in leap that, if turned on or added, would make Leap linking much more intuitive and ergonomic.

    The staff member said:

    • Ctrl-S would be fantastic
    • A shortcut to simply close a record, as exists in the form of Alt-F4 in Polaris.

    Those are the big ones.

    Any others that can be turned on or created specifically for entering and navigating the "Actions" > "Create Item" path, like those buttons themselves, would be very gratefully appreciated.

    Idea Value
    The value of this idea would be improving accessibility and usability of leap for those that may be accustomed to keyboard work and have limitations with the mouse

    Many of the keyboard shortcuts that are in the Polaris client are not found in Leap. This is harder for people with difficulties switching between the keyboard and mouse. We have a user who would love to have access to these keyboard shortcuts in leap that, if turned on or added, would make Leap linking much more intuitive and ergonomic.

    The staff member said:

    • Ctrl-S would be fantastic
    • A shortcut to simply close a record, as exists in the form of Alt-F4 in Polaris.

    Those are the big ones.

    Any others that can be turned on or created specifically for… more

    69 votes

    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  ·  6 comments  ·  System Administration & APIs  ·  Delete…  ·  Admin →

13. Polaris 7.6 - On Order status available in Item Bulk Change

    Make On Order an item status that can be bulk changed.

    Idea Value
    This would increase efficiency of staff working on acquisitions database management. Daily, we have On Order items that need to be changed to In Processing.

    34 votes

    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  ·  Acquisitions, Serials & Inventory Management  ·  Delete…  ·  Admin →

14. Polaris 8.0 - Web Admin - PAPI Key Management Permissions

    With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).

    We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in the future, and moving admin activities from the client to the web.

    There should be more granular, PAPI Key Management-specific permissions, so that only appropriate users can access or change these, not anyone with admin access.

    Idea Value
    For customers who use API keys, and also give some staff access to system administration functions, this is likely to be a security gap, and may prevent them from moving all staff functions off the client.

    With 7.1, Polaris administrative settings can now be accessed on the web, which includes PAPI Key Management. However, the PAPI keys can be accessed and changed today by anyone with the permission 'Access Administration - Allow' (which gives basic access to system admin settings).

    We give some of our staff access to admin settings, for activities like adding workstations and updating branch hours. As it stands these users can access and change the API settings through web-admin, but they should be secured so only systems administrators have access. This will be barrier for us sharing web-admin with our staff in… more

    16 votes

    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  ·  9 comments  ·  Discovery & OPAC  ·  Delete…  ·  Admin →

15. Polaris 7.8 - Improve Student/Patron Import

    The Problem

    At best, the method and workflow used to bulk import patrons into Polaris (often referred to as student import) is archaic. The Polaris documentation for this process, Importing Student Records as Patron Records, is 19 pages long and seven of those pages are definitions and descriptions for the format of a pipe delimited file. This file contains 65 separate columns, all of which must be included in the file even if they contain no information. The documentation defines at least three columns that you should not populate… so why are they there? You can obtain a sample Excel file so long as you have access to the Supportal.

    After you've populated this spreadsheet you'll need to convert it to PSV and add another and completely separate line above the patron data that specifies the number 1 (Why?), the time, the date, a branch ID, a user ID, a workstation ID, and the version and build of your Polaris system. (Incidentally, the documentation doesn't specify that last bit, you only find out about it in another Supportal post. The documentation says you should end the top line with the number 20. Again, why?) After you do all of that, rename the file in a very special way and change the extension to TRN before putting it in a very special location on your workstation or server. Finally, initiate the import via… the BookMobile?

    Meanwhile, with Koha, you can obtain a starter CSV from within the ILS itself, and import the patrons through a patron import workform. Their patron import documentation comes out to just over two pages and 554 words.

    I apologize for the rant, but I want to stress the length, the tedium, the potential for error, and the brokenness of the Polaris process. As it stands right now, it's almost impossible for anyone other than an ILS administrator to handle patron imports.

    Ideas to Fix the Problem

    Basic changes that would go a long way:

    • Change the import file to CSV.
    • Simplify the CSV to remove columns that shouldn't be used.
    • Add patron import to Leap.
    • Offer the sample CSV within Leap.
    • Create an import process that asks for the information in the leader of a TRN file, but defaults to the current time, date, branch ID, workstation ID, and user ID.
    • This import workform should be separate from the BookMobile functionality.

    Idea Value
    Every year, right around the time I'm submitting this idea, Polaris libraries across the United States are importing large amounts of students into their systems. The process for doing so is meticulous, yet it's also error prone and convoluted. That's not the kind of system you need when you're adding hundreds or thousands of new patrons into your system. The PSV format of the TRN file practically guarantees that you're going to have to make at least one or two file conversions when you obtain data from a separate entity, such as a school. Switching to CSV helps ensure a closer interoperability between database types and product vendors so the potential for error is greatly reduced.

    The Problem

    At best, the method and workflow used to bulk import patrons into Polaris (often referred to as student import) is archaic. The Polaris documentation for this process, Importing Student Records as Patron Records, is 19 pages long and seven of those pages are definitions and descriptions for the format of a pipe delimited file. This file contains 65 separate columns, all of which must be included in the file even if they contain no information. The documentation defines at least three columns that you should not populate… so why are they there? You can obtain a sample Excel… more

    53 votes

    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

    1 comment  ·  Customer Relationship & Account Management  ·  Delete…  ·  Admin →
    COMPLETED  ·  AdminSamantha Quell (Admin, Innovative) responded

    An updated student record/patron import option has been added to Polaris 7.8.

16. Polaris 7.7 - Make it possible to create a record set from Saved Reports in Simply Reports

    Currently, when you create a report in Simply Reports and save it for future use, the saved report will allow you to generate a PDF or a spreadsheet file, but will not allow you to request that a record set be created. You can only create a record set by recreating the report from scratch in the Simply Reports interface. We have reports that we run monthly to catch items that are newly assigned to LOST, MISSING, and DAMAGED statuses, and to get a record set that I can work with, I have to run each report from scratch, manually. This is time-consuming and makes mistakes more likely. Please consider adding the capability for saved reports in Simply Reports to generate a new record set when run. Thanks!

    Idea Value
    Time saving, more efficient, more useful

    Currently, when you create a report in Simply Reports and save it for future use, the saved report will allow you to generate a PDF or a spreadsheet file, but will not allow you to request that a record set be created. You can only create a record set by recreating the report from scratch in the Simply Reports interface. We have reports that we run monthly to catch items that are newly assigned to LOST, MISSING, and DAMAGED statuses, and to get a record set that I can work with, I have to run each report from scratch, manually.… more

    62 votes

    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  ·  Reporting & Analytics  ·  Delete…  ·  Admin →

17. Polaris 7.8 - More Hold Routing Sequences

    Add more (optional) Holds Request to Fill Routing Sequence tables.

    Idea Value
    As libraries work together more and more in order to provide the best possible services, it's important that Polaris provide needed flexibility in holds routing. This is especially important for consortia (many of which are growing as independent libraries experience budget crunches and are looking for efficiencies). The current primary/secondary RTF and different grouping options are good, but insufficient as material delivery challenges make moving holds across libraries more costly/difficult (especially if there are large areas involved).

    25 votes

    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  ·  3 comments  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →

18. 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

    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 →

19. Polaris 7.7 - Store item due date in the check-in transaction

    This might be a little specific, but I am proposing that the item due date should be stored as part of the check-in transaction in the Transactions Database in SQL.

    Idea Value
    This seems like a relatively small change to the SQL tables, but it would allow some information to be more easily gathered. For instance, I recently received a question where I was trying to determine if there's any trend in what triggers the return of overdue material (e.g. first/second notice, the bill, or collections). If the due date was included in the check-in transaction, I think I would be able to run a report to see how many days overdue items were returned and draw some conclusions from that. I think this would also be useful for libraries who have recently gone fine free or are considering going fine free.

    This might be a little specific, but I am proposing that the item due date should be stored as part of the check-in transaction in the Transactions Database in SQL.

    Idea Value
    This seems like a relatively small change to the SQL tables, but it would allow some information to be more easily gathered. For instance, I recently received a question where I was trying to determine if there's any trend in what triggers the return of overdue material (e.g. first/second notice, the bill, or collections). If the due date was included in the check-in transaction, I think I would… more

    17 votes

    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  ·  Circulation, Access Services & Fulfillment  ·  Delete…  ·  Admin →

20. 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

    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 →