239 results found
-
A "full Payment History file" event should log an error to the Admin App's System Messages log
Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.
Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged,…
15 votes -
Add an API endpoint which permits writing to review files
Currently, when a query is beyond the capabilities of Create Lists, it is usually possible to use a SQL query with Python to produce a report. Such a report might list record numbers of bibs/items/orders/patrons/etc which bear further examination and correction by library staff, but staff must copy record numbers or barcodes in the report and paste them into the SDA to pull up the records in question. It would be much easier if an API endpoint permitted those record numbers to be written to a review file so staff can go through them one-by-one in the SDA.
Another use…
11 votes -
Add the ability to search for more fields for volumes in create lists other than just holds.
The only option in create lists for volumes is to find holds. It would be helpful to be able to search for volumes that 'match' or 'has' variable fields. Then we could search for volumes that say 2024, for example. It would also be helpful to have this in Global Update as well when toggling to variable fields.
2 votes -
Include authorities in the Search/Holds module
It'd be great if authority records and cross references were included under the Search/Holds module and be the same as what staff encounter with the Catalog module. Right now it is different. In our system, staff often use Sierra to place holds with the public on their behalf. It would be great if authorities were available in the Search/Holds module results display so that staff could benefit from the information.
If a staffer did an author search and they had a pen name (Robb, J.D.) then they'd be redirected to see the other author's name (Roberts, Nora).... Or they may…20 votes -
Add a Stat Group When Creating a Patron API Key for Vendors
This proposal suggests enhancing the Patron API key creation process by incorporating a Stat Group field, allowing staff to categorize API keys by vendor and track their usage using existing reporting tools. The proposed enhancement would modify the API key creation window to include an optional Stat Group field towards the bottom. If left blank, the default stat group (zero) would be assigned, maintaining current functionality. This change addresses a common issue where vendors do not implement the stat group provided by the library, often resulting in API-driven transactions being categorized under stat group 0. This leads to inaccurate or…
26 votesThe product team will review this idea for consideration for a future release.
-
Translate item status and OPAC message codes in Summary View
Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.
5 votes -
Warning at Hold Placement for Homebound Patrons
Description:
Sierra’s “Check Reading History During Homebound Checkout” feature is very helpful, but many homebound materials in our workflow are supplied through holds from other branches. At the hold placement stage, no warning is shown if the patron has previously borrowed the same title, which leads to unnecessary requests and inter-branch transfers.Requested enhancement:
Add an option to display a warning when a hold is placed for a homebound patron if their Reading History shows a previous checkout of the same item or another item attached to the same bibliographic record.Benefits:
- Avoids unnecessary item movement
- Saves staff…6 votes -
Generate a Hold Cancellation notice when clearing Expired/Defunct Holds
Currently, only when you cancel a hold from either the Hold tab or the Hold queue do you get the option to generate a hold cancellation notice. When a defunct hold is cleared from the holdshelf (clear expired holds), we would like to see a prompt to send a hold cancellation notice(s), just as we do when cancelling holds outside of the clear holdshelf process. All those that get cleared could use the same “drop hold” message in the text of circulation notices (explaining your hold has been cancelled because it’s expired/hold pickup by date has passed). These would be…
12 votes -
innovative_footer
The Innovative_Footer token for webopac does not have any CSS styles or identifiers associated with it so that it can be controlled through stylesheets. The footer is inappropriately placed on our website due to this lack of control.
Propose adding identifiers to the underlying HTML code so that it can be styled properly. Replace its <span> tag with a <div> tag might be appropriate.
3 votes -
Add 'Previous' button to Receiving
Staff are really appreciating the addition of a 'Previous' button to the record creation process which allows them to back up and fix a mistake without having to go all the way through the process before returning to make a correction. Staff would like to see similar functionality within the Receiving process. We receive using the process that combines creating the item with receiving.
Currently, for receiving an item, it will prompt you through the boxes to fill in the required information. As you proceed through, if you make a mistake or skip something you have to cancel and start…
12 votes -
Use a suppression code to block particular bib records from running through a Headings Report
Considerable time would be saved if bib records suppressed from public display (by way of a suppression code) were not included in the Headings Report. These bib records are typically from electronic sets or batches that amount to hundreds of records, some with several headings for each record.
7 votes -
Passing the UPC Code
When an item lacks an ISBN in the 020 field (DVDs and CDs only generally have UPCs in the 024 field) the cover image is very much hit or miss. Syndetics has been contacted, however, it appears that Sierra needs to "pass the UPC code” in order for this to work. This addition would be helpful.
37 votesThis idea will be included in the Sierra November 2026 release (v6.7).
-
Automatic SSL Certificate Renewal
Keeping our systems secure with SSL certificates is essential. Certificates need to be renewed and there is a service commitment to handle this process. But there is a better way. SSL providers can be setup to automatically renew and deliver an updated SSL certificate to our systems when their expiration time approaches.
This idea is for Innovative to support software-only site with setting up an automatic SSL renewal process thereby keeping our systems safe from expiring certificates and making the process worry-free.
26 votesSelected for the Sierra 6.7 release by MEEP enhancement process
-
Title Priority Paging Optional Feature Compatibility
Problem:
Currently, the "Prioritize Paging Open Locations First" feature and the "Prioritize Hold Fulfillment at the Pickup Location" feature for Title Priority Paging are incompatible. When you have both turned on, pages will skip closed locations and page at an open location, but will not allow the hold to be filled because there is a copy available at the hold pickup location. However, the hold pickup location is not paged for that item since paging skipped that location, so they don't see that patrons are waiting. This causes staff confusion and also impacts how quickly a patron can receive their…
7 votes -
Additional patron block controls
Additional options for patron blocks would be amazing and allow additional control for libraries to select what integrated systems or circulation services are available. e.g. Block self-service options in the library (SIP2 or API), however, allow holds to be placed through discovery layers.
The controls don't have to be limited to this. Adding the functions and options to select how these are applied from Sierra, rather than relying on integrated systems to control this would be great.
6 votes -
Restart a Range of Sessions/Processes in Admin App
Sierra 6.5 saw the move of the process for restarting terminal sessions from our text-based management tool to the Sierra Admin App. While I'm chuffed enough about that to be writing this enhancement idea on Thanksgiving Day (and to be using the word chuffed), I'm hoping further development can make it even better & restore some of the functionality from the admin app that isn't available in this updated interface.
Specifically, I'd like to be able to restart a range of terminals (for example, all staff sessions), mirroring the Restart Multiple Terminals option in text-based. Yes, we can check a…
4 votes -
Add pull date to ILL record
Add a field to ILL records that includes the hold pull date. This information is in the ILL clear hold shelf report, so the system has the information. It does not appear in the ILL record and therefore cannot print on the hold slip. Staff need to manually write the date on each hold slip. Other hold slips, including INN-Reach, print a pull date and ILL holds should be able to have this information added to the record for printing purposes.
5 votes -
Show Sequence Number on Repeated Bills
We use the Repeated Bills feature, where after the bill is sent day 30, we send a repeat bill (#2) on day 40 and a final repeat bill (#3) on day 50. Unfortunately, when you run the Notice job for Repeated Bills, there is no way to tell whether the repeat being sent is for day 40 (#2) or day 50 (#3) except if you scroll through all of them and do the math as it pertains to the item status date. Staff haven't been doing that regularly. Ideally, there would be a column that showed you what # of…
4 votes -
Add ability to extend the hold Pickup By date to the /v6/patrons/holds/{holdId} API endpoint
Currently the only hold parameters one can modify via the API are
PatronHoldPut {
pickupLocation (string, optional): the hold's pickup location code,
freeze (boolean, optional): whether the hold should be frozen (suspended)
}It would be very helpful if the Pickup By date – and while you're at it, the Hold Note – were added as modifiable parameters. There have been many times when unscheduled branch closures or problems in sending hold pickup notices have caused us to want to extend hold Pickup By dates for items on the holdshelf.
Having this functionality in an API endpoint would permit a…
16 votes -
Decision Center - Include Series Information in Weeding Reports
When pulling Low Circulation (or High) reports (Collection Tools > Maintenance), would like to include the Series Title (if applicable) in the displayed (and exported) report. We run into titles that have low circs, but if we see it's in a series, we normally don't weed it, because the series should remain complete. Thus we are stuck using Create Lists for this type of information (either exporting the report as a review file and then exporting fields THAT way or simply starting with Create Lists from the get-go). It would be more convenient if it was included in Decision Center.
8 votes
- Don't see your idea?