ILLiad Ideas
149 results found
-
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 -
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 -
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.
10 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.
17 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 -
Copy Layout & Grid Settings - Separate Borrowing, Doc Del, and Lending In the Staff Manager, please adjust the granularity of the Copy Layout & Grid Settings by Borrowing, Doc Del, and Lending. If I make major changes to the Borrowing layout, I'd like to be able to copy those changes to the relevant student employees & staff, but not overwrite their layouts in DocDel and Lending. It would be very helpful if we could indicate which layouts to change and which to retain in these different areas of ILLiad.
1 vote -
Book Chapters - Should use Article holdings path instead of Loan holdings path Book chapter requests use the incorrect custom holdings path; they pull from OCLCILLLoanHoldingsPath instead of OCLCILLArticleHoldingsPath, but the latter is the correct path.
4 votes -
iOS app for ILLiad on iPad Please develop an ILLiad app for iOS on iPad. It would greatly ease some of the difficulties our workers have doing their job remotely.
2 votes -
Add price to Symbol/days to lend grid instead of hovering for that information. Having to hover over a symbol to see the cost while in borrowing trying to build a custom string takes extra time. It would be great if the cost could be displayed right next to the days to fill.
11 votes -
12 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 -
Add export of User list from the Staff Manager Add the ability to export of list of staff user from the staff manager similar to functionality available in Ares
3 votes -
Hard to tell when Editing vs Copying a row in Customization Manager tables When working in the OpenURLMapping table, we noticed it really is impossible to tell if you're in the "Copy" or "Edit" mode because the ID value doesn't show up in either of them. We'd expect it to show while in Edit mode, but be blank in Copy mode.
In general, when working with a table in the customization manager, it gets very confusing when you think you hit Copy but then worry you may have hit Edit instead since the opened row says "Edit Row" either way. If there was some way to indicate better whether you were in Copy…
4 votes -
Bulk data updates I'd like to see an addition to the database manager where we can run a search against the transactions, users or lending library tables and from those results, batch update fields in that table for those results. An example would be if we have a campus that changes names (which we've had a couple times) We could run a query on all users with that pickup site and batch update them to the new name. I see this as an addition to the database manager since that is able to be restricted to a VERY limited number of staff.
3 votes -
ILLiad Lending scanning display email of borrower In the lending scanning window, display the email address of the borrower. When sending via Article Exchange it isn't always known if the email address is filled out in the address book. If the email address is not in the address book, the article does not get delivered.
5 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 -
Searching from the Check In From Lending Library Screen If you accidentally click Search without any information in the search fields, a long list of requests come up and the first one in the list automatically displays. This has caused trouble with new employees who have not noticed and mistakenly checked in items that we have not received. Please change this so that no results appear if you do not enter search information or at least a window opens asking if you want to proceed.
2 votes -
Expand fields searched in citation information on both the home and the lending update stacks search screen The citation information search in the client should be expanded to include things like Item Number and ISBN.
3 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
- Don't see your idea?