8 results found
-
"notification status"
Expand NotificationStatusID list/table to include TXT Sent and TXT Failed, plus any additional like TXT Failed - bad phone number
4 votes -
Bib Record Links in LEAP
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 -
(SMS - Cirriusimpact) Allow for Almost Due / Auto-renew to patrons by SMS
Allow patrons to receive Almost Due / Auto-renew messages through the SMS - Cirriusimpact product integration.
12 votes -
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.
79 votes -
API to Update Bibliographic Records
I'm specifically looking for a great integration between the cataloging tool BTCat and Polaris.
Libraries use tools like BTCat and Skyriver to search for new bib records and update/edit existing records. After making changes, the records currently have to be exported from the cataloging software, then imported into Polaris. These tools have the ability to "push" records into other ILS systems, skipping the need for a manual export/import of records. Adding this functionality would aid libraries in transitioning away from the Polaris desktop client (as bibliographic editing in Leap is a tedious process, at best).
20 votesWe actually added an endpoint to support this integration in Polaris 7.6 (BibsPost). We've been working with BTCat to consume the endpoint in their application.
I'm going to set this to "Planned" for now because the integration is not live with BTCat yet. But the development piece required for Polaris has been done. Please let BTCat know you are interested!!
-
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.
17 votes -
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.
39 votes -
Count Renewals Separately- how many patrons actually checked out an item
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…81 votes
- Don't see your idea?