6 results found
-
Ability to view history for item and volume records.
It would be helpful for us to have access to the history of item and volume records, including details of their creation and any subsequent edits. This would improve our ability to track changes and ensure accountability if any issues come up.
26 votesThis enhancement is planned for Sierra 6.6.
-
Include Individual Item Costs in Overdue Notices
Make it an option to also include the item cost in the overdue notice as well (incentive to return!).
In our date due slips (JasperSoft) we include the cost of each item and a total cost to show what the patron saved by using the library vs. buying.
61 votesWe are planning to add the item cost to overdue notice data so it can be included in overdue notices sent through LX Starter as of Sierra 6.7.
Additional changes will be needed in LX Starter before the new data can be included on emails for overdue items.
-
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 votesThis development is planned for Sierra 6.7.
-
Fix truncated Z39.50 server names in SDA
Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.
The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.
As-is, the "Selected Databases" dialog can be dragged wider by the…
4 votesThis idea will be implemented in Sierra 6.7.
-
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…
48 votesSupport for a newer version of Jaspersoft Studio will be provided in Sierra 6.7.
-
Add permission to prevent user deletion of notice jobs
We frequently have the unfortunate situation where staff accidentally delete their paging list from the list of Notices. Ideally, we'd prefer that frontline staff be able to prepare, print, & fulfill their paging lists but not be able to delete them.
Separating authorizations to create/edit/delete these lists from the preparation & printing would save support staff a great deal of time spent recreating these lists & remove some of the potential for frustration & confusion among frontline staff.
47 votesThis enhancement is planned for Sierra 6.6.
- Don't see your idea?