Alerts and notifications for acquisitions

Related Jira tickets and Confluence pages

https://folio-org.atlassian.net/wiki/x/gxkb

Problem

A growing number of libraries is asking for alerts and notifications related to tasks that need to be done, conditions that need to be addressed and similar. In other words, libraries want to be alerted to things that require their attention rather than having to perform manual steps to see if these issues need to be addressed.

 

Requirements and use cases

Requirement

Status

Use case(s)

Requirement

Status

Use case(s)

Alert staff of unarrived materials based on library-selected criteria (such as receiving status and vendor)

confirmed

Library wants to be alerted to generate time-sensitive claims for certain vendors or titles.

Library wants to be alerted that a group of claims is ready to be reviewed before sending.

Library wants to be alerted when previously claimed material has still not been received based on claim interval.

Alert staff of pending renewals for ongoing orders based on certain criteria (such as days before renewal)

confirmed

Library wants to be alerted to review upcoming subscription renewals

Alert staff a group of materials is ready to be bound

ACQ-Sig

Library sends journals to be bound after a certain number of issues have arrived. Library wants to be notified that journals are ready to be bound once that offset threshold is reached.

Notify acquisitions staff of a purchase request

ACQ-Sig

Library patrons are able to request a purchase for material. If this was to generate a pending order acq staff would need to be notified so it could be reviewed and processed

Notify users of duplicate orders that could be canceled or deleted

ACQ-Sig

User is importing a number of orders from an external system. Post import if the orders are identified as duplicates they should be flagged and user should be notified.

Notification of last copy OR cancelation of subscription

ACQ-Sig

  • User at member library A cancels "only" subscription for a given material. Patrons at member library B might be relying on access to that material and will no longer be able to use it. User at library A is notified so they can make a decision whether they now must acquire that material to maintain access.

  • When a libraries copy of something becomes the only one left in the consortium the demand for that item could become more difficult to manage very quickly. User at the library must determine whether to purchase additional copies.

Possible approaches