ILLiad Ideas
517 results found
-
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.
7 votes -
Improve Error handling in Electronic Delivery Utility (EDU) to keep cascading errors from occurring.
When the EDU loses connection to a network location where files are stored due to a timeout or issue, the EDU continues to try and process causing a loop of error messages that cause the EDU to crash. See ticket# 38285 on 3/14 screenshots for error. Please enhance to report the loss of the connection and stop the EDU from continuing. Matt did not think we could re-establish the connection so I don't know if restarting the EDU is an option but Matt added
"we could maybe better handle the errors when it can't make open files and stop trying…
3 votes -
Clear OCLC search filters when a request is closed
When searching for harder to find items in OCLC through ILLiad, we often use the custom search or set filters in the Limits box. The search terms and filters stick from request to request. The worst problem is that if I filter by year, this doesn't appear obviously in the limits, but when I search the next request by ISSN/ISBN nothing comes up. I have to remember to open Limits and clear the year from the filter.
It would be so helpful if these fields would just reset with every request. There isn't any case where I want the same…
2 votes -
Add User Expiration Date as an option for Customized Layout in 1-borrowing form, and 2-Check In From Lending Library batch screen.
We'd like to be able to see the User Expiration Date in the client on the borrowing request form and the borrowing batch process "Check In From Lending Library." This would help us when assigning due dates and renewals (in case we need to truncate what the lending library offered), and may also determine where we send initial requests as well. At the moment, User Expiration Date is not in the list of fields to choose from when customizing layouts.
1 vote -
Integrate API keys for Docline
NLM rate limits Docline searches to 3 per second without an API key. It is rare, but under the right circumstances, the client can exceed this, in which case using the API would be beneficial.
1 vote -
Ability to add tags to Default Notes field of Cancellation Reasons.
Cancellation Reasons have associated Default Notes fields. It would be great if tags could be inserted into the Notes fields to auto-fill information.
Example:
Cancellation Reason: We could not fill your request by your deadline.
Default Note:
You indicated you did not need this item after <#Transaction.NotWantedAfter>. If you would still like to received this item, please ....8 votes -
Hide due dates on shipped Borrowing loans on Web
9.1 web pages, patrons can see due dates for requested/shipped items before they’ve arrived. This has confused patrons and does not always reflect the due date that will actually be assigned to the material.
6 votes -
Replace Lending Web Shipped Items Due Date field in new pages
The Lending Web pages don't contain due date information in the tables, despite the documentation saying it should be a default table field and it historically being displayed in the pages.
1 vote -
Make label position selectable for print processes
We would like label templates to not generate placeholder text when there is no data and we would like to indicate on which label printing should begin.
1 vote -
Allow users to specify pickup locations on a per-request basis
ILLiad should support the selection of a pickup location on a per-request basis.
2 votes -
Have Lender Select box consider Odyssey and email addresses too
Atlas support said recently that only the shipping and billing address fields are checked for incoming ILL requests. Libraries often change their contact info. and it would be best if the system is checking for that too in order to avoid outdated Lender records in the Client and misdeliveries
13 votes -
SAML multiple attributes (allow for multiple and to list those which are allowed)
We have come to understand that ILLiad's SAML module does not support SAML2 attributes sent by the Identity Provider with multiple values. These would take the basic form in the SAML assertion XML like:
<saml:Attribute Name="multiAttributeName">
<saml:AttributeValue>Value 1/saml:AttributeValue
<saml:AttributeValue>Value 2/saml:AttributeValue
<saml:AttributeValue>Value 3/saml:AttributeValue
/saml:AttributeIt is described on pg 31 of the spec https://www.oasis-open.org/committees/download.php/56776/sstc-saml-core-errata-2.0-wd-07.pdf#page=31
As this is a common method of delivering data structures inside of SAML attributes especially when specifying items like user affiliations or group memberships, we request that support be added in the future to read and operate on multi-value/list attributes within the RemoteAuthValidation table.
2 votes -
ReShare Addon create a more robust breadcrumb trail
When the ILLiad ReShare addon creates a request in ReShare, there isn't much in the way of tracking after the request is submitted. We suggest adding notes to the ILLiad TN anytime the addon takes action on the request so there is a static history of what actions the addon has taken. That way if the request enters a different fulfillment method, such as OCLC, then there is preservation of the past ReShare request number and any other actions that the addon has taken. Otherwise, this information is lost (the ReShare Request ID is overwritten in the ILL number field).
3 votes -
Fulfillment Data should be included in Custom Search results
Custom searching for transactions doesn't return information from the FulfillmentData table. We need to be able to calculate money spent through DSP addons like Reprints and Get It Now and there isn't any other way to gather that information out of ILLiad, other than using an ODBC link and an external program.
2 votes -
1 vote
-
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.
9 votes -
Prevent borrowing renewal requests when the lending library will not accept them
As a lender, FSU does not accept renewals and this is indicated in our notes, in the Client when we mark a request as Shipped and in the Policies Directory. In WSILL, the Renew option disappears when a borrower has exhausted renewal requests. There is no equivalent in ILLiad and borrowers can continue to send renewal requests regardless of settings and indicated preferences. Borrowers should not be able to request renewals when lenders have indicated they will not be accepted. (via KAK)
6 votes -
Additional section of the homepage for storing filled article requests
We have received a request from one of our most active researchers to add an additional section to the ILLiad homepage that users could route article requests to, rather than all filled requests being under Electronic Documents. This would help our users manage higher volumes of requests.
7 votes -
Google Scholar chromium version no longer authenticates using EZ Proxy URL
Former Scholar addon had a field where I put our custom Google Scholar URL that authenticates with EZ Proxy and shows which articles we have licensed access to. New version only searches "generic" Scholar which does not link to what we have access to (just paywalled stuff). When can you bring back this functionality? It's the only reason I used the addon.
1 vote -
Add semicolon as option for separating multiple email addresses
When sending emails to multiple recipients, ILLiad functionality should be expanded to allow both commas and semicolons, as semicolons are the known character for the function with other email programs/ API.
11 votes
- Don't see your idea?