#metabrainz

Oh yea I'll check for that as well

Thanks for reminding

Though it should be responsive by default but I'll still check for it

Hi lucifer monkey

I have updated the PR with the screenshots on desktop and mobile view as well

I had one more query

I created the branch `importer-UI` from the branch `main-importer` but I had created the PR #3317 that merges to main instead of `main-importer`

Now when I go to edit option in the PR, I don't see the option to set `main-importer` as the branch it merges to from the list of branches

suvid: yes you can't do that because `main-importer` is a branch on your github fork not the metabrainz repo.

lucifer[m]: oh

sol first `main-importer` will have to be merged to main and then only `importer-UI` would be merged right?

yes.

Hey lucifer is the entire DB present on wolf?

MB or LB?

MB

yup it us

* yup it is

* ````>>>... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* ```>>> spark.sql("select count(*) from listens l, recording_artist ra where l.recording_mbid = ra.recording_mbid").show()... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

* ```... (full message at <https://matrix.chatbrainz.org/_matrix/media/v3/...>)

Shouldn't the 2 be equal?

no, because in this query filter for listens which have a matching recording mbid in recording artist table. that filters out listens which don't have a recording mbid.

yeah but shouldn't all the listens have a mbid?

i mean if not all atleast like the most of it

right now roughly 10% of the listens have a matching mbid

no, all listens have a msid but not all listens have a mbid.

ah that is probably because your spark wolf setup only has the sample dumps.

again, MB db on wolf is not the same as your spark setup on wolf.

MB db has the full dataset, your spark setup only sample.

so the discrepancy is fine right

yes

is there a possibility to get the entire db or like some more content cause the results are too small to test and verify

hey monkey lucifer any update?

Not yet.

lucifer: np

i was using wrong endpoint for refreshing access token

`Refresh your access token by sending a refresh request to /api/v1/oauth/token` i'll try to debug i'll let u know if its resolved!

<rayyan_seliya123> "hey lucifer just wanted to..." <- Hey lucifer: if u by mistake missed my chat 🙂

[@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) take a look at how Spotify search is implemented in BrainzPlayer and then try to implement search using this endpoint the same way.

the Spotify player in BrainzPlayer is using Spotify api search directly but the process should overall be similar.

<holycow23[m]> "is there a possibility to get..." <- I can try importing the entire metadata in your wolf cluster, sure.

lucifer[m]: lucifer: sure I will look onto Spotify how it is implemented and will update you after that I was thinking to move all my commits or backend file changes to this new pr and close the previous one is it good to you ??

[@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) you can have the api and the frontend change in 1 PR. And leave the indexer changes in the old PR.

lucifer[m]: Okk sure !! But there is one change in my `handler.py` file which I wanted to do but coz of the issues I faced I am unable to do so ! For that change I would have to push the entire handler.py. File in this pr 🥲 or we can edit it later would be fine ?

<lucifer[m]> "I can try importing the entire..." <- I will test it out for a little more if needed will let you know

Hey ansh and monkey , could you help me with the stats section related to 'Top Listeners' from my [proposal](https://community.metabrainz.org/t/gsoc-2025-development-of-advanced-user-statistics-visualizations/750040)? Should I go ahead with the implementation method I described there, or would you suggest a different approach?

[@rayyan_seliya123:matrix.org](https://matrix.to/#/@rayyan_seliya123:matrix.org) check out your old branch and update the handler file in that PR. Then rebase your current branch on the old branch and it should work fine.

lucifer[m]: Sure I will try this !

lucifer: what's the earliest year of a listen that we have?

[@holycow23:matrix.org](https://matrix.to/#/@holycow23:matrix.org) will have to check but 2002 or 2005.