> For the complete documentation index, see [llms.txt](https://developer.rategain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.rategain.com/content/content-update-1/associating-media-to-textual-content.md).

# Associating media to textual content

Media is made up of all different content types like still images, virtual tours, steaming video and more. DHISCO allows the association of Media to the properties textual content. Media can be tied to descriptive text found within the HCD XML Update Interface message. The following data types (represented below by the OTA message element IDs) can have different media types specifically linked to them:

* HotelInfo (for property images such as exterior, lobby, etc.)
* Service/@Code (for hotel amenities such as pool)
* MeetingRoom
* GuestRoom
* Restaurant
* Attraction
* Recreation

Media is linked to data types via a shared code called a ContentID, which is sent using the attribute ContentID within the Description element. If a data type has media to be associated, a ContentID should be created for that data type. It is up to the supplier to create the ContentID they want to use (must be unique per property). That same ContentID then needs to be referenced when providing the media types and media metadata in order to create the linkage. For example, the property may have two restaurants, each with one or more photos. Each restaurant would then be assigned a unique ContentID. All media for the first restaurant would reference the ContentID assigned to that first restaurant and so on.

It is also possible to associate a single media type to more than one ContentID. For example, a property might have 2 guest rooms that are basically the same with the exception of the view. In this case, both rooms could utilize the same type like photo. Each guest room would have a unique ContentID assigned and the shared photo would then reference both ContentIDs.

If a media type is submitted and does not have a ContentID assigned, it will only be linked to the property and not tied to any specific property attribute, e.g. room, restaurant or guest room. The absence of a linkage between a media type and the textual content in HCD will not prohibit the return or display of that media type.

*NOTE: Only still images may be provided by the supplier using this interface specification. All other media types must be delivered by a certified media provider.*


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://developer.rategain.com/content/content-update-1/associating-media-to-textual-content.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
