Skip to content

CIRC-2538: Implement shadow location handling for DCB items in fetchItemRelatedRecords#1679

Open
zakletskyi-epam wants to merge 2 commits into
masterfrom
CIRC-2538
Open

CIRC-2538: Implement shadow location handling for DCB items in fetchItemRelatedRecords#1679
zakletskyi-epam wants to merge 2 commits into
masterfrom
CIRC-2538

Conversation

@zakletskyi-epam

Copy link
Copy Markdown
Contributor

Purpose

Fix retrievalServicePointName storing "DCB" instead of the real service point name for ECS Page requests in Central tenant.

Approach

fetchItemRelatedRecords (single-item path) was using locationRepository (regular /locations) to resolve a DCB shadow item's location, which returns the DCB virtual service point as primary. The fix mirrors the existing pattern from the batch fetchLocations path — routing DCB items (isDcbItem() == true) to shadowLocationRepository (/locations?includeShadowLocations=true), which returns the correct primary service point.

TODOS and Open Questions

  • Check logging
  • Use GitHub checklists. When solved, check the box and explain the answer.

Learning

CIRC-2538

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant