ILLiad Ideas
502 results found
-
4 votes
-
Allow Address number field change
When a new lender address is created, an address number is automatically assigned and that number cannot be changed. Please allow that field to be edited in case we want to re-arrange the order of our addresses. Some addresses are used a lot more often and we want that to be 1 or 2 but cannot right now. Thank you.
11 votes -
Permissions for Electronic Delivery Utility
University of Pittsburgh would like more control over access to the Electronic Delivery Utility, particularly in reference to billing features. Please consider tiered permissions that limit individual staff use and limit the ability to skip or adjust automatic billing totals.
2 votes -
Allow staff to customize which transaction statuses are displayed under each heading in the patron interface
I would like more customizable display options for transaction statuses in the patron interface. For example, once a patron clicks the "Renew" button, the request disappears from their checked out items list until the renewal is processed and routed back to checked out to customer. I would like items in the Renewed by patron status to also appear under the checked out heading.
We use a lot of custom queues and would like to be able to manage where requests display in the patron interface.
2 votes -
Import ILL into Alma without Checking In
Sometimes when I check in an item from a lending library, I receive an NCIP error that causes a loan to not be automatically imported into Alma. After I fix whatever caused the error, I currently have to check the item in again. This messes up the tracking and can cause an OCLC error. It would be nice if there was an option to only import the request without updating the status in ILLiad and OCLC.
2 votes -
Change to the redirect of a user when they Register in the pages of another nvtgc
If a user registers to ILLiad (specifically via the NewAuthRegistration.html) in the wrong nvtgc site's pages, during the dll redirect to the right nvtgc pages the UserNotifications entries are not added for the user. The dll log does show that entries are being added but it appears this is written to the log even when the entries have been skipped over.
2 votes -
Update the Primo New UI addon
The Primo New UI addon can cause the ILLiad client to crash. The addon appears to be running endless in the background, building up processes that eventually cause a memory error forcing the ILLiad client to crash.
One way to cut down on these crashes is to turn the auto-search function off for the addon, and to reboot the client once or twice a day.
Note: because this is a custom addon not developed by Atlas Systems, we don't officially support it. We are looking into ways for making this more clear in the documentation, but if there is enough…
1 vote -
Add Note While Returning Books
When I check items in to return them to their owning institutions, I often need to make a note in the request. Currently I can only do that by opening the request first. It would be nice if I could double-click in the notes field and add the note from the "Borrowing Check Item In" screen.
7 votes -
Option for selecting queues from a drop-down when creating routing rules
To piggyback off of the case-insensitivity with queue names ideas: https://uservoice.atlas-sys.com/forums/581665-illiad-ideas/suggestions/42375580-case-insensitivity-for-queue-name-and-custom-field. Another option to avoid having errors if a queue name is typed in a routing rule without proper case sensitivity would be to have a way to select queues such as a drop-down menu when creating custom routing rules.
4 votes -
Case-insensitivity for queue name and custom field names
When creating routing rules or addons that route to queues, allow for case-insensitivity. For example, normal behavior would prevent the renewal button from showing in the default 9.1 web pages if a routing rule includes "Checked Out To Customer" instead of "Checked Out to Customer" since this isn't the correct name case sensitivity in ILLiad. Allowing for case insensitivity could open the door to allowing for custom field names.
3 votes -
Ability to print selected pull slips
Would love to print from different physical locations but need to be able to select which pull slips (or receives, or whatever!) should be pulled for printing, so that you do not disrupt work at another location.
9 votes -
satisfaction survey per transaction
We would like the patron to be able to answer a satisfaction survey when they receive their document or response. it would be valuable to identify transactions that were challenging (from the patron's perspective) and have front-line staff followup with them. a 1-5 star rating would be sufficient along with a comment box.
3 votes -
Make barcodes more usable/searchable in the ILLiad client
Expand the ItemNumber field in ILLiad to accommodate multiple barcodes for multi-volume sets. Add ItemNumber to the default Number search in the ILLiad ribbon for easy access. Add ItemNumber to fields searched by TN/ILL # search on Check Item In interface.
All of the above would allow more efficient handling of borrowing returns when paperwork with Transaction is missing.
16 votes -
End of the line Deflection
When a library uses the following deflection:
Requests: Loan
Deflection Type: Enable Real Time Deflection - except when I am last in the lender stringOCLC should bump past them in the string, but AUTOMATICALLY add them back to the end of the string of potential lenders.
2 votes -
Tag other ILLiad users in a staff note
We can use flags and notes to ask other ILLiad staff users questions about a request, but it would be even simpler if we could include @PersonName in a staff note and notify them that they'd been tagged for review/response.
6 votes -
Add the ability to customize elements on the Detail Page based on request status
We would like the ability to customize what elements/fields display to the user on the Request Detail page. We use custom queues for certain requests and do not want the Due Date to display in the detail view for requests in those queues.
1 vote -
PMID Addon
It would be great to have an Addon similar to the existing DOI Addon. If a user on the webform enters a PMID, ILLiad searches and fills in/adjust the rest of the request data.
10 votes -
Allow tracking of multiple renewals for one request through ILLiad
Currently ILLiad will only track the first renewal for a request. However, many lending libraries allow for multiple renewals, and with current closures this is happening more frequently. It would be helpful to have ILLiad route and track renewals for requests beyond the first one so that the due date in borrowing requests match what the lender has determined.
38 votes -
PLEASE change Docline Lua scripts to stop on the Docline screen that show the request is a duplicate.
Change (or change back) ILLiad Lua scripts to automatically stop on the screen that has the duplicate request alert. It flashes past so quickly now, it's easy to miss and then we have to pay for article twice. The way the scripts run now, you've lost us a great Docline feature.
2 votes -
Add hidden fields to request forms for more flexibility
Currently the Status field is the only option for creating unique request forms. It would be nice to be able to have more information to customize request forms. Some of the user information, such as Status or User Info # would be valuable to work with on request forms. If could be queried to hide/add fields based on unique statuses. The data could be in a query parameter or hidden input field on the page.
4 votes
- Don't see your idea?