Tags that should be ingnored in ListenBrainz

ListenBrainz
, , ,
1

I’m not sure if I need to put this theme in MusicBrainz or ListenBrainz category.

Tags are common and used both in Musicbrainz and ListenBrainz. Usually it works well for things such as genres or associations (game name for its soundtrack, characters and similar non standardized but useful tags). But sometimes there are tags, that are too specific and used by someone for private collection or for narrow things that won’t be useful for someone else. Particularly, I’m one of these persons, who uses tags of this kind.

изображение
изображение994×567 103 KB

Here (MB), for instance, I have 3 tags, that won’t be useful at all in ListenBrainz and will be annoying for other users of LB.

  • yt title as alias - my main music streaming platform is YT and usually recording name are not formatted in any proper way at all; there is no any standard there; still I need to format them according to MB guidelines, so I delete info as ‘artist name’, ‘cover in x language’, ‘guitar cover’ etc. But this formatting makes it hard to find this release for usual listeners, so I always add original name without change in formatting as alias. I use this tag to mark releases, where I did it.
  • role:тюнотайм - I use role:[role_name] syntax for collecting roles from edited by me releases, that are not covered by standard MB relationships yet or I didn’t know how to add them.
  • patrons in annotation - started to use for managing this my practice after this discussion.

All these tags have no any sense outside MusicBrainz or my logic, useless for other LB users and only wastes free space for more relevant tags, so it can be helpful to have some possibility to hide these undesired tags. I don’t really know, how it can be implemented exactly, but here are some ideas that I had in my head (without deep analysis of them)

  • separate level/system for these tags; IMO is too hard, because it makes tag system over complicated; and it is wasteful to create a new system of tags every time, when there is something non standard.
  • using some prefix for this goal as mb: - MusicBrainz, us: - user specific or ht - hide tag, in the beginning of some tag:
    • examples: mb: patrons in annotation, mb: role:decorations
    • can be easily ingored because of certain structure
    • optional and can be used for any other tag, that I think will be useless for other people;
    • if someone decides still to have them, it should be possible to implement optional setting “Hide tags starting with ‘x’ prefix” with ‘yes/no’ states in ListenBrainz.
5 Likes
2

I use a bunch of tags that probably don’t make sense to show by default. Some like dance/by-name/polska/rørospols or media/phonograph/by-speed/33rpm might be useful to others, but are formatted in a bit of an odd way to match the rest of my tags. Others like the added/ ones are useless to anyone other than me. And then there are the private/ ones that are intentionally meaningless without the software I use them with. Not sure what a good solution would be, but I’d probably use it if there were one.

3 Likes
3

A simple solution would be to list the genre tags at the front. Similarly to how genre tags and other tags are separated on MB pages.

4 Likes
4

It is not really full solution, because except for genres there are plenty other tags, that still can be useful for others as ‘german cover’, ‘bpm:90’, ‘[game name]’, other associations etc. I want to hide some too specific tags, that are almost useless for other users and to keep other tags public but without this user specific garbage to make taglist list clearer and more useful

Still, it probably looks as a good idea to list genres separately

2 Likes