ILLiad Ideas
536 results found
-
Do not move MailToAddress transactions to Awaiting Customer Contact when patron is blocked or item is Library Use Only At present, if a patron is set to HoldForPickup, checked in Loan requests go to In Transit to Pickup Location and can be moved to Awaiting Customer Contact manually or via routing rule while if a patron is set to MailToAddress checked in Loan requests go directly to Awaiting Customer Contact.
This is fine for the majority of materials, but not ideal for items that are restricted to In Library Use Only (which we will not mail to patrons regardless of their preference) or for items for Blocked patrons (who need to return materials before we'll send items again).
We've…
1 vote -
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 -
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 -
Develop pathway for ILLiad stub accounts to complete registration when RemoteAuth (particularly EZproxy) is in use. Desired behavior: Patrons authenticated via RemoteAuth (EZproxy) who begin but do not complete registration can subsequently return to registration with their data populated from the latest info in the UserValidation table.
We use RemoteAuth for patrons to authenticate via EZproxy, and change implemented in order to preserve user PINs during the ILLiad 9.0 upgrade. We also do a daily upload to the UserValidation table that includes just those patrons who are eligible for ILL service. This table populates the NewAuthRegistration form so they can successfully submit registration and access ILLiad.
When users authenticate via RemoteAuth before they have been added…
1 vote -
strip extra characters out of PMID field when receiving from Pubmed via OpenURL The OpenURL generated by Pubmed has the PMID field sent as:
&rft_id=info%3Apmid%2F26824237
which puts extra info in front of the PMID value. This means staff have to touch each request and clean it up before searching it. It would be great if the OpenURLMapping table could have an option to strip characters from a value or some other means to clean up that field when it carries over.14 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 -
Web Interface for the Staff Manager and Customization Manager A web interface that combines the features of the Customization Manager and Staff Manager in one place.
0 votes -
More ItemInfo and UserInfo fields Consider increasing the number of ItemInfo and UserInfo fields to more than 5 each. We have already used up all of the ItemInfo fields and have had to re-purpose existing fields to collect the additional information we need in our borrowing requests.
60 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 -
Printing a individual invoice I would like the ability to print an invoice right away for the libraries that email their request and ask that we attach an invoice to the request. Most of the time these are specialty or international libraries that rarely or don't use OCLC or Docline. This would also be good for individual users ( former Lomsone Doc Users) who are not part of our university or our medical association.
13 votes -
Check OCLC Status before sending Overdues-do not send for "Returned" OCLC status items Remove step of manually checking for OCLC "Returned" status before generating overdues. it would be helpful if the automatic process included checking the OCLC status before sending it off and not sending for items in Returned status.
5 votes -
ability to update OCLC request to complete Attempting to Check In from Lending Library will cause a Connection Manager error if an item is returned to the lender but the borrowing library has not performed the OCLC Received or Returned update.While the Connection Manager error can be cleared, the system flag will remain unless the borrowing library updates the request.
It would be helpful to have a way to override these flags, particularly if the item is considerably overdue.
8 votes -
Bulk Renew in Borrowing With libraries closed indefinitley all over the world, we have to push due dates out, possibly multiple times. This is easy enough to do in an ILS, but ILLiad does not allow me, as the Borrowing Coordinator, to push out a renewal request for one new due date for all items currently due before that date. That would save me hours, possibly days of work!
18 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 -
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 -
Allow the CreationDate field to be added to loan and article pull slip templates It isn't currently possible to add the CreationDate field to the loan and article pull slip templates because that field is not included in the xlsx datasource columns. Can this be fixed? Having the CreationDate field on pullslips would make it easier to know which printed requests are close to expiring and need immediate attention.
19 votes -
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 -
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 -
Database Manager - Extend the transaction purge options The transaction purge tab in Database Manager only has transaction date as a criteria. The Patrons tab allows for a very fine grain approach for deciding which users to purge. It would be nice to have a similar or expanded group of options for transaction purging.
For example, it would be nice to be able to delete test users that have test transactions, which we cannot currently do effectively now.
6 votes -
Import complete information (esp. Publisher) from OCLC into ILLiad when sending request Currently ILLiad imports the title field from sent OCLC requests. It would be great if it imported more info such as the journal publisher. We are constantly asked for details of how many Publisher X or Publisher Y journal articles were requested through borrowing. We can't provide the info because the patron doesn't supply it and ILLiad doesn't import it (and manually doing it for our volume of requests is too time consuming).
6 votes
- Don't see your idea?