Rick take care. We realize you use PVD a specific way, however yours is not the only way.
Please do stay on topic. This is uncalled for and inappropriate in a civil discussion about how a software application should work. It's a simple fact PVD is designed as a
movie database. If you want to argue it should be turned into a
DVD database, go ahead. I believe it would be more productive to discuss how it might better handle media-specific information without throwing it's fundamental design premise out the window.
It would be nice to be able to enter the movie series name when it is in a series. Then display movies by name or with movie series grouped. With movies not in a series, sorting by movie name instead would be appropriate...
In other words, you want movie titles and series to be listed together alphabetically. I suppose this might work for those who want to adopt this as their primary "view" of their collection (like those presently inclined to record movies as episodes). It seems rather rigid, however, in comparison to grouping. When I group my movies by series, it's because I want to see them
as series (e.g., in most cases, it's appropriate and informative to sort them by year). I'm generally not interested in movies that are not members of a series at this time. They are, however, still there (in the "undefined" group) should I want to do something like show movies of a particular director. When done, I revert to plain view.
With movies grouping by unit purchased ie box set, similar grouping options would be appropriate except the series the user entered would be say "Matrix 1,2,3 box set".
Since the series name has to be entered by the user, it can be whatever the user wants it to be. I dedicate just one field for "Movie series," and use it for a number of different grouping purposes. Most are for what most would consider to be movie series, but it's also used for other purposes. The existing grouping feature works very well in temporarily providing an alternate view of my collection, but what you're describing sounds too rigid.
Let's not forget this thing is built on a relational database. With its ability to group, sort, filter and search, just about any presentation can be achieved. Maybe some general enhancements can be made, like adding the ability to record information on group nodes. But it shouldn't be necessary to argue for hard-coded changes to accommodate individual user preferences. I think we'd all be better served by new features that help make the full power of the program and the database more accessible and easier to use. By that I mean things like saved grouping, filter and (advanced) search settings—so users can configure the presentation of their collection to their heart's content, and recall any saved configuration instantly.