> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/fabric-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/fabric-knowledge-base/resources/use-cases-and-best-practice/storing-news-program-in-fabric-studio.md).

# Storing News Program in Fabric Studio

This guide outlines best practices for modelling, storing, and managing news programs in Fabric Studio, using a clear and scalable metadata structure.

### 📺 Overview

News programs often differ from scripted content in how they are structured and catalogued. Fabric Studio offers flexibility to represent both **seasonless** and **season‑based** news formats while maintaining discoverability and metadata consistency.

This use case focuses on structuring a news program—specifically *Evening News*—so that episodes are organised yearly for easier navigation and metadata management.

***

### 🧩 Core Metadata Structure

Fabric Studio’s out‑of‑the‑box metadata model includes:

* **Show** level metadata
* **Season** level metadata
* **Episode** level metadata

Although originally designed with scripted programming in mind, this model can be adapted for news content without technical limitations.

#### ✅ Recommended Structure for News

**Show:** Evening News\
**Season:** 2025 (or any calendar year)\
**Episode 1:** 01/01/2025\
**Episode 2:** 02/01/2025\
…and so on.\ <br>

<figure><img src="https://1453363788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPS7xvtVOuEwjKjl1m1Xs%2Fuploads%2FDdn58TO3lOCYDsVfcc9z%2Fimage.png?alt=media&amp;token=8aee1a8a-b494-4b8b-b574-fa134ffee4a6" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1453363788-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPS7xvtVOuEwjKjl1m1Xs%2Fuploads%2FotdOplwXMz7fJSOLP8us%2Fimage.png?alt=media&amp;token=b8763361-467e-4f60-9f77-c7fd3e3d3695" alt=""><figcaption></figcaption></figure>

This structure allows:

* Daily episodes to be easily located by date
* Quick grouping by year
* Compatibility with downstream systems using standard EIDR‑aligned hierarchy

***

### 📌 Why Seasons Represent Years

Although news programs are often considered *seasonless*, mapping seasons to calendar years is beneficial:

* Ensures **EIDR alignment**, where seasons may still exist as organisational nodes
* Creates **clean yearly segmentation**, especially useful for daily or high‑volume content
* Improves **episode discoverability**, as users can immediately navigate to a relevant year
* Avoids overloading a single season with thousands of entries

***

### 📝 Working With Episode Metadata

Fabric's episode-level metadata is generally designed for scripted content, but **all existing fields remain usable** for news.

For example, you can map:

* "Episode Title" → Broadcast Date
* "Air Date" → Transmission Date
* "Synopsis" → Summary of story highlights

You may reuse fields as long as they provide value to your workflow.

To make sure you can easily differentiate News content, it is suggested that you create a specific **record type** for Episodic News.&#x20;

***

### 🗂️ Adding News‑Specific Metadata

News programs often require additional metadata not found in standard episodic structures (e.g., story lineup, anchors, editorial restrictions, segment summaries).

#### ✔ Use **Metadata Sections**

Fabric Studio allows you to create dedicated **Metadata Sections** to store domain‑specific information. A section lets you:

* Group custom fields relevant only to news
* Apply **permissions** to control which users can view or edit the section
* Keep the default metadata clean and consistent across asset types

Example section: **News Editorial Metadata**

* Lead Presenter
* Key Stories
* Political Sensitivities
* Compliance Notes
* Running Order

This ensures that specialised metadata does not interfere with standard metadata used by the wider organisation.

***

### 🔐 Permission Management

Using sections, you can assign fine‑grained access rights so that only:

* Editorial staff can modify news‑specific fields
* Compliance teams can view regulatory notes
* Producers can edit running order metadata

This keeps sensitive metadata secure while ensuring each team sees only what's relevant.

***

### ✅ Summary

By organising news programs using a structured Show → Season (Year) → Episode (Date) hierarchy and leveraging custom Metadata Sections, Fabric Studio provides:

* High discoverability for daily episodes
* Flexibility to store news‑specific metadata
* Secure access control
* Compatibility with EIDR and existing Studio workflows

This approach ensures your news content remains organised, scalable, and easily maintainable across teams and systems.