293 results found
-
NCIP activity should update Circactive
Currently, authentication using the NCIP protocol does not update the CIRCACTIVE attribute in the patron account. We use this protocol to authenticate to a statewide ILL service and we'd like to know when cards are being used in this union catalog and not just our own.
We use CIRCACTIVE to determine which cards are being used and which ones aren't. This is useful for statistical purposes, but is also linked to our patron database purge process.
8 votesThe product team will review this idea for consideration for a future release.
-
Increase Max Size of Item Code 1 Field
The Item Code 1 field was going to solve all my statistical issues. I thought it had 5 characters and each character could be 0-9 which meant I could assign a meaning to each character. For example, the first character indicates agency (1 for CPL, 2 for ADL, 3 for BKM) and the second character indicates audience (1 for adult, 2 for young adult, 3 for juvenile, 4 for other) and the third character, format, etc. HOWEVER it turns out that the largest number this field can hold is 32767 which is weirdly random and very limiting when you want…
5 votesThe product team will review this idea for consideration for a future release.
-
TODAY Command
Similar to the keyboard codes (ex. %ENTER%), it would be useful to have a command code for today's date. In item records, we input the current date in a 995 field using a macro but must update our date macro each day. Being able to have a command for the current date would save time and lead to fewer errors when users forget to change the date.
2 votesThe product team will review this idea for consideration for a future release.
-
Have system-generated review files appear in the drop-down list in Global/Rapid Update
Idea Description
If system generated review files could appear in Global Update/Rapid Update Review File dropdown list without even downloading them to Create Lists first that would save so much time.It's a normal part of my daily workflow to upload records using Mobile Worklists or Data Exchange, copy them into Create Lists and manipulate the file in Global or Rapid Update.
Idea Value
With the file appearing in the dropdown list in Global/Rapid update, the file can be manipulated as usual AND users wouldn't have to remember to empty the Review File (which was only created so it could…35 votes -
Notice Count Should Be A Count Of Notices Not Items
Since becoming a III customer in 2008/2009, it's baffled me that we don't see a representation of the total number of notices sent daily via autonotices, but instead see the Notice History feature, which shows the number of items for which notices are sent.
I think it would be far more useful for statistical purposes if the number of notices sent for each notice type was what's recorded & shared by Sierra.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Don't allow Scheduler to save passwords it can't use
I just learned that Scheduler Output MARC records can't send an FTP password that includes the characters [{}"/
It will let me save a task with such a password and spend months trying to figure out what's wrong. If it can't deal with a particular password, it should give an error saying what's wrong with the password.
7 votesThe product team will review this idea for consideration for a future release.
-
Add Sierra Hold Request Date into Hold cancellation notices
Support team told us Sierra isn't designed to supply hold request date for cancellation notices. Please consider add it. thanks
5 votesThe product team will review this idea for consideration for a future release.
-
Allow users to define icode1 in Sierra
Our library uses the icode1 field as a statistical category code. We'd like to be able to define our icode1 values, with codes and labels stored in Sierra and visible to staff. Currently we keep a list of codes and their meanings stored in a shared drive and have to share it with our cataloguers. Staff can see the "stat category" field in item records, but there's no translation anywhere in Sierra and the userdefinedicode1_myuser SQL view is blank.
23 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
More Granularity in Hold Blocks
Currently, the ability to override a hold block is governed by permission 92.
A hold might be blocked for a number of reasons. Staff might attempt to place more than the max number of holds allowed for a customer. They might place a hold for a customer on an item they already have checked out, etc.
One scenario especially has been problematic for as long as I can remember:
A patron finds an item on the shelf & takes it to a service point to check out. It turns out that this item can satisfy a hold placed by another…
7 votesThe product team will review this idea for consideration for a future release.
-
Require authentication to view Sierra API documentation
Enhance cybersecurity by not revealing the api methods through the swagger interface to unauthenticated users. For example, a potential hacker can view the swagger interface which shows all methods and explains how to use them. This is an issue on all api endpoints including the iii sandbox. My idea is to only reveal the swagger methods to authenticated users.
https://sandbox.iii.com/iii/sierra-api/swagger/index.html#!/patrons
6 votesThe product team will review this idea for consideration for a future release.
-
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…
2 votesThe product team will review this idea for consideration for a future release.
-
Allow Requiring SAML for Sierra Web
Sierra now supports SAML for authenticating staff, but still allows users to authenticate without MFA using the less secure Sierra legacy authentication method. Sierra should allow administrators to require SAML authentication instead of always allowing users to choose SAML or Legacy.
4 votesThe product team will review this idea for consideration for a future release.
-
Create user permissions/roles for limiting SierraDNA access
We have had a number of instances recently in which a vendor has requested SQL access in order for us to utilize there services. We are hesitant to allow for that (and have policies against it) due to the quantity of secure data that would also provide access to.
What we need is a way to provide lesser SQL access to particular users to allow them to tap into only the relevant tables (bibs & items for some. Circ_trans and patrons for others).
Beyond the vendor scenario it would also be fantastic to provide limited access to more of our…
13 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
-
Ability to change password on login page of SDA
Many libraries are creating individual logins for each staff member. Staff needs the ability to change their password in case they forget it. At this point, they need to be logged into the SDA to change their password which doesn't help if they can't remember it.
17 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add a Note Field in the RFID Pad Server Options Table
As ILS administrators of a large consortium, we would like the RFID Server Options Table to have an additional field/column to add notes (library name, dates, staff initials). When one of our member libraries needs to change RFID entries, we sort through nearly 200 lines to determine which one needs updating. Many entries use IPs without identifying library information. We must read through old library correspondence to discern which IPs belong to the library. This task takes up valuable time when we are trying to assist a library with troubleshooting or adding and removing entries.
An additional free-text field to…
13 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Release Item Price Field in Sierra Item Record for SIP2
Libraries using SIP2 connections for self-checks cannot have due slips that have "You Saved" information because the Item Price field is not available via SIP2.
While due slips with this information can be used at a staff station with the SDA, as more and more libraries move to self-check, the lack of this field's availability in SIP2 is a barrier.
Use case: a library has a self-check machine that uses SIP2 and wants to include "You Saved" information on their due slips.
12 votes -
Increase Sierra Username Character Limit
We need to increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a user's network login name (one less thing to remember). Anything over 12 characters forces us to make a different Sierra username that fits within the Sierra parameters.
11 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Batch Shuffle Hold Queue
We would like the ability for authorized/admin level staff to collectively shuffle multiple holds, so those at the bottom of the queue can be selected & moved to the top. Their order at the top wouldn't necessarily matter, as long as the group were all advanced in the queue.
Use cases: item recalls, where tech services staff have to place dozens of holds on items, all of which wind up at the bottom of the queue & need to be shuffled individually/manually.
Book club: we had a situation recently where staff at one branch cancelled holds on book club items…
1 voteThe product team will review this idea for consideration for a future release.
-
Remove duplicate items on paging list
Duplicate instances of a single item frequently appear on Bib Paging Lists resulting in confusion and either wasted paper (up to 7 pages were printed for a single item once) or wasted time deleting those lines before printing. There is no need for the paging list to alert us to multiple holds for any item, especially if we can't physically fulfill those holds.
36 votes -
AI Clean Up Functionality - Sierra
I understand that III is planning to incorporate AI functionality into the Vega platform (newsletter text, website content, etc...). I think it would be really useful to have AI data cleanup functionality developed for Sierra.
I'm not sure exactly what this would look like but here are some potential ways this could improve catalog metadata:
- catalog record cleanup (bad codes, incorrect codes, codes inconsistent with local practices for similar records, etc...)
- patron record cleanup (bad codes, codes inconsistent with similar-type accounts, etc...)
- automatic tagging of demographic (we use one of the patron codes to indicate reciprocal library…9 votesThis idea will be reviewed by the product management team for possible inclusion in a future release.
- Don't see your idea?