Compatibility with additional/custom tags on Smart Views

[ssechaud]

I really like the idea of letting the user specify which tags the database should index. This would let people who want to, index the tags they want with the accompanied performance hit it would incur while not forcing everyone to receive it.

[Der_Rio]

I have put some thought into the new ml_ll plug-in with how we might be able to define & use custom tags but it's then how to store those values that's the problem

As for the DB have a look at the Entity-Attribute-Value model.
In detail: https://en.wikipedia.org/wiki/Entity%E2%80%93attribute%E2%80%93value_model

As graph: https://www.researchgate.net/figure/The-Main-Concept-of-the-Entity-Attribute-Value-Model-The-entity-attribute-value-serves_fig2_257884193

[dro]

The storage side issue is more down to how the nde db works as you need to define the column first before you can use it & also the type (which I assume the likes of sqlite also require - I can't remember how it works off hand).

As I had initially thought about allocating a few empty columns and then via preferences they're stored / accessed as needed from those columns against the user config. Or as I think about it now I could just use a fixed naming for the extra columns so it can be increased dynamically which would also work (which a rebuild of the database would help realign the data / remove the dead space).

Though I think there's scope that some values would always need to be dynamically generated vs being generated on import / update so maybe I'm overthinking it vs what's needed 😉
With regards to the prior post, maybe a full set of options on what tags are read / stored in addition to custom ones would be the best solution. That way it can also help determine the columns able to be shown in the views vs the expected defaults.

Iit might need a bit of thinking about how to handle the filter panes as some would need certain values to be present but I need to make them more flexible anyway vs trying to mimick the existing ml_local selection in the current starting point of the ml_ll implementation.
This has given me a number of thoughts on things to try out so thank you both of you 👍

-dro

[araxhiel]

Hi all,

First and foremost, I would to to apologize for this "act of necromancy" (LOL - too much D&D lately), but haven't seen any related/duplicate topic more recent on this.

Now, I know that since when this was initially discussed a lot of thing have happened, and certainly I am aware that other features are top priority, nonetheless I wanted to touch base on this just in case any additional feedback/update can be shared.

Are there any plans, no matter how low priority they could be, to add support for additional tags (ID3, Vorbis Comments) on Smart Views?

Thank in advance, and once again, apologies for reviving this very old thread.

Regards.