288 results found
-
Set a maximum price allowed for the item price field
I'm blatantly copying this idea from a suggestion by Wes Osborn in the Polaris Idea Exchange (https://ideas.iii.com/forums/951742-ils-polaris/suggestions/46833076).
While creating item records, generally while following prompts in an item template, it is easy for staff to scan a value such as a barcode or ISBN into the price field by mistake, resulting in items that can incur bills in the billions of dollars if the issues are not caught. Additionally, it's easy to miss entering a decimal point and still wind up with charges exponentially higher than intended.
This could be mitigated by setting a maximum allow value for…
8 votes -
Improve the labels for LDR, 006, 007 and 008 in Create Lists
Currently in Create Lists it is very difficult to specify criteria for special fields like the leader, 006, 007 and 008. Many of these have the exact same label, like Audience, which appears four different times. Each of them is for audience as it appears in different versions of the 008 for different record types. Then it appears four more times in the 006.
It would be helpful if each of these different audience codes were labeled in Create Lists, such as "Audience for Books," and "Audience for Music," etc. This would make it much easier to use this function.…
23 votes -
REST API-compatible Time to Holdshelf/Time to Reshelve
Our library has deprecated the classic WebPAC in favor of a REST API-based custom discovery layer, but the Time to Holdshelf/Time to Reshelve temporary status message we've configured isn't included in the API response. It would reduce frustration for staff and patrons if we could implement a delay before items appear to be on the shelf when patrons check our website or mobile app.
Please add the temporary status to the REST API response.
7 votes -
Sierra Patron Address info updates
The Sierra Patron Record is able to be communicated to Vega Discover in such a way that differentiates the following fields:
Street Address Line 1
Street Address Line 2
City
State
Postal Code
Country
Discover does not parse Sierra addresses correctly.
1) New Discover registrations do not parse correctly in Sierra.
2) Existing registrations in Sierra do not parse correctly in Discover.This was the comment by Innovative Staff on this topic:
Discover does have difficulty with parsing Sierra patron addresses, and this is not changing in the July release. For libraries who do allow patrons to edit their own…6 votes -
Restart a Range of Terminals
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…
26 votes -
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”…
8 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 | MANUAL12 votes -
loan rule determiners by agency
It would be nice to be able to choose location agency and leave location blank in the determiner table for some situations. In our case we have 4 partner library systems and one has 7 branches. Each of these branches has the exact same loan rules to allow certain items to circ to the whole consortium, and others to limit to only their system. If we could use agency, we would only have to create one set of those rules instead of one for each branch location prefix (in this case their branches are pri, max, bar,…
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…
6 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.
22 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.
16 votes -
Scheduler: include workflow to schedule/export completed SQL scripts
Scheduler is a powerful tool. Libraries would like to use that tool to schedule SQL scripts. I understand that libraries use 3rd party tools to create SQL statements and then schedule/export/send the results to other 3rd party tools. It would help a lot of libraries that don't have the resources to do this extra setup if a query could be added to scheduler and that query be emailed to one or more individuals in a csv file.
Why do libraries have to use SQL? SQL allows us to query/export/link fields that cannot be queried in Create Lists. Querying the database…
7 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…
17 votes -
Create an API endpoint that delivers language translations to Vega
We maintain English and Te Reo Māori names for library branches and item locations in the Sierra branches table. Making these available through an API would allow Vega to display the correct names automatically, and provide a consistent bilingual experience. This would also remove the need to manage translations separately in Vega Admin.
5 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.
4 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…
5 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.
5 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 -
Improve item title display on patron-facing devices by adjusting SIP2 parameters
Skip certain MARC subfields when preparing data for SIP2 connection.
Specifically:
When Sierra needs to send information to display an item title on a patron-facing device (automated materials handler, self-checkout kiosk, etc.) via SIP2, it currently appears to concatenate all occupied subfields of MARC field 245 and remove the delimiters. This means that certain information not intended to be patron-facing can end up appearing in the title the patron sees on screen (e.g. "880-01 Desu nôto 2..." appearing instead of just "Desu nôto 2...", where "880-01" is not actually part of the title, but rather a reference to another field…4 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…
19 votes
- Don't see your idea?