179 results found
-
Eliminate the two-tiered (context) logins that identify branch locations and personalized user
Several years ago we adopted context logins. We have established that a 1 tier login will not work for us.
CURRENT STATE : Our Regional Library consists of 39 branches in almost as many cities. To distinguish the branch of our Sierra users we currently use a two-tiered login. This login process allows us to continue to use generic branch accounts while meeting our obligations to protect customer information. The two-tiered login allows us to collect branch-specific data and apply unique user settings, options, and settings.
The drawback is that our staff must login twice and it may pose an…
6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Add a shortcut to print out patron barcode
When staff opens a patron's record, add a shortcut feature that allows them to print out patron barcodes. This will really help when someone comes in and don't have their library card with them, so wants to get their barcode information
4 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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…
10 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
10 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Improve item title display on patron-facing devices by adjusting SIP2 parameters
Skip certain MARC subfields when preparing data for SIP2 connection.
Specifically:
When Sierra needs to send information to display an item title on a patron-facing device (automated materials handler, self-checkout kiosk, etc.) via SIP2, it currently appears to concatenate all occupied subfields of MARC field 245 and remove the delimiters. This means that certain information not intended to be patron-facing can end up appearing in the title the patron sees on screen (e.g. "880-01 Desu nôto 2..." appearing instead of just "Desu nôto 2...", where "880-01" is not actually part of the title, but rather a reference to another field…6 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.
-
The Z39.50 Server and Authority Records
Searches of Innovative databases that contain authority records using Z39.50 search do not return authority records.
The ability to search for an authority records would contribute to the quality of the database and make it easier to generate linked data.
5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
2 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
12 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Charge type on fines tab needs to specify if it is a damaged item
Would love to see the word "replacement" changed to a word that gets at the actual status. Currently the charge type of "replacement" is used for a long overdue item that has been billed or a damaged item that has been billed. To find out if the item that has been billed is damaged or just hasn't been returned you have to go into the item record to see if a damaged note has been added.
6 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Allow for Diacritics in E-mail Receipts
We've been exploring new ways that our library, as an institution, can meet the evolving interests of DEI efforts. One very small but meaningful way we thought we might do this is to allow for the inclusion of diacritic characters in customer names in Sierra.
Their inclusion appears as desired on the customer record when created/displayed in Sierra (images dia1 - dia2).
They do not appear to impede searching for the customer by name - the search just ignores them (images dia3 - dia4).
They appear as desired in the name display in the Classic Catalog (image dia5).
They appear…
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Notify the library staff of new ILL requests via email
An option for Sierra to notify the library of new ILL requests via email rather than a staff member manually checking the new requests function.
4 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
15 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Protect local-only MARC fields that have a specific subfield coding
There are instances where its appropriate to put in a MARC field in the bibliographic record that only pertains to your local institution and you wouldn't want that field erased if the record was overlaid. If that MARC field was designated a local-note, using a $5 then that field would be "protected".
8 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
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.
-
Customise Encore 'Did you mean' offerings to prevent offensive suggestions
We've had a couple of instances where the Encore 'Did you mean?' suggestions have offered up inappropriate alternatives to the search that was performed.
The first example was that it suggested 'sex manuals' when a search for 'car manuals' was performed.
The second example was that it suggested 'American poets' when a search for 'African poets' was performed, to which our client took offense at.
We would like to see some functionality added to Encore that would allow us to customise what suggestions display and what do not display for the 'did you mean' algorithm. This would allow us to…
1 voteThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Make Third Party API Transactions More Apparent for Sierra Customers
Some time ago, an idea was submitted to enhance the Sierra API to provide statistical group information, so that circulation transactions in third party applications could be credited to a statistical group other than 0 None.
The idea won the "Let's Connect Sierra API Challenge."
With the release of Sierra 6.0, it then became possible to include a new optional data parameter to specify the statistical group that should be used when recording a transaction performed using the APIs.
My library was excited to hear this, as we'd recently begun using the self-checkout feature in the Bibliocommons' app not long…
5 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
2 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Penalty points for patrons who reserve books and then don't pick them up at the library
Currently, on Sierra it is possible to block patrons based on overdue penalty points (OD PENALTY) when they check in or renew overdue items. This is done with the patron fixed field OD PENALTY. The system calculates the penalty points that have to be added to the patron record and when a patron exceeds the maximum number of penalty points allowed by the library, the patron is blocked. More info at https://documentation.iii.com/sierrahelp/Default.htm#sgcir/sgcir_fine_penaltypoints.html
THis feature is very useful. Wouldn't it be a good idea to be able to apply a similar strategy for patrons that request a hold on a bib/item…
9 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
-
Make the hold status information updatable in API
There is currently no way to update the status of a hold in the API.
It would be very useful to change the status from
"status": {
"code": "0",
"name": "on hold."
},to
"status": {
"code": "i",
"name": "Requested item ready for pickup."
},Enhancement to be integrated into https://ideas.iii.com/forums/951745-ils-sierra/suggestions/47618129-it-s-about-time-to-make-holds-apis-first-class-cit ?
2 votesThis idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
- Don't see your idea?