search

nicford / Movilytics

Welcome to our website Movylitics, a Sophisticated GroupLens dataset and tmdb analytics exploration tool.
BSD 3-Clause "New" or "Revised" License
3 stars 3 forks source link

audience/audience.controller.ts #29

Closed kimdanny closed 3 years ago

kimdanny commented 3 years ago

I have created a separate endpoint for audience api for testing which was done in audience.controller.ts. This api endpoint was used in ucl-imdb frontend when retrieving user segmentation result for Charts.

Should I remove audience endpoint and incorporate into movie-report?

nicford commented 3 years ago

You can, but this is not a major issue in terms of design. Another question is whether to keep them as separate endpoints, or to incorporate everything into the /movie-report/mid endpoint.

This could lead to some latency when a user visits the movie report page, because, if we put everything into one request (movie-report), it could take a significantly long time to complete. But it also might not, so we need to test this.

nicford commented 3 years ago

In terms of usability, if someone wants to use our api, having a complete report accessible from our api is very useful, so they done have to worry about query several endpoints to get all the data. On the other hand, some one may not want to use all the available data in the movies report, but rather choose smaller sub-sections of if, like just the audience info. In this case, it would be better to have separate endpoints. So overall, the best thing to do would be both, but since we're running out of time, LET'S GET DOWN TO BUSINESS!!

kimdanny commented 3 years ago

Got down to business