mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-05-04 18:09:12 +03:00
Support for moving items to allow for automatic organisation of libraries #6934
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @geo-martino on GitHub (Apr 21, 2025).
I've been developing a plugin that automatically organises files on the file system according the recommendations in the documentation. I would ultimately like to release this soon, but I keep running into the same issue with path mapping on items.
I've tried multiple approaches, but every time a file is moved on the file system, Jellyfin considers the item to no longer exist and adds a new item for the file at the new location while deleting the item that referenced the old location. This is a challenge as it means that any attempts to automatically organise a library with Jellyfin or otherwise will cause a user to lose all configuration on the items within it (custom images, ratings, favourites, other metadata changes, etc.).
I have developed some functionality which allows a user to move an item via the API. Ultimately, I would like to have this functionality implemented within the UI too so that a user can move an item in the same way that they may delete the item too. I will link the PR to this issue here.
I can use this functionality in conjunction with my auto-organiser plugin to organise a library and update the reference to the path in Jellyfin's database. This effectively works, but I am still facing the same issue where the item is replaced with a brand new item for the moved file each time.
From looking around at some previous issues, I understand there is an issue in which the item ID is coupled to the path and so any updates to the path generates a new ID for an item, hence Jellyfin assumes the file is deleted and adds a new item with the new ID. I also understand that there migrations to the database in development currently that may address this. Will these changes help support items with updated paths? If help is needed to support, I will happily contribute, though I may need some more context if any one could support.
Thanks and looking forward to contributing!
@jellyfin-bot commented on GitHub (Aug 20, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (Sep 11, 2025):
This issue was closed due to inactivity.