683 results found
-
Enhanced Data fields in SimplyReports
We would like to have more enhanced data fields within SimplyReports in order to help users create reports that can fit their needs a bit better. For example, we recently ran into an issue where a staff member wanted a field that can indicate status descriptions for Lost/Unpaid or Lost/Accruing. In this case, it was explained that there would need to be a combination of patron account information, item status information and library settings needing to be available in order for this to work. Can possibly looked into for the future?
24 votes -
More granular permissions for deleting items/bibs
In Polaris, a single delete of a bib/item record will result in that record being 'marked for deletion.' It is no longer visible in the PAC, but is still visible in Polaris with a Deleted status. Deleting a record in Deleted status, or what we've termed 'double-delete,' will result in the record being fully purged from the database.
Sometimes, staff will delete a record and go back to it to verify the deletion. They see it's still visible in Polaris (missing the Deleted status) and delete it a second time. This accidental purging results in no longer being able to…
24 votes -
Add Notes to a Hold
Often library staff place requests on specific items and need to follow-up when the item is returned (check condition, re-label, compare copies of title, replace, discard, etc.). Our previous ILS supported a hold notes field that would display the saved note when the item was checked out. This reminded staff of why they had requested the item, or would let another staff member know what needed to be done with the item when the hold was filled. The note would either display as a pop-up or as part of the table of checkout information. The note could be printable if…
24 votes -
Leap auto-formatting in date and postal code fields
The patron birthdate field and postal code field both require correct formatting to save the record. If would be helpful to staff if Leap could have auto-formatting (as many web forms do), e.g. insert the dashes in the birthdate (yyyy-mm-dd) and capitalize and insert the space in the postal code (A1A 1A1).
Adding the calendar date picker back for the birthdate field would also be great, assuming that the issues it used to cause could be resolved.
24 votes -
Bib record conversion from AACR2 to RDA
It would be a real timesaver if Polaris could automatically convert AACR2 records to RDA records upon import. Even if only partial changes could be made, it would be a big help to our catalogers.
24 votes -
Copy to create new INLI in Leap
In Polaris, when you are in an INLI you can click the New button you get the option to Copy Existing Work Form. The new INLI retains some values from the existing one (e.g. fund, title, author).
In LEAP you need to exit the INLI, and then click the New Line Item button, which does not fill in any of the information. Makes adding line items slower and more repetitive when you need to re-enter everything.24 votes -
Remove Branch Requirement from Patron Bulk Change
Allow bulk change to all fields in the bulk change workform when the record set contains patrons from more than one registered branch. Currently, the system requires that a single registration branch must be applied to the patron records before changing the patron code and/or the library assigned blocks. These values are set at the branch level; however, most libraries use consistent patron codes and blocks across branches.
This was previously submitted in the old enhancement process:
"Bulk changing a patron code requires the selection of a registered branch. We request that this requirement be suppressed if all branches can…
24 votes -
Suppress Deleted Items from Staff View
With the option to retain deleted item records, results for staff can become cluttered with items that are no longer available. If we could suppress the display of "Deleted" items list on a bib (similarly to the suppression of "Discard" status items in the OPAC) this would allow us to retain item details for historical/statistical purposes without inconveniencing staff. It would be useful to suppress bibs where all items are deleted as well, but I can understand if that would need to be spun off into separate development.
This could be done as a setting, so that they don't surface…
23 votes -
Send patrons a notification when holds go into Not Supplied status
Unless patrons are regularly monitoring their account (some don't even do this at all) they would have no idea when their holds go into Not Supplied status. Having a notification for this would alert them to take some sort of action (try to reactivate if possible, order another edition/version, contact the library for other options).
23 votes -
View Pending Holds For Pickup at Other Libraries in Request Manager in Leap
Currently, the only way to view pending holds for pickup at other libraries in Request Manager is in the Polaris Client. We would like this brought over to Leap. This idea would make the Request Manager in Leap and the client equal in terms of capabilities.
23 votes -
Validate controlled thesauri (650 or 655 _7 $2)
Adding the $2 validation opens the door to using so many controlled thesauri, like Spanish headings via Queens and National Library of Spain, OLAC's video game headings, Homosaurus' headings, and many more that would make searching easier for customers and staff by providing access points that mimic how they talk about their interests and information needs.
It would be a step closer towards inclusion by using various existing vocabularies that institutions want to use, unlock more potential of the ILS, as well as improve authority maintenance overall.
23 votes -
Increased reporting ability in SimplyReports
Details on items going in-transit, enroute, and/or transferred are not kept within the Polaris Transactions database. Instead, the data is only kept within the Polaris database. This means if an item is deleted, then statistics on it going in-transit/transferred/enroute are lost. The enhancement request here would be to include that information into the Polaris Transactions database.
This could also serve as a generic enhancement request for increased reporting abilities within Simply Reports. It seems there are a lot of things our libraries would like reports on that are not possible to create within Simply Reports. It almost always involves historical…
23 votes -
Restrict hold pickup areas by material type
Allow each library to specify specific material types(?) to not be allowed to be picked up in certain pickup areas. Example would be a wi-fi hotspot not being allowed to be picked up in a locker.
23 votes -
Display more previous borrowers on item circulation view
On an item record, you can currently only see the information about the current borrower and the most recent previous borrower. This should be increased to at least 3, so that in the case of a question about condition or missing parts, we have more than 1 patron we can ask.
23 votes -
Increase functionality of API with Overdrive
We would like to see additional information and functions available in the Polaris Client or LEAP so that staff have more resources and information to support customers with questions about online resources.
For example, library staff would benefit from seeing real-time hold information in Polaris about items on Overdrive or Hoopla. Currently, Polaris shows an asterix (*) under holds. Library staff need to either go to the PAC or Overdrive to provide customers with this information. It would help library staff to have information available in one place rather than requiring staff to go to multiple sources to answer a…
23 votes -
Purchase requests / Patron driven acquisitions
Provide a way for patrons to request materials that can become part of the holds workflow.
23 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).
23 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!!
-
Custom cover images should show up in Leap
We use ChiliFresh as a source for cover images and we also use their service to upload custom images for missing covers, kits, etc. After the MARC record is updated with the custom image tag, the new image shows up in the PowerPAC immediately. However, it never shows up in Leap. Leap is already pulling images from ChiliFresh (as well as other sources) for the cover images in Leap's item and bib records. It's really weird that it doesn't pull from the same source to get the custom image attached to the record.
22 votes -
Checkin Lost Item as Damaged
If an item has a "lost" status, and is returned damaged we are unable to change the status to "damaged" via the check-in damaged option (must be in/out for damaged check-in to be used). This would be helpful for situations where the patron returns an item that was declared lost (either automatically by being +30 days overdue or manually) and then later found and returned to the library via drop box, to be able to demonstrate the item was returned damaged with no previous poor condition notes on the item.
22 votes -
Option to suppress more fields in patron registration
For our system, having both an expiration date and an address check date is redundant, and staff constantly fail to update the address check date to match the expiration date. I'd like to have the ability to suppress the address check date as well as other fields, such as street address lines 1 and 2.
22 votes
- Don't see your idea?