INTERACT FORUM

Please login or register.

Login with username, password and session length
Advanced search  
Pages: [1]   Go Down

Author Topic: Trying to understand relational fields.  (Read 2652 times)

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Trying to understand relational fields.
« on: February 05, 2013, 04:36:23 pm »

In classical one often have the same compositions by different performers.
As they come from different CDs the compositions are spelled different.
To enforce a uniform tagging I set my tags Opus, Work, and Work_Year to relational to Series.

For Series I generate a key Composer_Opus

I have Opus and Work populated
I generate the Series using an expression:
=ListItem([composer],0,/,)If(IsEmpty([Opus]),_[Work],_[Opus])

Most of the time this works
But sometimes Opus and Work are cleared.
What could be the cause?

Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: Trying to understand relational fields.
« Reply #1 on: February 05, 2013, 05:11:37 pm »

So Opus and Work are Series relational, but Series relies on Opus and Work?  That seems like a loop.
Logged
The opinions I express represent my own folly.

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Re: Trying to understand relational fields.
« Reply #2 on: February 05, 2013, 05:26:39 pm »

I believe this is called recursion.

But if I use Catalog (not relational, single value only) I get exactly the same results

Logged

MrC

  • Citizen of the Universe
  • *****
  • Posts: 10462
  • Your life is short. Give me your money.
Re: Trying to understand relational fields.
« Reply #3 on: February 05, 2013, 05:33:09 pm »

Dunno.  I was just speculating about possible areas of investigation.

Maybe it is a bug.  Maybe its the same issue vagskal has seen (don't know if it is resolved).
Logged
The opinions I express represent my own folly.

Matt

  • Administrator
  • Citizen of the Universe
  • *****
  • Posts: 42385
  • Shoes gone again!
Re: Trying to understand relational fields.
« Reply #4 on: February 05, 2013, 08:42:19 pm »

If files join a relationship that already has files, they must either:
1) Force their value to the other files in the relationship
or
2) Inherit their values from the other files in the relationship

I believe whether #1 or #2 happens depends on which set of files is larger.  But in any case, you could get results that vary a little depending on the other files already in the relationship.

Could that explain it?
Logged
Matt Ashland, JRiver Media Center

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Re: Trying to understand relational fields.
« Reply #5 on: February 06, 2013, 04:49:25 am »

Thanks for the explanation.
In the example above Op.53 is already in the lib so either the value of the new entry or the existing value should be used but it is cleared.
Op.11 is completely new in the collection but it is cleared.

I don’t see any distinct pattern.
It happens both to existing and new relations and most of the time it works but not all of the time.
As I lost a lot of information because of this I have all relational tags duplicated in non-relational ones.
Logged

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Re: Trying to understand relational fields.
« Reply #6 on: February 06, 2013, 05:11:52 am »

I did the following
- Cloned the main library
-Cleared it
-Populated it with the 7 Scriabin CDs
- applied the formula

There is a very distinct pattern, each CD has its first tracks with the same key in Series cleared.
All other are fine

Logged

Vincent Kars

  • Citizen of the Universe
  • *****
  • Posts: 1154
Re: Trying to understand relational fields.
« Reply #7 on: February 18, 2013, 04:59:38 pm »

I would highly appreciate if anybody at JRiver would look into this problem because each time I populate the Series I lose the tags of the first tracks of the CD

Thanks

Vincent
Logged
Pages: [1]   Go Up