Skip to main content

 

OCLC Support

Tipasa release notes, July 2017

Release Date: July 23, 2017

Browser support

This release was tested with the following browsers:

  • Chrome (latest version)
  • Firefox (latest version)
  • Internet Explorer 11

Adobe Reader and JavaScript need to be enabled.

Browser compatibility chart

 

Recommended actions

For this release, we recommend that you review the following checklists and complete the relevant tasks so that you can adjust your policies and workflows and train your staff. These checklists identify updates that we have determined as significant for most institutions. We encourage you to review all of the items in the release notes to determine whether there are other items that might require additional action or follow up by your institution.

Action

Following the release, we recommend that you clear your browser’s cache before starting to work with Tipasa.

Have you updated addresses in all your borrower and lender Constant Data? If not, please do so on behalf of all your borrowing and lending partners. Address labels do not print properly unless the addresses are formatted correctly.

Share release notes with your colleagues.

https://oclc-prod.mindtouch.us/Tipas...d_known_issues

Workflow improvements

Manually route existing requests through Direct Request

Direct Request automates processing of borrowing requests. As of the May 2017 release, you can now manually route newly created requests through Direct Request. With this release, you can also manually route existing requests though Direct Request. This lets you to submit a borrowing request without selecting lenders or applying constant data, provided your Direct Request profile is set to produce the request. Patron data is required for the request to be processed with Direct Request.

For example, if a borrowing request could not initially be produced by Direct Request, the Request History may include entries similar to the ones below.

tipasa-rn-july2017

You may wish to enhance the citation information and route the request through Direct Request again. To do that, you can use the Send to Direct Request button, which is now available for any borrowing request that has not yet been submitted to lenders.

tipasa-rn-july2017-2

If the request is produced with Direct Request, it will appear in the Direct Produced queue. If it is not produced, it will remain in the list for staff review. You can check the Request History to see why it could not be produced, make further changes, and send to Direct Request again if appropriate.

Additional details are available in the Tipasa documentation:

https://oclc-prod.mindtouch.us/Tipasa

Apply Constant Data and send requests to Print Queue when batch processing requests for Considering and Advanced Lending

With the May 2017 release, you became able to update lending requests individually prior to responding “Yes”. This allowed you, for example, to add a due date and return address before printing the pull slip. With this release, you can now make batch updates to requests prior to responding “Yes”.

You are now able to:

  • Apply Constant Data to batches of lending requests for Considering and Advanced Lending queues (Verifying, Retrieving, Scanning, and Packaging).
  • Send batches of requests to print queues for Shipping Labels and Book Straps/Stickers for Considering and Advanced Lending queues.
  • Respond “Yes” to batches of lending requests without applying Constant Data or overriding previously saved values.

For example, this screen shows the new batch options for Verifying. Notice the new checkboxes for the print queues as well as the drop-down menu for Constant Data, which includes a blank option for retaining previously saved values.

tipasa-rn-july2017-3

Note that checks for required fields, valid due date, and lender cost not exceeding borrower max cost are only done when you respond “Yes”. These validations are not done when updates are made to Considering or Advanced Lending queues.

Note also that if a request ages out before you respond “Yes”, and the moves to another potential lender, the Constant Data that you entered is removed from the request.

Additional details are available in the Tipasa documentation:

https://oclc-prod.mindtouch.us/Tipasa

Bug fixes

Errors listed in Notification Log when text notifications turned off

Previously, the Notification Log included failed attempts to send text (SMS) notifications even if you have disabled text notifications in Service Configuration for your library. After this release, these errors will no longer display in the Notification Log.

tipasa-rn-july2017-4

Overdue notification sent to patron after loan is renewed

Previously, automated overdue notifications were sent to the patron even if a request had been renewed by the lender. After this release, the system will check the patron due date before sending any automatic overdue notifications.

Known issues

The following known issues have been corrected in this release:

  • Recently closed requests are temporarily not searchable as either an ‘active request’ or ‘closed request’ from the Tipasa home page.
  • Status/cancel button display issues in the user portal
  • Print export fields not printing correctly: Supplier Name.

Lists of current known issues and recently fixed issues can be found at:

https://help.oclc.org/.../Tipasa/Release_notes_and_known_issues/Known_issues

Future releases

Roadmap information is available at:

OCLC Tipasa Community

Important links

Product website

More product information can be found at:

http://www.oclc.org/en/tipasa.html

Support website(s)

Support information for this product and related products can be found at:

OCLC Community Center 

At the OCLC Community Center, you can:

  • Connect with community peers
  • Collaborate, ask questions and gain insights
  • Contribute and share ideas to improve products
  • Stay on top of and discuss OCLC announcements

http://www.oclc.org/community/home.en.html

 

  • Was this article helpful?