258 results found
-
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 -
Send To: Globally Purge Charges
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 Globally Purge Charges.
The state of Ohio has a statute of limitations on debt collection that has us purging money owed longer than 5 years on a weekly basis. While this is bazonkers IMO, apparently it's also the law of the land, & it would make the process much more quick & convenient if we could select a file in Create List, navigate to…
11 votes -
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…
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.
-
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.
-
Track User, Time, and Process for Deleted Records
Currently, when a record is deleted in Sierra, the system captures the date via the deletiondategmt, but it doesn't track the exact time, the specific Sierra user, or the process used to delete it. We would like to see this metadata enhanced to include the Sierra user, a timestamp, and the function or process used (Delete Records, API, etc.), with the date.
Tracking these details is critical for consortium management, system auditing, and data integrity. Having this information readily available would significantly improve our ability to handle targeted staff training when records are deleted in error, investigate the…
10 votes -
Retain Out Location When Renewal Stat group is not zero
Currently, in order to maintain the out loc field in an item record while it is checked out for libraries with auto-renewal, the actual renewal location statistic group number must be zero. This is frustrating as the zero stat group number does not display in reports and we need all renewals to appear in reports. There needs to be a way to retain the out loc in an item record when the renewal stat group number is not zero.
10 votes -
Add timestamp to "Suspended" field in user account
Problem:
Our practice is to suspend user accounts when a staff member leaves, rather than delete it, so that we can copy the necessary permissions when a replacement is hired. We then try to delete the accounts after 6 months, but there is currently no method within the Admin App or SQL that tells you when a login was suspended, so we have to track that manually.
Value: adding a timestamp to this field would enable us to more seamlessly manage user accounts for our large consortia and ensure that unnecessary logins are periodically purged.
10 votes -
Decision Center - physical format/collection sorting
In the settings for code categories (Physical Format and Collection), you can change the display order, but it only applies to that page, not to the option menu users see when building a report.
When creating a report, the list of categories is always alphabetical. There is also a "Sort A-Z" button, which is currently unnecessary (and caused confusion as its existence implies that there could be another way).
I suggest applying the manual display order set in Admin Tools to the "edit" pop-ups in the initial filters of a report.
This would allow us to put more commonly-used categories…
10 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 -
Enable Passkeys for patron authentication
Passkeys are both easier for people to use and safer than using passwords and PINs. Passkeys allows users to sign in to their account using the same mechanism they use to unlock their device - fingerprint, face recognition, etc. There are a couple of good introductions to the benefits of Passkeys over traditional username/password credentials here:
https://fidoalliance.org/passkeys/
https://developers.google.com/identity/passkeys10 votesThe product team will review this idea for consideration for a future release.
-
Paging Queue should recognize changes to the Not Wanted Before Date in Hold record
Sierra queues the hold for paging at the time the hold is placed, based on the data the hold was placed with. If the hold is modified after that (by changing the Not Wanted Before date), those changes don't update the paging queue, and Sierra will continue to page as if the hold had not been modified.
10 votesThe product team will review this idea for consideration for a future release.
-
Improve diacritics in sierra to search Arabic and other Semitic langauges
Improve diacritic searching in Sierra to include Semitic languages, especially Arabic! We have a fair number of Arabic books in out collections, and a large Arabic community, but Sierra support for Arabic characters does not seem complete. We often find that Arabic letters in Sierra is replaced by a white square, which seems to mean that the character is not supported. The names appear fine in Vega but the non supported letters do not seem to be indexed in the search results. This is an important language for members of our community and support for it is important in our…
10 votesThe product team will review this idea for consideration for a future release.
-
Move to Bottom of Group - use marc field instead of field name
Our catalogers would like the option when choosing a field and selecting "Move to Bottom of Group" that it could go to the bottom of the list of numbered tags it is part of instead of the field name of tags. An example is moving a 5xx field to the bottom of a list of other 5xx fields, and not to the bottom of the record if there is an 852 (also a note) field.
10 votesThe product team will review this idea for consideration for a future release.
-
Check Out tabs (check out, checked out items, holds, etc): ability to toggle between tabs in Check Out
Technical Services Staff and Circulation Staff often ask for the ability to toggle between tabs in Check Out. We need to reduce repetitive keyboard strokes at checkout and this workflow requires staff to continually reach for the mouse during a circulation transaction.
For example: There is no way to move from the patron check out screen to the patron holds screen without using the mouse to select the corresponding tab.
The Check Out options (check out, checked, out items, holds, fines, check in, linked patrons, bookings etc) could be hardcoded to the drop down menu options so that Administrators could…
10 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?