Settings and activity
31 results found
-
22 votes
An error occurred while saving the comment An error occurred while saving the comment MEEP candidate for the Sierra 6.7 release
Functional Requirements (what does it need to do?)
● Ability to configure claimed return-based block as part of the library’s loan rules
● Trigger block when claimed returned count increases to and beyond the limit.
● Enforce block during checkout, renewal, hold pickup and ILL transactions.
● Allow manual override by staff in Circ Desk transactions.
● Use existing “Override patron blocks” permission (98)
● Provide appropriate error messages when a circ transaction is blocked.
● The claimed returned count is decremented automatically when CR items are checked in.Notes on “Override patron blocks” permission (98)
Note that the system only requires this permission if the Check-out: Authorization required to override patron block circulation option is set to "YES". -
71 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 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 searchAn 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 -
52 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 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.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. -
46 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 7.1 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.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. -
35 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 7.1 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.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 7.1 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.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. -
35 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
*As a library staff member, I can recover the output of failed notices and expired holds & holdshelf reports and run them again without needing to re-create the data through laborious processes that may produce inaccurate results.
-
19 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
*As a library admin, I can enter a date range to add or delete entries in the Days Closed table.
-
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 7.1 release
Functional Requirements (what does it need to do?)
*As an API user, I can retrieve circulation transaction data using an API for use in various external applications.
-
31 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 MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
*As a library admin, I can enter labels in Sierra to explain the codes I have defined in the icode1 table.
*As a library staff member, I can see the labels assigned by my library to the codes in the icode1 table so that I understand what the code means.
-
19 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
*As a staff member working in Global Update, I can copy selected records from a review file into a new review file so I can work directly on a subset of the records without changing the original review file.
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
As a staff member working in Global Update, I can copy selected records from a review file into a new review file so I can work directly on a subset of the records without changing the original review file.
-
12 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
*As a library staff member, I can see the process (program) that was used to create or update an item record in the item record history.
-
12 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
*As an API user, I can create a new review file from a list of record IDs that I supply via API.
*As a staff member using Create Lists, I can identify review files that have been created via API rather than by query.
-
28 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 release
Functional Requirements (What does it need to do?)
As a library admin, I can define patron checkout limits by grouping item types into a single rule.
-
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 7.1 release
Functional Requirements (what does it need to do?)
*As a library admin, I can define a patron block based on the maximum number of overdue items.
*As a library staff member, I trust the system to block patrons who have reached their limit of overdue items and prevent them from checking out additional items.
*As a library staff member with permission to override patron blocks, I can override the block on max number of overdue items.
*As a library patron, I can see the reason when I am blocked by having reached the library's max number of overdue items.
*As a library patron, I can return or renew library materials to clear the block based on a max number of overdue items.
-
16 votes
An error occurred while saving the comment MEEP candidate for the Sierra 7.1 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.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. -
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.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.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. -
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. -
34 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.
MEEP candidate for the Sierra 7.1 release
Functional Requirements (what does it need to do?)
● Ability to configure claimed return-based block as part of the library’s loan rules
● Trigger block when claimed returned count increases to and beyond the limit.
● Enforce block during checkout, renewal, hold pickup and ILL transactions.
● Allow manual override by staff in Circ Desk transactions.
● Use existing “Override patron blocks” permission (98)
● Provide appropriate error messages when a circ transaction is blocked.
● The claimed returned count is decremented automatically when CR items are checked in.
Notes on “Override patron blocks” permission (98)
Note that the system only requires this permission if the Check-out: Authorization required to override patron block circulation option is set to "YES".