Jump to content

Plugin: Manage Coming Soon


Recommended Posts

ginjaninja
Posted (edited)

image.png.3cd05cf45d592f92e49d109154f0f87c.png

Purpose and Function

  • [Add Movie] To speed up the creation of Coming soon movie placeholders (With Coming Soon Tag), so users can see what is coming soon.
  • [Make Live] To speed up moving placeholder to live state (Library Change / Coming Soon Tag Removal / Maintain Metadata and ID across move)
  • Folder names are normalised to TMDB matches (To help Emby match them correctly)
  • Simple placeholder video included, option to choose your own.
  • Very niche, might just be a me thing.
  • Learning new UI model

Getting Started

  • Register for TMDB API Key and add to config
  • Create Emby API Key and add to config (Plugin uses rest /refresh endpoint to direct immediate refreshes)
  • Specify your library for coming soon placeholders and library for when gone live.
     

Disclaimers

Vibe coded with Claude, backup database before 1st use until tested, use dummy libraries/paths during testing, only limited short term testing on beta server so far. This plugin has file system delete commands targeted at coming soon movies.

Download

0.0.0.2Emby.ManageComingSoon.dll

 

Changes

 

 Known Issues


Roadmap

Write TMDB match to NFO to force correct detection

Edited by ginjaninja
sh0rty
Posted

Thanks for your plugin. It would be really useful imo, when the plugin could be connected to Radarr/Sonarr and setup the monitored and not available items as coming soon items in Emby.

ginjaninja
Posted
57 minutes ago, sh0rty said:

Thanks for your plugin. It would be really useful imo, when the plugin could be connected to Radarr/Sonarr and setup the monitored and not available items as coming soon items in Emby.

Thanks you are very welcome. Yes i had something around this in my mind but never even half formulated (I am not familiar with the tools in this regard). Now ive got an example of how to reach out to Emby and TMDB apis, maybe the next learning point is how to provide a (webhooks?) interface which Radarr/Sonarr could consume and in return consume their interface. I think the job of the plugin would need to be lightweight without too much functionality doing 'just enough' to link something to something else; where these somethings are doing the real work (not least because im learning). If you were interested to formulate an idea id be interested to (learn to) implement it.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...