239 results found
-
Support SRU (Search/Retrieve by URL) in addition to Z39.50
Sierra supports Z39.50 but not SRU. Remote search and import/overlay of records from SRU-only sources seems to be increasingly important. We have begun to encounter potential partners who are no longer able to offer Z39.50 access because their systems only support SRU; likewise, we would like to be able to offer SRU ourselves to maximize interoperability.
GPL-licensed software is available to add SRU support to Z39.50-capable systems such as Sierra (for example, CQL-Java, yazproxy and metaproxy):
https://www.loc.gov/standards/sru/
https://www.indexdata.com/resources/software/cql-java/
https://www.indexdata.com/resources/software/yazproxy/
https://www.indexdata.com/resources/software/metaproxy/4 votes -
Globally purge charges by itype
Idea: add a limiting feature to Globally Purge Charges that allows for choosing which fines to clear by itype.
We use itypes to delineate lending in addition to the location code. With libraries transitioning to fines-free policies and seeking to waive existing overdue fines for patrons on some items (but not all), the current function structure complicates matters, as it only allows for limiting by location code, rather than by item type. There are ways to work around it but they are cumbersome.
5 votes -
Allow holds on bibs when holdable items are on order
We have a non-holdable lucky day collection whose items are on the same bib as our regular, holdable copies of those titles. Sierra allows patrons to place holds on titles that are on order, but sometimes the non-holdable copies are the first to arrive -- at which point, Sierra sees that all items on the record are non-holdable, and stops allowing holds until the first holdable copies come in.
Innovative recommended splitting nonholdable items onto a separate bib record, which seems liable to clutter up the catalog; moreover, some of these items are likely to be moved into our regular…
33 votesThe product team will review this idea for consideration for a future release.
-
Offer the ability to retain a patron's receipt preference at checkout
At checkout, Circulation Staff must ask patrons at the end of each checkout if they want a printed receipt, email receipt, both, or none, or place a pop-up message on their account. It would be great if there were a way to retain each patron's receipt preference so that upon closing out the patron's record, the preferred receipt would be sent, print, both, or no receipt would be given.
36 votesThe product team will review this idea for consideration for a future release.
-
Send to: Notices
It would be great if the logic & momentum that introduced Send To - Rapid or Global Update in Sierra 6.3 & will soon allow the same shortcut to Delete Items could also be applied to the Notices function.
I had submitted a similar request that the shortcut be added to Globally Purge Charges & am wondering if this might be combined into one request or if it's easier to introduce them one at a time?
Use case: each week, Cincinnati generates a list of customers sent a statement of charges (bill notice) via Create Lists. This list is then…
6 votes -
Disable fine lock
Because our library does not use fines, having the "Failed to acquire fines payment lock. If not cleared, fines payments cannot be processed" message is of no utility for us. We'd love multiple users to be able to view a patron record without this message showing up.
9 votes -
Disallow cancellation of holds by Pickup Location, Loan Rule or Stat Group
It would be helpful to have the ability to prevent a hold from being canceled based on its pickup location.
We have holds pickup lockers installed in three locations and are finding that if the lockers contain an item which has since had its hold canceled, the lockers will send a CheckIn SIP transaction to Sierra for that item, resulting in the item being [logically] used to fulfill someone else's hold [while physically still housed in a locker]. For popular new releases, this is happening more frequently than one might imagine. The ability to disallow the cancellation of holds at…
10 votes -
2038 issue
We use the patron's 18th birthday as their youth card expiration date. Due to the Year 2038 issue we have been unable to add the correct date for several years now. We would really like to be able to have (any/all) date fields updated so we can begin to record accurate future dates again.
29 votesThis will be implemented in Sierra in 2027.
-
Insert/Update Location Codes from a CSV file
Develop a utility to add new location codes to the so-called Branches table using a CSV file as input. Optionally permit updates (overlays) of existing location code entries so that the branch_code_num, name and/or is_public columns may be reassigned values in this way.
Our library has very granular location codes which describe branch (or collection subset of a branch such as a display area), audience, format and genre, loosely speaking. This amounts to 220-250 location codes per branch (or collection subset). We currently have over 5,000 distinct location codes in our Sierra database, and every time a new branch is…
10 votes -
Add search functionality to scoping rule function
As a consortium, our system has hundreds of location codes. We appreciate the new functionality to add locations to scopes ourselves, but it is cumbersome to scroll through the list of hundreds of branch entries each time to find the code you need to add. It would be helpful if there was search functionality, where you can type in the code, and it brings up the corresponding entry in the branches list for you to select.
9 votes -
Create Granular Permissions for Editing Permissions for Select Group of Users
We would like to see more granulated permissions for user administration, especially with assigned permissions, settings, options, workflows, etc.
We would like the ability to assign a particular group of user accounts (e.g., circ student employees) to a specific admin (e.g., head of circulation) without assigning ALL system administration. It would be helpful for troubleshooting and having this department be able to assign macros, specific permissions, and print settings to different accounts.
Ideally, this "group admin" would have the ability to edit settings on accounts for options, settings, and workflows. It would be great if they could clone and create…
9 votes -
Abililty for Sierra's NCIP responder to be able to parse ISBNs
Right now NCIP for Symphony, Voyager, Polaris, Koha and Evergreen all accept ISBNs, but Sierra's does not.
7 votes -
Allow for Customization of Fields Included in Expanded Display of Patron Records
I recently learned that the fields included in the Expanded Display for patron records (when you rollover/click the i next to the record) are hard coded.
I found this unfortunate, because what's shown in the Expanded Display differs depending on where you're viewing it, which in the case of patron records is either going to be in the Search/Find a Patron view or the Check Out mode view.
Examples of where I see room for improvement here:
1) When I search for a patron by name & come up with dozens of people with the same name, an identifier like…
7 votes -
When receiving items, limit search results to orders available for receipt
It would be nice if there was a setting in the Receiving function to limit your search to only items available to be received. We search by PO and have to wade through loads of items already received and billed. This was available years and years ago on the old Horizon system.
13 votesThe product team will review this idea for consideration for a future release.
-
Options Group setting for showing Last Patron
In a consortial setting we have some libraries that would like to avoid showing last patron data for a item in an attempt to avoid retaining data that could be used to breach a patron's privacy.
13 votesThe product team will review this idea for consideration for a future release.
-
Improve server security by supporting Apache module mod_security
With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.
3 votes -
Include periodical issue information in overdue notices
We had a patron complaint that the email notices do not include magazine issue information, only the main title. The notices also do not include item barcodes, so there isn't any data to match against a specific issue. Could information from the Issue field in the item record be displayed in overdue notices?
13 votesThe product team will review this idea for consideration for a future release.
-
Add ability to suppress a subfield in the 1xx
Add the ability to suppress subfield 1 in the 1xx field so it will not show in Sierra. This way it can be unsuppressed when the library starts using linked data.
20 votesThe product team will review this idea for consideration for a future release.
-
Refund Functionality in Sierra
Currently, Sierra does not provide built-in functionality for processing or tracking refunds. While the system records partial payments that result in credits (displayed as negative fines) and waivers applied by staff (visible in Fines Paid), there is no equivalent workflow or tracking for refunds.
We request the addition of a refund tracking feature within the patron record, ensuring that staff can see when a refund has been issued. Specifically, we propose:
A clear refund indicator in the patron record.
A display of refund amounts including payment method in the Fines tab, similar to how fines and waivers are shown.
An…12 votesThe product team will review this idea for consideration for a future release.
-
Deposit Functionality
Ability for patron to add money to their Sierra patron account (via self-check) to pay for future fines, fees, and printing. We are looking to go mostly cashless, but some patrons aren't able to get credit cards (like our young patrons here after school). Our self-check machine takes cash, which would allow patrons to print and pay fees/fines with cash, even if the staff doesn't have a cash register.
7 votes
- Don't see your idea?