253 results found
-
Improve patron address parser to better map data to the patron_record_address table
Sierra has a mechanism for parsing the free text entered into patron address fields in the client into separate fields for elements such as city/state/postal code that exist in the patronrecordaddress table. Those distinct fields may then be searched in create lists or utilized in SQL queries. However, the algorithm used to parse out those data points is extremely rigid in terms of the data it expects to see and is quite prone to mapping data incorrectly if an address entered into a patron record does not conform to those guidelines.
For one common example in our system…
29 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…
16 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.
4 votes -
Additional macro modifiers in Sierra
Add additional macro modifiers in Sierra.
The 6.3 update removed the Control + F1 modifier macro. Can we consider adding more modifiers such as left/right control, left/right alt, and left/right shift keys?
Thank you!
3 votes -
Improve clear hold functions for integrated systems
When a hold has been cleared or is defunct, the information Sierra provides integrated systems (IMMS for our example) over API is not consistent. In particular, when clear holds is run in Sierra. During clear holds, the item status either remains at ! On holdshelf or changes to another item status. When it remains as !, IMMS sees the hold is still active and does not instruct staff to clear the item from the hold shelf. Daily and weekly processes are needed to update the item records for IMMS to recognise the changes.
Can the clear hold function in Sierra…
16 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.
9 votes -
Rearchitect iiirecord.record_metadata to provide improved audit trail accountability
It is sometimes helpful to see who created, updated or deleted a record. Catmaint provides a lot of detail but doesn't cover many record types. I propose the following solution, which doesn't have particularly burdensome storage requirements:
- Build a many-to-many table with an id primary key column, a timestamp, a code indicating the C-R-U-Uprevious-D record operation and foreign keys linking to record_metadata.id and to iii_user.id.
- Backfill this new table using the available timestamps in record_metadata, catmaint and any other table like catmaint which might provide record edit history.
- Rename record_metadata and drop its four *_gmt timestamp columns. Yes, this creates…
14 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…
14 votes -
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 -
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…21 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 -
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…
27 votesThe product team will review this idea for consideration for a future release.
-
Create a GET API endpoint for circulation transactions
This idea came from a discussion at the IUG2025 Sierra Reporting Forum.
It would be very useful to provide an endpoint to assist with gathering/generating the sorts of circulations statistics that would normally require SQL access. However, the all or nothing nature of SQL permissions is a barrier that prevents many users from being permitted to access those features. With the API on the other hand a user could be limited to simply having read access to an endpoint such as this, along with likely the bib and item endpoints so that they may craft reports without also having to…
26 votesThe product team will review this idea for consideration for a future release.
-
Create a pop-up when you are about to overwrite a review file in create lists.
It is very easy to accidentally overwrite a review file in create lists. There should be a pop-up that asks if you want to overwrite the file so that you know you're doing it.
16 votes -
Block particular bib records from having their URLs checked by use of a suppression code
Block particular bib records from having their URLs checked by use of a suppression code
5 votes -
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 -
Add "max number of overdue items" column to patron block table
Many libraries have eliminated fines and they would like alternative ways to provide an incentive for patrons to return items. We would like the option to block patron circulation based on a Library determined number of overdue items. This rule could be added to the Patron Block table so that libraries could customize rule as necessary.
Idea Value: This new setting would provide an incentive for Customers to return their items.
Idea Value: We don't want to restrict the number of items a Customer can sign out, but want to restrict borrowing after a specific number of overdues.
Idea Value:…
30 votesThe product team will review this idea for consideration for a future release.
-
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 -
Update Expected Format Requirements for Email Variable Length Field
Idea: update the expected format requirements for the email variable-length field to account for modern, non-standard email domains.
Relevance: The prevalence of non-standard email domains is growing. Currently, Sierra accepts some non-standard formats, like .me, but rejects others like .health. This prevents the saving of the patron record and requires that the patron provide another email or change their notice preference.
8 votes
- Don't see your idea?