Server - Store Manual Identifications in database

[ginjaninja 573]

To avoid having to re-identify objects more than once after a rebuild, remember manual identifications separately to main database.

 

eg store

 

Object,String from local scan,id on primary provider x, id on provider y etc

Artist,bono,7f347782-eb14-40c3-98e2-17b6e1bfe56c,,

 

during initial ingestion into library check matches against this db first for id.

perhaps store the id in the nfos stored in media library.

 

[Luke 40079]

We already do, although it won't survive a database rebuild. 

[ginjaninja 573]

given the most useful use case for these manual identifications is a complete library rebuild, it would be good to store them separately.

[Luke 40079]

isn't that what local metadata is for?

[ginjaninja 573]

yes metadata  in media folders is perfect for remembering manual identifications for most objects , but not music artists. manual music artist identifications  would need to stored in programdata/metadata? (not all artists manual identifications  could be stored in media folders as not all artists have a folder in library....). if this  is already the case then  great, suggestion closed. btw metadata in media folders is not read 100% eg. after a fresh build music artist images are sourced from providers in preference to local metadata in media folders.

 

edit 

just did manual rebuild to .23 after wiping system folder and library.db

bono (artist previously manually identified) was not identified correctly

Edited August 26, 2018 by ginjaninja