307 results found
-
Record History for bib records does not capture elevated credentials
Currently the Record History report for Bib Records in Sierra contains a list of record changes, the login that made a change, and when it was changed.
However, if the change to a bib record was attempted with a login without the required permissions, Sierra will ask for a login with elevated permissions and allow the user make a change once logged in. In this case, the Record history will record the first login (without required permissions), instead of the elevated login needed to make the change.
Problem: Record History report for Bib Records Record History report for Bib Records…
5 votesThe product team will review this idea for consideration for a future release.
-
Automatically email due slips from Express Lane
Do you want all of your patrons to receive due slips by email, every time they check out an item?
Express Lane can be configured to automatically print a due slip, or allow patrons to choose between some combination of print or email due slips with an option to decline, but cannot be configured to automatically send an email due slip with no option to decline.
In our special library, it is desirable to always send email due slips with no option to decline. We want our patrons, who are all employees, to receive this documentation for every loan for…
5 votesThe product team will review this idea for consideration for a future release.
-
Validate tickler date field to prevent miltickle failures
When a tickler has invalid data in the "Date (YYYYMMDD)" field, Sierra's nightly tickler process will fail and any ticklers on order records not already processed will not be sent. This failure will keep happening every night until the problem is discovered.
For example, dates entered with dashes separating the elements ("YYYY-MM-DD") or with additional characters following the date ("YYYYMMDD - Note text here") will cause this kind of failure.
In the absence of an easy way to search for invalid data in the tickler date field (e.g., Create Lists), it would be very desirable for Sierra to validate user…
5 votesThe product team will review this idea for consideration for a future release.
-
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.
-
Always renew a checked out item in SDA if there is an available item (without pop-up)
By default in the SDA, items are blocked from renewal if a hold is placed on the associated title or volume.
If the Renew Title Holds feature is enabled, the system gives you the option to OVERRIDE the block on renewing held titles and volumes. The system does not consider frozen holds when blocking items from renewal.
Staff will always select "yes" to a renewal if there is an available item. They do not want to continually select "override" when they are renewing multiple holds.
Can there be an option to always renew if there is an available item (without…
5 votesThe product team will review this idea for consideration for a future release.
-
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.
-
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.
-
Expand to different order statuses for the Sierra REST API
The Sierra REST API does not return the order record for the bib if the order status is "a" (fully paid). It will only return information if it's "on order".
Patrons are unable to place holds on new materials using Innovative Mobile for bibs with paid order records that do not yet have items attached.
5 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
give libraries the option to exclude ratings from Homebound circulation workflows
Our homebound customers love the Sierra reading history functionality, but tell us that they do not want the Library to give them a checkout receipt that includes an option to rate the title. They also tell us that they do not want their personal information on the receipt (and the library cannot edit the Homebound receipt template).
Additionally, circulation staff workflows are hindered because if a stack of homebound items are returned, they have to use the keyboard / mouse to move past the checkin rating prompts.
5 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Allow self-check out of virtual items using Sierra API
Update the Sierra API to allow self-check out of virtual items. We use Bibliocommons app and our customers cannot use the self-checkout feature to check out INN-Reach items.
5 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Enable API update of patron records to blank out expiry date
Sometimes we want to update a patron record and blank out a date in the expiry date field for a continuing staff member.
The patron API cannot do this - blank values are rejected as invalid JSON e.g.
{"expirationDate": " - - "}
{"expirationDate": ""}
{"expirationDate": "--"}
{"expirationDate": "null"}All we can do is add a date, and for continuing staff we can only use the maximum possible date of 18 Jan 2038.
Enhance the API to accept a blank value in expiry date.
5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Make Third Party API Transactions More Apparent for Sierra Customers
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…
5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Returning items not in hand
We were wondering if a “Return Item” button could be put alongside “Renew” “Claimed Returned” when in the Checked Out Items screen, so that you can return an item not in hand etc.
Simply select the item already issued to a member, and hit 'Return'.5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Location Code 0 Displays as None in Checkout Location Field
With the recent changes that allow the label to display in the item record, staff now see the descriptive name of the statistical group in the checkout location. However, 0 displays as None and does not honor what is in the Statistical Group Maintenance table. We have ours labeled for Web Renewals and would like this display to honor what is in the table as opposed to saying 0 None.
5 votes -
check in claimed returned (item location should reflect where item was made claimed returned)
For libraries with floating collections, the location where an item was made "claimed returned" may not reflected in the item record. This is because the 3 options staff have when an item is "claimed returned" does not change the location of the item.
Essentially the problem:
An item is “checked out” at location A.
The item is “claimed returned” at location B.
The item location remains as location A.Staff have 3 choices when they make an item claimed returned:
· 1. Places a claimed returned note in both the item and patron records
· 2. (Optional) Removes the check-out…
5 votes -
Allow sorting options for API Results
An example of this is the Items/GET API appears to sort the results based on catalog date/item id of the item. It would be nice to specify a different sort parameter that would allow the current sort or a new sort which would return them in the same sorting specified in the Cataloging function in Sierra.
This might be nice for other APIs as well.
5 votes -
increase the number of indexed characters in title keys (long titles do not sort in SDA Search)
A Keyword search in the SDA Search/Holds does not sort titles as expected because of the number of indexed characters in title keys.
Innovative has noted: "These title keys are a fixed number of characters and is based on approximately the first 30 characters of the title. We don't have any way to adjust this in the system configuration. "
We have DVD titles that include the title, season, and episodes. These do not file as expected in a SDA search because all of the metadata is longer than 30 characters.
I understand that the "phrase" facet after performing a…
5 votesThe product manager will review this idea for possible inclusion in a future release.
-
A "full Payment History file" event should log an error to the Admin App's System Messages log
Today our Payment History file reached 9,999 records which is close enough to the 10k record capacity that the attached error message was displayed. Fortunately the staff member had the presence of mind to screen-capture this error dialog today so I could read its message verbatim, but this isn't always the case. It would be helpful for an error of this severity to be written to the System Messages log viewed using the web-based Sierra admin app.
Given the low variety of error messages written to that log, there must be all kinds of similar messages which are not logged,…
4 votes -
Create a pop-up when you are about to overwrite a review file in create lists.
It is very easy to accidentally overwrite a review file in create lists. There should be a pop-up that asks if you want to overwrite the file so that you know you're doing it.
4 votes -
add location column in Count Use function
Under the count use function, is it possible to add a location column? Currently, we have Title / Barcode / Count / Status. This way, when staff collects used but not checked out items and counts their usage, they can also see - at a glance - if the item belongs to a different floor/location and can separate it on the spot.
This added information will save staff time and minimize the chance of something being misplaced.
4 votes
- Don't see your idea?