Tipasa Release Notes, June 2022

Administrative actions

These items require immediate action or decisions.

Follow-up actions

In an effort to keep your staff informed of new features and changes, you may also want to consider these items.

Quickly email Article Exchange links for off-system copy requests to library users

When an off-system borrowing request is filled and the document is added to the request via Article Exchange, the full request details email will autopopulate the Article Exchange URL and password. 

For more information, see Off-System Requesting.

Provide library users with Article Exchange links for off-system requests in My Account

For off-system requests, your library users will now see the appropriate Article Exchange links in My Account. Links will display once the file has been dropped in the Tipasa request and the status has updated to Received. These requests will appear just like requests supplied by OCLC network suppliers.  

For more information, see Off-System Requesting.

Utilize new data inserts to autopopulate request data in notifications

You can now save time and provide important request information by utilizing the new notification inserts listed below. To add these data inserts to your notifications, go to the Notifications section of OCLC Service Configuration.

Note: These inserts will be available beginning June 13th, 2022

Patron address inserts

${PatronAddresse1!}
${PatronAddressline2!}
${PatronAddressLocality!}
${PatronAddressPostalCode!}
${PatronAddressRegion!}
${PatronAddressCountry!}

Delivery address inserts

${DeliveryAddressShipTo!}
${DeliveryAddressLine1!}
${DeliveryAddressLine2!}
${DeliveryAddressLocality!}
${DeliveryAddressPostalCode!}
${DeliveryAddressRegion!}
${DeliveryAddressCountry!}
${DeliveryAddressEmail!}

Billing address inserts

${BillingAddressShipTo!}
${BillingAddressLine1!}
${BillingAddressLine2!}
${BillingAddressLocality!}
${B¡llingAddressPostalCode!}
${B¡llingAddressRegion!}
${BillingAddressCountry!}

Return address inserts

${ReturnAddressReturnTo!}
${ReturnAddressLine1!}
${ReturnAddressLine2!}
${ReturnAddressLocality!}
${ReturnAddressPostalCode!}
${ReturnAddressRegion!}
${ReturnAddressCountry!}

Renewal information data inserts

${RequestedDueDate!} 
${Renewed!}

Supplier information data inserts

${SupplierltemBarcode!}
${SupplierCharge!}
${SupplierNote!}

Off-System request data inserts 

${RequesterOffSystemReferenceld!}
${SupplierOffSystemReferenceld!}
${OffSystemRequesterName!}
${OffSystemSupplierName!}

Date data inserts

${ReturnedDate!}

For more information, see Notification data inserts. 
 

Aging period for requests in problem statuses is now 180 days

With this release, the aging period for requests in problem statuses will become 180 days.

Queues for problem status include the following:

• RECEIVED?
• NOT RECEIVED
• RECEIVED BUT MISSING
• OVERDUE
• RETURNED/COMPLETE?
• RETURNED BUT MISSING

Any requests that have been in a problem status for 180 days or more will automatically close. If you have unresolved requests that you will need to continue to track after the release, please make note of the request details. Depending on various factors such as age and your request volume, these requests may not be findable in the system after they’re closed automatically.

For more information, see Request Aging.

Product Insights: Resource Sharing

To help you become familiar with the enhancements and fixes included in this release, please attend the upcoming webinar Product Insights: Resource Sharing.