The Movie Database 支持

When sending a request with pagination within to API endpoints, there is no sorting, for example, according to the vote_average field.
So, why is there no similar query parameter, for example
api.themoviedb.org/3/trending/movie/week?page=2&order-by=vote_average

6 回复(第 1 页,共 1 页)

Jump to last post

Hi @gurkantuna,

For the trending data, this is by design. Trending is only useful to view in its original trending order. If you want more flexibility (although, there is no trending data) you should look at discover.

@travisbell said:

Hi @gurkantuna,

For the trending data, this is by design. Trending is only useful to view in its original trending order. If you want more flexibility (although, there is no trending data) you should look at discover.

Thanks @travisbell , actually I wasn't just talking about only trending, but I think that the case I mentioned is also required for trending data. It doesn't matter if it is a trend data or any other filter, the paginated data should return by any sorting parameter.

You can review it from
https://movies.gurkantuna.com/genre/28/pages/2 => order by vote_up from 8.2
https://movies.gurkantuna.com/genre/28/pages/3 => order by vote_up from 8.2 again!

The data that should be there is below
/pages/2 example 20 data 8.2, 8.2, 8.1.......8.0
/pages/2 example 20 data 8.0, 8.0, 7.9,7.8.......7.7

However, you should have noticed that the vote_up ranking only exists based on the page you are on and does not continue from the next page. Because there is no endpoint in the API from where I can pull data in this way. So, have I explained this clearly now?

You should take a look at the discover endpoints. They are the only endpoints that support more dynamic queries like this. The options for sort_by are listed there.

@travisbell said:

You should take a look at the discover endpoints. They are the only endpoints that support more dynamic queries like this. The options for sort_by are listed there.

https://api.themoviedb.org/3/discover/movie?api_key=***&with_genres=16&sort_by=vote_average.desc

I'm currently receiving data that is close to my intention with 'sort_by=vote_average.desc'. But even weird movies with a budget of $0 seem to get 10 points :)
It seems like your backend service calculates the average even for 1 vote, which I think is wrong and open to similar manipulation. You should include the average calculation at least after 50-60~ votes.

I finally gave up because of the weird ratings. Thanks for your help though.

If you want to only include movies with a certain number of votes, you should use the vote_count.gte filter.

@travisbell said:

If you want to only include movies with a certain number of votes, you should use the vote_count.gte filter.

Oh, I should have reviewed the parameters more carefully. I added vote_count.gteparam and the data is more accurate now, thanks.

找不到电影或节目?登录并创建它吧。

全站通用

s 聚焦到搜索栏
p 打开个人资料菜单
esc 关闭打开的窗口
? 打开键盘快捷键窗口

在媒体页面

b 返回(或返回上级)
e 进入编辑页面

在电视季页面

(右箭头)下一季
(左箭头)前一季

在电视集页面

(右箭头)下一集
(左箭头)上一集

在所有图像页面

a 打开添加图片窗口

在所有编辑页面

t 打开翻译选择器
ctrl+ s 提交

在讨论页面

n 创建新讨论
w 切换关注状态
p 设为公开 / 私密讨论
c 关闭 / 开放讨论
a 打开活动页
r 回复讨论
l 跳转至最新回复
ctrl+ enter 发送信息
(右箭头)下一页
(左箭头)前一页

设置

想给这个条目评分或将其添加到片单中?

登录

还不是会员?

注册加入社区