268 results found
-
Need for "Check-in: Do not fulfill holds" function to only apply to current check-in
Libraries have the option to use "Check-in: Do not fulfill holds". This checks in the item without without fulfilling any holds that are in the hold queue for that item. This item will never appear on a Title or Item paging list unless the item is checked in AGAIN. To be eligible to appear on a Title or Item paging list the item must be checked in a second time.
We need an option to release that restriction. The hold should be unfulfilled only during that specific check-in.
Reasons for this:
1) Our transportation system may be stopped due to…
12 votesThe product team will review this idea for consideration for a future release.
-
Add Invoice Number to Invoice Summary
The Invoice Summary that is sent after posting invoices only lists the voucher number. Our Finance department has to go through the Invoice Register and match the invoice number to the voucher number to know what invoices should be paid. This is very time consuming, and susceptible to human error. Please consider adding the invoice number to the Invoice Summary.
19 votesThe product team will review this idea for consideration for a future release.
-
Schedule and automatically place contents of a system-generated review file into one or more designated list
Each week staff go into Create Lists and repopulate a designated review file with current data from a system-generated list. Two examples of system-generated lists include the OVERDUE ITEMS and PURCHASE ALERTS files. It would be great if our site could schedule Sierra to identify a specific list number and replenish or refresh the contents of it with most current system file's data. This would make the task fully automated. It's important to our system to be able to designate which list or review file number to use for each system-generated file job, however. We are a consortium and our…
3 votes -
Include the AA (patron identifier) element in the 10 Checkin Response for SIP2
When users return the materials via self-check machines, we want an email receipt to be automatically sent to them. Unfortunately, Sierra does not currently support the AA element in the 10 Checkin Response. Some libraries purchased the Patron API feature to get it to work but if Sierra include the AA element, it will simplify the process.
4 votes -
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…
6 votesThe product team will review this idea for consideration for a future release.
-
Paging Queue should recognize changes to the Not Wanted Before Date in Hold record
Sierra queues the hold for paging at the time the hold is placed, based on the data the hold was placed with. If the hold is modified after that (by changing the Not Wanted Before date), those changes don't update the paging queue, and Sierra will continue to page as if the hold had not been modified.
10 votesThe product team will review this idea for consideration for a future release.
-
Limit access to Login Names & Parameters via permissions
We'd like to be able to limit access to the Login Names & Parameters section of the Admin Corner (especially the Limit Network Access tables) via permissions. Certain functions, such as load tables, require certain staff members to have access to the Admin app, but having the login names and parameters unrestricted leaves an unnecessary hole in security. There are other functions in Admin Corner that require separate permissions and prompt users to enter their credentials, but not this one.
8 votesThe product team will review this idea for consideration for a future release.
-
Add an option to restrict check-in to owning location
For some fragile items that we don't want to put in transit (e.g. telescopes, vinyl records), we want to be able to limit check-ins to the owning location. We can communicate these limits to patrons on our website and through signage or labels, but we'd like there to be an option within Sierra to generate a pop-up (with an option to override) so staff are alerted to tell the patron they have to bring the item back to another location.
8 votesThe product team will review this idea for consideration for a future release.
-
Add a backdate option to the /v6/items/checkouts/{barcode} endpoint for checking in items
I would like to add an optional parameter to the Sierra API endpoint for checking in items to allow for backdating those transactions as you can within in the client as it may help with automating some projects.
For an immediate example, I have identified a number of items that were not removed from the checkout table correctly due to locked patron records, where the were placed in transit and I can see a time the checkout ought to have occurred via the in transit message. I would like to write a script to correct these failed checkins once they…
5 votes -
Improve diacritics in sierra to search Arabic and other Semitic langauges
Improve diacritic searching in Sierra to include Semitic languages, especially Arabic! We have a fair number of Arabic books in out collections, and a large Arabic community, but Sierra support for Arabic characters does not seem complete. We often find that Arabic letters in Sierra is replaced by a white square, which seems to mean that the character is not supported. The names appear fine in Vega but the non supported letters do not seem to be indexed in the search results. This is an important language for members of our community and support for it is important in our…
10 votesThe product team will review this idea for consideration for a future release.
-
Notice scheduling
Currently, the notices for Current Checked Out Items allows for daily or weekly scheduling, but it would be handy to have the ability to set this at a longer time frame such as monthly, quarterly or by semester as most of our materials check out for much longer periods of time (16 weeks or longer generally), and some users find the weekly reminders tedious.
Either the option to set the automated notices to a longer time period, or the ability for patrons to choose a longer reminder period (opt in to weekly, monthly, etc notice) would be very helpful.
5 votes -
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)…
34 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
New Skins for Sierra
Can we get some new skins to choose from for the SDA/Sierra Web?
There are currently two: Half Dome & Glacier Point.
We currently use colors to differentiate between our Production instance of Sierra & our Test version. However, we also have a Training database.
Variety is the spice of life! How about a rose-colored skin, a powder blue, or a "Millennium Green" as an homage to the Millennium database?
26 votesThe product team will review this idea for consideration for a future release.
-
Enable Passkeys for patron authentication
Passkeys are both easier for people to use and safer than using passwords and PINs. Passkeys allows users to sign in to their account using the same mechanism they use to unlock their device - fingerprint, face recognition, etc. There are a couple of good introductions to the benefits of Passkeys over traditional username/password credentials here:
https://fidoalliance.org/passkeys/
https://developers.google.com/identity/passkeys10 votesThe product team will review this idea for consideration for a future release.
-
Patron Preferred Pronouns
Sierra patron records should include a patron pronouns field, so that library staff can record customers' stated preferred pronouns and use the correct language in conversations and communications with customers. The field should be able to display in the Brief patron display. This step would help to support inclusion, wellbeing, and belonging in libraries.
17 votesThe product team will review this idea for consideration for a future release.
-
Clear and Set Permissions at one go
We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope faster way to change the user. At this time you must first remove previous user (Admin - Clear Permissions) and then add new user (Admin - Set Permissions). Staff suggested one function that would both Clear previous and Set new Permissions. E.g. Set Permission could remove the old user and then ask the new user. We set up macros for both functions so staff can use them instead of drop-down menu. However, I suppose…
3 votes -
Max Item A-D But For Holds
I had first suggested this over a decade ago when at another library that was struggling how to balance its combination of branch & research library users & the sort of requests they might make. While no longer there, I still see it as a potentially useful means for staff to develop their request processes & create limits within limits.
What I'd like to see is the ability to not only set a hold threshold, but as is the case for the Max Items A-D allowed as applied to checkouts, allow a similar breakdown for holds.
Optimally, this would allow…
17 votesThe product team will review this idea for consideration for a future release.
-
Persistent Column Resizing in Summary Tab
Persistent Column Resizing in Summary Tab:
Currently, users can resize columns in the Summary Tab (Orders, Items, and Holdings) during a session. However, these adjustments are not retained after the session ends, requiring users to reapply their preferred column sizes each time they log in.
I propose an enhancement to allow users to permanently save column resizing preferences across sessions. This feature would greatly improve usability and efficiency by enabling a more customized and consistent interface tailored to individual workflows.
This enhancement would benefit users who frequently manage data within the Summary Tab by reducing repetitive actions and ensuring a…
9 votesThe product team will review this idea for consideration for 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…
50 votesSupport for a newer version of Jaspersoft Studio will be provided in Sierra 6.7.
-
Move to Bottom of Group - use marc field instead of field name
Our catalogers would like the option when choosing a field and selecting "Move to Bottom of Group" that it could go to the bottom of the list of numbered tags it is part of instead of the field name of tags. An example is moving a 5xx field to the bottom of a list of other 5xx fields, and not to the bottom of the record if there is an 852 (also a note) field.
10 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?