Settings and activity
31 results found
-
44 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment -
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. -
28 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. -
50 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.
-
46 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. -
27 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.
-
34 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. -
38 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
·
-
10 votes
An error occurred while saving the comment Mobile Worklists supports dynamic font sizes as set on the mobile device. Are you looking for something different?
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.