#Is it possible to limit a file-based collection by year of the movies?

1 messages ยท Page 1 of 1 (latest)

tranquil gull
#

I was hoping to publish a specific library that contains only Christmas movies in the last 5 years by editing my standard Christmas list to just take movies from the last 5 years using the 'starting' and 'ending' flags under template_variables.

I've tried the config below and it creates a new collection but does not limit it to the years provided.

Is this possible, or do I have to go into IMDB and create custom versions of each holiday playlist that is confined to the years I want? Thanks!

Here is the relevant section of my config.yml:

#config.yml
    metadata_path:
    - file: config/movies/movies.yml
    - pmm: actor
    - pmm: genre
    - pmm: content_rating_us
    - pmm: franchise
    
    - file: config/movies/modern_christmas_movies.yml
      template_variables:
        data:
          starting: current_year-5
          ending: current_year
#modern_christmas_movies.yml

templates:
  Modern_Holiday:
    url_poster: <<poster>>
    sort_title: +++++++++_<<collection_name>>
    collection_order: release.desc
    delete_not_scheduled: true
    visible_home: true
    visible_shared: false
    visible_library: true
    sync_mode: sync

collections:
   Modern Christmas Movies:
    schedule: range(11/22-1/8)
    template: {name: Modern_Holiday, poster: https://theposterdb.com/api/assets/69443}
    sort_title: +++++_Christmas_Modern
    trakt_list:
      - https://trakt.tv/users/movistapp/lists/christmas-movies
      - https://trakt.tv/users/pualani78/lists/christmas-2020
      - https://trakt.tv/users/veninjak/lists/complete-christmas-2021-copy
    imdb_list:
      - https://www.imdb.com/list/ls025976544/
      - https://www.imdb.com/list/ls003863000/
      - https://www.imdb.com/list/ls526077529/ #christmas 2023 list
#... (a couple of other lists excluded for brevity)
idle wagonBOT
#

Welcome @tranquil gull!

Someone from <@&938443185347244033> will assist when they're available.

Including the meta.log from the beginning is a huge help, type !logs for more information.

#

You can press the "Close Post" button above or type /close at any time to close this post.

low sphinxBOT
#

1: Go to your config folder

2: Go into the logs folder

3: Look for meta.log (not meta.1.log etc)

4: Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

5: Still confused? ยฏ\(ใƒ„)/ยฏ

Log file too big? USE PASTEBIN or ZIP THE FILE

tranquil gull
idle wagonBOT
#

๐Ÿ“ If you want to review this again, myrison:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

#

๐Ÿ“ If you want to review this again, bullmoose20:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

idle wagonBOT
# idle wagon
**Rec 01** - ๐Ÿš€ **VERSION UPDATE AVAILABLE**

๐Ÿš€ VERSION UPDATE AVAILABLE
Current Version: 1.18.2 (Docker)
Newest Version (at the time of this log): 1.19.1

Latest PMM Versions (as of 2023-12-23 19:48:43)
Master branch: 1.19.1
Develop branch: 1.19.1-develop33
Nightly branch: 1.19.1-nightly60

In the PMM discord thread, type !update for instructions on how to update.
For more information on updating, [https://www.metamanager.wiki/en/latest/home/kb.html#checking-plex-meta-manager-version]
2 line(s) with New Version errors. Line number(s): 10, 3833

lucid grove
#

Oh wow... I haven't seen someone on 1.18.2 in months if not a year.

#

Can you upgrade PMM?

#

And move to develop branch?

low sphinxBOT
#

NOTE: This is addressing UPDATING your current setup, not changing from, for instance, latest to nightly.

The update method depends on how you installed it.

I'm running locally and got the code by downloading the zip file:
Download a new zip file, uncompress it, and move your config dir into that new directory. Reinstall requirements.

This is the "fussiest" method of update.

I'm running locally and retrieved the code via git:

cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

You may need to reinstall requirements if switching branch or updating to a new major version:
python -m pip install -r requirements.txt

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

I'm using docker locally:

docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.].

I'm using docker on a NAS or some other remote context:

Update the image using whatever means the NAS provides.
Depending on the system, this might be a simple rebuild of the container, or you may need to manually pull the new image first.

#

NOTE: This is addressing changing from, for instance, latest to nightly.

The method depends on how you installed it.

**I'M USING DOCKER:**
docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.], setting the image as meisnate12/plex-meta-manager:TAG_HERE

