[42] fix docs typos

This commit is contained in:
meisnate12 2023-04-27 23:14:07 -04:00
parent 0fbd026a3c
commit 779c32cbe7
6 changed files with 16 additions and 27 deletions

View file

@ -1 +1 @@
1.19.0-develop41
1.19.0-develop42

View file

@ -21,7 +21,6 @@ templates:
tautulli_<<type>>:
list_days: <<list_days_<<key>>>>
list_size: <<list_size_<<key>>>>
list_buffer: 20
collections:
Plex Popular:

View file

@ -16,17 +16,10 @@ It has watch analytics that can show the most watched or most popular Movies/Sho
Both Tautulli Popular and Tautulli Watched have the same sub-attributes detailed below.
| Attribute | Description | Required | Default |
|:---------------|:-------------------------------------------------------------------------------------|:--------:|:-------:|
| `list_days` | Number of Days to look back of the list | &#10060; | 30 |
| `list_minimum` | Minimum Number of Users Watching/Plays to add to the list | &#10060; | 30 |
| `list_size` | Number of Movies/Shows to add to this list | &#10060; | 10 |
| `list_buffer` | Number of extra Movies/Shows to grab in case you have multiple show/movie Libraries. | &#10060; | 10 |
If you have multiple movie Libraries or multiple show Libraries Tautulli combines those in the popular/watched lists so there might not be 10 movies/shows from the library to make your `list_size`.
In order to get around that, you can use the `list_buffer` attribute that defaults to 10. This will get that number more movies from Tautulli but only add to the collection until the size reaches the number in `list_size`.
So if your collection doesn't have as many movies/shows as your `list_size` attribute increase the number in the `list_buffer` attribute.
|:---------------|:-----------------------------------------------------------|:--------:|:-------:|
| `list_days` | Number of Days to look back of the list. | &#10060; | `30` |
| `list_minimum` | Minimum Number of Users Watching/Plays to add to the list. | &#10060; | `0` |
| `list_size` | Number of Movies/Shows to add to this list. | &#10060; | `10` |
The `sync_mode: sync` and `collection_order: custom` Details are recommended since the lists are continuously updated and in a specific order.
@ -47,7 +40,6 @@ collections:
tautulli_watched:
list_days: 30
list_size: 10
list_buffer: 20
```
```yaml
collections:
@ -55,11 +47,9 @@ collections:
tautulli_popular:
list_days: 30
list_size: 20
list_buffer: 20
tautulli_watched:
list_days: 30
list_size: 20
list_buffer: 20
sync_mode: sync
summary: Movies Popular on Plex
collection_order: alpha
@ -71,7 +61,6 @@ playlists:
tautulli_popular:
list_days: 30
list_size: 20
list_buffer: 20
sync_mode: sync
summary: Movies Popular on Plex
```

View file

@ -3,6 +3,7 @@
You can have the script edit the metadata of Movies by adding them to the `metadata` mapping of a Metadata File.
An example of multiple metadata edits in a movie library is below:
```yaml
metadata:
Godzilla (1954):
@ -210,7 +211,7 @@ The available attributes for editing movies are as follows
|:-----------------------|:---------------------------------------------------------------|
| `title` | Text to change Title. |
| `sort_title` | Text to change Sort Title. |
| `edition` | Text to change Edition. |
| `edition`<sup>1</sup> | Text to change Edition. |
| `original_title` | Text to change Original Title. |
| `originally_available` | Date to change Originally Available.<br>**Format:** YYYY-MM-DD |
| `content_rating` | Text to change Content Rating. |
@ -221,6 +222,8 @@ The available attributes for editing movies are as follows
| `tagline` | Text to change Tagline. |
| `summary` | Text to change Summary. |
1. Requires Plex Pass
### Tag Attributes
You can add `.remove` to any tag attribute to only remove those tags i.e. `genre.remove`.

View file

@ -49,13 +49,13 @@ The below example shows how `title` can be used to match artists.
```yaml
metadata:
artist1: # Matches via the title "Game of Thrones"
artist1: # Matches via the title "Ke$ha"
match:
title: Game of Thrones
title: Ke$ha
edits...
artist2: # Matches via the title "24"
artist2: # Matches via the title "311"
match:
title: 24
title: 311
edits...
```
@ -63,14 +63,12 @@ The Mapping Name can also be used to reduce line-count, as shown here:
```yaml
metadata:
Ke$ha: # Matches via the Name "Game of Thrones"
Ke$ha: # Matches via the Name "Ke$ha"
edits...
"311": # Matches via the Name "311"
edits...
```
**Note:** to search for an artist titled with a number from the mapping name you must surround the number in quotes like in the example below. Otherwise, it will look for the artist associated with that TVDb ID.
## Metadata Edits
The available attributes for editing artists, albums, and tracks are as follows

View file

@ -1512,7 +1512,7 @@ class MetadataFile(DataFile):
titles.extend(util.parse(self.type_str, "title", value, datatype="strlist"))
if not titles:
titles.append(mapping_name)
titles.append(str(mapping_name))
if "alt_title" in methods:
logger.debug("")