> 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/menu/tasks/movie-collection-summary.md).

# Movie Collection Summary

Review the collections that movies are in

![Sample Movie Collection View](https://3508557057-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx0gPeIfHpbgTioNust1M%2Fuploads%2FWQWSA81LFZeCP0RdrMhe%2Fimage.png?alt=media\&token=cdf7cf58-9295-4cd3-8d0f-d538e83563c9)

This looks at all movies that are indicated to be part of a series or collection of movies. For each collection it gets the other movies in the collection and identifies whether they are in the library.

You can:

* Filter records using Checkboxes at the top
  * Remove Completed collections => If all the movies in a collection are in your library, this option will remove the collection from this view
  * Remove Future Movies => If a movie has no release date, or has a future release date it will be removed from the view
* Filter and sort using right-click on Column Headers
* Right-click to add the movie to the library (among other actions)
  * `Force Refresh` - For movies already in the library this allows you to refresh the details of the selected movie
  * `Edit Movie` - View and edit the currently highlighted movie.
  * `Add to Library` - Does a short process to allow you to select the folder the movie should be stored at and adds the metadata to the library.


---

# 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/menu/tasks/movie-collection-summary.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.
