You must not be very imaginative, if you cannot think of a reason. You seriously want people to ceate collections for every movie series? That might well be hundreds of collections, each with just a few movies. That wouldn't help navigation or improve the 10-ft view of your library in any way. All it'd do is mess up the collections view and create lots of manual labor for all users wanting this.
XBMC has a plug-in that automates this grouping, so if you have movies that the scraper determines is in a series (e.g. Iron Man), they get grouped together and only one image is shown when browsing movies. It really helps clean things up, and above all, it's an automatic process. I don't care at all what you can do by manually editing things, I just don't have time or desire to do so.
You completely misunderstood my post. If you use the TMDB agent, a collection is already created for each movie series. The option has been there for some time and uses the same data as XBMC because the source in TMDB is the same. Some of those collections are useless because the data in TMDB is user-generated. Not the issue of this thread, even though the name would imply it.
The core of the discussion is whether, in the All Movies view, the movies in a collection should be grouped under one icon by default. This would mean only one icon for Iron Man movies instead of 3. I support that as an option but not as the default, largely because the only source of the data happens to be pretty bad a good deal of the time. Since we don't have flattening for TV shows (meaning when there's only one season of a show on a server, clicking on a show should not show you Season 1 but the actual episodes) I would not assume it would come into play here. That means the hundreds of collections auto-created under the current agent might result in most collections consisting of one movie. This means that for all of those, the list is not shortened and we've introduced an extra level to click through for watching a single movie.
Development requests are best broken into separate issues:
- Should the scraper add collection info (though several are discussing this, it's already there in the TMDB agent and has been for a while)?
- Should there be a view that groups collections under a single icon? This does not exist in Plex and would likely mean that any collection of any size would result in an icon in the list that had to be clicked through to get a list (of even one) movies.
- Should this view be the default (for All Movies)?
The first question keeps being asked in spite of its existence. The second is valid and I agree that there might be some people that would prefer it. I think it would be of limited utility because of bad data in TMDB on series. Specifically, there are many "series" in TMDB that are built to include extras and non-theatrical items that would not generally be considered movies in Plex. This means that a lot of collections of only 1 movie would be created, potentially making the navigation more cumbersome instead of less.
So you can be happy that collections data is automated, or you can do it yourself. But you can't complain about it not being there or say that it's too hard if you choose to maintain it yourself.
Let me give an example. Megamind is in TMDB and has a collection listed. The collection consists of one movie (Megamind) and one extra from the DVD/Blu-Ray release. This would, if the navigation is consistent from all previous iterations of Plex, result in a Megamind Collection icon in the movies list. To get to watch Megamind, you would have to navigate to the collection, click on it, select the (likely only) one movie that you had and then click on it to play it in some way. You could argue that collections of only one movie on the server should be flattened, but that has not happened with TV shows, so it is not terribly likely to be done here.
If that view weren't the default one, I have no problem whatsoever in it being developed. My only issue is with the third question above. I don't agree that grouping movies into collections should be the default view. This is largely because the automated collections data is so bad. Since movies can be in multiple collections for valid reasons, it also introduces the possibility of considerably longer queries to build the list. Again, acceptable if you choose that view explicitly but not as a default.