I am attempting to make some modifications to the SportsScanner agent to suit my own purposes. When I do a match search from a file I see a log entry that looks something like this:
2018-04-02 17:38:22,740 (8b38) : INFO (agentkit:958) - Searching for matches for {'released_at': '2018-03-31'...
However, if I attempt to access media.released_at I get an error because TV_Show (see agentkit.py:L701) doesn’t have this property in the model. If I make a local edit and add it everything works great. Of course, the next time I update this will blow up again and I’ll have to make the edit. So, how do I go about making sure this gets added? I mean, the information is provided in the kwargs so why not just map it to a model property, right?
Can anyone tell me of a formal process to get a change like this implemented? Do I just have to hope someone sees this and makes the change?
‘originally_available_at’ is the field name for tv-show and episodes, A date object specifying the movie/episode’s original release date.
‘year’ for movie libraries only
Thanks for the info, but that doesn’t seem to be available. I am logging it out and get a ‘None’ value. I am not a Python guy, so maybe I am doing something wrong? I have seen other logging display something more like an instance of an object though, so it doesn’t seem like I’d get ‘None’ unless the value was not actually set.
Perhaps this is a bit different because these are sporting events with a date in the title? Not sure if the agent bits for TV show have that kind of smarts or not, but things don’t really seem to be the norm for this agent.
Even if there is something weird going on internally for this agent, there is a piece of data being passed into the search that is inaccessible on the model. That doesn’t really make sense, right? So how does one go about informing the Plex team about this and getting things changed, however the Plex devs see fit?
@tim.hobbs media.originally_available_at is used by series in the Update() part. My agent uses it (see mt signature and look at Beta branch).
Search is there to assign a unique id depending on the info provided. no need to pass along that field to update which update solely based on the guid provided by the Search function…
