318 results found
-
globally update bibliographic records with multiple branch codes
We would like to be able to globally add an additional bibliographic branch code to a subset of bibliographic records harvested through "create lists." This is because currently (Sierra 6.1), it is possible to change a bibliographic branch code, but not add additional ones while retaining the original branch.
The reason is that we have records for electronic resources that should display under a relatively new scope set up for a new branch. With only the original branch in the bibliographic record, it is necessary to view the entire collection (or the original branch) to access the item in the…5 votesThe product team will review this idea for consideration for a future release.
-
Simplify FTP login for vendor status reports
Description
Sierra will enter the FTP login information automatically when downloading vendor status reports when that information is saved in the system.Value
Makes it easier to retrieve files quickly and easily.19 votes -
Add "last status update" to low & high circulation weeding report results
A "last status update" column in the low & high circulation weeding report results would help identify items for weeding or stock rotation.
Why would this field help us weed or identify items for stock rotation?
This item field identifies the last date an item changed their status. Many libraries change an item's status to "in transit" when they move an item from one branch to another. To that end, this field could help identify items that have either newly been received to a branch, or have sat on the shelf for some time.Items moving around systems with stock…
1 voteThe product team will review this idea for consideration for a future release.
-
SAML matchpoint with patron variable field
We implemented Patron SAML and uses a patron variable field to be the matchpoint. This field contains the patron's email address. Our IdP accepts dots, dash and underscores in patrons' email address. Due to Sierra indexing rules where symbols (including dots, dash and underscores) will be dropped, different patrons with the same letters in their email address but have different symbols in different positions won't be able to authenticate through Patron SAML.
e.g. Patron A's email = abc.def@test.com, Patron B's email = abc_dec@test.com . Both will fail authentication as Sierra will use abcdef@test.com and return both patron records.5 votesThe product team will review this idea for consideration for a future release.
-
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.
-
Scan barcodes directly into Create List review file
The "import records" within Create List was a game changer. But going a step further would be adding the ability to direct scan barcodes into a review file. This would save time in circumstances where you have only a few records you need to update.
32 votesThe product manager will review this idea for possible inclusion in a future release.
-
Spending Limit Pop-Up
I know its shocking when the subject of pop-ups in Sierra comes up that anyone would want "MORE!," but our Acquisitions staff would like to see a warning of fund spending over limit at invoicing in addition to ordering.
Their rationale is that shipping & Mylar costs usually cannot be pre-determined. Once posting happens, the fund goes negative. Since there is no going back, like when you're about to go down the chute at the end of Splash Mountain, there should be a warning.
8 votes -
Make Vendor Payment Info More Readily Accessible
The vendor payment address should be accessible at invoice payment function. Currently, the invoicing function needs to be closed & address information accessed at order record, vendor, etc.
9 votes -
Reading History via API
At this time it is apparently possible to retrieve the patrons Reading History via REST API sorted by date (oldest first or newest first). The most requested API enhancement request for us is to be able to retrieve the patrons Reading History via REST API sorted by Title. Another enhancement request is to be able to retrieve the patrons Reading History via REST API sorted by Author. This would be useful since users may have hundreds of items in the reading history.
6 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
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.
-
Connect Global Update with Scheduler
We complete many repetitive tasks in cataloging and patron record management each day. This entails using Create Lists to generate the list, and then using Global Update to perform the same set of edits each time. We need Scheduler to be able to connect into Global Update to perform those tasks automatically.
This may require enhancement of Global Update to save the Command Input, or it might mean adding the Command Input choices to Scheduler.
Example:
Scheduler runs an updated Create List using a saved search query to identify items that need their suppression code updated.
It then uses a…20 votes -
New Linked Patron logic : Link a patron record to a second patron with no reciprocal link.
Why is it important to link patrons?
- Without linked patron functionality someone that is authorized to pick up a hold on another account is complicated. This is manually done by staff using patron notes, and the authorized patron signs out the book leaving the original hold on the other patron record.
- Parents visiting the library with children would like to jump to the record of each child rather than using the child’s cards.
Current privacy and circulation workflow issues:
- Someone could link to the child record without authorization. If a patron is sharing their circulation details with someone, they should…
8 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Allow SIP2 AF field to offer alerting patrons to pending expiration.
That way other devices such as self checks can show that warning to the patron in the case of them checking out items and having the due date shortened to their expiration date instead of the full borrowing period for the item. If they were alerted they could contact staff to update their account and any item due dates that were shortened to their prior expiration date.
8 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Always be able to freeze a hold in catalogue(s)
Provide Libraries with the option to "always be able to freeze a bib or item level hold".
If circulation/OPAC rules allow a customer to place a hold, the customer should always be able to freeze it.
At this time, customers cannot freeze a bib level hold if there is an item attached to the bib that could fill the hold. Customers tell us that they want to manage their holds. They are unsure of a "Not Needed Before" date, but they know that they do not want to fill the hold immediately.
This is important for libraries that split out…
22 votesThe product manager will review this idea for possible inclusion in a future release.
-
Add New Patron Block Based On # of Items Claimed Returned
During the Circulation Forum at this week's IUG, a few libraries brought up their continued interest in going fine free, but also shared how they still faced challenges within their respective institutions from those who felt materials would not come back.
This is a realistic concern, especially for libraries that couple going fine free with the protracted loan periods made possible by autorenewals. It can sometimes be challenging to get customers to return things, so we appreciate the availability of patron blocks that will prevent checkouts, renewals, etc., but not penalize a customer financially, like the ability to suspend borrowing…
8 votes -
Provide direct access to Decision Center's Title Details page
One of the nicest features in Decision Center is the title details screen, which you can access by clicking on a title in the handful of reports that include title entries such as the Popular Titles Report.
However, if you're logged in and happen to know the URL structure for those pages (https://[your Decision Center URL]/report/titleDetails/[bibnumber]) you can actually pull up the information for any title in your database directly.
I'd like to see a means for navigating to that screen more directly and just expose this awesome feature of the platform that already exists. I envision a simple page…
4 votesThe product team will review this idea for consideration for a future release.
-
It's about time to make Holds APIs first-class citizens
Idea Description
It would be far nicer to have the ability to work with hold data directly--in contrast to having to retrieve hold data via the patron APIs. For example: currently, in order to (reasonably) find the "pickupByDate" values for holds with status "(Bib, Volume, Item) hold ready for pickup" you would have to use a combination of the Sierra SQL feature (to first find all the patron record numbers possessing such a hold) and then filter all the holds for the list of patrons (from the previous step) having the "pickupByDate" key in the response object. Once you have the holds,…14 votes -
Allow notices to be sent to e-mail addresses entered in separate fields.
In Sierra we have to add additional e-mail addresses comma separated in the same field for Print template notices to be sent to more than one address.
Right now we are implementing Vega Discover and there patrons can add additional e-mail addresses. They end up in separate e-mail fields in Sierra though and doesn´t work for Print template notices.
The integration built for us between IMMS and Sierra does pick up addresses from all e-mail fields to send out pick up notices for holds.So it would be great if this could also be the case for Print template-notices from…
11 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Fix truncated Z39.50 server names in SDA
Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.
The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.
As-is, the "Selected Databases" dialog can be dragged wider by the…
4 votesThe product team will review this idea for consideration for a future release.
-
New function to scan items into Sierra to change an Item status to "in transit"
Our branches select which items should be sent to another library for stock rotation. Before items are sent to another branch, staff change the item statuses to "in transit". For various reasons, the branch staff cannot use Mobile Worklist to batch change these items to "in transit". The staff use Circa, but would prefer a Sierra integrated solution.
Why integrate this solution in Sierra:
Circa is aging out. We cannot limit Circa permissions to only change Item status to "in transit".
We want to use the "item status update date" to track when items last moved to a branch.
We…
1 voteThe product team will review this idea for consideration for a future release.
- Don't see your idea?