291 results found
-
Improvements to Updated Bib Headings report using AACP
When AACP is turned on and we've loaded new / changed authorities, there are some bib records impacted by the authorities' headings which do not get automatically updated and require staff edits. Sometimes it is terminal punctuation that needs to be added for certain entries perhaps tied to a new closed death date; or sometimes it's an indicator in a bib MARC field that should get added because it's in the authority record that's new or changed. We think just a little bit of development here would help save staff time.
2 votes -
Allow patrons to choose to get notifications at both phone and email
We've had patrons requesting to be allowed to choose both notification methods- phone and email, not only one. This would be very useful for patrons whose phones get shut off frequently, or who have another person helping them by picking up their holds for them. Two contact methods would be helpful.
4 votes -
Batch Edit Branches Table
We would like the ability to select multiple, or a range of entries in the Branches table & be able to edit them in batch. For example, making a list of newly available location codes public, or assigning them a Circulation Address Number would be much easier if we could update dozens of entries at once, rather than one at a time.
It would be nice to see this introduced across multiple tables.
2 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…
15 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…
5 votes -
innovative_footer
The Innovative_Footer token for webopac does not have any CSS styles or identifiers associated with it so that it can be controlled through stylesheets. The footer is inappropriately placed on our website due to this lack of control.
Propose adding identifiers to the underlying HTML code so that it can be styled properly. Replace its <span> tag with a <div> tag might be appropriate.
2 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.
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.
8 votes -
Provide In Transit status and print transit slips for ILL items
ILL items- In Transit status and print transit slips
We have three branches and our ILL department is located at one of the branches. We would like the ILL module to change the status to "In-Transit" instead of "Ready for Pickup" and print a transit slip when the items are being sent to two other branches.1 vote -
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.
9 votes -
Permit due date extension via the API
Currently the only way to extend item due dates is to run Rapid Update on a review file of those items. I would like to be able to programmatically update due dates via the API. I see two potential benefits of this feature:
Benefit 1: Rapid Update prompts for a single absolute date to apply to a group of items in a review file. There have been many times when we have wanted to extend the due dates of a group of items by "n days", regardless of their current due date. It would be straightforward to write a Python…
7 votes -
Redirecting Duplicate Copies at Check-In
For libraries using floating collections, the system should support automated redirection of duplicate copies at the point of check-in to other branches that do not currently hold a copy of the title.
The system should surface eligible destination branches automatically, eliminating the need for manual title-level analysis by staff.
In multi-branch library systems, the workflow should allow configurable prioritization rules to determine the destination branch when redistributing items.
Prioritization logic could be applied in the following order:
1) No copy of the title is currently available/on the shelf at the receiving branch
2) Title (or item if not possible) has…3 votes -
Remove leading diacritic from normalised author fields
Sierra currently removes any leading apostrophe for example from the normalised author fields on bibs. For example, normAuthor over API. Other diacritics such as ʻokina (ʻ) is not removed from normalised fields. Because of this, any systems that use norm fields over API are not alphabetising the author correctly.
It would be great if Sierra could remove the ʻokina (ʻ) from the normalised author fields. Specifically normAuthor.
2 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…
9 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.…
8 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…
10 votes -
ID scanner to auto-populate account information
A Sierra feature to allow scanning a Driver’s License to auto-populate customer information for a new account and/or to update an existing account. Automatically inserting a customer's name, date of birth, address, and DL number would result in less typos/mistakes, save considerable staff time when creating or updating an account, and additional staff time in reviewing and fixing errors.
1 vote -
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.
6 votes -
Translate item status and OPAC message codes in Summary View
Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.
4 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…
36 votes
- Don't see your idea?