254 results found
-
Use Field long name for create list export
We've updated many of our data fields to have long names that make sense to front end staff who see patron and item records, however Create list sees the long name values when creating a list search, but the export of the data exports the system name. For example PCODE3 is called "Local Library" for our system, but a create list export defaults back to PCODE3. It would be nice to be able to export using the contexual long name so admins and create list users don't have to have a cheat sheet or remember what the system code is…
4 votes -
Enable Copying of Scheduler Tasks and Jobs
As a consortium, we schedule several monthly jobs/tasks for all 78 library locations. Scheduler does not allow you to copy an existing job/task and apply it to another library. We had to manually add each job, even though the majority of the parameters were the same. (78 lib * 5 tasks each is a lot of manual work.) And/or we should be able to create a template to reuse.
4 votes -
innovative_footer
The Innovative_Footer token for webopac does not have any CSS styles or identifiers associated with it so that it can be controlled through stylesheets. The footer is inappropriately placed on our website due to this lack of control.
Propose adding identifiers to the underlying HTML code so that it can be styled properly. Replace its <span> tag with a <div> tag might be appropriate.
4 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.
4 votes -
Show Sequence Number on Repeated Bills
We use the Repeated Bills feature, where after the bill is sent day 30, we send a repeat bill (#2) on day 40 and a final repeat bill (#3) on day 50. Unfortunately, when you run the Notice job for Repeated Bills, there is no way to tell whether the repeat being sent is for day 40 (#2) or day 50 (#3) except if you scroll through all of them and do the math as it pertains to the item status date. Staff haven't been doing that regularly. Ideally, there would be a column that showed you what # of…
4 votes -
Increase Max System Display Limit for Fines
Our library has very generous allowances for both checkouts & holds on patron accounts. This can sometimes come into conflict with Sierra's seemingly arbitrary system limits. For example, when these items go unreturned & result in replacement charges, which then cannot be added because of the imposed limits. Like my waist can no longer accommodate 32" pants, Sierra cannot currently accommodate the lending policies taken advantage of by some of our more active borrowers.
I'm sure there are other examples where these limits can manifest, but attached is an example message recently seen by staff which reads:
CANNOT ADD FINE…
4 votes -
RFID switching
One of our branches uses shielded RFID pads, and the software could hook in to their previous ILS and context switch the current RFID action (tag on, tag off, no change) depending on the active function screen by overlaying a screen over the ILS to track the toggling.
Can support for this functionality be offered for Sierra? I assume it would involve working with the RFID vendors to get it up and running.
The current workaround is to use Sierra macros to trigger the RFID function change, but this is reliant on staff remembering to press the keys which may…
4 votes -
Include the AA (patron identifier) element in the 10 Checkin Response for SIP2
When users return the materials via self-check machines, we want an email receipt to be automatically sent to them. Unfortunately, Sierra does not currently support the AA element in the 10 Checkin Response. Some libraries purchased the Patron API feature to get it to work but if Sierra include the AA element, it will simplify the process.
4 votes -
Fix truncated Z39.50 server names in SDA
Z39.50 database display names are limited to 50 characters in Admin Corner, but the contents of this field is truncated (at some length < 50) when displayed in the "Selected Databases" dialog in Sierra.
The 50 char limit may seem generous, but for multilingual organizations (and/or multilingual databases or those that just have long names!) it can already be a challenge to abbreviate the database name in each language to fit while still retaining sufficient information. Truncation of this field further reduces the functional length of the database name.
As-is, the "Selected Databases" dialog can be dragged wider by the…
4 votesThis idea will be implemented in Sierra 6.7.
-
Add alt tags to improve accessibility
A lot of alt tags appear empty by default and other accessibility issues seem to be outstanding. These two are examples that cannot be corrected by admins.
Add relevant tags to improve the accessibility of the search results page briefcit.html. The search box form has no labels that can be read by screenreaders:
Element Location: #searcharg
<input type="text" name="searcharg" id="searcharg" size="30" onchange="return searchtoolSubmitAction()" maxlength="75" value="[search term]">
The search history select element has no accessible name:
Element Location: .navigationRow[align="center"]:nth-child(5) > form > select[name="HISTORY"][onchange="onSelectChange(this, '')"]
<select name="HISTORY" onchange="onSelectChange(this, '')">
4 votesThe product team will review this idea for consideration for a future release.
-
Reflect Time to Holdshelf/Time to Reshelve status in SDA
Our library is interested in using the Time to Holdshelf/Time to Reshelve feature, but it doesn't really meet our needs. We've asked elsewhere (https://ideas.iii.com/forums/951745-ils-sierra/suggestions/51503123-rest-api-compatible-time-to-holdshelf-time-to-resh) for the temporary status to be reflected in the API so we can show it in our custom discovery layer. However, we'd also like it to be reflected in the SDA so that staff can see at a glance whether an item is likely to be on a shelving cart before going to (or directing a patron to) the shelf.
(Reviving Bob Gaydos' previous suggestion here: https://ideas.iii.com/forums/951745-ils-sierra/suggestions/48812237-time-to-holdshelf-delay-period-not-reflected-in-sd)
3 votes -
Access to SAML logs
When using the LDAP authentication option, it was useful to be able to see the authentication logs to diagnose login issues. After switching to SAML authentication, access to the SAML logs is only available to Innovative support.
I propose granting customers access to the CAS Apereo application logs so that we can see SAML authentication issues. These logs may not be as detailed as the LDAP ones since the authentication is happening at the IdP but they might provide clues to further investigate authentication issues.
3 votes -
Two First Names, No Last Name
We periodically have customers that have two first names, but not a last name. When hold slips are printed, Sierra interprets the second name as their last name, but this is not the case. We would like to just have their two first names show up on the holds slip, if possible. We have done a workaround for now to ensure that the name they use is the second name listed so that their holds slips show the first name they use, but it would be better to have both names printed.
3 votes -
Data Exchange > Send PRINT FILE using FTS - Include Login Column
I am often having to clean up/delete files that have been saved/"printed" via FTS File Exchange to Data Exchange (send print files out). I sort by date, clear old ones, but some I am hesitant, may still be needed. It would help immensely if the system identified the login associated with this printed file. Then I'd know who to ask/who owns this file (and who isn't deleting their old files). The login column is used elsewhere in the system (Create Lists, etc.), so would ensure consistency.
3 votes -
Additional macro modifiers in Sierra
Add additional macro modifiers in Sierra.
The 6.3 update removed the Control + F1 modifier macro. Can we consider adding more modifiers such as left/right control, left/right alt, and left/right shift keys?
Thank you!
3 votes -
Reinstate Manual Charge
We would like to be able to reinstate manual charges, whether they're for the collection agency fee, or something like a damaged container or replacement power cable. The reason why we cannot currently reinstate this particular charge type is not stated in documentation & while I may have known at one point, memory fades as we age. Being able to simply reinstate a manual charge would simplify & expedite workflows, whereas now, we have to make like Hall & Oates.
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 -
Schedule and automatically place contents of a system-generated review file into one or more designated list
Each week staff go into Create Lists and repopulate a designated review file with current data from a system-generated list. Two examples of system-generated lists include the OVERDUE ITEMS and PURCHASE ALERTS files. It would be great if our site could schedule Sierra to identify a specific list number and replenish or refresh the contents of it with most current system file's data. This would make the task fully automated. It's important to our system to be able to designate which list or review file number to use for each system-generated file job, however. We are a consortium and our…
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.
-
Add the ability to search for more fields for volumes in create lists other than just holds.
The only option in create lists for volumes is to find holds. It would be helpful to be able to search for volumes that 'match' or 'has' variable fields. Then we could search for volumes that say 2024, for example. It would also be helpful to have this in Global Update as well when toggling to variable fields.
2 votes
- Don't see your idea?