Settings and activity
28 results found
-
45 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
An error occurred while saving the comment An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• The software Sierra uses for print templates has been updated to a recent version and print templates have been tested for compatibility with the print templates provided in previous versions of Sierra.
-
40 votes
The product manager will review this idea for possible inclusion in a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
• Sierra will have a system-wide option accessible to library system administrators to enable and disable this feature so that it can be turned on if/when the library decides to use the feature.
• When the feature is enabled, a library system administrator will be able to configure the feature to be enabled or disabled at self-check stations. If enabled, Sierra will automatically clear the hold at self-check stations. When disabled, the system will keep the hold on the (duplicate) item.
• When the feature is enabled, a library staff member checking out a non-holdable item will be prompted to cancel or keep the hold on another item on the same bibliographic record.
• The feature will apply to bib and volume-level holds, but not item-level holds since those have been placed on specific items.
• The feature will apply to the holds on a single bibliographic record, not on a group of bibs (e.g. same title in different formats with separate bibs).
• Best effort will be made to include this new functionality in Sierra API.Notes: Must consider the use case where libraries with short loan or reserve collections still want patrons to be able to have an active hold on regular-loan items.
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• Sierra will have a system-wide option accessible to library system administrators to enable and disable this feature so that it can be turned on if/when the library decides to use the feature.
• When the feature is enabled, a library system administrator will be able to configure the feature to be enabled or disabled at self-check stations. If enabled, Sierra will automatically clear the hold at self-check stations. When disabled, the system will keep the hold on the (duplicate) item.
• When the feature is enabled, a library staff member checking out a non-holdable item will be prompted to cancel or keep the hold on another item on the same bibliographic record.
• The feature will apply to bib and volume-level holds, but not item-level holds since those have been placed on specific items.
• The feature will apply to the holds on a single bibliographic record, not on a group of bibs (e.g. same title in different formats with separate bibs).
• Best effort will be made to include this new functionality in Sierra API.Notes: Must consider the use case where libraries with short loan or reserve collections still want patrons to be able to have an active hold on regular-loan items.
-
28 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● Staff can select and save a due slip preference (print, email, none) in the patron’s account.
● Patrons can select and save a due slip preference (print, email, none) in their account information using the WebPAC, Vega Discover, or a third-party discovery UI that supports updating my account information via API.
● The preference is stored persistently and editable by staff or the patron themselves.
● The preference is applied automatically at the end of each checkout session.
● The system checks the patron’s saved preference upon checkout completion.
● The appropriate due slip is printed, emailed, or skipped based on the preference.
● Staff can override the preference if needed for a one-time change.
● Due slip preference is exposed via the patron API.
● External systems can read and update the preference.
● API documentation includes due slip preference field and usage examples. -
43 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● New notice text is available specifically for damaged items.
● The system selects the appropriate notice (lost vs. damaged) based on item status.
● Notice includes customizable fields such as item title, barcode, fee amount, and reason.
● A new item status “Damaged & Paid” is created and applied automatically upon payment.
● The status is visible in item records, reports, and Create Lists.
● Staff can filter by “Damaged & Paid” in Create Lists or equivalent tools.
● The status change is logged with date and user ID.
● Create Lists or reporting tools support filtering by “Damaged & Paid” status.
● Lists can be exported with relevant metadata (title, barcode, payment date).
● Staff can save and reuse these filtered lists for inventory workflows. -
59 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
• Make the not wanted before (NWB) date accessible to library patrons so they can control the earliest date when their holds will be automatically active. This will be the “Thaw” date in the patron interfaces.
• The patron will be able to modify the NWB date from various user interfaces (e.g. WebPAC, Vega Discover, via Sierra API).An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• Make the not wanted before (NWB) date accessible to library patrons so they can control the earliest date when their holds will be automatically active. This will be the “Thaw” date in the patron interfaces.
• The patron will be able to modify the NWB date from various user interfaces (e.g. WebPAC, Vega Discover, via Sierra API). -
60 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
• A library staff user will be able to apply one or more changes to a set of loan rules without needing to open and edit each loan rule one-by-one.
• The user will receive confirmation before the changes to the loan rules are saved.
• The staff user will be able to create a backup of the loan rules before changes are made.
• The staff user will be able to import a saved set of loan rules from a backup file.
• Loan rules will be validated upon import.Notes: The entire file needs to be exported/imported to maintain the file structure/integrity in Sierra.
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• A library staff user will be able to apply one or more changes to a set of loan rules without needing to open and edit each loan rule one-by-one.
• The user will receive confirmation before the changes to the loan rules are saved.
• The staff user will be able to create a backup of the loan rules before changes are made.
• The staff user will be able to import a saved set of loan rules from a backup file.
• Loan rules will be validated upon import.Notes: The entire file needs to be exported/imported to maintain the file structure/integrity in Sierra.
-
38 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● Assigning ownership
o A new "Owner" field is available in the saved search properties.
o Only users with appropriate permissions can assign or change the owner.
o The owner’s name or initials are displayed in the saved search list view.● Viewing last run info
o Each saved search displays the last run date and user initials.
o This metadata is visible in both the list view and the search details.
o The data updates automatically after each run.● Renaming saved searches
o Saved search names are editable via UI.
o Name changes are logged with timestamp and user info.
o Validation prevents duplicate names or invalid characters.● Identifying unused searches
o A filter or report shows saved searches by last run date.
o Searches not run in the last 6 months are flagged.
o Admins can sort or export this list.● Bulk management
o Admins can select multiple saved searches at once.
o Bulk actions include delete, archive, and assign owner.
o Confirmation prompts appear before deletion.● Usage alerts
o The system displays a warning when saved searches reach 80% of the limit.
o Notification includes a link to cleanup tools or reports.
o Admins can configure the threshold for alerts. -
31 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● The payment lock message clearly states that another station has the patron record open.
● Staff are informed of which actions (e.g., payment, adjustment) are temporarily unavailable.
● The message includes a suggestion to close the record on the other station to unlock payment functionality.
● Staff can retry accessing the payment function after the record is closed elsewhere. -
19 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● Integration between Sierra and automatic certificate renewal infrastructure established by local sysadmins (for short-term, renewable certificates like LetsEncrypt, DigiCert, etc.), is introduced as:
o A staging location in Sierra where a new or just-renewed SSL certificate may be placed by an external process for subsequent installation and activation
o An API which installs and activates the new or just-renewed SSL certificate in Sierra's production locations, restarting services as necessary, providing confirmation in API response
o An option for Sierra to automatically install and activate certificates as they appear in the staging location, and provide the confirmation result in a user-viewable log, as an alternative to the API call
o Both the API call and the auto-install method support rollback to the previous installed certificate
o Authorized users may review logs of certificate installation activity including public certificate details -
17 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● Staff can select a print template when initiating spine label printing from Create Lists.
● Templates support customization for font, layout, spacing, and label type.
● The selected template is applied to all labels in the batch.
● Admins can create, edit, and delete print templates.
● Templates are stored centrally and accessible to authorized users. -
23 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● The new Stat Group field as provided as an optional field in the API key creation UI.
● When creating a new API key, the user can assign a stat group to be used by the API key
● If no stat group is assigned to the API key, the stat group will default to stat group 0.
● Actions taken by the REST API will use the stat group associated with the key unless explicitly set otherwise in the request.
● Desirable: provide a way to retroactively assign a stat group to existing API keys. -
43 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
• The user permissions to create, edit and delete notice jobs has been separated from the permission to prepare and print the notice jobs.
• The permission for create/edit/delete shall be available upon upgrade, but not assigned to any user by default.An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• The user permissions to create, edit and delete notice jobs has been separated from the permission to prepare and print the notice jobs.
• The permission for create/edit/delete shall be available upon upgrade, but not assigned to any user by default. -
13 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● When no exact match is found, the system offers “Did You Mean” suggestions or similar items.
● Suggestions are based on common misspellings, phonetic similarity, or fuzzy matching.
● Staff can quickly rerun the search using a suggested term without retyping. -
17 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
• The search facets will include a new option that combines (ANDs) the “available in my library” and the “location” facets so that results shown represent items available at the location selected.
Note: Current functionality of the facets “ORs” the fields so that items can be either “in the branch” or “available” and they will display in the results.
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• The search facets will include a new option that combines (ANDs) the “available in my library” and the “location” facets so that results shown represent items available at the location selected.
Note: Current functionality of the facets “ORs” the fields so that items can be either “in the branch” or “available” and they will display in the results.
An error occurred while saving the comment MEEP candidate July 2024
-
24 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
● Reports > Record History will be available for item records and volume records through the Sierra client, like the record history displayed for bib records
● Details displayed will include action (created, edited outside a circ transaction, deleted), user login, and date/time
● Library staff want to be able to track when the item location has been changed
● A time-limited store is available for viewing in the Sierra client (X days)
● The longer-term record history information is available for reporting through Vega Reports
● At the library level, libraries can opt out of storing item and volume record history -
10 votes
We are reviewing this idea for possible inclusion in a future release.
An error occurred while saving the comment This is possible today in Polaris for both voice and SMS messages. It would require architectural changes in Sierra to send a second overdue for telephone notices but is possible now for SMS notifications.
-
25 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• A library staff user authorized to waive fees can waive a partial amount owed by a patron without the need to make a partial payment at the same time.
• The partially-waived amount will be recorded in the patron’s fines history.
• Partially-waived fees will be recorded in the fines and fees report produced by Sierra. -
18 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• Add a system-level configuration to Sierra to notify a system administrator when an offline circulation file has been uploaded. This configuration shall be in an administrative interface (i.e. circulation options, Admin App, etc.).
• The configuration will provide a field for an email address of one or more people to notify when a file has been uploaded.
• The system administrator shall receive notification when the offline file has been uploaded successfully. -
28 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• Orders displayed in the “purchase orders to FTP” queue will include an order sent column to show the order has already been sent to a vendor.
• Sent orders can be highlighted on the display in a user-defined color according to a user preference.
• If orders that have been sent are selected to send again, a pop-up message containing the text "File contains previously sent orders. Do you wish to proceed?" appears when individual orders are packaged together into a single file for uploading to the vendor.
• The message allows the staff member to back out and remove any previously-sent orders before proceeding or continue.
• The text of the pop-up is internationalized so it can be translated into multiple languages. -
18 votes
A nearly identical idea was previously submitted through Idea Lab and is under review.
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• The screen will be doubled from its current size to show more patron fields on the screen.
• When using either the brief display or the brief display w/address, the pre-defined fields will wrap across two columns (existing functionality).
• When using the custom patron record display, a library staff member will be able to set the number of columns and the number of fields to display on screen in the Sierra client > Admin > Options > Patron Display tab.
• If there are more fields than can be displayed, a vertical scroll bar will appear on the right side of the screen to show the remaining fields.
• An administrator will be able to set the number of columns and the number of fields to display on screen in a user’s custom patron record display options in the Admin App > Authorization and Authentication > Users > [user] > Options > Patron Display > Custom Display Settings.
MEEP candidate for the Sierra 6.6 release
Functional Requirements (what does it need to do?)
• The software Sierra uses for print templates has been updated to a recent version and print templates have been tested for compatibility with the print templates provided in previous versions of Sierra.