Backoffice Products

Release notes - v1.4.0

Planned

Metadata-staging and Metadata-Prod: Rollout scheduled on June 24, 2026.
Metadata-QA: Rollout scheduled on June 12th, 2026

Beta v1.4.0. Environment Information:

PROD Bank Baseurl: https://api.metadata.services.pbs.org/rest/v1

QA Bank Baseurl: https://qa.metadata.services.pbs.org/rest/v1 


Core REST API Endpoint: 

QA

https://qa.metadata.services.pbs.org/core/v1

Header: "Authorization: Bearer <access_token>"

Production: 

https://api.metadata.services.pbs.org/core/v1

Header: "Authorization: Bearer <access_token>" 

________________________________________________________________________________

Release Overview
We are pleased to introduce a backend enhancement aimed at improving the scalability and maintainability of content identifier management across the platform.

This update focuses on internal data handling improvements and does not impact existing APIs, request/response payloads, or integrations.

What’s Changed

The ContentIds field (previously stored as a JSONB array in entity tables such as Series, Season, Episode, etc.) has been refactored internally. Content identifiers are now managed through a new cross-reference (xref) table where: Each Content ID is stored as an individual record Array-based storage is replaced with multiple normalized rows

What This Means for You

No changes to API contracts

Existing REST API endpoints remain unchanged Request and response payloads are fully backward compatible

No action required

Client applications and integrations will continue to function as-is No updates to code or configurations are required


Benefits of This Enhancement

Improved performance and scalability for handling large volumes of Content IDs Better data normalization enabling more efficient querying and indexing Enhanced maintainability and future extensibility of the data model


Compatibility

Fully backward compatible No breaking changes No impact on existing API consumption patterns


Enhanced Payload Column In Each Entity
The following payload fields are included across entities:

  • ContentIDList for Series, Season, Episode, Compilation, and Manifestation entities 
  • AlternateContentIDList for Edit and Supplemental entities 
  • AlternateAssetIDList for File entity 
  • AlternateEventIDList for Events entity
  • LogicalAssetIDList for Policy, Permission, Prohibition, and Funder entities
Login or Signup to post a comment