#metabrainz

zas[m]: looking into it

Jade: Some minor changes, but I am happy with these now: https://www.figma.com/design/L0qNv3z5vSkNDoiX7B...

Have you been having trouble opening Figma? There are some comments in there as well. I’m happy to export the drafts for you in some other way.

I have not gone through all the different emails and made mockups, just those first three - I figure my role is just to supply the design, not edit the content. That said, if you have time I think it would be very cool to ask the community for feedback, on the forums, and see if there are any easy changes to be made. Or see if you can find your own improvements to make, and check them with the community.

In any case, feel free to tag me back in if there is anything I can be helpful with, otherwise I will leave you to it :)

<02UltimateRiff> question about the ListenBrainz API... when track_metadata.additional_info.tags is submitted with a listen, does that also submit folksonomy tags to MusicBrainz? from https://listenbrainz.readthedocs.io/en/latest/u...

<02UltimateRiff> looking at adding a ticket to some of the scrobblers/listens submitters I use if it does~

<aerozol[m]> "Jade: Some minor changes, but..." <- Great! Thank you :)

<aerozol[m]> "Have you been having trouble..." <- Ah, I didn't notice the comments. Figma doesn't work too well on my phone, but it works OK on my desktop, so it's fine

<aerozol[m]> "I have not gone through all..." <- OK! That's something for me to do later, then

yvanzo (IRC): someone was asking about getting part of work rels from search results

I was thinking it wouldn't work in the sense that we don't do rels in search... but we actually do for work, with both composer/lyricist and performance of recording rels (https://beta.musicbrainz.org/ws/2/work/?query=w...) but I cannot find where we actually define those

Can you give me a hint? :)

I think returning parts for works would make sense, to avoid people having to query (at least) twice to find the movements for a work for example

Maybe the same applies to events where we have held at and performers but it'd make sense to also have the parts for festivals and whatnot

Added SEARCH-723 for that

SEARCH-723: Show work (and event?) parts in search results https://tickets.metabrainz.org/browse/SEARCH-723

reosarevok: That would be a search indexer issue.

Ah, it'd just be a line like the current

`artist_links = relationship("LinkArtistWork", viewonly=True)`

in https://github.com/metabrainz/sir/blob/master/s... ?

I didn't realize we were not restricting stuff further, just doing all artist-work rels for example

Any big reasons not to do LinkEventEvent and LinkWorkWork?

aerozol, atj: I published the blog post about Solr 9 and forwarded to bsky & mastodon.

reosarevok: The reason to not make all the details available from search was to keep it manageable.

Yeah I know

But it feels Event-Event at least should be almost only part ofs, so not a lot of growth in the index and a fair amount of usefulness

I'd say Work-Work is also mostly just small and useful although of course some works and events have a lot of parts, but since there's nothing to even indicate which ones do otherwise, it seems pretty hard to use the API for that otherwise

Would need to always browse rather than search or do a ton of tentative lookups

I completely agree that all the details are relevant, and some more than others.

I was quickly checking just updates but I have to go now. 👋

Sure :) I might look into a small PR next week and we could see how much bigger it makes indexes and whether it seems problematic

Thanks!

reosarevok: do you remember if there was another ticket related to issues with the duplicate checker similar to MBS-13576? I kinda recall that there was

MBS-13576: Not consistently warned when adding artist with duplicate name https://tickets.metabrainz.org/browse/MBS-13576

maybe it was MBS-13389

MBS-13389: Artist Creation https://tickets.metabrainz.org/browse/MBS-13389

I think there's even a few like that with ises on creation

UltimateRiff: no that doesn't submit any data to MusicBrainz.

mayhem: fyi spark cluster was having some issues, i think it had something to do with rabbitmq not sure. everything looks okay for now and stats should become up to date tomorrow.

mayhem: how to respond?