Bug 16488 - Update NAME/TITLE columns when new value is encountered
: Update NAME/TITLE columns when new value is encountered
Status: CLOSED DUPLICATE of bug 10324
Product: Logitech Media Server
Classification: Unclassified
Component: Scanner
: 7.6.0
: All All
: P2 normal with 3 votes (vote)
: 7.6.0
Assigned To: Andy Grundman
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-27 19:09 UTC by Jim McAtee
Modified: 2011-05-12 14:24 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2010-08-27 19:09:12 UTC
During a library scan, database lookups are done on the NAMESEARCH/TITLESEARCH columns in the contributors, albums, tracks and genres tables.  The NAME/TITLE columns are populated with the first value encountered and never updated thereafter.

The SEARCH columns have punctuation removed, so that it's possible that multiple original strings may match them when doing a lookup.  The net result is that strings which differ only in punctuation may not be 'fixed' by running a new & changed scan.  Example:

AC-DC
AC/DC

If a user found the first one being displayed by SbS for this artist, but wanted the second, updating all file tagging and running a new & changed scan would would not update the contributor's NAME.

The solution would be to return the NAME/TITLE columns when doing scanner lookups in these tables and compare them to the original string.  If they differ then update the NAME/TITLE column.
Comment 1 Jim McAtee 2010-08-28 02:00:11 UTC
Also see bug 10324.  That bug deals with what to do when you have NAMESERCH matches where the original strings may or may not contain accented characters.  I think the solution is the same - in order to have a new & changed scan update the database you have to use the last one found.

It's interesting, now that I think about it...  It may be impossible to ensure that only running new & changed scans will exactly duplicate the database produced by running a full scan.  The reason is that lookups will match for different strings, but only one of those strings can be stored in the NAME/TITLE column.  So the final database depends on the order that the files are scanned.
Comment 2 Andy Grundman 2010-08-28 04:56:14 UTC
I recall we decided somewhere that we should always treat artists with different names, even differing only in accents, etc, as different artists.  Mostly so you can easily detect problems with your tags, and maybe they are in fact different artists in some cases.
Comment 3 Andy Grundman 2010-08-28 04:58:10 UTC
Yeah this is really a dupe of 10324.
Comment 4 Andy Grundman 2010-08-28 04:58:23 UTC

*** This bug has been marked as a duplicate of bug 10324 ***
Comment 5 Bradley D. Wall 2011-05-12 14:24:18 UTC
closing due to duplicate.