Skip to end of banner
Go to start of banner

Alerts and notifications for acquisitions

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Related Jira tickets and Confluence pages

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

https://folio-org.atlassian.net/issues/?jql=key%20%3D%20%22UXPROD-2327%22%20OR%20key%20%3D%20%22UXPROD-4920%22%20OR%20key%3D%20%22UXPROD-4154%22%20OR%20key%20%3D%20%22UXPROD-832%22%20OR%20key%20%3D%20%22UXPROD-890%22%20ORDER%20BY%20created%20ASC

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)

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.

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

PENDING

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.

Possible approaches

  • No labels