ILLiad Ideas
502 results found
-
7 votes
-
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 -
staff password complexity description
Add a field to the StaffPasswordComplexity field to allow a plain text description of the regular expression. A user should able to view what the password requirements for staff passwords are without having knowledge of regular expressions.
7 votes -
ILLiad Aeon integration: send scan files back to ILLiad for request fulfillment
We use ILLiad to Aeon integration to facilitate Special Collections scanning for ILL lending. When we send a scan request via ILLiad to Aeon, we would like the ability for Aeon to pass the .pdf back to ILLiad for request fulfillment. Currently, Aeon staff have to email the .pdf to ILL staff in order for the file to get uploaded to ILLiad for ILL delivery. This would be similar to the Ares/ILLiad integration: we pass scans to ILLiad from Ares for scanning fulfillment through OpenURL.
7 votes -
Add Expired User Indication on User Record
When using User Expiration in 9.1, the only indication of a user's expired status on the User Record is the Expiration Date. All other indicators are the same as a New User :
User Record= no status button active
https://www.screencast.com/t/1xqQr0NbaIZTransaction Record=flag by username and "user not cleared" status warning
https://www.screencast.com/t/0DttY3BXKQkPI would be helpful to be able to readily distinguish between users that are expired vs. users that are new.
7 votes -
Include ability to batch update records
I realize that this could be very dangerous and should be locked down behind something like the database manager, but having the ability to batch update records (transaction, user, lender, etc) in ILLiad would be a huge time saver. There are times when local data or workflows change, and the ability to change more than one record at once would open up a lot of possibilities.
7 votes -
A key to determine if request auto opens (or doesn't) when it's the only item in a queue.
I would like to be able to control if a request will automatically open when searched or when a queue of one is displayed.
Primarily, I want to be able to STOP the request from opening automatically. Many times we search for an item to see info, or route to an active status, and auto opening just slows down our ability to do this as we wait for the request to render.
7 votes -
Overdue Workflow Enhancement
Add option set a time to auto-route extremely Overdue requests (e.g. those which have received notice 3 + 30 days) into a custom queue indicate that the item is lost and an invoice needs to be created.
7 votes -
Limit Number of Library Symbols added to the Lending String with Custom Holdings
Add ability to customize the number of libraries that are added when using Custom Holding to create the Lending String.
Many libraries want to create shorter lending strings (less than fifteen) so that requests are not out for potentially weeks before being filled. Currently, in order to create shorter lending strings you have to manually add library symbols or remove library symbols after using custom holdings to auto-generate a string.
7 votes -
automated email confirming return via Web Circ
When loan is checked in via Web Circ (and status changes from Checked Out to Customer to In Transit From Customer), ILLiad automatically sends email to patron confirming return. Patron receives confirmation of returned ILL + helps ILL staff reduce claims returned situations. Email would simply acknowledge return, including the TN, title, author, etc.
7 votes -
Add RequestType to default IFM ILLiad reports
Purdue University needs to break down IFM charges by RequesType for internal reporting. Having this in the default reports would be very helpful. We'd like to see it for both Lending and Borrowing.
7 votes -
Make a library's loan period visible on the borrowing holdings screen
When creating a holdings list, currently borrowers can see the institution name, days to respond, and fees for lending institutions. It would be nice to see the library's loan period for items in this area.
7 votes -
Ability to upload request from Reference Citation service
Our researchers often use Reference Citation services such as RefWorks, EndNote or Zotero to create bibliographies. We would like for them to have the ability to upload a batch/list of items from a service like this or from an excel spreadsheet.
7 votes -
When non-OCLC library creates an LWeb account, have a registration workflow built in to check legitimacy before they can submit requests
We want non-OCLC libraries to be able to create their own accounts, and to be able to make that process more transparent. However, right now, anyone can create an account and immediately place requests.
After catching some illegitimate requests entered in this way we made a routing rule to review LWeb requests, but it would be better to have the workflow built into the system, so we can better manage approving, expiring, blocking, and communicating with non-OCLC libraries.
7 votes -
Alert when an installed add-on is updated
If an installed add-on has a new version, be alerted (via either a popup in the client or even via subscription through email).
7 votes -
Have OCLC search default to serials *and* internet resources by default for journals
Many electronic journals are classified as internet resources versus a serial, so both need to be selected in a search
7 votes -
Addon update notification
Surface an alert in the ILLiad System Dashboard notifying users that an ILLiad addon in use on the local ILLiad system has been updated in the directory. It can be hard to find out if addon updates are available and it can be tricky to troubleshoot or support if different versions of the addon are installed. Having a notification of an available addon update - that an ILLiad system is using an outdated version of an addon - would save time and troubleshooting as well as help users to benefit sooner from bug/security fixes.
6 votes -
Improve Z39.50 and FOLIO connection
There's already a call out to FOLIO to improve how multi-volume holdings appear in XML to make them visible via Z39.50, but it would probably help matters if Atlas Systems and FOLIO worked together to make this improvement for all libraries migrating to FOLIO. https://issues.folio.org/browse/ZF-84
Basically, if there are multiple volumes of a title, only summary holdings and inaccurate availability status are visible through Z39.50. Some libraries have implemented custom addons to get around this, but this is really a workaround to what should be a standard function.
6 votes -
Only display "Reason for Cancellation" in Request Details on the web if the item is currently in a cancelled status.
We regularly cancel items that get revived later once the patron has made a decision or change of some sort. When those items are revived, "Reason for Cancellation" continues to show in the Request Details on the web. It would be helpful if this field only displayed if the item was in the status of "Cancelled by ILL Staff" or "Cancelled by Customer", and otherwise was hidden.
6 votes -
Billing for lost items
Ability to create an individual invoice for lost items and have the Billing Manager handle billing for one-off invoices.
6 votes
- Don't see your idea?