265 results found
-
Allow the "remember me" in Sierra Desktop App login screen to remember passwords as well as username (as previous versions of Sierra did)
Previous versions of Sierra (version 5 and below) allowed the saving of usernames and passwords in the Sierra desktop app login screen. Since upgrading to 6 this functionally has been lost.
9 votes -
Save title and author info in reading history after title is deleted
Customers want to know what titles they've checked out even if the library no longer has it. It would be ideal if Sierra (and subsequent discovery layers can pull the info) could save the title and author in the record metadata so that even if the bib record is deleted, the customer can see it.
20 votes -
assign 1st and 2nd tier timeout permissions (for those using context logins) : SDA and Sierra Web
In the SDA OR Sierra Web, the Sierra 2-tier login workflow allows administrators to set a "time-out" setting to the 2nd tier (personalized) login. This setting determines if the session will time out or close after a specific amount of time.
This is an excellent workflow except that there is no setting to manage 1st tier inactivity. This means at the end of the day we have many Sierra licenses that remain open and the Library must manually force close the desktop applications using the "restart a process" in Admin Corner.
Please configure context logins so that Libraries can determine…
4 votes -
Generate Statement of Charges directly within patron record
It would be very helpful to be able to print a Statement of Charges directly from a patron record (and have it formatted for 8-1/2 x 11 paper and mail-ready).
For context, we are a 138-library consortium, all notices are Auto Notices, and we do not run Statement of Charges for the consortium. Yes, you can run a statement for 1 patron in the Notices function, but this requires consortium staff intervention since that permission is locked down to consortium staff. It would be much simpler for our member libraries to be able to print such a statement on an…
16 votes -
Choose Priority between Item-level holds queue and bib-level holds queue
More control over choosing priority between the item-level holds queue and the bibliographic-level holds manually so that the Processing department can pull back specific items on popular, high-volume holds with more ease.
3 votes -
Decision Center: Identify titles eligible for stock rotation in pooling locations
We have a floating collection and use Decision Center to manage our collection. We need to know what is on the shelf OR not on the shelf at multiple sites. To do this, we use excel pivot tables to manipulate the "low circulation weeding reports". I have attached the workflow and the result.
After pivoting the "low circulation weeding reports" (searching for items that have circulated less than 300 times in 1 month at multiple branches) our result includes everything on the shelf at multiple branches. The pivot table allows us to identify which titles are at a branch AND…
3 votes -
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…
21 votesThe product manager will review this idea for possible inclusion in a future release.
-
REST API security enhancement request: Assign granularity to API role permissions
Objective: Allow Libraries to assign granularity to API role permissions.
When Libraries give a 3rd party vendor read access, we want to be able to restrict the endpoints associated with the role. In addition, we want to restrict the fields that can be returned. Ideally, the implementation of the requested features below will provide an interface to the Innovative clients where the vendor access will be managed.
There are endpoint and field restriction examples below to show how assigning granularity to API role permissions would allow libraries to improve access management.
Endpoint restriction example:
We would like to be able…6 votesThe product manager will review this idea for possible inclusion in a future release.
-
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.
29 votesThe product manager will review this idea for possible inclusion in a future release.
-
Decision Center: Pooling Report not based on demand
The Pooling Report generates a list of titles where "the pooling branch has more copies than it needs to meet 150% of demand". This is not the only reason that multi-branch libraries with floating collections have pooling collections.
Items in a floating collection can be returned to any location.
Could we have a pooling report that identifies:
1) Titles that have never been assigned or checked out at the location of the drought location
AND/OR
2) Titles not held at the drought location
Thank you,
Elizabeth2 votesThe product manager will review this idea for possible inclusion in a future release.
-
Customize default item view based on function
It is currently an option to be able to set the default view of an item record across Sierra. However, it would be nice to be able to have a different default view set for the different functions in Sierra.
For example:
When in the Circulation function - I'd prefer the default view to be Hold.
When in the Cataloging function - I'd prefer the default view to be Item.
When in the Acquisitions function - I'd prefer the default view to be Order.I understand that I could just have multiple windows open and set the default view differently…
21 votesThe product manager will review this idea for possible inclusion in a future release.
-
Restrict Location Code Edits to Locations in Scope (especially in Rapid Update)
There is currently a setting allowing us to prevent logins from editing records with a location code outside of their current scope. However, users are able to edit records in their scope to have location codes outside of their scope, which then blocks them from being able to edit the records again. This happens accidentally sometimes, and is particularly a problem in Rapid Update. It would be great if item location dropdowns in Rapid Update, and possibly the item record as well, only showed locations in the user's scope in order to prevent this problem. Alternately, the system could prevent…
17 votesThe product manager will review this idea for possible inclusion in a future release.
-
Granular Permissions on Item Record
We would like to see more specific permissions on items records to allow staff who don't have access to edit entire item records to be able to do basic things like add and delete item messages or change the status of the item.
Frontline staff are discovering outdated item messages or finding that items are missing, and it's inefficient for them to have to contact someone else to change the status of the item, or delete an item message attached to it.
14 votesThe product manager will review this idea for possible inclusion in a future release.
-
Add ability to add/store PDF documents in patron records
I know that there is a product called External Patron Images that would allow patron photos to display in their records. I am wondering if a similar product exists for documents (such as PDF)? For some of our lending items, patrons must sign a user waiver to agree to the terms and conditions, and we currently have a two step process to verify if this has happened each time they come in. It would be good to be able to add the scanned image of the waiver to a patron record for easier verification.
7 votesThe product manager will review this idea for possible inclusion in a future release.
-
Allow patron to set thaw date of frozen holds
Allow patrons to set a thaw date when freezing holds. Patrons often forget they froze holds and the hold lingers until it expires. Also, make this information available in the API for third party vendors, such as discovery layers.
26 votesThe product manager will review this idea for possible inclusion in a future release.
-
"Both" Option for Due Slip Delivery
The first request we got after releasing emailed Due Slips was for the option to generate both an email and a print slip. Some people like the physical reminder in the form of a printed slip (that doubles as a bookmark!) and an electronic version that they can use as a reminder or a fallback.
18 votesThe product manager will review this idea for possible inclusion in a future release.
-
MFT support in data exchange
Prior to Sierra 6.0 and the introduction of MFT, it was possible to use FTP to transfer files though data exchange within Sierra. This is no longer possible as MFT is not supported in data exchange.
Please add support for MFT in data exchange in the same way as support for MFT has been added in scheduler.11 votes -
Allow Global Update of Fund Codes
Allow for Global Update of fund codes. I work in an academic library and will often get purchase lists from our liaison librarians for a specific department. The records are brought in and the attached order records are edited in GU with the correct vendor, and selector, etc. It would be a time-saver if I could also update the fund code (which are tied to academic departments) at the same time.
14 votes -
Allow sorting options for API Results
An example of this is the Items/GET API appears to sort the results based on catalog date/item id of the item. It would be nice to specify a different sort parameter that would allow the current sort or a new sort which would return them in the same sorting specified in the Cataloging function in Sierra.
This might be nice for other APIs as well.
5 votes -
Insert name, date of birth and address using an ID scanner
I am wondering if Sierra can be adapted to automatically insert name, date of birth and address using an id scanner, such as those used at grocery stores when verifying a person's age. This would save staff the time of manually entering this information into the appropriate fields. It would also allow less typos and/or other mistakes when inputting the information. Of course, having the manual option would still be necessary.
8 votesThe product manager will review this idea for possible inclusion in a future release.
- Don't see your idea?