Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[rjm]

I am wondering how user fields which store one value for each album work.

What is the definition of an album? Is an album defined as every unique string in the field Album? Or every unique string in the fields Artist+Album? Or something else?

I could do some experiments to deduce this but prefer to know with certainty what is going on before I commit to using relational albums.

Perhaps you could also answer the same question for relational series.

Thanks for your help.

[wig]

I was just going to post something similar. Is there any way to distinguish different albums with the same name?

I am wondering how user fields which store one value for each album work.

What is the definition of an album? Is an album defined as every unique string in the field Album? Or every unique string in the fields Artist+Album? Or something else?

I could do some experiments to deduce this but prefer to know with certainty what is going on before I commit to using relational albums.

Perhaps you could also answer the same question for relational series.

Thanks for your help.

[Matt]

A relational album field looks at 'Album Artist (auto)' and 'Album'.

So, for example, multiple 'Greatest Hits' will work fine as long as you have clean and correct artist values.

[rjm]

Thank you. Relational album fields have the potential to do some very powerful things.

Does a relational series field look at 'Album Artist (auto)' and 'Series'?

[Matt]

Does a relational series field look at 'Album Artist (auto)' and 'Series'?

No.  I wouldn't expect the Artist to be filled for videos, where Series is commonly used.

So I would recommend that you don't name two different series the same name.  Give them a suffix if necessary, like "The Office (British)" and "The Office (American)".

[rjm]

makes sense, thank you