**I'M USING DOCKER ON UNRAID**

:one: Click on DOCKER tab and then on Plex-Meta-Manager
:two: Edit Repository: setting to switch branches:

meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.

**I'M USING DOCKER ON A SYSTEM WITHOUT COMMAND PROMPT (SUCH AS NAS):**

The same concepts as above will apply:
:one: pull new image
:two: recreate container using that image instead of the current one.

Whatever the system, there will be a way to accomplish these two things.

**I'M RUNNING LOCALLY VIA GIT:**
cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

tranquil gull
#

Sure @lucid grove , I can. Is what I'm asking about possible in the newest version?

quasi hemlock
#

its just hard to troubleshoot when not updated

lucid grove
#

Exactly... the wiki for that version is no longer available so I don't even know what might be going on....

tranquil gull
#

okie dokie... I'm using Docker so that should be easy enough, one moment.

lucid grove
#

Super easy

tranquil gull
#

can you please remind what I add to my run command to switch to the develop branch? This is what I'd do otherwise for the main branch:

docker run -it -v /mnt/docker/plex-meta-manager:/config:rw meisnate12/plex-meta-manager:v1.19.1

#

oh wait... look at that, I think it's right up above in the help text...

lucid grove
#

Yes. I posted the bot message for updates and for branches

#

:develop instead of :v1.19.1

#

Also pretty sure you need to pull it down before you run

#

You are running an interactive session...

#

Not sure why exactly

tranquil gull
#

ok here is the log from the develop version. No change in terms of results,but at least we can rule out any old version issues. Thanks for taking a look.

idle wagonBOT
#

๐Ÿ“ If you want to review this again, myrison:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

#

๐Ÿ“ If you want to review this again, bullmoose20:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> ๐Ÿ“

idle wagonBOT
hexed iron
#

template_variables are specific to the PMM Defaults

#

you cannot freely use it/them on any file

tranquil gull
#

ok thanks for confirming, that's what I needed to know.

quasi hemlock
#

you could possibly limit it within your yml file, since you are not using the default

tranquil gull
#

Thanks @quasi hemlock , would I use the same parameters? Where I would I place this in the movies.yml file?

      starting: current_year-5
      ending: current_year
quasi hemlock
#

no, cause again those are variables within the defaults. i haven't used my own collections like that yet, but also depends on how you have your yml set up

tranquil gull
#

ok, got it... I'm just going to combine some of the bigger lists in IMDB by exporting/importing, that should get it done. Thank you for the help, I appreciate it. happy holidays!

hexed iron
#

starting and ending are for Dynamic Collections so also can't be used here ๐Ÿ˜„

#

if you can send this file:
modern_christmas_movies.yml

#

rather than posting the code, attach the full file

#

we can look at what can be done to help

tranquil gull
#

Ok thanks for the offer, that's very nice of you. It'd be interesting to know if there is another way to do it other than manual manipulation of IMDB lists (which is what the last line in the file now represents)

hexed iron
#

adding this to the bottom will do the trick:

    filters:
      release: 1825

filters anything not released in the past 1825 days (5 years)

lucid grove
#

What about leap years? ๐Ÿ˜›

tranquil gull
#

lol... I think I can live without accounting for leap years @lucid grove . @hexed iron , awesome, thanks, I will try it out!

low sphinxBOT
#

NOTE: This is addressing UPDATING your current setup, not changing from, for instance, latest to nightly.

The update method depends on how you installed it.

I'm running locally and got the code by downloading the zip file:
Download a new zip file, uncompress it, and move your config dir into that new directory. Reinstall requirements.

This is the "fussiest" method of update.

I'm running locally and retrieved the code via git:

cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull

For BRANCH_NAME, substitute master, develop, or nightly

You may need to reinstall requirements if switching branch or updating to a new major version:
python -m pip install -r requirements.txt

Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.

I'm using docker locally:

docker pull meisnate12/plex-meta-manager:TAG_HERE

replace TAG_HERE with latest, develop, or nightly

Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.].

I'm using docker on a NAS or some other remote context:

Update the image using whatever means the NAS provides.
Depending on the system, this might be a simple rebuild of the container, or you may need to manually pull the new image first.

idle summit
#

Anything further needed here?

lucid grove