Skip to content

feat(titles): migrate titles and resources to HoldingsIQ v2 API - #727

Merged
psmagin merged 1 commit into
masterfrom
MODKBEKBJ-830
Oct 21, 2026
Merged

psmagin merged 1 commit into
masterfrom
MODKBEKBJ-830

Conversation

@psmagin

@psmagin psmagin commented Oct 20, 2026 •

Copy link
Copy Markdown
Collaborator

Purpose

Migrate titles and resources to HoldingsIQ v2 API

Approach

  • Use folio-holdingsiq-client v2 title and resource endpoints; resources are handled as the flat v2 Resource model, nested titles keep Title
  • Map module title/resource filters to the client TitleFilter and ResourceFilter; package resources are loaded through the resources service
  • Check whether a title is already in a package with a direct resource lookup instead of a title name search
  • Keep resource visibilityData: hidden when at least one category is hidden, and applied to PF, FTF and MARC on update
  • Add filter[zdbid] and filter[access] to titles and package resources search
  • Add visibility per category, packageType, isPrimaryPackage and isOrderedThroughEbsco to resources
  • Add title relationships to title and resource records with include=relationships
  • Rename PackageVisibility schema to Visibility, shared by packages and resources
  • Migrate title and resource test stubs and fixtures to v2

Changes Checklist

  • API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
  • Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
  • Interface Version Changes: Indicate any changes to interface versions.
  • Interface Dependencies: Document added or removed dependencies.
  • Permissions: Document any changes to permissions.
  • Logging: Confirm that logging is appropriately handled.
  • Unit Testing: Confirm that changed classes were covered by unit tests.
  • Integration Testing: Confirm that changed logic was covered by integration tests.
  • Manual Testing: Confirm that changes were tested on local or dev environment.
  • NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues

https://folio-org.atlassian.net/browse/MODKBEKBJ-830
https://folio-org.atlassian.net/browse/MODKBEKBJ-831
https://folio-org.atlassian.net/browse/MODKBEKBJ-833
https://folio-org.atlassian.net/browse/MODKBEKBJ-834

@psmagin psmagin self-assigned this Oct 21, 2026
@psmagin psmagin added the ai label Oct 21, 2026
@psmagin
psmagin marked this pull request as ready for review October 21, 2026 08:49
@psmagin
psmagin requested a review from a team as a code owner October 21, 2026 08:49
- Use folio-holdingsiq-client v2 title and resource endpoints; resources
  are handled as the flat v2 Resource model, nested titles keep Title
- Map module title/resource filters to the client TitleFilter and
  ResourceFilter; package resources are loaded through the resources service
- Check whether a title is already in a package with a direct resource
  lookup instead of a title name search
- Keep resource visibilityData: hidden when at least one category is hidden,
  and applied to PF, FTF and MARC on update
- Add filter[zdbid] and filter[access] to titles and package resources search
- Add visibility per category, packageType, isPrimaryPackage and
  isOrderedThroughEbsco to resources
- Add title relationships to title and resource records with
  include=relationships
- Rename PackageVisibility schema to Visibility, shared by packages and resources
- Migrate title and resource test stubs and fixtures to v2

Closes: MODKBEKBJ-830
@sonarqubecloud

Copy link
Copy Markdown

@psmagin
psmagin merged commit 6c4c127 into master Oct 21, 2026
20 checks passed
@psmagin
psmagin deleted the MODKBEKBJ-830 branch October 21, 2026 11:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants