281 results found
-
Attach new volume from Serials Checkin function
We'd like the ability to be able to attach a volume record from the Serial Checkin module. This would save time and make the serials module more useful.
4 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Additional Collection Summary Reports in Decision Center
We would like to have a collection summary report based on item records with a count by item type and location. If possible, adding a limiter for circulation status, for example on shelf or checked out.
4 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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 -
Translate item status and OPAC message codes in Summary View
Currently, it's possible to have item status and OPAC message codes displayed in the summary view. However, we'd like the option to display the full names of these statuses/messages rather than the codes to make things clearer for staff who don't have them memorized.
3 votes -
Include items checked in via selfcheck in Homebound Patron Reports
Sierras Homebound Patron Report currently excludes items that are checked in via selfcheck (SIP2). Since almost all check-ins in our libraries are done through selfcheck machines, the report provides an incomplete history and is not usable for tracking items checked in for homebound patrons.
Please update the report logic so that all check-in methods, including selfcheck check-ins, are included. This would ensure accurate reading history and make the module much more useful for libraries that rely on automated check-in workflows.
3 votes -
Support SRU (Search/Retrieve by URL) in addition to Z39.50
Sierra supports Z39.50 but not SRU. Remote search and import/overlay of records from SRU-only sources seems to be increasingly important. We have begun to encounter potential partners who are no longer able to offer Z39.50 access because their systems only support SRU; likewise, we would like to be able to offer SRU ourselves to maximize interoperability.
GPL-licensed software is available to add SRU support to Z39.50-capable systems such as Sierra (for example, CQL-Java, yazproxy and metaproxy):
https://www.loc.gov/standards/sru/
https://www.indexdata.com/resources/software/cql-java/
https://www.indexdata.com/resources/software/yazproxy/
https://www.indexdata.com/resources/software/metaproxy/3 votes -
Improve server security by supporting Apache module mod_security
With the increase in bot attacks causing DOSS downtime, it is important to be on top of server security. The Apache module "modsecurity" has been around for over 20 years and there is an active community creating rules (https://coreruleset.org/) to block bot attacks. I think that Innovative should include modsecurity in their Apache build and actively support or provide the option to its customers to include rules to increase server security.
3 votes -
Clear and Set Permissions at one go
We have implemented SDA Context User functionality so staff will open Sierra using shared library login and then add their own login (permissions). We would hope faster way to change the user. At this time you must first remove previous user (Admin - Clear Permissions) and then add new user (Admin - Set Permissions). Staff suggested one function that would both Clear previous and Set new Permissions. E.g. Set Permission could remove the old user and then ask the new user. We set up macros for both functions so staff can use them instead of drop-down menu. However, I suppose…
3 votes -
Expand the options tied to permission 109, update uncataloged records
Currently Sierra permission 109, update uncataloged records, is tied to whether or not the bib record has a CDATE (no catalog date) field. It would be great if permission 109 could be customized by a library to be controlled by another option outside of just the presence of the CDATE field. For example, we use field 31 to control the level of cataloging of a record (including full MARC) and to suppress the bib. It would be helpful if we could tie the codes from that field to this permission. It's worth mentioning that permission 109 and the presence of…
3 votesThe product team will review this idea for consideration for a future release.
-
Make printer option defaults available by workflow, and have "send to email address" send only to staff email addresses
This is two fold. First, we would like to be able to set a default printer option determined by the staff users workflow (circulation workflow/function would default to "email to patron", and cataloging function would default to local printer, etc). So staff log in and select their function area and the system uses a specific printer default accordingly.
Secondly, we would like to have the "Send to email address" printer option changed somewhat. When selected, it would have a drop down of emails available to send to. These would be set up by the system admin. It would reduce the…
3 votesThe product team will review this idea for consideration for a future release.
-
Disable Reprint bills button In Sierra
We can’t use this button because we don’t use print templates for our bills.
We would prefer them to look pretty with Print Templates instead of the plain text we currently have. To avoid staff confusion, it would be great if this we had the ability to disable/grey out this button.3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
NCIP Authentication - Add support for optional blocking
We recently started using NCIP authentication for our new ILL service. We learned after implementation that NCIP login is blocked for any of the reasons in the Patron Block Table. This makes sense when the block is for an expired card, or for fees over the threshold. This makes less sense when they have reached their maximum holds in Sierra.
What we're seeing is that patrons cannot log into the system at all when any of the block parameters are true. We would like to be able to enforce certain blocks but not others for account login.
We can increase…
3 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Split the Patron_Name in the Item Paging Slip and Item Paging List data libraries into first name and last name
The element PatronName in the Item Paging Slip & Item Paging List Data library be broken up into Patronfirstname and patronlast_name elements like in the hold/transit slip data libraries.
3 votes -
Ability to import Create Lists Review File into Decision Center
Collection and circulation analytics would improve if we could import Create Lists item/bib search results into Decision Center.
If so, Decision Center could aggregate Create Lists results (searches based on authorities, orders, or hold/patron circulation behaviours) to provide circulation and collection statistics.
Our libraries would be satisfied for this import to display the fields that are in the “high”/ “low” circulation weeding reports.
We understand that the aggregated statistics in Decision Center are generated the night before.
3 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Modify Estimated Price Via Rapid Upate
Our Acquisitions staff does not use List Price when ordering, & is hoping that Estimated Price could be modifiable via Rapid Update. At the moment, this would help them modify 200+ order records, which they now have to do manually.
3 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 -
Add "Send to Batch Check-in" Navigation to Create Lists
Building on the recent navigation enhancements that allow users to send Review Files from Create Lists to Rapid Update, Global Update, and Delete Records, we propose adding a "Send to Batch Check-in" option.
Now that Batch Check-in has been integrated into the Sierra client (as of the 6.5 Release), adding this "Send to" functionality would significantly streamline workflows and reduce the risk of errors associated with file handling.
2 votes -
Redirecting Duplicate Copies at Check-In
For libraries using floating collections, the system should support automated redirection of duplicate copies at the point of check-in to other branches that do not currently hold a copy of the title.
The system should surface eligible destination branches automatically, eliminating the need for manual title-level analysis by staff.
In multi-branch library systems, the workflow should allow configurable prioritization rules to determine the destination branch when redistributing items.
Prioritization logic could be applied in the following order:
1) No copy of the title is currently available/on the shelf at the receiving branch
2) Title (or item if not possible) has…2 votes -
Remove leading diacritic from normalised author fields
Sierra currently removes any leading apostrophe for example from the normalised author fields on bibs. For example, normAuthor over API. Other diacritics such as ʻokina (ʻ) is not removed from normalised fields. Because of this, any systems that use norm fields over API are not alphabetising the author correctly.
It would be great if Sierra could remove the ʻokina (ʻ) from the normalised author fields. Specifically normAuthor.
2 votes
- Don't see your idea?