Plugin: Ginjaninja Tools - List Protector - [Auto] Repair your Playlist|Collection memberships

[ginjaninja 665]

Purpose and Function

• Protect playlists and collections from unintended member removal (eg Library Move).
• I didnt like that after a folder move i would have to manually repair my playlists [and collections].
• Provides an auto and manual repair pathway using an evidential reasoning engine for candidate scoring.
• Evidence > Scoring > Belief > Decision (something like that :-))
• Put plainly, list member goes missing, plugin looks for missing member to repair the list.

Getting Started

• Start with auto repair disabled.
• Use checkboxes to protect (Prot) your  playlists, and repair (Repr) your playlists.
• 
• 

Disclaimers

• Vibe coded with Claude, backup database before 1st use until tested. Note this is being released in a less than perfect state, the intention is to gather feedback from users on wether the observations and weighting are establishing correctly/incorrectly scored candidates and in which circumstances.

Download

https://github.com/ginjaninja1/ListProtection

0.0.0.8 ListProtection.dll (unprotect and reprotect protected playlists after updating)

0.0.0.6ListProtection.dll (unprotect and reprotect protected playlists after updating)

0.0.0.4ListProtection.dll

0.0.0.2 ListProtection.dll

Changes

0.0.0.8

• Fixed bug whereby an identical emby id couldnt be a candidate for missing member, when id in the ground truth database (but not in the list)
• Fixed bug whereby new list members were not recorded with the same detail in the database (as originally protected mplaylist members)

 

0.0.0.6

• Bad bug fix, Emby changes ListItemEntryIds for every member when 1 member is added to the playlist. Plugin now handles.

0.0.0.4

• Moved plugin storage to \data\Listprotection (its nicer there)
• Improved realtime event monitoring, fiting emby events for playlists and collections more closely especially itemmoved.
• Added "rudimentary" (needs testing) support for collections, added general support for more baseitem types, more closely indexing emby's natural media item properties.
• Improved status, only shows candidate numbers in status summary if greater than user specifed confidence threshold.
• added filter to list management for users with 10s of Playlists|Collections.

 Known Issues

• Non audio media items mostly untested, supported via ilspy of dlls alone.
• Issues and suggestions welcome.

Roadmap

• Improve candidate generation for non audio list items.
• Make logging and Event History better.
• Keep an eye on performance, in case sqlite is neccesary (currently json)

Feedback Request

• Feedback on scoring, when its wrong or needs a tweak. Primarily thisis about ideas for identifying [supporting] signals of what is a good candidate.

Other Info

• Plugin stores data in \data\ListProtection (good to know if you want to reset/uninstall)

Edited October 27 by ginjaninja

[ginjaninja 665]

0.0.0.4 uploaded in 1st post

• Moved plugin storage to \data\Listprotection (its nicer there)
• Improved realtime event monitoring, fiting emby events for playlists and collections more closely especially itemmoved.
• Added "rudimentary" (needs testing) support for collections, added general support for more baseitem types, more closely indexing emby's natural media item properties.
• Improved status, only shows candidate numbers in status summary if greater than user specifed confidence threshold.
• added filter to list management for users with 10s of Playlists|Collections.

[ginjaninja 665]

0.0.0.6

• Bad bug fix, Emby changes ListItemEntryIds for every member when 1 member is added to the playlist. Plugin now handles.

[IAmHugh 99]

The Github link is dead.

[ginjaninja 665]

2 hours ago, IAmHugh said:

The Github link is dead.

thanks corrected, https://github.com/ginjaninja1/ListProtection

[ginjaninja 665]

0.0.0.8

• Fixed bug whereby an identical emby id couldnt be a candidate for missing member, when id in the ground truth database (but not in the list)
• Fixed bug whereby new list members were not recorded with the same detail in the database (as originally protected mplaylist members)

Full disclosure, i had to use the plugin because my 1000 member playlist had got wiped of its members. No idea what caused it, but one possibility is a bug in the plugin, cant be ruled out... That said if it wasnt my bug, then the plugin worked well to repair the members so glass half full.