mirror of
https://github.com/Radarr/Radarr.git
synced 2026-03-02 22:57:34 -05:00
Premier year of a movie for (interactive) search and matching #9330
Labels
No labels
Area: API
Area: Database
Area: Db-migration
Area: Download Clients
Area: Extras
Area: Import Lists
Area: Indexer
Area: Metadata API
Area: Notifications
Area: Organizer
Area: Parser
Area: Scanning
Area: Tooling
Area: UI
Area: Unit Tests
On Hold: MetadataAPI Blocking
On Hold: MetadataAPI Blocking
Priority: High
Priority: Low
Priority: Medium
Status: Accepted
Status: Cannot Reproduce
Status: Confirmed
Status: Help Wanted
Status: In Progress
Status: Indexer - need invite
Status: Info Needed
Status: Investigating
Status: Logs Needed
Status: Maybe One Day
Status: Needs Triage
Status: On Hold
Status: Ready for Review
Status: Unlikely
Status: Waiting for OP
Status: Won't Fix
Type: Bug
Type: Documentation
Type: Duplicate
Type: Enhancement
Type: External Bug
Type: Feature Request
Type: Regression
Type: Support
Type: Support.
conflict
lidarr-pull
no-conflict
not-pulled
readarr-pull
readarr-pull
sonarr upstream
sonarr-pull
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Radarr#9330
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @erwinkramer on GitHub (Dec 30, 2025).
Is there an existing issue for this?
Is your feature request related to a problem? Please describe
As #11221 explained, primary movie years are inconsistent across movie metadata providers. An example, Brick from 2005 is known as Brick from 2006 too, but they are both the same. See:
2005 entries:
2006 entries:
In Radarr, interactive search won't work, because the movie is commonly being referenced as 2005, but not as 2006. The latter is what Radarr seems to be solely using.
More context on the TMDB forum: https://www.themoviedb.org/talk/60ec2b2be004a60046027b89. If i had to guess, this is an issue for about 0.5-1% of all movies.
TMDB API response:
Describe the solution you'd like
Include the earliest premier year for (interactive) search (and matching) too.
As seen in the API response, it is premiered (
"type": 1) in 2005 (twice) and 2006, so it would make sense to have the earliest premier year as something that is used for (interactive) search at least.According to servarr: "Radarr uses the year of the oldest Theatrical Release date for primary purposes and the oldest Premier date as secondary only for matching." - https://wiki.servarr.com/en/radarr/faq#how-does-radarr-determine-the-year-of-a-movie - according to this logic, it should use 2005 as year for interactive search too, or does that not mean 'matching'? If it also counts as matching, then I assume this request is not a feature but a bug.
Describe alternatives you've considered
.
Anything else?
.
@mynameisbogdan commented on GitHub (Dec 30, 2025):
Radarr does not calculate the year, it's uses the year from TMDb based on their rules. Read more at https://www.themoviedb.org/bible/movie/59f3b16d9251414f20000009#5a0b2152925141656100000d which would explain the year for Brick.
Radarr only uses the releases dates to calculate availability based on your picked option, and uses premier year for matching only if the years are different.
Changing how this works would most likely break a lot of other movies, since groups could use TMDb as metadata source too. My suggestion to you for Brick is to at least contact TMDb and request for the year to be changed to 2005 if possible if you consider it to the correct one.
@erwinkramer commented on GitHub (Dec 30, 2025):
Well then why shouldn't it be used for (interactive) search? Seems to be low risk.
@mynameisbogdan commented on GitHub (Dec 30, 2025):
Maybe only as a fallback with only the original titles to prevent duplicating the requests, like I said on discord. Fallback means only if other searches returned 0 results, not an separate search.
BTW, most people with proper indexers won't notice the year discrepancy because searching by imdbid or tmdbid doesn't care about the year. An workaround for your issue for now is to enable
Remove Yearin the indexer settings in radarr > settings.@erwinkramer commented on GitHub (Dec 30, 2025):
Thanks, I didn't know about this setting, and this is a nice workaround for now.