253 results found
-
Allow for creation of new item records in Global Update
In Global Update, it would be very useful and time saving to be able to attach item records there in a big batch to review files.
My library adds items with an internet location for print records we also have online access to. Going into hundreds of individual records to attach the same thing repeatedly takes up so much time.
We can add multiple items to an individual bib record and scanning in one barcode in the attach multiple items window allows the other barcodes being added to follow the numbering pattern. Can this similar concept/function be applied to Global…
9 votes -
Add ability to group itypes into categories in the new patron checkout limit table
With the new patron checkout limit table, we lost the ability to group itypes into a category if we want to use the other limits like library location. We need to be able to either group itypes in the new patron checkout limit table, or use a combination of the old table and the new. We really need the new library location limiter in the new table so that our ptype 30 can only checkout items at our offsite kiosk and no other library, but we now lose the ability to still group our itypes into categories. Our itypes are…
31 votes -
Add index selector and pre-search limits to Check Out (Circulation Desk) Function
This idea is expanding on one originally proposed here by Catherine Kelso (https://ideas.iii.com/forums/951745/suggestions/47046682).
It would be helpful to more easily search on patron record indexes besides barcode when you need to (name, record number, e-mail, etc...) and for those sorts of searches it would be helpful to limit the search preemptively as you can in other search functions throughout Sierra. Say you want to search for the "Smith, John" with a teen ptype and a home library of anytown branch.
The current default search of entering a barcode should remain, it should just be simple to toggle to…
11 votes -
Make Additional PCODEs Available
Libraries are increasingly looking at ways to gather metrics on patrons without identifying them. Data on age, gender, race, or all manner of characteristics might be collected, depending on the library.
I'd like to see Sierra be more accommodating in what it can collect & store on a patron's record, with the introduction of one or more additional PCODEs that can be used to store a significant amount of fixed field codes.
For example, we partner with schools in our service area & offer not only educator cards, but do an upload of student data. Having schools within our service…
14 votes -
Extend data retention of accounting transactions in SierraDNA
The accounting transaction tables in SierraDNA allow you to query information you would normally only have access to via a retained posting register. However, it is hardcoded to only retain information for 2 weeks, which isn't enough time to do anything meaningful with that data.
Ideally I'd like to see data for a full fiscal year but if there needs to be a limit for whatever reason, maybe tie it to the related payment history file.
10 votes -
Create Lists: Prevent the hopping or jumping of lists after a sort is applied
Currently, when a staffer goes into Create Lists and sorts the lists using one of the column headers, while scrolling down to locate the appropriate list, Sierra jumps or hops upward thereby losing the staffers place in Create Lists. This idea is to prevent that from happening and to make the default or custom sort in Create Lists stick. This would save staff time and reduce errors as well.
27 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…
12 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.
15 votes -
Split Permissions for Hold Blocks
This is a resubmission of a recently expired idea.
Currently, the ability to override a hold block is governed by permission 92.
A hold might be blocked for a number of reasons. Staff might attempt to place more than the max number of holds allowed for a customer. They might place a hold for a customer on an item they already have checked out, etc.
One scenario especially has been problematic for as long as I can remember:
A patron finds an item on the shelf & takes it to a service point to check out. It turns out that…
8 votes -
Automatically email Manage Holds results to library staff
Have the results of Manage Holds automatically on a regular schedule (ie. each morning).
This would let staff pick holds even if they don't have Sierra open or available. The automated emails could be set up within the Manage Holds function itself, or could be accomplished if Scheduler worked with Manage Holds (right now Scheduler only works with Create Lists and Data Exchange).
10 votes -
Provide full Branches table and full Location code list via Sierra REST API
Today, Sierra’s REST API does not provide a reliable way to retrieve a complete list of location codes (and their names/labels) as defined in Sierra’s Branches table (SDA: Admin > Parameters > General > Branches). This creates friction for discovery-layer implementations and other third-party integrations that require an authoritative, up-to-date list of locations.
Innovative Support shared that “it’s not possible to get a list of all locations using the REST API,” and that the closest option is the branches endpoint, which only returns locations that are linked to entries in the Branch Address table, not a full representation of the…
44 votes -
Max Items A-D, But for the Number of Holds Allowed
This is another resubmission of a recently expired idea that I had first suggested over a decade ago when at another library that was struggling how to balance its combination of branch & research library users & the sort of requests they might make. While no longer there, I still see it as a potentially useful means for staff to develop their request processes & create limits within limits.
What I'd like to see is the ability to not only set a hold threshold, where a Patron Type is allowed x holds, but as is the case for the Max…
7 votes -
Update Print Template Assignment Methodology
After spending over an hour adding new print templates to every login for a new library, I am once again reminded of the inefficiency of the current methodology for assigning print templates to logins.
Idea: Print Templates can be assigned like Permissions for Sierra. They would have their own sidebar, and logins could be added to each print template. That way, it only takes a couple of clicks to add print templates in mass to several logins, rather than clicking into the login, then settings, then print templates, then scrolling to find each print template and set the prompt. This…
26 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…10 votes -
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…
15 votes -
Copy/paste multiple MARC fields simultaneously
When creating a new record for a material, it's sometimes necessary to copy part, but not all, of an existing record. However, there is currently no way to copy/paste multiple MARC fields simultaneously, despite the fact that you can perform similar operations on multiple MARC fields simultaneously like deleting them. This would be especially helpful when needing to copy/paste 336, 337, and 338 as well as various subject fields.
20 votes -
Change the logic for updating the status date change field in the item record
Currently, the item status updated date that is displayed when hovering over the status field in the item record does not update when an item only goes from "available" to "checked out" because the actual status code remains the same "-". These are valid status changes that we want to be able to see. I know that we have the "last checkout" date field, but we want the status updated date to reflect all status changes, including when the item changes from checked out to available and vice versa.
7 votes -
Allow Patrons to Opt-out of Certain Circulation Notices
Many libraries offer mail delivery services for patrons who are unable to visit in person. Currently, when items become available, these patrons receive a standard "ready for pickup" notification, even though their materials will be mailed to them. This creates unnecessary confusion and may lead patrons to believe they need to come to the library.
Providing the option to customize or opt out of specific notifications, such as "Ready for Pickup" alerts for patrons enrolled in mail delivery, would greatly improve clarity and enhance the user experience.
14 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…
11 votes -
Sorting Search/Holds Queries
Staff would like to see the ability to sort results retrieved from queries performed in Sierra's Search/Holds mode.
Say for example they do a keyword search for Star Wars at our Forest Park branch. 124 items are found. The results are displayed alphabetically by default. But if the staff member wants to quickly sort by DVDs, they can't even click on the Format column heading, as it exists currently.
While they can run multiple limits to narrow down the results by format, language, shelving location, publication date, etc., they might just as equally be inclined to SORT the entire list…
12 votes
- Don't see your idea?