#metabrainz

Hi, can someone please link me to any piece of documentation on MusicBrainz that explains canonical MBIDs?

^ CC alastairp

Pratha-Fish: afaik, there's no such documentation.

F

canonical MBID isn't a MB concept but mayhem can probably give a brief explanation of the concept

sure.

we've got the concept of a release-group, yes?

a release group may contain one or more versions of a given release.

how do you know which one is the "most representative" of those?

monkey: thankyou!

yess, I can try `display: flex` (with `wrap`, right?)

mayhem: that looks awesome!

there isn't a good way to pick one. so we mainly go with the first digital version and call that the canonical release in a given release group.

I was working on fixing the mobile and tablet layouts. On that topic, can you check the mobile layout? (hint: filters)

aerozol suggested a collapsed floating filter button yesterday. I was thinking that we can have the expanded filter layout at the start of the page and it collapses into a floating filter button while scrolling. I did some googling but I can't think of a logic for this one yet :p

Probably not with wrap. This is for the three column layout (filters, release grid, slider) so we don't want them to wrap

monkey: alright

I think the release grid works well as-is.

so then for each recording that appears on a canonical release, those recordings are considered canonical.

I mean with css grids

all other recordings that appear in the releaese group that do not appear on the canonical release are non-canonical.

css grids scare me

Pratha-Fish: does that make sense?

I mean… I think you did good with the current layout, don't you think so?

I always mess it up when I start using css grids

its because of bootstrap tho

aside from improving round-off errors and improving the handling of non-square images, I'm quite happy with this approach.

monkey: i'll try out that function

mayhem: Thanks! That helped a lot :)

Different css grid mayhem ;) This is for https://test.listenbrainz.org/explore/fresh-rel...

aah, sorry.

I was confused since I clearly do not use css-grid.

It's grid day !

alastairp: How much time left until you clock out for the day? (I'll get to you with as many updates as possible before you go)

grid day! :D

I knew you weren't a square mayhem !

heh

Also while we're at it, how long would it take to publish a blog on blog.metabrainz.org once the final draft is ready?

just press the button and done.

lucifer: the user fresh releases work :) I noticed that the user and sitewide responses have different required fields like the `release_group_secondary_type` and `caa_id`. https://usercontent.irccloud-cdn.com/file/lu7GK...

chinmay: hmm, what differences do you see?

The filters look pretty good to me chinmay. Perhaps we could have the slider horizontal and under the filters on mobile?

The collapsible floating button would take a bit more time to figure out, but it's doable. We use a library for drag and drop of the youtube video player (react-draggable), in case that could help with the floating button (not sure we want to move it around, but thought i'd mention it)

Pratha-Fish: it's getting later here, but I'm more or less around if you get something to me today

say, 2 hours

Sounds good

lucifer: Sitewide: https://jsonhero.io/j/nhGbYZ3yCGv2 User: https://jsonhero.io/j/YDlbaEdaCWiy

there's a difference is schema

confidence is an obvious one

yes confidence is extra in user ones. and the release group type is sometimes omitted from sitewide ones (not sure why, i'll make them mandatory). but everything else should be same

They are marked optional that's why :p

ah no that's not what i meant. if you mark as optional, the key will still appear but with the null value.

oh

the to_dict just below explicitly deletes the key if its null due to which its not always present.

but i am wondering why delete it all because we usually don't do that.

ooo understood

my only concern was that the schema were not consistent

yes, i think you can use the sitewide releases schema + add an optional confidence field to it.

that should work in all cases.

if you see the screenshot above for user releases you'll see "Single + null" on the tooltip

wait let me try something out to make it consistent

i see. yeah you'll have to add an if check for that.

okay

monkey: I was thinking a horizontal top/bottom sticky timeline as well :)

i don't think we need to move the filter button around. bad ux in this case

Certainly doable. I started writing something up about how to use flexbox to go from columns to rows layout, maybe even how to reorder the rows if needed, but then I realized we would need to make the slider horizontal, which means using media queries in the react component. Certianly doable (it is used in a couple of places in the codebase) but I just don't like the idea :p

But if that's the only solution…

or the best

P.S: I think you could have two covers per row in mobile view, rather than one. I think there's enough space

And that means a more usable page with half the scrolling :p

monkey: when you have time, i have put the image without node_modules on beta for testing.

pages seem to load fine and i was able to view source maps as well. not sure what else to test.

monkey: "but I just don't like the idea" which idea exactly? :p

Using media queries in JS

you're right, there's plenty space for two cols

oh that

I dislike that too

will test lucifer

Yeah, but we would need it to make the slider horizontal. Don't think we can do that cleanly with just css

hmm.. nope

gotta get dirty

mayhem: lucifer: monkey: aerozol: and anyone else - RFC. This is about the user fresh releases.

