Library Management Challenges (UMS-MLX, .nfo, kodi, confusion)
Posted: Sun Oct 07, 2018 5:16 am
First post here - please be kind.
I have a very large collection (1000's) of video files that I am attempting to serve through UMS. I'm struggling a bit to find the best way to manage and organize all of this and I'm turning to this audience for help and suggestions.
The true problem here is ORGANIZING. It it's native form, UMS does just fine to serve up these videos according to the directory structure respective to each file. What I'm really striving for is more of a dynamic catalog / library where a single file can appear in multiple directories. Functionality would be similar to what XBMC/Kodi offers where a files are grouped by genre, director, release year, imdb rating, etc.
So right off the bat, why not use Kodi? I really like the lightweight nature of UMS and many of the other configurable options it offers. I think Kodi could maybe be incorporated in my solution - via scraping, and/or the use of .NFO files - but I'm not certain how really. There's the Jumpy plugin but I have no idea what benefit that could provide for me, if any.
I initially started out with UMS-MLX. I still think this is likely the best answer for my situation but I'm running into some challenges there as well. Hopefully @taconaut is active and can assist! The Library Management works well file-by-file but seems to be a little buggy for me when attempting to apply tags in BULK to a number of selections. What I'm looking for a more efficient & systematic way to apply tags. If I could achieve this, I could use UMS-MLX to display groupings accordingly.
I have a very large collection (1000's) of video files that I am attempting to serve through UMS. I'm struggling a bit to find the best way to manage and organize all of this and I'm turning to this audience for help and suggestions.
The true problem here is ORGANIZING. It it's native form, UMS does just fine to serve up these videos according to the directory structure respective to each file. What I'm really striving for is more of a dynamic catalog / library where a single file can appear in multiple directories. Functionality would be similar to what XBMC/Kodi offers where a files are grouped by genre, director, release year, imdb rating, etc.
So right off the bat, why not use Kodi? I really like the lightweight nature of UMS and many of the other configurable options it offers. I think Kodi could maybe be incorporated in my solution - via scraping, and/or the use of .NFO files - but I'm not certain how really. There's the Jumpy plugin but I have no idea what benefit that could provide for me, if any.
I initially started out with UMS-MLX. I still think this is likely the best answer for my situation but I'm running into some challenges there as well. Hopefully @taconaut is active and can assist! The Library Management works well file-by-file but seems to be a little buggy for me when attempting to apply tags in BULK to a number of selections. What I'm looking for a more efficient & systematic way to apply tags. If I could achieve this, I could use UMS-MLX to display groupings accordingly.
- I starting poking around here https://github.com/taconaut/ums-mlx/wik ... rs#view-db and tried (unsuccessfully) to query & update the tagging through the DB... truthfully, I couldn't make sense of the structure or even identify where there library was stored.
- mediamelt initiated some really promising discussion here viewtopic.php?t=3355#p21432 that looks like my exact problem. Functionality described here would allow UMS-MLX to use .NFO files to populate metadata. I tried following along and it looks like @taconaut worked towards a KodiNfoImportPlugin plugin here but I'm a bit lost on how to enable (compile?) the plugin for use. The original .JAR file (which is what I think I need) is no longer accessible. The convo suggests that the plugin may have been added for public release but I'm unsure if that happened. Assuming I can get this to work, I'm not certain whether I could use this process to create custom tags or if I'm limited to the Kodi metadata structure.
- lastly, there's a UMS-KODI plugin here which may or may not be broken?