266 results found
-
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.
-
Login indicator
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 better indicator (e.g. color) so it would be easier to notice if personal login/permissions is added or not (or if someone has forgotten to remove their personal login/permissions). At this time when you open Sierra using the library login you can see "Sierra" and "local system name" on the upper left corner (in our case Sierra Helmet). When you add personal login your name (user account full name) will display too (in our case…
1 vote -
New Search Limit for Manage Holds
We're currently dealing with a known issue in Sierra 6.2, where volume holds aren't being added to paging lists. Having discovered it on our end fairly recently, we've asked staff to continue running their paging lists for other items, but use the Manage Holds function to find & fill volume requests.
The problem is that the current search retrieves such a high number of items. And while the search results display counts of the title number of holds, & the total number of bib, volume, & item level holds, you cannot currently limit them & make the Manage Holds report…
7 votesThe product team will review this idea for consideration for a future 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…
2 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
6 votesThe product team will review this idea for consideration for a future release.
-
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.
-
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.
8 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…36 votes -
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.
5 votesThe product team will review this idea for consideration for a future release.
-
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.
-
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.
24 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.
-
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…
15 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Increase Invoice Limit for Downloaded Invoices
The current cap of 99 invoices downloadable per day can impede & dictate staff workflows.
Because of this, our Acquisitions staff must also set limits with vendors like Baker & Taylor, as we can receive more than 99 in a day. It would be optimal if they could download at will up to invoice limit.
Not all shipments are dealt with sequentially, which further complicates matters.
13 votes -
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.
18 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
42 votes -
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.
-
Update "last checkin" field even if item wasn't checked out
Update the "last checkin" field every time an item is checked in. Now, when you check in an item, the "last checkin" field is not updated if the item is not checked out. I don't know of any reason to not update it. When I look at an item record, I want to know the last date that the item was seen; this can be useful in tracking down items that seem to be missing, or coming up with a list of items that might be missing.
10 votesThis idea will be reviewed for consideration as an enhancement in an upcoming release.
-
Allow libraries to customize return addresses for bills
Our library would like the option to have the return address for bills reflect the address of the patron's home library (as defined in the patron record) rather than the owning location of the item. The current setup (using the owning location of the first item on the bill) means that when patrons check out items sent from another branch to fill a hold, they can receive a bill from a library that they may never have been to. While patrons can visit any of our locations to resolve a bill, we would prefer the bill to reflect their local…
6 votesThe product team will review this idea for consideration for a future release.
- Don't see your idea?