1. since we are sorting user fresh releases according to descending confidence score, the timeline gets messed up (https://usercontent.irccloud-cdn.com/file/lu7GK...). And there's no real use of timeline if the releases are not sorted according to date. In this case, do we get rid of the timeline altogether or think of something else? We can show some kind of feedback like a blurb(?) above or

below the release card based on confidence score.

2. if we do decide to not show timeline to user releases, I think we should keep the sitewide releases as the primary page where the user lands when they go to .../explore/fresh-releases and show a toggle or a link to the user that will take them to user specific releases. I thought about this because I believe the timeline (however buggy that may be at present :p) is one of the important experiences for the users who navigate

to this page.

maybe we should add a option to allow the users to sort by date or confidence score?

but that can come later i guess. my suggestion would be let's finish sitewide page first and get that deployed.

sounds good to me

i don't have opinions on whether the user specific page and the sitewide page should be the landing one but both should link to each other for logged in users.

I also agree we we should first focus on the sitewide page with the date slider sorted out.

Then we can figure out what we want to display for the user's personal page. The easy option is to just not show the date slider, or use it instead to navigate confidence score (not sure that's really important to be honest).

alright

We have the same problem of finding/linking personal vs sitewide stats for the reports page as we do for the fresh releases. Maybe we can find a good solution that would work for both (and other pages in the future)

navigating according to confidence score will be confusing imo

sounds good

you could hide the date slider when sorting by confidence but show it when sorting by date. but not sure if that makes UI awkward.

To recap the second question: we have for example https://beta.listenbrainz.org/user/mr_monkey/re... vs https://beta.listenbrainz.org/statistics . How do we easily navigate from personal to sitewide pages?

Calling dr. aerozol :p

maybe a message on the lines of view global/sitewide version near the top? and view personal version message near the top of sitewide page.

^ monkey: had something like this on my mind as well

Also my first thought

lucifer: beta seems to be working fine indeed. I tested pretty much everything I believe.

Lighter images !

awesome, thanks!

now need to figure if this can be united with static builder.

alastairp: I think I've added some significant and mindful upgrades to the blog. Could you take a peek if time allows?

Pratha-Fish: that looks much better to me. are you planning on using short bullet points in the final post?

or will you write them out in more detailed descriptions?

Pratha-Fish: in my opinion the flow of this rewritten version is much better, well done for turning it around so quickly. I've given some much more specific feedback on a few parts of your recent changes. I think that should be enough feedback for you to finish it off

So hungover...

mayhem: I was thinking I would do a PNG overlay of the whole image, e.g. the headphones and their shadow go over top of your images.

alastairp: I just haven't completely refactored the parts with bullet points yet. I'll only be keeping bullet points where it will benefit instead of over complicating the description, and hopefully it'll come much better off soon :)

But I've actually been thinking I might construct the whole thing from stock images rather than use single photos. Would you be interested in possible 'change the flooring', 'add a plant', 'more records' options? At least in future? I'll prototype it next week and see how it looks compared to the photos

I've also recieved the new changes on Google doc. Thanks, I'll update you with a complete doc early on Monday 🎉

Wtf mayhem you already did it! Awesome! I'll get finessing!!

This is such an exciting message history 😂

😂

monkey: chinmay: for navigating between personal and sitewide stats we could go a step further and have an option to type in any username/pick a friend from a drop down as well

chinmay: just had a thought, on mobile maybe we don't have the slider but have the date pop up when you scroll. I'll try find an example

That's when you scroll on Plex. Maybe an option if the slider is causing headaches. Could have a slight color change for future/past dates

aerozol: I love this idea!

(about personal/sitewide releases)

and i also love the scrolling idea

I wonder what such components are called

color change for dates will be interesting

aerozol: yes, please do that overlay -- trivial to add. :) good thinking.

aerozol: I'm eyeing https://usercontent.irccloud-cdn.com/file/SKxYv... as the next one I implement, because orange.

but I feel that there are too many circles and the fonts in the small circles are too small to read.

I think it would be best to get rid of the smallest size of circles

monkey: i tried the changehandler function. we don't need the offset height

monkey: i think i got a way around the "path fuckery". instead of doing it in docker do it in webpack config :p it seems to work in light testing.

will do more testing and let you be the judge of which one is preferable.

mayhem: I actually added more circles because it looked crappy with fewer! But hopefully how your code puts it together looks nice than my manual arranging

oh, a heh. I didn't think arranging them was my job. I thought it was going to be another template like the other one.

aerozol: orange supremacy! imo this one looks clean and easier on the eyes (maybe with some color combos like randoma11y.com) https://usercontent.irccloud-cdn.com/file/xDwDB...

For all of these I imagine we would let users pick colors but maybe have some nice presets? So they can click and have something nice

because this particular problem is generally HARD to do well.

mayhem: ohhh I thought the size might change based on listen numbers! Getting way ahead of myself eh

let me see if I can find a reliable algorithm that doesn't take too much computing power.

chinmay: I really love the wine color too... But I could spend all day making color combos tbh, fun times

if I can, then we're in. Otherwise might just be a template.