275 results found
-
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.
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Order Status rapid update
Rapid or global update to update all Order Status at once.
9 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Allow libraries to customize return addresses for bills
Our library would like the option to have the return address for bills reflect the address of the patron's home library (as defined in the patron record) rather than the owning location of the item. The current setup (using the owning location of the first item on the bill) means that when patrons check out items sent from another branch to fill a hold, they can receive a bill from a library that they may never have been to. While patrons can visit any of our locations to resolve a bill, we would prefer the bill to reflect their local…
5 votesThe product team will review this idea for consideration for a future release.
-
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…
19 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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…
14 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Unfilled Pages Function
Following Disney's lead of recycling years old ideas for theme park attractions, I'd like to see an idea I'd had while working with a former employer brought to fruition in Sierra. We had been using Millennium at the time & the Circ Product Manager had gotten to a point in development that there was a near-working model on III's test environment (I've got screenshots & even a Captivate video somewhere), but I left that employer & the III product manager left III & the idea was abandoned. Sure, it's not as exciting as Disney's announced "Villains Land" or a boat…
5 votesThe product team will review this idea for consideration for a future release.
-
Show recall info in Manage Holds
When using Manage Holds, information about any recalls that have been issued for items on hold is not displayed.
This information can be found by consulting the item record (right click, "Edit item", then open the item) and checking for a "Recall Date" value, but it would be very helpful for us if this information could be included directly in the Manage Holds results. For example, the "Hold Status" column could include indication of recalls to provide a fuller picture of the situation at a glance.
This idea could be incorporated in work on the following related suggestion:
https://ideas.iii.com/forums/951745-ils-sierra/suggestions/48633872-improve-standardize-information-available-when-vie4 votesThe product team will review this idea for consideration for a future release.
-
Update "last checkin" field even if item wasn't checked out
Update the "last checkin" field every time an item is checked in. Now, when you check in an item, the "last checkin" field is not updated if the item is not checked out. I don't know of any reason to not update it. When I look at an item record, I want to know the last date that the item was seen; this can be useful in tracking down items that seem to be missing, or coming up with a list of items that might be missing.
8 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Additional (Staff Only) Message Field In Patron Records
We have been considering enabling the display of the free text Message field in patron records in the WebPac (& a corresponding tab in Bibliocommons). It seems like an easy & useful way to quickly & effectively communicate with customers on issues related to their account.
For example, we might want to create a list of patron records at a library location that is closing for renovation to let them know that for the duration of the closing, their holds will be routed to another nearby branch. We'd apply the message to impacted patron records for as long as it's…
12 votes -
globally update bibliographic records with multiple branch codes
We would like to be able to globally add an additional bibliographic branch code to a subset of bibliographic records harvested through "create lists." This is because currently (Sierra 6.1), it is possible to change a bibliographic branch code, but not add additional ones while retaining the original branch.
The reason is that we have records for electronic resources that should display under a relatively new scope set up for a new branch. With only the original branch in the bibliographic record, it is necessary to view the entire collection (or the original branch) to access the item in the…5 votesThe product team will review this idea for consideration for a future release.
-
Increase Invoice Cap
The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.
Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.
Not all shipments are dealt with sequentially, which further complicates matters.
10 votes -
Add "last status update" to low & high circulation weeding report results
A "last status update" column in the low & high circulation weeding report results would help identify items for weeding or stock rotation.
Why would this field help us weed or identify items for stock rotation?
This item field identifies the last date an item changed their status. Many libraries change an item's status to "in transit" when they move an item from one branch to another. To that end, this field could help identify items that have either newly been received to a branch, or have sat on the shelf for some time.Items moving around systems with stock…
1 voteThe product team will review this idea for consideration for a future release.
-
SAML matchpoint with patron variable field
We implemented Patron SAML and uses a patron variable field to be the matchpoint. This field contains the patron's email address. Our IdP accepts dots, dash and underscores in patrons' email address. Due to Sierra indexing rules where symbols (including dots, dash and underscores) will be dropped, different patrons with the same letters in their email address but have different symbols in different positions won't be able to authenticate through Patron SAML.
e.g. Patron A's email = abc.def@test.com, Patron B's email = abc_dec@test.com . Both will fail authentication as Sierra will use abcdef@test.com and return both patron records.5 votesThe product team will review this idea for consideration for a future release.
-
Support SFTP for WebPAC file upload
Organizations with restrictive security policies may be unable to use FTP over port 1021 (or any other port) for file transfer to Sierra WebPAC, since FTP is an inherently insecure protocol. For the same reasons, FTP should ideally not be in use at all (even where permitted by the customer's organization) since it entails sending login credentials in cleartext which makes it subject to interception and abuse.[1]
Without FTP, the only alternative is to use Web Master within Sierra Desktop App to upload files to make changes to Live or Staging WebPAC screens.
If Innovative implements Secure File Transfer Protocol…
4 votesThe product team will review this idea for consideration for a future release.
-
Simplify FTP login for vendor status reports
Description
Sierra will enter the FTP login information automatically when downloading vendor status reports when that information is saved in the system.Value
Makes it easier to retrieve files quickly and easily.18 votes -
Ability to restart the CAS login
Sometimes the CAS login to Sierra fails. Either the page is inaccessible, or we see an LSE-OA-Error-2 from our use of OpenAthens authentication to Sierra. The only solution available is to us is to reboot the Sierra application server. This is inconvenient since staff have to log out of their activities.
It would be useful if there was an option in the Restart a Terminal section of Sierra to restart the CAS service. This would hopefully clear up the error and not require a server reboot.
2 votesThe product team will review this idea for consideration for a future release.
-
Spending Limit Pop-Up
I know its shocking when the subject of pop-ups in Sierra comes up that anyone would want "MORE!," but our Acquisitions staff would like to see a warning of fund spending over limit at invoicing in addition to ordering.
Their rationale is that shipping & Mylar costs usually cannot be pre-determined. Once posting happens, the fund goes negative. Since there is no going back, like when you're about to go down the chute at the end of Splash Mountain, there should be a warning.
8 votes -
Print or create review file of only selected items in Headings Reports
In Headings Reports, it would be useful to send only selected listings to a printer or to export as a new review file. Currently if you try to select only a few of the total shown, it will print or export the entire report, not the selected listings.
11 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Reading History via API
At this time it is apparently possible to retrieve the patrons Reading History via REST API sorted by date (oldest first or newest first). The most requested API enhancement request for us is to be able to retrieve the patrons Reading History via REST API sorted by Title. Another enhancement request is to be able to retrieve the patrons Reading History via REST API sorted by Author. This would be useful since users may have hundreds of items in the reading history.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Provide direct access to Decision Center's Title Details page
One of the nicest features in Decision Center is the title details screen, which you can access by clicking on a title in the handful of reports that include title entries such as the Popular Titles Report.
However, if you're logged in and happen to know the URL structure for those pages (https://[your Decision Center URL]/report/titleDetails/[bibnumber]) you can actually pull up the information for any title in your database directly.
I'd like to see a means for navigating to that screen more directly and just expose this awesome feature of the platform that already exists. I envision a simple page…
4 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?