[UXPROD-3881] RTAC: Support including holdings from child instances in RTAC response Created: 26/Oct/22  Updated: 30/Nov/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: New Feature Priority: TBD
Reporter: Brooks Travis Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: RTAC, discovery, metadatamanagement, resourceaccess, rtac
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-3880 RTAC: Support including items from ch... Draft
Development Team: None
PO Rank: 0
Rank: Cornell (Full Sum 2021): R5

 Description   

Current situation or problem:

FOLIO's RTAC APIs currently return only those holdings directly linked to the provided instance record via a holdings record. However, FOLIO also supports expressing additional hierarchical (parent-child) relationships among instances. When requesting RTAC for an instance with a child instance, the child instance's associated holdings should be returned as part of the result set.

In scope

  • Updates to mod-rtac and related modules to enable returning not just holdings directly related to an instance record, but those related to child instances, as well.

Out of scope

  • Configuration to support limiting the relationship types for which this is done

Use case(s)

  • Libraries that catalog multi-part monographs using parent-child instance relationship
  • Libraries that catalog collections related loose materials (flyers, pamphlets, personal papers) into multiple distinct items with their own bibliographic significance, but which are part of a larger collection that should be cataloged as a whole
  • "Special" materials such as video game systems and their related game titles that should be findable as a whole or individually

Proposed solution/stories

Links to additional info

Questions

  • Should child instance information be included in the results (title, UUID, HRID, etc.)
  • Should this require a query parameter to invoke?

Generated at Fri Feb 09 00:35:32 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.