268 results found
-
Ability to find the most checked out item in a year
Ability to find the most checked out item in a year
Please add a simple way in Sierra to report the most checked out item for a selected year, including the option to show the top five checked out items.
Currently, this is very difficult or impossible to do directly in Sierra because checkout totals are not stored in a way that allows staff to easily rank items by circulation count for a specific year. Create Lists can find items based on fixed fields, item data, and limited transaction-related criteria, but it cannot easily produce a yearly “most checked out”…
7 votes -
Overlay matching should evaluate all repeatable subfields (e.g., every $a in the 019), not just the first occurrence
When a load table's overlay match point targets a repeatable field such as the 019 (OCLC number cross-reference), the load process only compares the first subfield occurrence against Sierra's index. Although Sierra correctly indexes every $a in the 019 individually, the overlay-match routine stops after the first $a. Any additional OCLC numbers stored in the second, third, or subsequent $a subfields are ignored when determining whether an incoming record should overlay an existing one.
As a result, records that should match an existing bib overlay as new duplicates instead, because the matching value lives in a $a other than the…
4 votes -
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…
16 votes -
Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our…
5 votes -
Make Third Party API Transactions More Apparent in Sierra
Some time ago, an idea was submitted to enhance the Sierra API to provide statistical group information, so that circulation transactions in third party applications could be credited to a statistical group other than 0 None.
The idea won the "Let's Connect Sierra API Challenge."
With the release of Sierra 6.0, it then became possible to include a new optional data parameter to specify the statistical group that should be used when recording a transaction performed using the APIs.
My library was excited to hear this, as we'd recently begun using the self-checkout feature in the Bibliocommons' app not long…
5 votes -
YTD Renewals tracker on item records
Similar to the YTDCIRC tracker on item records in Sierra, add a tracker for YTD renewals as well. This would allow collection development staff to quickly assess a more accurate snapshot of an item's usage.
14 votes -
Add process to the details logged in item record history
I was hoping to see the login used to receive the items listed in the Item Record History. If possible, it would be great to see both the user and the process.
Event | user | PROCESS
Created | user | MANUAL
Created | user | RECEIVING
Updated | user | GLOBAL UPDATE
Updated | user | MANUAL10 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.
18 votes -
Add Days Closed Table to SierraDNA
We are interested in being able to tap into the Days closed table programmatically but it is inaccessible to both the APIs and SQL, and doesn't even have a native export feature (though you can copy and paste it easily enough).
Creating a SQL View for it seems the most straightforward solution, just provide access to the existing table, along with row numbers to preserve the ordering.
12 votes -
Separate Summary View properties for each search function
When a Sierra SDA login is created the system utilizes individual summary view properties for the various search functions. By default in cataloging if you open up the summary view of a record you see item records, in search/holds you see holds, in place orders you see orders and in serials checkin you see checkin records.
However, when the staffer changes that setting from the record view properties menu (say to change this to view all), it can impact all 4 search functions. It would be better to split this review view summary option out so it may be set…
4 votes -
include PostgreSQL scheduled patches and upgrades in roadmap and upgrade documents
Sierra 6.6 includes an upgrade to PostgreSQL 16. Innovative should be more specific and tell us that we are upgrading to PostgreSQL 16.10. PostGres 16.14 was the last version in this cycle.
Does Innovative upgrade PostgreSQL with each Sierra upgrade? Will they patch between upgrades with any security fixes?
Libraries need to know Innovative's plans PostgreSQL development, and I am unsure if they are always included in the upgrade notes.
4 votes -
Add "Send to Batch Check-in" Navigation to Create Lists
Building on the recent navigation enhancements that allow users to send Review Files from Create Lists to Rapid Update, Global Update, and Delete Records, we propose adding a "Send to Batch Check-in" option.
Now that Batch Check-in has been integrated into the Sierra client (as of the 6.5 Release), adding this "Send to" functionality would significantly streamline workflows and reduce the risk of errors associated with file handling.
12 votes -
Allow Pickup Location Changes After Hold Is Activated (with Optional Patron Notification)
In Sierra, once a hold is activated, the pickup location becomes locked. This occurs even if an error happens or the original location becomes unavailable. The limitation creates workflow issues for libraries that use lockers, shared delivery systems, or multiple branches.
We are requesting a system enhancement that allows authorized staff to edit the pickup location of a hold after it has been activated, but before it is checked out or expires.
-Why This Is Needed:
Locker and space-based workflows: Staff may discover after trapping a hold that a locker is full or not functioning. At that point, there is…
36 votes -
Add the ability to transfer an item-level hold to the bib level
Please add the ability to transfer an item-level hold to the bib level. In our system, holds automatically attach to an available item. When the item that has captured the hold is unavailable for some reason (ie. the item has gone missing), there is no easy way to deal with the hold if there isn't another available item. You only see the option to transfer the hold to another specific item. If these are all circulating or unavailable and there is a list of holds at the bib level, you cannot currently transfer that item hold back to the bib…
17 votes -
Multiple Notice Preferences
Allow patrons to choose one or more notice preferences. A patron would receive the same notice through any and all channels they want, allowing the library to better serve a variety of needs and lifestyles.
3 votes -
Text/SMS Notice Preference
Please integrate text messaging/SMS as a notice delivery method just like print, phone, and email. Some patrons want texts and no other method. Even if patrons must complete a step outside Sierra, staff should be able to see and choose text as a preference. This would make things more consistent and easy for both patrons and frontline staff.
We had planned to switch to Vega Interact SMS but discovered that it is intrinsically linked to email notices, limiting its ability. We would love to have SMS as a real notice option in Sierra.
4 votes -
Ability to Transfer Bib-Level Holds to Volume-Level Holds
Our consortium would like to request a feature enhancement in Sierra that allows ability to transfer volume-level holds to bib-level holds.
Currently, when we need to move records from a multi-volume bibliographic record (with volume records) to a monographic bibliographic record (without volume records), we must manually add or copy each volume-level hold to the bib-level record and then remove the original volume-level hold. This is a very tedious and time-consuming process, especially within a consortium of more than 100 libraries.
A streamlined method to transfer holds between volume and bibliographic levels would save staff time, reduce errors, and improve…
21 votes -
Indication in ILS of SMS Subscription
We would very much like to see some indication in our ILS (Sierra) that a patron has opted in to receive SMS messages.
Even if SMS Alerts cannot be their own, unique notice type & not just supplement the patron's chosen notice preference of email or phone, the simple activation of a new field would be useful for frontline staff trying to troubleshoot during interactions with the patron.
Even a date/time stamped Note field entry that is applied when Vega Interact SMS first authenticates against the patron's record during the opt-in process would be incredibly helpful, even more so if…
4 votes -
Modify Estimated Price Via Rapid Update
Our Acquisitions staff does not use List Price when ordering, & is hoping that Estimated Price could be modifiable via Rapid Update. At the moment, this would help them modify 200+ order records, which they now have to do manually.
2 votes -
Data Exchange should automatically identify and fix MARC-8 records.
Data Exchange should determine if a file being loaded is in UTF-8 or MARC-8 format before loading. If it is MARC-8, it should be converted to UTF-8 before loading.
I want to be clear that I'm not talking about using the MARC bit that supposedly identifies if the character set is UTF-8. That cannot be trusted. I want a system like the character detect feature in MarcEdit, that will actually look at the characters in the incoming records and determine what character set they really are.
There are still a lot of MARC-8 records out there, and it is not…
11 votes
- Don't see your idea?