More > Media Center 17

Series & Movies

<< < (2/2)

rick.ca:

--- Quote ---The focus of my library is non-fiction so having a common structure across all media types is very beneficial. I can see that if your library focus is pop culture then it does not matter.
--- End quote ---

You said...


--- Quote from: rjm on October 14, 2011, 10:35:52 pm ---I'd like us to standardize on using Artist, Album, Name for all media types...
--- End quote ---

...and I attempted to explain why that would not be a good idea.

I have no objection to removing all restrictions on field use that's not absolutely necessary for database integrity. We should be able to select or create the fields we want to use—whether to use the same set of fields for different data types, or to deliberately use separate fields. In other words, you're currently suffering from the imposition of unnecessary "standards." Adding more such standardization is not the answer.

bytestar:
Full agree  :)


--- Quote from: rjm on October 14, 2011, 10:35:52 pm ---I'd like us to standardize on using Artist, Album, Name for all media types as follows:

Type: Artist, Album, Name

Movie: Series, Title, Part # or Extra
TV: Series, Season, Episode
Documentary: Producer, Title, Episode
Music: Artist, Album, Track
Audiobook: Author, Title, Chapter
eBook: Author, Title, null
Photo: Photographer, Topic, Image Name

This permits the construction of views that work for multiple media types, and eliminates media specific fields like Series and Title.

--- End quote ---

Matt:
I don't think we're going to move in this direction.

We actually tried pushing audio-named fields on all media types some years ago, and I think it was a mistake.

It's not intuitive for a user to think "Artist" when describing a television series, for example.

The database is designed so that it's quite efficient to have discrete fields, even if they only apply to certain media types.

rjm:
I understand. Perhaps something could be done about one issue that has bugged me for years.

The field Name has some special properties. For example, default views assume that the title is in Name for Video and Documents. In addition, Name is populated with filename on import. I use Album for title and I'm forever fighting the default behavior.

It would be great if we could configure the default field for title.

Navigation

[0] Message Index

[*] Previous page