Settings and activity
21 results found
-
36 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment 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. -
44 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.7 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.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. -
26 votes
Selected for the Sierra 6.7 release by MEEP enhancement process
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 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:
- 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
- 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
- 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
- Both the API call and the auto-install method support rollback to the previous installed certificate
- Authorized users may review logs of certificate installation activity including public certificate detailsAn 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 -
21 votes
Selected for the Sierra 6.7 release by MEEP enhancement process
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 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.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. -
27 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release
Functional Requirements (what does it need to do?)
● Title and author remain visible even if bib or item records are deleted.
● APIs expose stored title/author fields, even if bibs/items have been deleted.
● Metadata retained indefinitely unless patron deletes it.
● Bulk bib deletion does not affect stored metadata. -
49 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release
Functional Requirements (what does it need to do?)
● Each item barcode appears exactly once per list.
● System suppresses duplicate rows for the same item_id.
● All holds remain tracked; paging list simply avoids duplicate display.
● Optional counter on the item line: “Holds pending: X”.
● Only pageable items appear.
● Multiple holds for a single item do not generate multiple pull requests.
● Paging list behavior is identical aside from deduplication. -
14 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release
Functional Requirements (what does it need to do?)
● The system allows more than 99 invoice files to be downloaded per day.
● Staff can initiate downloads without receiving a limit-related error.
● The expanded limit does not negatively impact system performance or data integrity. -
40 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.7 release
Functional Requirements (what does it need to do?)
● When displayed, Holds information shall include
- Hold Placed Date/Time.
- Placement Channel (Sierra Desktop, Sierra Web, Web OPAC, Mobile App, SIP2, NCIP, etc.).
- Actor (Patron or Staff login).
- Program (client identifier).
- Include bib title, item barcode, pickup location, queue position.
● Details shall be displayed in
- Patron’s holds tab
- Bib-level holds
- Item-level holds
- Volume-level holds
- Cancelled/expired holds
- Manage Holds
● Details that are not applicable are not displayed
● Staff edits do not override original hold placement metadata.
● SIP2/NCIP holds marked as SYSTEM actors.
● Batch imports set API or SYSTEM channel.
● Unknown channel stored as UNKNOWN. -
28 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release*
* This idea will require implementation across multiple Sierra releases.Functional Requirements (what does it need to do?)
● Accepts ZIP+4 formats: #####-####, ##### ####, #####—####, ##### - ####, ##### - ####.
● Normalizes to #####-####.
● Ignores whitespace variations.
● City and region/state fields correctly populated.
● Identifies address_line1 and address_line2.
● Parses city, region/state, ZIP even if placed on separate lines.
● Supports no-comma entries using token pattern detection.
● Trims whitespace.
● Normalizes punctuation.
● Standardizes casing on city and region/state.
● Country detection logic configurable.
● Normalizes valid patterns.
● Parser generates confidence scores.
● Prompts display when below threshold.
● Quick-edit preview provided.
● Existing records unchanged.
● New parsing applies only on add/edit.
● Create Lists and SQL behaviors remain intact.
● Accepts Canadian postal codes (A1A 1A1).
● Accepts UK postal formats.
● Accepts Australian postal formats.
● Accepts New Zealand postal formats.
● Support plug-in pattern libraries for more countries.
● Bulk reparse tool for legacy addresses. -
27 votes
Selected for the Sierra 6.7 release by MEEP enhancement process
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release
Functional Requirements (what does it need to do?)
● The last circ activity date will be updated when a vendor uses the patron validate API to authenticate a patron.
● Vendor roles shall be provisioned with the minimum permission required to perform authentication flows only.
● Vendor roles shall not have authorization to read, search, list, update, delete, or otherwise access patron records.
● Any attempt by vendor roles to access patron-related resources shall be denied and logged. -
26 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release*
*This idea will require implementation across multiple Sierra releases.Functional Requirements (what does it need to do?)
● Staff can save a Global Update command as a reusable profile.
● Profile includes fields, values, filters, and safety settings.
● Scheduler can select a saved Create Lists query and Global Update profile.
● Scheduler runs query → generates list → applies update.
● Logs success, failures, and affected record counts.
● Permissions control profile creation/editing.
● Detailed audit logs are kept.
● Preview/dry-run mode available.
● Dashboard or log shows job name, status, next run, last run, error logs. -
64 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release
Functional Requirements (what does it need to do?)
● Timestamp and user ID automatically added to notes and messages added to patron and item records by library staff.
● Stored as formatted metadata at the beginning of the note or message field
● Displayed in staff UI and API.
● Existing notes remain unchanged.
● User can delete notes and messages using standard Sierra delete commands.
● New storage for datestamp may be needed to be able to search -
33 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.7 release
Functional Requirements (what does it need to do?)
● New configuration option exists: OFF (default), ALLOW_IF_ANY_ORDERS_EXIST.
● When enabled, Sierra allows holds under the configured rule set.
● Given a bib has at least one on-order item when a patron attempts to place a hold, then the system allows the hold.
● The hold is added to the queue attached to the bib record or designated holdable item type per existing policy.
● No requirement to move Lucky Day items to a separate bib. -
17 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.7 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.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. -
48 votes
Support for a newer version of Jaspersoft Studio will be provided in Sierra 6.7.
An error occurred while saving the comment 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.
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.
-
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 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. -
26 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. -
11 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.
-
31 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. -
36 votes
An error occurred while saving the comment MEEP candidate for the Sierra 6.5 release
Functional Requirements (what does it need to do?)
• In the Global/Rapid Update functions, the list of review files to select as the target set of records is augmented with the "system-generated review files" available on the system, in the same way as the Create Lists "copy review file" action.
• A Global/Rapid Update task that targets a "system-generated review file" processes all the records in that file at the time it was selected. In other words, any subsequent updates to that "system-generated review file" (records added/removed, etc.) are not visible to the running Global/Rapid Update process.
• After the Global/Rapid Update process completes, any data related to the record range has been cleaned up (e.g., temporary files deleted, transient review files cleared, etc.).
• Existing review files in Create Lists are not used/modified by the Global/Rapid Update process.
AdminMike Dicus
(Product Manager, Innovative)
shared this idea
·
MEEP candidate for the Sierra 6.7 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.