ILLiad Ideas
532 results found
-
Include ISIL as supported symbol type in Odyssey protocol. Odyssey currently supports the symbol types of OCLC, DOC (Docline), ISO and RAPID. At ReShare, we would love it if the schema were updated to include ISIL symbols so that we could transfer files for non-returnables. Please support ISIL (ISO15511:2009) as a library symbol taxonomy for Odyssey. (https://webstore.ansi.org/standards/iso/iso155112009)
3 votes -
renewal Add the ability to specify length of renewal to the groups management tab. Since we can set loan periods based upon group, renewal length should also be able to be specified for each group.
2 votes -
Limit Cloning in webpages by status We want to be able to make the action “Clone” ONLY allowed for Completed Requests. We want to remove it from Checked out Items, Outstanding Items, Cancelled Items, and Delivered PDFs.
8 votes -
Allow multiple addons to register for the same processing step (system event) Currently only one addon is able to register for a given processing step (i.e., system event: https://atlas-sys.atlassian.net/wiki/spaces/ILLiadAddons/pages/3149423/ILLiad+Addon+System+Events ), thus only one can be active at a time and still work successfully. It would be helpful if multiple addons could register in succession for a single system event. To give one example (but there would be many more cases with diverse addons), a library uses the ILLiad Alma NCIP addon when processing received & returned loans in Borrowing, and also wants to use the Flag Popper addon to flag certain requests for staff inspection at point of return (currently only one…
2 votes -
Celebration Addon or Feature Allow ILLiad staff users to set celebration triggers prompting ILLiad to display animated fireworks or other celebratory image. Set a default trigger of 1,000,000 transactions. Other ideas might be for when queues are cleared or other numbers of transaction totals in each module have been reached. This feature request is in celebration of Auburn University Libraries (AAA) reaching 1 MILLION transactions in ILLiad on 8/17/23.
11 votes -
Update Docline scripts to include fill in to Docline's Place Request by Journal UI Not all requests placed in Docline have a PMID. We must use the Place Request by Journal UI (ISSN, NLM, OCLC). This is different than the Manual function in ILLiad. ILLiad does not have a script to fill the citation information in to this request form thus we must type the citation, requestor, and TN number in to the form manually. Because not everything ordered in Docline has a PMID, this is an essential function needed to improve our workflows. A script is needed to facilitate this function.
12 votes -
Allow ILLIAD staff to customize name of column labels. Hi,
I'm having to do a lot of re-organization of my data after I've created a custom report from ILLIAD. I find myself renaming columns so I know what data I'm looking at. If there was a feature that allowed us to rename the columns in the backend, this would be great for resource sharing managers who have to report on this dataset!
6 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.
9 votes -
Make the client installer deployable It is recommended as standard practice for 2+ decades that users should not be admins on the workstations they use. Thus, they cannot install or update the ILLiad client themselves.
Throughout the IT industry, the way to install any software or updates is via centralized management (whether Windows or Mac workstations, or Chromebooks, tablets or phones) and automated deployments. This primarily occurs when a control server instructs workstations to install software using the workstation's own, built-in "SYSTEM" account which is a "super-admin".
The ILLiad client installer is the only software I've ever experienced (of many hundreds of applications) that fails…
5 votes -
Change SSN field to ID This field label has caused some concern/confusion in the past, and I doubt anyone still uses it to store SSNs. Currently we have to implement various customizations to hide the real column name wherever it appears in search grids.
11 votes -
ReShare Addon notify user when request is unfilled in ReShare Enhance the ReShare server addon to send a notification to the requesting user when a request is polled from ReShare (i.e. unfilled/end of rota). Notification should be customizable.
2 votes -
Fix Turnaround reports to include API-created Transactions Turnaround reports currently do not include any transactions created via the API. This is because the SQL queries that drive the Turnaround reports search the history table for specific status messages, and API-created transactions don't have those messages. Either the SQL queries need to be updated to include the API status messgae, or the API needs to use the same status message as the regular webpages in order for these transactions to appear in Turnaround reports. Right now, Turnaround reports for institutions that use the API to create transactions are totally inaccurate.
5 votes -
Send Notification dropdown should only display applicable emails based on ProcessType and RequestType Emails showing in the Send Notification dropdown are apparently populated when the TN is opened, and it shows ALL the EmailRouting table entries for that ProcessType (e.g. borrowing, doc del, lending) regardless of whether that particular email has a notification template for that RequestType (article or loan).
So what happens, is that there is a long list of emails in the dropdown, and if they choose an email template that doesn't apply to that TN's RequestType, then it throws an error, which isn't really graceful.
Ideally, the Send Notification dropdown would only show applicable emails that work for both that…
4 votes -
Fill in Lending DueDate field when TN is in other transactionstatus other than Awaiting Lending Request Processing If lending loan requests come in via Rapid and are routed to Awaiting Stacks Searching via a Routing Rule (because they already have the location and callnumber), the lending request never gets the DueDate assigned automatically because that only happens the first time a TN is opened from the Awaiting Lending Request Processing status. Could ILLiad somehow set that DueDate even though the Awaiting Lending Request Processing status is skipped?
5 votes -
Custom search to retrieve PDFs on the server that haven't been viewed A custom search will currently retrieve requests “Delivered to Web” that HAVE been viewed, but not those that have haven’t. Being able to quickly retrieve a list of those not viewed and highlighting those delivered more than 3 days earlier would facilitate sending a customized reminder notification while the PDFs would still be useful to patrons. The reminders could be sent once or twice per week.
Alternately, modifying the Electronic Delivery Reminder Server addon with an option to send the reminder x times per week (rather than each day after the first reminder is sent) could achieve the same results…
13 votes -
Lengthen conditional message The Lending Notes field in OCLC has a character limit of 500 characters, but ILLiad will only put through 255 characters. Would it be possible to increase this?
6 votes -
Automatic pickup reminders The current addon for this is too specific for one institution's processes. I'd like a simple pickup reminder to be able to be sent from ILLiad without an addon that sends the reminder at a specific number of days after the original notification (regardless of day of week, etc.) and only sends it once and/or on multiples like (value = 3, 3 days after original notification) or (value - 3,10, 3 and 10 days after original notification)
6 votes -
Additional request field auto-copying functionality (user-by-user basis) Currently, the CopyTitleToClipboard key in ILLiad Customization Manager allows for the auto-copying of the request title. However this setting is global for all users, and can only turned off or on by Process Type (Borrowing, Doc Del, Lending). It would be helpful to provide individual staff with the ability to override the auto-copy functionality, solely on their client, in order to either choose another field to auto-copy (e.g., Transaction Number), or alternately not to auto-copy any field when opening a request. The general setting (via the CopyTitleToClipboard key) would remain active for any staff members who did not "opt out"…
2 votes -
Viewing "Return To" Address in "Check in from Lending Library" when Receiving When Receiving borrowed items in the "Check in from Lending Library" tab, we should be able to view the constant data "Return To" address so we know which address to select when receiving. We have to click on an address in the list, and then view the constant data in the request in a box on the right hand side. I wish we could have that constant data box to view right on that first Check In page so it is easier to select the correct address to return the item to.
6 votes -
Make Illiad fields searchable regardless of including accent marks/special characters Allow the ability to do searches in ILLiad & pull up the correct results regardless of whether that field has a special characters or accent marks, etc. For instance, doing a patron last name search for Peña, should pull up with Pena or Peña (currently it has to be an exact match). Same thing with titles & authors, if the title has accent marks or special characters, we cannot pull up the request without also including the special characters/accent marks.
6 votes
- Don't see your idea?