Extended Tags?

Get answers about the current version of MediaMonkey 5

Moderator: Gurus

martialartsguy
Posts: 298
Joined: Mon Apr 03, 2006 9:11 am
Location: Denver, CO

Extended Tags?

Post by martialartsguy »

So what are extended tags? I can't seem to find any documentation on them in the support section of the site.
MM 5.0.0.2338

MM Gold since 2006
Lowlander
Posts: 50796
Joined: Sat Sep 06, 2003 5:53 pm
Location: MediaMonkey 5

Re: Extended Tags?

Post by Lowlander »

https://www.mediamonkey.com/wiki/WebHel ... ustom_Tags

They are tags that are not supported in MediaMonkey itself (ie. not shown in Columns like Custom Tags), but are tags that have a name and a value (unlike Custom Tags which don't have a name in the tags (just in MM itself they can be renamed)).
Barry4679
Posts: 1674
Joined: Fri Sep 11, 2009 8:07 am
Location: Australia
Contact:

Re: Extended Tags?

Post by Barry4679 »

martialartsguy wrote: Thu Jul 22, 2021 6:42 pm So what are extended tags? I can't seem to find any documentation on them in the support section of the site.
I think that Extended Tags are a half done job in MM5 atm. You can make them, but you can't use them in MM5, and can't locate them for auditing. More information here.
Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
rusty
Posts: 7589
Joined: Tue Apr 29, 2003 3:39 am
Location: Montreal, Canada

Re: Extended Tags?

Post by rusty »

I think that rather than 'half done' one could say that it's designed for a more limited usecase (for users that work with specific other apps, and just have a need to see the data from those apps). Some users may have hundreds of different extended tags (depending on what other apps they're using), and adding all of them to the MM DB would be untenable for performance, UI overload, and cross-media-format tag (in)compatibility reasons.

That said, I could envision a feature that allows for the definition of custom fields mapped to tags on a per-media-format basis. But this would be a tremendous undertaking with limited benefits.

-Rusty
Peke
Posts: 14613
Joined: Tue Jun 10, 2003 7:21 pm
Location: Serbia
Contact:

Re: Extended Tags?

Post by Peke »

Hi,
That said, we also opened them up to be accessible in MM5 API https://www.mediamonkey.com/docs/api/cl ... tendedTags and anyone can make own plugin specifically for his needs.

As always we are here to help debugging, testing, consulting, but as Rusty pointed this is rather user specific case which only needed tool (above) to make this happen.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying
Image
Image
How to add SCREENSHOTS to forum
Barry4679
Posts: 1674
Joined: Fri Sep 11, 2009 8:07 am
Location: Australia
Contact:

Re: Extended Tags?

Post by Barry4679 »

rusty wrote: Fri Jul 23, 2021 1:54 pm I think that rather than 'half done' one could say that it's designed for a more limited usecase (for users that work with specific other apps, and just have a need to see the data from those apps). Some users may have hundreds of different extended tags (depending on what other apps they're using), and adding all of them to the MM DB would be untenable for performance, UI overload, and cross-media-format tag (in)compatibility reasons.

That said, I could envision a feature that allows for the definition of custom fields mapped to tags on a per-media-format basis. But this would be a tremendous undertaking with limited benefits.
Point taken re the design intent.
Also accept that the feature would have limited benefits, but is hard to see that if would be a tremendous undertaking.

All it would take is:
  • for those Extended tags where the user had registered a link to one of the Customx database columns
    • the CustomX column is marked as read-only
    • when MM5 updates the track's Extended tag value, it also pushes that value to the corresponding Customx cell in the database
    • and when MM5 did an add/rescan of the tracks, it updated the Customx column
    • and when MM5 did an Update Tags (Ctrl+S), it pushes CustomX values down to the tracks
Everything else comes for free, because the linked Customx column can be treated like just any other data carrying column, with existing logic. The Customx column could continue to be stored in the tracks, which would be duplication as pointed out by LowLander, but that is not a material impact.

The difficult thing could be the read-only bit. ... That would be a nice to have feature, but is not essential. People can understand limitations like that. Right now I can rename a track using File Explorer, or tag it outside of MediaMonkey. Those actions cause the MM5 database to get out of sync. People understand that, and deal with it. ... IMO that complication|hassle would be preferable to having some data element that was important enough fir me to maintain in MM, but which remained all but invisible within MM.

I don't have any personal Use Case for this feature, but it would likely be of significant benefit for those who do. Presumably there is a body of such people, otherwise you would have implemented the feature in the 1st place.
Want a dark skin for MM5? This is the one that works best for me .. elegant, compact & clear.
Post Reply