#musicbrainz

Wondering what's the usual way of tracklisting podcasts/mixes when they are presented as a single recording. Example: https://musicbrainz.org/release/79772084-f2ca-4...

In the case of https://musicbrainz.org/release/78b2efc3-3d92-4... I put it as an annotation but it's obviously not the most database-friendly way.

There's the DJ-Mix of relationship which I also have used in the past but I'm unsure if it's supposed to be used for that.

I think using the dj mix relationship is fine. It did this too:

Is there any way for an application to submit tags on behalf of a user without having to ask for the users username and password?

How would you prove that the user had actually submitted the tags? That sounds like a recipe for disaster, unless I'm missing something.

Tokens

I could see having temporary oauth tokens for submitting to the API instead of raw credentials. Those token would be API only so the app doesn't have full access to your MB account.

Although __please__ don't do it like YouTube. Nobody wants to register applications and have secondary credentials

there's no way to submit edits to the main text part of the database - it's strongly recommended to do edits via the musicbrainz editor pages because of the tools, validations, and links to the docs available there. Note that for adding new releases, the release editor supports "seeding", which lets you provide some pre-filled values.

Musicbrainz does already have oauth tokens and such for applications - I use that in my isrc submission tool https://magicisrc.kepstin.ca/ for example (click login in the top right).

but the data you can submit with that is limited to ... isrcs and scanned barcodes, i think?