ILLiad Ideas
515 results found
-
Lender Addresses with Invoices that are Active
Lender Addresses linked to Invoices that are Active (even those marked Paid) cannot merge with another address. The only option currently is to manually change or delete invoices first. Please consider allowing Paid invoices to not be considered "Active
1 vote -
Support for New Docline "NLM Unique ID" Requests
Since New Docline's initial release, NLM has continued to add and refine features. One feature that has changed recently is an improved ability to handle requests based on NLM Unique ID. This is in addition to requests for articles with a PMID and "manual" requests.
Request by NLM Unique ID is great for requesting print books that NLM owns (since they are such a reliable lender) as well as for all journal articles that are not indexed in PubMed, but for which a journal-level bib record exists in NLM's LocatorPlus catalog.
In fact, New Docline's "Borrow - Unique Journal ID"…
14 votes -
Allow ILLiad to pull in Language code or other info from OCLC records
If ILLiad could include the language code from a record (when available), it would help us know who to refer to when we needed assistance and to get better statistics on what languages we are supporting.
Similarly, pulling in subject headings would be really useful for referring to our liaison librarians and for consideration with acquisitions funds; right now we have to base these off of the department of the requester, but we're missing cross-departmental opportunities this way.
2 votes -
Allow FORMSTATE tag to persist through webpage workarounds.
When a workaround is used on the webpages to display something outside of the usual ILLiad workflow, it breaks the tag and doesn't allow OpenURL to route the user back to their request. Ideally, the formstate would persist through the workaround, and the user would be routed back to their request instead of dropped onto the main menu.
2 votes -
Connection Manager
Make sure the Connection Manager does a full check of the Pending status during each cycle run and not just after midnight or after a service restart. This is from ticket 10049.
4 votes -
Bring Back UNDO Shipped for all requests
Is it possible to have the ability to UNDO Shipped brought back, or have another way to undo a request?
13 votes -
Send Renewals Requests Automatically without Assigning New Due Date
Enable the Send All Renewal option when AutomaticRenewals key is set to No.
4 votes -
See last opened request
Could there be a way to see a list of the last 5 or so requests that a staff person opened? We sometimes forget to place notes or verify a piece of information before it gets routed to the next step. Titles or usernames are not always remembered correctly to find the request again. Even just the last request opened would be helpful.
9 votes -
Cover sheet for Lending Requests
Add the ability to apply a coversheet on the lending side which would allow lenders to include copyright information as required by the CONTU guidelines.
8 votes -
Allow us to adjust the number of times a journal is requested before it appears on our copyright list.
If CONTU is not law, and our institution decides that 10 requests is the definition of replacing a subscription, we should be able to change a setting in ILLiad so that we can easily follow our own guideline, rather than ignoring the list and reconciling all titles at the end of the year.
4 votes -
Add Captcha challenge to login and password reset pages
Captcha might prevent the recent scripted logins which are resulting in fraudulent lending requests.
1 vote -
Enhance the MARC record display in WorldCat searching
It would be great to add features from OCLC Connexion's MARC display to the display of MARC records in ILLiad. We'd like to see the value in 040 subfield b (language of cataloging) displayed in a column in search results to quickly narrow down the potential correct record for an item. It would also be really helpful to right-click on a MARC tag to go to the OCLC site for a definition of that field. Modeling the MARC display after the great features in Connexion would really help with efficient searching.
4 votes -
2 votes
-
Enable automatic Odyssey coversheets for borrowing
There is currently a function that allows a custom coversheet to be inserted automatically before Odyssey sending for Borrowing & Document Delivery, but not for Lending. It would be great from the lending library’s standpoint since we’d be more compliant in terms of copyright & licenses if we could include the Title 17 notice there, and any usage restrictions. It would also be great for the borrowing library’s standpoint since Odyssey is a more direct delivery method than Article Exchange
13 votes -
Flag or add a notification of some sort sort to identify stale requests.
It would be nice to be able to see requests that are sitting around in queues when they should have moved on or some action might need to be taken by staff. An example would be items that have been sitting in Request Sent for too long with patrons not getting their materials in a timely fashion.
16 votes -
3 votes
-
ILLiad Event Hook for Borrowing Item Shipped
Would it be possible to create an event hook that would trigger when ILLiad detects that an item has been updated to Shipped in OCLC? Currently, my code is regularly checking the Request Sent status for a new value in the DueDate field, but it would be preferable to have it triggered by a system event.
16 votes -
Docline/ILLiad
It would be so nice if ILLiad/Docline would integrate better. Processing Docline requests in ILLiad is too much back and forth. it would nice to see a pop-up notification when requests are unfilled in Docline or if it worked like special messages in OCLC.
3 votes -
Allow API to Add, Remove, and Update records in the UserValidation table
Stanford U is locally hosted and has a custom job that imports users directly into the Users table. This job will update users based on any change event triggered in the Registrar's database. It creates many users that never end up using ILLiad. We would like a standard method of creating a process that pushes users into the UserValidation table and can update users, regardless of their being in the Validation table or in the Users table.
8 votes -
Allow API to update existing users
This is similar to the request to "update user account by pulling user data from org directories via Single Sign on"
9 votesCorrection: The API supports creating users but not updating existing users. We are reviewing this request.
- Don't see your idea?