Details
Assignee
UnassignedUnassignedReporter
Pavlo SmahinPavlo SmahinLabels
Priority
P3Development Team
SpitfireRelease
Not ScheduledTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Unassigned
UnassignedReporter
Pavlo Smahin
Pavlo SmahinLabels
Priority
Development Team
Spitfire
Release
Not Scheduled
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created March 10, 2025 at 9:10 AM
Updated March 10, 2025 at 9:11 AM
Overview:
In a consortium environment, MARC authority records can be either shared across tenants within the consortium or local to each tenant. Report generation in
mod-data-export-worker
currently does not distinguish between shared and local records or reflect this distinction in export output. To improve clarity for users, reports such as "Failed updates: linked bibliographic fields" and "MARC authority headings update" should include appropriate columns ("Instance record type" and "Authority record type") with the values "Shared" or "Local", depending on the record type. For non-consortium environments, these columns should not appear in the reports.This story builds on the solution implemented in
mod-entities-links
, leveraging the newly extended statistics model with the source field (shared
orlocal
) for seamless integration withinmod-data-export-worker
.Requirements:
Extend report generation logic in
mod-data-export-worker
to include record type columns in the output for consortium environments.Ensure the source field (
shared
orlocal
) in the statistics model is accurately reflected in the reports.Prevent inclusion of unnecessary columns when the tenant is NOT in a consortium environment.