318 results found
-
Allow Global Update of Fund Codes
Allow for Global Update of fund codes. I work in an academic library and will often get purchase lists from our liaison librarians for a specific department. The records are brought in and the attached order records are edited in GU with the correct vendor, and selector, etc. It would be a time-saver if I could also update the fund code (which are tied to academic departments) at the same time.
14 votes -
Postpone/freeze a hold after it's Ready for Pickup
Postpone/freeze a hold after it's Ready for Pickup
Similar to Overdrive's redeliver option. Allow a patron to postpone/redeliver their hold one time if it comes in unexpectedly or at a time when they cannot come to pick it up.14 votesThe product manager will review this idea for possible inclusion in a future release.
-
More universal accessibility features
Improving universal accessibility features for users/employees with diverse accessibility needs.
For example, for employees with visual impairments :
- High contrast mode and adjustable font size. Currently, users can change text color and size, but increasing the font size often causes content to be hidden, as the window does not automatically adjust. Users must manually resize the window each time. A responsive layout would greatly improve usability.Other potential improvements could include : screen reader compatibility, customizable keyboard navigation, text descriptions for icons, etc.
Even just the high contrast would help a lot. Additionally, it would be helpful if users…
13 votes -
Add ability to extend the hold Pickup By date to the /v6/patrons/holds/{holdId} API endpoint
Currently the only hold parameters one can modify via the API are
PatronHoldPut {
pickupLocation (string, optional): the hold's pickup location code,
freeze (boolean, optional): whether the hold should be frozen (suspended)
}It would be very helpful if the Pickup By date – and while you're at it, the Hold Note – were added as modifiable parameters. There have been many times when unscheduled branch closures or problems in sending hold pickup notices have caused us to want to extend hold Pickup By dates for items on the holdshelf.
Having this functionality in an API endpoint would permit a…
13 votes -
Options Group setting for showing Last Patron
In a consortial setting we have some libraries that would like to avoid showing last patron data for a item in an attempt to avoid retaining data that could be used to breach a patron's privacy.
13 votesThe product team will review this idea for consideration for a future release.
-
Include periodical issue information in overdue notices
We had a patron complaint that the email notices do not include magazine issue information, only the main title. The notices also do not include item barcodes, so there isn't any data to match against a specific issue. Could information from the Issue field in the item record be displayed in overdue notices?
13 votesThe product team will review this idea for consideration for a future release.
-
Send To - Delete Records
Sierra 6.3 saw the introduction of a feature that allows users to select a file in Create Lists mode & then, from the Tools - Send To menu, direct that file to either Global or Rapid Update, eliminating the need to navigate to those functions & then find & select that file.
I would like to see the same introduced, but for the Delete Records function.
Doing so would similarly streamline the workflow when doing record purges in Sierra.
13 votesThis enhancement is planned for Sierra 6.5.
-
Lock Commands in Rapid Update
When using the Rapid Update function to update individual item records, you can select a specific field (or fields) and values to update. After setting up your desired fields to update, you then scan the item barcode, hit Enter twice, and return to the point to scan the following barcode. We have had multiple instances where staff accidentally insert an additional field to change after scanning a barcode. One example is if they accidentally hit the space bar instead of the Enter key. It then defaults to the Copy# field. If there were a way to lock the selected Commands…
13 votesThe product team will review this idea for consideration for a future release.
-
Preserve notice job sort between edits
Sierra does not preserve any applied sorts after a "Notices Job" Edit dialog is closed. Instead, jobs are re-sorted by job number. This makes it difficult to keep track of which jobs have been reviewed, and generally contributes to unnecessary frustration in the Notices function.
This improvement is related to "Arrange Saved Notice jobs" suggested by Kathy Setter, but instead of applying a custom arrangement I am asking for persistence on a short-term basis:
https://ideas.iii.com/forums/951745-ils-sierra/suggestions/46677958-arrange-saved-notice-jobsRationale:
When making changes to multiple notice jobs at once, it is often necessary to sort notice jobs (e.g., by template, location, or "auto") to…13 votesThe product team will review this idea for consideration for a future release.
-
Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our…
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
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.
-
Increase Invoice Limit for Downloaded Invoices
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.
13 votes -
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…
13 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.
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Limit Pickup Location Based on Item Type
We have three pickup locations: lockers, curbside and hold pickup shelves inside the library. For our Library of Things item type we would want to eliminate the lockers as an option because they cannot hold those items because of space.
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Exclude specific patron types from getting notices
Being in an academic library, we have certain patron types which function differently than other types. This applies particularly to the differences between a student patron type and a faculty patron type. It would be helpful for us to have the ability to exclude certain patron types from getting certain kinds of notices.
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Preferences font settings can affect catalog display
When you increase the font size to 20 for cataloging, it enlarges all the other information except the title line which remains the same. As a result, the title line appears smaller in comparison to the other information. It would be great is the title also displayed in the larger font.
13 votes -
Sort "Due Date" column in "Item" view as date instead of string
When a user is in the Cataloging workflow, the "Due Date" column in the "Item" view is sorted as a string instead of a date, eg "1-01-2023" comes before "9-01-2021". It would be helpful for this to be sorted as a date and match the sorting of the "Due Date" column in the "Holds" view.
13 votes -
Override Prompt/Authorization Required - List Permission(s) Needed
Sometimes it's unclear what permission is triggering the authorization required/override prompt during a transaction and thus what staff member will need to step in to override/allow the transaction to go through. It would be helpful if the "authorization required" prompt included the permission(s) that apply to the transaction.
13 votesThe product manager will review this idea for possible inclusion in a future release.
-
Correct 0 date values in SQL views to NULL values
In circtrans and finespaid views (and maybe more views) there are several dates that are showing a value of 0 (which displays as 1969-12-31 due to UNIX date formatting).
Dates do not have a value of 0, they can however, have a value of NULL, which is already how things work with other dates in the system, like the bib record cataloguingdategmt.
This should be fixed for any dates in the system, not because anyone may or may not vote for it, but because it is both inaccurate and inconsistent.
I logged this as a ticket,…
13 votes
- Don't see your idea?