I’ve noticed this is a particularly a problem with foreign films. It seems like Plex is trying to pull the films’ first non-festival US release date, which in some cases is decades after the original release date. Take Il Sorpasso for example:
The original release date is 1962. However, Plex seems to be pulling the US DVD release date in 2014 (when it was picked up by Criterion).
I think saying “some data will always be wrong because it was entered by humans” is reductive and missing the point here. Of course there will always be input errors, but this is obviously a deeper issue and not just a few incorrect dates.
I went to TheMovieDB.org and shockingly, despite being entered by humans, the 1962 date is correct there. And if it wasn’t, it would take me a total of 5 clicks and typing a new date to correct it. It took me much longer to type this post than it would have to assess and correct data on that site.
And you still can (well when site like TVDB do not lock it). and new data from those sites will get ingested in about 2 days as everything is always being updated. There is constant queue when something is at bottom of queue it takes about 2 days to update.
Again you can edit things like the year a movie came out on your server anytime you want. You can make thing come out in the future if you want
Why do you think that one of your paying customers opened this thread? Why do you think he kept replying after the first time you said “you can just fix it yourself on your server”?
I have already explained “how this is happening?”. Not liking the truthful answer doesn’t change the answer.
Data is wrong sometimes, caches get stuck. API’s can return different data than what is seen on site. This happened and still happens with legacy agents as well.
Whether the agents writes the data to server or you edit it yourself it is written to the same place.
