INTERACT FORUM
Windows => JRiver Media Center 33 for Windows => Topic started by: PreLives on January 13, 2025, 11:05:58 am
-
I recently upgraded from JRiver 29 to V33, and I've noticed a difference in how the import configuration works.
In V29, when assigning a value to a list field like [Keywords], the value would be added if the field was blank or appended if there was an existing value. However, in V33, the value is added when the field is blank but overwrites any existing value instead of appending to it. In V29, I used the checkbox option "Skip for files that already have a value in this field" to control assigning or overwriting a value.
Was this change intentional, or is it a bug? Personally, I preferred how this part of the import process worked in V29.
Below is an example of how my configuration functions. Essentially, it checks the [Name] field to see if a specific keyword exists. If the keyword is found, it’s assigned to the [Keywords] field. Then, the first keyword is removed from the [Name] field to allow the process to search for Keyword2, and so on.
Configuration Example:
Field: Keywords
Value: =IfCase([Name],8,Keyword1,Keyword1,Keyword2,Keyword2,Keyword3,Keyword3)
Field: Name
Value: =Replace([Name],ListItem([Keywords], 0),,1)
Field: Keywords
Value: =IfCase([Name],8,Keyword1,Keyword1,Keyword2,Keyword2,Keyword3,Keyword3)
Field: Name
Value: =Replace([Name],ListItem([Keywords], 1),,1)
Field: Keywords
Value: =IfCase([Name],8,Keyword1,Keyword1,Keyword2,Keyword2,Keyword3,Keyword3)
Field: Name
Value: =Replace([Name],ListItem([Keywords], 2),,1)
-
It was an intentional change.
MC 30.0.42:
Changed: Tag on import rules now replace list type fields instead of appending to them.
-
Could you share the rationale behind this decision?
List fields are inherently designed for multiple values, and the previous behavior in V29 seemed more intuitive. Users could easily clear or replace values with the Replace() function if needed, while the new behavior in V33 requires using the more complex ListBuild() function to append values.
-
Bump
-
Thank you for clarifying that the change was intentional. I guess I’m less concerned with the rationale at this point and wondering more if it would be possible to restore the previous functionality, either as an option or in some other way. The V29 behavior seemed more aligned with how list fields are generally expected to work, and it simplified workflows significantly.
Would it be feasible to bring back the old functionality, perhaps as an alternative mode or a setting for those who preferred the prior behavior?
-
Would it work to just include the field again when you build the list?
-
Yes, using the ListCombine() function works; however, it feels unnecessarily complex and less intuitive for the average user. I’m unclear on the rationale behind this change, and I would prefer if the previous functionality could be restored.
If reverting is not an option, please let me know, and I will adjust my import configuration accordingly, as I use this tagging method for multiple fields.
-
I'm keeping a nervous eye on this...
I rely heavily on some auto import rules that deal with lists, mostly keywords for my incoming photos. I don't mind changes, so long as they don't break these routines that have worked with supreme confidence for many years 😊
-
Maybe appending could be an option on the rule?
-
Would that rule fall under the Tasks section within Media Import, where a user may 'Select any additional tasks that Auto-import should perform.'?
If so, that works for me.
-
It's where you fill in the tagging rule. You can now check a box to append. It'll be in the next public build. Thanks for the help.
-
👍