12 results found
-
Module data on the library catalogue (Online Reading List)
We are using Talis Aspire as our Online Reading List.
We are looking for ways to synchronise module code and module name data from Talis Aspire with our library catalogue so that we can easily identify whether a book on our catalogue is on a reading list.
Attached please find the example that captured from other library.
May I know if there are any updates ? I had submitted the same request last year.
2 votesProduct Management has reviewed this request and determined that this idea is too narrowly focused to be included in the product roadmap.
-
Elevated credentials do not work in Data Exchange
If a computer is logged into the SDA with a set of credentials that do not allow access to Data Exchange, the system prompts the user to login with appropriate credentials. When the user logs in with the elevated credentials, the SDA does not function properly. The Data Exchange dropdown list is unavailable for the newly elevated user. The user has to completely log out of the SDA in order for Data Exchange to work. I believe this is a bug in the system. If elevated credentials are prompted, then the functionality should work after the login. Otherwise, do not…
2 votesI'm closing this in Idea Exchange since it sounds like a bug and should be investigated by our Support team.
-
verify address subfields in patron record (SDA)
Many libraries depend on zip/postal codes, city, prov/state metadata to make financial and library service decisions. No subfields in the address field can be verified. The postal code has some verification, but the record can be saved if that field is not entered correctly. We would like the option to make the CITY, PROV/STATE, and POSTAL CODE/ZIP data verified, and to have a description beside each "expanded" address subfield to guide staff on how to enter the data.
Idea Value
Libraries should be able to verify the address subfields (like the city, prov/state, and postal/ZIP code).Analytic tools (even Decision…
18 votesWe do see the value in incorporating address verification functionality but believe that this would need to be a broader initiative that takes LX Admin and Polaris into consideration.
I will archive this idea for future reference and it may be re-considered for a future release.
-
hold placed more than 180 days ago : hold pickup location should always be editable by staff in SDA
Staff cannot change the hold pickup location if a hold was placed more than 180 days in the past (perhaps the hold is frozen, there is a long hold queue, or the book publishing date was delayed). Essentially this means that once past 180 days, Staff cannot manage the hold. We don't want to cancel the hold and then apply an arbitrary "Not Needed Before date".
Idea Value
Many Idea Lab tickets request the ability to batch change hold pickup location or change the pickup location of items with a status of "on the hold shelf". This is another instance…26 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Better differentiation in holds checkout warning messages
Currently, the Sierra message that you're checking out a book that's on the holds shelf for someone else is almost identical to the message that someone has a hold on the title at a bib level, and it is extremely easy for harried, hurried staff to skip right over the more important message, that they're accidentally checking out the book to the wrong person, because they think that the message is not important. I would like a way to either differentiate those two messages in Sierra to be more clear, or to eliminate the message that says the book has…
20 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Remember patron preference about receipts
This is connected to Paul Costa's idea "Check for Due Slip Delivery Method Change Before Closing Patron Record" (link). Many patrons, probably most, have a consistent preference about receipts -- either they almost always want one printed or they almost always don't. (Or prefer to have it emailed.)
What if we had a field in the patron record that recorded this preference, and when the patron record was opened for checkouts, the print receipt button defaulted to the patron's preference?
The field would default to "no receipt" when the patron record was created. I'd want input from others on whether…
31 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Check for Due Slip Delivery Method Change Before Closing Patron Record
Currently, Sierra goes by the delivery method selected before the last item is scanned, instead of when a user clicks the Close button. Having recently changed to not automatically print due slips, we are still working on asking patrons their preference before scanning items, but will often forget until all items have been scanned, which is too late. The workaround of using the Print Table option is less than ideal, as it doesn't follow our print template for Due Slips. As far as my knowledge goes, it also completely cuts staff off from the option to email the due slip…
19 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Bib level holds should be allowed on records with only non-viable items if there is an order record attached
Bib level holds should be allowed on bibs with non-viable items if there is an active order record attached. Currently, this is not possible, and there is no way to configure for this. There are a number of ways to configure the (many) places dictating holds and what can be held. But at the moment, none of them allow the hold (without a staff override) if the only remaining item is non-viable (missing, lost, etc.)
Idea Value
It doesn't make sense to me that holds are allowed on bib records with only an order record, but as soon as that…14 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Add option to email checkin receipt to patron
Currently Sierra offers the option to email the patron due date information. We use courtesy notices via email as a backup notification of due dates. We would like the option to email the checkin slip as well. We always offer the option to print a receipt upon checkin, and may patrons appreciate that, but have often commented that it would be more convenient to receive the checkin confirmation via email instead of being printed on a slip of paper that can get lost.
Idea Value
Email is easier to search and archive, whereas a paper receipt is prone to getting…22 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Clearer distinction between expired holds and clear the holdshelf
When a patron's hold expires or an item is cleared from the holdshelf, the Program column in View Canceled Holds reads "Clear Holdshelf" for both processes. A more apparent distinction between the two would be helpful to both patrons and staff.
Idea Value
The ability to see the difference between an expired hold and an item cleared from the holdshelf would allow staff to accurately explain to a patron why their hold was removed from their account. Differentiating between the two would also assist staff in troubleshooting issues with the Clear the Holdshelf and expired holds processes.33 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
Block patron circulation based on the number of overdue items
As libraries eliminate fines they would like alternative ways to provide an incentive for patrons to return items. We would like the option to block patron circulation based a Library determined number of overdues. This rule could be added to the Patron Block table so that libraries could customize rule as necessary.
Idea Value
Libraries use the patron block table to determine when a patron is blocked from circulation. As this table exists, could the # of item overdues be added to this table? Libraries could set this behaviour (as they do all patron block settings).Value: Although we never…
25 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
-
transfer holds between bibs
Allow transfer of bib level holds to another bib! Documentation states that only item specific holds can be moved, and then only to bib level on the same bib or to another item. We need to be able to easily move holds or even entire hold lists to another bib.
Idea Value
Moving holds to a new edition of a title, or a new volume of a series. Depending on individual library cataloging and their use of monograph versus serial records, not to mention volume information, there are many instances of having title level holds on something that has been…32 votesIn accordance with the Idea Graduation Workflow guidelines agreed upon by Innovative and IUG, this idea has been closed because it was submitted more than two years ago and has not been selected for inclusion in the product.
This idea is still available for commenting but is no longer eligible for voting.
Ideas that were submitted three or more years ago are archived for future reference.
- Don't see your idea?