Agreed.

This is probably a completely impractical suggestion because it would require a complete rewrite of the database, but I think in the long run, it would make the database smaller and maintenance of the database way more efficient and easier.

DVD profile information (UPC, edition, media companies, format, cover art, audio tracks, subtitles, HDR, 3D, region, SRP, case type, anything that could be unique to a particular SKU) should be separate from movie information (title, original title, cast, crew, production year, studio, running time, rating, rating information).

Every DVD, Blu-ray, and 4K release would reference the same data for the movie itself, so that if the cast/crew were correct for the DVD version of Black Hawk Down, it would automatically be correct for the Blu-ray and 4K versions, too.

Admittedly, this might make things like TV shows tricky, because every episode would need a separate entry, but it would, again, make the database more efficient. As it stands now, the database design is pretty inefficient and the database contains way too much redundant information.

If you check off a child tag in the "All Tags" view, the program automatically selects all of the parent tags, all the way up the tree. If you check the same child tag in the "Favorite Tags" view, however, it doesn't affect the parent tags at all.

This should be consistent across both views. My tagging system assumes that parent tags will be automatically checked, so the Favorites view isn't that useful to me, as is.