#metabrainz

Well, my week was kind of a mess, spent way too much time travelling between the city I come from and the one I study in but at least I got to see a concert in the large hall of https://musicbrainz.org/place/8da8cd3d-6162-471....

On the SpamBrainz side of things, I've gotten most of the API so far done but I'm struggling a bit with how to use Flask Blueprints (just takes a while to figure stuff out).

That's the super cool looking one, right? With all the levels

Yes! :D

(I've only been to https://beta.musicbrainz.org/event/9e7cf300-ebb... sadly)

I also forgot to commit my WIP work so I couldn't work on the train which had a lovely 50 minute delay at 1 in the night, yay!

fin.

(Only rsh7 and bukwurm / bukwurm_ left on my list.)

rsh7, go!

(Anyone else, speak up ASAP.)

hey

Last week I completed the work of importing the MB metadata in AB database. Then worked on the script to update the musicbrainz schema by importing the new data corresponding to a recording whenever there is any new recording insertion in acousticbrainz db.

And read about replication packets and figured out a little on how would i write a script to apply the packets to keep the musicbrainz data in AB db updated with the actual MB database

I have some questions regarding replication packets. bitmap: if you are free for a short discussion after this meeting, please let me know :)

yup, after the meeting :)

fin! bukwurm?

Hi

bitmap: thanks :)

This week on mostly code refactoring and improving mapping.

I set up test environment, wrote some tests.

I am wrapping up last phase objectives.

Documentation and improvement of mapping of some dumps is on radar for this week.

last phase of gsoc?

last == previous

So that's it for this week. :)

oh. ok.

bukwurm: So… fin?

Freso: Yeah

:)

Alright, great!

No one else is left on my list and I haven't seen anyone else asking to go, so…

Thanks bukwurm and everyone else for your reviews!

Next up is:

INST-24: Backwards electric guitar https://tickets.metabrainz.org/browse/INST-24

hi guys!

That's just backwards.

please read the ticet and the comments

So as asked last week, I would like consensus about https://tickets.metabrainz.org/browse/INST-24

it seems to be an "art instalment thing" to me which could be served fine with Instrument credits (see my comments on the ticket)

However, I am not certain certain, so incase someone has any counteropinions, _now_ is the time to speak up! :)

freso, you commented on it al ong time ago, do oyu have any imput at all?

CatQuest: Not really. I looked at the ticket again, but I don't know either which way.

a long time ago, you input*

i fear is that it will basically become a dumping ground for any "guitar played some other way" credits

"altered guitar" i belive we eiher already have or there is a ticket for it

I think I'm happy with ACs (ICs?), unless it becomes common enough, in which case we can review

Same.

any one else?

If there is a generic "guitar derivative"/"altered guitar" then the actualy "backwards guitar" instrument can be put there with AC/IC, and guitars played backwards can be AC/IC'd to regular "guitar"/"electric guitar".

yes

And as reosarevok said, we can review later with more data.

it's an archived rquest and noone else has looked at is since atleast before 2014

so deff. if suddenly it becomes popular or something. reopen or make an ew ticket

a new*

I'm sure we have plenty of ew tickets already. :)

extra props to HibiscusKazeneko for also replying ot this ticket

Freso: deff 😅

So done with this DR?

yup, seems liek it

like*

Alright!

thnak you everyone

Thanks for your time everyone!

</BANG>

\o/

thanks Freso

yes, thanks freso, threso

iliekcomputers: hey!

rsh7: you had questions about replication?

I'm going to delete that table now. Won't take much time

bitmap: yeah, hi!

hey

actually I was working on importing the Musicbrainz data in Acousticbrainz database and now i need to add a functionality to keep musicbrainz schema in AB updated with the actual Musicbrainz database

and I would use replication packets to apply in musicbrainz schema tables

kartikeyaSh: awesome.

bitmap: so, i was thinking that from which replication packet should i start to apply? I thought to go with the latest packets but I read that the new replication packet is applied only when the previous one is already applied to the database. So, from where should i start?

you start by importing a data dump, and the last replication sequence applied to that dump is stored in that dump (in the replication_control table)

the tools provided by mb (admin/replication/LoadReplicationChanges) automatically know what replication packet to download and apply

I assume you're using mb's tools, or mbslave, and not writing your own :)

oh okay.

No, actually I didn't use mbslave

We needed few tables from MB, so I created a schema for only those tables and wrote a script to import the data

from the fullexport dumps?

and I was testing with sample MB dumps, I found that the replication_control table is empty there.

right

it seems like it would be better to add an option to mb's import script to specify which tables you want to import, instead of reinventing the wheel, but maybe you have other requirements

we only wanted those rows that were relevant to us (for ex: only info about recordings that are in AB)

yeah

Alright! So, now I am thinking if I create one more table in musicbrainz schema which will store replication sequence number and stuff and then downloads the new packet and script to apply it on the tables and then update the sequence number. But the problem is, what replication packet to start from.

the script that i wrote to import the data is in here - https://github.com/metabrainz/acousticbrainz-se...

iliekcomputers: done

deleting table

what happens when a recording is added to ab but it doesn't exist in the musicbrainz schema because you didn't import it?

bitmap: we plan to have a script running that finds such recordings and imports their data.

kartikeyaSh: thanks.

where will you import it from?

production MB, the way CB reads it rn.

cool

soo this import_mb_data.py script is also reading from the production mb database, not importing from a data dump

if that's the case then you can get replication_control.current_replication_sequence at the beginning of the script, and that's the sequence you start from

there will likely be conflicts (data already existing) when the next packet is released, and you'll need to expect and handle those

Alright, got it!

Thank you :)

seems like a good argument for keeping all meb projects in one database though

yeah.

we came across some issues that are hard to solve efficiently still in CB because we can't join tables across projects.

in case anyone is interested in knowing how the graduation robes look like in India :D https://usercontent.irccloud-cdn.com/file/3uF0I...

Also that piece of cloth around my neck is our graduation 'hat' replacement

beautiful :) much better than french ones (there's none in most schools)

So you're a priest now?

^^ ;)

That comes as an added benefit of getting an engineering degree in our college

Sometimes picard does not save a cover.jpg when the release has a cover or the files have embed cover?

congrats on being all smrt now samj1912 !