180 results found
-
Provide indicator/warning when an order record has already been sent to a vendor
In the print/send orders function, it can be easy to accidentally upload an order to a vendor multiple times. As a means to mitigate this error I propose a two part feature.
As a first step, the system should provide some indication when viewing the orders to ftp queue if an order has already been ftp'd once. I could see two methods for accomplishing this. 1) Add a column to the queue display for sent date, taking the most recent date present that has been appended to the ISBN pick field in a record from having been previously sent. 2)…
25 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Ability to update inventory date from "checkin no patron" function
We are needing a way to update the inventory date field when an item is checked-in using the "checkin no patron" function.
When an item that is already in "-" available status, and you check-in the item, there is no field in the item record that records the date of this transaction. We are wanting a checkbox on the screen in that function that when checked, will update the item inventory date so that we can then see the last time that item was scanned.
This will help us with our inventory projects, as we do a full scan of…26 votes -
Introduce a "CANCEL" Button in the "ITEM ALREADY PAID FOR" Warning Popup
In Sierra's invoicing function, when selecting an order record already paid, a pop-up box appears with a warning message stating, "ITEM ALREADY PAID FOR." Currently, the only option available is to click "OK," which immediately proceeds to the next step of entering the item's price on that paid order record. However, adding a button labeled "CANCEL" in the warning pop-up box would be beneficial to prevent staff from inadvertently continuing to pay for the item on the wrong record. Clicking "CANCEL" should close the warning pop-up without proceeding further, returning the user to the search results list. The "CANCEL" option…
16 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Sierra should send an email notification when Offline Files are Uploaded
As the system administrator overseeing a 54-member library consortium, managing Offline File Processing is a routine responsibility. However, we often encounter delays in processing files because libraries don't consistently notify us when they upload offline files. This results in files remaining unprocessed until the next library contacts us, potentially causing unnecessary checkout delays. If we process the files too many days after uploading, additional errors may occur, making it challenging to track items adequately.
An email notification for Offline File Processing would ensure timely handling of uploaded files. We could proactively monitor file uploads, swiftly process them, and promptly address…
15 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Update print templates to support current release of Jaspersoft Studio.
The ability to create custom print templates is an essential component of many parts of the system. LX Starter is a viable replacement for the templates used for notices but not for the printing of things like due slips, spine labels, and hold slips that must remain within the SDA to support daily workflows.
Print templates are designed in a third party software called Jaspersoft Studio, but Sierra's documentation lists version 6.0 as being the last supported version of that software. However, that version is roughly 10 years old and the installer only seems to exist as an old link…
29 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Batch/Copy Option for Patron Record Creation
Someone at CHPL is suffering from Polaris envy & suggested Sierra offer a comparable record to copy/duplicate patron records. They're hoping for a way to speed up the record creation process for families of 5 or 6 that visit the library together & all need to register for cards, which is apparently not an uncommon scenario. The ability to quickly replicate certain fields (address, home library, maybe phone, e-mail, etc.) from one record for x more should facilitate that.
16 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Staff activity log
We occasionally have issues with staff abusing their ability to waive fines or deleting items inappropriately or accessing patron accounts outside of acceptable library operations. We would like to have a way to view these actions within a log file associated with each Sierra login (or filterable by login) so that these activities could be periodically audited by managerial staff and retroactively be reviewed when inappropriate system activities are believed to have taken place.
18 votes -
Allow users to define icode1 in Sierra
Our library uses the icode1 field as a statistical category code. We'd like to be able to define our icode1 values, with codes and labels stored in Sierra and visible to staff. Currently we keep a list of codes and their meanings stored in a shared drive and have to share it with our cataloguers. Staff can see the "stat category" field in item records, but there's no translation anywhere in Sierra and the userdefinedicode1_myuser SQL view is blank.
21 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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…
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Have system-generated review files appear in the drop-down list in Global/Rapid Update
Idea Description
If system generated review files could appear in Global Update/Rapid Update Review File dropdown list without even downloading them to Create Lists first that would save so much time.It's a normal part of my daily workflow to upload records using Mobile Worklists or Data Exchange, copy them into Create Lists and manipulate the file in Global or Rapid Update.
Idea Value
With the file appearing in the dropdown list in Global/Rapid update, the file can be manipulated as usual AND users wouldn't have to remember to empty the Review File (which was only created so it could…29 votes -
Add a Note Field in the RFID Pad Server Options Table
As ILS administrators of a large consortium, we would like the RFID Server Options Table to have an additional field/column to add notes (library name, dates, staff initials). When one of our member libraries needs to change RFID entries, we sort through nearly 200 lines to determine which one needs updating. Many entries use IPs without identifying library information. We must read through old library correspondence to discern which IPs belong to the library. This task takes up valuable time when we are trying to assist a library with troubleshooting or adding and removing entries.
An additional free-text field to…
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Remove duplicate items on paging list
Duplicate instances of a single item frequently appear on Bib Paging Lists resulting in confusion and either wasted paper (up to 7 pages were printed for a single item once) or wasted time deleting those lines before printing. There is no need for the paging list to alert us to multiple holds for any item, especially if we can't physically fulfill those holds.
33 votes -
AI Clean Up Functionality - Sierra
I understand that III is planning to incorporate AI functionality into the Vega platform (newsletter text, website content, etc...). I think it would be really useful to have AI data cleanup functionality developed for Sierra.
I'm not sure exactly what this would look like but here are some potential ways this could improve catalog metadata:
- catalog record cleanup (bad codes, incorrect codes, codes inconsistent with local practices for similar records, etc...)
- patron record cleanup (bad codes, codes inconsistent with similar-type accounts, etc...)
- automatic tagging of demographic (we use one of the patron codes to indicate reciprocal library…8 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Customise font size and other details in Sierra pop-up messages
We'd like the ability to customise the font size of the text in Sierra popup messages i.e, increase font of where items are going to be picked up, or making the destination in the top part of the message stand out? Or removing call number which we do not use.
12 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Option to exclude frozen holds from total holds queue in catalogue
Libraries should have the option to exclude frozen holds from the total holds queue that appears in any catalogue.
Benefits:
1) Customers will have a better idea of where they are in the hold queue.
We encourage customer-driven hold management, and customers have told us that they want an estimate of when their holds will be filled.
This is especially true when customers place multiple hold on titles within a series.2) Customers will not see inflated hold queues and provide feedback to the Library that they should purchase more copies.
3) Customers could make an education decision on whether…
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Ability to change password on login page of SDA
Many libraries are creating individual logins for each staff member. Staff needs the ability to change their password in case they forget it. At this point, they need to be logged into the SDA to change their password which doesn't help if they can't remember it.
12 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add fund code used to purchase item to item record
I was asked recently to create a list of items added to the database based on a fund code. I don't believe that I can do that in Create Lists. This is because order records and item records have no common field to link them.
I also cannot use Create Lists to pivot item records to their attached order records or vice versa.
We need to be able to do this because 1 bibliographic records may have items attached that were purchased from different funds. Example. 1 Fiction title may have items purchased from an ARP (automatice release program), and…
17 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
9 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Release Item Price Field in Sierra Item Record for SIP2
Libraries using SIP2 connections for self-checks cannot have due slips that have "You Saved" information because the Item Price field is not available via SIP2.
While due slips with this information can be used at a staff station with the SDA, as more and more libraries move to self-check, the lack of this field's availability in SIP2 is a barrier.
Use case: a library has a self-check machine that uses SIP2 and wants to include "You Saved" information on their due slips.
9 votes
- Don't see your idea?