#musicbrainz

the shoes are killing me

<10volumetrique> So apparently there's no ETI lower casing for Japanese releases and I think that is stupid

<10volumetrique> https://musicbrainz.org/edit/113115353

<10volumetrique> I mean, the guidelines are pretty clear that Instrumental should stay capitalized because of how it is on the cover... But isn't that completely irrational for stuff like ETI

<13BusterEverett> Japanese releases follow their own special rules

<10volumetrique> Which make sense except for eti

<10volumetrique> Why should they be exempt of lowercase on stuff like Instrumental or remix

<10volumetrique> It just doesn't make sense to me

<10volumetrique> So I'm just raising my concern 😅

<12Aerozol> Going to stream some editing if anyone wants to hang. Just for a little bit, been a while, need to brush the dust off! https://www.twitch.tv/aerozol2

<13BusterEverett> ETI is a subset of Style and Japanese is fully exempt from all Style for the culturally relevant aesthetic reasons the guidelines state. That particular release has the info printed in that uppercase styling as well. If it was lowercased, then I'm sure it would apply,

<13BusterEverett> Here's an example of style not applying in Korean: https://musicbrainz.org/edit/111146690

<10volumetrique> No, what I meant is that I disagree with these guidelines. Not that I will vote against the edi

<10volumetrique> I think Japanese style should have ETI guidelines is what I'm raising

<10volumetrique> Is there really a reason for it not to have it?

<13BusterEverett> Read the guideline

<13BusterEverett> "Japanese artists have a tendency to choose capitalization and punctuation for aesthetic reasons, and to be very consistent regarding case over all releases. For this reason, words in the Latin script on a Japanese release should be in the same case as on the album art if other available sources"

<13BusterEverett> Japanese artists have a tendency to choose capitalization and punctuation for aesthetic reasons, and to be very consistent regarding case over all releases. For this reason, words in the Latin script on a Japanese release should be in the same case as on the album art if other available sources, such as official discography or record label pages, are consistent, not normalized according to English or other

capitalization standards.

<13BusterEverett> Disagree with it if you wish, but I would be exceptionally surprised if there would be any alteration to that rule.

<04zoe.division> I used not to have any qualms with that guideline, till very recently I realized I was exhausted by the majority of english-titled japanese albums just screaming at me in my library in all-caps 🥲

<04elomatreb> Ideally™ we will Eventually™ get the "alternate tracklists" feature in the MB server that would allow storing two variants of such tracklists, one "original" and one that's standardized

<10volumetrique> I did read it. Still doesn't make a lot of sense for extra information in this day and age where remix and other info is written the English way. I'd appreciate it if I was not talked about in that tone, please 🙂

<10volumetrique> Just raising my opinion. Consensus will do what should be done.

<04elomatreb> note that disclaimer though, it's not an unconditional blanket exception because it's from a Japanese artist

<04elomatreb> it should be consistent across available sources for that exception to apply

didn’t notice moviebrainz.org rooms are dead

<05rustynova> Oh missed that. Wanted to see how pros were doing it

<05rustynova> BTW, finally added the Import with Harmony button https://github.com/RustyNova016/MusicBrainz-Use...

<05rustynova> https://cdn.discordapp.com/attachments/11939991...;

Is there any way to use Harmony data to improve existing release

other than copying & pasting of course

Not yet, you can hack Harmony's HTML form with your browser's developer tools to POST to an existing release, but there are two issues which have to resolved before this can be officially supported.

Namely MBS-13579 and a more general scenario as described by MBS-13493

MBS-13579: Seeding release labels for an existing release is only rarely working https://tickets.metabrainz.org/browse/MBS-13579

MBS-13493: Can't seed updates to existing tracklist artist credits https://tickets.metabrainz.org/browse/MBS-13493

alright, thank you

<11sound.and.vision> is search having a bad time a gain?

kellnerd: is https://tickets.metabrainz.org/browse/MBS-13616... not technically possible rn?

MBS-13616: allow seeding advanced relationships

(tagging you since harmony was mentioned)

reosarevok: I am not aware of any way to seed the release relationship editor, but I haven't checked again recently.

Hmm. There are scripts that clone release rels and stuff like that but maybe they don't actively seed but do it differently

bitmap would surely know

I don't think there's a way to seed the release one at the moment

Hmm, ok. I guess it shouldn't be super difficult in theory since we know how to seed relationship editors?

In theory 😉

but the release one doesn't use Controller::Role::EditRelationships, which is where seeding is handled for the other forms, so it might be more difficult than we expect

Oh no.

!recall oh no.

<13BusterEverett> MB attempts to make considerations for other cultural customs rather than flatten idiosyncrasies to the Western/English paradigm. Approaching interpretation of the rules through that lens is why it’s not making sense.

<13BusterEverett> It already has and that’s why it is the way that it is

<04zoe.division> the joy of finding a new release to add to the database...... 😸