> For the complete documentation index, see [llms.txt](https://docs.3q.video/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.3q.video/user-guide-new-ui/modules/mediarss-exporter.md).
# MediaRSS Exporter
The **MediaRSS Exporter** module allows you to create MediaRSS feeds from your content. These feeds can be used to provide selected media files to external systems, platforms, websites, apps, or syndication workflows.
{% hint style="info" %}
A MediaRSS export can be created manually by adding selected files, or automatically by defining rules that determine which files should be included in the feed.
{% endhint %}
From the MediaRSS Exporter module, users can:
* View existing MediaRSS exports
* Create new MediaRSS exports
* Add files manually to a feed
* Generate automatic MediaRSS feeds based on rules
* Select source projects
* Filter automatic feeds by metadata
* Define the number and maximum age of feed elements
* Share or use the generated MediaRSS feed
The MediaRSS Exporter module is available from the main navigation under **Modules**.
***
### MediaRSS Exporter Overview
The MediaRSS Exporter overview displays all configured MediaRSS exports in a table.
Each row represents one MediaRSS export and includes the most relevant information:
* Export ID
* Title
* Assigned projects
* Creation date
* Available actions
At the top of the page, users can switch between different views:
* **All MediaRSS Exporters**\
Shows all configured MediaRSS exports.
* **Only with Automatic Content**\
Shows only MediaRSS exports that are generated automatically based on rules.
* **Last Edited**\
Shows or sorts exports by their latest changes.
A search field is available to quickly find existing MediaRSS exports.
***
### Manual and Automatic MediaRSS Exports
A MediaRSS export can be managed in two different ways.
#### Manual MediaRSS Export
A manual MediaRSS export is created by adding selected files directly to the feed.
This gives editors full control over which files are included.
Manual feeds are useful when the exported content should be curated individually, for example for a specific partner, campaign, or publication workflow.
#### Automatic MediaRSS Export
An automatic MediaRSS export is generated by the system based on defined rules.
Instead of adding files manually, users configure filters and limits. The system then compiles suitable files from the selected projects and updates the feed automatically.
Automatic feeds are useful for recurring or dynamic workflows, such as latest videos, category-based feeds, partner feeds, or automated content syndication.
***
### Creating a MediaRSS Export
To create a new MediaRSS export:
1. Open **Modules** in the main navigation.
2. Select **MediaRSS Exporter**.
3. Click **Add MediaRSS Export**.
4. The properties panel opens.
5. Enter a **Title**.
6. Optionally add a **Description**.
7. Optionally enter an **Author**.
8. Decide whether the export should be automatic.
9. For automatic exports, configure the rules in the **Configuration** tab.
10. Save the MediaRSS export.
After saving, the export appears in the overview.
***
### Basic Settings
#### Title
The **Title** is the name of the MediaRSS export.
Choose a clear and descriptive title, especially when multiple feeds are used for different projects, partners, or workflows.
Example titles:
* Automatic Feed
* Public Videos Feed
* Partner Export
* Latest News Videos
* Product Video Feed
* Testfeed
#### Description
The **Description** field can be used to add internal notes or information about the purpose of the export.
This field is optional.
Useful information can include:
* Intended target system
* Partner or customer reference
* Content rules
* Editorial notes
* Internal workflow information
#### Author
The **Author** field can be used to define the author information for the MediaRSS export.
This field is optional and can be used when the receiving system expects author metadata in the feed.
#### Automatic MediaRSS Export
The **Automatic MediaRSS Export** option defines whether the feed is managed manually or generated automatically.
When this option is enabled, the system creates the feed based on the rules defined in the **Configuration** tab.
When this option is disabled, users can add files manually to the MediaRSS export.
***
### Managing Manual Feed Elements
For manual MediaRSS exports, users can manage the feed content in the **Edit Elements** area.
The element view shows:
* Number of elements
* Total duration
* Existing files in the feed
* Thumbnail
* Source project
* Title
* Duration
To add files manually:
1. Open the MediaRSS export.
2. Open **Edit Elements**.
3. Click **Add Files**.
4. Search for the files you want to include.
5. Add the selected files to the feed.
Files can be removed from the feed if they should no longer be included.
Manual element management is useful when the exact content of the feed should be controlled by an editor.
***
### Automatic Feed Configuration
For automatic MediaRSS exports, the **Configuration** tab defines which files are included in the feed.
The system compiles suitable files from the specified projects according to the configured rules.
Available configuration options include:
* Projects
* Content type
* Categories
* Types
* People
* Aspect ratio
* Number of elements
* Maximum age of content
The available filters may depend on the account configuration, metadata setup, and selected projects.
***
### Projects
The **Projects** field defines which projects are used as the source for the automatic MediaRSS feed.
Only files from the selected projects are considered for the feed.
This is useful when a feed should only include content from a specific content pool, department, customer, or editorial workflow.
Example use cases:
* Export only files from a news project
* Create a feed for a specific customer project
* Provide only public videos to an external platform
* Build a feed from a dedicated content pool
***
### Content Type
The **Type** setting defines which kind of media content should be included.
Available options include:
* **Video**
* **Audio**
* **Mixed**
Select the type that matches the target system or intended feed purpose.
For example, use **Video** for video syndication feeds, **Audio** for audio-only workflows, and **Mixed** when both media types are allowed.
***
### Metadata Filters
Automatic MediaRSS exports can be filtered by metadata.
Available filters may include:
* **Categories**
* **Types**
* **People**
* **Aspect Ratio**
These filters help control which files are included in the feed.
For example, an automatic feed can be configured to include only videos from a selected project that belong to a specific category or type.
This is useful for structured syndication workflows where external systems should only receive content matching certain editorial or technical criteria.
***
### Aspect Ratio
The **Aspect Ratio** filter can be used to include only files with a specific video format.
This is useful when a target platform requires a certain format or when feeds are created for specific frontend layouts.
Example use cases:
* Landscape videos for standard video portals
* Portrait videos for vertical video experiences
* Format-specific exports for partner platforms
***
### Number of Elements
The **Number of Elements** setting defines how many files should be included in the automatic feed.
This allows users to limit the feed size.
Example configurations:
* Latest 10 videos
* Latest 50 clips
* Latest 100 files
Limiting the number of elements helps keep the feed focused and easier to process by external systems.
***
### Maximum Age of Content
The **Maximum Age of Content** setting defines how old files may be to appear in the automatic feed.
For example, if the maximum age is set to **100 days**, only matching files created or updated within that period are considered for the feed.
This is useful for feeds that should only contain recent or currently relevant content.
***
### Sharing and Using the Feed
MediaRSS exports can be shared or connected to external systems.
Depending on the configuration, users can use the generated MediaRSS feed for:
* External websites
* Apps
* Content portals
* Partner platforms
* Syndication workflows
* Automated import workflows
* CMS or MAM integrations
The receiving system can use the MediaRSS feed to retrieve media information and process the exported content.
***
### Typical Use Cases
MediaRSS Exporter can be used for different workflows, for example:
* Providing a curated feed to a partner platform
* Creating an automatic latest-videos feed
* Exporting selected files to an external system
* Building a category-based syndication feed
* Supplying video metadata to a website or app
* Creating project-specific content feeds
* Exporting only recent content from a selected content pool
* Automating content delivery to downstream systems
***
### Notes
The MediaRSS Exporter module can be booked in **Module Management**.
The available filters and configuration options may depend on the account configuration, project setup, metadata fields, and user permissions.
For automatic exports, review the selected projects, filters, number of elements, and maximum content age carefully to make sure the feed contains the expected files.
Before connecting a MediaRSS feed to a production system, it is recommended to test the feed with representative content.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.3q.video/user-guide-new-ui/modules/mediarss-exporter.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.