295 results found
-
Correct 0 date values in SQL views to NULL values
In circtrans and finespaid views (and maybe more views) there are several dates that are showing a value of 0 (which displays as 1969-12-31 due to UNIX date formatting).
Dates do not have a value of 0, they can however, have a value of NULL, which is already how things work with other dates in the system, like the bib record cataloguingdategmt.
This should be fixed for any dates in the system, not because anyone may or may not vote for it, but because it is both inaccurate and inconsistent.
I logged this as a ticket,…
13 votes -
Allow holds on multiple bibs at the same time from a review file
There are times staff need to place holds on multiple items that are in a review file (we are working on a collection and need to change something about a group of items) and it's time consuming to go item by item. It would be nice to place bulk item holds on items in a review file.
12 votes -
Make pop-up windows remember size and location
When creating a new bib record and using the insert drop-down box, the windows always open in the same place and the same size. If I change the location or size of the window, I have to do it EVERY TIME. This is very annoying. Let me set those parameters and make them permanent for my login.
12 votes -
Improve search relevancy for titles with many adaptations
Our staff have found that when they search the staff catalog for classic titles with lots of adaptations many of the adaptations are ranked higher in the search results than the title they actually searched for. For example, a title search of our catalog for "Moby ****" yields "Ahab's Wife" as the top result, with other derivative works and commentaries all appearing before the first record for the novel itself (in our case, result number 24). We'd like to see the results weight matches on the work's own title (e.g., 245 field) higher than matches in other fields, such as…
12 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 -
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.
-
Release Item Price Field in Sierra Item Record for SIP2
Libraries using SIP2 connections for self-checks cannot have due slips that have "You Saved" information because the Item Price field is not available via SIP2.
While due slips with this information can be used at a staff station with the SDA, as more and more libraries move to self-check, the lack of this field's availability in SIP2 is a barrier.
Use case: a library has a self-check machine that uses SIP2 and wants to include "You Saved" information on their due slips.
12 votes -
Allow notices to be sent to e-mail addresses entered in separate fields.
In Sierra we have to add additional e-mail addresses comma separated in the same field for Print template notices to be sent to more than one address.
Right now we are implementing Vega Discover and there patrons can add additional e-mail addresses. They end up in separate e-mail fields in Sierra though and doesn´t work for Print template notices.
The integration built for us between IMMS and Sierra does pick up addresses from all e-mail fields to send out pick up notices for holds.So it would be great if this could also be the case for Print template-notices from…
12 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
allow libraries to customize options for "claim return" workflow
There are 3 options in the "claim return" workflow at checkin.
1) Checkin items (with no fines) and change status to missing.
2) Checkin items (with no fines) and change status to claims returned.
3) Leave items checked out (send overdue notices) and change status to claims returned.We always select #2, but we cannot stop staff from accidentally selecting #3. This is troublesome for us because in the #3 workflow customers get an email overdue notice when they have already told the library they have returned the item - and customers can be quite upset about this.
Is there…
11 votes -
Show pop-up when placing holds on items with special statuses
Sierra SDA allows you to place holds on items with special statuses, and do not show any pop-up window to warn of this circumstance. Currently this is not possible in Sierra for statuses other than 'Library Use Only'.
We would like the system to display a pop-up window when attempting to place a hold on an item with special status, as Sierra SDA does in checkout and checkin procedures.
Thanks.
11 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 -
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.
11 votes -
When placing hold in Search/Holds function, after typing patron's name, include patron i (info) button to help verify account
PROBLEM: When I search for an item via F3 Search/Holds, after finding the desired item and clicking to place the hold, a popup screen appears called "Search for patron." If I don't have the library card number but instead type in a name, and there is only one matching result, there is no way to preview whether that patron account is truly the correct one or not. Plus, for libraries with multiple branches, it is helpful to see the preferred pickup location.
SUGGESTED SOLUTION: in other areas/screens, there is a small i (info) button that one can hover their cursor…
11 votes -
Add an Option to restrict Bibliographic Records within the Sierra System ( specific permission)
Problem:
In the current version of the Sierra system, restricted or sensitive bibliographic records can only be suppressed from the public catalog but remain visible and accessible to catalogers within the system. This visibility creates the risk of accidental editing, publishing, or mishandling of these records, particularly:- Restricted Records: Some records are sensitive or confidential and should not be visible to all catalogers.
Records Under Review: Records undergoing auditing or verification need protection from edits until the review is completed.
Recommendation:
Introduce a feature that allows the System Administrator or Cataloging Supervisor to hide specific bibliographic records within the Sierra…
11 votesThe product team will review this idea for consideration for a future release.
-
Need for "Check-in: Do not fulfill holds" function to only apply to current check-in
Libraries have the option to use "Check-in: Do not fulfill holds". This checks in the item without without fulfilling any holds that are in the hold queue for that item. This item will never appear on a Title or Item paging list unless the item is checked in AGAIN. To be eligible to appear on a Title or Item paging list the item must be checked in a second time.
We need an option to release that restriction. The hold should be unfulfilled only during that specific check-in.
Reasons for this:
1) Our transportation system may be stopped due to…
11 votesThe product team will review this idea for consideration for a future release.
-
OAI-PMH service - suppressed records
As a default suppressed records are not included in the harvest stream. This becomes an issue when a harvested record later becomes suppressed in Sierra as the harvester does not know to remove it from its listings as its omission from the stream does not allow for identification of its suppressed state. I would recommend that the option to include suppressed records should be configurable as a harvest stream level, giving the library the ability to configure the inclusion/exclusion dependent on their business rules.
11 votesThe product team will review this idea for consideration for a future release.
-
Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Allow for Diacritics in E-mail Receipts
We've been exploring new ways that our library, as an institution, can meet the evolving interests of DEI efforts. One very small but meaningful way we thought we might do this is to allow for the inclusion of diacritic characters in customer names in Sierra.
Their inclusion appears as desired on the customer record when created/displayed in Sierra (images dia1 - dia2).
They do not appear to impede searching for the customer by name - the search just ignores them (images dia3 - dia4).
They appear as desired in the name display in the Classic Catalog (image dia5).
They appear…
11 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Protect local-only MARC fields that have a specific subfield coding
There are instances where its appropriate to put in a MARC field in the bibliographic record that only pertains to your local institution and you wouldn't want that field erased if the record was overlaid. If that MARC field was designated a local-note, using a $5 then that field would be "protected".
11 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
- Don't see your idea?