tom80H
December 6, 2021, 7:44pm
2
Refreshing the library metadata should sort this for good. Alternatively you can wait for approx. 1 week for the scheduled maintenance tasks to iron it out.
This is an expected side-effect of fixing a very old bug where we could not discern people with the same name and would always overwrite their data with the latest data from the most recently refreshed item.
We now store people uniquely when adding new items or refreshing old items, but this won’t fix existing items until they are refreshed. We have also added checks that run at PMS startup and when running a database optimize that will correct duplicate items, so these things should self-corre…