> For the complete documentation index, see [llms.txt](https://www.tvrename.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.tvrename.com/guides/features/organising.md).

# Organising

While the main objective of TV Rename is to rename and move/copy files into the appropriate locations in the library, there are many other things it can do at the same time:

### Keep Files Together <a href="#keep-files-together" id="keep-files-together"></a>

The system will keep files that share the same name together, renaming them all as one. This keeps related files (images, information, metadata) joined together. The system can also be configured to keep language specific files together for when you have subtitles in multiple languages.

{% hint style="info" %}
Further information can be found [**here**](https://www.tvrename.com/menu/preferences/files-and-folders.md).
{% endhint %}

### File Update Timestamp <a href="#file-update-timestamp" id="file-update-timestamp"></a>

The system can also be requested to update the ‘last updated’ dates to match the air-dates. This aims to help DLNA systems, but be wary if you are using a Linux based system such as a NAS for your media library. Linux has an inception date of 01/01/1970 and does not support earlier dates.

### DVD vs Aired Order <a href="#dvd-vs-aired-order" id="dvd-vs-aired-order"></a>

TV Rename can order a series in 3 ways at present:

* Aired Season Order
* DVD Season Order
* Alternate Order

To show how these are different take a look at Futurama on [The TVDB](http://thetvdb.com/series/futurama) and you can see that the episode order on DVD does not match the Aired order. The order is chosen for each show with **Use DVD Order** or **Use Alternate Order** on the [Advanced tab](https://www.tvrename.com/main/my-tv-shows.md#the-advanced-tab) of Add/Edit Show.

**Future Ideas**

There are a few ideas on the ideas wall to allow the ordering to be adjusted further to account for shows such as Mythbusters and American Dad. In both these cases the order that users want to organise the files does not match either the Aired or the DVD order.

* [**Allow reorganising season numbers**](https://github.com/TV-Rename/tvrename/issues/67)
* [**Allow offset for episode numbers**](https://github.com/TV-Rename/tvrename/issues/108)

### Media Centres <a href="#media-centres" id="media-centres"></a>

In addition to renaming and moving files the system can also download/create files for various media players:

* Kodi
* Mede8er
* pyTivo
* WD TV Live Media Player
* others

In each case the following types of files can be downloaded

* Fanarts, banners and posters
* Episode screenshots
* XML/Text files to explain details about the show/series/episodes

{% hint style="info" %}
Further information on the settings needed is [here](https://www.tvrename.com/menu/preferences/media-centres.md)
{% endhint %}

**Future Ideas**

There are plans to add support for other media centres and provide additional information by analysing the video files in more detail:

* [**Get the codec, size etc and use to show images in the show guide**.](https://github.com/TV-Rename/tvrename/issues/1040)
* [**AtomicParsley/MKVPropEdit support**](https://github.com/TV-Rename/tvrename/issues/1041)
* [**Support for additional Media Centres**](https://github.com/TV-Rename/tvrename/issues/1042)


---

# 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://www.tvrename.com/guides/features/organising.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.
