Spike: investigate performance impact on providing affected holdings and items count

Description

In the current implementation, when bulk edit job completes, the banner on the Confirmation screen reports how many records have been updated. However, there are some bulk edit jobs that the change affect also other record. For example, when holdings records are suppressed from discovery, the user can also suppress or unsuppress underlying item records. Similarly, when instance records are suppressed from discovery, the user can also suppress or unsuppress underlying holdings and item records. Users would like to be able to see the count of all affected records during the bulk edit job. The purpose of this Jira is to investigate possible performance impact on providing such information and possible way of mitigating it.

Acceptance criteria

  1. Determine performance impact of including counts of affected holdings records and items when setting instances as discovery suppressed or unsuppressed.

  2. Determine performance impact of including counts of affected items when setting holdings records as discovery suppressed or unsuppressed.

  3. Determine possible ways of mitigating the performance impact on non-ECS and ECS environments.

  4. Findings are documented and reviewed with the team and PO

  5. Required technical stories are created.

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

Activity

Show:

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Firebird

Release

Trillium (R2 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created December 13, 2024 at 9:22 PM
Updated February 6, 2025 at 7:32 PM
TestRail: Cases
TestRail: Runs