297 results found
-
Data Exchange > Send PRINT FILE using FTS - Include Login Column
I am often having to clean up/delete files that have been saved/"printed" via FTS File Exchange to Data Exchange (send print files out). I sort by date, clear old ones, but some I am hesitant, may still be needed. It would help immensely if the system identified the login associated with this printed file. Then I'd know who to ask/who owns this file (and who isn't deleting their old files). The login column is used elsewhere in the system (Create Lists, etc.), so would ensure consistency.
1 vote -
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.
4 votes -
Add Export Options to Sierra
There are various reports/files in Sierra that should be exportable to Excel or CSV for manipulation/analysis purposes, similar to our ability to export fines paid or statistical reports from the Statistics function. Candidates include Circulation Overrides (printable view puts each override on 2 lines) and other System Files (from admin app), Group Call Numbers (from Sierra 6.6), and really any sort of table or parameter that consists of columns/rows (branch table, patron type, etc.). This would save the effort of copying/pasting and attempting to fix in Excel.
4 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 | MANUAL2 votes -
Create Lists - Ability to track how many times an item has been checked out from its home library
We'd like to be able to track how many times an item was checked out to our patrons vs patrons from other libraries.
4 votes -
macros
Add additional macro modifiers in Sierra.
The 6.3 update removed the Control + F1 modifier macro. Can we consider adding more modifiers such as left/right control, left/right alt, and left/right shift keys?
Thank you!
2 votes -
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.
3 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.
11 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…
19 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…
7 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.
3 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.5 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.
10 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…4 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…
11 votes
- Don't see your idea?