2009-08-09, 00:32
joelmeans Wrote:Hi All,
I just wanted to drop a note in this thread to mention that I have submitted a patch which adds a "sorttitle" field to the movie info in the database. If this field exists for a movie, it is sorted based on that. There is one patch to add the basic functionality (requiring a <sorttitle></sorttitle> field to be added to your .nfo file) and another which adds a context menu button to edit the Sort Title in the GUI. You can get the patch from trac (ticket #7008).
Also, I am starting to work on adding the ability to group by sets. Currently, I have added a table to the database containing a list of sets and another table linking movies to sets, including the order of the movie within the set. This allows you to put a section in your .nfo that looks like this:
<set>
<name>Star Wars</name>
<order>1</order>
</set>
for Star Wars Episode I. I can read to and write from the .nfo file for this. Now I have to figure out what to do with this info with respect to the Library. It would be easy enough to add a "Sets" grouping similar to "Genre", "Actor", "Director", "Year", etc., but I think it would be nice to have an entry for each set in the "Title" listing which would take you to a listing of the movies within that set when clicked. That will require a lot more work and a lot more understanding of the way the views are put together.
Anyway, I just wanted folks to know that I am working on this and to see if people have other ideas of how it should work.
Thanks,
Joel
That's fantastic! Would you consider making the sets layout compatible with YAMJ? More info: http://code.google.com/p/moviejukebox/wiki/BoxedSets
It's very similar to what you've proposed, except that it condenses the individual sets into one line (element/optional attribute):
Code:
<set order="1">Some Set Name</set>
Also, a movie can be part of multiple sets:
Code:
<sets>
<set>Alien Collection</set>
<set>Predator Collection</set>
<set order="4">Another Set</set>
</sets>
While I admit, I'm requesting this for selfish reasons (we've already implemented a sets manager in Ember utilizing the YAMJ format), I also think it would benefit those people who use both programs (ie. - they won't have to have two similar, but incompatible, forms of set markers in their nfos and won't have to create the same sets twice). Just a suggestion....